Reference no: EM133749867
Case project - Software design document
LO1: Demonstrate comprehension of key methodologies and tools for the analysis and design of enterprise information systems.
LO2: Design data flow diagram(s), entity relationship(s) and state process modelling for user requirement analysis.
LO3: Develop, analyze, and diagnose conceptual, logical, and physical web and UML data models.
LO4: Investigate and incorporate user requirements, business rules and constraints into the design of an information system.
Detailed Submission Requirements
In this assessment, students must work in a group to prepare a case study of designing a software project.
A 2000-word Report on Software Design based on your Selected project details.
A 15-minute Presentation in week 4, session 7 during your class time by whole group.
You are required to form groups of Three to Four (3 to 4) students.
Your group is required to research and analyze a real-life situation and prepare a software design document of a project. Text of the project document can be prepared with essay writing AI (Artificial Intelligence) technology like service including referencing in the style you prefer.
Suggested topics (list is not restricted):
Fingerprint voting system
Peer assessment system
Video attendance system
Crowd control system
Sentiment analysis for product rating
Parking lot booking system
Weather forecasting system
Casual Marking and Control System
Internship Management System.
Your report must follow the structure given below:
Executive Summary
It should summarize the key points of the Software Design Document.
Introduction
Introduction has the following sections:
Background of Project: Explain the aims, objectives, and importance of the project. What problem you are solving.
Purpose: Explain the purpose of the Software Design Document.
Structure: Explain the structure of the Software Design Document.
Information Gathering
This section has the following three components:
Two information gathering methods: Select one interactive and one unobtrusive information gathering method and state its implementation for your software application.
Three Case Problems: Analyze at least three case problem scenarios for your selected software project, simplify each scenario by suggesting and applying information gathering approach.
System overview: Provide an overview of main functionalities of the system.
Design Viewpoints
Logical Viewpoint: Explain the logical viewpoint related to your project. Draw class diagrams to explain the logical viewpoint.
Information Viewpoint: Explain the information viewpoint related to your project. Draw Entity Relationship (ER) diagrams to explain the Information viewpoint.
Interface Viewpoint: Explain the various interfaces of the project. Provide screenshots (mockups) of various aspects of Front End of the software.
Interaction Viewpoint: Explain the interaction viewpoint related to your project. Draw Sequence Diagrams to explain the Interaction viewpoint.
References and Appendices
In Harvard referencing style
RETENTION OF RECORDS
Students are required to keep a copy of all items submitted or completed for assessment or evaluation until the end of the grade appeal period.
ULO 1: Demonstrate comprehension of key methodologies and
ULO2: Design data flow diagram(s), entity relationship(s) and state process modelling for user requirement analysis.
ULO3: Develop, analyze, and diagnose conceptual, logical, and physical web and UML data models.
ULO4: Investigate and incorporate user requirements, business rules and constraints into the design of an information system.