GENERIC

SOFTWARE ENGINEERING

PROCESS GROUP DOCUMENT

@(#)sepg.htm 3.3 03/10/01

Permission is granted to reproduce and adapt this document provided credit is given to the University of West Florida. This documentation is provided "as is" and no warranty of fitness for any particular purpose is made or implied.

ABSTRACT

This document defines the Software Engineering Process Group (SEPG) activities performed for the generic maintenance process architecture (GUMP++)for the Software Engineering graduate program at the University of West Florida (UWF). This document should be referred to and modified by the SEPG in an effort to comply with the Capability Maturity Model (CMM) for software.

ABSTRACT
1.0 INTRODUCTION
2.0 SEPG
2.1 SEPG RESPONSIBILITIES
2.2 GUMP++ CHANGE PROCESS
2.3 GUMP++ CHANGE REVIEW
REVISION HISTORY

1.0 INTRODUCTION

The SEPG is responsible for coordinating and sustaining changes to GUMP++ and for supporting normal software engineering operations. The SEPG should ensure that all changes to the process are documented and performed in a manner that will maintain consistency and CMM compliance. This document contains details on changing GUMP++ documentation and other activities to be performed by the SEPG.

2.0 SEPG

2.1 SEPG RESPONSIBILITIES

The SEPG must perform two main tasks: coordinating and sustaining process change and monitoring the GUMP++ software engineering activities. In order to coordinate and sustain the software maintenance process the SEPG should follow the GUMP++ Change Process defined in section 2.2. Monitoring of the project software engineering activities should be done weekly during class meetings by going over the process architecture activities described in the Generic Process Architecture and ensuring that all responsible engineers are aware of the activities to be performed at each cell.

2.2 GUMP++ CHANGE PROCESS

Any member of the organization can initiate GUMP changes. The SEPG should ensure that the changes are effectively implemented.

Initiator fills out a GUMP++ Change Proposal form (located in the Forms Directory) and emails it to the SEPG.

SEPG will verify CMM compliance and post the proposal to the discussion logs.

The SEPG presents the proposal to class at which time it is discussed for approval.

Upon approval, a Documentation Engineer will ask the SCM to check out the document(s), and make the appropriate changes IAW the Style Guide.

Once changes are complete, the SEPG will organize a GUMP++ Change Review with the initiator, PC, Documentation Engineer, and SQA.

Upon a successful GUMP++ Change Review the Documentation Engineer will ask the SCM to check in the document(s).

In the case of an unsuccessful GUMP++ Change Review - Either the GUMP++ change proposal is dropped and the document(s) are checked in as original or - the Documentation Engineer incorporates the deviations from the GUMP++ Change Review and proceeds back to step 5.

2.3 STEPS DURING A GUMP++ CHANGE REVIEW

The SEPG will schedule the GUMP++ Change Review IAW the GUMP++ Change Process.

During a GUMP++ Change Review:

SEPG presents the original GUMP++ Change Proposal submitted by the initiator.
Documentation Engineer presents the diff file(s) that demonstrate the changes to the original document(s).
SEPG/Initiator presents the lessons learned and any other information that may be of importance to the PC and/or SEPG representative for future changes.
Class Discussion.
Documentation Engineer obtains approval for Change.