|
 |
| Articles and White Papers
|
|
|
|
|
|
|
|
Entries for the 'Requirements Analysis (BABOK KA)' Category
» Agile Requirements
 (364 Views)
( 0 Comments)
| In the last few years, the agile software development movement has created a paradigm shift in how we work to understand system requirements. Agile teams shape software systems using a collaborative process, with executable software at its heart and documents marginalised to a peripheral role. This creates a fundamental shift away from tools for ma... |
» A Requirements Analysis Primer
(324 Views)
( 0 Comments)
| Depending on the maturity of the software development processes within an organization, activities such as requirements analysis and design are treated as wasted time. The logic seems to follow that programmers should be writing code, not talking about writing code. For anything but the most insignificant of solutions, this focus is short sighted a... |
» Tips for Business Analysts: Requirements in Complex Systems
(429 Views)
( 0 Comments)
| Some of you may be working on systems with many complex relationships between the parts. These complex systems may be described as a system of systems, or may be described as a product line, or perhaps both at once.
In these cases, you will often find that the requirements of a large, overall system are shared among a number of related projects, e... |
» So You Want To Be a Requirements Analyst?
(377 Views)
( 0 Comments)
| Be it explicitly or not, someone always performs the role of requirements analyst on a software project. The official title may be requirements engineer, business analyst, system analyst, product manager, or simply analyst , but someone needs to translate multiple perspectives into a requirements specification and communicate with other stakeholder... |
» The Popcorn Way and the Business Analyst
 (410 Views)
( 0 Comments)
| Given a specific project with a reasonably defined charter and clear business goals you, the business analyst, set out to elicit and document the detailed business requirements. So when do you stop? How do you know when you are done gathering the requirements? |
» The Software Requirements Struggle
(298 Views)
( 0 Comments)
| Traditional software development has always required a long requirements-gathering phase at the beginning of a project that, if not handled correctly, can often result in schedule delays and costly budget overruns that have a significant impact on the project itself. Software simulation can streamline that process and prevent many of the erro... |
» Specifying Good Requirements
(332 Views)
( 1 Comments)
| Many of the characteristics of properly specified requirements have been well known for many years, at least among professional requirements engineers. Yet most requirements specifications seen today in industry still include many poor-quality requirements. Far too many requirements are ambiguous, incomplete, inconsistent, incorrect, infeasible, un... |
» Requirements
 (372 Views)
( 0 Comments)
| Maybe it was that southern drawl.
Or maybe it was because I got mad.
I'm not sure why I still remember this moment so clearly, but I do. It happened when I was at Spyglass, over ten years ago. Several of us developers were in a meeting with Steve Stone, then recently-hired as director of the Champaign office. We were talking abo... |
» Common Requirements Problems, Their Negative Consequences, and the Industry Best Practices to Help Solve Them
(400 Views)
( 0 Comments)
| In this column, I summarize the 12 worst of the most common requirements engineering problems I have observed over many years working on and with real projects as a requirements engineer, consultant, trainer, and evaluator. I also list the negative consequences of these problems, and most importantly suggest some industry best practices that can he... |
» Requirements Engineering Tasks
 (525 Views)
( 0 Comments)
| Many managers and others who are not professional requirements engineers tend to greatly over-simplify requirements engineering (RE). Based on their observations that requirements specifications primarily contain narrative English textual statements of individual requirements and that all members of the engineering team are reasonably literate, the... |
|
 |
|
|