© Gunnar Wettergren1 IV1021 Project models Gunnar Wettergren

En presentation över ämnet: "© Gunnar Wettergren1 IV1021 Project models Gunnar Wettergren"— Presentationens avskrift:

1 © Gunnar Wettergren1 IV1021 Project models Gunnar Wettergren gunnarw@dsv.su.se

2 © Gunnar Wettergren2 Skapa en arbetsplan För att kunna göra detta måste vi: Bryta ner arbetet Uppskatta resursbehov Tid Personalkostnader HW/SW

3 © Gunnar Wettergren3 WBS – Work breakdown structure (identifiera aktiviteter) Den primärar anledningen till en WBS är att säkerställa att alla aktiviteter är identifierade och planerade Dela upp aktiviteter i mindre delar kan göras av projektmedlemmar Använd ett nivå system, nivå1, 2 etc.

4 © Gunnar Wettergren4 Example of WBS

5 © Gunnar Wettergren5 Uppskattningsmetoder Algoritmer Experter Analogier Top-down Bottom-up

6 © Gunnar Wettergren6 Exempel

7 © Gunnar Wettergren7 Two basic approaches Sequential models (Old) Start with a goal and the the PM’s job is to guide the project towards that goal Ex. Waterfall model Iterative models (New) Based on the reasoning that iterations with high customer involvement is beneficial and necessary for project success Ex. RAD, Prince, Prince2

8 © Gunnar Wettergren8 Problems with the old Created when there was chaos, discipline was the most important factor Requires a stable environment Inflexible and slow Based on an engineering thinking

9 © Gunnar Wettergren9 The new situation We have shorter time to develop systems in Turbulent ever changing environment Complex systems The customer must be involved to succeed Distributed environments Global marketplace

10 © Gunnar Wettergren10 Sequential models

11 © Gunnar Wettergren11 Definition of sequential models Step by step approach Usually document controlled Follows the engineering approach of divide and conquer Needs a fixed goal

12 © Gunnar Wettergren12 Waterfall model Is it feasible? Design Requirements Integration and system test Delivery Code and test The back arrows are an extension to the original waterfall model

13 © Gunnar Wettergren13 Problems with the waterfall model Problems discovered late in the project life cycle Requirements must be fixed at design start Often flaws in design and code Performance cannot be tested until at the end of the project

14 © Gunnar Wettergren14 Iterative models

15 © Gunnar Wettergren15 Prototyping What is it? Purpose? Why use prototypes? Benefits to the PM and the project

16 © Gunnar Wettergren16 Spiral model

17 Scrum - Roles Roles Product owner Scrum master Team © 2006 Gunnar Wettergren17

18 Scrum – Important concepts Product backlog – All requirements. Here we prioritize what is more important. The higher prio the more details Sprint backlog – Functionality to be implemented in sprint © 2006 Gunnar Wettergren18

19 Scrum – The sprint © 2006 Gunnar Wettergren19 Sprint planning 1 day Change walkthrough Planning the same way as any project Sprint Daily scrums What have I done since yesterday? What will I do? What is stopping me? Sprint review Demo Comments Changes

20 © Gunnar Wettergren20 UML – Unified Modeling Language

21 © Gunnar Wettergren21 Background Developed in 1993 by Rational Close connection to OO development Its strengths are: Good complement to high level languages All aspects of systems development can be expressed using UML Easy to learn since the model itself is based on OO

22 © Gunnar Wettergren22 UML Example (Use Cases)

23 © Gunnar Wettergren23 UML Example (class model)

24 © Gunnar Wettergren24 UML Example (Sequence diagram)

25 © Gunnar Wettergren25 UML Example (Implementation)

26 © Gunnar Wettergren26 Questions ??