Revision History

Problem Statement

Version 1.2

Problem Statement

we always forget doing many things, if you don‘t want to forget them,you can write them on a place. Now we will provide a place

for you. you can write them on my MiNiNotes(迷你便签)(以WPF版为例，windows phone 实现了一个小型计算器，这里就简单略过，主要讲解一下wpf版的迷你便签)，its interface is very easy, user can understand it easily.

MoodNotes Glossary

Version 1.2

Table of Contents

1. Introduction
2. Definitions 
   2.1 MiNiNotes
   2.2 MiNiNotes Content 
   2.3 MiNiNotes cut  
   2.4 MiNiNotes copy
   2.5 MiNiNotes paste         2.6 MiNiNotes  save        2.7  MiNiNotes save as     2.8 MiNiNote  delete             

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 MiNiNotes.

2.1 MiNiNote

The note you use to record your mood of everyday.

2.2 MiNiNote Content

The content of you want .

2.3 MiNiNote cut

Cut contents

2.4 MiNidNote copy

Copy contents

2.5 MiNiNote paste

Paste content

2.6 MiNiNote save

Save content to MyDocument(我的文档）

2.7 MiNiNote save as

Save content to anywhere in you computer.

MiNiNotes Supplementary Specification

Version 1.2

Table of Contents

1. Objectives
2. Scope
3. References
4. Functionality
5. Usability
6. Reliability
7. Performance
8. Supportability
9. Security
10. Design Constraints
    

    MiNiNotes Supplementary Specification

    1. Objectives

    The purpose of this document is to define requirements of the MiNiNotes. 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 MiNiNotes. 
    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

    Write what you want on it, you can save it.

    5. Usability

    Windows Phone 8.1 (And Windows Store App and WPF )

    6. Reliability

    It is reliable

    7. Performance

    It  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  provide a Windows platform.

 RequireMents

1. Add Notes

1.1 Brief Description

You can add a note.

1.2 Flow of Events

1.2.1 Basic Flow

if you click the "add"(新建) of button ,it can delete the content,and create a new note

1.2.2 Alternative Flows

The user clicks the Add Button, and an edit View will flow on.

User can write their contents.

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. save Notes

2.1 Brief Description

You can save your contents

2.2 Flow of Events

2.2.1 Basic Flow

if you click the "save" of button ,it can save the content to ‘我的文档‘

2.2.2 Alternative Flows

none

2.3 Special Requirements

None.

2.4 Pre-Conditions

None.

2.5 Post-Conditions

If the user clicks the save  Button, the note will be stored.

2.6 Extension Points

None.

3. Save as Notes

3.1 Brief Description

You can save your content to anywhere.

3.2 Flow of Events

3.3.1 Basic Flow

if you click the "save as" of button ,it can save your content to anywhere on your computer.

3.3.2 Alternative Flows

The user clicks the "save as" Button, and an "save as" View will flow on.

3.3 Special Requirements

None.

3.4 Pre-Conditions

None.

3.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.

3.6 Extension Points

None.

4. Delete Notes

4.1 Brief Description

You can delete your content.

4.2 Flow of Events

4.4.1 Basic Flow

if you click the "delete" of button ,it can delete your content.

4.3.2 Alternative Flows

None

4.3 Special Requirements

None.

4.4 Pre-Conditions

None.

4.5 Post-Conditions

None

4.6 Extension Points

None.