User feedback for Technology Tamed "Useful Links" page and expansion of Twitter tweets -- To leave a comment, click one of the the "comments" links above a post; Enter your text; -- If you're not a registered Blogger, select "Other" and leave your name; Preview then Publish your comment.
moved PasswordKeeper under all three OS's (7/8.1/10)
set up Shotty screen capture under all three OS's (7/8.1/10)
reinstalled DesktopOK layout manager under Win7 and Win8.1
reinstalled WinZip under all three OS's (7/8.1/10)
moved Watts Clever USB energy monitor to Win7
moved my Kiwi Syslog server to Win7
reinstalled MUM- Internode's Monthly Usage Meter under 7 and 8.1 and partially successfully under Win10 (won't return LAN card throughput since recent Win10 update)
moved the Aurora Communicator software for our solar generator to run under Win7
installed IP Camera Viewer under all three OS's (7/8.1/10)
reinstalled FileZilla FTP server under Win7
One failure was the redeployment of the Temper USB temperature probe software which had to be substituted with ThermoHID
An additional success was a successful reinstall of the long-time failed USB-UIRT remote control sender/receiver product under Win7
To anyone studying for their TOGAF 9 exams who happens to drop by, this page is just my collection of:
sites I found,
notes I made,
excerpts I copied,
abbreviations I made,
key text I highlighted,
acronyms I came up with
... anything to help me remember the sheer volume of (in my view - pointless) variances and nuances of "According To TOGAF " for the multi-choice Part 1 exam.
Part 2 - Scenarios are relatively easy in my view, because you are applying the process and principles but the Part One which has questions which for a couple I cannot find any DIRECT ANSWER (i.e. the answer is an extrapolation of knowledge) either in the TOGAF documentation or from Google searches ... that's an entirely different thing! I got very frustrated trying to learn this stuff!
e.g. How do you arrive at answer D for this question?
Which of the following correctly defines the Organisation category in the Architecture Content Framework?
a) Organisation, Location and Capabilities
b) Actor, Location, Role and Capabilities
c) Requirements, Actor and Function
d) Location, Actor, Role, and Organisation
e) Actor, Location and Structure
Option D. See TOGAF: Content Metamodel. Organisation, Location, Actor and Role form the Organisation category.
... eventually ... knowing the answer ... I was able to find it buried in this diagram
... nor can I see anywhere that clearly describes:the reasons for establishing an Architecture Board
i.e. TOGAF states that establishing and operating an Architecture Board is
more than offset by the savings accrued from preventing one off
solutions and unconstrained development. Which of the following answers
does TOGAF not state as a reason for establishing an Architecture Board?
a) Higher risk
b) High cost of operation and support
c) High costs of development
d) Lower quality
e) Better understanding of the business and their requirements
Double negatives are also common:
Which of the following is incorrect when describing Architecture Deliverables?
a) Architecture Deliverables contain Artifacts correct
b) Artifacts within deliverables may include Catalogs, Matrices and Diagrams correct
c) An Architecture Definition Document is an architectural deliverable correct
d) Architecture Deliverables may be composed of more than one artifact correct
e) Deliverables cannot be used as building blocks ... cannot is incorrect so deliverables CAN be used as building blocks
Logically Option E. as options A-D are definitely valid.
Then there are subtle questions like:
2 - Which one of the following is not a characteristic of a building block?
Choose one of the following answers
You skim thru the question and they are ALL correct !
... until you realise Buses the word cannotnot can
Anyhow ... on to my scruffy notes ... just in case they help anyone else with their TOGAF study
Technical
requirements - identifying, categorizing, and prioritizing the
implications for work in the remaining architecture domains; for
example, by a dependency/priority matrix (for example, guiding trade-off
between speed of transaction processing and security); list the
specific models that are expected to be produced (for example, expressed
as primitives of the Zachman Framework)
The
implemented system is actually an output of the development process.
However, given the importance of this output, it is stated here as an
output of the ADM. The direct involvement of architecture staff in
implementation will vary according to organizational policy, as
described in Part VII, 50. Architecture Governance.
Populated Architecture Repository
Architecture compliance recommendations and dispensations
Implementation Governance Model - how
the Transition Architecture that implements the architecture will be
governed through implementation. Typical contents of an Implementation
Governance Model are:
Governance processes
Governance organization structure
Governance roles and responsibilities
Governance checkpoints and success/failure criteria
Architecture Repository - made up of:
Metamodel, Capability, Landscape, (Ref)Library, (Gov)Log, SIB MetaCap(pause) Lanscape,Library,Log n' SIB
PCRF or ProcConRepoFlow - Process, Content, Repository, process Flow control
Concern vs Requirement - concern=key interests crucially important to stakeholders, determine acceptability of the system. requirement=statement of need that must be met by a particular architecture
What to ABB's "do" -
describe required capability of a single aspect of the overall model
capture architecture requirements
Capability Assessment
TRM - what is it - provides a model and taxonomy of generic platform services
has two main components:
A taxonomy, which defines terminology, and provides a
coherent description of the components and conceptual structure of an
information system
A TRM graphic, providing a visual representation of the taxonomy, to aid understanding
TRM services
Data Interchange
Data Management
Graphics and Imaging
International Operation
Location and Directory
Network
Operating System
Software Engineering
Transaction Processing
User Interface
Security
System and Network Management
III-RM - what is it - a subset of the TRM in terms of overall scope,
but expands certain parts of the TRM - in particular, the
business applications and infrastructure applications parts to help in design of an Integrated Information Infrastructure to enable Boundaryless Information Flow.
The core components of the III-RM are:
Business Applications
Brokering
Information Provider
Information Consumer
Infrastructure Applications
Development Tools
Management Utilities
Application Platform
Interfaces used between the components
Qualities the Application Software and Application Platform must adhere to
Value Chain - phase A - high-level view
of an enterprise and how it interacts with the outside world, focuses
on presentational impact so all participants understand the high-level
functional and organizational context of the architecture engagement
Transition states
Architecture
Contracts - Joint agreements between development partners and sponsors
on the deliverables, quality, and fitness-for-purpose of an
architecture.
Architecture Contracts may occur at various stages of the Architecture Development Method:
Statement of Architecture Work created in Phase A
The development of one or more architecture domains (BDAT) will normally be governed by an Architecture Contract
At the beginning of Phase G between the
architecture function and the function responsible for implementing the
enterprise architecture (In larger-scale implementations, there may well be one Architecture Contract per implementation team)
At the end of Phase G between the architecting function and the business users who will
be building and deploying application systems
They provide:
continuous monitoring to check integrity, changes, decision-making, and audit of all architecture-related activities
Adherence to principles, standards, and requirements of the existing or developing architectures
Identification of risks in all aspects of the development and implementation of the architecture(s)
accountability, responsibility, and discipline with regard to the development and usage of all architectural artifacts
formal
understanding of the governance organization responsible for the
contract, their level of authority, and scope of the architecture under
the governance of this body
The 7 parts of TOGAF - I, A, GT, Cont - EC n' T, RM n' Cap - 1.Intro, 2.ADM, 3.AG&T, ACF(content),Ent Contin, RefMod, ACF(capability)
(learn as a rhythm: IA (pause) GTcont (pause) EC'n'T (pause) RM'n'Cap)
ADM Guidelines and Techniques - Part III
Iteration - has 4 common sub-iterations CDTG
Prelim~A & Prelim~H (Context/Capability)
B~F and intra_B~D (Development)
E~F (Transition)
G~H (Governance)
Application - will occur
at Strategic, Segment & Capability levels SSC/BDTR
across Subject areas (Breadth), to varying Detail (Depth), for duration's (Time) dependent on Breadth & Depth of the described architecture. Accuracy has a bell-curve depending on Recency, where an architecture decreases in accuracy if not actively maintained.
Security
Often treated as a separate architecture domain within the EA while needing to be fully integrated in it.
has its own discrete methodology, views and viewpoints.
Security considerations have an impact on Phases A to H
Governing SOA's
- Enterprise architecture provides frameworks, tools, and techniques to
assist organizations with the development and maintenance of their SOAs
Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support.
Enterprise
principles provide a basis for decision-making throughout an
enterprise, and inform how the organization sets about fulfilling its
mission.
Architecture principles govern the architecture process
Structure
Name - represent the essence of the rule and be easy to remember
Statement - succinctly and unambiguously communicate the fundamental rule.
Rationale - highlight the business benefits of adhering to the principle
Implications - Should highlight both business and IT requirements for carrying out the principle - in terms of resources, costs, and activities/tasks
Stakeholder Management
- Support from the more powerful stakeholders will help the engagement
win more resource, thus making the architecture engagement more likely
to succeed.
Patterns - Building
blocks are what you use: patterns can tell you how you use them, when,
why, and what trade-offs you have to make in doing so.
Business Scenarios -
Gap Analysis
Migration Planning Techniques
Interoperability Requirements
Business Transformation Readiness Assessment
Risk Management
Capability-Based Planning
Content vs Capability frameworks -
Techniques for Architecture Development
Architecture Principles
Stakeholder Management
Architecture Patterns
Business Scenarios
Gap Analysis
Migration Planning Techniques
Interoperability Requirements
Business Transformation Readiness Assessment
Risk Management
Capability-Based Planning
NO CHANGE MANAGEMENT !
Boundaryless Information Flow - access
to integrated information to support business process improvements -
multiple sources of information securely delivered in the right context,
when/where-ever needed
The key point of the ADM cycle is to focus on what creates value to the enterprise, and to select horizontal and vertical scope
Incorrect reasons for limiting architecture scope
inflexibility of the baseline IT technical architecture
The relationship between the Architecture Continuum and
the Solutions Continuum is one of Guidance, direction and supportGDS
Definition of the Organisation category in the AContF - LARO Location Actor Role Organisation
