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

3. Overview The development process Documents OAD in Requirements Analysis 1.Problem Domain Analysis 2.System Definition 3.Class, Association, Dependency 4.Behaviour, Event

4. The project mainstays Journal – Agendas, Minutes, Notes Report – Work Items Schedule – Milestones, Activities

5. Organization - Players Customer – has the problem and has to be satisfied with the solution Project Team – works to find a solution Boss – defines the resources and monitors progress Consultant – contributes ideas and expertise

6. Team - roles Designer – develops solutions Integrator (tester) – ensures consistent releases Developer – develops components Documenter – ensures documentation Organizer (planner) – keeps orderly progress

7. Planning – why bother? Customer expectations Project progress The solution space

8. Planning – why! To be able to act rationally when – forseeable - events happen. Livet forstås baglæns, men må leves forlæns Søren Kierkegaard

9. Planning – how? Time Activity Deadline Milestone

10. Gant Chart Activity A B C …

11. Pert Diagram A 14 B 7 C 10 D 13 F 7 E 14 G 5 H 6 I 24

12. Status WP1

13. Literature (incomplete) Fred. P. Brooks: The Mythical Man-month G. Weinberg: The Psychology of Programming N.E. Andersen, et al.: Professionel Systemudvikling H. Mills: Chief Programmer Teams D. Gibbs: Extreme Programming

14. A Development Process (V-model) Requirements Spec --------------------------- Accpt. Test Report Acceptance Test Spec Architectural Spec ------------------------ Integr. Test Report Integration Test Spec Module Interface Spec Module Spec ------------------- Module Test Report Module Test Spec Program Source text A rational Design Process – or how to fake it Heninger & Parnas, 1979

15. Your Report! 1.Requirements Specification 1.1 System Definition 1.2 Problem Domain Structure 1.3 Application Domain Structure 1.4 Acceptance Test Specification 2.Architecture 3.Modules 4.Implementation 5. Test

16. Example: Computer Vison based implement guidance in row crops A rich picture

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

18. Example:The prototype software

19. FACTOR A concise description of a computerized system expressed in natural language FACTOR: Functionality for end use Application Domain of end use Conditions for success Technology to be used Object System Realization conditions

20. Example: FACTOR A computer system which guides an implement through crops in rows. (Application 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).

21. Problem Domain Description Class Diagrams (things and their relations) Selected Behaviours (events and their sequence) Notes - text (interpretation of concepts )

22. Example: Problem Domain Structure

23. Example: Tractor Behaviour Outside row In row ManualAuto start stop

24. Example: Interaction of Tractor and Row Weeder :Tractor:RowWeeder lower engage no_row

25. Summary: Problem Domain Analysis Rich Picture System definition - FACTOR Structure - Class Diagrams Behaviour - Statechart Diagrams Interaction - Sequence Diagrams Notes

26. Your Report - 1! 1.Requirements Specification 1.1 System Definition 1.2 Problem Domain Structure 1.3 Application Domain Structure 1.4 Acceptance Test Specification 2.Architecture 3.Modules 4.Implementation 5. Test

27. UML Notation Class Object Association Dependency Package

28. Class and Object Class name attributes methods Object: Class name 1* Association

29. Superclass Generalization Subclass

30. Aggregation the whole the part [arity]

31. Association [name] [arity]

32. Dependency ”uses”

33. Package (cluster) related classes > name

34. Summary: Diagrams Class and Object Generalization Aggregation Association Dependency Package Statechart DiagramStatechart Diagram Sequence DiagramSequence Diagram