10.13 Other Alternative Work Patterns

 < Day Day Up > 



Alternative work patterns provide flexibility for the SEP methodology. An alternative work pattern permits a project planner to tailor a project management plan to meet the specific needs of the project and still conform to SEP standards. Alternative work patterns provide the opportunity for the Core Team and related specialists to predefine the permitted tailoring and to ensure that a project planner’s customization does not overlook necessary activities or include unneeded ones. The alternative work patterns suggested are as follows:

  • Reduced-effort work pattern

  • Rapid Application Development (RAD) work pattern

  • Pilot development work pattern

  • Managed Evolutionary Development (MED) work pattern

  • Operations and maintenance (O&M) small-effort enhancement work pattern

  • O&M project work pattern

  • Commercial off-the-shelf (COTS) acquisition

The following are operational definitions for terms associated with these types of projects:

  • Proof of concept: A project that defines what will be proven and determines both the criteria and methods for the proof of concept. Once the proof of concept is demonstrated, a prototype project may be initiated.

  • Prototype: An ensemble that is suitable for the evaluation of design, performance, and production potential and is not required to exhibit all the properties of the final system. Prototypes are installed in a laboratory setting and are not installed in the field; nor are they available for operational use. They are maintained only long enough to establish technical feasibility.

  • Proof of technical feasibility: The result of a successful prototype.

  • Pilot: A system installed in the field to demonstrate that the system’s concept is feasible in an operational environment. The pilot system installed has a predetermined subset of functions and is used by a bounded subset of the user population. Its features may not all function smoothly. The goal of the pilot is to provide feedback that will be used to refine the final version of the product. The pilot will be fielded for a preset, limited period of time only to permit pilot systems to be evaluated for operational feasibility.

  • Proof of operational feasibility: The result of a successful pilot.

  • Production: A fully documented system, built according to the SEP, fully tested, with full functionality, accompanied by training and training materials, and with no restrictions on its distribution or duration of use.



 < Day Day Up > 



Managing Software Deliverables. A Software Development Management Methodology
Managing Software Deliverables: A Software Development Management Methodology
ISBN: 155558313X
EAN: 2147483647
Year: 2003
Pages: 226

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net