Polley's original charge
We should designate at least one person from each operating division (S&O, NCS, IS, ATSUS, Security) to serve as the chief architecture planner for that division. These people should serve together on a CIT Cross Divisional Architecture Team, to be chaired by the Director of Advanced Technology and Architecture. This team will be tasked with developing our architecture plans, standards and vetting cross-divisional IT issues. The members of the team will each have a dotted line report to the Director of ATA for purposes of work on this team. It is expected that the divisional architecture representatives will engage technical experts within their divisions as necessary to work on projects and issues.
Modified Charge
Scope:
Enterprise Technical Architecture is the description of the current and/or future structure of an organization's:
-
- Hardware, platforms, and hosting: servers, and where they are kept
- Local and wide area networks, Internet connectivity diagrams
- Operating System
- Infrastructure software: Application servers, DBMS, etc..
Enterprise Architecture is generally defined in terms of its constituent architectures, namely:
- Business architecture
- Application/software architecture
- Technology/infrastructure architecture
- Information architecture
A fairly general definition of architecture in the system space (versus civil or building architectures), is:
Architecture is the high-level definition of the structure of a system, which is comprised of parts, their interrelationships, and externally visible properties.
With this definition in mind, it is all the more obvious that Enterprise Architecture is more than the collection of the constituent architectures (Business, Application, Technology, and Information). The interrelationships among these architectures, and their joint properties, are essential to the Enterprise Architecture. That is to say, these architectures should not be approached in isolation. Together, they are intended to address important Enterprise-wide concerns, such as:
- meeting stakeholder needs
- aligning IT with the business
- seamless integration and data sharing
- security and dependability
- data integrity, consistency
- reducing duplication
Treating the Enterprise as a system, means taking the interactions among the constituent architectures into account. By the same token, the whole point of breaking a system into parts is so that task is less overwhelmingly complex, and specialists can focus on the parts and make progress.
Goals:
- Develop and publish a model of our current sate
- Develop and and evolve and model of the desired future state
- Articulate evangulize a shared vision of the future
Organizational Impact:
It will be the responsiility od ther Directord to review they progam oplans in the context of
When making decisions aon resource alloaction (portolio management) SRM will place considerable weight on wether or not the project or proporal moves us towards our desirde state
Team Makup:
One represenitive from each operational dividion will be designiated chief architecture planner for that division and be the primary represinitive on the Cross Divisionsl Architecture Team (CDAT). Each resentitive is expected to be dedicating at least 10% of their time to this effort. They will bve responsibil for aquiring and maintainig knoledge of the techncial and produc architecuere used across their division.
Each division Director will submitt their intended representitive(s) to SRM. SRM will make the final decision on membership.
Use