Whatoday_To-Do Part
Version 1.0
Revision History
|
Date |
Issue |
Description |
Author |
|
1/May/2015 |
WinPhone8.1 APP |
The initial idea of the project, first developing phone app |
王善宇 刘畅 刘敬成 |
|
10/May/2015 |
Win8.1 APP |
Transform the phone app to the Windows Store 8.1 platform |
|
|
12/May/2015 |
WPF APP |
Start the last platform, WPF, changing the functions |
|
Table of Contents
1. Objectives 4
2. Scope 4
3. References 4
4. Functionality 4
5. Usability 4
6. Reliability 4
7. Performance 4
8. Supportability 4
9. Security 4
10. Design Constraints 5
Whatoday To-Do Part
1. Objectives
The purpose of this document is to define requirements of the Whatoday To-Do part. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use-case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.
2. Scope
This Supplementary Specification applies to the users of the Whatoday app
This specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability as well as functional requirements that are common across a number of use cases. (The functional requirements are defined in the Use Case Specifications.).
3. References
None.
4. Functionality
- No web services yet
- The event names should be different in case of unwanted delete operations.
5. Usability
Windows Phone 8.1.
6. Reliability
The system shall be available 24 hours a day 7 days a week.
7. Performance
- The application can store more than 10,000 event records.
- The application ensures the safety of the data.
8. Supportability
None.
9. Security
- Since there’s no interaction with the Internet, no web security problems. But still no support to the log in security check.