1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.

Slides:



Advertisements
Similar presentations
Project management.
Advertisements

Objectives To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Software Engineering COMP 201
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
SWE Introduction to Software Engineering
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Project.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 COMP201 Project Management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4 Project Management “…a huge topic.” See Part 6, “Management”, Chaps.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
7M701 1 Software Engineering Project Management Sommerville, Ian (2001) Software Engineering, 6 th edition Ch. 4
Creator: ACSession No: 10 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringDecember 2005 Project Management CSE300 Advanced Software Engineering.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects l.
Project Management Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4 Project Management.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
贾银山 Software Engineering, Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering. Chapter 5 Slide 1 Chapter 5 Project Management “…a huge topic.” See Part 6, “Managing People”.
©Ian Sommerville 2006Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 5 Slide 1 Chapter 5 Project Management Modified by Randy K. Smith.
 Probably the most time-consuming project management activity.  Continuous activity - Plans must be regularly revised.  Various different types of.
Project management DeSiaMore 1.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Concerned with activities involved in ensuring that software is delivered: on.
Lecture 3 Project Management (The Classical Approach) CSC301-Winter 2011 Hesam C. Esfahani
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 Chapter 5 Project management. 2 Project management : Is Organizing, planning and scheduling software projects.
Software Project Management
Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
CSEM01 - wk8 - Software Planning1 Software Planning CSEM01 SE Evolution & Management Anne Comer Helen Edwards.
Project management.  To explain the main tasks undertaken by project managers  To introduce software project management and to describe its distinctive.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
COOP Seminar – Fall 2008 Slide 1 HOUSTON COMMUNITY COLLEGE SYSTEM SAIGONTECH SAIGON INSTITUTE OF TECHNOLOGY Software Project Management.
Project Management Yonsei University 2 nd Semester, 2012 Sanghyun Park.
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Software Engineering, 8th edition. Chapter 5 1 Courtesy: ©Ian Sommerville 2006 Oct 13 th, 2008 Lecture # 6 Project management.
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
CSC480 Software Engineering Lecture 5 September 9, 2002.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
Chap 4. Project Management - Organising, planning and scheduling
©Ian Sommerville 2000Software Engineering. Chapter 5 Slide 1 Chapter 5 Project Management “…a huge topic.” See Part 6, “Managing People”.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Project management l Organising, planning and scheduling software projects.
©Ian Sommerville 2000Software Engineering. Chapter 5 Slide 1 Chapter 5 Project Management “…a huge topic.” See Part 6, “Managing People”.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Project management 1/30/2016ICS 413 – Software Engineering1.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 4 Slide 1 Chapter 4: Project management l Organising, planning and scheduling software.
Project management (2) By: Zhou Chunlin School of Tourism, Conference and Exhibitions Henan University of Economics and Law.
Project management. Software project management ■It is the discipline of planning, organizing and managing resources to bring about the successful completion.
Chapter 3 Project Management Parts of this presentation is extracted from Ian Sommerville’s slides located at
1 Project management Organising, planning and scheduling software projects.
Project management Chapter 5. Objectives To explain the main tasks undertaken by project managers To introduce software project management and to describe.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
COMP201 Project Management.
Assistant Professor of Computer Science Washington State University
IS301 – Software Engineering V:
Software Project Management
Project management.
Software Project Management
Project management Lecture 9
Presentation transcript:

1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering & Technology Taxila,Pakistan

2 Today’s Class Project management (Ch 05) Today’s Class Project management (Ch 05)

3 Objectives To explain the main tasks undertaken by project managers To explain the main tasks undertaken by project managers To introduce software project management and to describe its distinctive characteristics To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process To discuss project planning and the planning process To show how graphical schedule representations are used by project management To show how graphical schedule representations are used by project management To discuss the notion of risks and the risk management process To discuss the notion of risks and the risk management process

4 Topics covered Management activities Management activities Project planning Project planning Project scheduling Project scheduling Risk management Risk management

5 What is Project Management?

6

7 Software project management Concerned with activities involved in ensuring that software is delivered on time and on schedule and in accordance with the requirements of the organisations developing the software Concerned with activities involved in ensuring that software is delivered on time and on schedule and in accordance with the requirements of the organisations developing the software Project management is needed because software development is always subject to budget and schedule constraints that are set by the organisation developing the software. Project management is needed because software development is always subject to budget and schedule constraints that are set by the organisation developing the software.

8 Project Management & Product Delivery

9 Software management distinctions The product is intangible. The product is intangible. The product is uniquely flexible. The product is uniquely flexible. Software engineering is not recognized as an engineering discipline with the same status as mechanical, electrical engineering, etc. Software engineering is not recognized as an engineering discipline with the same status as mechanical, electrical engineering, etc. The software development process is not standardised. The software development process is not standardised.

10 Management activities Proposal writing. Proposal writing. Project planning and scheduling. Project planning and scheduling. Project costing. Project costing. Project monitoring and reviews. Project monitoring and reviews. Personnel selection and evaluation. Personnel selection and evaluation. Report writing and presentations. Report writing and presentations.

11

12 Project staffing May not be possible to appoint the ideal people to work on a project May not be possible to appoint the ideal people to work on a project Project budget may not allow for the use of highly- paid staff. Project budget may not allow for the use of highly- paid staff. Staff with the appropriate experience may not be available. Staff with the appropriate experience may not be available. An organisation may wish to develop employee skills on a software project. An organisation may wish to develop employee skills on a software project. Managers have to work within these constraints especially when there are shortages of trained staff.ppo Managers have to work within these constraints especially when there are shortages of trained staff.ppoppo

13

14 Activity organization Activities in a project should be organised to produce tangible outputs for management to judge progress. Activities in a project should be organised to produce tangible outputs for management to judge progress. Milestones are the end-point of a process activity. Milestones are the end-point of a process activity. Deliverables are project results delivered to customers. Deliverables are project results delivered to customers. The waterfall process allows for the straightforward definition of progress milestones. The waterfall process allows for the straightforward definition of progress milestones.

15 Process to get Milestones

16 Project scheduling Split project into tasks and estimate time and resources required to complete each task. Split project into tasks and estimate time and resources required to complete each task. Organize tasks concurrently to make optimal use of workforce. Organize tasks concurrently to make optimal use of workforce. Minimize task dependencies to avoid delays caused by one task waiting for another to complete. Minimize task dependencies to avoid delays caused by one task waiting for another to complete. Dependent on project managers intuition and experience. Dependent on project managers intuition and experience.

17 Scheduling problems Estimating the difficulty of problems and hence the cost of developing a solution is hard. Estimating the difficulty of problems and hence the cost of developing a solution is hard. Productivity is not proportional to the number of people working on a task. Productivity is not proportional to the number of people working on a task. Adding people to a late project makes it later because of communication overheads. Adding people to a late project makes it later because of communication overheads.

18 Summary

19 Bar charts and activity networks Graphical notations used to illustrate the project schedule. Graphical notations used to illustrate the project schedule. Show project breakdown into tasks. Tasks should not be too small. They should take about a week or two. Show project breakdown into tasks. Tasks should not be too small. They should take about a week or two. Activity charts show task dependencies and the the critical path. Activity charts show task dependencies and the the critical path. Bar charts show schedule against calendar time. Bar charts show schedule against calendar time.

20

21 Task durations and dependencies

22

23 Activity network

24 Activity timeline

25 Staff allocation

26

27 Risk management Risk management is concerned with identifying risks and drawing up plans to minimise their effect on a project. Risk management is concerned with identifying risks and drawing up plans to minimise their effect on a project. A risk is a probability that some adverse circumstance will occur A risk is a probability that some adverse circumstance will occur Project risks affect schedule or resources Project risks affect schedule or resources Product risks affect the quality or performance of the software being developed Product risks affect the quality or performance of the software being developed Business risks affect the organisation developing the software Business risks affect the organisation developing the software

28 Software risks

29 Type of Risk Current Risks Current Risks Emerging Risks Emerging Risks Future Risks Future Risks

30

31 The risk management process Risk identification Risk identification Identify project, product and business risks Identify project, product and business risks Risk analysis Risk analysis Assess the likelihood and consequences of these risks Assess the likelihood and consequences of these risks Risk planning Risk planning Draw up plans to avoid or minimise the effects of the risk Draw up plans to avoid or minimise the effects of the risk Risk monitoring Risk monitoring Monitor the risks throughout the project Monitor the risks throughout the project

32 The risk management process

33 Risk identification Technology risks Technology risks People risks People risks Organisational risks Organisational risks Requirements risks Requirements risks Estimation risks Estimation risks

34 Risks and risk types

35 Risk analysis Assess probability and seriousness of each risk. Assess probability and seriousness of each risk. Probability may be very low, low, moderate, high or very high. Probability may be very low, low, moderate, high or very high. Risk effects might be serious, tolerable or insignificant. Risk effects might be serious, tolerable or insignificant.

36

37 Risk planning Consider each risk and develop a strategy to manage that risk. Consider each risk and develop a strategy to manage that risk. Avoidance strategies Avoidance strategies The probability that the risk will arise is reduced; The probability that the risk will arise is reduced; Minimisation strategies Minimisation strategies The impact of the risk on the project or product will be reduced; The impact of the risk on the project or product will be reduced; Contingency plans Contingency plans If the risk arises, contingency plans are plans to deal with that risk; If the risk arises, contingency plans are plans to deal with that risk;

38 Risk monitoring Assess each identified risks regularly to decide whether or not it is becoming less or more probable. Assess each identified risks regularly to decide whether or not it is becoming less or more probable. Also assess whether the effects of the risk have changed. Also assess whether the effects of the risk have changed. Each key risk should be discussed at management progress meetings. Each key risk should be discussed at management progress meetings.

39 Key points Good project management is essential for project success. Good project management is essential for project success. The intangible nature of software causes problems for management. The intangible nature of software causes problems for management. Managers have diverse roles but their most significant activities are planning, estimating and scheduling. Managers have diverse roles but their most significant activities are planning, estimating and scheduling. Planning and estimating are iterative processes which continue throughout the course of a project. Planning and estimating are iterative processes which continue throughout the course of a project.

40 Key points A project milestone is a predictable state where a formal report of progress is presented to management. A project milestone is a predictable state where a formal report of progress is presented to management. Project scheduling involves preparing various graphical representations showing project activities, their durations and staffing. Project scheduling involves preparing various graphical representations showing project activities, their durations and staffing. Risk management is concerned with identifying risks which may affect the project and planning to ensure that these risks do not develop into major threats. Risk management is concerned with identifying risks which may affect the project and planning to ensure that these risks do not develop into major threats.

41 Question & Review session For any query feel free to contact