for essays guru

There are numerous health issues that have been linked to sleep quality and quantity. For instance, poor and prolonged sleeping behaviors have adverse impacts on human health, such as hypertension, increased level of depression, anxieties, diabetes and depression. The quality of sleep can be assessed especially through physiological scaling such as body movements while sleeping. In light of the above concerns, humans need to understand their sleep patterns in order to avoid sleep-related health problems. One of the ways of understanding personal sleep patterns is to use monitoring and tracking devices (Mohr, 2015). This calls for the need to develop an app that will perform the task of tracking personal sleep patterns through motion detection.

The primary goal of this project is to design an app that helps users to identify their possible sleep problems by monitoring their sleeping patterns. This system will work through tracking of sleeping patterns through motion detection. The goal is to implement it as an application for smartphones that are supportive of Android. Another goal is to investigate the degree to which sleep actigraphy using smartphone accelerometers is possible and come up with algorithms for extracting important information regarding the sleeping quality from the gathered information. The app can also be used easily by third party applications by detecting sleep-related activities such as body movements.

The scope of the project will be confined to sleep monitoring and tracking functions. This will require the development of an app that will have various features. First, the app will work on smartphones that support Android operating systems. The scope of the project will be to determine the extent to which sleep actigraphy using smartphone accelerometers is possible. Furthermore, a set of algorithms will be designed to gather important data regarding the sleep quality of an individual. The app will solely run in smartphone devices. Moreover, the scope of the tracking functions will be limited to body movements. Body motion may take the form of eye opening and movements, and the general movements of each body part.

While the app will work by monitoring sleep patterns, there are various areas that will not be included in the project. First, the application will only work for users who have smartphones. This means that other devices such as personal computers (desktops, laptops and palmtops) will not be compatible with the above application. In addition, the proposed application will only work using the Android operating system. Therefore, other operating systems such as Windows, Linux and Macintosh are completely excluded from this project. Furthermore, the application that is to be developed will solely work by tracking sleep patterns through motion detection. Thus, other mechanisms of detecting sleep patterns will not be included in the scope. In particular, mechanisms that will not be utilized include snoring and breathing movements that are generated while sleeping.

The user interface of the application will be designed with the use of Android. In as much as it would be possible to begin the process of recording body movements in the main application, there is a more effective way which ensures that the detection goes uninterrupted. The Android Service Class is exactly designed for this purpose. A Service is a software component that can undertake long running activities in the background and does not offer a user interface. The Service is started and regulated by an activity and may offer a notification to users with respect to the present state of the service.

The owners of the resources will be determined by the project’s resource plan. In this respect, all the key stakeholders involved in the development of the project by way of funding or showing interests are the potential resource owners. For example, there are healthcare institutions that could require the development of this app for monitoring patients’ sleeping patterns and making recommendations on the right steps to be taken to improve a patient’s sleeping patterns. These groups would be directly involved in the funding of the project development operations. In addition, representatives of key smartphone manufacturing companies are also going to be the owners, especially if they are involved in the direct funding of the system’s development.

The receivers for the project will be determined by the delivery plan. For example, the receivers for delivery of team process and document template will include the project manager, supporters, as well as project recorders. In addition, the receivers for the master plan documents an SRS documents will include the technical lead, the project manager, as well as the recorder. The software development plans and coding systems will be received by the developer and technical lead. Furthermore, the receiver of all the information that concerns payment and budgeting of the entire project will be received by the project manager.

The suppliers of the project will include individuals who are involved in the supply of the necessary resources for the development of the sleep-tracking and monitoring software. For instance, they will include suppliers of software and hardware infrastructures. Other suppliers will be in form of pen and paper resources and services.

The project will be organized in teams that are headed by the project manager. The process will start by identifying needs from users and documenting them. Thereafter, the actual process of software development will resume. Finally, the system will be implemented and undergo maintenance on a regular basis.

2.

3.

3.1

3.2

3.2.1 Project Team

The project is being developed independently of any outside financial backers at the time of the finalization of this document. Should the project receive further funding from any outside source, contract negotiations will be held with the parties providing funds.

The following workflow chart shows the process that development team will adopt:

The process shown above will be utilized for every major function of the application. It borrows heavily from the Waterfall software model. Given that the project is being developed outside the influence of any specific client, this model allows us to set requirements and keep them fairly static throughout the development process. A large portion of changes to the specification and/or the process are expected to come internally, therefore a highly incremental process like Agile is not necessary to keep up with any changes.

Given the relatively small scale of the project, the team will implement a simplified version of a risk management model used for Agile software development, as proposed by Ville Ylimannela from the Tampere University of Technology (see references section for document link). The process will use minimal documentation that will be modified as risks are identified and analyzed. It is the Project Manager's duty to oversee the implementation of the risk management system described in the table below:

Quality assurance will be spearheaded by the QA Lead: The QA lead will provide test cases for each function and delegate them to the corresponding team member/s that worked on that function. It is the responsibility of the team members to report to the QA lead with any inconsistent or unexpected behavior of a function, whereupon the QA lead will try to recreate the behavior and plan for any steps necessary to remedy them.

Configuration and change management will be handled by the C&C Manager: As development on the project advances, unforeseen circumstances may arise. It is the responsibility of the C&C Manager to have a plan in place to anticipate and accommodate any changes to the project specification and project process. The weekly meetings, as well as any client meetings, will serve as a platform for the C&C Manager to identify any potential changes to either the specifications or the process.

For the commercial version of the application, client data will be accessed and stored using the Google Play Services authorization features. A user will not need to create an account, as they will use their pre-existing credentials from their Google accounts. The data will be stored on the device as it is being analyzed by the system. The data will also sent back to Google servers which will allow for data backups and prevent data loss should a user damage their phone, uninstall the application or any other case where data could be corrupted. The data will only be accessible to the user and the project team (for testing and analytical purposes only). In any case where user data has been breached, the development team will take the necessary steps as dictated by Google’s guidelines for utilization of their services.