system analysis

    • requirement specifications

    • prioritization of requirements

 

requirement specifications

Experience shows that a systematic approach is vital to the success of any larger IT project. The most important step is the definition of the requirements to be fulfilled by the software system.

Thus, the definition of the specs are at the beginning of every project. All requirements and boundary conditions on the customers side are written down. Technical solutions or concepts to realize the requirement are not part of the specs. These specs will be the basis of an offer, and will at the end of the project allow the customer to objectively judge on the success of the project.

Projects run the risk of failure, if in the very beginning the aims of the project are not detemined, at least they tend to miss their cost and time targets.

prioritization of requirements

Not always all requirements can be fulfilled by a real IT system. Often there are limits due to technical or financial restrictions or due to boundary conditions. Therefore, it may be a good idea to let the customer evaluate the "importance" of requirements which ends up in a prioritization of the specs.