System requirements are interactions between agents/users and software components within the system. System requirements translate business requirements. Business requirements provide the "black box" description of the enterprise software system while system requirements provide the transparent, or "white box" description. System requirements enter the black box and describe sub-functions performed by agents and software components.

System requirements are further divided into functional and nonfunctional requirements. Functional requirements realize the business requirements. Nonfunctional requirements are simple statements that specify the qualitative requirements for software components as to how well they perform their functions. Examples of nonfunctional requirements include availability, testability, maintainability, performance, ease of use, etc.

This service translates the business model into a user model that contains complete technical specifications of the project.

Benefits

• It becomes easy to decide precisely what to build for the detailed technical requirements, including all the interfaces to people, to machines and other systems

• These user requirements are precisely correct simply because they are the results of direct translation from business requirements

Inputs

• Use case templates, descriptions and guidelines as well as report template

 Outputs

• User case report, user interface prototype, and logical data model

 Typical Duration

• 5-15 weeks

 Typical Efforts

• 15-35 days