C.1 Case Description

In a fruit-juice production plant, storage tanks and heating tanks are connected by a system of pipes. To produce a batch of mixed juice, ingredient fruit juices are transported from storage to the heating tanks, where they are heated according to a recipe to a temperature for a certain duration. The heating process is started and monitored by a human operator. Your job is to design the heating-control software. This case is based on an example of Shlaer and Mellor (1992).

The specification has the following structure.

• Business context.

  • Business goal tree

  • Operator workflow

• Mission and context.

  • Mission statement

  • Context diagram

  • Assumptions

• Desired functionality.

  • Function refinement tree

  • Service descriptions

• Subject domain.

  • Entity-relationship diagram

  • State transition diagram of heater behavior

• Desired emergent behavior of composite system.

  • Primary event-action pair

  • Transactional event-action list of emergent behavior

  • State transition diagrams of emergent behavior

• Desired system behavior. Stimulus-response list

• Alternative requirements-level architectures.

  • Von Neumann-style architecture without objects

    • Data flow diagram

    • State transition diagram of control process

  • Von Neumann-style architecture with objects

    • Communication diagram

    • State transition diagrams of control objects

  • Pure object-oriented style architecture

    • Communication diagram

    • Sequence diagram

    • Collaboration diagram

    • Static structure diagram

C.2 Business Context

Figure C.1: Business goal tree. (See also Chapters 5 and 14.) The activities in italics are to be supported by the control software.

Figure C.2: Workflow of the operator of the juice-heating controller. (See also Chapter 14.)

C.3 Mission and Context

Figure C.3: Mission statement for a...