Part I: Elicit Requirements Document the requirements for your project. At a min

Part I: Elicit Requirements
Document the requirements for your project. At a minimum, you should identify three-to five-high level requirements, functions, and features and fifteen-to twenty-five-detailed requirements. The requirements you identify will be used as the basis for the WBS.
Note. Provide the appropriate level of detail while maintaining a reasonable number of requirements since you will base your planning and scheduling on these requirements.
Format your requirements in one of two ways:
Simple Sentence format that outlines the high-level parent requirements and then breaks these down into multiple user requirements, which then flows into system requirements. “The system SHALL…”
User Stories format, you will have high-level requirements known as Epics and in each Epic, you will have multiple User Stories that follow the formatted language: “As a ROLE, I need a FUNCTION, so that I can, BUSINESS VALUE”.
Note. Remember, your requirements should represent ALL the scope in your product and project.
Part II: Work Breakdown Structure
Create a WBS that identifies the following:
Summary tasks – A summary task is a parent or top-level task that groups together a set of related detail tasks (subtasks). For example, the Summary task “System Integration Testing” might include detail tasks such as “Test User Interface”, “Test Data Integrations” and “End to End Testing”, these detail tasks should then be further decomposed to show more subtasks that are related to the detail tasks. Summary tasks organize related tasks in the WBS in a logical manner.
Detail tasks – Subtasks to at least a level 3 decomposition (excellent submissions will include WBS level 4 under several Summary Tasks).
Milestones – Project milestones mark specific events along a project’s timeline. They are checkpoints that identify when groups of activities included under a Summary task have been completed and/or a deliverable approved by the sponsor or customer. Milestones are used to communicate progress to stakeholders.
Project management deliverables & tasks as well as closing tasks
Keep ALL of the tasks in one column of the Excel sheet (this will make it easier to import your task list to MS Project for the next assignment).
DO NOT provide start dates, finish dates, duration estimates, or Gantt charts (you will work on these items in subsequent lessons and assignments).
Note. While there is no minimum or maximum number of tasks, the expectation is that you will have between 75 – 100 tasks in your WBS and at least 3 to 4 levels of decomposition.
Cite any research or templates used consistent with APA style guidelines.
Submit your Requirements & WBS by the due date by clicking on the assignment in Canvas and uploading the document. Include a title page. Use Times New Roman, 12 point font.
Submission Requirement: This assignment is to be completed using Excel. Use one sheet in the Excel workbook to create the product/project functional and non-functional requirements and use a second sheet in the same workbook to create the WBS. You will only submit one file in total.
Please refer to the project charter file for this project information. Also, I also uploaded the WBS Excel file example for your reference. Please let me know if you have any questions.