CPN Models as Enhancements to a Traditional Software Specification - - PowerPoint PPT Presentation

cpn models as enhancements to a traditional software
SMART_READER_LITE
LIVE PREVIEW

CPN Models as Enhancements to a Traditional Software Specification - - PowerPoint PPT Presentation

CPN Models as Enhancements to a Traditional Software Specification for an Elevator Controller Jens Bk Jrgensen Department of Computer Science University of Aarhus Denmark MOCA04, Aarhus, October 2004 1 Problem: design of an elevator


slide-1
SLIDE 1

1

CPN Models as Enhancements to a Traditional Software Specification for an Elevator Controller

Jens Bæk Jørgensen Department of Computer Science University of Aarhus Denmark

MOCA’04, Aarhus, October 2004

slide-2
SLIDE 2

2

Problem: design of an elevator controller

Subject domain

Ten floors Two cages Buttons, doors, sensors, …

Controller responsibilities

Control movement

  • f cages

Display information

slide-3
SLIDE 3

3

Wieringa’s specification: desired functionality

Mission statement, function refinement tree, service descriptions Partial context diagram Also dictionary and descriptions of entities in subject domain

slide-4
SLIDE 4

4

Wieringa’s specification: desired behaviour of cage movement

Also descriptions of desired behaviour of allocation of request to cages, location indication, etc.

slide-5
SLIDE 5

5

CPN model: representation of controller specification

Set of Standard ML functions

setdirection stophere turnidle servenow resetdirection addrequest removerequest updatelocationindicators

slide-6
SLIDE 6

6

CPN model: desired behaviour of subject domain Entities in subject domain represented as tokens – cages as (cageid,floor,requestlist, direction) Three net modules:

  • Basic Cage Movement
  • Requests and Allocations
  • UpDown and Indicators
slide-7
SLIDE 7

7

CPN model: requirements-level architecture

Representation of controller

Processes ~ Standard ML functions Data stores ~ tokens

Representation of subject domain

Entities ~ tokens

Communications

Possible internal communications in system ~ transitions Possible communications between controller and entities in environment ~ transitions

slide-8
SLIDE 8

8

CPN model: basis for system engineering argument

Argue that specification and domain properties together entail requirements Prerequisites for argument

CPN model executable CPN model coherent

Example requirement: Collect passengers

Trigger: Passenger pushes floor button F Delivered service: Controller ensures that cage stops at floor F and allows passengers to enter

slide-9
SLIDE 9

9

Some perspectives on CPN in software engineering

Compliance with Jackson’s basic tenets

Distinguish the machine from the problem domain Don’t restrict description to the machine State explicitly what is described

Advantages compared with statecharts

CPN adequate to address scheduling CPN conveniently describe two cages together CPN facilitate prototyping and experiments

slide-10
SLIDE 10

10

Conclusions and discussion

Advantages of adding CPN model

Can be used as requirements-level architecture Facilitates system engineering argument

Cost-benefit issues of adding CPN model

Gap between model and implementation Can existing specification be improved with simpler means?

Formal verification viable?

Improve quality of system engineering argument Argue about more advanced behavioural properties Scalability problems