Project Phase II – Content Requirement
Your individual project is developed based on the case descriptions. All the diagrams should be created using a diagramming tool (draw.io) and copied and pasted to a MS Word document, which then should be submitted to
The following details the required content for project
phase II.
Note: the following structure is expected to be followed and each diagram well formatted and presented.
Required Content
• Title Page
Table of Contents
• Assumptions (Optional)
• Revised content of project phase I including domain class diagram, use case diagrams, use case scenarios, and activity diagrams.
• System sequence diagram – Develop a system sequence diagram based on each fully detailed use case description
• Design class diagram – Develop a design class diagram for the system. Include all classes of the system in the diagram. However, for the classes that are not involved in the use cases you’ve chosen, you can keep their methods blank.
Detailed system sequence diagram- Develop a first-cut sequence diagram for each use case description you’ve chosen for the project
The table below summarizes the number of diagrams needed for project phase II
Diagrams
No. of diagram that needs to be produced
Domain class diagram
1
Use case diagram
Use case scenario
2
Activity diagram
2
System sequence diagrams
Design class diagram
1
Sequence diagram
2Project Phase II – Content Requirement
Your individual project is developed based on the case descriptions. All the diagrams should be created using a diagramming tool (draw.io) and copied and pasted to a MS Word document, which then should be submitted to
The following details the required content for project
phase II.
Note: the following structure is expected to be followed and each diagram well formatted and presented.
Required Content
• Title Page
Table of Contents
• Assumptions (Optional)
• Revised content of project phase I including domain class diagram, use case diagrams, use case scenarios, and activity diagrams.
• System sequence diagram – Develop a system sequence diagram based on each fully detailed use case description
• Design class diagram – Develop a design class diagram for the system. Include all classes of the system in the diagram. However, for the classes that are not involved in the use cases you’ve chosen, you can keep their methods blank.
Detailed system sequence diagram- Develop a first-cut sequence diagram for each use case description you’ve chosen for the project
The table below summarizes the number of diagrams needed for project phase II
Diagrams
No. of diagram that needs to be produced
Domain class diagram
1
Use case diagram
Use case scenario
2
Activity diagram
2
System sequence diagrams
Design class diagram
1
Sequence diagram
2
