1.0 Participants

Faculty:

• Gregory Abowd
• Ashok Goel
• Mike McCracken
• Melody Moore
• Colin Potts
• Spencer Rugaber
• Linda Wills

Research Assistants:

• Christian Ertmann-Christiansen
• Dean Jerding
• Bill Murdock

2.0 Ongoing Research & Development

2.1 Task 1 Methodology Descriptions

The MORALE approach to software evolution is the synthesis of several methodologies supporting individual aspects of the evolutionary life cycle. To support this synthesis and to enable effective transfer of our methods, we are writing guidebooks for each of the individual methodologies.

2.1.1 Subtask 1.1 Inquiry Cycle Methodology Guidebook
Mission oriented requirements analysis

2.1.2 Subtask 1.2 Software Architecture Analysis Method Methodology Guidebook
Scenario based assessment of software architectures

2.1.3 Subtask 1.3 Synchronized Refinement Methodology Guidebook
Reverse engineering and software understanding

2.1.4 Subtask 1.4 SBF Tutorial and Reference Manual
Structure, Behavior, Function language for describing software systems and their architectures

2.1.5 Subtask 1.5 MORPH Methodology Guidebook
Model Oriented Reengineering Process of Human Computer Interfaces

2.2 Task 2 Tool Development

While MORALE is primarily a methodology project, we are developing several tools to support analysts using the methodologies.

2.2.1 Subtask 2.1 ISVis Event Visualizer
A program understanding and visualization tool for viewing and analyzing event logs of programs executing specific scenarios.

2.2.2 Subtask 2.2 GBRAT Hierarchical Goal Representation Editor/Viewer
A tool to support an analyst constructing mission oriented requirements.

2.3 Task 3 Case Study

The primary validation mechanism for MORALE is the case study. The two case studies we are currently anticipating comprise the analysis of an evolving system and an assessment of SBF as a suitable architectural description language (ADL).

2.3.1 Subtask 3.1 Case Study Schema
We are constructing a schema by which case studies can be performed. We are also undertaking a pilot study of web browsers to instantiate the schema.

2.3.2 Subtask 3.2 SBF Assessment
SBF can be used as an architectural description language. EDCS includes several other projects developing ADLs. MORALE requires a means for representing architectures so that analysis can be performed. This task assesses the adequacy of SBF for this role.

3.0 Notable Accomplishments & Technology Transition

• Rugaber attended a meeting at TACOM attended also by CECOM and ARDEC. TACOM agrees to supply domain documentation and source code for evolutionary legacy systems.
• Rugaber, Moore, and McCracken met with other Georgia Tech groups, briefing them on MORALE. In particular, we met with the simulation group at the Georgia Tech Research Institute which has active contacts with defense contractors who might be interested in our work. Rugaber and McCracken also met with the Army Research Laboratory (ARL), which has a branch on campus, to brief them on MORALE.

4.0 Progress on Inter/Intra Cluster Collaborationn

• Participated in cluster planning meeting in Lake Placid
• Participated in cluster meeting in Marina Del Rey
• Win/Win tool obtained from USC and installed
• Balboa tool obtained from Colorado
• Signed Xinotech non-disclosure agreement in anticipation of receiving their documentation

5.0 Publications

• None yet.

6.0 Travel

• EDCS Kick-off Meeting: Lake Placid, New York, July 17-19, 1996, (Rugaber)
• Rationale Capture and Software Understanding: Marina Del Rey, California, September 18-20, 1996, (Potts)

7.0 Miscellaneous/Administrative/Problematic Issue

8.0 Plans For The Next Reporting Period

• Subtask 1.1 completed
• Subtask 1.2 completed
• Subtask 1.3 completed
• Subtask 1.4 completed
• Subtask 3.1 completed
• Participation in Architecture Cluster meeting, October 23-25, Napa, California (Abowd)
• Participation in DARPA PI workshop, October 7-8, Dallas, Texas (Moore)
• Attend SIGSOFT'96/FSE-4 conference, October 14-18, San Francisco (Abowd)