solved According the case and scope management plan finish the Project

According the case and scope management plan finish the Project Scope Statement
1.Executive Summary
A well-written Executive Summary is one that can be used in multiple documents as needed.  As with other Executive Summaries, this summary should briefly describe the project’s background and the organization’s purpose and objectives for the project. 
A short, 2 to 3 paragraph description of the business needs and key features of the project. It allows the stakeholders to quickly develop knowledge about the project.
2.Business Requirements
The specific statement(s) that describe the organization’s business problem to be solved. Usually, this information comes from the original business case or project charter (or case study information). By including the business requirements, anyone reading the document is reminded of why the project was undertaken.
– Please submit at least 5 business requirements (Must be SMART and Testable) for this assignment.
3.Solution Requirements
This section lists all relevant technical, project and regulatory requirements, classified by priority. Typically, solution requirement priorities are “must have”, “should have” and “nice to have.” (MoSCoW technique).
This section also identifies verification method and acceptance criteria used to determine whether a requirement has been successfully met.
– Please submit at least 7 solution requirements – adequately prioritized by category with effective and testable/measurable acceptance criteria.
4.Exclusions (Out of Scope)
This section explicitly declares project scope items that will not be addressed by this project.
– Please submit at least 5 out of scope project exclusions.
5.Key Project Features
This section, identify any conditions that limit project planning activities (such as – detailed project scheduling and budgeting.)  Constraints of the project such as “must have “milestones, constrained due dates, availability of certain important personnel or project budgetary restrictions.
– Please submit at least 5 project limiting conditions.
6.Assumptions & Risks
This section addresses risks identified in the business case and project charter. It is important to update the status of any risk identified during project initiation or identify additional risks uncovered in the requirements collection process.
– Please submit at least 5 project assumptions and risks
7.Approvals
This is a space for stakeholders to formally approve all of the scope statement content, including all requirements and their priority.
It is important for all stakeholders to understand and agree upon the scope statement contents. Once signed, the project team will use the scope statement to begin identifying detailed tasks, resources, durations, and the overall project schedule and budget. It is critical the scope statement be as accurate, complete, and realistic as possible.