1、Lessons Learned Entry: 1591Lesson Info:a71 Lesson Number: 1591a71 Lesson Date: 2005-02-10a71 Submitting Organization: LARCa71 Submitted by: Kimberly Graupnera71 Authored by: John StoughtonSubject: Requirements Development Abstract: The GIFTS Project requirements development was hampered by differing
2、 roles, goals, and objectives of the participating agencies, partners, and contractor teams. Description of Driving Event: Each team brought their own “requirements culture” to the mix. The process suffered from requirements that were vaguely definable at Level 1, and thus could not be properly allo
3、cated and flowed down to lower levels. Some Level 1 requirements were unfunded, too. Some requirements were specified with verifications that could not be tested. The end result was a GIFTS instrument being designed and built to requirements we had, but not to the requirements we wished we had. Less
4、on(s) Learned: Identify the interested parties and their goals, objectives, and requirements up front. Use one requirements development process from the start, and stick to it. Ensure parties of interest are bringing forth mature requirements and that these requirements are funded. Write specificati
5、ons and verifications that can be tested and measured. Recommendation(s): Have all participating agencies, partners, and contractor teams participate in a group requirements training session specifically for your project. Dont bring in outside parties late in the game. Provided by IHSNot for ResaleN
6、o reproduction or networking permitted without license from IHS-,-,-Evidence of Recurrence Control Effectiveness: N/ADocuments Related to Lesson: N/AMission Directorate(s): a71 ScienceAdditional Key Phrase(s): a71 External RelationsAdditional Info: Approval Info: a71 Approval Date: 2006-04-12a71 Approval Name: dkruhma71 Approval Organization: HQProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
