Last modified May 24, 2017

COMP 477 / 377, Fall, 2017—Schedule

DateTopic(s) ReadingAsgn.
given
Asgn.
due
Aug. 28 Course introduction
Brief background and history of I.T. project experience and pitfalls
Roles and responsibilities in a project team.
A phased Life Cycle for system development
- Textbook review
- Brooks: Chapters 1 & 3
- Management Discipline
- Role Definition
1 -
Sep. 5 Labor Day holiday
Sep. 12Specifying a task and its deliverables
Estimating resources and duration for a task
Forming a task network
Analyzing the critical path and aggregating task estimates
Using project-management software (part 1)
Launching an application system development project; the project charter
Assignment #2 team formation
- Waterfall Approach
- Brooks: Chapter 2
- Burden of Proof
- Two Rules
- Planning a Simple Project with MS-Project
2 -
Sep.19Using project-management software (part 2)
Communication within the project team—the project workbook
Determining and documenting business system requirement
Justifying a project; return on investment
Specifying computer system requirements for a proposed new application system—part 1
Brooks: Chapter 7 - -
Sep 26Specifying computer system requirements for a proposed new application system—part 2: Specifying data
Requirements methodology wars: S.A., UML, and others
Interface prototyping
- Brooks: Chapters 8 & 11
- Requirements Crisis
- What Ever Happened to Systems Analysts?
- 1
Oct. 2 Managing changes during the project
Staffing for a major programming effort
- Requirements Are not Discrete
- Defining Data Items
- Implicit Data Dictionaries
3 & 4 2
Oct. 9Fall break ---
Oct. 16Estimating the life cycle
Highlights of textbook chapters
Brooks: Chapter 4
Legacy Systems
- -
Oct. 23Brief (20 minutes) study period for questions
Mid-term examination
Group workshop session
- - -
Oct. 30 Mid-Term examination sample answers
Testing an application system
Stages of testing
Manual versus automated testing
Continuous testing strategies
Overview of ESD deliverables
Unit testing
5 3
Nov. 6Status reporting—task level
Incremental and "agile" alternatives
Status reporting—project level
Project planning for purchasing and installing
an application software product
-Have we lost our minds?
- Agile methods
- Task status is binary
- -
Nov. 13 Late stage decisions:
- testing shortcuts.
- scope reduction
- slippage & overrun negotiation
Post project review and analysis
Human factors and personnel issues
- Deadlines and Target Dates
- Requirements shortcuts for packaged application software products
- Brooks: Chapter 14
- 4
Nov.20 Professional activities, publications, and certification for the project manager.
A popular design tool: UML:
- Instilling Professionalism
- Brooks: Ch. 15 & 16
- Stereotyping distorts personnel management
- Theory X & Theory Y
6 -
Nov. 27 Alternatives to the phased life cycle
Impact on project management of "Agile" and other fad methodologies
- Insubordination an Agile Tradition?
- Exceeding Estimates: a "Waterfall" Failure?
- False phases
- Chrysler project
- Unified Process
- 5
Dec 4 Assignment #6 team presentations and discussion
Course review & final exam. preparation
Déjà Lu Yet Again! - - 6
Dec 11Final examination
Suggested answers (posted after December 11)
--

Return to Syllabus

Last updated May 24, 2017