- BETA

Wednesday, March 10, 2010

All About Requirements

  • Learn
  • Share
  • Connect

Free Webinar: Leveraging Requirements Visualization – A Biotechnology Company’s Agile Case Study - Register


System Requirements

Business Requirements

Solution Requirements

Software Requirements

Requirements Design

Small Business Requirements

Requirements Education

Requirements Management

Requirements Training

Requirements Engineering

Functional Requirements

Data Requirements

Project Requirements

Information Requirements

Requirements Analysis

Requirements Development

Requirements Gathering

Technical Requirements

Requirements Process

Requirements Specification

Usability Requirements

Requirements Visualization

Product Requirements

Report Requirements

Architecture Requirements

Requirements Definition

Requirements Traceability

Customer Requirements

Website Requirements

Non Functional Requirements

Supplementary Requirements

User Interface (UI) Requirements

Agile Requirements

Model Requirements

Stakeholder Requirements

Requirements Tool

Transition Requirements

Requirements Workshops

Requirements Planning

Requirements Signoff

Requirements Package

Maintain Requirements

Communicate Requirements

Prioritize Requirements

Organize Requirements

Verify Requirements

Validate Requirements

Allocate Requirements

High-level Requirements

Requirements Prioritization

Auditing and Reporting Requirements

Activity Logging Requirements

Licensing Requirements

Security Requirements

Concurrency Requirements

Usability Requirements

Accessibility Requirements

Reliability Requirements

Accuracy Requirements

Precision Requirements

Availability Requirements

Redundancy Requirements

Error-Handling Requirements

Performance Requirements

Stress Requirements

Turnaround-Time Requirements

Response-Time Requirements

Throughput Requirements

Startup and Shutdown Requirements

Supportability Requirements

Scalability Requirements

Maintainability Requirements

Configurability Requirements

Localizability Requirements

Installability Requirements

Compatibility Requirements

Testing Requirements

Training Requirements

Capacity Requirements

Backup and Recovery Requirements

Legal and Regulatory Requirements

Requirements Elicitation

Requirements Application

Requirements Testing

IT Requirements

Writing Requirements

User Requirements


Latest Requirements Buzz

Reusable Security Requirements
This is a great presentation by Donald Firesmith covering the topic of Reusable Security Requirements.  

A Lean and Scalable Requirements Information Model for the Agile Enterprise
Agile development practices introduced, adopted and extended the XP-originated "User Story" as the primary currency for expressing application requirements within the agile enterprise. The just-in-time application of the user story simplified software development and eliminated the prior waterfall like practices of overly burdensome and overly constraining requirements specifications for agile teams. However, as powerful as this innovative concept is, the user story by itself does not provide an adequate, nor sufficiently lean, construct for reasoning about investment, system-level requiremen...

Requirements Gathering - Define Requirements Accurately
The requirements you capture must be stated in business terms, must be clearly stated, must be concise, and must be feasible. To ensure that requirements are clearly stated, you should have them proof read by someone external to the project (or at least someone not familiar with the requirements you've captured).

Ensuring Requirements Gathering Success in an Agile Environment
Quality requirements contribute to the success of agile and traditional project management projects. The requirements definition process followed in a traditional project management framework and the features-based storyboarding that is typical of agile approaches are different, but they also have many similarities. The actual process used to define and gather requirements may be different, but the criteria for quality requirements remain constant. What are these similarities and differences in the process of gathering requirements? What happens to the role of the business analyst in an agile ...

The Sound of Valid Requirements
If requirements management practices were songs entering a popularity contest, requirements validation would hardly be a favorite contender. It's easy to understand why: validation is usually a tedious, time consuming task, and, as with nearly every quality control activity, it is supposed to reveal defects, going against our natural desire of being right, not making mistakes, and singing in tune.

The Path to Requirements Elicitation
The path to requirements elicitation is something that analysts are rarely taught. Everyone knows that it involves interviews and research, but within most organizations, exactly how the interviews and research should be conducted is nebulous.

Requirements Gathering - Define Requirements Accurately
The requirements you capture must be stated in business terms, must be clearly stated, must be concise, and must be feasible. To ensure that requirements are clearly stated, you should have them proof read by someone external to the project (or at least someone not familiar with the requirements you've captured). Any questions raised by your proof reader should trigger a re-write of that requirement. Clean the language up until your proof reader understands the requirement.

The Problem With Defining Information Requirements
There are a lot of problems associated with IT, such as computer performance, capacity planning, security, networking, disaster recovery, but probably the biggest problem is requirements definition. In other words, accurately defining the information needs of the end-user.

Eliminating Ambiguity from Your Requirements
From a developer's standpoint, few things are more frustrating than having to make lots of calls and research to learn what to create because the requirements are ambiguous. From an analyst's view, few things are more frustrating than having your requirements misunderstood. Yet so often, requirements are ambiguous to their readers, despite the writer's best efforts.

Documenting Requirements For Software Development Projects
There are various ways and means by which requirements for software development projects can be gathered and documented.  Before you start documenting the requirements you might want to be sure if you have captured all the required information.  

What are Requirements?

BABOK® Guide, Version 2.0, states:

“A requirement is:

1. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
2. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification, or other formally imposed documents.
3. A documented representation of a condition or capability as in (1) or (2).”

From Wikipedia:

"In engineering, a requirement is a singular documented need of what a particular product or service should be or do. It is most commonly used in a formal sense in systems engineering or software engineering. It is a statement that identifies a necessary attribute, capability, characteristic, or quality of a system in order for it to have value and utility to a user."


Copyright 2009 by Modern Analyst Media LLC