You are deep into the analysis phase of your Internet-accessible Student Records

Question

You are deep into the analysis phase of your Internet-accessible Student Records System (SRS). You have finished both the Functional Modeling (activity diagram, use case diagram, and use case description) and the Structural Modeling (class diagram and the CRC cards). Now you are ready to move into the Behavioral Modeling where you will model the behavior or the objects that make up the SRS system. In this week, you will use your functional and structural models as the basis for your behavioral models that need to be developed for the SRS system. Specifically, your deliverables for this week are designed to develop these two behavioral diagrams for the Register a Student for Classes use case. Sequence diagram Communication diagram In addition, you will also need to create a state machine diagram for the RegistrationRecord class (the class that maintains the registration of a student in a class). These behavioral model and diagrams are major milestones in your architectural and design work. They give you your first opportunity to verify that your use case (in this case, Register a Student for Classes) could actually be implemented using the objects of your class diagram design. If you reach this verification, then you are done with the analysis phase of your SRS project. Deliverables Sequence diagram for the Register a Student for Classes use case Communication diagram for the Register a Student for Classes use case State Machine diagram for a RegistrationRecord object.
STEP 2: Create the Sequence Diagram
1. Create a sequence diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix iLab environment.
2. Explain your work and the decisions you made to arrive at your proposed solution.
STEP 3: Create a Communication Diagram
1. Create a communication diagram for the Register a Student for Classes use case using the Rational Software Architect software in the Citrix iLab environment.
2. Explain your work and the decisions you made to arrive at your proposed solution.
STEP 4: Create an Object State Diagram
1. Create a state machine diagram for an object of the RegistrationRecord class (the class that maintains the registration of a student in a class) using the Rational Software Architect software in the Citrix iLab environment.
2. Explain your work and the decisions you made to arrive at your proposed solution.

Explanation / Answer

The Functional Requirement specifies how the system or application SHOULD DO where in Non Functional Requirement it specifies how the system or application SHOULD BE. Some functional Requirements are Authentication Business rules Historical Data Legal and Regulatory Requirements External Interfaces Some Non-Functional Requirements are Performance Reliability Security Recovery Data Integrity

Related Questions

Navigate

• Browse (All)
• Browse Y
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.