About Us


  Process Models

  SE Resources


  Contact us

Breaking News!

A new blog ...

visit OnCenter, Roger Pressman's running commentary on the world at large

A new edition ... the 7th edition of Software Engineering is available now

A new book ... Roger Pressman and David Lowe on Web Engineering

A first novel ... Roger Pressman's first novel is a technothriller -- The Aymara Bridge

A new curriculum! RSP&A has partnered with QAI to develop a comprehensive Internet-based software engineering curriculum.

A redesigned site! ... we've done a major redesign and added many new features for 2009 - 2010

Adaptable Process Model
Task IV.26 Implement the Change

IMPORTANT NOTICE: The complete Adaptable Process Model (APM) is provided for informational purposes and for assessment by potential users. The APM is copyrighted material and may not be downloaded, copied, or extracted for use in actual project work. The full hypertext (html) version of the APM may be licensed for use and customization within your organization. Contact R.S. Pressman & Associates, Inc. for complete licensing information.

Task IV.26 Implement the change

Intent: The intent of this task is to construct a deliverable that was modified in Task IV.25. If the deliverable is not executable, final documentation for engineering models is created. If an executable deliverable is developed, programming language source code is generated by translating the procedural design model.

Mechanics: For source code: Data structures and program component skeleton are created in the programming language of choice. Then each program component (module) procedural design is used as the basis for creating source code for the component.

Application of Formal Methods: structured programming

Application of CASE Tools: t.b.d.

SQA Checklist (for source code):

    1. Has each program module been reviewed for completeness, consistency and correctness?

    2. Have errors been found and corrected in each model?

    3. Has source code that has undergone significant change been re-reviewed?

    4. Are coders well-versed in the programming language or 4GL?

    5. Has change control been applied as parts of the model have been baselined (large projects only)?

Do's & Don'ts

    Do: Develop program components that are directly traceable to the design model.

    Do: Use the elements of good programming style (see Coding references).

    Don't: Use arcane or ambiguous language constructs; remember that someone will have to modify this code!

Helpful Hints

    1. Whenever possible, use source code constructs that follow the procedural design as closely as possible.

    2. Use indentation (or an indenting tool) to enable the code to reflect the logical structure of the procedural design.

    3. Use internal program comments to add to, not simply parrot, the semantics of the code.


1. non-executable deliverables, or

2. Source code for all program components

Use Browser "back" arrow or return to APM Process Design Language Description

Site search! We've added links to a search engine that will enable you to search our entire site for information you need. Enter the appropriate word or phrase below.


Home About us Products Product Models SE Resources Commentary Contact us

Web site and all contents © R.S. Pressman & Associates, Inc. 2001 - 2010, All rights reserved.
Free website templates