Request For Proposal RFP

1
Request For Proposal (RFP)
The following slides discuss the produced SRS
after requirement analysis phase
2
Physical view
3
(No Transcript)
4
(No Transcript)
5
(No Transcript)
6
(No Transcript)
7
(No Transcript)
8
E-R diagram of the Restaurant System
9
Enhance This Component Diagram
10
Design Example

• System Specification
• This System controls different activities in a
  typical Fast-Food Restaurant, and consists of
  Five communicating units

• - Order-Taking unit.
• - Assembling unit.
• - Preparation unit.
• - Inventory unit.
• - Management unit.

11
High Level Design
Structural View, Using Module-Chart
CUSTOMERS
FOODS
REQUEST-FOR-FOOD
SYSTEM
ORDER-TAKER
ORDERS
CONTROL DATA
ORDERS
ORDERS

ASSEMBLING
ITEMS
CONTROL
MANA GER
CHUTES
ORDER-ITEMS
CONTROL DATA
FOOD-PREP.
ITEMS
MATERIAL
SUPPLIES
CONTROL DATA
INVENTORY
MATERIAL
SUPPLY
SUPPLIES
SUPPLIERS
12
High Level Design
Functional View, Using Activity-Chart
13
High Level Design
Behavioral View, Using Statecharts
14
Detailed Design
PREP-ORDER
CHUTE-ITEMS
Off-page-chart is used to define the details of a
box in the parent chart .
CHUTE_IN
CHUTE_OUT
PREP_IN
PREP_OUT
_at_ASSEMBLY-DIRECTOR
ORD ERS
IN
READY_ORDER
CHUTE- SHORTAGE
READY-ORDERS
READY- ORDER
_at_ASSEMBLY_UNIT_CNTL

• Chart ASSEMBLY-UNIT
• is an intermediate chart
• containing chart-boxes
• and instances of generic charts.

INSTANCE
ASM1ltASM_GENERIC
ASM2ltASM_GENERIC

_at_ASM_INSTANCE_CNTL
ASSEMBLY_UNIT
15
Detailed Design Functional parts

• Functional decomposition
• of each unit determines the
• set of primitive activities.

• Control-activity can be
• a set of concurrent charts
• which control the
• activation of the activities.

16
Detailed Design Control parts

• Design of the user-interface is the
• key to the design of the Control parts .

• Control activity provides the
• concurrent execution of the operations.

• A Distributed-Control mechanism has been used
  to synchronize the operation sequences of the
  buttons in the order-taker screen.

17
Detailed Design ...
Distributed Control Mechanism

• Each concurrent statechart is controlled
• by a condition-variable. (e.g. RECALL_FLAG)

• Pressing a button on the panel, triggers
• an event (e.g. E_RECALL).

• A Reactive-State (e.g. S9) determines the next
  allowed operations.

18
Detailed DesignUser-Interface

• User-Interface design of
• a reactive system is crucial.

• Bindings of the Panel-
• Elements to the Variables
• of the charts are performed
• in the Data-Dictionary Forms.

• Order-Taker screen consists of 40 buttons to
  generate events as inputs and 18 text-displays as
  outputs .

19
Inter process communication
An example of producer-consumer

• Distributed control
• mechanism for private access to the shared-memory

fs!(D_USED)
Key point atomic execution of the actions in one
transition
20
Inter Process Communication ...

• Conditions D_USED BUF_F control the Producer
  and Consumers
• to enter their critical sections respectively.
• Variable WINNER determines which consumer can
  access to the shared buffer.
• (Consumer C2)

21
Instantiation

• - An independent Generic-Chart produces copies of
  a statechart or activity-chart (Reusability).
• - To create an instance of a generic-chart, an
  activity or a state with a special naming pattern
  is used.

Name of Instance lt Name of generic-chart
- Formal-Parameters Actual-Parameters are the
means for communicating the values of variables.
22
Producer Consumer example
Off-Page Chart
fs!(DATA_CONSUMED
Box-is-Chart
Instances of the Generic_Chart
Generic-Chart