FireBoard
Welcome, Guest
Please Login or Register.    Lost Password?
Go to bottom Post Reply Favoured: 0
TOPIC: The Requirements Document
#5
admin (Admin)
Admin
Posts: 6
graph
User Offline Click here to see the profile of this user
The Requirements Document 2 Years ago Karma: 0  
There are two components to a workable Requirements document.

First, a clearly explained and cataloged list of requirements, deliverables, and measures of success.

Second, you need an inventory of what exists today. The inventory validates how much work is left to do during the Design and GAP Analysis Phases. After all, there is not much to do if you can find solutions to these problems lying around in some Government think-tank database already.

Deliverables of our Air Car Future Project include:


* a flying car in every driveway

* widely available air car alternatives combustion-based automobiles

* a ban on combustion-based automobiles

* a renewable fuel alternative for trucking

* a robot-maid in every household

* button-pushing convenience in day-to-day chores and activities (not related to exploration and discovery that is)

* Food Replicators - enery to matter. An end to world hunger? Or can re-allocation do it?

* Travel Faster than light. You know - "Warp" propulsion

* Renewable/Sustainable Energy Sources capable of sustaining space exploration

* Stasis technology - "sleep" for 100 years and wake without aging once the trip is completed

* Cure or enhibit Aging - a disaster for the planet? … or a must-have for space travel.

* Traffic Light Timing - this is a Quick-Win idea promising to save millions in new road construction & emissions




Whatever the list contains initially, a stakeholder approved list is far from us at this point. I really am hoping for your help and am asking visitors to contribute to the list of advancements that you would like in your future - as you would like to see them...

* What are the additional priorities that need to be added?

* What doesn't belong on our list?

* What priorities and timing should be assigned?



Information about the information ...

Every "Requirements List" needs a few important additional information pieces in order to be fully useful to our planning effort. Important information to include in our list of Requirements includes the following:


* A catalogue number - becomes the basis of our Quality Control Checklist

* Summary Description

* Detailed Description - as required

* Priority - A, B, or C (where A is Imperative, B is Important, and C is "Nice to Have"

* Timing - when should this requirement be completed?

* Grouping - the meeting or grouping that this subject should be included along with other similar topics.



This forum is a great communications tool but its not the best place to keep our list - the list needs to be sortable and easily formatible - so I will include an initial Draft Excel spreadsheet. Download a copy of the Spreadsheet tool at OpenOffice.org to view this file...
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#7
jennyshred (User)
Fresh Boarder
Posts: 1
graphgraph
User Offline Click here to see the profile of this user
Re:The Requirements Document 5 Months, 3 Weeks ago Karma: 0  
It looks like you are defining a modern and out of this world future of cars this time. Truly if you will get the opinion of others to add on your list, one whole sheet of paper is not enough. You need to develop a workable spreadsheet where you can sort our everything.
 
Report to moderator   Logged Logged  
 
Last Edit: 2010/04/16 23:27 By jennyshred.
 
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop