I need help developing a scope statement for the following project. Please provide details in any assumptions made.

Third Avenue Software is a relatively young company that develops mobile applications for phones. The company is still trying to find its corporate identity and permanent footing; it has released several moderately successful products but is still looking for a best-seller. Likewise, the company is still trying to determine which internal systems work best for its employees. Project management is among these systems. Many of Third Avenues products thus far have been designed to serve niche markets, so the companys cofounders instructed their marketing staff and programmers to identify markets that have more universal customer appeal. A couple of programmers quickly turned their focus to the field of health care, which affects everyone directly or indirectly. The programmers drafted an idea for an app that could serve as a one-stop shop for customers health-care information and needs. The apps name is to be determined, but it will contain the following features and information. Because Third Avenue knows from experience that software complexity ratings can be useful for later time and cost estimates, management asked the programmers to include initial complexity estimates for each major feature set. These numbers are shown in parentheses and use a scale of 1 to 8: A fitness tracker that allows customers to record and track their blood pressure readings, cholesterol levels, exercise regimen, calorie intake, and other related information (3). A medication tracker in which customers can enter their medications and schedules for taking those meds. This electronic pillbox will contain a calendar that displays the customers medication schedule and an alarm that sounds whenever its time to take one of the medications (3). A physicians list that is essentially an electronic address book for the customers health-care company, doctors, nurses, and physicians assistants. The list will include controls that allow customers to quickly incorporate existing entries from other contact lists in their phones (2). An emergencies list for storing vital phone numbers and addresses. This list will provide quick access to local in-network hospitals, urgent care clinics, and children or friends who can be relied upon to provide transportation in an emergency. As soon as the customer enters and saves an address, an interactive GPS map becomes available in a new window, with voice and text directions (6). An emergency information list in which customers store important information about themselves, such as medical conditions (e.g., the customer is diabetic), allergies, adverse reactions to drugs, and other personal information that a physician, nurse, or other concerned party might find useful in an emergency (2). A resources feature that lists links to other popular online health sites, such as WebMD. The customer will have the option to add links to the list (1). A payment feature that tracks the customers medical expenses and allows customers to make medical payments through their phones (4). Usability Usability will be extremely important, as customers will tend to be older than those who download and buy the majority of mobile apps. For example, the app will require a prominent control for increasing the text display size. Such controls are available in a phones Settings feature, but many older users tend not to explore such hidden settings. The features mentioned above need to be immediately available and easily accessible when the app is launched. Another usability issue is crucial: How does the app balance customer privacy against the need to share some of the customers information in an emergency? For example, the emergency information list might be of no use in a medical emergency if the customers phone access is blocked by a password that only she knows. Taken as a whole, programmers give usability issues a complexity rating of 4 on a scale of 1 to 8. Monetizing the App Another unknown is the question of how to monetize the app most effectivelyfor example, the app will use ads, but how? Pop-up ads are an annoyance to many people; will they be tolerated by users or will they be immediately rejected? Will the app offer premium services, and if so, what are they? Will a subscription paywall be viable after an initial period of free use? The budget for the project is $350,000, and Third Avenue management would like to see a finished application available in four months. Third Avenue wants a working version of the application as quickly as possible. Management teams key goal is to have the team develop ideas for completing a minimum viable product (MVP) as soon as possible. An MVP is a streamlined, stripped-down version of a product that can still be released for real-world use and review. It contains a subset of features that will be included in the final version. An MVP must possess several key properties: It has sufficient usable features and value that users will buy it. These early users will see the potential benefits of the product and trust that it will only improve in later iterations. It provides a feedback loop that will help programmers improve the existing features and add new features with minimal delays. The MVP version, of course, must be available much more quicklymanagement wants it to be ready to ship in six weeks. The budget for completing the MVP is $120,000. The following team members have been assigned to develop the health-care app: A lead senior programmer A junior programmer who is considered by his peers to be the author of some of the best code at the company. Another talented young programmer A marketing representative who has experience in health care from a previous job The regulatory manager at Third Avenue The Quality Assurance manager The health-care app will undergo rigorous software testing by the Third Avenue Quality Assurance staff. A list of quality requirements must be developed for testing at least five of the important app features and/or usability issues described above. To get you started, here is a list of quality requirements for the emergencies list feature, which stores vital phone numbers and addresses as well as provides quick access to local in-network hospitals, urgent care clinics, and children or friends who can be relied upon to provide transportation in an emergency: Do all of the data-entry fields accept text without problems? For example, long entries in a field can sometimes be clipped or truncated prematurely, which is frustrating to users. Is it possible to enter nonsensical data in a field? For example, users should not be allowed to type text characters into a field that records phone numbers. Does the software automatically move the user from one entry field to the next? Does the cursor always appear in the next entry field as a means of visual feedback for the user? As soon as the user enters and saves an address, an interactive GPS map should become available in a new window, with voice and text directions. Does the window appear? Does it appear immediately? When you slide your finger to create the effect of movement within the map, does the software redraw in a timely manner?