Overview. Th d l t. • The development process. • Documents. • OAD in
Requirements Analysis. 1 ProblemDomainAnal sis. 1. Problem Domain Analysis.
2.
OOAD summary OOAD-summary
Overview • • •
The development Th d l t process Documents OAD in Requirements Analysis 1. 1 2. 3 3. 4.
Problem Domain Analysis Anal sis System Definition Class Association, Class, Association Dependency Behaviour, Event
Your Report! 1. Requirements Specification 1.1 System Definition 12 P 1.2 Problem bl D Domain i Structure St t 1.3 Application Domain Structure p Test Specification p 1.4 Acceptance
Example: Computer Vison based implement guidance in row crops p
A rich picture
System Definition •A concise description of a computerized system •Expressed in natural language
Example: A computer system which guides an implement through crops in rows. The system must not be slower than the traditional guidance methods, and must relieve human operators of local monitoring and control tasks tasks.
Example:The prototype software
FACTOR A concise description of a computerized system expressed in natural language FACTOR: •Functionality for end use •Application Application Domain of end use •Conditions for success •Technology gy to be used •Object System •Realization conditions
Example: FACTOR A computer system which guides an implement through crops in rows. rows (Application Domain). Domain) The system must not be slower than traditional guidance methods (Conditions), and must relieve human operators of local monitoring and control tasks (Functionality). The final system must be implemented on a TriMedia TRS8XX with a simple display and button user interface (Technology and Object System) The system shall be very dependable and inexpensive to produce (Realization Constraints). Constraints)
Problem Domain Description • Class Diagrams (things and their relations) • Selected Behaviours ((events and their sequence) • Notes - text ((interpretation p of concepts p )
Example: Problem Domain Structure
Example: Tractor Behaviour
In row Outside row
Manual start stop
Auto
Example: Interaction of Tractor and Row Weeder
:Tractor
:RowWeeder lower
engage
no row no_row
Summary: P bl Problem Domain D i Analysis A l i • • • • • •
Rich Picture System definition - FACTOR Structure - Class Diagrams Behaviour - Statechart Diagrams Interaction - Sequence Diagrams Notes
Your Report - 1! 1. Requirements Specification 1.1 System Definition 12 P 1.2 Problem bl D Domain i Structure St t 1.3 Application Domain Structure p Test Specification p 1.4 Acceptance
Your Report - 2! 1. Requirements Specification 1 1 System 1.1 S t Definition D fi iti 1.2 Problem Domain Structure 1.3 Application Domain Structure 1.3.1 Use Cases 1.3.2 Functions 1.3.3 Interfaces 1.4 Acceptance Test Specification
2 Architecture 2. A hit t 2.1 Criteria 2 X Module Interfaces 2.X 2.T Integration Test Specification
Activities: application domain analysis System definition
Interfaces
and Problem Domain models
Usage
Application Domain
Functions
Model and Software Requirements
Use Case
name
name name
name
Activities: use case analysis System definition
Use cases Evaluate systematically
Analyse work tasks
Str ct re Structure the use cases Find actors and use cases
E Example: l Start tool use
TractorOperator
RowWeeder start_tracking
E h use case is Each i described d ib d textually t t ll and/or by a behaviour diagram
Actor stereotype
start_tracking
TractorOperator
RowWeeder
Functions The actions of actors in use cases: • Update – state change in (internal) model • Signal – event in (internal) model • Read – (internal) model state inspection • Compute – (internal) model state summary Update/ Read/
Compute
System
Signal
Interfaces
Update/
IPanel
Read/ Compute Signal
Alarm
System
Example: User Interface
Example: Camera Interface The camera delivers JPEG compressed images with a frame rate of up to 10 per second. The resolution is ... The hardware interface is a DMA ... The standard software driver is ...
Summary: A li i Domain Application D i Analysis A l i • Use Cases • Functions F ti • Interfaces
Your Report - 3! 1. Requirements Specification 1 1 System 1.1 S t Definition D fi iti 1.2 Problem Domain Structure 1.3 Application Domain Structure 1.3.1 Use Cases 1.3.2 Functions 1.3.3 Interfaces 1.4 Acceptance Test Specification
2 Architecture 2. A hit t 2.1 Criteria 2 X Module Interfaces 2.X 2.T Integration Test Specification
Processes • Method in passive class - called from main • Method in passive class - linked to an Event • Method run in active class – explicit start Specified in UML by Statechart Diagram
Signals and Events • Signals are asynchronous events • A Signal or Event is a Class • A method th d may h have a send d dependency d d on a Signal • A method that recieves a Signal has a use dependency
Sensors, Actuators and Control Architecture for Embedded Systems • Sensors have passive interfaces with event methods • Actuators have passive interfaces with event methods • Control is active and uses sensors and actuators
Your Report - 4! 1. Requirements Specification 2. Architecture 2.1 Criteria 2.X Module Interfaces 2.T Integration Test Specification
3. Modules d l 3.X.1 Module Interface 3 X 2 Module Design 3.X.2 3.X.3 Module Test Specification
