Software Engineering Project Management
(CS - 413)

 

Department of Computer Engineering

Bilkent University

Fall 2009

 

 

Dr.Çağatay ÜNDEĞER

 

Part Time Instructor

Department of Computer Engineering - Bilkent University

Game Technologies, Informatics Institute – Middle East Technical University

&

General Manager

SimBT Inc.

 

e-mail : cagatay@undeger.com

web-site : www.cs.bilkent.edu.tr/~cagatay

 

Couse Assistant : Aslı Kale

 

Objective

 

In this course, software engineering and project management methodologies considering both practical and theoretical aspects in the context of information systems development will be studied in details. By taking the lecture, you will be supported with sufficient knowledge that will lead you to use software engineering project management methodologies to successfully initialize a project, reduce the development risks and finalize a project with success.

 

Scope

 

In recent decades, development of projects involving information systems has become a very crucial requirement in keeping organizations competitive with others. Projects in today’s business environment are usually undertaken by a team of highly skilled personnel, and have a considerable amount of risks that makes projects fail with about 40% probability. Therefore, having good project management skills is a very important aspect in managing teams and leading to success. In this course, the techniques to become a successful software engineering project manager will be studied starting with an introduction to the general terms in project management, continuing with brief descriptions of some project management standards, and ending with details of project management components.

 

Course Outline

 

         Introduction To Software Engineering Project Management

        What is Software Engineering?

        What is a Project?

        What is Project Management?

         Introduction to Project Life Cycle

        What is a Project Life Cycle?

        Usual Phases of Process Models

        Prescriptive Process Models

         Project Management Context

        Project Stakeholders

        Organizational Structures

        Project Management Office (PMO)

        Standards and Regulations

         Techniques Supporting Project Management

        Work breakdown structures

        Gantt charts

        Network diagrams

         Introduction to Project Management Components

        What are the Project Management Components?

        Brief Description of Project Management Components

         Project Management Components

        Project Integration Management

        Project Scope Management

        Project Time Management

        Project Cost Management

        Project Human Resource Management

        Project Communication Management

        Project Quality Management

        Project Risk Management

        Project Procurement Management

 

Course Requirements

 

The students are expected to develop a small-scale software project with a team of 2 - 4. The documentation and presentation of the project is the primary focus. Therefore implementation can be ignored. The project topic will be proposed by the teams. Microsoft Word, Power Point and Project can be used during the development of the projects.

 

Assessment Method

 

Description

References

%

Due

Term project

 

65%

 

            Project Description Document

7, 8

5%

12.10.2009 : 23:59

            Software Project Management Plan (SPMP - IEEE 1058-1998, 1058.1-1987)

use 10 as the reference, but you may get help from 6, 9, 13 and 14 as a sample.

10%

02.11.2009 : 23:59

            Software Requirements Specification (SRS - IEEE 830-1998)

use 15 as the reference (make it English), but you may examine 11 as well.

15%

30.11.2009 : 23:59

            Software Design Description (SDD - IEEE 1016-1998)

use 12 as the reference, but you may get help from 16 and 17 as a sample. Samples should not be considered as a complete reference.

15%

14.12.2009 : 23:59

            Presentation of Projects

Max 25 minutes per presentation. Too short and too long presentations will get lower grades.

 

The presentations will not be postponed due to tight schedule. 

 

Presentations will include at least: 

a)      Objective

b)      Scope

c)      Overview of requirements and Design

d)      Conclusion

 

A very technical presentation is not required. Be understandable. Don’t forget that the audience do not know your project.

 

20%

14.12.2009

   Group 1,2,3,4

 

21.12.2009

   Group 5, 6,7,8,9

 

28.12.2009

   Group 10,11,12,13

Assignments and/or Quizzes

 

25%

 

Attendance

 

10%

 

 

Lecture Presentations

 

1. Course Introduction

2. Introduction to Software Engineering Project Management

3. Introduction to Project Life Cycle

4. Project Management Context

5. Techniques Supporting Project Management

6. Project Management Components

7. Project Integration Management

8. Project Scope Management

9. A Detailed Look to Initiation of Project Scope Management

10. Project Time Management

11. Project Cost Management

11. Project Human Resource Management

12. Project Communications Management

13. The Capability Maturity Model Integration (CMMI)

 

 

References

 

[1] Mark A.Fuller, Joseph S. Valacich and Joey F. George, “Information Systems Project Management: A Process and Team Approach”, Pearson Prentice Hall, 2008.

 

[2] Roger S. Pressman, Software Engineering: A Practitioner’s Approach, Mc Graw Hill, 6th Edition, 2005.

 

[3] Walker Royce, “Software Project Management: A Unified Framework”, Addison Wesley, 11th Edition, 2003.

 

[4] “A Guide to the Project Management Body of Knowledge”, Project Management Institute, Inc., 2000.

 

[5] Cagatay Undeger, “A Survey: Active IEEE Standards for Software Develoment”, Department of Computer Engineering, Bilkent University, 2008.

 

[6] “Sciamachy Data Center Software Management Plan”, (a limited sample, which should not to be considered as a full IEEE sample), Sciamachy Data Center, 1999.

 

[7] Cagatay Undeger, “Proje Tanımlama Dökümanı Şablonu”, referans: Savunma Sanayii Müsteşarlığı, 2008.

 

[8] Cagatay Undeger and Berkay Undeger, “Project Definition Document Template”, original reference: Secretariat of Defence Industry, 2008.

 

[9] Cagatay Undeger, “Sample Work Breakdown Structure”, Department of Computer Engineering, Bilkent University, 2008.

 

[10] Software Engineering Standards Committee of the IEEE Computer Society, “IEEE Standards for Software Project Management Plans”, IEEE Std 1058-1998.

 

[11] Software Engineering Standards Committee of the IEEE Computer Society, “IEEE Recommended Practice for Software Requirements Specification”, IEEE Std 830-1998.

 

[12] Software Engineering Standards Committee of the IEEE Computer Society, “IEEE Recommended Practice for Software Design Descriptions”, IEEE Std 1016-1998.

 

[13] A sample software project management plan from Spring 2008 coarse.

 

[14] Another sample software project management plan from Spring 2008 coarse.

 

[15] Software Requirements Specification Template

 

[16] A sample software design description document

 

[17] Another sample software design description document