Proof

Often the  ICT-projectbudgets are exceeded due to defects and omissions in the:  specifications, software design, analyses, requirements, testspecifications e.o. .The way is this is handled , differs from company tot company . And even within a company every department  has its own solution. However they hardly succeed in solving the problem.

The damage is enormous : Some figures: 51% of all project excession are caused by defect andomissions in the preliminary processes(analyses, specification , requirements engineering. (source: Standish Report 2005). Defects due to bad requirements make 40 tot 50% of the projectbudget (source: Dean Leffingwell). One third of all projects are exceeding teh budget with more than 150% - 200% .  Not to mention the time-to-market losses. 

Standish Report click  >>>>  HERE

Proof enough you should say: Its time to really change the way of approaching the preliminary processes.

As a part of the solution already more modern projectmethods are implemented. I.e. RUP, Agile , Prince . An iterative approach, prototyping, risk analysis, are the most important issues here. They have in common that they all try to detect possible defects and omissions in an early state, with the goal to specify the right solution in one time in stead of three.  

However another, if not the most important improvement will be the unambigious defining of the right requirements and finding a way to maintain these requirements over the lifecycle of the software production process.  

SOLIM offers with the ARE methodoly a foundation for modern Software Product Life Cycle Management.