CSC 508 Milestone 5
Functional Requirements

When completed, the work for each tool should be checked into the projects/work directory for each project and informally inspection tested. "Informally" means that one group member should perform the inspection tests per the CSC 205 handout, but need not formally record the results.

The following is a summary of the tasks discussed in the 27-29 October meetings:

• Infrastructure Group
  • Top Level
    1. Update top-level menu to reflect changes:
       1. eliminate options menu, moving options functions (if necessary) to Edit Preferences
       2. document new style of menu presentation in each tool
    2. Begin work on completion of Sections 2.1 (Terminology and Definitions) and 2.3 (Common Environment Features).
  • Process Navigator, Browsing
    1. Modify idraw screen shots to reflect new organization of functions.
    2. Work with Artifact Navigator group to unify common navigation features.
    3. Begin work on new scenarios listed in "Work in Progress" section of last year's requirements.
  • Process Navigator, Enactment
    1. Refine step editing and gateway dialogs to reflect new features.
    2. Begin scenarios showing integration of large-grain dataflow programming within process navigator.
  • Artifact Navigator
    1. Modify idraw screen shots to reflect new organization of functions.
    2. Work with Process Navigator group to unify common navigation features.
    3. Begin work on new scenario for graphical view of linking information.

• Main Line
  • Requirements
    1. Work on functionality for listing and prioritizing requirements.
    2. Work with Prototyping Tool group on support for process iteration between the tools.
  • Prototyping
    1. Convert extant screen shots to Illustrator and work on new top-level interface.
    2. Work with Requirements Tool group on support for process iteration between the tools.
  • Design
    1. Work on updated form-editor UI.
    2. Work with Implementation Tool group on support for process iteration between the tools.
  • Implementation
    1. Work on new initial UI, consisting of (smart) text editor and debugging palette).
    2. Work with Design Tool group on support for process iteration between the tools.

• Pervasive
  • Testing
    1. Work on new initial UI, based on modified structure of artifact hierarchy.
    2. Update existing UI based on modified artifact hierarchy.
  • Config
    1. Continue refinement of last year's requirements, per reorganization list from Milestone 3.
    2. Read J. Tharp requirements on generalized version control and consider how to integrate those ideas into Inferno.
  • Admin
    1. Work on new initial UI, describing how schedule is initialized from process definition.
    2. Describe post-initialization functionality of adding new milestones to the schedule.
    3. Begin to define administration-related requirements for other Inferno tools.