Requirements Specification (search Room app)

Project name: Find study room App Requirements Documentation

Item Number: 001

Requirements Specification Sheet

State	O Draft	Identification number	RD
	O Initial version	Current version	V1.0
	O Revised version	Release date
		Template number
Classified	o no-secret U secrets o Confidential

Objective

The software requirement confirmation book mainly describes and defines the scope of the software, and gives a detailed description of the problems that the software must solve. Each issue can be thought of as a "feature" of a software product that requires a description of each function that deals with narrative, design constraints, performance characteristics, and interactions with other elements.

Software requirements Confirmation Another important role is to provide a software product validation acceptance criteria for functional realization of the identification and performance, constraints, such as the setting of conditions.

Document Revision History

Version number or change record number	Change state	Brief description (Change content and scope of change)	Revision Date	Change person	Approving person	Approval date
001	C	First development of requirements documentation	2015-4-13	Li Lin

* Change Status: c--creation; a--increase; m--Modify; d--Delete

1. Overview 1.1 Purpose

The purpose of this document is to define user requirements, to achieve a common understanding of software product requirements between end users and developers, to provide guidance for the development of the software as a goal of the project, and as a basis for software testing.

Readers of this document are end-user representatives, senior project managers, project managers, project team members, test team members, and quality assurance group members.

1.2 Range

This document is a software requirements specification for the project and is a technical document.

This document uses the following objects:

L Project Demand Personnel

L Project Manager

L Software Engineering Group

L User

L ...

The document may not be read or used by persons other than those specified above, without the written permission of the project manager.

1.3 Definitions, acronyms and abbreviations

Abbreviations, terminology	Explain
Eclipse	Integrated development Environment
DDMS	Dalvik Debug Monitor Service (to provide debug information)
ContentProvider	Used to share with other program data
Adb	A universal testing tool for Android
...

1.4 References

1. Yiang Shangrong, Introduction and practice of Android development, people's post and telecommunications publishing house, 2009.7

1. Yang Rich, Android application development Secrets, Mechanical industry Press, 2010.1
2. Yu Zhirong, Google Android SDK Development Example Daquan (2nd edition), People's post and telecommunications press, 2010.6
3. Guo Hongzhi, Android application development, electronics industry Press, 2010.6
4. Zhang Liguo, Shanghaiping, Android Mobile development Case study, people's post and telecommunications press, 2010.2

6. System Description 6.1 product background

The university is a class system, which will result in some classrooms empty and some students can not find the available self-study classroom in time. In order to improve the utilization of self-study classrooms, to reduce the time spent on students to find self-study classrooms, we develop this search classroom app, convenient for students to learn.

6.2 Features of the product

1. Users can upload empty self-study classroom data;

2. The app automatically locates the nearest teaching building to the user;

3. Error data remediation measures;

4. Push service.

6.3 User Classes and features

College students who prefer reading and self-study

6.4 Operating Environment

1. Server-side: Linux
2. Client: Android4.0 and above
3. Development language: Java
4. Database selection: MySQL

6.5 Limitations on design and implementation 6.6 assumptions and dependencies

[ list the assumptions that affect the requirements statement in the software requirements confirmation (as opposed to the known factors), which may include the business components intended for use or questions about the development or operational environment. You may think that the product will conform to a particular user interface design convention, but another reader may not think so. If these assumptions are incorrect, inconsistent, or changed, the project will be affected.

Determine the dependencies that the project has on external factors. For example, if you are planning to integrate components developed by other projects into the system, then you have to rely on which project will provide the correct operational components on time, and if those dependencies are already documented in other documents (such as project plans), then you can refer to other documents here. ]

6.7 Other conditions and restrictions

[ as far as possible to list the implementation of the project assumptions and constraints, such as: funding constraints, development period, equipment conditions, user site environment preparation, security and confidentiality, etc.]

7. Business Process

8. Function description

1. Users can upload empty self-study classroom data;
2. App automatically locates the nearest teaching building to users
3. Error Data remediation measures
4. Push Service

5. Data Description 5.1 Source and Data flow diagram 5.1.1 input data

Login name and password

User basic information

Newly added empty study room

Correction of self-study classroom

5.1.2 Output data

Self-study Classroom information

5.1.3 Data Flow Chart

5.2 Database Description 5.2.1 Classroom table

Column Name	Data type	Allow null values

5.2.2 User Table

Column Name	Data type	Allow null values

5.2.3 Timetable

Column Name	Data type	Allow null values

5.2.4 Entry Form

Column Name	Data type	Allow null values

6. Data Description 6.1 Data accuracy

[ data Internal display accuracy, external display accuracy]

6.2 Time Characteristics

[ system response time, Interface update processing time, data conversion and transmission time, etc.]

6.3 Adaptability

[ Adaptability when changes occur in operation mode, operating environment, interfaces with other software, and development plans]

7. Security 7.1 Safety Facility requirements

[ Detailed statement of requirements relating to loss, damage or damage that may occur during the use of the product.] Define the security or action that must be taken, and the potentially dangerous actions that are prevented. Define the safety standards, policies, or rules that a product must comply with. An example of a safety facility requirement is as follows: "If the pressure of the tank exceeds 95% of the specified maximum pressure, the operation must be terminated within 1 seconds." ] 

7.2 Security Requirements

[ Details of the requirements relating to system security, integrity, or personal issues will affect the use of the product and the protection of the data created or used by the product.] Define user identification or authorization requirements. Define the security or privacy policies that the product must meet. An example of the security requirements for a software system is as follows: "Each user must change the initial login password after the first logon. The initial login password cannot be reused. "]

8. Operating interface Requirements 8.1 user interface

[ a software component that states the required user interface.] Describes the logical characteristics of each user interface. Here are some of the features you might want to include:

L The style of the graphical user interface (GUI) standard or product line that will be adopted.

• limitations on screen layouts or solutions.

The standard buttons, features, or navigation links (such as a Help button) will appear on each screen.

l shortcut keys.

L report output definition.

L error message display standard.

For details of the user interface, such as the layout of a particular dialog, it should be written in a separate user interface specification without

Write the software Requirements specification. ]

8.2 Hardware Interface

[ describes the characteristics of each interface of software and hardware in the system, which may include supported hardware types, the nature of data and control information exchanged between soft and hard, and the communication protocol used]

such as network diagrams, etc.

8.3 Software interface

[ includes databases, operating systems, tools, libraries, and integrated business components that define and describe the purpose of exchanging data or messages between software components]

8.4 Communication Interface

[ description relates to the communication function used by the product, including electronic, web browser, network communication standards or protocols, and spreadsheets.] Defines the associated message format. Specifies communication security or encryption issues, data rates, and synchronous communication mechanisms. ]

9. Other requirements

[ define requirements not appearing in other parts of the software requirements specification, such as international requirements or legal requirements.] You can also increase the operational, administrative, and maintenance sections to improve product installation, configuration, startup and shutdown, repair and fault tolerance, and login and monitor operations. If you do not need to add additional requirements, you can omit this part. ]

10. Acceptance criteria

[ specific content of the various standards or conditions that specify the basis for product acceptance]

10.1 Software Quality

[ detailed statement of product quality characteristics that are critical to the customer or developer.] These attributes must be deterministic, quantitative, and, if possible, verifiable. ]

10.2 User Documentation

[ list the user documentation sections that will be distributed with the software, such as the operating manuals, installation manuals, maintenance manuals, online help, and tutorials.] Identify the delivery formats and standards for all known user documents. ]

Note: The content in the document [] is a description of the corresponding section and should be removed or changed to the appropriate content when writing the requirements specification for the specific project.

Requirements Specification (search Room app)