Process Decomposition

This is a software team which should have a significant degree of flexibility in selecting the software engineering paradigm which is best for the project or the software engineering tasks which populate the process model once it is chosen. A relatively little project which is similar to previous efforts might be best accomplished by using the linear sequential approach.  If time constraints very tight are imposed and the problem can be heavily compartmentalized then the RAD model is probably the right option.  If the deadline is so tight which full functionality cannot reasonably be delivered then an incremental strategy might be best.  Same, projects with the other characteristics will lead to the selection of the other process models.

At the Once the process model has been selected, the common process framework is adapted to it.  In the every case the CPF is discussed previous in this chapter planning the customer communication, engineering, release, construction risk analysis and customer evaluation can be fitted to the paradigm.   It will work for linear models for iterative and incremental models for evolution models and even for concurrent or component assembly models.   The CPF is a serves and invariant as the basis for all software work performed through a software organization.

But the original work tasks do vary.  The Process decomposition commences that the project manager asks the question:  how do we accomplish the CPF activity?  For example a small relatively easy project might need the following work tasks for the customer communication activity:

1.    Develop the list of clarification issues.

2.    Meet with the customer to address the clarification issues.

3.    Jointly develop a statement of scope

4.    Review the state of scope with all concerned

5.    Modify the statement of scope as needed.

These events might be occurring over a period of less than 48 hours.  They will present a procedure decomposition that is appropriate for the relatively small, simple project

Now we have to consider a more complete project that has a broader scope and which is more significant business impact. Like a project might need the following work tasks for the customer communication activity.

1.    Review the customer request.

2.    Schedule and Plan a formal which is facilitated meeting with the customer.

3.    Conduct research to describe proposed solutions and existing approaches.

4.    Prepare a working document and an agenda for the formal meeting

5.    Conduct the meeting.

6.    Jointly develop mini-specs which reflect, behavioral and data, function features of the software.

7.    Review each mini spec for consistency, correctness, and lack of ambiguity.

8.    Assemble the mini specs to a scooping document.

9.    Review the scooping document by all concerned

10.  Modify the scooping document as needed.

Both the projects perform the same frame work activity which we call customer communication but the first project team performs half as various software engineering work tasks as the second.