标签：

Revision History

Expressage Search Problem Statement

Version 1.0

Problem Statement

We are tasked with developing a new Expressage Search system. It is a new client-server system. The new system will allow clients to search for expressages and view logistics from personal computers attached to the campus LAN.

Many people shop online now,at the same time,the main problem people concern about is logistics.the updates on many shopping websites are not synced as soon as possible.so it becomes a problem for clients.they are desperate to know exact time and place of their goods. This database is an Ingres relational database running on a DEC VAX. Fortunately the college has invested in an open SQL interface that allows access to this database from college’s Unix servers. so the system must insure that access to the data on the legacy system occurs in a timely manner.  The system will access expressage api from the legacy database and update it on time. The servers will continue to maintain expressage information through another system.

When people purchase some goods online,the goods will generate logistics records which are stored in the

expressage websites,which could be accessed through api.

The system will allowclients to select good’s expressage info. They type the number of the expressage into the textbox together with the name of the expressage company’s name and click search,below it will be a list of the expressage records of that good,if the number is valid.

Revision History

Table of Contents

1.      Objectives                                                                                                                                                                                 4

2.      Scope                                                                                                                                                                                         4

3.      References                                                                                                                                                                                4

4.      Functionality                                                                                                                                                                            4

5.      Usability                                                                                                                                                                                    4

6.      Reliability                                                                                                                                                                                  4

7.      Performance                                                                                                                                                                             4

8.      Supportability                                                                                                                                                                          4

9.      Security                                                                                                                                                                                     4

10. Design Constraints                                                                                                                                                                     5

Course Registration System Supplementary Specification

1.            Objectives

The purpose of this document is to create Expressage Search System.  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 system.

2.            Scope

This Supplementary Specification applies to the Expressage Search System, which will be developed by all clients.

This specification defines the non-functional requirements of the system; 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

-          Multiple users must be able to perform their work concurrently.

-          If a course offering becomes full while a student is building a schedule including that offering, the student must be notified.

5.            Usability

The desktop user-interface shall be Windows 8.1 compliant.

6.            Reliability

The system shall be available 24 hours a day 7 days a week, with no more than 10% down time.

7.            Performance

1. The system shall support up to 2000 simultaneous users against the central database at any given time, and up to 500 simultaneous users against the local servers at any one time.
2. The system shall provide access to the legacy course catalog database with no more than a 10 second latency.
   Note: Risk-based prototypes have found that the legacy course catalog database cannot meet our performance needs without some creative use of mid-tier processing power
3. The system must be able to complete 80% of all transactions within 2 minutes.

8.            Supportability

None.

9.            Security

1. The system must prevent personal data from leaking.
2. Clients can only access their own data.
3. Clients should not access the data that does not belong to them.

10.         Design Constraints

The system shall provide a Windows-based interface.

Revision History

Table of Contents

1.       Introduction                                                                                                                                                                              4

2.       Definitions                                                                                                                                                                                 4

2.1     Expressage                                                                                                                                                                       4

2.2     Expressage Number                                                                                                                                                        4

2.3     Expressage Company                                                                                                                                                     4

2.4     Result                                                                                                                                                                               4

Expressage Search System 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 Expressage Search System.

2.1          Expressage

Goods records

2.2          Expressage Number

Every Expressage has a unique logistics number attached to it.

2.3          Expressage Company

There are many expressage company on the world.

2.4          Result

Show the expressage records of the goods.

just one last blog

标签：

原文地址：http://www.cnblogs.com/itria/p/4532408.html