Summarized PRJ Guidelines

You might also like

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 1

-

TITLE Abstract Introduction: . Background: Current system in use Problem statement: state what difficulties/challenges they are facing with the current system Proposed solution: What do you propose to do? Why your solution and not the existing ones? Little or no local support, cost, system configuration, bugs, etc System objectives: to increase efficiency, better information for decision-making, accuracy, efficient data storage and sharing, ease of upholding of standards, integrity and uniformity Project Objectives: What you hope to achieve in undertaking the project. Deliverables: o Functional reqments: what the system must have in order to function: database, modules (customer registration, quotes, etc) o Non-functional: What could be in the system that even if it didnt work, the system would function. E.g. some of the reports, login module System environment, o tools: Development tools: java, VB .NET, Database Man sys: php mysql, oracle, sql server, Documentation/Design tools: MS Visio (documentation & design), MS Access (for prototyping), Pentium X, Clock speed, RAM, H/Disk o Literature review: from analyzing the problem, what solutions exist out there, other developers, software houses, describe the solution: Features, local support, cost, etc. Methodology

You might also like