Introduction to the course Jerzy Nawrocki [email protected] Requirements Eng. & Project...

Introduction to the course

Jerzy [email protected]

Requirements Eng. & Project Manag.

Introduction to XPrince (2)


Aim of the course

Prepare the students to the role of Analyst and Project Manager



Context of the course

Requirements Engineering and

Project Management

Software Development

Studio



Outline of the schedule

March Lectures + labs on RE&PMApril Lectures + labs on RE&PM

Project Startup Presentation for 3rd year

May 3r year team selects projectsProject Initiation



Announcement

From dr Adam Wojciechowski:

Software Development Studio will start in the end of March – you will be informed later



Lectures

Date Time No. Title26.02 15:10 1 Introduction to the Course28.02 13:30 2 The Start-up Stage06.03 13:30 3 Functional Requirements (adv.)13.03 13:30 4 Non-functional Requirements20.03 13:30 5 The Project Initiation Stage27.03 13:30 6 The Architecture Elaboration Stage03.04 13:30 7 Soft Skills10.04 13:30 8 Release and Risk Management17.04 13:30 9 Mission-Critical Systems24.04 13:30 10 Project Closing and Course Summary



Rules

Load of the course: 20 lectures, 20 labs, 20 projects; 5 ECTS

Presence:Lectures – optionalLabs – obligatory

Grading rules:Labs: Running evaluationProject: Evaluation of the presentation + PIDNo exam



Rules

Consultation hours:J.Nawrocki: Tue (every 2nd), 11:15 – 12:00, room 109www.cs.put.poznan.pl/jnawrocki/require [email protected]

Estimated effort (hours): 20 lectures 10 running repetitions 50 literature 20 labs 10 preparation for labs 40 preparation for project150 TOTAL

Consultation hours:J.Nawrocki: Tue (every 2nd), 11:15 – 12:00, room 109www.cs.put.poznan.pl/jnawrocki/require [email protected]

Estimated effort (hours): 20 lectures 10 running repetitions 50 literature 20 labs 10 preparation for labs 40 preparation for project150 TOTAL

http://www.cs.put.poznan.pl/jnawrocki/require

mailto:[email protected]









http://www.cs.put.poznan.pl/jnawrocki/require










Introduction to

Jerzy [email protected]




Laboratory of Software EngineeringInstitute of Computing Sci.Poznan University of Technology

Master Degree Programme in Software Engineering

Consortium XPrince



Aim of the lecture

Outline the XPrince methodology.



Aim of the lecture

Outline the XPrince methodology.



Agenda

• XPrince – What for?• Team• Lifecycle• Final remarks



Agenda




XPrince – What for?



Software crisis

• Late delivery• Over budget• Overtime• Poor quality



Discipline-based approaches

More discipline!

Requirem.

Design

Code

Tests

ISO 9000

IEEE Std

IEEE Std

IEEE Std

1

2

3

4

5



PRINCE2

PRINCE = PRojects IN Controlled Environments

CCTA = the Central Computer and Telecommunications Agency, UK

1989: CCTA introduces PRINCE

1996: CCTA announces PRINCE2



PRINCE2

Project management methodology

Main actor: Project Manager

http://www.ccta.gov.uk/prince/

Managing Successful Projectswith PRINCE2





Complaints

Too much paper work! Too many

meetings!



Changes in requirements

CustomerCustomer

Let’s change requirements.

Developers

OK. OK. OK. OK.



Formal approach to changes

Change order

Err

End-user Configuration Manager

Change order

Developer

Report

Configuration Management Board

Decision

Change order

Project Manager







Extreme Programming (XP)

Tom DeMarcoTom DeMarco

"XP is the most import

movement in our field today."

lightweight (agile) methodology of software development



XP the Saviour

• Oral communication.• Artefacts: code + test cases• IEEE/ANSI standard 830/1993?

Needless!• Fagana inspections? Needless!• Function points? Needless!• No overtime!

I always said that!



Weaknesses

Discipline (Celebrity)

Agility (XP)

• Too much paperwork

• Slow decision process

• Resistance against change

• Assuming „on-site customer”

• Lack of written documentation

• Too short planning perspective



Solution

Addison-Wesley, 2004.

„every successful venture in a changing world requires both agility and discipline”



XPrince

eXtreme Programmingin controlled environments

XPrince Sources

XP

PRINCE 2 Rational Unified Process



Agenda




XP Team

Customer

Coach

Tracker

Tester

Developers



Management Team in PRINCE2

Project Board

Senior User Executive Senior Supplier




Project Manager

Report

Plan

Project Board





Project Manager

Project AssuranceReport

Plan

Project Board




Roles in RUP

Project Manager

Tester

Developer

Analyst

Architect



XPXP

Prince2Prince2

XPrince Team

Kierownik ZespołuKierownik ZespołuDevelopers

Analyst Architect

Project Board

Senior User Executive Główny dostawca

Manager (Coach, Tracker)

(Coach)(Cust., Tester)



Small but difficult project

Jurek – Senior user + Executive

Ewa – Project Manager + Analyst

Mirek – Architect (natural language processing)Łukasz – Architect (IBM Eclipse and Java)

Honoriusz – Developer Pankracy – Developer



Key roles in XPrince

Project ManagerAnalyst Architect



Team

Fred BrooksOS/360, IBM

Administrator

Secretary

Second pilot

Documentalist

Tools expert

Tester

Language expert

Editor

Secretary

Surgeon



Agenda




Release 2Release 1

XP Lifecycle

Increment 1.1 Increment 1.2 Increment 2.1 Increment 2.2



PRINCE2 Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 1.07

Starting up a Project

Initiating a Project

Stage 1 Stage 2 Stage 3 Stage 4 Closing a

Project



RUP Phases

Inception Elaboration Construction TransitionTransition



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07

Startup Initiation Elaboration

Release 1 Release 2 Release 3 Closing



Main outcomes of Startup

Startup

Project sponsor (customer)ProblemOutline of the solutionInterfaces (system’s environment)Preferred approach . . .



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07





Main outcomes of Initiation

Initiation

Business Process ReengineeringNon-functional requirementsRoles (Actors) Outline of functional requirementsOutline of the architecture. . .



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07





Main outcomes of Elaboration

Elaboration

Most difficult and important use casesArchitectural approaches (mechanisms)Description of crucial elements (protocols, database desing etc.)Code pieces (examplary solutions)



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07





XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07



Increment

1

Increment

1

Increment

1

Increment

2

Increment

2

Increment

2

TransitionTransition TransitionTransition TransitionTransition



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07



Req.

Arch.

Code



Agenda




Agility Alliance Manifesto

Individuals and interactions



7 Habits of Higly Effective People

Dr Stephen Covey 15 mln sold, 32 languages



Principles of Effectiveness

Be proactiveBe proactive Begin with the end in mindBegin with the end in mind

Put first things firsPut first things firs

Think win/winThink win/win

Seek first to understand ...Seek first to understand ...

SynergizeSynergize

Sharpen the sawSharpen the saw




O KO K

Working software




Cost of Requirements Defects

Cost of Error Correction

0

20

40

60

80

100

120

Req. Design Code Dev.Tst Sys.Tst Field Op.

Development Phase

Re

lati

ve

Co

st

Roger S. Pressman

13-6

times

10 times

15-40 times

30-70 times

40-1000 times



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07



Increment

1

Increment

1

Increment

1

Increment

2

Increment

2

Increment

2





O KO K

Working software


Customer collaboration



Natural languageUpdating the dataUpdating the data

ActorActor: MemberGoalGoal: Update personal data.Main scenarioMain scenario1. Member enters his account and password.2. System presents the personal web page.3. Member selects the update option.4. System presents the personal data ready for update.5. Member changes the data.6. System asks for acknowledgement.7. Member confirms the changes. ExtensionsExtensions1a. Account or password is incorrect. 1a1. System presents a message and returns to Step 1.




O KO K

Working software


Customer collaboration Responding to change

Tommorow or never!



XPrince Lifecycle

16.10 27.11 23.01 8.04 27.05 17.06 8.07



Increment

1

Increment

1

Increment

1

Increment

2

Increment

2

Increment

2




Thank you for your attentionThank you for your attention!!

Date post:	02-Apr-2015
Category:	Documents
Upload:	jaylene-major
View:	222 times
Download:	0 times

Introduction to the course Jerzy Nawrocki [email protected] Requirements Eng. & Project...

Documents