View TRAK:TRAK Viewpoint Selection



Each TRAK architecture viewpoint addresses a set of concerns which are defined in the viewpoint (in accordance with ISO/IEC 42010). TRAK has a minimum modelling process based on addressing the taskholder’s concerns. Using these concerns viewpoints can be chosen and views prepared. It is that simple.

TRAK Viewpoints & Concerns Addressed by Each

Taken from the TRAK Enterprise Architecture Viewpoints p35:

PerspectiveViewpointTitleQuestions / Concerns
EnterpriseEVp-01Enterprise GoalWhat is the Enterprise and what goals does it set out to achieve?
EVp-02Capability HierarchyWhat are the enduring capabilities the enterprise requires and how is capability measured?
EVp-03Capability PhasingHow is capability delivered over time? Are there any gaps?
ConceptCVp-01Concept NeedHave the concept needs been identified?
CVp-03Concept Item ExchangeHave the items exchanged by concept nodes been identified? What is required to satisfy the concept needs?
CVp-04Concept Activity to Capability MappingHow/are concept activities sufficient to deliver capability?
CVp-05Concept ActivityWhat does each concept node need to do?
CVp-06Concept SequenceHow are concept activities ordered? Is it important?
ProcurementPrVp-01Procurement StructureWhat is the project structure? How is it governed?
PrVp-02Procurement TimelineWhat other projects is this dependent on? How does their delivery time affect us?
PrVp-03Procurement ResponsibilityWhat responsibilities do organisations or jobs have in relation to a project or time? Are their boundaries clear?
SolutionSVp-01Solution StructureWhat does the solution consist of? Is it structured sensibly? What is the organisation structure / membership? How does responsibility (scope/jurisdiction) apply to the solution components?
SVp-02Solution Resource InteractionHow are resources connected together? How are the organisations, jobs & roles connected? Have the interactions/ interfaces/exchanges been characterised?
SVp-03Solution Resource Interaction to Function MappingAre there interactions/interfaces that cannot be justified by functional need? Do we have functions that cannot be realised because there isn’t an interchange?
SVp-04Solution FunctionHave all solution functions been identified? What does each part do?
SVp-05Solution Function to Concept Activity MappingDo the solution functions meet all of the concept activities? Is there unwanted solution functionality?
SVp-06Solution CompetenceDoes the organisation or job through its role have the necessary competence to conduct the function? Is the competence consistent with the solution?
SVp-07Solution SequenceIn what order do things need to happen?
SVp-11Solution Event CausesHow robust is the system to unwanted events? How dependable is the system? What causes (feared) events?
SVp-13Solution RiskWhat threats is the system of interest exposed to?? What are the vulnerabilities of the system of interest? What are the risks posed to the system, or to a third party by the system? How does the solution design mitigate or address the vulnerabilities, threats and risks?
ManagementMVp-01Architecture Description DictionaryIs the architecture description portable? Can it be understood in the way it was intended to be?
MVp-02Architecture Description Design RecordDo we understand the scope of the architectural task? What are the issues and findings that resulted?
MVp-03Requirements & StandardsHave all the constraints been identified?     What constraints/ requirements through normative documents/standards apply (or will apply) to the system, project, enterprise?
MVp-04AssuranceWhat are the claims made? What is the basis of the claim? Is the claim supported by evidence?



Category:Framework -> Viewpoint



© 2010 Eclectica Systems Ltd.