SWE 201: Introduction to Software Engineering Group Assignment #3 - [CLO# 2.1, 2.2, 4.2] Due Date: Thursday 11/10/1443 (
Posted: Fri Apr 29, 2022 6:32 am
SWE 201: Introduction to Software Engineering Group Assignment #3 - [CLO# 2.1, 2.2, 4.2] Due Date: Thursday 11/10/1443 (12/05/2022) at 11:59 PM. Assignment Instructions: . This is a group assignment. Work with your group. . Use the project report template provided on blackboard to write your report. Your project report should be organized and well written. . Make sure you fill out the contribution breakdown tables on the second page of the report according to the sections completed. • Place all files in a directory called "GroupName". Before submitting, zip your directory and upload a single zipped file to Blackboard. • Every group should upload one submission only. • Late submissions will be penalized 10% of the available points per day and will not be accepted three days after the due date. Assignment Overview: In this group assignment, you will make the required changes to the second version of your project report based on the feedback you received from me during the first presentation. You will also work on the details of your project's functional requirements (Chapter three in the project template provided on blackboard). Assignment Details: You will as group, define the following: 1. Stakeholders A system stakeholder is any person or organization who is affected by the system in some way and so who has a legitimate interest. In this section, you will define the stakeholders for your project. Every stakeholder must have a brief description. Patients: Description of this stakeholder Doctors: Description of this stakeholder. 2. Use Cases 2.1 Casual Descriptions In this section, you will define the use cases for your project and provide a brief description to each. Each use case must have a unique identifier that has the prefix "UC-" (UC-1, UC-2 ... etc.).
2.2 Use Case Diagram A use case diagram can summarize the details of your system's users (actors) and their interactions with the system. In this section, you will design the use case diagram as explained in class. 2.3 Detailed Descriptions In this section, you will provide a detailed description of FOUR or FIVE use cases (depends on the number of students in each group) in a tabular form as follows: UC#2: Registration REQ-5, REQ-8 Use Case Related Requirements Initiating Actor Participating Actors Preconditions Postconditions Users System Admin, Customer System should be active and running User's data has been saved into the system's database 2.4 Traceability Matrix In this section, you will map the functional requirements of your system with the use cases you defined in the previous subsection as below: UC81 X UCHZ UCH3 х REO-la RE0-16 REQ-2 REQ-3 X X х X 3. Sequence Diagrams In this section, you will develop a sequence diagram to TWO of the use cases you defined in the previous subsections.
2.2 Use Case Diagram A use case diagram can summarize the details of your system's users (actors) and their interactions with the system. In this section, you will design the use case diagram as explained in class. 2.3 Detailed Descriptions In this section, you will provide a detailed description of FOUR or FIVE use cases (depends on the number of students in each group) in a tabular form as follows: UC#2: Registration REQ-5, REQ-8 Use Case Related Requirements Initiating Actor Participating Actors Preconditions Postconditions Users System Admin, Customer System should be active and running User's data has been saved into the system's database 2.4 Traceability Matrix In this section, you will map the functional requirements of your system with the use cases you defined in the previous subsection as below: UC81 X UCHZ UCH3 х REO-la RE0-16 REQ-2 REQ-3 X X х X 3. Sequence Diagrams In this section, you will develop a sequence diagram to TWO of the use cases you defined in the previous subsections.