Method Engineering Overview
Definition of a System
Method Engineering and Method Execution can be viewed as a system just as a business function, business project, organisation or application can be viewed as a system. Per system theory, a system can be described as follows:
The system has the following characteristics:
1) A system operates in scenarios that have its own influencing factors.
2) A system has a particular purpose that can be described in terms of a mission or goals that need to be realised, which are driven by opportunities and threatened by constraints.
3) The system is either strong or weak to capitalise on opportunities and mitigate threats.
4) Every system has to use inputs to produce the required outputs, Inputs are sourced from and supplied to the system's target environment. For a project, the outputs are referred to as deliverables.
5) Every system always has to produce outputs or deliverables to satisfy the particular needs of certain parties that are part of the target environment.
6) Inputs and outputs related to resources such as data, technology, people, operational capital, raw material, energy, products, services, and others with specific implied characteristics.
7) Inputs and outputs are conveniently grouped as primary and secondary.
8) Stakeholders of a system have specific interests in the system's operation
9) The efficiency of the system is represented as the ratio between the input and output, only as long as the output is in demand. The system is represented as the ratio between the input and output, only as long as the output is in demand. The system can be effective in that it produces the required output but is not efficient due to the inputs that are consumed.
10) The system is influenced by factors from the target and external environment and attempts to have a direct impact on the target environment.
The following types of transformations can take place in a system using transformation mechanisms:
- Physical (Converting raw material into a product of higher value)
- Location (Moving objects from one place to another, for example, storage of goods)
- Transactional (A value-implied exchange, such as banking or stock brokerage)
- Informational (Modification of data into something more useful that could be reflected in a
- report)
Method Engineering Objectives:
The established methodology should be oriented towards attaining the following objectives:
1. Enhance the overall quality (effectiveness and efficiency) of accomplishing business engineering/transformation goals:
- Minimize human effort.
- Optimize time and cost.
- Ensure accurate and precise delivery of required results.
- Guarantee successful outcomes.
- Facilitate risk mitigation.
These objectives can be realized through an incremental approach involving early, continuous, and measurable deliverables, thereby reducing the associated risks of prolonged initiatives. This strategy aims for incremental cost and risk growth, coupled with a significant advancement in the benefits of change and operational modes.
2. Optimize stakeholder benefits:
- Identify stakeholders and articulate their expectations.
- Ensure the methodology delivers the anticipated benefits to all stakeholders.
3. Standardize on a universally accepted methodology concerning:
- Language (Terminology).
- Approach.
- Deliverables.
- Repeatability.
4. Elevate the organization's maturity for change:
- For a mature organization, the methodology should be:
- Well-defined and known to all stakeholders.
- Entrenched and consistently executed by all stakeholders.
- Subject to continuous engineering through research and development.
- Standardized across the enterprise.
- Comprehensive, covering all architectural layers and facets, complete life cycle, and all architectural data viewpoints.
Organisation / Project Specific Methodology (vs. Generalised Methodology)
The rationale for the development of organization or project-specific methodologies encompasses several key factors:
1. Legacy Method Integration:
Incorporating existing software, techniques, and other elements within the organization that are deeply ingrained and proven to be effective.
2. Industry-Specific Requirements:
Acknowledging the distinctive needs of various industry sectors such as Finance, Government, and Manufacturing, each of which has specific requirements tailored to their areas of focus.
3. Organizational Maturity:
Aligning the methodology with the maturity level of the organization, recognizing that a one-size-fits-all approach may not be suitable for all problem or opportunity resolutions.
4. Business Pressure for Results:
Responding to the strategic drivers, philosophies, and principles adopted within the organization, driven by the imperative to deliver tangible results.
5. Organizational Culture and Ethics:
Incorporating the unique culture and ethical considerations specific to the organization, ensuring alignment with its values and principles.
6. Environmental Scenarios and Influences:
Adapting to various environmental scenarios, situations, and external influences that may impact the project or organization.
7. Over-Regulated Environments:
Navigating through regulatory complexities and constraints in environments with stringent regulations.
8. Information Demands for Decision-Making:
Meeting the demand for comprehensive information required to facilitate informed decision-making processes.
A project-specific architecture is tailored to the specific requirements of a given project, allowing for the exclusion of certain elements from the overarching architecture framework, thus ensuring a more targeted and effective approach.
Generic Principles for the Method & Method Establishment
These Principles can Act as Control Mechanisms to Establish a Quality Method
- Facilitate Centralized Oversight with Decentralized Implementation.
- Foster a Synergistic Approach to Knowledge Generation, Balancing Top-down and Bottom-up Perspectives.
- Comprehensive in Scope (Encompassing all Stages of the Lifecycle, Architectural Layers, and Data Perspectives).
- Empower Governance over Architectural Structures and Adaptations.
- Strategic Guidance Influences Architectural Decisions, Shaping Portfolio and Project Management.
- Utilize an Object/Service Oriented Methodology.
- Establish a Continuous, Dedicated Functional Set for Methodology Engineering
- (Incorporating Processes, People, Technology, etc.).
- Deploy Pre-established Solutions/Objects (Patterns, Blueprints, Standard Solutions, etc.).
- Implement Methodological Frameworks Utilizing Software.
Deliverable's Required
The following artefacts and deliverables serve as pivotal method enablers:
1) Philosophies/Principles Adopted:
- Strategic drivers underpinning the method's foundation.
2) Meta Model – Function Perspective:
- Representation of objectives/goals for attainment.
3) Categories of Projects:
- Inclusive of process re-engineering, organisational restructuring, and package evaluation, selection, and implementation.
- Derived from the Meta Model <Function>.
4) Meta Model – Data Perspective:
- Normalised representation of data attributes with interdependencies.
- Business rules associated with method data, transcending mere meta data.
5) Data Artefacts and Related Templates:
- Structure/Catalogue of Data Artefacts employed throughout the life cycle.
- Specification of data attributes per Data Artefact.
6) Meta Model - Process to Execute the Methodology per Project Category:
- Process definition encompassing sequenced functions, deliverables (inputs/outputs), primarily data artefacts, and role players.
- Life cycles detailing repetitive sequences of techniques to accomplish specific objectives/goals.
7) Modelling Techniques and Related Guidelines:
- Graphical, textual, and algorithmic methods.
- Summarisation of rules derived from Meta Model <Data>.
- Notation usage (symbols) and inclusion of sample diagrams.
8) Framework:
- Comprehensive summary of all data/information requiring attention.
9) Enabling Software and Related Architecture:
- Functionality, physical data structure, semantic aspects, and logic/algorithms.
- Software integration architecture.
10) Governance:
- Inclusion of extracts/viewpoints from other deliverables.
- Agreement/sign-off on governance mechanisms.
- Integration of education and compliance measurement/reporting.
Implications of Method Engineering
Implications of a Newly Developed or Enhanced Methodology:
1. Training on Method:
- Emphasize competency development, encompassing knowledge, skills, values, and attitudes.
- Maintain a balance reflective of the nature of the managed change.
- Recognize that even optimal solutions may fail if not executed by individuals who comprehend their full potential or implement them incorrectly.
2. Organisational Restructuring:
- An inadequately aligned organisational structure may lead to inefficient method execution.
- Organisation structure changes necessitate:
- Revision of role/job descriptions (roles and responsibilities).
- Recruitment and structuring of resources (people).
3. Implementation of Governance:
- Establish a forum or structure to enforce the adopted method.
- Institute controls for effective governance.
4. Implementation of Capability for Ongoing Maintenance and Support of Method:
- Prioritize training and education initiatives.
- Develop a help desk system.
5. Evaluation, Selection, Configuration, and Deployment of Enabling Software (PPM and Architecture related):
6. Sourcing and Conversion of Existing Data/Knowledge into the New/Fixed Software's Database:
7. Budget Sourcing for Implementation, Management, and Support of the Method:
8. Measurement:
- Method Engineering necessitates assessments pre-, mid-, and post-change to determine financial viability.
- Metrics must be established to gauge conformance and contribution towards targets.
- Metrics should be deployed through governance mechanisms to influence effective operations.
- Performance targets should be set throughout the business and agreed upon with stakeholders.
9. Human Engineering:
- Stakeholder participation and behaviour are influenced by unique elements.
- Method engineering enforces a specific way of working and structure, where "structure enforces behaviour."
- Predict stakeholders' behaviour considering specific threats, uncertainties, constraints, changes, and the rate of change they face.
10. Project and Programme Management (PPM):
- Address the intricacies of project and programme management within the overarching methodology.
Process Overview
The method can be established and enhanced on an ongoing basis using the following typical life cycle steps:
