V.29.1 Define reengineering objectives
Intent: The intent of this task is to define the objectives for the reengineering activity. The goals of functional process improvement (FPI) are identified and the role of the application to be reengineering within the context of the improved process is defined.
Mechanics: This task specifies the objectives for using the application, supporting the application, and applying reengineering technology to rebuild the application.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Do one or more objectives address a direct business need?
2. Has the reengineered application's role in the business process been identified?
3. Have the tools and methods to be used for reengineering been discussed at a high level?
4. Has the customer (for the reengineering project) been involved throughout the definition of objectives?
5. Has the statement of objectives been reviewed internally and by the customer?
Do's & Don'ts
Do: Focus attention of the business process and the role of the reengineered application in it.
Do: Take a hard look at whether the application can be eliminated, rather than reengineered.
Do: Recognize that the reengineered application will have features that are not present in the existing application.
Don't: Misjudge the difficulties associated with reengineering.
Don't: Forget to consider parts of the existing application that may be reusable.
Helpful hints:
Goals should indicate how the business needs of the organization and the requirements of the reengineered application will be met. They should also address how standards and procedures, regulations, policy, and related information will affect the reengineering effort. Finally, objectives should consider how the methods and tools to be used for reengineering will be used to achieve a reengineered application.
Deliverables: list of objectives for the reengineered application
V.29.2 Examine the existing application in the context of current business requirements and process.
Intent: The intent of this task is to develop a representation of the current business process and the role of the reengineered application in it.
Mechanics: A business process modeling technique can be used to identify (1) key business data, key relationships among the data, (3) business functions, and (4) the flow of business data across the business area.
Application of Formal Methods: information engineering (enterprise modeling) techniques
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Does the business process model reflect actual business practices?
2. Is it likely that the business process will remain in tact for at least n years after the reengineered system is completed? [n is defined locally]
3. Does the reengineered application fit into the data flow of the business?
4. Has application interoperability been considered?
Do's & Don'ts
Do: Create the business model in a way that will enable you to change it as time passes.
Do: Be sure that business data are given as much emphasis as business function at this stage.
Do: Be sure that data reengineering is considered as thoroughly as application reengineering.
Don't Attempt to automate a poorly defined or inefficient business process. Work to improve it.
Deliverables:
1. business model
2. description of the reengineered application's role
V.29.2.1 Identify existing application software.
Intent: The intent of this task is to identify the software that is to be reengineered as well as all applications that must interoperate with the software..
Mechanics: Application interfaces are examined and cross checked against the business model (data flows) defined in Task V.29.2.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Has all relevant documentation been collected and examined?
2. Has descriptive information been assessed for completeness and traceability to the as built application?
3. Have all interoperable applications been identified?
4. Have all interfaces been described and all relevant data objects defined?
Deliverables: description of application interfaces
V.29.2.2 Identify existing data.
Intent: The intent of this task is to identify both internal and external data that may have to be modified as part of the reengineering effort.
Mechanics: The structure and format of all existing internal data structures and external files and databases are examined. If no descriptive information about the data is available, data structure and format are documented.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Have all external databases and files been identified and examined?
2. Does documentation exist for all external databases and files?
3. Have internal data structured been identified and examined?
4. have global data structures been identified and examined?
5. Does documentation exist for all internal data structures?
Deliverables: documented internal and external data structures
V.29.2.3 Identify existing technical Infrastructure
Intent: The intent of this task is to identify the operational environment (the technical infrastructure)in which the application to be reengineered resides. The technical infrastructure includes the hardware, operating system, network architecture, communication protocols, and existing utilities that form the environment for the application.
Mechanics: A schematic representation of the technical infrastructure is created. The schematic depicts the elements of the infrastructure and the manner in which the application to be reengineered interacts with these elements.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Has an infrastructure schematic been created and does it identify all elements of the infrastructure?
2. Has coupling between the application and the infrastructure been fully described?
3. Have modules that are coupled to the technical infrastructure been identified within the application?
4. Have risks associated with the existing technical infrastructure been identified?
Deliverables: schematic of the technical infrastructure and related descriptive information
V.29.3 Examine existing software descriptive information for completeness, consistency, correctness and correspondence to the executable application
Intent: The intent of this task is to ensure that existing software documentation will provide information necessary for the reengineering activity. If the documentation is deficient, reverse engineering (see Task. V.32.5) must be initiated.
Mechanics: Documentation is reviewed to determine completeness, consistency, correctness and correspondence to the executable application.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
SQA Checklist:
1. Have all documents associated with the application been identified?
2. Has information contained in each document been compared to the production application?
3. Have areas of non-compliance (i.e., the documentation does not accurately describe what happens in the executable application) been documented?
4. Have all documents been reviewed for completeness and consistency?
Do's & Don'ts
Do: Examine documentation at all levels of abstraction. Start with source code comments and work backward toward design documentation.
Do: Examine both requirements and testing documents.
Don't Believe that volume implies document quality. Be sure to review for correctness and other attributes.
Deliverables: list of documents and deficiencies
V.29.4 Conduct feasibility analysis
Intent: The intent of this task is to determine the feasibility of reengineering based on information determined in Tasks V.29.1 through V.29.3
Mechanics: Reengineering objective are reviewed to determine the scope of the effort. The role of the existing application with the current and future business context is explored. The current status of the of the existing application is assessed.
Application of Formal Methods: none
Application of CASE Tools: t.b.d.
Deliverables: Feasibility report
Use Browser "back" arrow or return to APM Process Design Language Description
