Professional Documents
Culture Documents
[SCIGT]
Page i of 12
TRADEMARKS
Product names referenced in this document may be trademarks or registered trademarks of their
respective companies and are hereby acknowledged.
Document
Version
1.0
Approval
Date
22/10/2013
Modified By
TABLE OF CONTENTS
1.
2.
3.
4.
5.
6.
INTRODUCTION............................................................................................................ 1
1.1 Organization of this Document...................................................................................1
FUNCTIONAL REQUIREMENTS.......................................................................................2
2.1 Funcionalidad general................................................................................................. 2
FR001 Descripcin..................................................................................................... 2
FR002 Agregar producto a la compra........................................................................2
2.2 Funcionalidad general................................................................................................. 2
FR0003 Descripcin................................................................................................... 2
USER INTERFACE REQUIREMENTS................................................................................3
3.1 General User Interface Requirements.........................................................................3
3.1.1 Accessibility...................................................................................................... 3
3.1.2 Usability............................................................................................................ 3
3.2 Screens....................................................................................................................... 3
3.3 Reports....................................................................................................................... 3
3.4 Forms.......................................................................................................................... 3
SYSTEM INTERFACE REQUIREMENTS............................................................................4
4.1 External Interfaces...................................................................................................... 4
4.2 Internal System Interfaces.......................................................................................... 4
BUSINESS RULE CATALOG............................................................................................ 5
5.1 5
NON-FUNCTIONAL REQUIREMENTS..............................................................................6
6.1 Environment-Development......................................................................................... 6
Development Environment........................................................................................... 6
Model Office / Pre-Production Environment..................................................................6
Reusability................................................................................................................... 6
6.2 Environment-Deployment........................................................................................... 7
Deployment................................................................................................................. 7
6.3 Environment-Installation............................................................................................. 7
Installability.................................................................................................................. 7
Portability..................................................................................................................... 7
Scalability.................................................................................................................... 7
Training........................................................................................................................ 7
6.4 Environment-System.................................................................................................. 7
Interoperability............................................................................................................. 7
Software....................................................................................................................... 7
6.5 Operations.................................................................................................................. 8
Availability................................................................................................................... 8
Backup and Restore..................................................................................................... 8
Operation Environment................................................................................................ 8
6.6 Performance............................................................................................................... 8
Capacity....................................................................................................................... 8
Redundancy................................................................................................................. 8
1. INTRODUCTION
This document contains the text-based detailed requirements for the delivery of the project. Refer to
the Detailed Requirements Package for the business analysis models and other information that
complete the requirements specification.
Section 3
Section 4
Section 5
Business Rules Catalogue contains the business rule that define, constrain, or
enable a business policy, business process or a detailed requirement
Section 6
2. FUNCTIONAL REQUIREMENTS
This section describes the detailed functional requirements of the system.
2.1
Funcionalidad general
3.1.1 Accessibility
-
3.1.2 Usability
-
3.2
Screens
-
3.3
Distribucin de pantallas.
Reports
Report Type
3.4
Report Name
Description
User Type
Forms
Form Name
Description
User(s)
Frequency
4.1
External Interfaces
External Entity
4.2
Description
Description
6. NON-FUNCTIONAL REQUIREMENTS
Non-functional requirements describe conditions that do not directly relate to the behaviour or
functionality of the solution, but rather describe environmental conditions under which the solution
must remain effective or qualities that the systems must have. They most often describe some of the
attributes of the system or system environment and are constraints on the solution.
6.1
Environment-Development
This category covers requirements specifically needed to support the development environment.
Development Environment
These requirements address special arrangements made in the development environment in
support of the project.
1.
Reusability
These requirements address the ease with which the product or a product component is
reused, or converted for use, in the same project or another project.
6.2
Environment-Deployment
This section describes the detailed capabilities that the solution must have in order to facilitate
the transition from the current state of the enterprise to the desired future state (e.g., conversion
and one-time deployment requirements), but that will not be needed once that transition is
complete.
Deployment
These are 'one-time-only' requirements that are necessary to transition and implement the
system. These requirements also address any site-specific related features that should be
modified to adapt the software to a particular installation. Once the system is implemented
these requirements become obsolete and are no longer needed.
6.3
Environment-Installation
Installability
These requirements address the ease with which the product is installed in the users
environment.
Portability
These requirements address the ease with which the product is implemented on or migrated to
other platforms or operating systems.
-
Scalability
These requirements address the ability of the product to adapt to new technologies and to
changes in post implementation metrics
Training
These requirements address training to be provided to the project team in support of project
activities.
6.4
Environment-System
This category defines requirements regarding the needs of the system environment including
hardware, software and infrastructure needs, as well as interoperability with other products or
applications.
Interoperability
These requirements address the need for the product to interface with other applications or
systems without interfering with the operation of those other applications or systems.
Software
These requirements address specific software considerations for a project.
6.5
Operations
Availability
These requirements define when the product is available.
Operation Environment
These requirements address special considerations for the operation and ongoing support of
the delivered product.
6.6
Performance
This is a broad category which covers all requirements related to system performance. It
includes response times, capacity, availability, business continuity/disaster recovery, reliability
and robustness.
Capacity
These requirements address the system load at any given time.
Redundancy
These requirements address the ability to replace a failed component with another component,
that is, the degree of availability, or fault-tolerance, of the system or infrastructure.