Object-Oriented System Analysis and Design The School of Prosperity Student Records System

profileSuperClass
 (Not rated)
 (Not rated)
Chat

Student Name: Course: CIS339 Session (month, year): Object-Oriented System Analysis and Design The School of Prosperity Student Records System (SRS) WEEK1—SYSTEM REQUEST 3 WEEK2—USE CASE DIAGRAM AND USE CASES DESCRIPTIONS 5 WEEK3—CLASS DIAGRAM AND CRC CARDS 9 WEEK4—SEQUENCE, COMMUNICATION, AND STATE MACHINE DIAGRAMS 15 WEEK5—PACKAGE DIAGRAM 19 WEEK6—METHOD CONTRACT AND METHOD SPECIFICATION 21 WEEK7—OBJECT-ORIENTED APPLICATION CODING 24 Week1—System Request 1 Use this system request template and complete the SRS system request. System Request—Name of Project Project sponsor: Name of Project Sponsor Business Need: Short description of business need Business Requirements: Description of business requirements Business Value: Expected value that the system will provide Special Issues or Constraints: Any additional information that may be relevant to the stakeholders 2 Validate and verify that your system request addresses the SRS Preliminary Planning Overview. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week2—Use Case Diagram andUse Cases Descriptions 1 Generate a use case diagram for all of your use cases, including their actors. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: SRS Use Case Diagram Use this use case description template and complete the two SRS use cases of (1) Maintain Class Records and (2) Register a Student for Classes. Maintain Class Records Use Case Name: ID: Importance Level: Primary Actor: Use Case Type: Stakeholders and Interests: Brief Description: Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events: 1. SubFlows: Alternate/Exceptional Flows: Register a Student for Classes Use Case Name: ID: Importance Level: Primary Actor: Use Case Type: Stakeholders and Interests: Brief Description: Trigger: Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events: 1. SubFlows: Alternate/Exceptional Flows: 2 Validate and verify your use case diagram and use case descriptionsagainst the SRS Requirement Definition and the SRS System Request. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week3—Class Diagram andCRC Cards 1 Generate a class diagram for the SRS system. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: SRS Class Diagram Use this CRC template and complete a CRC card for each class you designed in your SRS class diagram. Class1 CRC Class3 CRC Card Front: Class Name: ID: Type: Description: Associated Use Cases: Responsibilities Collaborators Back: Attributes: Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations: Class4 CRC Card Front: Class Name: ID: Type: Description: Associated Use Cases: Responsibilities Collaborators Back: Attributes: Relationships: Generalization (a-kind-of): Aggregation (has-parts): Other Associations: ClassX CRC Card 2 Validate and verify your class diagram and CRC cards against the SRS use case diagram anduse case descriptions. 3 Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. Week4—Sequence, Communication, and State Machine Diagrams

    • 8 years ago
    Object-Oriented System Analysis and Design The School of Prosperity Student Records System A+ Tutorial use as Guide
    NOT RATED

    Purchase the answer to view it

    blurred-text
    • attachment
      object-oriented_system_analysis_and_design_the_school_of_prosperity_student_records_system.docx