This page is published under the
terms of the licence summarized in the footnote.
This paper lists objects, structures and models for which detailed templates and guidance are offered in the training CD.
This paper does not cover architecture views (mappings between objects), meta models, repositories or document structures – all of which are addressed in other papers at ref 1.
|
Architecture precursors |
Business |
Information Systems &
Technology |
Management
|
|
Stakeholders |
Process |
Data |
Cost-benefit analysis |
|
Actor/stakeholder template |
Process map |
Data entity template |
RoI template |
|
Actor/stakeholder role template |
Use case template |
Business term glossary |
People cost view |
|
Concern |
Automated service template |
Data model |
Technology cost view |
|
Inputs |
Process diagrams |
Data source/store template |
|
|
Goal or requirement template |
Organisation |
Application |
Plans and governance |
|
Goal or requirements hierarchy |
Organisation/function
catalogue and template |
Application/component portfolio |
Migration path |
|
Goal or requirements traceability record |
Organisation/function structure |
Application template |
Project initiation document template |
|
Principle template |
|
Component template |
IT capacity plans |
|
Business rule template |
|
Applications architecture structure diagram |
Product structure |
|
Standards and other constraints |
Location |
Technology |
Activity structure |
|
A standards information base |
Location template |
Technology template |
Schedule charts |
|
Logical technical reference model |
Location type template |
Logical server template |
Governance |
|
Strategic technology policy template |
Location structure |
General device template |
|
|
Scope |
|
Server device template |
|
|
Context diagram |
|
Software layering diagram |
|
|
Input/output data flow template |
|
Logical platform configuration diagram |
|
|
|
|
Physical hardware configuration diagram |
|
|
|
|
Technical environments outline |
|
The table below presents a deliverable framework which helps to remind architects of the scope they may have to cover in any assignment. SISPOLDATM is an acronym drawn from the headings in the table above, which maps roughly to the rows of the table below. This is only a mental model, not an index or a normalised structure.
|
|
The scope of architecture work: a
reminder of what needs to be considered |
|||
|
SISPOLDATM |
Business |
IS development |
IT architecture |
IT operations |
|
Stakeholders |
Customers, suppliers, employees etc. |
Application users, maintainers etc. |
IT users, operators etc. |
IT users, suppliers etc. |
|
Inputs |
Business goals, constraints & standards |
Application requirements constraints & standards |
SLRs, constraints & standards |
SLAs |
|
Scope |
Human activity systems |
Information systems |
Infrastructure systems |
Infrastructure operations |
|
Processes |
Business processes, use cases & automated services |
Development processes, patterns & standards |
IT architecture definition |
ITIL processes |
|
Organisations |
Business departments |
IS department |
IT department |
IT services management |
|
Locations of |
Customers, suppliers & employees |
Application users & developers |
Data centers & client devices |
Data centers & client devices |
|
Data |
Products, services & information of all kinds |
Databases & I/O formats |
System management data, thresholds, back up |
Change requests, incident logs etc. |
|
Applications |
Business units and functions |
Applications & components |
Hardware & platform software |
Configured environments |
|
Technologies |
Business environment & equipment |
Development & test environments |
Production environment & DR environment |
System management tools |
|
Management |
Business change estimates & plans |
IS change estimates & plans |
IT change estimates & plans |
IT change management |
Ref 1: other papers in the library at http://avancier.co.uk
Footnote: Creative Commons
Attribution-No Derivative Works Licence 2.0
Attribution: You may copy, distribute
and display this copyrighted work only if you clearly credit “Avancier Limited:
http://avancier.co.uk” before the start
and include this footnote at the end.
No Derivative Works: You may
copy, distribute, display only complete and verbatim copies of this page, not
derivative works based upon it.
For more information about the
licence, see http://creativecommons.org