Blind Spots in Requirements Engineering
The importance of requirements engineering in the development of IT systems has been gaining traction in recent years. This is evident in the number of tools (e.g., IBM’s Requisite Pro, Serena, and Doors) that have gained in popularity and market share over time. Project managers are increasingly realizing the importance of allocating the time, resources, and funding required in gathering and managing business and functional and non-functional requirements at the onset of their projects. There is an expectation that these will result in increased customer satisfaction, better quality project results, and lower costs. Businesses and project teams invest in these costly software tools in the hope that the features the tools offer will help in ensuring project success through greater visibility into the scope and impact of requirements.
There is no doubt that using a structured approach to requirements development and management offers many benefits. It creates an environment that fosters collaboration and accountability. Using effective channels of communication with customers during the analysis and build phases, leads to higher levels of customer satisfaction. Having complete and accurate requirements capture enables the creation of accurate task and project estimations and the improved ability to manage risks and adjust to changing needs. Capturing requirements
Please log in or sign up below to read the rest of the article.
|
If you haven't got anything nice to say about anybody, come sit next to me. - Alice Roosevelt Longworth |




