Knowledge
Software Requirements Management Articles, Blog Posts, Books and Quotes
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
Do Agile Needs Business Analysts?
There is no business analyst role in the Scrum Agile project management framework. Based on this fact and some perceptions about Agile, Roland Hesz tries to answer the questions “Do we need a business analyst on an agile project? Are there Agile business analysts?”.
Read More
From Value to Solutions in Agile
Agile uses mostly user stories to capture requirements. In his blog post, Jean-Jacques Dubray explains that there is a problem with user stories because they tend to focus on the solution and not on the problem definition.
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
A Template for Software Requirements
When you are gathering and documenting software requirements, it is not always easy to remember all the dimension that should be included in this activity. The book “Mastering the Requirements Process” proposes a template that should help you in this activity.
Read More
Modeling with SoaML: Service identification
The power of a service-oriented architecture (SOA) is in its ability to enable business agility through business process integration and reuse. SoaML (Service-Oriented Architecture Modeling Language) is an Object Management Group (OMG) standard that is intended to help realize the potential of SOA.
Read More