CpSc 443, Software Project Management

Syllabus, Spring, 2011

Dr. Conlon

 

Catalog Description: An introduction to project management in the information systems, or IT development, area. Provides an understanding of the purpose, methods and benefits of process management by exposing the student to the concepts, practices, processes, tools and techniques used in process management for software development. Prerequisite: CpSc 210 or 207. (3 credits)

Class Meeting:

Section

Time

Place

1

MWF 3 (10:00-10:50 a.m.)

ATSH 230

Instructor:

Name

Phone

Email

Office

Michael P. Conlon, Ph.D.

724-738-2143

michael.conlon@sru.edu

ATSH 252

Office hours:   As indicated below, or by appointment.

Day

Mon

Tue

Wed

Thu

Fri

Time

11:00 a.m.-12:00 m.

11:00 a.m.-12:00 m.

11:00 a.m.-12:00 m.

8:15 a.m.-9:15 a.m.

11:00 a.m.-12:00 m.

Office hours are for you. Please feel free to visit me to discuss any problems. Do not wait until problems become unmanageable. If I am doing other work during my office hours, it is because no student has come to see me. I will gladly drop what I am doing to help you. If my office hours are inconvenient, see me before or after class and we will find a better time to meet.

Texts: Software Project Management: A Real-World Guide to Success , © 2004, by Henry, Addison Wesley. ISBN #978-0-201-75865-8. Also The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, second edition, ©1995, by Brooks, Addison Wesley Professional. ISBN #978-0-201-83595-3

Grading:

Exams

Project(s)

Homework, service, etc.

45%

45%

10%

Late Assignment Policy: Late assignments will not be accepted, and will receive a grade of zero. Exceptions will be made only in extraordinary circumstances.

Exam dates:

Sections

Exam 1

Exam 2

Final

5

Mon, Feb 21

Wed., Mar 30

Wed., May 4, 10:30 a.m.-12:30 p.m.

Attendance, reading, and participation: You are expected to attend every class and to arrive on time. Do not expect to be admitted to class if you are late. Please do all assigned reading before the class in which it is covered. You are expected to attend and participate in class, and you must do the reading and homework to participate.

Exams: Exams will cover both text and lecture material; some text material may not be covered in class. If you must be absent for an examination, please see me one week in advance to make alternate arrangements to take the exam. Please take care of bodily needs before coming to an exam: you will not be permitted to leave the room during an exam until your paper is handed in. All electronic communication, computation, and entertainment devices must be turned off and put away during exams. Use of such devices during an exam will be considered cheating.

Email: I may communicate via electronic mail, using your SRU address. Assignments may be announced this way. Be sure your email account is properly set up. You are responsible for checking your SRU email regularly.

Recording of Lectures: Video and/or audio r ecording of lectures is generally prohibited. The instructor reserves the right to reduce your grade should you make illicit recordings. Permission to record will be granted if there is an educational need for you to do so.

Plagiarism policy: Plagiarism or collusion will earn you a failing grade for the project, and you will be reported to the committee on academic integrity. You are not to cooperate with others in any way in the development of your programming projects, except as specified in the assignment. Cooperation in doing homework and labwork is encouraged. If you have cooperated with anyone in your homework projects, you must indicate that person's name in your header comments.

Copyright permission: By registering in this course you grant the SRU Computer Science Department permission to copy any of your work from the course for use in assessment or accreditation processes. Identifying information will be removed from such work.

The following statement is required of SRU faculty in order to comply with the TEACH Act, which modifies U.S. copyright law primarily to deal with the copyright implications of online education. The link to references is mine.

Copyright Statement: Students shall adhere to the laws governing the use of copyrighted materials. They must ensure that their activities comply with fair use and in no way infringe on the copyright or other proprietary rights of others. Additional information regarding copyright and fair use can be found at www.koce.org/classroom/copyright.htm.

Course Outcomes: This course and its outcomes support the Information Systems Learning Outcomes of Problem Solving and Critical Thinking (PS&CT), Communication and Interpersonal Skills (C&IS) and Ethical and Professional Responsibilities (E&PR). These Information Systems Learning Outcomes are tied directly to the University Wide Outcomes of Critical Thinking and Problem Solving, Communication , and Values and Ethics .

Program Objectives Assessed in CpSc 365:

Degree

Program Objective

Assessed Course Objective

IS

I.d. Perform critical analyses and write feasibility studies of system implementations

1. Define roles and responsibilities by PM process group (initiating, planning, executing controlling, closing

IS

II.b. Summarize technical information for technical and non-technical personnel

2. Articulate the purpose and benefits of project management (PM

IS

II.c. Use oral and electronic communication effectively

3. Written reports and oral presentations

IS

II.e. Work cooperatively in teams and with others

4. Work in groups to analyze a project and implement a solution

IS

III.e. Recognize the need for continuing professional development

5. Explain quality management and process improvement in the context of software development projects.

Additional Course Objectives include:

The student will be able to:

  1. 1.Apply key PM concepts.  

  2. 2.Explain the project life cycle (concept, definition, execution, finish).  

  3. 3.Apply estimating and risk management techniques to IS projects. 

 

Calendar (tentative), with assigned readings:

Date

Topic

Reading

Jan

19

People and Culture

Ch. 1

 

21

 

 

 

 

 

 

 

24

The Process

Ch. 2

 

26

 

 

 

28

 

 

 

 

 

 

 

31

Tools

Ch. 3

Feb

2

 

 

 

4

Measurements

Ch. 4

 

 

 

 

 

7

 

 

 

9

 

 

 

11

Management Vision

Ch. 5

 

 

 

 

 

14

 

 

 

16

Organizing Resources

Ch. 6

 

18

 

 

 

 

 

 

 

21

Exam 1

 

 

23

Scheduling

Ch. 7

 

25

 

 

 

 

 

 

 

28

The Plan

Ch. 8

Mar

2

 

 

 

4

 

 

 

 

 

 

 

14

People and their Roles

Ch. 9

 

16

 

 

 

18

Scheduling

Ch. 10

 

 

 

 

 

21

 

 

 

23

 

 

 

25

Hardware and Software Support

Ch. 11

 

 

 

 

 

28

 

 

 

30

Exam 2

 

Apr

1

Project Launch

Ch. 12

 

 

 

 

 

4

 

 

 

6

Monitoring the Project

Ch. 13

 

8

 

 

 

 

 

 

 

11

Adjusting the Schedule

Ch. 14

 

13

 

 

 

15

 

 

 

 

 

 

 

18

Software Engineering for Quality

Ch. 15

 

20

 

 

 

22

Delivering the System

Ch. 16

 

 

 

 

 

25

 

 

 

27

 

 

 

29

Assessing the Project and the Process

Ch. 17

 

 

 

 

May

2

 

 

 

 

 

 

 

4

Final Exam, 10:30 a.m.-12:20 p.m.