Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

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.   It is expected that the divisional architecture representatives will engage technical experts within their divisions as necessary to work on projects and issues.

Current Status

Week Ending

Description

10/3/2008

Staff were very busy during August and September, so we canceled a few of our bi-weekly meetings due to insufficient attendance.   We were able to meet a few times to discuss the upcoming QBR process (and the need to collect architecture inventory data), as well as plans to be involved in the architectural vetting of the proposed architecture in the Ensemble project.    For the next few weeks (beginning with our 10/7 meeting) we will have Keshav Santi from Identity Management and Jim Howell from S&O visiting our meeting to give us an update on architectural plans for Ensemble.   CCDAT will evaluate the proposed architecture against our own knowledge of existing architecture in our respective divisions and identify any impacts we see Ensemble having on existing systems. 

8/1/2008

Architecture Report presented at SRM.   SRM likes the report and approved adding information about the architecture inventory to the QBR process starting with the FY09 Q1 QBR.    CCDAT will need to work on refining the process by which this data is collected!
Additionally, CCDAT is being asked to take part in vetting the architecture design for the Ensemble (formerly PEP) project.   More information will follow as it becomes available!

July-August 2008

During these two months I have worked with the Architecture Committee to draft an "Architecture  Report" from the data obtained in the Architecture Inventory exercise.  The focus is on identifying (and grouping) technologies in their various stages of "support" so we can get a better picture of "where we are".  The report currently focuses on four areas:

  1. What technologies are we "fully invested in" for the next three years?
  2. What technologies are we "fully maintaining" for the next three years?
  3. What technologies are being phased out in the next three years?
  4. What technologies are being deployed in the next three years?

Architecture Inventory

The official confluence page for CIT's Architecture Inventory is now availble.

Refinements

Scope:

Architecture is the high-level definition of the structure of a system, which is comprised of parts, their interrelationships, and externally visible properties.  This team will focus on Enterprise Technical Architecture which is defined as the description of the current and/or future structure of an organization's:

...

  • ATA - Ron DiNapoli (chair)
  • ATSUS - Todd Maniscalco
  • IS - Donna Taber, Rick JonesSteve Barrett
  • NCS - Eric Cronise
  • OIT - Mark Mara, Jim Haustein
  • Security & IdM - Steve Edgar
  • S&O - Don Mac Leod Laurie Collinsworth 

Suggested Approach:

Start with a product, such as BlackBoard, and trace the  architectural dependencies.

...