System Analysis and Design- Analysis Phase

Overview and Requirements Analysis is part of the Software Development Life Cycle (SDLC) that focuses on defining business requirements, business processes, and business rules. Some of the analysis activities include defining the functional and non-functional requirements, creating use case diagrams, creating use case descriptions, and creating a class diagram. please complete the following analysis activities: 1) Prepare a Requirements Document that describes the functional and non-functional requirements of your system. 2 ) Create a use case diagram and use case descriptions for each use case scenario in your use case diagram (minimum of 3). 3) Create a class diagram. 4) Create sequence diagrams for the major use cases in the proposed system (minimum of 3). 5) Document the minutes of all project meetings and other project related events associated with this milestone (date, time, team members present, topics discussed, action items). These items will be included in your submission. (50 Points) The following pages describe the recommended format and guidelines. Requirements Document The Requirements Document should outline the functional and non-functional requirements in your system. You may use any format for your requirements document. You should identify the type of requirement (functional, non-functional). If it is a non-functional requirement identify the category of the requirement (i.e. usability, reliability, performance, etc.). Each requirement should be clearly numbered and contain a brief description. The description should be specific. (10 points) Use Case Diagram and Use Case Descriptions Create a use case diagram for your proposed system and create use case descriptions for each use case scenario. The use case description should include the use case name, actor, brief description, normal flow of events, and exception flow of events. (15 points) Use Case Name: required Primary Actor: Required Brief Description: Required...