Requirements Analysis (BABOK KA)

7202 Views
0 Likes
3 Comments
Extreme programming (XP) introduced the practice of expressing requirements in the form of user stories, short descriptions of functionality–told from the perspective of a user–that are valuable to either a user of the software or the customer of the software. The following are typical user stories for a job posting and search site: ...
7608 Views
0 Likes
0 Comments
As long as practitioners recognize that use case diagrams are optional and iconic (as opposed to schematic), they shouldn't have problems. The diagrams are useful, for example, on whiteboards as a way of sketching and framing an agenda while people are writing up and reviewing use case detail on index cards. The trouble starts, however, when pr...
5422 Views
0 Likes
1 Comments
There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the c...
8105 Views
0 Likes
0 Comments
The requirements engineering phase of software development projects is characterised by the intensity and importance of communication activities. During this phase, the various stakeholders must be able to communicate their requirements to the analysts, and the analysts need to be able to communicate the specifications they generate back to the sta...
7029 Views
2 Likes
0 Comments
We know that we must involve all the stakeholders if we want to discover a project’s requirements. But we need some guidelines on how to involve the right people and, given how busy everyone is, how to minimize the time and maximize the result. In this article, requirements expert Ellen Gottesdiener (www.ebgconsulting.com) shares her consider...
6993 Views
0 Likes
0 Comments
A multitude of sins can be hidden behind the phrase “living document.” You can submit documents that are incomplete or inconsistent as long as you promise to fix it later. In this month’s issue of Strategic Software Engineering, I want to talk about the strategic importance of being realistic about the state of knowledge, plans an...
4326 Views
0 Likes
0 Comments
In part 1 of this article EBG Consulting's Ellen Gottesdiener discussed the need to adapt your requirements practices to your product and project. In part 2, she explores additional issues for tailoring requirements development and management. Author: Ellen Gottesdiener
3770 Views
0 Likes
0 Comments
Should your requirements practices embrace the change-driven approach of agile methods--lightweight models, minimal documentation, and little process? Or should you take a risk-driven approach--robust models, careful validation, and rich documentation? In this two-part weekly column, EBG Consulting's Ellen Gottesdiener explains that you should tail...
4512 Views
0 Likes
0 Comments
Read about the lively Use Case Panel: Discussion Among the Gurus - a panel held at the 2002 Rational Users Conference. "Doug Rosenberg wouldn't have a 20-page use case. Ian Spence would. But, as Ellen Gottesdiener reminded the panel, it's not all about size. Welcome to the Use Case Panel: Discussion Among Use Case Gurus. And what a panel it ...
6870 Views
0 Likes
0 Comments
Just how important is it to fully develop your project’s requirements? After all, nailing down your requirements usually takes only 8% to 15% of your overall project effort. Truth be told, it’s not really something you’ll want to spend your resources and energy on—unless, that is, you care at all about the quality of your pr...
4523 Views
0 Likes
0 Comments
This article explores the top nine reasons the author, requirements expert Ellen Gottesdiener, has heard for NOT doing requirements right -- and how to address these reasons in response.  Author: Ellen Gottesdiener
6558 Views
0 Likes
0 Comments
Every project has requirements. It doesn't matter if it's building hardware solutions, developing software solutions, installing networks, protecting data, or training users. For the project to be a success, knowing what the requirements are is an absolute must. Requirements exist for virtually any components of a project or task. For example, a p...
6021 Views
0 Likes
0 Comments
 Most books and articles on software requirements are written as though you’re gathering requirements for a brand-new product—what’s sometimes called a green-field project. In reality, few people have that opportunity on every project. Many developers work on maintenance projects. In such a project you’re usually adding...
4805 Views
0 Likes
0 Comments
The software industry is exhibiting an increasing interest in requirements engineering — that is, understanding what you intend to build before you’re done building it. Despite the hype of "Internet time," companies across many business domains realize that time spent understanding the business problem is an excellent investme...
4993 Views
1 Likes
0 Comments
In the discipline of business analysis, the "hard skill" is writing (or modeling) and documenting the system or software requirements so that they are recorded, communicated and approved. Often, however, this important skill is also the one that is understood the least. Various formats or deliverables are used to document system and software requ...
Page 12 of 13First   Previous   4  5  6  7  8  9  10  11  [12]  13  Next   Last   

 



Upcoming Live Webinars

 




Copyright 2006-2024 by Modern Analyst Media LLC