亲，先吐槽一下下吧，首先，以下内容仅为老师布置的作业，又臭又长，本人目前也没有看出该博文有何价值，除了它极好地遵循了老师布置的作业奇特的八股文形式，并且在一定程度上让我提高了我微许翻译文章的能力（作业是用英文布置的）和咬文嚼字的能力，并且还极大地磨练了我的耐心，其它的意义实在找不出来了。好了，进入正题：
Revision History
| Date | Issue | Description | Aurthor |
|---|---|---|---|
| 19/May/1999 | 1.2 | Initial creation. Extracted the Problem Statement from the Vision document for purposes of scoping. | Lamba |
Problem Statement
Version 1.2
Problem Statement
不知你平常是否有这样的经历，游玩时看到一幅美妙的风景，想立即拍下来保存并记录此刻想法？直接拍照？可是不能记录呀。用OneNote?功能太复杂了，我仅想记录照片而已，好不好？于是，MoodNotes应运而生。你可以把它当作日记本，记录每日心情；你也可以把它当作笔记本，记录随时所思；你同样可以把它当作备忘录，记录游丝灵感。仅关注唯一功能，简洁小巧。
MoodNotes Glossary
Version 1.2
Table of Contents
- Introduction
- Definitions
2.1 MoodNotes
2.2 MoodNotes Title
2.3 MoodNotes Image
2.4 MoodNotes Content
2.5 MoodNotes Date
MoodNotes Glossary
1.Introduction:
This document is used to define terminology specific to the problem domain, explaining terms, which may be unfamiliar to the reader of the use-case descriptions or other project documents. Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions and other project documents can focus on what the system must do with the information.
2.Definitions
The glossary contains the working definitions for the key concepts in the MoodNotes.
2.1 MoodNote
The note you use to record your mood of everyday.
2.2 MoodNote Title
The title of the moodnote.
2.3 MoodNote Image
The image of the moodnote you have stored.
2.4 MoodNote Content
The content of the moodnote you use to describe the image.
2.5 MoodNote Date
The date you created the moodnote.
MoodNotes Supplementary Specification
Version 1.2
Table of Contents
- Objectives
- Scope
- References
- Functionality
- Usability
- Reliability
- Performance
- Supportability
- Security
- Design Constraints
MoodNotes Supplementary Specification
1. Objectives
The purpose of this document is to define requirements of the MoodNotes. 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 application.
2. Scope
This Supplementary Specification applies to the MoodNotes.
This specification defines the non-functional requirements of the application; 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
Taking Notes of your mood must be much simple.
5. Usability
The desktop user-interface shall be Windows8.1 compliant. And the mobile user-interface shall be WindowsPhone8.1.
6. Reliability
It has no time limit.
7. Performance
The application is light so that it almost has no storage limit.
8. Supportability
None.
9. Security
The application has no need to connect Internet and log in, so it has no security problem.
10. Design Constraints
The application shall provide a Windows-based desktop interface or WindowPhone 8.1.
RequireMents
1. Add Notes
1.1 Brief Description
This use case describes how a user add MoodNotes using MoodNotes.
1.2 Flow of Events
1.2.1 Basic Flow
This use case starts when the user wants to add a note.
He clicks the Add Button, and an edit View will flow on.
The user enters the title and content , and click Image Button to choose a picture.
Click OK Button to confirm the operation.
The application will store the note and make it appear on the listBox.
1.2.2 Alternative Flows
The user clicks the Add Button, and an edit View will flow on.
The user enters the title and content, and click Image Button to choose a picture or not.
He clicks the Cancel Button and the application just return without storage.
1.3 Special Requirements
None.
1.4 Pre-Conditions
None.
1.5 Post-Conditions
If the user clicks the OK Button, the note will be stored. If the user clicks the Cancle Button, the note will not be stored.
1.6 Extension Points
None.
2. View Notes
2.1 Brief Description
This use case describes how a user view MoodNotes using MoodNotes.
2.2 Flow of Events
2.2.1 Basic Flow
This use case starts when the user wants to view a note.
The user clicks note, and the View Window will flow out.
He clicks the Back Button to back.
2.2.2 Alternative Flows
None.
2.3 Special Requirements
None.
2.4 Pre-Conditions
The notesList must have notes there.
2.5 Post-Conditions
None.
2.6 Extension Points
None.
3. Modify Notes
3.1 Brief Description
This use case describes how a user modify MoodNotes using MoodNotes.
3.2 Flow of Events
3.2.1 Basic Flow
This use case starts when the user wants to modify a note.
He clicks the note, and edit View will flow out.
The user modifies the title or content or modifies nothing.
Click OK Button to confirm the operation.
The application will store the note and make the change appear on the listBox.
3.2.2 Alternative Flows
The user clicks the note, and an edit View will flow on.
The user modifies the title or content or modifies nothing.
Click Cancle Button to cancle the operation.
The application will just return and do nothing.
3.3 Special Requirements
None.
3.4 Pre-Conditions
The notesList must have notes there.
3.5 Post-Conditions
None.
3.6 Extension Points
None.
4. Delete Notes
4.1 Brief Description
This use case describes how a user delete MoodNotes using MoodNotes.
4.2 Flow of Events
4.2.1 Basic Flow
This use case starts when the user wants to delete a note.
He clicks the note, and edit View will flow out.
Click Delete Button to confirm the operation.
The application will delete the note and make the change appear on the listBox.
4.2.2 Alternative Flows
He clicks the note, and edit View will flow out.
Click Cancel Button to confirm the operation.
The application will just return and do nothing.
4.4 Pre-Conditions
The notesList must have notes there.
4.5 Post-Conditions
None.
4.6 Extension Points
None.