Socraweb

There a lot walks miss in the white breads week of a project. A study of the Standish Group puts that the beating chance of projects between 1994 and 2003 alley of scarcely 16% to 31%. There is a noticeable progress, but the pupil has been flunked still. According to the same study, projects walk especially mistake on unclear objectives, vague and changing need definition and flaw at user input. Say but, the phase of requirementsdefinitie.

The last decades is a lot of work perform at this phase. The requirements for CMMI-certifi catie (Capability Maturity Correct Integration) form for that reason a clear proof. As a promotion of maturiteitsniveau 1 is made to 2 in first authority dependent by an investment in the requirementsfase. This article gives ten tips for a good requirementsbeheer, based on industry best practices.

TIP 1: RECOGNIZE DE DIFFERENT LEVELS VAN REQUIREMENTS
A requirementsdefi nitie is notdocument that all truths contain. Rather one is collection of documents that build on each other further and each other verfi jnen. Considerably near it is that one the level of each part respects. As functional requirements come fit on a second level at bid and Server to base they self on a preceding view and probleemdefi nitie. That appears obvious, but this rule is stepped several times with the feet.

TIP 2: INVEST IN A BEGRIJPBAAR view document
We let stand still just by the top layer: the view document. The IT-fingers itch round meanwhile the analysis model, the architecture and even the design to sketch. But what benefit that if it yet obscurity exists around the use of the project and that one stakeholders. The view document brings the opportuniteiten and the exits problems of the project in card. The definieert the stakeholders and the system context. And it give you a complete list of features that the base forms for further analysis. As a final piece, the view document offers an explanatory wordlist. Such wordlist sounds perhaps tritely. Only a lot of misunderstandings can you already asked in the project solve with an unambiguous definition of drafts that otherwise through the different stakeholders different understood would become.