0% found this document useful (0 votes)
9 views2 pages

Software Project Guidelines

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views2 pages

Software Project Guidelines

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

NATIONAL DIPLOMA IN INFORMATION TECHNOLOGY

SOFTWARE DEVELOPMENT PROJECT GUIDELINES

 Introduction
 Preface
 Acknowledgements: vote of thanks to people/organisation who helped you.
 Methods of study: observation, questionnaires, interviews

PROJECT DEFINITION
 Name of system
 Executive summary- General overview of the study
 Description of the current system
 Problems of the current system
 Inputs of the existing system
 Outputs of the existing system
 Brief description of the proposed system
 Objectives of the proposed system
 Outline of the system study. Fact finding techniques
 Results of findings
 Alternative solutions: pick several alternatives (give pros and cons for each)
 Terms of reference
 Scope and boundary of the system
 Time schedule

FEASIBILITY STUDY
 Introduction
 Existing system summary and problems
 Benefits of the proposed system
 Types of feasibilities
o Technical feasibility
o Operational feasibility
o Social feasibility
o Schedule feasibility
o Legal feasibility
o Economic feasibility
o Political feasibility
etc
 Conclusion and recommendations

ANALYSIS
 Existing system description
 Problems of the existing system
 Fact finding methods/techniques
 UML Diagrams and ERD Diagrams
 Inputs documents
 Outputs documents
 User requirements
 Alternative solutions
 Recommended solution

DESIGN
 Proposed system description
 System flowchart
 Input, output and process Design
 Database and file design
 User interface design
 Design of system controls and security
 Proposed system UML diagrams

DEVELOPMENT
 Coding and testing( sample test data and results of tests runs)

IMPLEMENTATION AND POST IMPLEMENTATION PLAN


 System implementation plan (Changeover methods)
 Acquisition of hardware and software
 Installation of hardware and software
 Technical documentation/User manual
 Acceptance testing
 Training

CONCLUSION

Appendices

You might also like