Lab OverviewScenario/SummaryYou 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 di
Student Name: | |
Course: | CIS339 |
Session (month, year): | 03/2019 |
Object-Oriented System Analysis and Design
The School of Prosperity
Student Records System (SRS)
Week 1—System Request 3
Week 2—Use Case Diagram and Use Cases Descriptions 6
Week 3—Class Diagram and CRC Cards 12
Week 4—Sequence, Communication, and State Machine Diagrams 15
Week 5—Package Diagram 19
Week 6—Method Contract and Method Specification 21
Week 7—Object-Oriented Application Coding 25
Week 1—System Request 3
Week 2—Use Case Diagram AND Use Cases Descriptions 5
Week 3—Class Diagram AND CRC Cards 9
Week 4—Sequence, Communication, and State Machine Diagrams 15
Week 5—Package Diagram 19
Week 6—Method Contract AND Method Specification 21
Week 7—Object-Oriented Application Coding 24
Week 1—System Request Use this system request template and complete the SRS system request. System Request— Project sponsor: School of Prosperity (SoP) Business Need: The existing desktop system will be upgraded to web-based application and this system will be used to maintain records of students, courses, classes, and student registration and grades. Business Requirements: The system is capable of having the following functonalities:
Business Value: Conservative estimates of tangible value to the company include:
Special Issues or Constraints:
| |
Validate and verify that your system request addresses the SRS Preliminary Planning Overview. The business need area explains what the SoP is requiring the system to operate. The business requirements consist of what the system must be able to handle and the expectations of the system (once it’s completed). The business value breaks down the details of information that the new system will save on both staff hours and finances for the school. The issues area give problems that could exist once the system is implemented. | |
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. I, carefully, read the SRS Preliminary Planning Overview and highlighted the important business needs that the SRS system is to meet. I then started to complete the various sections of the System Request Form and while doing so, I referred back to the SRS overview document to confirm my conclusions and understanding. The result of this iterative process is the current System Request Form. |
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
Register a Student for Classes
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Validate and verify your use case diagram and use case descriptions against the SRS Requirement Definition and the SRS System Request. SRS has 4 major functionalities which are covered in the 4 use cases, which are as follows:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. I first read the case thoroughly and then listed all the functional and non-functional requirements on the page. Then I extracted the major use-cases from them. After that I generated the flows for those use cases. After extraction of the major use-cases and their actors I build a use-case diagram and after getting the flows I end up getting the fully dressed use cases. |
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 Card
Class2 CRC Card
Class3 CRC Card
Class4 Register
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Validate and verify your class diagram and CRC cards against the SRS use case diagram and use case descriptions. There are 4 major use cases, so for each case there can only be one class, because each use case is about updating the entries for one entity. There is one CRC card for each class and every detail about that class is written there. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. The decisions I made are quite simple. Because I created all the necessary classes and made the association relations in between them. Then I made CRC cards for those classes. |
Week 4—Sequence, Communication, and State Machine Diagrams
Generate a sequence diagram for the SRS system Register a Student for Classes use case. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: Sequence Diagram for the Register a Student for Classes Use Case
Generate a state machine diagram for the SRS system RegistrationRecord object/class (the class that maintains the registration of a student in a class). The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: State Machine Diagram for the RegistrationRecord Object | ||
Validate and verify your behavioral diagrams against the SRS Register a Student for Classes use case description and the SRS class diagram. | ||
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. |
Generate a package diagram for the SRS system. The diagram must be generated by a UML drawing tool. Copy and paste your diagram here: SRS Package Diagram | |
Validate and verify your package diagrams against the SRS class diagram and the SRS Register a Student for Classes use case sequence and communication diagrams. | |
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. |
Use this method contract template and complete a method contract for the GetCourseByCourseID() method of the CourseList class. CourseList.GetCourseByCourseID() Method Contract
Use this method specification template and complete a method specification for the GetCourseByCourseID() method of the CourseList class. CourseList.GetCourseByCourseID() Method Specification
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Validate and verify your method contract and method specification against the CRC card for the CourseList class and the CRC card for the Course class. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. |
Copy your code text of the CourseList.GetCourseByCourseID() method and paste it here: Code Text of Your CourseList.GetCourseByCourseID() Method Copy a screenshot of running the unit test of the CourseList.GetCourseByCourseID() method and paste it here: Screenshot of running the Unit Test of CourseList.GetCourseByCourseID() Method Zip all the files you used in this coding project; copy and paste the *.zip file here so that it can be unzipped and loaded into the IDE and run on another computer: A *.zip File of all of the Coding Project Files | |
Validate and verify your code and screenshot of the CourseList.GetCourseByCourseID() method against the method contract and the method specification of the same method. | |
Explain how you completed your work, the decisions you made to arrive at your conclusions, and the lessons you learned. |
Page 28 of 28