CIS 375 SOFTWARE ENGINEERING

University Of Michigan-Dearborn

Dr. Bruce Maxim, Instructor

Configuration Management:

(Tracking changes)

Configuration Management Team:

Configuration Control Board:

(Change control board)

Process:

(Of changes)
    1. Problem is discovered.
    2. Problem is reported to configuration control board.
    3. The board discusses the problem (is the problem a failure or an enhancement, who should pay for it)
    4. Assign the problem a priority or severity level, and assign staff to fix it.
    5. Programmer or analyst locates the source of the problem, and determines what is needed to fix it.
    6. Programmer works with the librarian to control the installation of the changes in the operational system and the documentation.
    7. Programmer files a change report documenting all changes made.

Issues:

(Of change process)
    1. Synchronization (when?).
    2. Identification (who?).
    3. Naming (what?).
    4. Authentication (done correctly?).
    5. Authorization (who O.K.’d it?).
    6. Routing (who’s informed?).
    7. Cancellation (who can stop it?).
    8. Delegation (responsibility issue).
    9. Valuation (priority issue).

Automated Tools For Maintenance:
    1. Text editors (better than punch cards).
    2. File comparison tools.
    3. Compilers and linkage editors.
    4. Debugging tools.
    5. Cross reference generators.
    6. Complexity calculators.
    7. Control Libraries.
    8. Full life cycle CASE tools.

Computer System Engineering:

Computer System Elements:
    1. Software.
    2. Hardware.
    3. People.
    4. Databases.
    5. Documentation.
    6. Procedures (more human type, not code).