Software engineering Lecture 21.

Slides:



Advertisements
Similar presentations
Project Management M Taimoor Khan
Advertisements

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Chapter 21 Project Management Concepts
1 14. Project closure n An information system project must be administratively closed once its product is successfully delivered to the customer. n A failed.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Project Management Software Projects – factors that influence results: –size –delivery deadline –budgets and costs –application domain –technology to be.
‘all aspects of software production’ - Software engineering is not just concerned with the technical processes of software development but also with activities.
1 Chapter 3 Project Management. 2 The 4 P’s  People — the most important element of a successful project  Product — the software to be built  Process.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Chapter 21 Project Management Concepts
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CSEB233: Fundamentals of Software Engineering
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Chapter 3 Project Management Concepts
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
Software Project Management By Deepika Chaudhary.
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Lecture 16: Chapter 24 Project Management Concepts
Project Management Concepts
Company LOGO CSEB233 Fundamentals of Software Engineering Module 9: Software Project Management Badariah Solemon 2010.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Chapter : Project Management Concept
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
Dr Izzat M Alsmadi Edited from ©Ian Sommerville & others Software Engineering, Chapter 3 Slide 1 Project management (Chapter 5 from the textbook)
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Dr. Rob Hasker. Avoiding failure  Standish Report, 2014 Standish Report 31% projects cancelled before completion 53% projects ~190% of original estimate.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter : Project Management Concept
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Monitoring Risk Factors General attitude of team members based on project pressures The degree to which the team is jelled Interpersonal relationships.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Project Management Why do projects fail? Technical Reasons
Software Project Management
INTRODUCTION: Project management involves the planning, monitoring, and control of the people, process, and events that occur as – software evolves from.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
PROJECT MANAGEMENT Software Engineering CSE
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 6/e Part 4 Supplementary Slides for Software Engineering: A Practitioner's.
Software Project Management
Exam practice… 4 marks.
Chapter 34 Project Scheduling
Software Engineering (CSI 321)
The importance of project management
Assistant Professor of Computer Science Washington State University
Chapter 3 Project Management
For University Use Only
Software Project Management
Functions Of Managemant
Chapter 21 Project Management Concepts
Software Project Management
For University Use Only
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 3 Mumtaz Ali Rajput +92 – 301-
Chapter 3 Project Management
FOUNDATIONAL CONCEPTS
SE 3800 Note 10 Project Management
Chapter 31 Project Management Concepts
Capability Maturity Model
Defining project management
Software Project Management
Chapter 27 Project Scheduling
Chapter 34 Project Scheduling
Chapter 21 Project Management Concepts
Capability Maturity Model
Information system analysis and design
Presentation transcript:

Software engineering Lecture 21

Project Management Software Projects – factors that influence results: size delivery deadline budgets and costs application domain technology to be implemented system constraints user requirements available resources

Project Management Project size: the project size increases, the complexity of the problem also increases and therefore its management also becomes more difficult. Delivery deadline directly influences the resources and quality. So a project manager has to first determine a realistic and reasonable deadline and then monitor the project progress and ensure timely delivery. Budgets and costs: project manager is responsible for ensuring delivery of the project within the allocated budget and schedule.

Project Management Application domain also plays an important role in the success of a project. The project manager thus needs to implement measures to handle unforeseen problems that may arise during the project lifecycle. Technology to be implemented: Technology also plays a very significant role in the success or failure of a project. System constraints: A system that fulfils all its functional requirements but does not satisfy the non-functional requirements would be rejected by the user. Available resources :The project manager has to ensure that the required number of resources with appropriate skill-set is available to the project.

Project Management Concerns All these point come one by one as in the previous slide. Line as well as the caption will appear one by one, starting from product quality then risk assessment.

Product quality: what would be the acceptable quality level for this particular project and how could it be ensured? Risk assessment: what would be the potential problems that could jeopardize the project and how could they be mitigated? Measurement: how could the size, productivity, quality and other important factors be measured and benchmarked? Cost estimation: how could cost of the project be estimated? Project schedule: how could the schedule for the project be computed and estimated? Customer communication: what kind of communication with the customer would be needed and how could it be established and maintained consistently? Staffing: how many people with what kind of resources would be needed and how that requirement could be fulfilled? Other resources: what other hardware and software resources would be needed for the project? 9. Project monitoring: how the progress of the project could be monitored?

Scope As it is. Resources Schedule

Why Projects Fail? changing customer requirements ambiguous/incomplete requirements an unrealistic deadline is established an honest underestimate of effort predictable and/or unpredictable risks technical difficulties miscommunication among project staff failure in project management

Management Spectrum(cont.) Effective project management focuses on four aspects of the project known as the 4 P’s. People Software development is a highly people intensive activity. Software factory comprises of the people working there. Product The product is the outcome of the project. No meaningful planning for a project can be carried-out until all the dimensions of the product Its functional as well as non-functional requirements are understood and all technical and management constraints are identified.

Management Spectrum Process Once the product objectives and scope have been determined, a proper software development process lifecycle model must be chosen to identify the required work products milestones in order to ensure streamlined development activities. It includes the set of all the framework activities and software engineering tasks to get the job done.

Management Spectrum(cont.) Project A project comprises of all work the required to make the product a reality. In order to avoid failure, a project manager and software engineer is required to build the software product in a controlled and organized fashion and run it like other projects found in more concrete domains.

Team Leaders MOI model of leadership - Weinberg Motivation: The ability to encourage technical people to produce their best Organization: The ability to mold the existing processes (or invent new ones) that will enable the initial concept to be translated into a final product Idea or innovation: The ability to encourage people to create and feel creative

Team Leaders(cont.) DeMarco says that a good leader possesses the following four characteristics: Heart: the leader should have a big heart. Nose: the leader should have good nose to spot the trouble and bad smell in the project. Gut: the leader should have the ability to make quick decisions on gut feeling. Soul: the leader should be the soul of the team.