Since 1994
Application Systems Design and Development Services
Ready-made Fully Customizable Solutions

About: Policies: Process Method

JHZ-CS's Process Method

This describes the process flow of projects conducted at JHZ-CS. Note the "Output" of each step is referenced as "Input" to subsequent steps.

  1. Project Proposal

    1. Requirements Analysis

      Input: Initial Design Request
      Output: Project Proposal

    2. Project Initiation

      Input: Project Proposal
      Output: Project Agreement

    Output: Project Agreement

  2. Design

    Input: Project Agreement

    1. External Design (function)
    2. Internal Design (logic)

    Output: Function and Logic Specifications

  3. Development

    Input: Function and Logic Specifications

    1. External Interface Coding
    2. Logic Coding
    3. Unit Test

    Output: Unit Tested Code/Components

  4. Function Test

    Input: Unit Tested Code/Components, Function and Logic Specifications

    Testing is performed in an integrated emulated production environment.

    1. New Function Test
    2. Regression Test
    3. Progression Test (when applicable)

    Output: Tested Code/Components

  5. Integration Verification Test

    Input: Tested Code/Components

    1. Code Integration
    2. Integration Test
    3. Customer Verification

    Output: New Function(s)

Optional Project Steps

  1. User Documentation

    Input: Design Specifications
    Output: Users Guides and References

  2. User Training

    Input: Users Guides, References, and Training Materials
    Output: Trained User base

  3. Skill Transfer

    Technical information transfer intended for future in-house maintenance and support

    Input: Code and documentation
    Output: Trained Technical Personnel

Project Documentation

Project documentation provides specification of requirements. The documentation serves as reference for project communications and progress monitoring. Its purpose continues after project completion serving as future technical reference for maintenance, skill transfers, training and as baseline specification for subsequent enhancements.

Parallel co-development project environments benefit from formal project documentation assisting in communication of co-dependent component technical information required by multiple groups.

  • Project Proposal

    The Project Proposal is a living document during the Initial Requirements Analysis and Proposal Stages. It begins as a response to a request for proposal. It defines project purpose, objective, requirements, pre-requisites, dependencies and terms including copyright ownership, cost, and time of completion. The Project Proposal typically undergoes a series of reviews and revisions cycle until a mutual understanding is reached.

  • Project Agreement

    The Project Agreement defines project purpose, objective, requirements and terms, cost and time of completion.

  • Function Specification

    The Function Specification defines external aspects of new and existing interfacing components impacted by the project; components that accept input and/or produce output. Inputs and outputs may be user initiated or machine initiated. It describes each external component elements, attributes pertaining to its inputs and outputs. It serves as input to the Logic Specification, input for coding user and machine interfaces, and as input to Function Test. The Function Specification does not describe logic aspects which are described in the Logic Specification.

  • The Logic Specification

    The Logic Specification defines internal logic and processing aspects of components created or impacted by the project. It describes logical processes operating on inputs and producing outputs defined in the Function Specification. It defines component relationships. The Logic Specification serves as input to Coding, Unit Test and Function Test and serves as process logic flow to subsequent projects. The Logic Specification is maintained internally at JHZ-CS.

Design Change Policy

"Design Change" refers to changes to design of an on-going project which has successfully completed its Design stage and once coding has commenced. Essentially, all design change requests are deferred to a follow-on enhancement project once a project's Design stage has been completed. This policy helps assure project progression continues smoothly to completion.