CIS 375 SOFTWARE ENGINEERING

University Of Michigan-Dearborn

Dr. Bruce Maxim, Instructor

Management & Object Oriented Projects:
    1. Establish a common process framework (CPF).
    2. Use CPF & historic data to eliminate time & effort.
    3. Specify products & milestone.
    4. Define Q.A. checkpoints.
    5. Manage changes.
    6. Monitor.
    1. Number of scenario scripts.
    2. Number of key classes.
    3. Number of support classes.
    4. (# of key classes)/(# of support classes).

Object Oriented Estimating & Scheduling:
    1. Develop estimates using effort decomposition, FP, etc.
    2. Use O.O.A. to develop scenario script and count them.
    3. Use O.O.A. to get the number of key classes.
    4. Categorize types of interfaces:

      5. No U.I. = 2.0 G.U.I. = 3.0

      Text U.I. = 2.25 Complex G.U.I. = 3.0

      Use to derive support classes:

      (# of key classes) * (G.U.I. #)

    5. Total classes = (key + support) * (average # of work units per class).

      6. (» 15-20 person days per class)

    6. Cross check class based estimate (5) by multiplying.

(avg. # of work units) * (# of scenario scripts)

Project Scheduling Metrics:
    1. Number of major iterations (around spiral model).
    2. Number if completed contracts.

(Goal: at least 1 per iteration)

Object Oriented Milestones:
    1. Contracts completed.
    2. O.O.A. completed.
    3. O.O.D. completed.
    4. O.O.P. completed.
    5. O.O. testing completed.