Current Articles | Search | Subscribe (RSS)

Entries for the 'Requirements Management and Communication (BABOK KA)' Category

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

(2732 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: 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: Business Vocabulary: The Most Basic Requirement of All

(3966 Views) (1 Comments)

Business Vocabulary: The Most Basic Requirement of All

Structured business vocabulary is a missing ingredient in most current approaches to developing requirements. This omission should greatly concern every business analyst. Indeed, business vocabulary is key to a whole range of fundamental challenges, including but not limited to capturing business rules. One reason is that business vocabulary, like ...

» FEATURED: Managing Requirements from a Business Analyst or an Enterprise Architect perspective using BABOK 2.0 and/or TOGAF 9

(6159 Views) (3 Comments)

Managing Requirements from a Business Analyst or an Enterprise Architect perspective using BABOK 2.0 and/or TOGAF 9

Many BAs are using the BABOK which contains information about a Requirements Management process, from identifying organizational situations that give cause to a project, through to starting the requirements gathering process, to delivering a solution to the business or a client. TOGAF 9, from an Enterprise Architecture viewpoint, also pr...

» 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: 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.

» Just Enough Documentation

(2661 Views) (1 Comments)

Is documentation a blessing or a curse? If you’re working on an agile project does it get in the way? If you’re updating a core system that runs your company’s business, are you cursing the analyst who didn’t adequately document all the business functionality? Is today’s agile project tomorrow’s core system?

» 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,...

» Report Requirements: An Overview

(2867 Views) (0 Comments)

A user of almost any given software system or business application will require precise analytics in order to objectively measure its effectiveness, or the effectiveness of an associated product. These analytics –or reports—therefore, must measure the right criteria at the right time(s) in the right way in order to be useful to the user. For that r...

» FEATURED: Documenting SOA (Service Oriented Architecture)

(4741 Views) (0 Comments)

Documenting SOA (Service Oriented Architecture)

For projects that may well be delivered by Service Oriented Architecture (possibly using Service Oriented Analysis), I would suggest that you may need to consider different or additional ways of documenting your requirements and specifications. The reason for this is that the way you shape your requirements needs to encompass both the holistic natu...

» Agile Requirements: Not an Oxymoron

(5895 Views) (2 Comments)

Adult children. Jumbo shrimp. Seriously funny. I’m sure you recognize these expressions as oxymorons—self-contradictory phrases, often with an ironic meaning. Should we add “agile requirements” to the list? Does agile development fit in with traditional requirements practices? And if so, how?

» How to Deliver a Recommendation

(3741 Views) (2 Comments)

Like it or not, every business analyst will have to stand up in front of a group and present. The group might be your business clients, the project stakeholders or just your fellow team members but for many people, one of two things will happen: it will frighten the life out of them OR they’ll umm and ah their way through, sending the audience to s...

Page 1 of 4

First Previous [1] 2 3 4 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 Management and Communication (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 Management and Communication (BABOK KA)' Category

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