Functional Requirements Status and Plans

1
Functional Requirements Status and Plans
Christopher Neyman Erik Johansson W. M. Keck
Observatory Viswa Velur California Institute of
Technology
Keck NGAO Team Meeting 11 November 5, 2007
Videoconference
2
Outline

• Status of AO and laser FRD draft 0.3
• Requirements management database tests
• Discussion

3
FRD AO section status

• Converted from Word document to Excel template
  for easier input into database
• Required functionality well documented
• Specification about 75 complete
• Traceability about 75 complete
• Text field references KAON, error budget, SRD,
  and/or ScRD sections.
• Version on Twiki and imported into database

4
FRD Laser section status

• Converted from Word to Excel database template
• Laser status
• 27 pages of requirement, 200 requirements
• Laser requirements, LTA, diagnostics Laser
  service enclosure well done.
• Required functionality well documented
• Traceability 90 (by Nov. 5th)
• Rational 90 (by Nov. 5th)
• Version on TWiki and database (By Tuesday Nov. 6
  CRN)

5
Selecting requirements database software

• Erik Johansson made a brief evaluation of a
  number of requirements management tools for use
  in the NGAO project (details in KAON)
• DOORS (Telelogic)
• Cross-Tie (Teledyne Brown Engineering)
• CaliberRM (Borland)
• OSRMT (open source)
• Rational Requisite Pro (IBM)
• RMTrak (RBC Product Development)
• ARTS (Goda SW)
• Contour (JAMA)

6
Selecting requirements database software

• Selected Contour by Jama Software, Inc.,
• web-based
• multi-user tool
• no client software required
• easy to use and configurable to meet our needs
• reasonably affordable
• user community includes Intel, Amgen, and
  Lockheed-Martin, as well as smaller companies and
  startups

7
Testing requirements database software

• Received a 30 day trial multiple-user version of
  Contour
• Expires Nov. 23
• Installed at Keck
• AO requirements imported from Excel template
• Laser requirements imported from Excel template
• See following screen shots on slides
• Global access through Keck fire wall
• Make accounts and distribute passwords

8
Contour project explorer
Requirements document section easier to organize
final documents
Rationale and traceability (just text field for
now)
Organized by SEMP WBS
Short name for easier searching
9
Contour requirements editor
Rich text editor
10
Contour links and change history
Link to other database elements
Attach documents or web links
Add notes and email change notices
Compare versions
11
Contour issues

• Need to decide on what to put into database or
  link to outside URL
• Automatic report generation
• Issues with formatting
• Outside user testing
• Access should be global (any IP) but requires two
  passwords (Contour and Keck internet)
• Make decision on Contour by November 23.

12
Requirements issues

• Forward and backward trace requires putting
  contents of ScRD, SRD into database
• Make decision on Contour by November 23
• Gather input for AO laser requirements version
  2.0
• Release as design work completes at start of
  calendar 2008