Software Engineering 2 A practical course in software engineering. Ekkart Kindler

Transcription

1 Software Engineering 2 A practical course in software engineering

2 Conclusion, Outlook, Discussion

3 Motivation 3

4 4

5 1. What did you learn? Objectives of this course: Basic skills in software engineering! 5

6 Software Engineering is much more than programming! listening and understanding! analytic and conceptual work! communication! a social process! acquiring new technologies! a discipline with proven concepts, methods, notations, and tools! and ever new technologies emerging! 6

7 Experience Software Engineering requires much experience! This experience can not be taught theoretically! will be provided in this course! tutorial project and (only) backed by the lectures 7

8 Issues How to make useful UML models Domain model OOA Implementation OOD Learn to use new technologies YOURSELF! Eclipse / EMF / GMF / Java3D / 8

9 Issues Get requirements straight Write a systems specification 9

10 Specifying Software Project Definition Requirements Specification rough detailed Systems specification Complete Models Implementation, Documentation Handbook what how 10

11 Specifying Software Project Definition Requirements Specification rough detailed Systems specification Complete Models Implementation, Documentation Handbook rough detailed 11

12 Specifying Software Project Definition Requirements Specification rough detailed Systems specification Complete Models Implementation, Documentation Handbook low cost high cost 12

13 Issues writing, talking, communicating, and organizing yourself work together version management (other/better tools) 13

14 Issues Quality Management Testing Reviews Many practical issues on programming and solving problems 14

15 Issues Integration and extension Integrating features in existing software (PlugIn Mechanisms, ) Developing parts in parallel (based on a common model) Separating concerns Stepwise extension (prototyping, agile) 15

16 Topics Software Specifications (incl. writing) Modelling & Meta modelling Quality mangament (incl. testing) Code generation Working together Management 16

17 2. What did you not learn? 17

18 Technology issues MOF (Meta Object Facility) Software without Programming (EMF and more) / code generation technologies Other technology: other application servers, databases, service technologies Analyse, validate, verify these models, Other programming and modelling paradigms: e.g. Aspect Oriented Modelling... 18

19 Advanced Topics Just to give you some idea

20 Future technologies Modelling dynamic behaviour (and generating code from that) Defining transformations Get completely rid of programming?! 20

21 More details & experience Master courses Requirements Engineering (H.S) Systems integration (H.B.) Web Services (H.B.) Formal methods (A.H.) Advanced topics in SE (E.K./ B.W., f16) Bachelor and master projects (last week / CITIES presentation) 21

22 Coordinating Interactions The Event Coordination Notation

23 From lecture 1: Example 23

24 From lecture 1: Example From this (EMF) model for Petri nets: Generation of (Java) code for all classes methods for changing the Petri net loading and saving the Petri net as XML files ( XMI) PetriNet * Object 1 source Node 1 target Transition Place Arc * Token With this and some more GMF information: Generation of the Java code of a graphical complete editor (with many fancy features). No programming at all. Transition Place Arc Token 24

25 From lecture 1 PetriNet * Object 1 source Node 1 target Transition Place Arc * Token Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: %pluginname package PetriNets.impl; Bundle-SymbolicName: APetriNetEditorIn15Minutes.diagr Bundle-Version: qualifier public class PetriNetImpl extends EObjectImpl implements PetriNet { Bundle-ClassPath:. protected EList<PetriNets.Object> object; Bundle-Activator: PetriNets.diagram.part.PetriNetDiagr Bundle-Vendor: %providername protected PetriNetImpl() { Bundle-Localization: plugin super(); Export-Package: PetriNets.diagram.edit.parts, } PetriNets.diagram.part, PetriNets.diagram.providers protected EClass estaticclass() { Require-Bundle: org.eclipse.core.runtime, return PetriNetsPackage.Literals.PETRI_NET; org.eclipse.core.resources, } org.eclipse.core.expressions, org.eclipse.jface, public EList<PetriNets.Object> getobject() { org.eclipse.ui.ide, if (object == null) { org.eclipse.ui.views, object = new EObjectContainmentEList<PetriNets.Object>(Petri org.eclipse.ui.navigator, } org.eclipse.ui.navigator.resources, return object; org.eclipse.emf.ecore, } org.eclipse.emf.ecore.xmi, org.eclipse.emf.edit.ui, public NotificationChain einverseremove(internaleobject otherend, int org.eclipse.gmf.runtime.emf.core, switch (featureid) { org.eclipse.gmf.runtime.emf.commands.core, case PetriNetsPackage.PETRI_NET OBJECT: org.eclipse.gmf.runtime.emf.ui.properties, return ((InternalEList<?>)getObject()).basicRemove(otherEn org.eclipse.gmf.runtime.diagram.ui, } org.eclipse.gmf.runtime.diagram.ui.properties, return super.einverseremove(otherend, featureid, msgs); org.eclipse.gmf.runtime.diagram.ui.providers, } org.eclipse.gmf.runtime.diagram.ui.providers.ide, org.eclipse.gmf.runtime.diagram.ui.render, public Object eget(int featureid, boolean resolve, boolean coretype) { org.eclipse.gmf.runtime.diagram.ui.resources.ed switch (featureid) { org.eclipse.gmf.runtime.diagram.ui.resources.e case PetriNetsPackage.PETRI_NET OBJECT: APetriNetEditorIn15Minutes;visibility:=reexpor return getobject(); } return super.eget(featureid, resolve, coretype); Analysis Design Implementation Coding 25

26 e.g. a Petri net simulator? 26

27 2. The Event Coordination Notation Motivation Given some object oriented software with (or without) explicit domain model Model behaviour on top of it and make these models executable Model behaviour on a high level of abstraction (domain): coordination of behaviour Integrate behaviour models with structural models Integrate different structural models and manually written code (or code generated by different technologies) 27

28 2.1 Example: Vending machine Coin * * Slot Brewer Safe 1 * Control * * Output Panel * Coffee Tea 28

29 Instance: Object Diagram :Coin :Coin : Slot :Coffee :Coin : Safe :Control :Coffee :Output :Panel :Tea 29

30 Coordination Diagram GUI Coin insert GUI pass return_ Safe pass return_: ALL pass: 1 * * insert: 1 1 pass: 1 Slot insert return_ pass reset Panel GUI coffee GUI tea GUI cancel GUI reset: ALL pass: 1 * * coffee: 1 tea: 1 cancel: ALL Control coffee tea cancel pass reset coffee: 1 tea: 1 reset: ALL * Coffee Brewer coffee tea reset cup_in cup_in: 1 * Tea Output GUI cup_in GUI cup_out GUI 30

31 ... + Event declaration GUI Coin insert GUI pass return_ Safe pass return_: ALL pass: 1 * * insert: 1 1 pass: 1 Slot insert return_ pass reset Panel GUI coffee GUI tea GUI cancel GUI reset: ALL pass: 1 * * coffee: 1 tea: 1 cancel: ALL Control coffee tea cancel pass reset insert(coin coin, Slot slot) pass(coin coin, Slot slot) return(slot slot) reset_() coffee: 1 tea: 1 reset: ALL * Coffee Brewer coffee tea reset cup_in cup_in: 1 * Tea coffee() tea() cancel() cup_in() cup_out() Output GUI cup_in GUI cup_out GUI 31

32 Interactions :Coin :Coin :Coin pass : Safe pass pass: 1 pass: 1 : Slot pass :Panel coffee pass: 1 coffee: 1 :Control pass coffee coffee: 1 coffee: 1 :Coffee :Coffee coffee :Tea :Output 32

33 Interactions :Coin :Coin :Coin pass : Safe pass pass: 1 pass: 1 : Slot pass :Panel coffee pass: 1 coffee: 1 :Control pass coffee coffee: 1 :Coffee :Coffee coffee :Tea :Output 33

34 Another Interaction :Coin return :Coin :Coin return : Safe return: ALL return: ALL : Slot return reset :Panel cancel reset: ALL cancel: ALL :Control reset cancel reset: ALL reset: ALL reset: ALL :Coffee reset :Coffee reset :Tea reset :Output 34

35 Local behaviour: Coffee 35

36 Local behaviour: Coin 36

37 Local behaviour: Control pass coffee reset cancel 37

38 Local behaviour: Slot return reset 38

39 Interactions :Coin return :Coin :Coin return : Safe return: ALL return: ALL : Slot return reset :Panel cancel reset: ALL cancel: ALL :Control reset cancel reset: ALL reset: ALL reset: ALL :Coffee reset :Coffee reset :Tea reset :Output 39

40 2.2 ECNO: Basic Concepts ElementTypes (Classes) EventTypes with parameters insert(coin coin, Slot slot) Global Behaviour: Coordination annotations for references Event type Quantification (1 or ALL) Local behaviour: ECNO nets (or something else) Event binding (with parameter assignment) Condition Action Control coffee tea cancel pass reset coffee: 1 tea: 1 Brewer reset: ALL coffee tea reset cup_in 40

41 2.3 Extensions ECNO with its basic concepts has some limitations, which makes modelling things in an adequate way a bit painful. Sometimes, we want to extend event types later 41

42 Event Extension tea tea_blend tea_temp 42

43 2.4 Example2: Petri nets t remove add Transition t enabled: for ALL incoming Arcs a: for ONE source Place p of Arc a: find a token Fire Transition t: for ALL incoming Arcs a: for ONE source Place p of Arc a: find a token and remove it for ALL outgoing arcs a: for ONE target Place p of Arc a: add a new Token 43

44 Petri net: Abstract Syntax 44

45 Example2: Petri nets t remove add Transition t enabled: for ALL incoming Arcs a: for ONE source Place p of Arc a: find a token Fire Transition t: for ALL incoming Arcs a: for ONE source Place p of Arc a: find a token and remove it for ALL outgoing arcs a: for ONE target Place p of Arc a: add a new Token 45

46 ECNO Semantics of PN 46

47 Result t4 t1 t3 t2 47

48 Petri net simulator 48

49 3. Conclusion 49

50 Next Steps 50

51 Example: Moving Shuttles Track at occupied Shuttle Simple succ pred 51

52 An Instance :Simple pred succ t1:simple at occ s:shuttle pred succ t2:simple pred succ :Simple 52

53 Behaviour :Simple pred before <<delete>> succ t1:simple at occ s:shuttle pred occ succ at t2:simple pred succ :Simple after <<create>> 53

54 Behaviour as Story Pattern t1:simple pred succ at occ at <<delete>> occ s:shuttle t2:simple at occ :Shuttle 54