Software Requirement Specification example

1. Introduction

1.1 Purpose: To compile this document to further customize the details of software development and facilitate coordination between users and developers. this document is intended for the management of project entrusting units. we hope to make the software development work more specific.

1.2 Project Background

1.2.1 project entrusting organization: *** Company

1.2.2 Development Organization: *** Company

1.3 Definition

1.4 references

2. Task Overview

2.1 goals:

<1> Decision Support: provide the required reports and documents in a timely manner as required by the Company, and give sales and incoming purchases to department leaders as appropriate.

<2> improve efficiency: use software for management to avoid manual management errors and delays, so as to achieve efficient management.

2.2 running environment:

<1> hardware: Pentium-level processing chip
1 Mbit/s compatible graphics card
256 colors, 800*600 compatible display
Standard compatible printer

<2> Software: Win95 Operating System

2.3 conditions and restrictions:

One computer for programming
Completion period: 2000/7/1
No capital supply

3. Data Overview

The data flow chart is as follows:

3.1 static data: including the system logon password, database location, and System Analysis of raw data

3.2 dynamic data: including data displayed in each database, user logon information, and system time

3.3 database description:

Personnel Management Database: personal details of company personnel, including archive information
Sales Management Database: sales records of the current day and previous sales statistics for sales analysis
Financial management database: detailed table of company internal accounts and income and expenditure
Technical Management Database: detailed records of technical archives required by the Company (including documents)

3.4 Data Dictionary:

<1> data stream entry description:

1. Data Stream name: login information
Source: user input
Destination: Internal System Inspection
Composition: user name and password
Traffic flux: Input once each login

2. Data Stream name: logon result
Source: System
Destination: User
Composition: return information
Traffic flow rate: once each login

3. Data Stream name: Enter the modification Information
Source: User
Direction: System judgment
Composition: varies by database content
Traffic Flow: Depends on user input.

4. Data Stream name: feedback information
Source: System judgment
Destination: User
Composition: character data returned by the system after judgment
Traffic Flow: depends on the current information of the system.

5. Data Stream name: Recognition Information
Source: Internal System Inspection
Direction: System judgment
Composition: identification information of each database in the system
Traffic Flow: the user enters the flow once each time.

6. Data Stream name: Processing Information
Source: System judgment
Destination: processing of various databases
Composition: Read/modify the identifier, read/modify the variable name
Traffic Flow: the user enters the flow once each time.

7. Data Stream name: Read and modify
Source: System judgment
Destination: System databases
Composition: Read/modify ID, read/modify content
Traffic Flow: the user enters the flow once each time.

<2> data file entry description:

1. Data File Name: Personnel Data
Brief description: storage personnel information
Data File composition: Personnel Information (mainly cstring type)

2. Data File Name: sales data
Summary: Stores Sales records of the current day and past
Data File composition: Sales Information

3. Data File Name: Financial Data
Brief description: stores Financial Management Information
Data File composition: financial management records

4. Data File Name: Technical Data
Brief description: stores the technical archives used internally by the company.
Data File composition: technical file name, content

<3> description of the processing logic entry:

1. processing NAME: Inspection
Brief description: determine the user's permission
Input data stream: logon information
Output Data Stream: logon result
Processing logic: Determine whether it is consistent with the internal user information of the system

2. processing NAME: Judgment
Brief description: determines the user's operations and reads/stores the data.
Input data stream: Enter the modification Information
Output Data Stream: feedback information
Processing logic: determine user operations-> call database-> Read/modify-> feedback

3. processing NAME: personnel file management
Brief description: operations required for the personnel database and interaction with the judgment part
Input data stream: process information, read and modify
Output Data Stream: read, modify, and process information
Processing logic: determine the content that the user wants to read/modify-> feedback the user's required information

4. processing NAME: sales statistics
Brief description: perform the operations required for the sales database and interact with the judgment part.
Input data stream: process information, read and modify
Output Data Stream: read, modify, and process information
Processing logic: determine the content that the user wants to read/modify-> feedback the user's required information

5. processing NAME: Financial Statistics
Brief description: Perform required operations on the financial database and interact with the judgment part.
Input data stream: process information, read and modify
Output Data Stream: read, modify, and process information
Processing logic: determine the content that the user wants to read/modify-> feedback the user's required information

6. processing NAME: Technical Management
Brief description: operations required for the technical statistics database and interaction with the judgment part
Input data stream: process information, read and modify
Output Data Stream: read, modify, and process information
Processing logic: determine the content that the user wants to read/modify-> feedback the user's required information

<4> description of Source and Sink entries:

Name: User
Brief description: it is both a source point and a collection point. It sends action information to "test" and "judgment" for processing, and receives feedback on the data stream through the interactive interface: Login result, login information, and Input Modification information, feedback
Number: One

4. Functional Requirements

4.1 function division

It can be divided into four parts: personnel management, sales management, financial management, and technical file management.

4.2 Function Description

<1> personnel functions:

(1) Records and stores relevant archives of all employees within the company.
(2) Check and modify the data of personnel files in the database.
(3) personnel can be retrieved by department or name.
(4) When an employee's employment period reaches the full year, remind him on time.

<2> sales statistics

(1) Calculate the company's sales by day, including sales volume, sales volume, sales ratio of each region, sales volume of different sales methods, and sales gross profit.
(2) Prepare monthly/quarterly report and Annual Report for sales analysis, and evaluate the performance of different sales personnel.

<3> Financial Management

(1) assist financial personnel in Computer Management, and log on and output inventory/purchase/sales
(2) Remind buyers based on preset inventory Conditions
(3) make statistics on the collection status, and prompt when the accounts receivable reach the preset value

<4> technical management functions

(1) log on to technical materials
(2) log on to and collect statistics on service records, conduct overall Fault Analysis on machines of different models, and make analysis reports
(3) Manage the demands for parts for repair and prompt for stock-up

5. Performance Requirements

5.1 data accuracy: because the data is internal data of the company, there must be no error

5.2 Time Feature: The sales statistics of the current day must be real-time, and inventory problems can be immediately reflected. Meanwhile, the financial management data is used to calculate the current inventory situation, and the purchase situation is estimated.

5.3 Adaptability: this software is only used on the machine of the company's internal management personnel, so adaptability is not considered.

6. operation requirements

6.1 user interface:

Screen format:

(1) menus and toolbar are required for convenient operation.
(2) The database information can be directly modified on the screen.
(3) statistical results can be displayed on the screen.
(4) The system analysis result is displayed in another window.

Report Format:

(1) personnel management reports only require ordinary personal data
(2) Requirements for sales statistical reports can print statistics of the current day or previous statistics respectively
(3) The requirements for the financial statistical report should be printed out in the inventory and company account details table
(4) Technical Management Report requirements: You can print the Technical Archive summary table and the content menu format of any technical archive document respectively. The menu items must be roughly the same as those of Win95, in addition, the additional function enables the input and output time of a new single item: The year is represented by four digits.

6.2 hardware interface: standard printer interface is required for report printing

6.3 Software Interface: Windows Standard Interface

7. Other requirements

Usability: easy to use and user-friendly

Security and confidentiality

Maintainability: maintenance documents of the software are required to facilitate maintenance.