Software Engineering: Models

Software Engineering: Models David Millard (dem@ecs.soton.ac.uk)

Overview Definitions of Modeling UML Use Case Diagrams (recap) A Modeling Problem UML Activity Models What are they? How do you create them? When do you use them?

Definitions Modeling (n) “ A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.” Wikipedia "Modeling has been an essential part of engineering, art and construction for centuries. Complex software designs that would be difficult for you to describe textually can readily be conveyed through diagrams. Modeling provides three key benefits: visualization, complexity management and clear communication.” IBM “ Some development managers wonder why modeling is important at all. After all, the code should speak for itself… Why add an extra layer of abstraction that we have to maintain as the project progresses? The reason is that there are a number of clear benefits that models provide a development organization. They are enhanced communication, better planning, reduced risk, and reduced costs” Software Modeling Introduction – Borland White Paper

Definitions Modeling (n) “ A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.” Wikipedia "Modeling has been an essential part of engineering, art and construction for centuries. Complex software designs that would be difficult for you to describe textually can readily be conveyed through diagrams . Modeling provides three key benefits: visualization, complexity management and clear communication.” IBM “ Some development managers wonder why modeling is important at all. After all, the code should speak for itself… Why add an extra layer of abstraction that we have to maintain as the project progresses? The reason is that there are a number of clear benefits that models provide a development organization. They are enhanced communication, better planning, reduced risk, and reduced costs” Software Modeling Introduction – Borland White Paper

Definitions Modeling (n) “ A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.” Wikipedia "Modeling has been an essential part of engineering, art and construction for centuries. Complex software designs that would be difficult for you to describe textually can readily be conveyed through diagrams . Modeling provides three key benefits: visualization, complexity management and clear communication.” IBM “ Some development managers wonder why modeling is important at all. After all, the code should speak for itself … Why add an extra layer of abstraction that we have to maintain as the project progresses? The reason is that there are a number of clear benefits that models provide a development organization. They are enhanced communication, better planning, reduced risk, and reduced costs” Software Modeling Introduction – Borland White Paper

Definitions Modeling (n) “ A modeling language is any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules. The rules are used for interpretation of the meaning of components in the structure.” Wikipedia "Modeling has been an essential part of engineering, art and construction for centuries. Complex software designs that would be difficult for you to describe textually can readily be conveyed through diagrams . Modeling provides three key benefits: visualization, complexity management and clear communication .” IBM “ Some development managers wonder why modeling is important at all. After all, the code should speak for itself … Why add an extra layer of abstraction that we have to maintain as the project progresses? The reason is that there are a number of clear benefits that models provide a development organization. They are enhanced communication , better planning, reduced risk, and reduced costs” Software Modeling Introduction – Borland White Paper

Unified Modeling Language UML - Unified Modelling Language - 3 creators: Grady Booch, Ivar Jacobson and James Rumbaugh started in early 1990’s A visual language for developing software systems

UML Use Cases to capture requirements Use cases model What the system should do Who uses (benefits from) the system From the user’s point of view

…but how to capture behaviour?

…but how to capture behaviour? Inside the box!

Problem With a partner draw a diagram to capture the following process (as if you were graphically describing it): “ You’re dozing in bed, waiting for your alarm. When it goes off you get up, get dressed and go downstairs. You make some breakfast and eat it while reading the morning paper. When you finish you leave the house.”

Look at Your Diagram What were the features of your diagram? Actions or Events …

Look at Your Diagram What were the features of your diagram? Actions or Events Sequence Parallel A Start and Stop Decisions Logical Partitions?

UML Activity Diagrams UML Equivalent of a FlowChart Provides a high level view of what’s going on inside a Use Case (Is a variation of a UML State Diagram)

UML Activity Diagrams Is based on: Activities Linked with Transitions With one Start and one Stop Get Up Get Dressed Start Transition Stop Activity Activity

UML Activity Diagrams Doze Alarm gone off? Get Up [Yes] [No] Decisions points (branches) are written as diamonds A Branch has an optional description Transitions out of a branch are labeled (guard conditions) Branch Guard Conditions

UML Activity Diagrams Bars (Forks and Joins) Used to show that things happen in parallel Or to bring together several transitions Make Breakfast Leave House Eat Breakfast Read Paper Fork Join

Putting it All Together Make Breakfast Leave House Eat Breakfast Read Paper Doze Alarm gone off? Get Dressed [Yes] [No] Go Downstairs Get Up

Adding Swimlanes Make Breakfast Leave House Eat Breakfast Read Paper Doze Alarm gone off? [Yes] [No] Go Downstairs Upstairs Downstairs Get Dressed Get Up

Adding Swimlanes Swimlanes partition a diagram Used to show different logical areas Diagrams can often be partitioned in different ways According to a Phase According to the Actor According to Department There is no right way Partition in whatever is the most useful way

When to use Activity Diagrams?

When to use Activity Diagrams? When analysing a use case What actions are there and when do they happen? This is sometimes called Workflow Useful for communicating order and dependency But they do not show Interactions, Data or State Other UML diagrams for this!

Summary Modeling is An abstract representation… … of some complex knowledge or design… … to help communicate it UML Use Cases model requirements from the user view UML Activity Diagrams model workflow from the system view Formal version of flowcharts Activity Diagrams include: Branching (decision making) Forks and Join (parallel activities) Swimlanes (logical partitioning)

Software Engineering: Models

More Related Content

What's hot (20)

Similar to Software Engineering: Models (20)

More from David Millard (10)

Recently uploaded (20)

Software Engineering: Models