|
 |
 |
Home
>
Hot Topics
>
Requirements
Hot Topic: Requirements
Defining, changing and gathering requirements is one of the first steps that can get your project off on the right foot, or headed down the wrong path.

Testing Requirements
- by Luc K. Richard
(October 27, 2003)
|
|
Requirements Definition is one of the various activities of the software lifecycle. And like any other activity, it must be tested before being declared as complete.
|

The Requirements Puzzle
- by Paula K. Martin
(May 2, 2001)
|
|
Before you start putting the pieces together, you need to see the big picture. Learn how to define your customer's project requirements and fit them into the right solution.
|

The Art of Requirements Gathering
- by George Spafford
(March 10, 2003)
|
|
A project has an objective to attain in a fixed amount of time with a limited amount of resources. Attaining the objective means that necessary requirements must be identified and managed. The intent of this article is to build on previous articles discussing expectations and provide some ideas about the requirements-gathering process.
|




Know What You Need
- by Andre Leclerc
(June 2, 2000)
|
|
Do you really expect to get what you want if you don't know what you need? Requirements are essential to success. Get them right--right from the start.
|

Discovering Stakeholder Expectations
- by George Spafford
(December 11, 2002)
|
|
It pays to understand and manage the expectations of sponsors and stakeholders. As expectations are reviewed and nominated to become requirements, the use of a "parking lot" list will help ease the stress for some unmet expectations, and change management will further help ensure that expectations are met when the project draws to a close. Park your eyes here to find out more.
|

Stakeholder Expectations
- by George Spafford
(November 4, 2002)
|
|
We've explored the identification and mapping of stakeholders, the first steps of the expectation management process. If expectations are not actively managed during the course of a project, then the risks for partial or total project failure increase. With that in mind, this article will continue to explore the theme and lay the groundwork for the active management of stakeholder expectations.
|

Designing to Close the Stakeholder Value Gap
- by Michael R. Wood
(June 15, 2001)
|
|
Asking stakeholders what they value seems to be the easiest way to find out. But there are flaws in traditional survey techniques. Here's a three-pronged approach that can help you close the treacherous stakeholer value gap.
|

Requirements Documentation
(
Report
-
Template
)
|
|
Complete and accurate requirements are possible if you use a template that takes the guesswork out of the process--changes in the user's mind notwithstanding.
|

Preliminary Application Development Requirements
(
Specifications/Procedures
-
Template
)
|
|
If you are developing an application for users, it helps to know what your basic business requirements are before you begin extensive analysis and design. This form will help you document them.
|

User Requirements Planning Form
(
Specifications/Procedures Questionnaire / Questionnaire
-
Template
)
|
|
When developing a new system, you'll have to interview the future users and ascertain their requirements for the system. This form walks you through the process.
|

Pre-Development Requirements Checklist
|
|
To ensure that the system you are preparing to build fully addresses all the necessary user and technical requirements, and only those requirements, answer the questions in this checklist.
|


Business Information Requirements
(
Report
-
Template
)
|
|
What data should you keep in a Data Warehouse and why? This form helps you identify the needed data and its associated characteristics in relation to your business requirements.
|


Stakeholder Requirements Comparison Matrix
(
Template
)
|
|
Different stakeholder groups affected by your project will want different results. Each group's requirements will not only differ, but sometimes be in conflict. Use this template to identify conflicts/potential conflicts, gaps, contradictions or incompatibilities between stakeholder group requirements, so you can reconcile them.
|

Software Requirements and Technical Specification
(
Template
)
|
|
When you're dealing with software requirements and technical specifications, you can't be too thorough, too detailed or too careful. This template will help you identify the functional/technical requirements for your own special project. It also will help you describe the data model that will be used along with its implementation.
|

| Whenever you are asked if you can do a job, tell 'em, "Certainly, I can!" Then get busy and find out how to do it. |
| - Theodore Roosevelt |
|
|
 |
|