Task: Assess Viability of Architectural Proof-of-Concept









var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{4AC346F0-E6FC-4D2C-8410-2EDF8DDDC91D}", "{F04ADECF-743C-4BEB-A92C-9FF25AE7429D}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_IY0NkAISEdqTna4sZVFRow", "_ydt62NnmEdmO6L4XMImrsA", "{F04ADECF-743C-4BEB-A92C-9FF25AE7429D}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{4AC346F0-E6FC-4D2C-8410-2EDF8DDDC91D}", "{F04ADECF-743C-4BEB-A92C-9FF25AE7429D}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_kC0pcN7GEdm8G6yT7-Wdqw", "_ydt62NnmEdmO6L4XMImrsA", "{F04ADECF-743C-4BEB-A92C-9FF25AE7429D}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', true, false, false);










Task: Assess Viability of Architectural Proof-of-Concept















This task defines how to evaluate an Architectural Proof-of-Concept against Architectural Requirements and Risks.


Disciplines: Analysis & Design






Purpose



To evaluate the synthesized Architectural Proof-of-Concept to determine whether the critical architectural requirements are feasible and can be met (by this or any other solution).



Relationships



RolesPrimary Performer:



Software Architect


Additional Performers:



InputsMandatory:



Architectural Proof-of-Concept


Business Case


Glossary


Risk List


Vision



Optional:



Supplementary Specifications


Use-Case Model






Outputs


Reference Architecture


Review Record






Process Usage


Analysis & Design
 > 
Perform Architectural Synthesis
 > 
Assess Viability of Architectural Proof-of-Concept






Steps




Determine Evaluation Criteria



The criteria against which the Architectural Proof-of-Concept is to be evaluated are drawn from the architecturally significant requirements, which were the drivers in its construction.



Evaluate Architectural Proof-of-Concept



In this step, the Architectural Proof-of-Concept is tested against the evaluation criteria: the way in which this is done will depend on the form of the proof-of-concept. For example, in the case of an executable prototype, this may be through demonstration; in the case of a conceptual model, through inspection and reasoning, or, for a simulation, requiring the set-up and running of the simulation model with input data derived from the evaluation criteria, then the collection and analysis of output data from the model.



Assess Results



The results from the evaluation are assessed to determine not only if the architecturally significant requirements can be satisfied, but also as a check on the validity of those requirements. At this time in the development, requirements are still mutable, and not necessarily well-understood by the stakeholders; for example, perhaps the opportunity exists to relax requirements that were shown to be high-risk by the evaluation of the Architectural Proof-of-Concept. All these avenues should be thoroughly explored in assessing the results - this contrasts with the situation later in elaboration and construction, when there will be much greater reluctance to change or reinterpret requirements. After the assessment, with a better understanding of scope and feasibility by all stakeholders, change proposals to the Business Case, Vision and Risk List are prepared, if necessary. In addition to the above concerns, answering the following questions can also be useful: How does the prototype stack-up against its original goals and expected schedule ? How does the design of the prototype compare against the Architecture baseline? What is our new understanding of the project risks (whether or not they were directly addressed by the prototype)?  









©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();