B. Create UML Use Case Diagrams that could be inserted into a Software Requirement Specification (SRS) document that captures all functional requirements for this application. Use the task description in part A to elicit the requirements. You will only be required to document the functional requirements and provide Use Case diagrams. You do not have to complete a complete SRS document.
1. Document the functional requirements with UML use case diagrams for each requirement. For eachfunctional requirement provide the following:
• Requirement number and title
• Description of the functionality
• Input
• Results of processing or output
• Error handling or recovering requirements outlined
• UML use case diagrams (It is very important that your UML use case diagrams are complete and proper UML 2.0 Modeling notation is used.)
C. Create UML Class and Sequence Diagrams that could be inserted into a Software Design Specification (SDS) document. (It is very important that your UML diagrams are complete and proper UML 2.0 Modeling notation is used. Your design must be an object-oriented design.) You will only be required to submit the class and sequence diagrams and not have to complete a SDS document.
1. Your UML Diagrams should include the following:
a. Comprehensive Class Diagrams: Show all classes and all relationships among all classes. These should include the following:
• Relationships: Your object oriented design will require you to diagram all class relationships using correct UML 2.0 Modeling notation which minimally includes:
- Inheritance
- Association Relationships
• Multiplicity: Note any multiplicity in the relationships (e.g., 1-1, 1-many, etc.) using correct UML 2.0 Modeling notation.
• Attributes: For each class, all attributes with types (e.g., int, double, etc.) and access control (e.g., private, public, protected) need to be noted using proper UML 2.0 Modeling notation.
• Methods: Methods with signatures and access control should be provided. All methods have to be indicated, including all constructors, setters, and getters.
• Abstract Classes and Interfaces: Any abstract classes and interfaces used in your design must be properly indicated using UML 2.0 Modeling notation.
b. Sequence Diagrams: Model the object interactions required for each functional scenario. For each Use Case provided in the functional requirements section, at least onesequence diagram should be provided to model the interaction between the objects inside the application.
topsolutions8@gmail.com