Short Description ...

Requirements specification is that part of specification that describes requirements for a new or changed system from a user's view.

>>  WHAT should the specified system be capable of?

[The terms requirements specification and specification are often used interchangeably.]

Product specifications contain a detailed description of capabilities (eg. technical, economical, organisational), which are necessary or required in order to reach the goals of the project. (DIN 69901)

Our Services ...

• startup workshop (brainstorming, project scope, spot problematic areas, build project teams, ...)
• analyze current status (input-output analysis, interface analysis, interviews with employees, self-recording, ...)
• support in conducting analysis (review of system architecture proposals, finding details and specification of required prozesses, ...)
• project workshops (define required processes, develop functional requirements, mind-map techniques for detailing requirements, design layouts of form templates, ...)
• finalizing the requirements specification (creation of specifications)

Customer quote ...

Project: "Requirements specification and feasibility study" for a new standard product development at an internet engineering company in Linz, April 2003

Quote from an e-mail we received from management:

"Dear Mr Bergsmann,
we recognized your workshop as very inspiring to us. Of course we always try to do as much as possible in-house,
but it was very enlightening to realize that competent external experts absolutely make sense."

More information about this service ...

In the context of requirements engineering we try to collect customer requirements as completely as possible.

This is mostly done in the form of project workshops or process analysis, where the involved employees are interviewed.

Furthermore we collect other important information like technical, organizational, financial and more constraints as well as the information concerning the current status and acute vulnerabilities.

The current status is in the majority of cases collected in the form of efficiently performable  input-output analysis.

The surveys are supplemented with a functional analysis, interface analysis plus required-process-definition for the targeted system.

In this phase we consider mostly the customer's/user's view and not the developer's technical perspective.

As a result of this services a comprehensive requirements specification is made, together with a cost estimation and a skelet of project plan for implementation purposes.

A well-made requirements specification can be used as solid base for a detailed fix-priced offer and the creation of the project plan.

The purpose of the requirement document lies in specifiyng the functionality of the system to be developed, and agreeing on it by both contractor and client. The content of the requirements specification serves as  a base for the acceptance of the system by the client.

On demand the benefit and the potential of the future solution can be compared to the current state, together with a proper analysis and an adequate results presentation.

The requirements specification contains must-have, desired and differential criteria that are to be followed during the acceptance process.

With the requirements specification it can determined later, whether and how the finished (or being in realization) application meets the predefined requirements.

As the requirements specification is usually a part of the project contract, it is essential that there is an agreement on the requirements specification before the contract is created.

If you are interested in more information concerning the requirement engineering, please visit our newsletter section.