(ref.doc)TSE18-10

IEEE Transactions on Software Engineering
Vol 18, No 10, October 1992

Representing Software Engineering Models:
The TAME Goal Oriented Approach
by Markku Oivo and Victor R. Basili

This paper describes a methodology as well as a knowledge
representation and reasoning framework for top down goal
oriented characterization, modeling and execution of software
engineering activities.

What is needed is a top down framework [for SW Eng. research].

It is an attempt at defining a measurement-based closed-loop
process [...]

QIP:
- Planning [quantifiable goals, etc...]
- Execution [provide feedback for corrective action]
- Analysis and Packaging [post mortem analysis]

The model definitions need to be able to evolve, be modified or
refined based on learning [...]

The basic inheritance hierarchies or lattices are not enough for
modeling SEM's and GQM's.

Each object [...] must retain knowledge not only of its
descendants in the hierarchy but also of its possible ancestors,
parts [...]

Relationships:
- Is-A/Children
- Instance-Of/Instances
- Part-Of/Has-Parts
- Compatible-Objects
- Dynamic-Attribute
- Counterpart

Each object can have a potential Is-A relationship to several
super classes but only one of them is active at any point in
time.

[...] we still consider our system a class based system as
opposed to an object-based system such as Self. Self has the
notion of prototype metaphor instead of classes and variables.

In schema evolution [object-oriented databases] the coercion
mechanism discards information during type changes if their
definition is not included in the new type.

The top-down construction of a GQM model starts with the
formulation of an overall top level goal. [...] The goal objects
[...] are characterized by attaching question level attributes
[...] Each question in turn is defined by one or more metrics.

By defining SEM's and GQM's as two clearly separate models, we
can create a highly modular system and a far better support for
representing knowledge in a reusable and easily maintainable
form.

knowledge representation
reasoning principles
inter-object relationships
dynamic viewpoints
selective inheritance
SEM: Software Engineering Model
QIP: Quality Improvement Paradigm
GQM: Goal Question Metric Paradigm
Experience Factory
ES-TAME: Embedded System TAME
RT-SA/SD: Real-Time Structured Analysis and Design

*Note The management of changing types in an object-oriented database:
oopsla86.
Note:
 SELF.