|
 |
| Articles and White Papers
|
|
|
|
|
|
|
|
» Ten Application Definition Best Practices
 (379 Views)
( 0 Comments)
| The ubiquity of software project failures – with failure defined as projects that fundamentally failed to meet business-sponsor expectations, missed scheduled completion dates, or exceeded budget – is a pronounced theme in any number of independent research reports on custom software development. The Standish Group, for example, cited that only 31%... |
» Simulation software a cure for hospital's requirements validation ills
 (283 Views)
( 0 Comments)
| When your users are physicians and nurses, they don't have time to sit in meetings explaining what they want out of an application or to wade through documents validating requirements. Patient care is their number one priority.
To get over that obstacle, the development team at the University of Texas M.D. Anderson Cancer Center relies on a sim... |
» FEATURED: Exploring Requirements with a Wall of Wonder
 (1958 Views)
( 1 Comments)
| In this article, I describe one very effective collaborative technique -- the Wall of Wonder (WoW) -- that helps software teams produce the kind of detailed, sharply defined requirements that effectively guide development. As an "emergent" deliverable, requirements evolve through exploration and examination using representative forms such as low-fi... |
» FEATURED: Integrating iGrafx FlowCharter and Rational Requisite Pro
 (561 Views)
( 0 Comments)
| While working on a Business Architecture effort several years ago, I collaborated on developing a new internal standard for business process and business capability description. From my perspective, a business capability is the required function or desired service that a business unit performs and the business process is the set of methods employed... |
» Requirements Tools that Empower Business Analysts
(604 Views)
( 0 Comments)
| Industry experts agree -- the success of any software development project depends directly on the definition of complete, high-quality, accurate requirements. Today's business analyst (BA) takes a lead role in defining those requirements. BAs are responsible for eliciting, analyzing, communicating, and validating requirements for a huge variety of ... |
» Requirements gathering resources, practices lacking at Fortune 500 companies
(1068 Views)
( 0 Comments)
| Requirements gathering resources and best practices were found lacking at Fortune 500 companies, a recent study from Voke Inc. found. But if business analysts are equipped with the right tools and enough resources, businesses stand to benefit greatly. |
» FEATURED: Software Sizing During Requirements Analysis
(1351 Views)
( 0 Comments)
| Software production has become one of the key activities of the industrialized world. Software applications are now the driving force of business, government operations, military equipment, and most of the services that we take for granted: electric power, water supplies, telephones, and transportation.
Most major companies and government agenc... |
» Volere Requirements Techniques: an Overview
(817 Views)
( 0 Comments)
| The Volere requirements techniques were developed to answer the need for a common language for discovering requirements and connecting them to solutions. The language needs to be understandable by business people, customers, business analysts, engineers, designers, suppliers, testers or anyone else whose input is needed. All of these people have di... |
» Managing Process Architecture and Requirements in a CMMI® based SPI project
(411 Views)
( 0 Comments)
| When developing or changing a process, and all its related assets, often the process engineers have to face an important issue: how defining an integrated set of processes so that each process element is designed taking in consideration its relationships with all the other interfacing elements. Together with this issue, we also have the need to ens... |
» Rapid Requirements Engineering – Does a Specification Always Need to Come at the Start?
(481 Views)
( 0 Comments)
| Requirements and the way they are dealt with are decisive to the success of a project. This statement is never really questioned in modern software engineering circles.
Why is it, then, that a systematic requirements engineering (RE) system is so rarely established?
Where do the problems lie when it comes to implementing such a system?
This p... |
|
 |
|
|