Ki sa ki se Achitèk Referans ak analiz Fit / Gap

Description

Before defining Reference Architecture, it is better to have some idea about software architecture. Software architecture has various definitions which are derived from different sources. It ranges from designing, creating and maintaining all the code of large computer systems to incorporating all the functioning of the physical and logical components of enterprise systems as well. It is a combination and interaction of all the components (software and hardware) to make a complete system specific to different business needs.

Achitèk nan Referans ak analiz Fit / Gap se yon kout nan dokiman ki deklare Achitèk nan Referans yo dwe itilize kòm baz pou achitekti pwojè a ye a epi ki gen ladan raison a pou desizyon sa a. Li se tou yon pwosesis analiz yo konprann achitekti a referans ak aplikasyon li.

Yon Achitèk Referans se yon modèl predefini achitekti fèt pou sèvi nan biznis patikilye ak kontèks teknik.

Source of Reference Architectures within an organization can be any proven framework and asset used in earlier projects. The work product is generic and applies equally to selection of Reference Architectures from other sources.

The most important part of a Reference Architecture is to understand the fitness and gaps found during analysis.

A Reference Architecture Fit/Gap Analysis tabulates the key factors involved in selecting a Reference Architecture:

  • Business scenarios
  • Business drivers
  • Architecture characteristics

Asset selection involves tradeoffs. Reference Architecture Fit/Gap Analysis documents the differences between the desired project architecture and the reference architecture in a statement-of-fit and identifies modifications required for the project.

Purpose

Now let us check the purposes Fit/Gap analysis in Reference Architecture model. The Reference Architecture Fit/Gap Analysis are used for the following

  • To assist in determining the scope of a proposed solution development project
  • As an input to other architecture work products. Depending on the size of the gaps, the chosen Reference Architecture and associated fit/gap analysis may form the basis for the whole architecture.
  • To highlight any gaps where the Reference Architecture does not fit project requirements. These indicate areas of risk or substantial architectural work required in the project. It also helps to select the reference architecture for the proposed project.

Impact of Not Having Reference Architecture

Chwazi yon Achitèk Referans redui risk la pa resèvi pwouve, best-practice solutions. Not applying a standard Reference Architecture increases project effort and cost, ak ogmante risk nan echèk pwojè.

The best way to use architectural assets is to start by selecting a Reference Architecture. This will form the context for a more detailed selection of assets and guidance.

Rezon pou pa sèvi ak Achitèk Referans

Sou avantaj ki baze sou pwojè, ta dwe pwodui sa a toujou ap pwodui.

If appropriate Reference Architectures are not available to a project or a project decides not to use a Reference Architecture, then at most the Executive Summary, including reasons why a Reference Architecture was not selected, should be completed. Often even this is unnecessary. A note can be added to the documentation of the choice of work products.

How Fit/Gap analysis is documented

A Reference Architecture Fit/Gap Analysis is basically textual document, ak tab evalye pwofil la karakteristik kondisyon ak pwoteksyon matyè. Fòm nan tabulaire dekri tout pwen ki nesesè yo jwenn yon foto klè nan achitekti a refere ak kapasite li yo nan pwojè a pwopoze.

Rezime ekzekitif: Brief deklarasyon sou Achitèk Referans chwazi ak nenpòt pi gwo pwoblèm / risk.

Entwodiksyon: Kòmantè Entwodiksyon nan sou achitekti nan referans.

Kle chofè: Yon deklarasyon kout sou objektif yo biznis oswa kontrent.

Achitèk Kondisyon Lis pou Tcheke pou: The document consists of a standard set of questions and potential answers regarding architectural requirements, which allows a systematic collection of the architectural requirements for the project. This set is used as a checklist to prompt for customer architectural requirements and associated issues, which are documented in a table, as below. This is a sample table and it can be of a different format according to the standard of the organization.

Requirement Reference Architecture Characteristic Required Value for Project Risks/Issues/Comments Points to Investigate
Requirement name Relevant range of values for this architecture Range applicable to the customer Any gaps, risks, likely future issues, topics for subsequent analysis

Subject Area Checklist:Each Reference Architecture encompasses several subject areas (sometimes referred to as “domains”). Subject areas are specific areas of concern, pa egzanp, the web based delivery channel is a subject area consisting of Web browsers, domain name servers, elatriye. A simple and clear way of examining the “fit” of a Reference Architecture to customer requirements is to compare it to the subject area coverage. Following is a table for capturing the details.


Subject Area
Present in Architecture? Required by Customer? Issues/Risks/Notes
Name of subject area Yes/No Yes/No

Statement of Fit:A summary of the extent of “fit” between the Reference Architecture and customer requirements. Each Reference Architecture is described at several levels of abstraction, and guidance is provided at each level on the characteristics supported. For each area where the Reference Architecture does not meet requirements, describe briefly:

  • The unmet requirement. This is very important for selecting the reference architecture.
  • The type and extent of delta that would be requisite for the Reference Architecture to meet the requirement. Also mention if it needs to be extended, modified, or receive a new subject area?
  • An estimate of the cost and risk of the delta

Development Approach

The following steps should be taken in generating this work product:

  1. Identify the most likely Reference Architecture candidate. As there are a small number of Reference Architectures, each with a well-defined focus, it should be simple to identify one or two as relevant to the customer’s project goals and future business model.
  2. Review the description of the asset context, which is provided in both textual and illustration form, with the customer to assess fit. The illustrations, in particular, are a powerful way of checking customer understanding of the proposed approach. During this process, kliyan an ka deside chanje kondisyon deja deklare l ', pa egzanp, nan rekonesans ke modèl la achitekti ki ofri pa Achitèk nan Referans la se siperyè nan yon sèl la li te deja envisagées.
  3. Sèvi ak Chofè biznis, IT Principles and Requirements lists to characterize customer requirements Check with the customer on whether there are any other important requirements that have not been covered by the standard characteristics.
  4. Examine the fit of the requirements with the characteristics provided by the Reference Architecture at various levels of abstraction.
  5. From the asset base, identify the subject areas covered by the Reference Architecture. Compare these with the subject areas required by the customer.
  6. Analyze the fit between the Reference Architecture and the customer requirements. Document all gaps, and make initial assessments with the customer on how these shortcomings will be resolved. This may involve:
  • Pwolonje achitekti a (e.g., ki lye ak nan yon matyè plis)
  • Modifye Achitèk nan Referans (dir, chanje estrikti entèn li yo oswa konpòtman)
  1. Dokimante raison a pou chak nan desizyon sa yo an tèm de sipozisyon, jistifikasyon biznis, risks, elatriye.
  2. Make an overall assessment of viability and risk based on the information available at this point.

Validation and Verification

Perform the following checks:

  • Verify that the customer has approved the criteria used to compare and choose the Reference Architectures.
  • Verify that all major requirement areas of the customer have been considered.
  • Verify that critical dependencies of the architecture in the target environment can be met.
  • Valide nenpòt konpwomi yo te fè ak moun ki bay yo kliyan ak Byen ak kritè sa yo.
  • Verifye si achitekti a se fleksib nan chanjman antisipe.
============================================= ============================================== Buy best TechAlpine Books on Amazon
============================================== ---------------------------------------------------------------- electrician ct chestnutelectric
error

Enjoy this blog? Please spread the word :)

Follow by Email
LinkedIn
LinkedIn
Share