1. Software Engineering Lecture 2 ASPI8-4 Anders P. Ravn, Feb. 2004

2. Your Report - 2! 1.Requirements Specification 1.1 System Definition 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.1 Criteria 2.X Module Interfaces 2.T Integration Test Specification

3. Overview Software Requirements OAD in Application Domain Analysis Architecture for Embedded Systems 1.Usage 2.Functions 3.Interfaces

4. Activities: application domain analysis Usage Functions System definition and Problem Domain models Interfaces Application Domain Model and Software Requirements

5. Use Case name > name > name > name

6. Activities: use case analysis Find actors and use cases Analyse work tasks System definition Use cases Evaluate systematically Structure the use cases

7. Example: Start tool use start_tracking > TractorOperator > RowWeeder Each use case is described textually and/or by a behaviour diagram

8. Actor stereotype start_tracking > RowWeeder TractorOperator

9. 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 Signal > System

10. Interfaces System > Alarm IPanel Update/ Read/ Compute Signal

11. Example: User Interface

12. 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...

13. Summary: Application Domain Analysis Use Cases Functions Interfaces

14. Your Report - 3! 1.Requirements Specification 1.1 System Definition 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.1 Criteria 2.X Module Interfaces 2.T Integration Test Specification

15. Design criteria Usable Secure Efficient Correct Reliable Maintainable Testable Flexible Comprehensible Reusable Portable Interoperable

16. Architecture

17. Interface Class and Dependency IRow SegmentationPositionUpdate use > IRow use realise

18. Package related classes name

19. Active Class name

20. 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

21. Signals and Events Signals are asynchronous events A Signal or Event is a Class A method may have a send dependency on a Signal A method that recieves a Signal has a use dependency

22. 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

23. Your Report - 4! 1.Requirements Specification 2. Architecture 2.1 Criteria 2.X Module Interfaces 2.T Integration Test Specification 3.Modules 3.X.1 Module Interface 3.X.2 Module Design 3.X.3 Module Test Specification 4.Implementation 5.Test