Project Generalities

For each of the above projects establish:

• Informal and formal domain descriptions,
• informal and formal requirements descriptions,
• informal and formal software design proposals:
  • software architecture descriptions and
  • program organisation descriptions.

Each project report must show that the following aspects have been covered -- or to which degree (on a scale of 0-10) they are covered in the project report:

• Conformance Expectations:
  • Descriptions (Chapter 10):
    • Designations
    • Definitions
    • Refutable Assertions
  • Abstractions & Modelling (Chapter 3):
    • Model- respectively Property-oriented Models.
    • Representation resp. Operational Abstraction.
    • Hierarchical vs. Configurational Abstraction.
    • Denotational and Computational Semantics.
  • Domain (Chapter 8):
    • Stake-holder Perspectives.
    • Normative contra Instantiated Domain.
    • Intrinsics.
    • Domain Support Technologies.
    • Domain Rules & Regulations.
    • Domain User Behaviour.
  • Requirements (Chapter 10):
    • Domain to Requirements Projection.
    • Domain Requirements Instantiation.
    • Domain Requirements Extension.
    • Interface Requirements: Which aspects ?
    • Machine Requirements: Which aspects ?
    • Scripts ?

This ``coverage'' can be most simply identified by ``copying'' the above text and inserting L^ATEX \vref references to your text.

The next section outlines more.