|
|
Resources
|
|
Below are various resources for our clients to use in their requirement definition, management, and control process.| Papers | Links | Questions | Guide | Reference Card | Rqmts Mgmt Process | Templates | Example Scope/Rqmts | Watch Ivy Hooks and General Alexander Haig on World Business ReviewAs previously announced by Compliance Automation, Inc., Ivy Hooks appeared on World Business Review, hosted by General Alexander Haig, on CNBC. Now we have brought them to you! Simply click below to view this segment of World Business Review and learn how Compliance Automation, Inc. helps with a methodology to clearly define a projects requirements. See the program. PapersThis page contains various papers and presentations we at CAI have produced for various publications and organizations on topics concerning requirement management and requirement engineering. LinksThis page includes a growing list of links to requirement management and requirement engineering process related information. QuestionsThis page contains answers to questions our students have asked us about requirements. Our "Guide for Managing and Writing Requirements" is available for purchase.Compliance Automation, Inc. developed this guide to help our clients (engineers, scientists, managers and other personnel) in the process of writing and managing their requirements. "For Managers Only" .pps file (1 MB)Since lack of knowledge and skills is a major contributor to poor requirements, training is a key element to improving requirements for a project and in implementing a workable requirements process. This presentation provides a overview of how your organization can deliver a winning product if your people are trained in developing and managing requirements. CAI Reference Card (Side 1 PDF file 747 KB Side 2 PDF file 693 KB)This file was produced by popular demand to allow our clients a quick reference to the generic process covered in our seminars, to the activities you need to complete before writing requirements, and to the definition and qualities that lead to writing good requirements. "Product Requirements Development and Management Procedure" (PDF file 244 KB) prepared by: Pat Schuler and Tom Shull from NASA Langley Research Center (LaRC). This procedure defines a process to generate, document, review, baseline, and manage requirements for your project. Pat and Tom created this requirement management process based on our book "Customer Centered Products". Two prime objectives of this process are "to ensure customer and user requirements are understood and met" and "to define a set of complete, consistent, unambiguous, and verifiable requirements" We are making this process available on our web site so that you can start from a process, and modify it, rather than creating a whole process yourself. Note that this process reflects the needs and work processes of the team that built it. You will most likely need to modify the process to fit your organization's product line and culture. Still plagiarism is a great way to save time and money and this is a well-done job that deserves to be used by many. Please give us feedback on how the use of this process works for you. Requirement Document TemplatesThese are templates developed for the NASA Johnson Space Center Orbiter upgrade office. While they were tailored for their type of projects, they should be of use to anyone wanting an example to start with in developing their own template tailored to their unique process, product, and organization. Program Requirement Document (PRD) Template (188 KB MS Word file) Systems Requirement Document (SRD) Template (364 KB MS Word file) Example web based application scope and requirements. ( 873 KB MSWord file)
This document is from Randolph Air Force Base and is and example of the way they
are creating scope (first several pages of the document) and also writing
requirements for a web-based application. The scope is a fairly simple template
that captures needed data and agreement before the requirements are defined. The
requirement format is unique to this organization and it works. Both the
requirement authors and the developers understand the format and use it for all
their documents. Since the object is an understanding between the requester and
provider --this format is right for them. The VMPF is for members of the Air
Force, active, reserve, and guard, to check their status and input information.
It is replacing lots of paper forms and is a very successful evolving system.
You can actually see the system on-line and get an introduction but not enter it
without having the correct access.
If you have any other resources that you would like to share with the requirements engineering community or have comments or suggestions concerning the resources on this page, |
||
|
Copyright © |