Your SlideShare is downloading. ×
Bridging the gap between an enterprise and its projects ...
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Bridging the gap between an enterprise and its projects ...

560
views

Published on

Published in: Education, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
560
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
38
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Bridging the gap between an enterprise and its projects : Using the Zachman Framework to define IT Architecture KnowFuture - Event Bridging the gap Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 2
  • 2. Bridging the gap between project : Architecture Management with the Zachman Framework Our Main Message Architecture Management with the Zachman Architecture Management with the Zachman Framework :: Framework – bridges the gap between an enterprise and its bridges the gap between an enterprise and its projects projects – supports management of complexity (when you supports management of complexity (when you have to make several packages (and/or in-house have to make several packages (and/or in-house developed applications) working together) developed applications) working together) Grégory Grin 21-Jan-2004 3 Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 4
  • 3. Bridging the gap between project : Architecture Management with the Zachman Framework Do you know the spaghetti syndrome? Grégory Grin 21-Jan-2004 5 Bridging the gap between project : Architecture Management with the Zachman Framework The story starts like this…. Day 1 I have a great idea for a new customer That will be a very product great and advantageous product. We want to launch it in 2 weeks!! We have 2 weeks, let’s build a product-specific solution... Grégory Grin 21-Jan-2004 6
  • 4. Bridging the gap between project : Architecture Management with the Zachman Framework … continues like this…. Day 2 I have a great idea for a new customer That will be a very product great and advantageous product. We want to launch it in 2 weeks!! We have 2 weeks, let’s build a product-specific solution... Grégory Grin 21-Jan-2004 7 Bridging the gap between project : Architecture Management with the Zachman Framework ...And continues again… and again... Day n Day 1 Grégory Grin 21-Jan-2004 8
  • 5. Bridging the gap between project : Architecture Management with the Zachman Framework ...And finally : The technical landscape is like a big spaghetti plate! 2 weeks? Forget it !! § Applications were built one-at-a-time for individual product Spaghetti landscape § Each application was its own center of the universe No architecture Interfacing was a necessary afterthought § Each application’s architecture has its own presentation, logic, and data layers § Many applications have their own security models and log- ins § Files and databases are islands and often store redundant data that is already stored in other files and databases …etc..etc… At each time we have to make a change we have to touch everything and we need a lot of time and resources ! Grégory Grin 21-Jan-2004 9 Bridging the gap between project : Architecture Management with the Zachman Framework In other words : § Projects work under high pressure : the product is for next week § Projects are focused in meeting deadlines, which is good by the way... ð This create an unavoidable trend to build solutions that are project specific : “vertical solutions” ð At a point of time, the technical landscape is like a big spaghetti plate… and nobody takes care about the end-to- end architecture! Grégory Grin 21-Jan-2004 10
  • 6. Bridging the gap between project : Architecture Management with the Zachman Framework But, in the meantime, everybody wants : Reduced time-to-market, Reduced time-to-market, Reduced time-to-market, Reduced time-to-market, Reduced time-to-market, Reduced time-to-market, alignment, alignment, alignment, alignment, alignment, alignment, integration, integration, integration, integration, integration, integration, flexibility, flexibility, flexibility, flexibility, flexibility, flexibility, interoperability, interoperability, interoperability, interoperability, interoperability, interoperability, quality, quality, quality, quality, quality, quality, seamlessness, seamlessness, seamlessness, seamlessness, seamlessness, seamlessness, adaptability, adaptability, adaptability, adaptability, adaptability, adaptability, user-friendliness, user-friendliness, user-friendliness, user-friendliness, user-friendliness, user-friendliness, usability, usability, usability, usability, usability, usability, reusability, reusability, reusability, reusability, reusability, reusability, security….. security….. security….. security….. security….. security….. How can we get this from spaghetti ? Grégory Grin 21-Jan-2004 11 Bridging the gap between project : Architecture Management with the Zachman Framework Solution? “We need a managed Architecture” § In other words : – We need an Architecture – We need to manage it Grégory Grin 21-Jan-2004 12
  • 7. Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 13 Bridging the gap between project : Architecture Management with the Zachman Framework Swisscom Mobile § The leading mobile phone operator in Switzerland § 66% market share with 3.675 M customers and 2600 points of sales § 2002 revenue: 4112 Mio CHF § 2400 employees § 75% Swisscom AG, 25% Vodafone Group The Swisscom Group § Switzerland´s leading telecom company § Positioned as the leading provider of mobile and fixed voice and data services and Internet-based services. § Offers a comprehensive range of telecom products and services § 2002 revenue: 14,52 Billion CHF § 20,470 employees Grégory Grin 21-Jan-2004 14
  • 8. Bridging the gap between project : Architecture Management with the Zachman Framework What does Swisscom Mobile provide? § Phone calls, short message service (SMS), voice mail § Add-on services : – roaming (phone calls when you are in other countries), fax and e-mails (unified messaging), call forwarding, teleconferencing… – Mobile phone (micro)payment § Third party content: railway timetables, stock prices, weather, bank account information, portal of services § Business services : Corporate Mobile Network, Mobile Office, Machine-to-machine mobile data communication § Public Wireless LAN § Multimedia messaging, WAP surfing § Games – downloadable and on-line § Prepaid and post paid billing § … and more Grégory Grin 21-Jan-2004 15 Bridging the gap between project : Architecture Management with the Zachman Framework Functional layers End-user Applications Business Business Multimedia messaging, WAP portals,Games, Chat, Support Support Third party information services, Corporate Mobile Office... Management Layer Delivery Services Delivery Services CRM, CRM, Rendering, Personalization, Service creation environment... Rendering, Personalization, Service creation environment... Billing, Billing, Provisioning, Provisioning, Finance, Finance, Supply Chain, Supply Chain, Product Product Enabling Services Enabling Services Management... Management... User identification, Authentication, Real-time billing interface, User identification, Authentication, Real-time billing interface, network gateways... network gateways... Network Network Circuit switches, Packet switches (GPRS), Public Wireless LAN, Circuit switches, Packet switches (GPRS), Public Wireless LAN, UMTS... UMTS... Grégory Grin 21-Jan-2004 16
  • 9. Bridging the gap between project : Architecture Management with the Zachman Framework Strategic Issues § For a mobile phone company, technology is not business support or a business enabler - it is the business § Telecom technology vendors have a dominant role in the industry § Core technology and services are very standardised and well-served by package vendors § Competition is in emergent value-added services: – It isn’t feasible to develop in-house what you need to build them - you base them on packages – Development is mostly about configuring packages and making them work together. Grégory Grin 21-Jan-2004 17 Bridging the gap between project : Architecture Management with the Zachman Framework Strategic Impact of Packaged Solutions You can’t get everything It’s vital to make the right The effects are not limited to right - some solutions won’t choices for selection of the value-added services. work as well as you packages and their Underlying technology can expected, some vendors will accompanying technology, be affected, business support go out of business, some and for business systems (CRM, provisioning, solutions will be overtaken partnerships with package billing ...) have to handle the by better ones from vendors changes competitors You need an architecture that is not specific to the packages you currently use - an architecture where you can swap old solutions for better ones. Grégory Grin 21-Jan-2004 18
  • 10. Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 19 Bridging the gap between project : Architecture Management with the Zachman Framework Architecture Management@Swisscom Mobile § Define and manage technical Architecture processes within the company § and manage technical Architecture processes within the company § Develop and maintain technical information (conceptual level) § and maintain technical (conceptual level) § Define target Architecture including guidelines, principles and roadmap § Define target Architecture including guidelines, principles and roadmap § Ensure synchronisation between Architecture roadmap and platform roadmaps § synchronisation between Architecture roadmap and platform roadmaps § Control & report on Architecture & Security compliance of solution implementations § Control & report & Security compliance of solution implementations § Define Security concepts. Co-ordinate, report & escalate. Responsibility is share with SCM line § Define Security concepts. Co-ordinate, report & escalate. Responsibility is share with SCM line organisation organisation § Provide support to the line in understanding Architecture & Security processes and content (End-to- § Provide support to the line in understanding & Security processes and content (End-to- End Architecture & Security) End & Security) § Support platform introduction decision according to company priorities § Support platform introduction decision according to company priorities Grégory Grin 21-Jan-2004 20
  • 11. Bridging the gap between project : Architecture Management with the Zachman Framework End-to-end architecture management End-user Applications Business Business Support Support Multimedia messaging, WAP portals,Games, Chat, Third party information services, Corporate Mobile Office... § We define how to integrate systems and capabilities for the greater good CRM, CRM, of the enterprise, consistently from an Application Service and Billing, Billing, Provisioning, Provisioning, end-to-end perspective : From the Application Service and Enabling Services Enabling Services Finance, Finance, Supply Chain, Supply Chain, end-user application to the network Management Layer Product Rendering, Personalization, Service creation environment… Rendering, Personalization, Service creation environment… Product Management... Management... element, through business support User identification, Authentication, Real-time billing interface, User identification, Authentication, Real-time billing interface, network gateways... network gateways... systems. § We ensure consistency between the Core Network Core Network Circuit switches, Packet switches architecture layers (e.g : between Circuit switches, Packet switches Core Network and Enabling) and detect potential conflicts between roadmaps of evolution of different Radio Access Network Radio Access Network domains GSM Cell, Pwlan Cell, UMTS Cell... GSM Cell, Pwlan Cell, UMTS Cell... Grégory Grin 21-Jan-2004 21 Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 22
  • 12. Bridging the gap between project : Architecture Management with the Zachman Framework Starting point § The basic ideas :: The basic ideas – Define how to integrate systems and capabilities for the greater good of the enterprise – Define how to integrate systems and capabilities for the greater good of the enterprise – Define target architectures and roadmaps – Define target architectures and roadmaps – Synchronise architecture roadmaps with platform roadmaps – Synchronise architecture roadmaps with platform roadmaps – Support projects in identifying platform impact and designing solutions compliant with the – Support projects in identifying platform impact and designing solutions compliant with the architecture architecture – Review projects in terms of alignment against the defined architecture – Review projects in terms of alignment against the defined architecture § Findings :: Findings (We need :) – Descriptions of current (over time changing) and target architectures, which must :: – Descriptions of current (over time changing) and target architectures, which must – Provide reference and content – Provide reference and content – Support control of project architecture compliance – Support control of project architecture compliance – Architecture Management standardised processes and activities, using this Reference – Architecture Management standardised processes and activities, using this Reference Architecture Architecture Grégory Grin 21-Jan-2004 23 Bridging the gap between project : Architecture Management with the Zachman Framework Starting point and guide : The Zachman Framework § A framework is a classification scheme that § A framework is a classification scheme that enables focused concentration on selected aspects enables focused concentration on selected aspects of subject or object. of subject or object. § It is useful for :: § It is useful for – simplify for understanding and – simplify for understanding and communication communication – clearly focus on independent variables for – clearly focus on independent variables for analytical purposes analytical purposes – maintained a disciplined awareness of – maintained a disciplined awareness of contextual relationships that are significant contextual relationships that are significant to preserve the integrity of the object to preserve the integrity of the object § The Zachman Framework is a classification scheme for descriptive representations of complex § The Zachman Framework is a classification scheme for descriptive representations of complex objects. objects. § It is generic and can be used to classify the descriptive of any object :: an enterprise, a product... § It is generic and can be used to classify the descriptive of any object an enterprise, a product... Grégory Grin 21-Jan-2004 24
  • 13. Bridging the gap between project : Architecture Management with the Zachman Framework Grégory Grin 21-Jan-2004 25 Bridging the gap between project : Architecture Management with the Zachman Framework The Zachman Framework for Enterprise Architecture : Fundamentals § Use the Framework as a classification scheme for descriptive representations of an Enterprise § Different perspectives – Planner : Objectives / scope – Owner : Model of business – Designer : Model of information system – Builder : Technology Model – Sub-contractor : detailed representation § Different abstractions (different ways to describe the enterprise) – What : Material description - Data – How : Functional description - functions and processes – Where : Spatial description - Flows – Who : Operational description - People / workflow – When : Timing description - Dynamics / Events – Why : Motivation description - Strategies Grégory Grin 21-Jan-2004 26
  • 14. Bridging the gap between project : Architecture Management with the Zachman Framework The Zachman Framework for Enterprise Architecture : Fundamentals Rules of the framework § Do not add rows or columns to the framework § Each column has a simple generic model § Each cell model specialises it’s column generic model § Level of detail is a function of a cell not a column § No meta-concept can be classified into more than one cell Grégory Grin 21-Jan-2004 27 Bridging the gap between project : Architecture Management with the Zachman Framework Scope What What How How Where Where Who Who When When Why Why Scope Scope Business Business Model Model Logical Logical Design Design Physical Physical Design Design Components Components Functioning Functioning System System § The Zachman framework is not an architecture. It is a classification scheme for organising and managing architecture. We are using it as our reference framework: – To organise the perspectives and aspects of the architecture we have identified – To organise what we already have, look for gaps, identify what we need, and prioritise Grégory Grin its development 21-Jan-2004 28
  • 15. Bridging the gap between project : Architecture Management with the Zachman Framework Two Frameworks Guidance Architecture Reference Architecture Reference Guidance Products What How Where Who When Why Guidance Products How to build and How to build and maintain enterprise Logical maintain enterprise products products Physical How to review How to review project deliverables project deliverables Support & Constrain Improve & Extend How to support How to support projects projects Project Project Products What How Where Who When Why Products Logical Physical Project reviews Project Guidance Project Guidance How to develop How to develop project products project products Project lifecycle Project lifecycle Grégory Grin 21-Jan-2004 29 Bridging the gap between project : Architecture Management with the Zachman Framework Two Frameworks Architecture Framework Project Framework § Contains descriptions of project deliverables, which may be composites i.e. may span more § Contains reference products that together than one Framework cell define the overall architecture § Descriptions of deliverables are not prescriptive § Each reference product is primitive and but there is guidance on what kinds of contained within one Zachman cell deliverable would be expected in different types of project § Reference products grow incrementally as projects gradually realize the target § Framework cells define characteristics and architecture properties that must be present in the deliverables to establish architectural compliance § Projects produce deliverables that meet the framework specifications Grégory Grin 21-Jan-2004 30
  • 16. Bridging the gap between project : Architecture Management with the Zachman Framework Architect’s roles in projects § Consultant to Solution Architect – second opinion on solutions § Consultant to Solution Architect – second opinion on solutions § Support for defining project-specific instance of framework: § Support for defining project-specific instance of framework: – Kinds of deliverable recommended: may be composites – Kinds of deliverable recommended: may be composites – Required properties of deliverables [“You should be able to – Required properties of deliverables [“You should be able to answer these questions”]: based on reference products, answer these questions”]: based on reference products, specific to Framework cells specific to Framework cells § Support of project team during development: § Support of project team during development: – Using reference products as sources of content – Using reference products as sources of content – Using reference products as constraints – Using reference products as constraints § Assessment of architectural compliance § Assessment of architectural compliance Grégory Grin 21-Jan-2004 31 Bridging the gap between project : Architecture Management with the Zachman Framework Where have we got to ? § Initial decision: start with CRM and EAI Bus § One year architecture program management - established control and consistency over initial projects § Creation of an architecture governance process § Selection of the Zachman Framework Coaching / mentoring § Creation of architecture definition within the Framework approach with § Development of guidance Know – for using the architecture definition in projects Gravity – for ensuring compliance of projects with the architecture § Applying the guidance on projects Grégory Grin 21-Jan-2004 32
  • 17. Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 33 Bridging the gap between project : Architecture Management with the Zachman Framework Step 1 : take into account issues due to the specific context (1) Issue Solution Approach Framework There is an “ideal” set of packages that Drive the logical application architecture from business requirements Logical and would match closely the capabilities of Maintain mappings to both target and current physical application physical "How" the conceptual applications - but this set architecture models is a moving target Maintain detail of physical architecture in current – keep the target definition “light” Delivering required functional capabilities Make selections and use the Framework to ensure they are applied Logical and using the facilities of the available consistently physical "How" packages - may have options to map and “Why” functions to more than one package. models Packages need to support business view Enterprise Data Model visible to Business Model owners & mapped to Logical and of data application package databases physical “What" models Many applications need their own Enterprise Data Model mapped to package data bases. Logical and databases and some data has to be Primary owner application defined for replicated data physical “What" replicated Replication defined and managed in physical models models, Physical “Where” model Grégory Grin 21-Jan-2004 34
  • 18. Bridging the gap between project : Architecture Management with the Zachman Framework Step 1 : take into account issues due to the specific context (2) Issue Solution Approach Framework Swappable solutions enabled by EAI Enterprise Message Model to control that the EAI Bus is used Logical and consistently across projects. physical “Where" models It is not possible to phase everything to fit Interim solutions are swapped in and out in the same way as Physical “What”, neatly over time. We have to develop replacement of parts of the current architecture by parts of the target "How" and interim solutions in some areas. architecture “Why” models Neither projects nor application support End-to-end workflow models (with both human and automated Logical and teams have the end-to-end view of actors) are built, and kept consistent with the “How” and “Where” physical “Who" support for business processes models. These models are owned by the architecture team, and kept models, in step with the end-to-end view of business process in the business models There are many constraints on the use of Design decisions (and the rationales for them) and package Physical “What“, packages. Some are inherent in the constraints are documented in the “Why” column. “How” and packages themselves and some resulting They result in constraints and guidance that impact other columns, “Why” models from Swisscom Mobile design decisions especially “What” and “How”. It’s vital to make this information readily available to projects in concise form. Grégory Grin 21-Jan-2004 35 Bridging the gap between project : Architecture Management with the Zachman Framework Step 2 : define the Reference products What How Where Who When Why Logical Enterprise Conceptual Entity Message Data Application Logical Behaviour Model Logical Logical Model (EDM) Architecture Workflow models Architecture Design Logical Rules Logical Data Data Actors Business Event Message Catalog Ownership Catalog Catalog Physical Message Application Current Application Model Package DB and Target Package Physical Specifications Application Constraints Physical Enterprise Design Architectures System Event Message. Workflow EDM Mapping Catalog Permitted Catalog Model . Physical Technologies Data Catalog Master/Slave & Tools Integration Mapping Relationships Manager Specification Grégory Grin 21-Jan-2004 36
  • 19. Bridging the gap between project : Architecture Management with the Zachman Framework Simplified Meta-model of Reference Products Logical View (Row 3) Physical View (Row 4) Grégory Grin 21-Jan-2004 37 Bridging the gap between project : Architecture Management with the Zachman Framework Simplified Meta-model of Reference Products Logical View (Row 3) The concept is that each cell in the reference framework The concept is that each cell in the reference framework should be a view of a single underlying repository should be a view of a single underlying repository We have quite a way to go on this ––still using Access, We have quite a way to go on this still using Access, Excel, Visio, Word (& some UML tools) Excel, Visio, Word (& some UML tools) Physical View (Row 4) Grégory Grin 21-Jan-2004 38
  • 20. Bridging the gap between project : Architecture Management with the Zachman Framework Step 3 : Build reference products Examples of reference products Examples of reference products § Enterprise Data Model § Logical Data Catalogue § Enterprise Message Model Grégory Grin 21-Jan-2004 39 Bridging the gap between project : Architecture Management with the Zachman Framework Roles of Enterprise Data Model § The Enterprise Data Model (EDM) is a tool for defining a set of concise, unambiguous, stable, and IT-independent definitions of an organisation's information resources. It specifies: – The significant objects that an organisation needs to hold information about (these are called entities) – The way that these objects relate to each other, (these are called relationships) – The key facts that the organisation wants to know about these objects (these are often called attributes) – The business rules that govern the relationships between these objects § Enables: – Selection of packages that support business views of the data – Mapping those views to the packages’ databases § Supports “primary ownership” of data by conceptual applications - is basis for master/slave data relationships in physical design § Also used by business people (row 2 owners) for reference Grégory Grin 21-Jan-2004 40
  • 21. Bridging the gap between project : Architecture Management with the Zachman Framework Reference Product: Enterprise Data Model Informal Informal Overview Overview Grégory Grin 21-Jan-2004 41 Bridging the gap between project : Architecture Management with the Zachman Framework Logical Data Catalogue § The primary purpose of the Logical Data Catalogue is to identify reusable logical groups of data across the whole SCM Architecture on a logical (conceptual) level. In contrast to the physical (technical) level, the logical (conceptual) level : – is completely implementation independent, i.e. – clean of design decisions, such as application partitioning, data replication, etc. – not biased towards any specific technology, such as databases – is stated in a business readable manner § Data groups are “building blocks”, reusable across business objects, tables, and logical and physical messages § Mapping to messages and physical databases is managed by data group, not by data item Grégory Grin 21-Jan-2004 42
  • 22. Bridging the gap between project : Architecture Management with the Zachman Framework Logical Data Catalogue : Abstract Primary name Person Synonyms (none) Generalisation (none) Definition The representation of a natural person (human being). Item roles Data definition Definition Role constraints party Party Details about the person as a • mandatory party. id Person Identifier Identifier to uniquely identify • mandatory, many that person. name Person Name (as defined in data definition) • mandatory title Title (as defined in data definition) • optional, many gender Gender (as defined in data definition) • mandatory marital status Marital Status (as defined in data definition) • optional nationality Name The born nationalities of that • optional, many person. date of birth Date The official date when the • optional person was born. language Language (as defined in data definition) • optional occupation Occupation (as defined in data definition) • optional number of children cardinal The number of immediate • optional descendants of that person. Group constraints • (none) Structure LDC::Data Groups::Who - People & Organisations «datagroup» 1 0..1 «datag roup» Person Full Name «datag roup» Date name date of birth Person 1..* 0..1 «datagroup» «data type» Person Identifier id number of children cardinal * 0..1 «data item» title occupation «dataitem» Title Occupation marital status nationality 1 gender 0..1 * language 0..1 «data item» «dataitem» «data item» «dataitem» Gender Martial Status Name Language Sources • [EDM2] Grégory Grin 21-Jan-2004 43 Bridging the gap between project : Architecture Management with the Zachman Framework Data groups «data group» «data group» «data group» «business object» «business object» «business object» Bank Bank Account Billing Account text clearing code 1 * Name branch Account Number account number text account id Name account name «aspect» text sub account id «data group» text account type «data group» Date valid through Party (Bill Payer) text status «business object» Currency currency Timepoint last change «data group» boolean dunning deactivated 1..* * * 1 Organisation Date activation date «business object» boolean prepayment required Billing Account Group Organisation Identifier id monogamous Date deactivation date Organisation Type type Date suspension date «data group» «aspect» Name name Date reactivation date «business object» Party (Legally Responsible) Name registered Name Party 1..* 0..1 Bank Account financial profile Date date of incorporation * * subcontract Currency currency «data group» rational deposit «business object» rational balance «data group» «aspect» «aspect» «aspect» Contract 1 rational creedit thresholds «business object» Party (Subscriber) Party (User) Party (Orderer) Contract Number contract number Person 1 1..* * text contract type Person Identifier id text status * 1 Person Name name Timepoint last change «data group» Title title «business object» monogamous 0..1 Gender gender Price Plan Group Marital Status marital status * * Name nationality * * * 1 «data group» Date date of birth «business object» «data group» Subscription «business object» Language language * Order Occupation occupation Subscription Number subscription number text status Order Number order number «data group» cardinal number of children «business object» text status Price Plan Timepoint last change 1 1 * Informal Informal «data group» Physical Address «data group» * «data group» * 1 «data group» «data group» Overview «business object» «business object» «business object» «business object» Overview Credit Card Ordered Product Product Feature Country Code country * 1 1 Name city Name credit card name text status Postcode postcode text credit card number Timepoint last change 1 Name street Name credit card holder cardinal quantity Description house Date expiry date boolean replace * * Description appartment «data group» «business object» Product Component Grégory Grin 21-Jan-2004 44
  • 23. Bridging the gap between project : Architecture Management with the Zachman Framework Reference Product example: Logical Message Primary name Customer Address changed Type NoC Synonyms ADDRESS_M UTATION Generalisation (none) Definition One or more detail of the customer’s address has been changed Avg. Frequency 2000 per month Periodic: One Target: Transactional: X The primary purpose of Episodic: X Many Targets: X Non-transactional: Item roles Data definition Definition Role constraints the Enterprise Message person id Person Identifier Identifier to uniquely identify • optional Model is to identify the person who’s address has changed reusable message types organisation id Organisation Identifier Identifier to uniquely identify • optional across the whole SCM the organisation who’s ad- dress has changed Architecture on a change Change Type (as defined in data definition) • mandatory logical (conceptual) effective date Date The date on which the re- • mandatory level. quested change becomes valid. physical address Physical Address (as defined in data definition) • mandatory Group constraints • defined(person id) xor defined(organisation id) Producers • CRM Consumers • OM • Billing • Collection • Provisioning Grégory Grin 21-Jan-2004 45 Bridging the gap between project : Architecture Management with the Zachman Framework Agenda § Introduction : we need Architecture Management § The context § Architecture Management@Swisscom Mobile § The approach § Some practical experiences § Conclusions Grégory Grin 21-Jan-2004 46
  • 24. Bridging the gap between project : Architecture Management with the Zachman Framework Conclusions § The Zachman Framework provides a holistic view on the enterprise and helps to § The Zachman Framework provides a holistic view on the enterprise and helps to identify gaps identify gaps § The Zachman Framework is even then helpful, when you plan to use commercial § The Zachman Framework is even then helpful, when you plan to use commercial packages instead of developing the IT infrastructure by yourselves packages instead of developing the IT infrastructure by yourselves § Adapting the Zachman Framework to company-specific needs allows the definition of § Adapting the Zachman Framework to company-specific needs allows the definition of artefacts to be delivered by projects required for architecture governance artefacts to be delivered by projects required for architecture governance § Reference products provide a "quick-start" solutions for required artefacts § Reference products provide a "quick-start" solutions for required artefacts § Reference products are highly reusable and reusability should be a primary goal § Reference products are highly reusable and reusability should be a primary goal § § Project products are means to check architecture compliance Project products are means to check architecture compliance § § Projects must be treated as "customers" from the architectural governance Projects must be treated as "customers" from the architectural governance perspective perspective § A common language (such as UML) is very helpful § A common language (such as UML) is very helpful § Coaching/mentoring on Zachman and architecture is helpful and much more efficient § Coaching/mentoring on Zachman and architecture is helpful and much more efficient in changing the culture than direct support. in changing the culture than direct support. Grégory Grin 21-Jan-2004 47 Thank you for your attention Grégory Grin John Hall Head of Architecture Governance Consultant gregory.grin@swisscom.com john.hall@knowgravity.com