Jan 31 2013
This is the fifth and the last part of the summary for the Software Requirements book. Previous posts: Software Requirements – Part 1 Software Requirements – Part 2 Software Requirements – Part 3 Software Requirements – Part 4 Software Requirements Management Requirements management includes all activities that maintain the integrity, accuracy, and currency of the …
Permanent link to this article: https://www.productivecsharp.com/2013/01/software-requirements-part-5/
Jan 16 2013
This is the forth part of the following book summary. Previous posts: Software Requirements – Part 1 Software Requirements – Part 2 Software Requirements – Part 3 Requirements Validation Validation ensures that the requirements exhibit the desirable characteristics of excellent requirement statements (complete, correct, feasible, necessary, prioritized, unambiguous and verifiable) and of excellent requirements specifications (complete, consistent, …
Permanent link to this article: https://www.productivecsharp.com/2013/01/software-requirements-part-4/
Jan 01 2013
This is the third part of the book summary of the Software Requirements book. Previous posts: Software Requirements – Part 1 Software Requirements – Part 2 Who is the Requirements Analyst? The Requirements Analyst is the individual who has the primary responsibility to gather, analyze, document, and validate the needs of the project stakeholders. The …
Permanent link to this article: https://www.productivecsharp.com/2013/01/software-requirements-part-3/
Dec 08 2012
This is the second part of the summary of the Software Requirements book. Previous posts: Software Requirements – Part 1 Let’s continue our discussion with new questions. Who is a customer? An individual or organization who derives either direct or indirect benefit from a product. It is clear that customer development relationship is extremely …
Permanent link to this article: https://www.productivecsharp.com/2012/12/software-requirements-part-2/
Dec 07 2012
In the 1995 the Standish Group did a very revealing research called The Chaos Report. The research shows a staggering 31.1% of projects will be cancelled before they ever get completed. Further results indicate 52.7% of projects will cost 189% of their original estimates. Lack of user input and incomplete requirements and specifications were listed as …
Permanent link to this article: https://www.productivecsharp.com/2012/12/software-requirements-part-1/
