Report on Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

The white paper is about the “Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF.”  It means that using the requirement management in the TOGAF describes the analysis of the potential integration for the novel proved practice method in the current practice of the requirement management. This white paper also discusses the methodology of TOGAF along with the requirement management and enterprise architecture. There are the following contributions of the requirement management in TOGAF in this paper

·         Way of thinking that is also explained the principles, philosophy as well as assumptions that are underlying the method of requirement and that management which is approached.

·         The way of working that is also explained the reference method which identifies the structure of requirement management activities by the TOGAF ADM phase.

·         Way of modeling that describes the concept of goals, principles, architecture, requirements, and stakeholders.

·         Way of supporting that describes the method of analyzing as well as viewing of requirements model along with support tools.

Introduction of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

The requirement management is a process which is tracing, analyzing, documenting as well as prioritizing the requirements as well as controls the change of communication which is related to the stakeholder. Requirement management is the continuous process in the whole projects whereas the requirement is the capability where the outcome of the project should also conform. TOGAF is the “the open Group Architecture framework” for the architecture of enterprises which also provides the methods of implementing, planning as well as designing the enterprise's information technology architecture. Therefore the TOGAF is a high-level method for design which is modeled at a four-level.

The requirement management is a significant activity in managing as well as designing the enterprise architecture (EA). Therefore the goal of the diffident stakeholder from a base is changed for any organization. And it is also translated for the organization requirements architecture that also reflects the requirements and it is realized through the services of software, and the day to day operations. ADM (architecture development method) in TOGAF’s is the requirements management which is the central process and it applies for the different stages of the ADM cycles.  However, the TOGAF has shown the requirement for requirement management as well as refrains for the recommending and the mandating of exiting methods with these tools of requirement engineering (Engelsman et al, 2010).

The requirement management in the TOGAF is also shown the different structures which facilitate various applications in an ADM, and thus this white paper presented the method of the potential integration for the novel has proven practice and it is also based on the requirements engineering cycle. Enterprises architecture is the design of the management function for an enterprise which is not an easy task. There are different frameworks along with the enterprise management tools that also promise to deliver the various guidance of the enterprise's management. In this research paper the architecture framework for the TOGAF along with the promising detail which is a highly generic development architecture method. Then this type of paper also presented the generic development which steps could also complement through the pattern that is based on the Enterprises architecture management. The requirements management is the ongoing process that is playing a significant role in the TOGAF or ADM and the process of requirement management is also related to the ADM phases.  The guidance of the TOGAF which offers the actual requirement management and it is limited than the methodology along with the modeling of requirement management is the well-aligned by both TOGAF along with the ArchiMate enterprises modeling architecture.

For the potential integration of novel proven practice methods with current practices of requirements management within TOGAF in this paper then explained;

·         Way of thinking that is also explained the principles, philosophy as well as assumptions that are underlying the method of requirement and that management which is approached.

·         The way of working that is also explained the reference method which identifies the structure of requirement management activities by the TOGAF ADM phase.

·         Way of modeling that describes the concept of goals, principles, architecture, requirements, and stakeholders.

·         Way of supporting that describes the method of analyzing as well as viewing of requirements model along with support tools (Quartel et al, 2010).

Research problem of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

In this research paper, the research problem is requirement management within TOGAF by the analysis of the potential integration of the novel proven practice methods by current practices.  

Analyzing existing approaches with a distinct
perspective of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF
Problem chain – Way of thinking of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

The requirement engineering which is concerned by the process of determining a solution for several problems. Thus this type of concern could also approach the problem-oriented view that is also focused on the various understanding of problems along with the oriented view that focused on the selections along with the design of solution alternatives.

By applying the different views which are alternatively and could also identify the problem chain, and every chain links also connected by the problem solution like the solution supposed against problem through the next chain. The business analyst might be investigated the business problem along with the specified business solution for the problem, and the new solution which is most likely required IT supports as shown in the below figure;

In TOGAF the principle architecture governs the process of architect for the implantation when the guide along with the constraints of the design implementation of the decision taken in the development process. While TOGAF provided a cyclic process model, which has all the ingredients like the description of objectives, overview of the approach, the inputs which are required, which steps are to be executed, the output which will be the result of all the above step and this output might be the input of next ADM cycle. The way of thinking which enables the traceability by enterprise architecture and the element could also be traced back to the principle, a motivated goal.

Figure: Problem Chain

Motivation and architecture – Way of working of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

As explained above in the way of thinking this idea also advocate the way of working in the enterprise architecture where every chain translates the current architecture of model into the detailed and solves the various problems. The principles into the management requirements which is existing by the new elements of the enterprise's architectures like the product or services along with the organization applications. In the below figure which is also shown the relationship among the motivation models along with the architectures of the model as well as indirectly of the relationship among requirement management and the architecture process. The requirements management which is encompassed by the requirement engineering that’s also refining, analyzing, modeling and principle requirements (Foorthuis et al , 2008) ;

Figure: Management requirement and Enterprise architecture relationship

Motivation concept –Way of modeling

There is the core concept of ArchiMate which is focused on the extensional enterprise aspects and the appearance of the operational entity is included in the intentional aspects where the business goals, principle, requirements which motivate the enterprise designs and not covered through the core concepts (Quartel et al, 2010)

Figure: Extension of ArchiMate framework

Tools and techniques – way of supporting

A requirements model may grow quickly in subsequent RE cycles. Furthermore, the relationships involving some goal, principle or requirement may be distributed over different views of the model. Therefore, tool support to create, manipulate and analyze requirements models is indispensible. Model creation and manipulation requires an editing tool that supports both the ArchiMate core concepts and the motivation extension  (Chen, 2008).

Research methodology of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

In February 2009, version 9 of “The Open Group Architecture Framework” (TOFAG) framework was presented which superseded the TOGAF version 8.8.1. This version of TOGAF introduced some additional keeping in mind the support of the EA management approach. Below are the main features which were introduced in version 9 of TOGAF.

Content Framework:  To improve the consistency in all of the created deliverables, TOFAG 9 introduced a content framework with a model of architectural work.

Modular structure: The resource base of TOGAF version 8.1.1 was modularized in TOGAF version 9 to improve its usability and incremental adoption.

Extended Guidance: The TOGAF version has been extended with a logical information model and it also contains a capability framework that included the very important definition of skills, responsibilities, organizations, and roles.

Architectural style: This feature is very important in TOGAF version 9 which provided additional guidelines to adapt the process of TOGAF in specific situations like security architecture or service-oriented architecture (SOA).

 

Figure: Architecture development method cycle

TOGAF version 9 mainly consists of 6 parts. The above diagram represents the ten different phases in an EA development considered as a generic method. TOGAF version 9 presents’ different ways using which people can adapt the method to the different process styles of their needs are it also caters to different enterprise levels. The content model in version 9 TOGAF is one of its novelties. It gives a metamodel for describing different architectural artifacts. But TOGAF does not impose its use and other conceptual metamodels like the ArchiMate model can also be used.

Complementing TOGAF using the Enterprise Architecture Management Pattern Catalog

The EA catalog provides the best practices which can be used the address the typical EA management concerns. The best practices employ their process descriptions. Due to this limitation, the catalog does not provide all overall process descriptions. While TOGAF provided a cyclic process model, which has all the ingredients like the description of objectives, overview of the approach, the inputs which are required, which steps are to be executed, the output which will be the result of all the above step and this output might be the input of next ADM cycle. So, the generic methodology of TOFAG can complement the EA management catalog best practices. The TOFAG starts with a preliminary phase and it initializes the EA management approach. The tasks which are usually performed during this phase are the definition and establishment of the EA team, the implementation of the supporting tools. Usually, architecture guidelines are principles that are also defined during this phase. After the completion of the preliminary phase, the Architecture vision phase (A) is initiated.

The main purpose of this phase is to identify the relevant stakeholders also identify what their concerns might be. In TOFAG, no procedure is defined to gather the relevant concern of the stakeholders is identified. Here the EA management pattern catalog can complement TOFAG as it lists the typical concerns in the context of ES management. These concerns can be used as input to the stakeholder which is identified using TOGAF. After the completion of phase A, the corresponding business, information system, technology architecture is developed in Business Architecture (B), Information Systems Architecture (C) and Technology Architecture (D) phases. These three architectures are fundamentally very similar to each other. TOGAF uses baseline architecture and a gap analysis is required to evaluate the difference between baseline architecture and target architecture that is going to be used. Here the EA management pattern catalog can also complement TOGAF. As TOFAG describes a generic model; the EA management pattern catalog can help facilitate the adaption to the specific needs of an enterprise.

The first step is to gather only the relevant information that is needed to make informed decisions to the scope of architecture effort. Here EA management pattern catalog can be used; it supports the concern-driven approach which can be used to deduce the relevant information. The next step is to determine the overall modeling process. To do this EA management pattern catalog can be consulted for the best practice solutions. The next step in this phase is to identify the required visualization and here EA management pattern can help ensure the suitability of the models. The next phase is Opportunities are Solutions (E) and it concerns the use of intermediate architectures for transformation from baseline architecture to the target architecture. This phase includes different kinds of refinements. Here EA management catalog can help generate possible planned architectures.

 The next phase is the Migration Planning phase (F), which deals with the implementation of some or all the planned architectures. The main steps of this plan are the business value assignment and prioritization of the project. Here EA management pattern catalog can help plan which leads to certain demands regarding the information model and it also helps with the visualization which is needed in this phase. The next phase in the process is the Implementation Governance phase (G) where the selected projects in the previous phase are executed. The main steps in this phase identification of deployment resources and skills also monitor the execution of the project. Here EA management pattern catalog helps with the implementation concern through best practices solutions. The next phase Change Management phase (H) which also concludes an ADM cycle concerns the changes are required in the architecture. The key tasks here are to monitor the deployment techniques and develop change requirements (Buckl et al, 2009).

Conclusion of Analysis of the potential integration of novel proven practice methods with current practices of requirements management within TOGAF

Summing up all the discussion the research paper is about the requirement management in the TOGAF for the analysis of the integration of novel based proven methods using current practice. In this white paper, the discussion is also about the ADM of TOGAF that provides the guideline for executing as well as establishing the enterprise architecture process of management. The pattern is based on enterprise architecture management and it is also presented by the enterprise management catalog which is discussed and provides guidance for addressing the specific concerns. As TOFAG describes a generic model, the EA management pattern catalog can help facilitate the adaption to the specific needs of an enterprise. TOGAF uses baseline architecture and a gap analysis is required to evaluate the difference between baseline architecture and target architecture that is going to be used.