13
Detailed Requirements [SCIGT] Saved 23 October 2013 Page i of 13

03 Detailed_Requirements

Embed Size (px)

Citation preview

Page 1: 03 Detailed_Requirements

Detailed Requirements[SCIGT]

Saved 23 October 2013 Page i of 12

Page 2: 03 Detailed_Requirements

TRADEMARKSProduct names referenced in this document may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.

DOCUMENT REVISION HISTORYProject Name:

Document Status (e.g. Draft, Final, Release #):

Change Request# (Optional)

Document Version

Approval Date Modified By Section, Page(s) and Text Revised

1.0 22/10/2013

Page 3: 03 Detailed_Requirements

TABLE OF CONTENTS1. INTRODUCTION..............................................................................................................................................1

1.1 Organization of this Document....................................................................................................................12. FUNCTIONAL REQUIREMENTS.......................................................................................................................2

2.1 Funcionalidad general..................................................................................................................................2FR001 – Descripción.......................................................................................................................................2FR002 – Agregar producto a la compra..........................................................................................................2

2.2 Funcionalidad general..................................................................................................................................2FR0003 – Descripción.....................................................................................................................................2

3. USER INTERFACE REQUIREMENTS..................................................................................................................33.1 General User Interface Requirements..........................................................................................................3

3.1.1 Accessibility.....................................................................................................................................33.1.2 Usability...........................................................................................................................................3

3.2 Screens.........................................................................................................................................................33.3 Reports.........................................................................................................................................................33.4 Forms...........................................................................................................................................................3

4. SYSTEM INTERFACE REQUIREMENTS.............................................................................................................44.1 External Interfaces.......................................................................................................................................44.2 Internal System Interfaces...........................................................................................................................4

5. BUSINESS RULE CATALOG..............................................................................................................................55.1 5

6. NON-FUNCTIONAL REQUIREMENTS...............................................................................................................66.1 Environment-Development..........................................................................................................................6

Development Environment............................................................................................................................6Model Office / Pre-Production Environment.................................................................................................6Reusability......................................................................................................................................................6

6.2 Environment-Deployment............................................................................................................................7Deployment...................................................................................................................................................7

6.3 Environment-Installation..............................................................................................................................7Installability....................................................................................................................................................7Portability......................................................................................................................................................7Scalability.......................................................................................................................................................7Training..........................................................................................................................................................7

6.4 Environment-System....................................................................................................................................7Interoperability..............................................................................................................................................7Software.........................................................................................................................................................7

6.5 Operations...................................................................................................................................................8Availability......................................................................................................................................................8Backup and Restore.......................................................................................................................................8Operation Environment.................................................................................................................................8

6.6 Performance.................................................................................................................................................8Capacity.........................................................................................................................................................8Redundancy...................................................................................................................................................8

Page 4: 03 Detailed_Requirements
Page 5: 03 Detailed_Requirements

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.1.1Organization of this DocumentThis document is organized into the following sections:

Section 1 Introduction – provides an overview of this document.Section 2 Functional Requirements - contains the functional requirements for the solution, which

are in addition to and support the requirements presented in the Use Cases.Section 3 User Interface Requirements – contains the broad-spectrum requirements related to

the interaction between the application and the users. Reports are also listed.Section 4 System Interface Requirements - contains the requirements related to the interaction

between the system and external systems, and between internal applications within the system.

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 Non-Functional Requirements– contains the requirements 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.

Page 6: 03 Detailed_Requirements

2. FUNCTIONAL REQUIREMENTS

This section describes the detailed functional requirements of the system.2.1 Funcionalidad general

Proyecto 01 – Área de Almacén.AA0001 – Reporte de Técnicos.

Muestra la lista de técnicos activos para la entrega de equipos.AA0002 – Reporte de Ordenes.

Muestra la lista de Órdenes que se realizaran en el día.AA0003 – Grafica sobre el trabajo de los Técnicos.

Producción diaria de órdenes respecto a los técnicos.AA0004 – Grafica sobre las Ordenes Terminadas diarias.

Tendencia de las órdenes que se realizan en el tiempo acordado o fuera de tiempo de ejecución.

AA0005 – Reporte por DistritoMuestra la lista de Distritos.

Proyecto 01 – Área de OperadoresAO0001 – Reporte por Operador.

Muestra la lista de Operador con sus órdenes correspondientes.AO0002 – Reporte por Distrito.

Muestra la lista de Distritos por operador.AO0003 – Indicador de Servicios e Instalaciones.

Muestra el indicador de las órdenes por operador.AO0004 – Grafica sobre el operador.

Tendencia respecto a la ejecución diaria de cada operadorAO0005 – Reporte de SIN30 y SIN7

Ordenes que provocan costos adicionales a la empresaAO0006 – Reporte de Ordenes Terminadas – Activas – Reagendadas - Agendadas.

Lista de órdenes que se deben de atender en el dia.AO0007 – Indicador de Ordenes Fuera de tiempo según su fecha de atención.

Indicador de órdenes que se atendieron en el tiempo determinado y los que se pasaron.Proyecto 01 – Área General

AG0001 – Acceso IlimitadoTendrá acceso a todas las funciones del sistemas de control

Page 7: 03 Detailed_Requirements

3. USER INTERFACE REQUIREMENTS

3.1 General User Interface Requirements

3.1.1 Accessibility -

3.1.2 Usability-

3.2 Screens- Se utilizará el estándar de pantallas que actualmente tiene el CRM Portal:

- Color.- Distribución de pantallas.- Paginado sobre pantalla de búsquedas.

3.3 Reports

Report Type Report Name Description User Type Frequency

3.4 Forms

Form Name Description User(s)

Page 8: 03 Detailed_Requirements

4. SYSTEM INTERFACE REQUIREMENTS

This section describes the requirements related to the interaction between the system and external systems, and between internal applications within the system.

4.1 External Interfaces

External Entity Description

4.2 Internal System Interfaces

Application Description

Page 9: 03 Detailed_Requirements

5. BUSINESS RULE CATALOG 5.1

Page 10: 03 Detailed_Requirements

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-DevelopmentThis 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.

Model Office / Pre-Production EnvironmentThese requirements address special considerations for the model office environment in support of the project. 1.

ReusabilityThese 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.

Page 11: 03 Detailed_Requirements

6.2 Environment-DeploymentThis 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-InstallationThis category covers permanent requirements (versus temporary deployment requirements) related to installation of the system. It includes installability requirements, requirements regarding the physical environment, packaging, portability, reproducability, scalability and training.Installability

These requirements address the ease with which the product is installed in the user’s environment.

PortabilityThese 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

TrainingThese requirements address training to be provided to the project team in support of project activities.

6.4 Environment-SystemThis 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.

SoftwareThese requirements address specific software considerations for a project.

6.5 OperationsAvailability

Page 12: 03 Detailed_Requirements

These requirements define when the product is available.

Backup and RestoreThese requirements address plans and provisions for backup and restore operations.

Operation EnvironmentThese requirements address special considerations for the operation and ongoing support of the delivered product.

6.6 PerformanceThis 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.

CapacityThese requirements address the system load at any given time.

RedundancyThese 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.