Our SERVICES ...

• Startup Workshop (brainstorming, project definition, problem identification, project team formation, ...)
• Analysis of current state (input-output analysis, interface analysis, staff talks, Selbstaufschreibung ...)
  Support of the analysis performance (review of proposals for the system structure, detailing and specification of target processes, ...)

• Future state definition (Should process definition, drafting the functional requirements, using the Mind Map technique to detail the requirements, providing templates and other information, Masken-/Report-Layouts draft, the definition of interfaces, ...)
• Elaboration of the requirement specification (creation of specifications /  requirement specifications)

More information about this performance range ...

As a part of the requirement analysis, the requirements of the customer are logged as precisely as possible.

This is done mainly in the form of project workshops or interviewing the employees involved (in the case of process analysis).

Furthermore other project-relevant information is gathered, such as  technical, organizational, financial and other conditions as well as the information concerning the current state and current problems.

The current state information is usually gathered in the form of input-output analysis, which can be performed in a very efficient way.

The surveys are complemented  by a functional analysis, interface analysis and a future state definition for the desired system.

The considerations are based on the user and customer view in this phase, not from the technical point of the developer.  

The results of these performances include a detailed requirement specification, cost estimation and a framework for the project plan realisation.

A good requirement specification can be used as a basis for a detailed fixed price offer and a project plan elaboration.

The purpose of the requirement document is to make an agreement about the system to be implemented between the customer and the developer. The content of the requirement specification also serves as a basis for the acceptance of the system by the customer.

On demand it is possible to complement the requirement specification with an analysis and appropriate representation of the benefits and potentials of the solution to be realized, in comparison with the current state.

The requirement specification contains must, wish and definition ciriteria, which serve as a base for the acceptance process. The requirement specification also allows to determine the degree of fulfillment of (or deviation from) the specifications by the application (completed or in development).

Since the requirement specification is usually a part of the contract, it is necessary to reach an agreement concerning the specification contents between the customer and developer.

Further details can also be found in our newsletter on Requirements Engineering.

Information on Requirement creation can be found in the corresponding guideline.