IS314 – Computing Project

Systems Analysis and Design Document

Requirements
1. You must make corrections to your project proposal.
2. Prepare a document showing the different models for your allocated project.
3. You are going to draw models from the traditional structured approach or object-oriented approach.

Analysis and Design Document Template

 There are two templates provided at the end of this specification.
i. The first template should be used by students using the TRADITIONAL STRUCTURED
APPROACH for analyzing and designing their document.
ii. The second template should be used by students using the OBJECT ORIENTED METHOD
for analyzing and designing their document.
 All teams will need to use only one of these templates for their project. You must choose only one
approach for your Systems Analysis and Design and not both.
 Teams submitting documents containing both approaches will receive a mark of ZERO (0).

Reference
Reference all materials you use.

Final Document
You should put the following items in one PDF document:
 Cover page
 Corrected project proposal
 Systems Analysis and Design Document
 Mark Allocation Sheet

Submission
 Please submit an electronic version of the report on Moodle using the Systems Analysis and Design
Document Submission Box.

Note: Only the Project Manager needs to submit the report on Moodle.
Plagiarism
 No two teams should submit same or similar documents. All such cases will be dealt with
severely.

Queries
 Teams are to maintain contact through Moodle discussion forum.
 Consult your Project Supervisors during their consultation hours for queries.

IS314 – Systems Analysis and Design Document 1

Systems Analysis and Design Document Template (Traditional Structured Approach)

1. Project Title
2. Project Team
3. Table of Contents
4. Introduction
5. Context Diagram
6. Diagram 0 (Event-Partitioned System Model)
7. Diagram 1
8. Process Descriptions
9. Data Flow and Data Element Descriptions
10. Structure Chart
11. Pseudo code
12. Application Architecture
13. Deployment Environment
14. Development Environment
15. Entity Relationship Diagram
16. Data Dictionary
17. Functional Requirements
18. Non-functional Requirements
19. Conclusion
20. Appendix

IS314 – Systems Analysis and Design Document 2

 Systems Analysis and Design Document Template (Object Oriented Approach)

1. Project Title
2. Project Team
3. Table of Contents
4. Introduction
5. Use Case Diagrams
6. Use Case Descriptions
7. Detailed Class Diagram (Entity Classes only)
8. Sequence Diagram
9. Package Diagram
10. Application Architecture
11. Deployment Environment
12. Development Environment
13. Entity Relationship Diagram
14. Data Dictionary
15. Functional Requirements
16. Non-functional Requirements
17. Conclusion
18. Appendix

IS314 – Systems Analysis and Design Document 3

 Systems Analysis and Design Document Mark Allocation Sheet

After our group discussion, we recommend the following mark allocation to each group member, based on
level of contribution throughout this phase of the project.

Group Number: _________________________

Project Manager: ________________________

Student ID Percentage of final points

Signed
Student Name Student ID Signature Date

IS314 – Systems Analysis and Design Document 4