Usability Views Article Details
 home | timeline | recent | popular | e-reports | userati | books | about 

Taking Software Requirements Creation from Folklore to Analysis (15 Feb 2006)
Large software systems are too often late, costly and unreliable. Too often the requirements are not well understood or wrong. Understanding and bounding the requirements in a specification is an essential step to solving this problem. As early as 1970 Royce pointed at that unvalidated requirements leads to unmanageable projects. In particular, requirements complexity drives effort required to build software intensive systems, the time it takes to build them and their inherent reliability. Complexity management is critical and by enhancing existing simulation environments used by system engineers to formulate alternative system designs, software engineers can understand the sensitivity of requirements complexity to the likelihood of producing a workable system. Model-Driven Software Realization is a current practice for achieving this understanding. Combining functional and performance simulations with sizing and effort estimation efforts leads to a holistic understanding of feature, form, cost, schedule and trustworthiness.
Add this article to

Article URL:

Read 374 more articles from Ubiquity sorted by date, popularity, or title.
Next Article: Mastering Ajax, Part 3: Advanced requests and responses in Ajax
  RSS 0.91  Subscribe with Bloglines  Add to My Yahoo!  Preview in Google Reader
Books about Usability | Information Architecture | Information Visualisation | Technology History

Some of the people who make up the Userati group
This site is a labour of love built by Chris McEvoy

Popular Items
> Top Knitting Sites
> Ajax Sucks
> What if Jakob Nielsen had a blog?
> Kate Bush and Pi
> Simply Google