©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 3 Slide 1
Project management
Organizing, planning and
scheduling software projects
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software Project Management: Characteristics, Activities, and Planning, Study Guides, Projects, Research of Software Engineering
A series of slides from ian sommerville's 'software engineering' book, covering the basics of software project management. It discusses the importance of management in software development, the distinctive characteristics of software projects, and the key management activities, including project planning and scheduling.
Typology: Study Guides, Projects, Research
Pre 2010
1 / 23
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software Project Management: Characteristics, Activities, and Planning and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!
Software Engineering, 5th edition. Chapter 3
Project management^
Organizing, planning andscheduling software projects
Software Engineering, 5th edition. Chapter 3
Objectives^ ^
To introduce software project management and todescribe its distinctive characteristics To discuss project planning and the planningprocess To show how graphical schedule representationsare used by project management
Software Engineering, 5th edition. Chapter 3 ^ Concerned with activities involved in ensuringthat software is•^
delivered on time,• on schedule, and• in accordance with the requirements of the organizationsdeveloping and procuring the software
Software project management
Software Engineering, 5th edition. Chapter 3
Why is management important?^ ^ Software engineering is an economic activityand therefore is subject to economic,non-technical constraints^ ^ Well-managed projects sometimes fail. Badlymanaged projects often fail
Software Engineering, 5th edition. Chapter 3
Management activities^ ^ Proposal writing^ ^ Project costing^ ^ Project planning and scheduling^ ^ Project monitoring and reviews^ ^ Personnel selection and evaluation^ ^ Report writing and presentations
Software Engineering, 5th edition. Chapter 3
Management commonalities^ ^ These activities are not peculiar to softwaremanagement^ ^ Many project management techniques used inengineering are equally applicable to softwareproject management^ ^ Technically complex engineering systems tendto suffer from the same problems as softwaresystems
Software Engineering, 5th edition. Chapter 3
Project planning^ ^
Probably the most time-consuming projectmanagement activity Continuous activity from initial concept throughto system delivery.•^ Plans must be regularly revised as new information becomesavailable
Software Engineering, 5th edition. Chapter 3
Types of project plan^ Plan^
Description
Quality plan
Describes the quality
procedures and standards that will be used in a project.
Validation plan
Describes
the approach, resources and schedule used for system validation.
Configurationmanagement plan
Describes the configuration managementprocedures and structures to be used.
Maintenance plan
Predicts the
maintenance requirements of the system, maintenance costs and
effort
required.
Staff development plan.
Describes how the skills and
experience of
the project team
members will be developed.
Software Engineering, 5th edition. Chapter 3
Activity organization^ ^
Activities in a project should be organized toproduce tangible outputs for management tojudge progress Milestones
are the end-point of a process activity ^ Deliverables
are project results delivered to customers The waterfall process allows for thestraightforward definition of progress milestones
Software Engineering, 5th edition. Chapter 3
Milestones and deliverables
PrototypedevelopmentEvaluationreport Requir ementsanalysis Requir ementsdefinition Feasibilitystudy Feasibilityreport
Designstudy Architecturaldesign
Requir ementsspecificationRequir ementsspecification
ACT IVITIES MILESTONES
Software Engineering, 5th edition. Chapter 3
Scheduling problems^ ^
Estimating the difficulty of problems and hencethe cost of developing a solution is hard Productivity is not proportional to the number ofpeople working on a task Adding people to a late project makes it laterbecause of communication overheads The unexpected always happens. Always allowcontingency in planning
Software Engineering, 5th edition. Chapter 3
Bar charts and activity networks^ ^
Graphical notations used to illustrate the projectschedule Show project breakdown into tasks. Tasks shouldnot be too small. They should take about a weekor two Activity charts show task dependencies and thethe critical path Bar charts show schedule against calendar time
Software Engineering, 5th edition. Chapter 3
Activity networks tart
M 3 T
T
Fi ni sh T1 0 M 7 T7 T M 2 T
M 5
T
8 day s 4/ 7/ 94
1 4/ 7/ 94^
1 5 d ay s
1 5 d ay s4/ 8/ 94
2 5/ 8/ 94 7 day s 5/ 9/ 94 10 days 1 5 d ay s 1 9/ 9/ 94 1 1/ 8/ 94 2 5 d ay s 5 d ays 2 0 d ay s 1 0 d ay s 2 5/ 7/ 94 1 5 d ay s 2 5/ 7/ 94 1 8/ 7/ 94 1 0 d ay s
T
M 1^
T
T9 M 6
T1 1 M 8 T1 2 M 4
Start
- Software Engineering, 5th edition. Chapter - Activity timeline4/
- 11/7 18/
- 25/7 1/
- 8/8 15/
- 22/8 29/
- 5/9 12/
- 19/
- T4T1T2M1T7T
- M5T8M3M2T6T
- M4T9M7T
- M6T1 1M8T
- M4T9M7T
- M5T8M3M2T6T
- T4T1T2M1T7T