In this blog post, Karl E. Wiegers tries to answer the question: How long will it take to “do requirements” on your software project? The answer is naturally: it depends! The post lists conditions that can accelerate requirements development and other factors that lengthen the time needed for effective requirements development. Things are also different if you use a traditional project approach or if you follow an incremental and iterative framework like Scrum. You should also examines the tasks that the business analysts will actually perform and how long those tasks will take. All this should improve your ability to estimate the requirements development effort needed for future projects.
How Long Do Requirements Take?
Reviewing Requirements for Testability
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]Read More
User Stories for Both Requirements and Testing
User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, […]Read More
Understanding System Analysis Models
This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.Read More