Current Articles | Search | Subscribe (RSS)

Entries for the 'Requirements Analysis (BABOK KA)' Category

» FEATURED: How Detailed Should Requirements Be? Part 3 - When More Requirements Detail Is Advisable

(2731 Views) (3 Comments)

How Detailed Should Requirements Be? Part 3 - When More Requirements Detail Is Advisable

There are several situations in which recording only high-level requirements information increases the project’s risk. When you encounter situations such as the ones described in this article, expect to spend more time than average developing detailed requirements specifications.

» FEATURED: How Detailed Should Requirements Be? Part 2 - When Less Requirements Detail Is Appropriate

(2179 Views) (2 Comments)

How Detailed Should Requirements Be? Part 2 - When Less Requirements Detail Is Appropriate

Several conditions make it appropriate to leave the requirements descriptions at a higher level of abstraction. Recognize that these are broad guidelines. The BA should perform a risk-benefit analysis to balance the potential downside of omitting important information against the effort required to include it.

» Requirements Reuse: the State of the Practice

(928 Views) (0 Comments)

Requirements Reuse: the State of the Practice

For several decades, software reuse has been a recognized solution to improving efficiency of software development. However, implementing reuse in practice remains challenging and the IT community has little visibility into the state of the practice specifically as it pertains to reusing software requirements. This paper presents the results of a s...

» FEATURED: How Detailed Should Requirements Be? - Part 1

(6300 Views) (15 Comments)

How Detailed Should Requirements Be? - Part 1

Recently I was chatting at a wine tasting event with a couple of lawyers, who I had just met. One was surprisingly inquisitive about my work in the software requirements arena. Apparently she was working on case involving software at that very time. At one point she asked me, “How do you know how detailed to make the requirements?”

» FEATURED: How to Effectively Engage Requirement Contributors to Achieve Project Success

(2274 Views) (0 Comments)

How to Effectively Engage Requirement Contributors to Achieve Project Success

Your new system just went live and the project, that replaced a critical legacy system, is coming to a close. Business analysts gathered requirements and worked closely with users and developers, but did you capture all of the requirements?

» FEATURED: Starting Your Requirements Education

(3003 Views) (1 Comments)

So you want to be a better requirements analyst. Or maybe you’re completely new to business analysis and you just want to learn what requirements analysis involves, period.

» FEATURED: An Introduction to Requirements Traceability

(4444 Views) (2 Comments)

An Introduction to Requirements Traceability

Requirements traceability ensures that each business need is tied to an actual requirement, and that each requirement is tied to a deliverable. This is a valuable practice for the business analyst. According to A Guide to the Business Analyst’s Body of Knowledge, (BABOK 2.0), all requirements are “related to other requirements, to solution componen...

» FEATURED: Requirements Are Rules: True or False?

(6848 Views) (3 Comments)

“Requirements are rules. They arise from business models, but they are different from those business models.” Perhaps you’ve heard the argument. Maybe you’ve even made it yourself. Are they? No! Read this article to find out why.

» FEATURED: Taming the Beast of Complexity

(2290 Views) (2 Comments)

In that article we presented our case that the typical approach to business requirements management was fundamentally flawed, with key issues being development of business requirements within a project context, and capture of those requirements using unstructured artifacts, particularly narrative.

» FEATURED: The structure of business analysis documents

(12016 Views) (5 Comments)

The structure of business analysis documents isn't a commonly discussed topic. This article will show what documents are produced by a BA and the main sections they contain. These are the main documents produced by a BA over the course of a project...

» FEATURED: iRise Requirements Visualization

(3805 Views) (0 Comments)

Thousands of business analysts have turned to software visualization from as a strategy to simplify their jobs and cut through the confusion. With iRise, business analysts are empowered to quickly assemble a high-fidelity working preview of an application before development ever begins. These visualizations look and act just like the final product,...

» Measurably Improving Your Requirements

(3343 Views) (3 Comments)

Requirements continue to be a major problem area for most organizations. According to industry reports, the leading causes of quality, cost, and schedule problems are lack of understanding of the customer’s needs, incomplete requirement specifications, and managing changing requirements. In fact, requirements are so important that one of the defini...

» FEATURED: Requirements and the Beast of Complexity

(9186 Views) (1 Comments)

Requirements and the Beast of Complexity

This article promotes a new approach to requirements management that reduces project complexity and improves communication between business and IT. This new approach can be used on its own, or as a supplement or precursor to existing approaches. Critical features of the approach are: detachment of business requirements from individual projects; and...

» FEATURED: Six Simple Steps for Accelerating and Perfecting Requirements: A Framework, a New Model, and Visualization

(5439 Views) (2 Comments)

Six Simple Steps for Accelerating and Perfecting Requirements: A Framework, a New Model, and Visualization

We present a requirements framework and methodology that may be different from what you are doing. Its three prominent characteristics are a framework, a new model, and visualization. The framework ensures completeness of all requirements. The new model is the Decision Model, transforming important business thinking into a tangible and manageable b...

» FEATURED: Using Extreme Inspections to Significantly Improve Requirements Practice

(5075 Views) (6 Comments)

Using Extreme Inspections to Significantly Improve Requirements Practice

Extreme Inspections are a low-cost, high-improvement way to assure specification quality, effectively teach good specification practice, and make informed decisions about the requirements specification process and its output, in any project. The method is not restricted to be used on requirements analysis related material; this article however is l...

Page 1 of 6

First Previous [1] 2 3 4 5 6 Next Last

Join the Premier Community for
Business Analysts, Business Process Professionals,
Systems Analysts, Data Analysts, and more…

Business Analyst Articles: Business Analysis & Systems Analysis

Entries for the 'Requirements Analysis (BABOK KA)' Category

Join the Premier Community for Business Analysts, Business Process Professionals, Systems Analysts, Data Analysts, and more…

Business Analyst Articles: Business Analysis & Systems Analysis

Entries for the 'Requirements Analysis (BABOK KA)' Category

Join the Premier Community for
Business Analysts, Business Process Professionals,
Systems Analysts, Data Analysts, and more…