Professional Documents
Culture Documents
0>
Supplementary Specification Date: <09/12/2003>
Vision PortPASS
Supplementary Specification
Version <1.0>
Vision PortPASS Version: <1.0>
Supplementary Specification Date: <09/12/2003>
Revision History
Date Version Description Author
<09/12/2003> <1.0> Status Assessment Anders Bengtson
Jingtao Wang
Naem Ahkter
Sazzad A. T Mohammed
Vision PortPASS Version: <1.0>
Supplementary Specification Date: <09/12/2003>
Table of Contents
1. Objectives
2. Scope
3. References
4. Functionality
4.1 System Error Logging
5. Usability
5.1 Windows Compliance
Supplementary Specification
1.Objectives
The Supplementary Specification document aims to define requirements of the Vision PortPASS
system. This Supplementary Specification includes 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 concerns with the Vision PortPASS system that will be
developed by our company. The purpose of the system is to function as a security-enhancing
device for users of the system. It will have a client-server architecture where communication is
carried out over a 3G network. Surveillance devices will be connected to a central server than can
be accessed by registered users of the system. Access to the server is done either from a cell
device in a 3G-cell phone network or through an Internet browser using the existing Internet
infrastructure.
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
Applicable references are:
Applicable references are:
1. Vision for the Vision PortPASS system, V2.0
2. RUP2002, Rational Software Corp.
3. Use case description
4. Use Case Model Survey Date:04/12/2003
5. Iteration Plan Date:31/10/2003
6. Risk List Date:12/12/2003
7. Software Development Plan Date:16/10/2003
4. Functionality
This section provides functional requirements that are general to most use cases.
The system should log all system errors. Fatal system errors shall result in an orderly
shutdown of the system.
The system error messages shall include a text description of the error, the operating
system error code (if applicable), the module detecting the error condition, a data stamp,
and a time stamp. All system errors shall be retained in the Error Log Database.
5. Usability
Vision PortPASS Version: <1.0>
Supplementary Specification Date: <09/12/2003>
This section lists all of those requirements that relate to, or affect, the usability of the system.
5.1 Windows Compliance
The desktop user-interface shall be Windows compliant.
5.2 Design for Ease-of-Use
The user interface of the Vision PortPASS System shall be designed for ease-of-use and all the
users can use it easily without knowing too much knowledge of the computer and additional
training on the System.
5.3 Online Help
The system should provide online help including step by step instructions on using the
system.
6. Reliability
6.1 Availability
Because the implementation has just begun the availability requirements will be defined in the
next iteration.
6.2 Mean Time Between Failures
Because the implementation has just begun the MTBF will be defined in the next iteration.
7. Performance
This section will give an overall description of the performance characteristics of the system.
The system must be able to complete 80% of all transactions within 2 minutes.
8. Supportability
This section defines any requirements that will enhance the supportability or maintainability of the
system being built.
The users can download the updated versions to the client portion of the system over the
Internet.
9. Design Constraints
Vision PortPASS Version: <1.0>
Supplementary Specification Date: <09/12/2003>
This section lists any design constraints on the system being built.
The client application shall be compatible with the J2ME runtime environment and server
application should be compatible with Java/J2EE runtime.