Project Management-Development and Software Engineering-Lecture Slides, Slides of Software Engineering

This lecture is part of lecture series for Software Engineering course. Prof. Prateek Aron delivered this lecture at Allahabad University. Its main points are: Project, Management, Organising, Planning, Scheduling, Software, Graphical, Representation, Risk, Development

Typology: Slides

2011/2012

Uploaded on 07/16/2012

sanaka
sanaka ๐Ÿ‡ฎ๐Ÿ‡ณ

4.6

(21)

71 documents

1 / 30

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project Management
๏‚—Organising, planning and scheduling software projects
1 COMP201 - Software Engineering
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e

Partial preview of the text

Download Project Management-Development and Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity!

Project Management

๏‚— Organising, planning and scheduling software projects

Objectives

๏‚— To introduce software project management and to describe its distinctive characteristics

๏‚— To discuss project planning and the planning process

๏‚— To show how graphical schedule representations are used by project management

๏‚— To discuss the notion of risks and the risk management process

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 and procuring 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

Software Management Distinctions

๏‚— The product is intangible ๏‚— (cannot be seen or touched)

๏‚— 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

๏‚— Many software projects are 'one-off' projects

Management Commonalities

๏‚— These activities are not peculiar to software management

๏‚— Many techniques of engineering project management are equally applicable to software project management

๏‚— Technically complex engineering systems tend to suffer from the same problems as software systems

Project Staffing

๏‚— 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 ๏‚— Staff with the appropriate experience may not be available ๏‚— An organisation may wish to develop employee skills on a software project

๏‚— Managers have to work within these constraints especially when (as is currently the case) there is an international shortage of skilled IT staff

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. Configuration management plan

Describes the configuration management procedures 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.

Project Plan Structure

๏‚— Introduction

๏‚— Project organisation

๏‚— Risk analysis

๏‚— Hardware and software resource requirements

๏‚— Work breakdown

๏‚— Project schedule

๏‚— Monitoring and reporting mechanisms

Milestones in the RE Process

Evaluation report

Prototype development

Requir ements definition

Requir ements analysis

Feasibility report

Feasibility study

Architectural design

Design study

Requir ements specification

Requir ements specification

ACT IVITIES

MILESTONES

Project Scheduling

๏‚— Split project into tasks and estimate time and resources required to complete each task

๏‚— Organize tasks concurrently to make optimal use of workforce

๏‚— Minimize task dependencies to avoid delays caused by one task waiting for another to complete

๏‚— Dependent on project managers intuition and experience

Bar Charts and Activity Networks

๏‚— 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

๏‚— Activity charts show task dependencies and the critical path

๏‚— Bar charts show schedule against calendar time

Task Durations and Dependencies

COMP201 - Software Engineering 17

Task Duration (days) Dependencies T1 8 T2 15 T3 15 T1(M1) T4 10 T5 10 T2,T4 (M2) T6 5 T1,T2 (M3) T7 20 T1 (M1) T8 25 T4 (M5) T9 15 T3,T6 (M4) T10 15 T5,T7 (M7) T11 7 T9(M6) T12 10 T11(M8) docsity.com

Activity Timeline

M

Start

 - 4/7 11/7 18/7 25/7 1/8 8/8 15/8 22/8 29/8 5/9 12/9 19/ 
  • T
  • T1T - M - T7T - M - T - M - M - T - T - M - T - M - T - M - T11 M - T

Staff Allocation

4/7 11/7 18/7 25/ 1/8 8/8 15/8 22/8 29/8 5/9 (^) 12/9 19/ T T8 T T T T T T T6 T T T

Fred

Jane

Anne

Mary

Jim