Articles
Reviewing Requirements for Testability
Modern software development approaches like Agile 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 a good […]
Read More
Techne: New Requirements Modeling Languages
Techne is an abstract requirements modeling language that lays formal foundations for new modeling languages applicable during early phases of the requirements engineering process. During these phases, the requirements problem for the system-to-be is being structured, its candidate solutions described and compared in terms of how desirable they are to stakeholders.
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
Clarifiying the Role of Business Analysts
In this article, Trent Wong discusses how well the Business Analyst’s role is defined in organization. He starts by saying that the Business Analyst is a key success factor for software development projects. You need him to getting the requirements list properly, effectively communicating them to management and translating the requirements so the developers can […]
Read More
User Stories Are Not Requirements
The common wisdom is that Agile register requirements using the user stories format: “”As a , I want <goal/desire> so that “. In this article, Earl Beede explains why user stories are not requirements.
Read More