Previous: Design model Up: Design model Next: Detailed design

High level design

Design model of proposed flight combinations.

propose-flight-combination.des:
design model
consists-of:
propose-flight-combination.app

set.arch

minimal-conventional-lisp.plat

Application design

propose-flight-combination.app:
Application design
Application:
propose-flight-combinations
application architecture:
control over the sub-systems but since there is only one subsystem there is no top level control.
has-subsystems:
propose-flight-combinations.sub

propose-flight-combinations.sub:
Sub-system;
name:
propose-flight-combinations;
type:
KBS;
Functionality:
``Proposes a set of flight combinations. It takes the domain model selection-set as an input set and filters out two elements using the criteria that are defined in the domain models afternoon-flight-associations and best-afternoon-flight and produces a set of elements that satisfy the conditions of the domain model flight-pair.''
Implements:
``The task propose flight combinations in the task model.''
Has-decomposition:
propose-flight-combinations.dec
Has-detailed-design:
propose-flight-combinations.dapp

[ propose-flight-combinations.dec:] Decomposition

paradigm:
Expertise;
DDL:
[Terpstra, 1993]
program description:
The decomposition of the subsystem into conceptual entities that realise the functionality.

From the task layer:

propose-flight-combinations; select-morning; filter-flights; select-afternoon; combine;

From the inference layer:

select-1; filter; select-2; combine;

from the domain layer:

domain ontology:

morning-flight; afternoon-flight; flight-pair; domain model:

selection-set; best-afternoon-flight; flight-pair;

___________________________________________________

ronald@arti