Request Consulting Services

Today's information technology needs are so complex and varied that a disciplined and methodical approach to even the simplest problem is necessary to ensure the appropriate solution to the problem with minimal risk.

The TechProse method is a proven, three-layered architectural approach that we have developed over the years. It focuses on developing Functional, Technical and Component Architecture.

Each step is fully documented and builds upon the previous step. Rollout begins as soon as initial components or prototypes are complete.

The Steps in the Process

1. Project Requirements Specification
2. Functional Requirements Specification
3. Technical Design Specification
4. Implementation
5. Rollout, Documentation and Education
6. Improvement

Step 1 - Project Requirements Specification (PRS)

• Deliverable: Functional/Technical Outline of Requirements.
• TechProse defines the project needs, application functionality, or business process issues, and develops a PRS that includes:
  • Budget
  • Timeline
  • Technology requirements
  • Process requirements
  • External interfaces

back to process steps

Step 2 - Functional Requirement Specification (FRS)

• Deliverable: Formal Specification.
• TechProse defines the project needs, application functionality, or business process issues, and develops a PRS that includes a formal, structured specification that defines the business operations of the application and/or associated processes.
• The analysis process allows for the definition of all business objects and possible relationships between these objects. This makes it possible to define all operations or functions that may be performed upon each and every object, with appropriate business rules. In the analysis, each function can be defined in grammatical terms using NOUNS, VERBS, ADJECTIVES, and ADVERBS.
• The FRS consists of a structured, formal definition for these objects, plus protocols and data associated with each object. In this way, TechProse defines the exact, required functionality of the application, and assigns a requirement number, leaving no room for ambiguity.

back to process steps

Step 3 - Technical Requirements Specification (TRS)

• Deliverable: Technical Architecture.
• In this third step, TechProse designs the technical architecture, including the technology to be used for implementation. This consists of the technical steps required to implement the functionality defined in Step 2. The design is based on proven components and technology that have been used many times before by TechProse engineers. This technology forms the basis for the standard TechProse tools that have been developed over many years of implementation to support the architecture
• Each numbered requirement explicitly stated in Steps 1 and 2 must be explicitly answered in the technical design.

back to process steps

Step 4 - Implementation

• Deliverable: Step-by-Step Development.
• TechProse uses the step-by-step implementation process. That is, the first deliverable, which might be as simple as application startup and shutdown, or user login/logout, is delivered very quickly, usually within days of initiation of implementation.
• This allows an end user to receive a running system and be in a position to develop internal use and support of the application quickly. While this initial delivery is usually very limited in scope, the entire technological platform is often required to support it. Thus end user personnel are quickly introduced to the technology, as well as the roll out processes used by TechProse.
• The implementation process also allows a very precise measurement of progress towards completion of the implementation step. TechProse follows a very specific "development-unit test-integration test-release" process that involves tight control of source code, binaries and other resources, as well as project team cooperation strategies.

back to process steps

Step 5 - Rollout, Documentation and Education

• Rollout is a gradual process. A beta or test version of the application is released very early in the implementation step. This allows partial release of an application into production where appropriate.
• Customer response dictates the rollout process up to a beta level. Beyond that, TechProse uses the normal release process, which may also involve data migration, for the target client environment.
• TechProse has a wealth of experience in technical and end user training that supports the education of the end users for the application. The client is also encouraged to include internal technical personnel as part of the project team early on. TechProse provides a complete turnover of knowledge, processes and tools, along with the application rollout.

back to process steps

Improvement Process

At each stage TechProse applies quality measurement processes. After each project, TechProse conducts a post-mortem and the process is evaluated and improved for the next implementation. Information gathered becomes part of our quality matrix.

back to top