Software Requirements Specification Sheet

1. Introduction

1.1 Purpose

This document first gives a general overview of the overall network structure and functional structure of the whole system, attempts to give the whole software outline from the overall architecture, and then describes the functional requirements, performance requirements and other non-functional requirements in detail. The description of functional requirements uses the UML use case model, mainly describes the basic event flow of each use case, if there is an alternative event flow is described, otherwise omitted. A very intuitive use case diagram is also given. These text and graphics are designed to provide a detailed and accurate description of the user's needs, as well as to create conditions that make it easier for users to understand the requirements.

This document provides a detailed description of the requirements and specifications for this software product, which is the basis for the design and the main basis for writing test cases and conducting system tests. At the same time, this document is also the main basis for users to determine the functional requirements of software.

1.2 Document Conventions

This document is written according to the following requirements and conventions:

( 1 ) headings up to three levels, respectively, in bold small three, blackbody fourth, black body Four, the title is bold

( 2 text font for the body of the small four, no special case, the font color are used black.

( 3 the paragraph that appears ordinal does not use the automatic numbering function and the manual number, the sequence number according to each level ( 1 ), 1 ), a ) and other special circumstances.

1.3 expected readers and reading suggestions

The main content of this document is divided into 4 Parts: Comprehensive description, system characteristics, and non-functional requirements and external interface description. The overall structure of the system is mainly introduced in the general description, and the functional requirements of the system are described in detail, which is the main part of this paper, and the non-functional requirements are described in detail. The external interface Requirements section of the user interface, software interface, The hardware interface and communication interface are described.

This document is intended for a variety of reader objects:

( 1 Project Manager: The project manager can follow the documentation to understand the functionality of the expected project and project design and project management accordingly.

( 2 ) Designer: Analyze the requirements and design the project, including the design of the database.

( 3 Programmer: Cooperate with the design report, understand the project function, and write the user manual.

( 4 Testers: Write test cases based on this document, and perform functional and non-functional testing of software products.

( 5 Sales Staff: Understand the functionality and performance of the expected software.

( 6 users: Understand the functionality and performance of the expected software, and work with analysts to discuss and negotiate the overall requirements.

( 7 other people: teachers can understand the software's functionality and performance accordingly.

when reading this document, you should first understand the functional profile of the software, and then you can have a proper understanding of each function according to your own needs.

range of 1.4 products

The software needs to fully consider the actual situation of the specific users. The software is mainly used in the students of various universities, the main function is to achieve curriculum, curriculum reminders, Notepad and other functions.

1.5 Reference Documents

No

2. General Description

the future of 2.1 software

Now the market schedule software has been basically saturated, the competition is very big.

2.2 features of the software

The software combines the curriculum with Notepad, adding reminders to facilitate the students ' daily learning arrangements.

2.3 user classes and features

Users are mostly students who are always unable to remember lessons or forget things.

2.4 Operating Environment

Client: Android4.0 and above

2.5 design and implementation Limitations

Partial functionality not implemented due to technical limitations

2.6 Assumptions and Dependencies

users can only follow some of our requirements to do, such as date format.

3. external interface Requirements

3.1 Hardware interface

No special requirements

3.2 Software Interface

No special requirements

3.3 Communication Interface

No special requirements

4. System Features

4.1 Landing Interface

4.2 Main Interface

4.3 Classification Interface

4.4 Publishing Interface

4.5 Personal Interface

4.5 Other Interfaces

5. Other non-functional requirements

5.1 Security Requirements

(1) users can access the database for injury modification

( 2 users can only view their own information, and collect and purchase information only when they log in successfully.

5.2 availability requirements

(1) convenient operation.

(2) fault tolerance, user operation error will be prompted.

(3) has a complete user operation guide.

5.3 user documentation

(1) User manual:Word Format document

(2) Online assistance:HTML help format file

6. Other requirements

(1) support various models of mobile phones

( 2 Easy to operate, from the user point of view, user-friendly all needs

Software Requirements Specification Sheet