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, vytváření a udržování celý kód velkých počítačových systémů, který bude obsahovat všechny fungování fyzických a logických prvků podnikových systémů, jakož. Jedná se o kombinaci, a interakce všech složek (software a hardware) aby celý systém specifické pro různé podnikatelské potřeby.
The Reference Architecture and Fit/Gap analysis is a short of document stating the Reference Architecture to be used as the basis for the current project’s architecture and including the rationale for this decision. It is also a analysis process to understand the reference architecture and its implementation.
A Reference Architecture is a predefined architectural pattern designed for use in particular business and technical contexts.
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, Vybrali Referenční architektura a související fit / gap analýza může být základem pro celé architektury.
- 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. To také pomáhá vyberte referenční architekturu pro navrhovaný projekt.
Dopad Není s referenční architektura
Selecting a Reference Architecture reduces the risk by reusing proven, best-practice solutions. Not applying a standard Reference Architecture increases project effort and cost, and increases the risk of project failure.
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.
Reasons for Not Using Reference Architecture
On asset-based projects, this product should always be produced.
Jestliže vhodný referenční architektury nejsou k dispozici k projektu, nebo projekt rozhodne použít referenční architekturu, pak nanejvýš shrnutí, včetně důvodů, proč Referenční architektura nebyly vybrány, should be completed. Often even this is unnecessary. A note can be added to the documentation of the choice of work products.
Jak Fit / Gap analýza je dokumentováno
Referenční architektura Fit / Gap analýza je v podstatě textový dokument, with tables assessing the requirements characteristic profile and subject area coverage. The tabular form describes all the required points to get a clear picture of the referred architecture and its fitness in the proposed project.
Executive Summary: Brief statement of selected Reference Architecture and any major issues/risks.
Úvod: Introductory comments about the reference architecture.
Key Drivers: A brief statement of the business objectives or constraints.
Architecture Requirements Checklist: 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 | Požadovaná hodnota Project | Rizika / problémy / Komentáře body vyšetřovat |
| Požadavek jméno | Relevantní rozsah hodnot této architektury | Rozsah použitelný pro zákazníka | Všechny mezery, rizika, pravděpodobné budoucí problémy, témata pro následnou analýzu |
Subject Area Checklist:Každý Referenční architektura zahrnuje několik tematických oblastí (někdy označované jako "domény"). Subject areas are specific areas of concern, například, webový dodání kanál je předmětem plocha se skládá z webových prohlížečů, servery doménových jmen, etc. 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. Následuje tabulka pro zachycení detailů.
Oborová |
Prezentujte v architektuře? | Požadavku zákazníka? | Otázky / rizika / poznámky |
| Název předmětu plochy | 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, a pokyny jsou uvedeny na každé úrovni na podporovaných vlastnostech. Pro každou oblast, kde Referenční architektura nesplňuje požadavky, stručně popsat:
- Neuspokojené požadavky. To je velmi důležité pro výběr referenční architekturu.
- Typ a rozsah delty, že by podmínkou pro referenční architektura pro splnění požadavku. Dále uveďte, zda je třeba prodloužit, změněna, nebo přijímat novou tematickou oblast?
- Odhad nákladů a rizika delty
Development Approach
Následující kroky je třeba podniknout při vytváření tohoto pracovního produkt:
- Identify the most likely Reference Architecture candidate. As there are a small number of Reference Architectures, každý s dobře definovaným zaměřením, to by mělo být jednoduché identifikovat jeden nebo dva jako relevantní pro zákazníka cílů projektu a budoucí obchodní model.
- Přečtěte si popis aktiv kontextu, který je k dispozici jak v textové formě a ilustrace, with the customer to assess fit. The illustrations, zejména, are a powerful way of checking customer understanding of the proposed approach. During this process, Zákazník se může rozhodnout změnit své dříve uvedené požadavky, například, prostřednictvím uznání, že architektonický model poskytuje referenční architektura je lepší než ta, kterou již předpokládá.
- Použití businessu, 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.
- Examine the fit of the requirements with the characteristics provided by the Reference Architecture at various levels of abstraction.
- From the asset base, identify the subject areas covered by the Reference Architecture. Compare these with the subject areas required by the customer.
- 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:
- Extending the architecture (e.g., linking to an additional subject area)
- Modifying the Reference Architecture (i.e., changing its internal structure or behavior)
- Document the rationale for each of these decisions in terms of assumptions, business justification, rizika, etc.
- 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.
- Ověřit žádné kompromisy, kterého bylo dosaženo zákazníků a majetku poskytovatele na základě těchto kritérií.
- Ověřte, že architektura je odolný vůči předpokládané změny.
