Appendix F Enterprise Architecture Artifacts

Transcription

1 Appendix F nterprise Architecture Artifacts he following is a list of the A artifacts that are recommended for use when documenting an enterprise using the A 3 ube Framework. xamples of each artifact are provided on following pages. A 3 ube Level/hread trategic (I) Business (B) (D) (A) s & (I) ecurity () tandards () Workforce kills (W) Artifact ID # Artifact ame (* omposite Artifact) -1 trategic lan* -2 W Analysis -3 oncept of perations cenario -4 oncept of perations Diagram -5 Balanced corecard * B-1 Business lan* B-2 ode onnectivity Diagram B-3 wim Lane rocess Diagram * B-4 Business rocess/ervice odel B-5 Business rocess/ roduct atrix * B-6 Use ase arrative & Diagram B-7 Investment Business ase* D-1 Knowledge anagement lan D-2 xchange atrix* D-3 bject tate-ransition Diagram D-4 bject vent equence Diagram D-5 Logical Data odel D-6 hysical Data odel D-7 Activity/ntity (RUD) atrix * D-8 Data Dictionary / bject Library A-1 ystem Interface Diagram A-2 ystem ommunication Description A-3 ystem Interface atrix * A-4 ystem Data Flow Diagram A-5 ystem/perations atrix * A-6 ystems Data xchange atrix * A-7 ystem erformance atrix * A-8 ystem volution Diagram A-9 Web Application Diagram I-1 onnectivity Diagram I-2 Inventory I-3 apital quipment Inventory I-4 Building Blueprints * I-5 enter Diagram I-6 able lant Diagram I-7 Rack levation Diagram -1 ecurity and rivacy lan* -2 ecurity olutions Description -3 ystem Accreditation Document* -4 ontinuity f perations lan* -5 Disaster Recovery rocedures * -1 echnical tandards rofile -2 echnology Forecast W-1 Workforce lan* W-2 rganization hart W-3 Knowledge and kills rofile An Introduction to nterprise Architecture 3 rd dition 283

2 A 3 Framework Area echnology Business trategy s & Artifact # and ame -1: trategic lan A trategic lan is a high-level policy and planning document that an enterprise uses to document its direction, competitive strategy, most important goals, and the enabling programs and projects (strategic initiatives). he trategic lan covers a future period, usually 3-5 years. Description A trategic lan is a composite A artifact that should guide the enterprise s direction over a 3-5 year period in the future by providing the following items, each of which are primitive (basic) A artifacts. Full versions of abbreviated primitive artifacts are separate artifacts. rovide a ission tatement and a Vision tatement that succinctly captures the purpose and direction of the enterprise. Develop a tatement of trategic Direction that fits the enterprise s purpose, ensures survivability, allows for flexibility, and promotes competitive success. his statement is a detailed description of where the enterprise intends to go. ummarize the results of a W Analysis that is based on the statement of strategic direction and which identifies the enterprise s strengths, weaknesses, opportunities, and threats. he full W analysis is artifact -2. ummarize the situation and planning assumptions for several oncept of perations cenarios that support the enterprise s strategic direction. his summary should include one current scenario that describes at a high-level the coordination of ongoing activities in each line of business, as well as several future scenarios that account for different combinations of internal and external drivers identified through the W Analysis. he complete scenarios are artifact -3. Develop a Diagram that in a single picture captures the essence of and participants in the current operating scenario. his graphic is artifact -4. Develop a General ompetitive trategy for the enterprise that incorporates the current and future scenarios and moves the enterprise in the intended strategic direction in a way that and address internal/external drivers such as culture, line of business requirements, market conditions, competitor strategies, and risk. Identify trategic Goals that will accomplish the competitive strategy, and specify the executive sponsors who are responsible for achieving each goal. Identify trategic and resource sponsors for the initiatives, which are the ongoing programs or development projects that will accomplish each trategic Goal. ummarize utcome easures for each trategic Goal and Initiative, using the Balanced corecard or similar approach. he full scorecard is artifact -5. An Introduction to nterprise Architecture 3 rd dition 284

3 A 3 Framework Area echnology Business trategy s & Artifact # and ame -2: W Analysis he trength, Weakness, pportunity, and hreat (W) Analysis takes a holistic look at the enterprise by identifying internal and external factors which when mapped can reveal areas for improvement and focus. xample ne of the earliest activities the enterprise performs in developing a strategic plan is a trength, Weakness, pportunity, hreat (W) Analysis. his analysis looks at internal and external factors to determine areas that the enterprise should focus on to increase its survivability and success, as well as areas that the enterprise should avoid, or decrease its exposure to. he results of the W Analysis should be summarized in the trategic lan along with the matrix table illustrated below, and the full W Analysis is archived in the A Repository as a separate primitive artifact (-2). he following is an example of a way to summarize a W Analysis. xternal Factors Internal Factors xternal pportunities () 1. ontracting 2. Government 3. ew echnology 4. artnerships xternal hreats () 1. Funding 2. arket Drivers 3. erger 4. Advanced echnology 5. I Adoption Rate Internal trengths () 1. User ommunity 2. Relationships 3. Involved Leadership 4. In-house echnology 5. Legacy Architecture 6. raining Budget 7. ulture 5/3: Legacy Web ortals 1/3: ecurity 1/2: FD Requirements 6/5: I raining 1/5: I Awareness Internal Weaknesses (W) W1. olicy / Regulations W2. Governance Value W3. I kills ystems W4. nterprise Architecture W5. I kills rocess W6. Low Usability/Implementation W W4/4: A haring W W4/1: Funding Data From the identification of Internal trengths (), Internal Weaknesses (W), xternal pportunities (), and xternal hreats () for the enterprise, a matrix arrangement like the example above can help to reveal internal and external areas to focus on. his W Analysis is also used to help enterprise architects and strategic planners to develop oncept of perations () scenarios that detail current and future operating environments. An Introduction to nterprise Architecture 3 rd dition 285

4 A 3 Framework Area echnology Business trategy s & lanning Assumptions 1. ew Video eleconferencing capability. 2. roduct roll-outs at ational conferences. 3. eed to hold detailed product discussions on short notice, globally x7 work availability. 5. Increased suburban commuting and telecommuting. 6. racking of Govt. reports to anticipate product needs. 7. hanging population demographics, driving new product development. 8. Increased cost benefit of solar powered lighting. 9. Additional product features to attract customers 10. Global use of DAs for employee communication. 11. Integration of sales, marketing, and production information. 12. Accurate customer quotes on the fly. Artifact # and ame -3: cenario A oncept of perations cenario is a narrative document that describes how the enterprise operates currently or will operate several years in the future given certain stated internal and external factors identified in the W Analysis. he scenario is footnoted with planning assumptions. xample Jeff Linder, Vice resident of Industrial ales for Danforth anufacturing ompany (D) had just finished a presentation at the 2008 ational Highway afety onference along with Richard Danforth, D s, who had teleconferenced in on the big display screen behind the podium. 1 As Jeff was leaving the main conference room, Andrea ewman, Director of afety and ransportation for the tate of ennessee, asked Jeff if they could talk about the new line of solar-powered highway lights he had just given a presentation on. 2, 3 hanks for taking a minute to talk Jeff. I want to tell you about a situation we have in ennessee and see if your new product line can help said Andrea as they found a table in the refreshment area. 4 o problem, thanks for asking Jeff said. Andrea pulled up a document on her tablet computer and said Jeff, here is a report that shows an increasing number of serious accidents in rural areas of ennessee involving passenger cars and agricultural equipment or commercial trucks. We ve attributed it to the growth of suburban communities further out in the countryside that then depend on two-lane country roads for commuting into the city. 5 When you put slow tractors and trucks together with cars that are in a hurry at all hours to get somewhere, you have a recipe for disaster. Isn t this problem being seen in other places around the country? asked Jeff. Yes, and one of the contributing factors that is consistently coming out of investigations of the night-time accidents is the lack of good lighting on these country roads. 6 I am thinking that your highway grade solar lighting can help us provide more night visibility on high-risk rural roads without needing electrical infrastructure. 7, 8 Jeff thought for a minute before responding. You know, the new line of highway lights has options to incorporate 911 emergency call boxes and Global ositioning ystem (G) equipment that can connect to both tate and local level first responders. 9 his might be useful in also improving response times should an accident occur in spite of the improved lighting. Andrea nodded and said, Yes, I doubt that better lighting will solve the entire problem, but it will help people see each other better, and these other options can improve accident response times. What is the pricing on these units? Jeff pulled his ersonal Digital Assistant (DA) 10 out of his pocket and connected to D s marketing and sales database at headquarters via a satellite Internet link. 11 Andrea, these units are $11,300 each, including the G and 911 features. Andrea took notes and responded, If I can get permission to conduct a pilot test in a couple of months can you provide the lights? Jeff asked How many miles of road? About four miles in the particular area I m thinking of said Andrea. k, the suggested density for the new unit is 18 per mile, so that would be 72 units total. I can give you our 10 percent early-adopter discount, so the total would be $732,240. Let me check what the shipping time would be. Jeff sent a high priority to Bob Green, Vice resident of anufacturing. Bob was in the factory when he received Jeff s on his DA, and after checking the D roduction cheduling ystem, responded two minutes later that a special order for 72 units could be completed and shipped 35 days from when the order is received. Jim relayed this information to Andrea, who said, Wow, that s fast. I have all the information I need to propose the project, I ll get back to you next week 12 An Introduction to nterprise Architecture 3 rd dition 286

5 A 3 Framework Area echnology Business trategy s & Artifact # and ame -4: oncept of perations Diagram A oncept of perations () diagram is a high-level graphical depiction of the how the enterprise functions, either overall, or in a particular area of interest. xample Diagram his Diagram shows at a high level how a fictitious system called the Hurricane Warning ystem would conduct its primary mission of providing a coordinated weather surveillance and reporting capability using land-based, sea-based, airborne, and space-based resources. An Introduction to nterprise Architecture 3 rd dition 287

6 A 3 Framework Area Artifact # and ame echnology Business trategy s & -5: Balanced corecard he Balanced corecard goes beyond financial measures of success for an enterprise and establishes goals and measures in four key business views: ustomer;, Financial; Internal Business rocesses; and Learning and Growth. Description he Balanced corecard suggests that people should view the enterprise from four perspectives, (not just a money perspective) and should develop metrics, collect data, and analyze the enterprise relative to each of these perspectives, as is shown in the figure to the right. he Balanced corecard is a management and measurement system that enables enterprises to clarify their vision and strategy and translate them into action. he scorecard provides feedback around both the internal business processes and external outcomes in order to continuously improve strategic performance and results. When fully deployed, the balanced scorecard transforms strategic planning from an academic exercise into the nerve center of an enterprise. 1 Financial o succeed financially, how should we appear to our shareholders? ustomer Internal Business o achieve our Vision rocesses vision, how and hould we o satisfy our Appear to our hareholders & trategy customers? ustomers, what Business processes ust we excel at? Learning and Growth o achieve our vision, how will we sustain our ability to change and improve? Balanced corecard trategic trategic Initiative 1 Initiative 2 Financial erspective trategic bjective utcome easure 1 utcome easure 2 utput easure A utput easure B utput easure Internal Business rocess erspective trategic bjective utcome easure 1 utcome easure 2 utput easure A utput easure B utput easure ustomer erspective trategic bjective utcome easure 1 utcome easure 2 utput easure A utput easure B utput easure Learning and Growth erspective trategic bjective utcome easure 1 utcome easure 2 utput easure A utput easure B utput easure trategic trategic trategic Initiative 3 Initiative 4 Initiative 5 1 Balanced corecard Institute An Introduction to nterprise Architecture 3 rd dition 288

7 1. A 3 Framework Area echnology Business trategy s & Artifact # and ame B-1: Business lan he Business lan provides a high-level description of the key line of business functions, and financial strategy that will accomplish the strategic goals and initiatives. Description he following items are often found in a Business lan: 1. Business verview 2. xecutive eam rofile 3. Relationship of Business Activities to trategic Goals 4. rganizational tructure 5. arket utlook and ompetitive trategy 6. Business ycles 7. apitalization ummary 8. Financial trategy 9. urrent Financial tatus ummary 10. Business artnerships and Alliances An Introduction to nterprise Architecture 3 rd dition 289

8 A 3 Framework Area echnology Business trategy s & Artifact # and ame B-2: ode onnectivity Diagram he ode onnectivity Diagram shows the operational nodes, activities performed at each node, node-to-node relationships, and information exchanges. he purpose of this diagram is to show, at a high level, who are the operating groups in the enterprise (lines of business) and how they share information. xample erforms: Activity A Activity B ode 1 eedline 1 ype X ode 2 From xternal ource (upply hain) erforms: Activity A Activity eedline 2 ype Y erforms: Activity ode 3 An Introduction to nterprise Architecture 3 rd dition 290

9 A 3 Framework Area echnology Business trategy s & Artifact # and ame B-3: wim Lane rocess Diagram A takeholder Activity Diagram shows which stakeholders (those with a vested interest in the enterprise) are involved with line of business processes, and the timing of that interaction. he diagram uses the format of swim lanes to arrange stakeholders by row, and timeframes by column, then overlaying activities with flowchart symbology. xample An Introduction to nterprise Architecture 3 rd dition 291

10 A 3 Framework Area echnology Business trategy s & Artifact # and ame B-4: Business rocess Diagram A Business rocess Diagram shows a detailed breakdown of an activity, including how each step in the activity relates to the others. he B-4 diagram follows the IDF-0 modeling technique to show what the inputs, controls, outputs, and mechanisms are for each step in the process. Description and xample Inputs: Items that initiate/trigger the activity and ontrols are transformed, consumed, or become part. ontrols: Guide or regulate the activity; usually Inputs utputs Activity indicate when/ how a process will be performed. utputs: he results produced by the activity; the reason for which the process was performed. I echanisms echanisms: ystems, people, and equipment used to perform the activity. IDF-0 activity modeling is suitable for business process documentation in that it provides both high level context views, and more detailed views of each step in the activity in a format that can be further decomposed and interrelated with other processes to show linkages. his type of diagram is useful in showing linkages between steps and internal/external influences, but may not indicate a time sequence. An Introduction to nterprise Architecture 3 rd dition 292

11 A 3 Framework Area echnology Business trategy s & Artifact # and ame B-5: Activity/roduct atrix he Business Activity & roduct atrix maps the lifecycle of revenue-producing products to various lines of business throughout the enterprise. his matrix highlights who owns business processes and products, as well as the extent of supply chains. xample he Activity/roduct atrix maps the lifecycle of each revenue-producing product that the enterprise produces to the line(s) of business that support one or more phases of the product lifecycle. his matrix allows the enterprise to see where the vertical and horizontal (cross-cutting) business product activities are located, as well as to help define ownership of those processes. he B-5 Activity/roduct atrix can then be used with various level artifacts (e.g. D-7 Activity/ntity atrix) to further map the product lifecycle to requirements for data across the enterprise. Business roduct Line of Business A Line of Business B Line of Business Line of Business D Line of Business Line of Business F Line of Business G roduct 1 R F L roduct 2 W D F L roduct 3 W D F L roduct 4 R F L roduct 5 F L roduct 6 W D F Remarks R = Research & Develop W = Warehouse = ervice L = Legal = anufacture D = Distribute F = Financials he product lifecycle illustrated in this example has five sequential stages (research and development, manufacturing, warehouse storage, sales/distribution, and servicing) and two parallel administrative functions (financials and legal). roduct lifecycles are different within most enterprises, and adjustments to the B-5 matrix should be made accordingly. An Introduction to nterprise Architecture 3 rd dition 293

12 A 3 Framework Area echnology Business trategy s & Artifact # and ame B-6: Use ase arrative & Diagram A Use ase narrative follows the Unified odeling Language (UL) format for identifying business requirements, their context, stakeholders (actors), and business rules for their interaction with systems, services, and applications that are identified as technology solutions requiring development. xample An Introduction to nterprise Architecture 3 rd dition 294

13 A 3 Framework Area echnology Business trategy Artifact # and ame B-7: Investment Business ase An Investment Business ase uses a standard format to describe the value, risk, and return on investments made in technology and other resources. he Business ase also contains an alternatives analysis, program performance tracking metrics, architecture information, and security status information. xample 1. ew Requirement. A new requirement for resource(s) or support is identified in a line of business (LB), which is brought to the A and capital planning teams for evaluation. 2. xisting olution heck. he A and capital planning teams determine that an existing A component cannot meet the requirement. 3. ew olution Business ase. he sponsoring LB determines that the requirement is of sufficient importance to merit the cost of developing a business case: Business eed. Describe the requirement in terms of the gap in operational or administrative performance it represents to the LB and the enterprise. Impact if ot Resolved. Describe the impact to the enterprise if the performance gap is not resolved, including strategic, business, and technology impact. Alternatives Analysis. Identify 3 or more viable alternative solutions (if 3 exist). ost-benefit Analysis. Quantify the direct and indirect costs and benefits for each alternative on a lifecycle basis, including qualitative items. s & Return on Investment. Do a RI calculation for each alternative. et resent Value Adjustment. Do a V adjustment for each RI calculation to account for anticipated cost increases over the investment s lifecycle. 4. Business ase valuation. he business case s alternatives are evaluated by the Architecture Working Group (AWG) for the correctness of the analysis, and alignment with the A at each level of the framework. he apital lanning Working Group (WG) then reviews the business case for the correctness of the financial analysis. A coordinated recommendation is made to the executive-level apital lanning Board (B) as to whether the business case should be approved or disapproved. 5. Business ase Approval. he B reviews and approves/disapproves the business case in the context of the enterprise s overall investment portfolio using criteria that identify value from a strategic, business, and technology perspective: 6. Implementation. If the business case is selected (approved) for funding by the B, the proposed solution becomes an implementation project that is managed by the sponsoring LB. he project is reviewed by the B at key milestones and/or periodically as part of the capital planning process oversight of all projects. An Introduction to nterprise Architecture 3 rd dition 295

14 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-1: Knowledge anagement lan he Knowledge anagement (K) lan provides a detailed description of how knowledge, information, and data are shared across the enterprise. he K lan includes descriptions and diagrams of information sharing between systems, applications, knowledge warehouses, and databases Description and xample K lan ontents he approach to managing data, information, and knowledge across the enterprise How data and information-sharing support the Business lan Data and information-sharing strategies and diagrams for each line of business Data and information sharing strategies with external partners and customers Which types of data in the enterprise require extra protection he lifecycle for data and information that is key to the success of the enterprise (data creation, sharing, updating, storage, retrieval, and deletion) xample of a High Level K Diagram An Introduction to nterprise Architecture 3 rd dition 296

15 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-2: xchange atrix he xchange atrix describes relevant attributes of data exchanges between systems. hese attributes include size, logical specification of the information i.e., media, timeliness required, and the security classification and properties of the information. xample exchanges express the relationships across four important aspects of the architecture (information, activities, locations, and times) with a focus on the specific aspects of the information flow. exchanges identify which business nodes exchange what information during the performance of what activities and in response to which events. Additional information on who is performing the activity can be added, if needed for security analysis. he detailed information in the xchange atrix may be hard to collect but it is necessary to fully understand the information flow in the enterprise and its security aspects. he matrix also identifies the event that triggers the information exchange (e.g., set schedule or citizen request). he matrix keys the exchange to the producing and using activities and nodes and to the needline (from the ode onnectivity Diagram) the exchange satisfies. he xchange atrix partitions each high-level needline into its component parts, i.e., into distinct information exchanges between business nodes. An example format for this artifact is provided below. Additional characteristics may be added to the D-1 matrix based on the purpose or goals of the enterprise. 1 IFRAI DRII UR DI- AI IFRAI XHAG ARIBU DLI IDIFIR IFRAI XHAG A/ID DIA IZ DIG D DIG AIVIY RIVIG D RIVIG AIVIY RIGGRIG V FRQUY ILI HRUGHU URIY IRR- ABILIY RQUIR DIGIAL, VI, X, RAG LII IAG,. 1 K. owell and A. Reedy An Introduction to nterprise Architecture 3 rd dition 297

16 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-3: bject tate ransition Diagram A tate ransition Diagram uses the notation from the Unified odeling Language to show how the lifecycle of a specific data object. his diagram shows changes to attributes, links, and/or behavior(s) of the n-line rder object that are a result of internal or external system events which trigger changes in state. xample lace -rder n-line order entry/ calculate line total, do/display line total rder checked heck tock heck stock/ nter/ calculate order total, do/display order total ut of tock ancel order ancelled ntry/adjust register do/display refund n-line ayment (amount) tart he Lifecycle of he n-line rder bject (Item#, Qty/ Reset Register) ake -ayment -payment entry/calculate Balance, do/display balance, exit/pay balance ull tock (quantity) rder rocessing Do/prepare ordered items for shipment Item(s) shipped Finish Delivered ntry/adjust register do/display refund An Introduction to nterprise Architecture 3 rd dition 298

17 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-4: bject vent race Diagram he vent-race Diagram allows the tracing of actions in a set of scenarios or operational threads. ach model should focus on a critical sequence of events and a description of this scenario should accompany the model. xample With time proceeding from the top of the diagram to the bottom, a specific diagram lays out the sequence of information exchanges that occur between business nodes for a given scenario. hese information exchanges are associated with events and actions (see xchange atrix). he direction of the event arrows shows flow of control, in terms of the business process, from node to no. 1 D V/I D 1 D 2 D 3 event 1 at time 1 {formula relating time 1 to time 2} event 2 at time 2 essage 1 essage 2 event 3 at time 3 {formula relating time 3 to time 3'} time 3' time 4 essage 3 essage 4 essage 5 essage 6 time n essage 7 essage 8 1 K.owell and A. Reedy, 2001 An Introduction to nterprise Architecture 3 rd dition 299

18 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-5: Logical Data odel A semantic data model can be developed using traditional structured methods and symbology (ntity Relationship Diagram), or one can use the object-oriented method and symbology of the Unified odeling Language (UL), which produces a lass Diagram and/or bject Diagram. xample lass Diagram (shows the static structure of a system) Dog wner lasses Link ame olor ex Barks ats Association ame Address hone Feeds errier ame olor ex Barks ats oodle ame olor ex Barks ats bjects U Keybd onitor (with inheritance of attributes) xample of Aggregation, which expresses a art-of relationship between a component object and an aggregate object An Introduction to nterprise Architecture 3 rd dition 300

19 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-6: hysical Data odel he hysical Data odel is used to describe how the information represented in the Logical Data odel is actually implemented in automated information systems. xample here should be a mapping from a given Logical Data odel to the hysical Data odel (D). he D is a composite model whose components can vary greatly, as shown in the template below. For some purposes, an entity-relationship style diagram of the physical database design will suffice. he Data Definition Language may also be used in the cases where shared databases are used to integrate systems. References to message format standards (which identify message types and options to be used) may suffice for messageoriented command and control subsystems. Descriptions of file formats may be used when file passing is the mode used to exchange information. Interoperating systems may use a variety of techniques to exchange data, and thus have several distinct partitions in their D with each partition using a different form. hysical Data odel rovides essage Format: - tandards Reference - essage ype(s) - essage Fields with Representation - ap From the Logical Data odel to the essage Fields File tructure: -tandards Reference -Record and File Descriptions -ap from Logical Interface odel to Record Fields hysical chema: -DDL or RA otation with sufficient detail to generate the schema -ap from the Logical Data odel to the hysical Data odel with Rationale 1 K. owell and A. Reedy, 2001 An Introduction to nterprise Architecture 3 rd dition 301

20 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-7: Activity/ntity atrix An Activity/ntity atrix is developed by mapping which data entities are affected by related line of business activities. ften called a RUD atrix because it identifies the basic types of transformations that are performed on data (reate, Read, Update, Delete) through a business process. xample 5 ntity-activity atrix ntity-activity (RUD) atrix: tock Item tock Receive new stock ontrol U Receive customer order R Issue customer with goods Issue monthly statement Receive faulty goods rder new printed catalog rder new stock R ail catalog to customer ntity ype Invoice Invoice Line Item ustomer ustomer R U U R R R R onthly tatement Warehouse R ntity-activity atrix (RUD): =reate, R=Read, U=Update, D=Delete heck matrix that: Is every entity affected by at least one activity, if not, it s singular and should be dropped? Is there just one reate activity for each entity? ote that reate may be a boundary activity, that may have happened through internal processes. atalog atalog roduction atrix may be used to: Define the scope of the problem Describe a system map artition the system (luster Analysis) Determine who owns the data and/or processes (activities) An Introduction to nterprise Architecture 3 rd dition 302

21 A 3 Framework Area echnology Business trategy s & Artifact # and ame D-8: Data Dictionary he Data Dictionary provides a comprehensive listing of the data entities that are collected and maintained by the enterprise, including standards for the attribute fields, keys, and relationships. he Data Dictionary may also include a library of reuseable Data bjects that use UL methods. xample FILD A DAA Y FILD LGH KY AI DRII AL R_ID UBR 5 K RY ID A sequential number that uniquely identifies each record in tblrototype R_ID UBR 5 FK RAL ID A sequential number that uniquely identifies each record in tblroposal R_RDLI X 20 RY RDU LI he target olar ell product line onsumer R_VLA G UBR 5 RY VLAG lectrical output, in volts 3.5 R_DRI I X 100 RY DRII A brief description of the prototype R_WIDH UBR 20 RY WIDH Width, in inches, of the prototype 2 R_LG H UBR 20 RY LGH Length, in inches, of the prototype 4.25 R_HIK UBR 20 RY HIK hickness, in inches, of the prototype.375 R_WIGH UBR 20 RY WIGH Weight, in ounces, of the prototype 10 R_AR DA RY AR DA Date development of the prototype began 11/29/2000 R_D DA RY D DA Date development of the prototype was completed 5/17/2001 An Introduction to nterprise Architecture 3 rd dition 303

22 A 3 Framework Area echnology Business trategy s & Artifact # and ame A-1: ystem Interface Diagram he ystem Interface Diagram shows the logical and/or physical interfaces between the enterprise s systems for information, production, etc. where information and/or other resources are exchanged. xamples D-1 (ortheast Regional ffice) ystem A D-2 (id-west Regional ffice) ystem B ystem xternal onnection ystem D ystem ystem F D-3 (Headquarters ffice) An Introduction to nterprise Architecture 3 rd dition 304

23 A 3 Framework Area echnology Business trategy s & Artifact # and ame A-2: ystem ommunication Description he -2 artifact compliments the -1 ystem Interface Diagram by providing a description of how data is communicated between systems throughout the enterprise, and includes specifics about links, paths, networks, and media. xample D-1 (ortheast Regional ffice) ystem A ystem B D-2 (id-west Regional ffice) LA ystem Dedicated -3 Data Line Internet ommercial ellular Dedicated -1 Data Line Firewall ystem D LA ystem ystem F D-3 (Headquarters ffice) An Introduction to nterprise Architecture 3 rd dition 305

24 A 3 Framework Area Artifact # and ame echnology Business trategy s & A-3: ystem Interface atrix he ystem Interface atrix shows the nature and status of physical and logical interfaces between information systems throughout the enterprise. xample 1. rovides detail on the interface characteristics of the A-1 artifact. Allows quick overview nables rapid assessment of potential re-use or redundancies 2. Useful tool for managing the evolution of systems, infrastructures, technology insertion, functional upgrades. 3. Interface characteristics that could be captured include: tatus (existing, planned, potential, deactivated), purpose, classification level, key interface(s) ystem Interface atrix ystem 1 ystem 2 ystem 3 ystem 4 ystem 5 ystem 6 ystem 7 ystem 8 ystem 9 ystem 1 * ystem 2 X * ystem 3 X * ystem 4 X * ystem 5 X * ystem 6 X X X * ystem 7 X * ystem 8 R R * ystem 9 X * X = xisting Interface = lanned Interface R = Retire Interface An Introduction to nterprise Architecture 3 rd dition 306

25 A 3 Framework Area echnology Business trategy s & Artifact # and ame A-4: ystem Data Flow Diagram he ystem Data Flow Diagram is better known as a Data Flow Diagram and is intended to show the processes within a system that exchange data, and how those exchanges occur. he A-4 artifact compliments the B-4 Business rocess Diagram, and can be decomposed to show additional detail. xample 1. aptures and describes system functions and the data flows between them. 2. Documents system functional hierarchies. 3. rimary purpose is to: Develop a clear description of the necessary system data flows that are input (consumed) and output (produced) by each system nsure functional connectivity is complete upport appropriate level of functional decomposition for additional detail 4. Is the systems counterpart to the B-4 Business rocess odel (IDF-0 diagram). ustomer Job Request D4 roject racking D3 Laws/tandards Resource Details Legal Requirements D1 D2 1.0 rocess Request ersonnel Files arts/quip Files Job Request Details Labor Availability arts Availability 3.0 Delegate Resources roject Resource Instructions upervisor Job Delegation roject Update pecial Request 3.0 Assess Resources Delegation Info. Job Details 4.0 Repair Highway Applicable tandards D4 roject racking roject Update An Introduction to nterprise Architecture 3 rd dition 307

26 A 3 Framework Area Artifact # and ame echnology Business trategy s & A-5: ystem/perations atrix he ystem/perations atrix relates operational activities to system functions within and between lines of business throughout the enterprise. xample 1. Relates operational activities to system functions 2. Identifies the transformation of an operational need into a purposeful action performed by a system 3. upports decision making as follows: Identify stovepipe systems and opportunities for automation Identify redundant systems and functions Analyze gaps in performance arget investment opportunities perational Activity ystem / perations atrix all for ales Data Input ales Data Update ales Data Distribute ales Data Use ales Data ystem Function Load ales Data Input emplate X Display ales Data Input emplate X Load ew ales Database X Receive ew ales Data X Load Historical ales Database X Update ew ales Data ub-able X Update Historical ales Database X Receive ales Data orrections X Update Historical ales Database X end ew ales Data X end Updated Historical ales Data X Receive ew ales Data Querry X end ew ales Data X X Receive Historical ales Data Querry X end Updated Historical ales Data X X An Introduction to nterprise Architecture 3 rd dition 308

27 A 3 Framework Area Artifact # and ame echnology Business trategy s & A-6: ystem Data xchange atrix he ystem Data xchange atrix uses a table format to show which systems exchange particular types of data within and between lines of business throughout the enterprise. Description and xample he ystem Data xchange atrix describes, in tabular format, data exchanges between systems within a systems node and across systems nodes. he focus of the ystem Data xchange atrix is on how the data exchanges actually are (or will be) implemented, in system-specific details covering such characteristics as specific protocols and data or media formats. hese aspects of exchanges, while difficult to document, are critical to understanding the potential for overhead and security constraints introduced by the physical aspects of the implementation. he ystem Data xchange atrix relates to, and grows out of, the xchange atrix. hat is, the automated portion(s) of each information exchange in the xchange atrix is associated with the system interface that carries the corresponding system data in the ystem Interface Description. he business characteristics for the information exchange are replaced with the corresponding system data exchange characteristics. For example, performance attributes for the business information exchanges are replaced by the actual system performance attributes for the automated portion(s) of the information exchange. Automation may introduce characteristics that are not intrinsic to the business information exchange. 1 Identification & raceability ature of ransaction ource & Destination ource Destination erformance ecurity riority lassification hroughput imeliness Frequency ystem Function ystem ystem Function ystem riggering vent Format/tandard ize Data lement ame Data xchange xchange ystem Interface eedline 1 K. owell and A. Reedy, 2001 An Introduction to nterprise Architecture 3 rd dition 309

28 A 3 Framework Area Artifact # and ame echnology Business trategy s & A-7: ystem erformance atrix he ystem erformance atrix lists the metrics that are important with regard to reliability, availability, and maintainability. xample 1. pecifies the quantitative characteristics of system: Hardware/software Interfaces ommunication components 2. Identifies both current and future parameters. 3. Includes all relevant technical performance characteristics, for instance: ean ime Between Failure Restart Rate ystem Initialization ime Data ransfer Rate ystem erformance easures easure Area ype of riginal urrent easure Baseline tatus arget ystem aintainability ercentage ystem Availability ercentage ystem tart-up (Initialization) ime econds ystem Restart (Re-boot) ime econds Hosted Application tart-up ime (>100 B) econds Hosted Application tart-up ime (<100 B) econds Data hroughput apacity (# of input types) egabytes ean ime Between Hardware Failures Days ean ime Between oftware Failures Days ystem ettings Back-up ime inutes ystem Data Back-up ime inutes mail utbox ransfer Rate (<1B) econds mail utbox ransfer Rate (<300KB) econds An Introduction to nterprise Architecture 3 rd dition 310

29 A 3 Framework Area Artifact # and ame echnology Business trategy s & A-8: ystem volution Diagram he ystem volution Diagram shows the evolution of a system including the relationship and timing of consolidations installations, upgrades, and retirements, sometimes shown in the context of changes to other systems, applications, websites, and databases. xample ystem A ystem B ystem ystem A-1 Website X Intranet ystem A-2 ystem D ystem D-1 ystem Database Q ystem D-2 ystem D-3 ystem F ystem G-1 ystem H ystem G Q1 Q2 Q3 Q4 Q5 An Introduction to nterprise Architecture 3 rd dition 311

30 A 3 Framework Area echnology Business trategy s & Artifact # and ame A-9: Web Application Diagram he web application diagram shows the logical relationships between web-based information services, in this case showing a detailed diagram of services that interact via standard protocols and interfaces that promote platform-independent data interchanges. xample. ecurity ervice Data ervice -ail ervice earch ervice A-XL Interface A-XL Interface A-XL Interface A-XL Interface Web ervice User A/XL Web ervice Request essage Web ervice (WDL) Descriptions Access rotocol (A) Web ervice Bus UDDI Web ervice Registry A-XL Interface A-XL Interface A-XL Interface A-XL Interface -Biz ervice R ervice R ervice ther Web An Introduction to nterprise Architecture 3 rd dition 312

31 A 3 Framework Area echnology Business trategy s & Artifact # and ame I-1: onnectivity Diagram he onnectivity Diagram shows the physical connections between the enterprise s voice, data, and video network including external Wide Area s (WAs) and Local Area s (LAs) also called extranets and intranets. xample ystem A Account Login/Authentication rimary User Interfaces & GUI Field perations ystem B WA ystem D ystem WB ortal AB Database Database XYZ IR uppliers Industry itizens Lobbyists User Group 1 User Group 2 rint & File erver mail & Desktop Application ervers torage Area Financial & HR ainframe Web erver User Group 3 An Introduction to nterprise Architecture 3 rd dition 313

32 A 3 Framework Area Artifact # and ame echnology Business trategy s & I-2: Inventory he Inventory lists all of the hardware and software on the enterprise s voice, data, and video networks throughout the enterprise. he list may include bar code numbers or other unique identifiers. xample D, Inc. quipment Inventory Description Bar ode Location Vendor odel # Data 100-ort tackable witch #1 D-620 Bldg 1 V 73G ort tackable witch #1 D-621 Bldg 1 V 73G ort tackable witch #1 D-622 Bldg2 V 73G ort tackable witch #1 D-623 Bldg3 V 73G ort tackable witch #1 D-624 Bldg 3 V 73G ort tackable witch #1 D-625 Bldg 4 V 73G ort tackable witch #1 D-626 Bldg 4 V 73G20 50-ort A/Gigabyte Router D-611 Bldg 1 Hamre H ort A/Gigabyte Router D-612 Bldg 2 Hamre H ort A/Gigabyte Router D-613 Bldg 3 Hamre H ort A/Gigabyte Router D-614 Bldg 4 Hamre H7500 Application erver #1 D-616 Bldg 1 Kayprime K455 Application erver #2 D-617 Bldg 1 Kayprime K455 Application erver #3 D-618 Bldg 1 Kayprime K455 rint erver #1 D-603 Bldg 1 Kayprime K430 rint erver #2 D-604 Bldg 3 Kayprime K430 Web erver #1 D-605 Bldg 1 Kayprime K502 Web erver #2 D-606 Bldg 3 Kayprime K502 Internet Firewall D-610 Bldg 1 Gladiator 3000 olor rinter D-370 Bldg 1 HG 755 B/W rinter #1 D-375 Bldg 2 HG 380G B/W rinter #2 D-375 Bldg 3 HG 380G B/W rinter #3 D-375 Bldg 4 HG 380G B/W rinter #4 D-375 Bldg 5 HG 380G elecommunications aster BX witch D-801 Bldg 1 Westcom W9000 BX 100-Line ode ontroller D-802 Bldg 1 Westcom W9002 BX 100-Line ode ontroller D-803 Bldg 2 Westcom W9002 BX 100-Line ode ontroller D-804 Bldg 3 Westcom W9002 BX 100-Line ode ontroller D-805 Bldg 4 Westcom W9002 VI Interface Unit D-807 Bldg 1 Westcom W1380 GreenBerry ell hone Unit D-808 Bldg 1 Greenberry KJ1700 Video V Roll-Around Unit #1 D-960 Bldg 1 learel 1800 V Interface Box D-961 Bldg 1 learel 739 An Introduction to nterprise Architecture 3 rd dition 314

33 A 3 Framework Area Artifact # and ame echnology Business trategy s & I-3: apital quipment Inventory he apital quipment Inventory lists all of the non-information technology capital (depreciable) equipment in each line of business throughout the enterprise. he list may include bar code numbers or other unique identifiers. xample D, Inc. apital quipment Inventory Description Bar ode Location Vendor odel # anufacturing quipment Robotic Welder #1 D-1501 Bldg 4 Daiwoo 4R35 Robotic Welder #2 D-1502 Bldg 4 Daiwoo 4R35 Robotic Welder #3 D-1503 Bldg 4 Daiwoo 4R35 Die ast xtractor #1 D-1546 Bldg 4 Avex 500G Die ast xtractor #2 D-1547 Bldg 4 Avex 500G etal ress-tamper D-1560 Bldg 4 Avex 360 eries Final Assembly Unit D-1565 Bldg 4 Avex 200 eries Quality ontrol hecker D-1607 Bldg 4 Humbart H201G Boxing Unit #1 D-1615 Bldg 3 Janro J-700 Boxing Unit #1 D-1616 Bldg 3 Janro J-700 torage helving Unit #1 D-901 Bldg 2 G J3000 torage helving Unit #2 D-902 Bldg 2 G J3000 Building quipment 40-on Air onditioner #1 D-465 Bldg 1 Liebert 400L 40-on Air onditioner #1 D-466 Bldg 2 Liebert 400L 40-on Air onditioner #1 D-467 Bldg3 Liebert 400L 40-on Air onditioner #1 D-468 Bldg 4 Liebert 400L Fire ensing ontrol Box #1 D-763 Bldg 1 G 1600 Fire ensing ontrol Box #2 D-764 Bldg 2 G 1600 Fire ensing ontrol Box #3 D-765 Bldg 3 G 1600 Fire ensing ontrol Box #4 D-766 Bldg 4 G 1600 Diesel Back-up Generator #1 D-248 Bldg 3 Honda 36H-750 Diesel Back-up Generator #2 D-249 Bldg 4 Honda 36H-750 An Introduction to nterprise Architecture 3 rd dition 315

34 A 3 Framework Area Artifact # and ame echnology Business trategy s & I-4: Building Blueprints he I-4 artifact is a full set of electronic blueprints for all of the physical buildings and rooms throughout the enterprise. he blueprints aid in planning and decision-making regarding the placement of workspaces, production facilities, warehouses, networks and other business functions. lectronic Blueprints An Introduction to nterprise Architecture 3 rd dition 316

35 A 3 Framework Area echnology Business trategy s & Artifact # and ame I-5: enter Diagram he I-5 artifact is an overhead diagram of the information technology network center. his diagram can be part of the I-4 set of blueprints, and is maintained electronically to support the numerous changes to network center(s) and server rooms that can be expected over a number of years. xample Rack 1 Rack 2 Rack 3 Rack 4 Rack 5 Rack 6 Rack 7 Rack 8 Rack 9 Rack 10 Administration Desk Assembly/Repair Bench est Bench arts torage Unit 2 arts torage Unit 1 HVA Unit An Introduction to nterprise Architecture 3 rd dition 317

36 A 3 Framework Area echnology Business trategy s & Artifact # and ame I-6: able lant Diagram he able lant Diagram shows physical connectivity between voice/data/video networks throughout the enterprise and to global suppliers. he diagram should show the types of cable (fiber, A-6, etc.) and the bandwidth (-1, -3, etc.) of each cable run between network centers, server rooms, wiring closets, and external connections. xample ite B Building 4 Firewall erver Room Ded icated -3 Data Line Global onnectivity AD Local able ervice Local elco Internet hone witch -1 Voice and Data Line Firewall Building 1 Wiring loset 1 Wiring loset 2 Wiring loset 3 enter -3 Voice & Data Line BX elephone witch V enter -1 Voice & Data Line Fractional -1 Back-up Line -1 Voice & Data Line Wiring loset 4 Building 2 Wiring loset 5 Building 3 ite A An Introduction to nterprise Architecture 3 rd dition 318

37 A 3 Framework Area echnology Business trategy s & Artifact # and ame I-7: Rack levation Diagram his diagram provides a front and rear view of each of the information technology equipment racks that go into a network center, server room, and/or wiring closet. his diagram supports the I-5 and I-6 diagrams and is maintained electronically to support the numerous changes that can be expected over a number of years. xample verhead Fan 50-ort witch #1 50-ort witch #2 KVA witch Administrator s Laptop File ervers (luster A&B) urge rotector and Battery Unit Rack 1 - Front Rack 1 - BAK An Introduction to nterprise Architecture 3 rd dition 319

38 A 3 Framework Area echnology Business trategy s & Artifact # and ame -1: ecurity lan he ecurity lan provides both high-level and detailed descriptions of the security program that is in effect throughout the enterprise. his includes physical, data, personnel, and operational security elements and procedures. hapter 11 provides additional detail on ecurity lans. xample utline 1. Introduction urpose of the I ecurity rogram rinciples of I ecurity ritical uccess Factors Intended utcomes erformance easures 2. olicy xecutive Guidance echnical Guidance Applicable Law and Regulations tandards 3. Reporting Requirements I ecurity rogram Roles and Responsibilities I ecurity rogram chedule and ilestones I ecurity Incident Reporting 4. oncept of perations I ecurity hreat ummary I ecurity Risk itigation Integration with nterprise Architecture omponent/ystem ecurity lans 5. ecurity rogram lements ecurity ersonnel ecurity perational ecurity hysical ecurity 6. tandard perating rocedures est and valuation Risk Assessment ertification and Accreditation Disaster Recovery/ontinuity of perations Records rotection and Archiving Data rivacy An Introduction to nterprise Architecture 3 rd dition 320

39 A 3 Framework Area echnology Business trategy s & Artifact # and ame -2: ecurity olutions Descriptions he ecurity olutions Description provides a high-level view of how security is provided for selected resources throughout the enterprise. he solutions cover four dimensions of security: physical, data, personnel, and operations and may include diagrams or matrices. xample utline perational ecurity In the area of operational security, the ecurity rogram should promote the development of standard operating procedures (s) for all A components that support line of business operations. s should also be developed for recovery from major outages or natural disasters, and for enabling the continuity of operations if all or part of the enterprise becomes disabled. Data ecurity In the area of information security, the ecurity rogram should promote security-conscious designs, information content assurance, source authentication, and data access control. he assessment of types of data being handled for privacy protection concerns should also be done (e.g. customer credit data or employee s ersonnel ecurity In the area of personnel security, the ecurity rogram should promote user authentication and I security awareness, and new user/recurring training. badges, biometrics, card swipe units, cipher locks, and other methods of combining personnel and physical security solutions should be implemented. hysical ecurity he elements of physical security that should be captured in the A include protection for the facilities that support I processing, control of access to I equipment, networks, and telecommunications rooms, as well as fire protection, media storage, and disaster recovery systems. An Introduction to nterprise Architecture 3 rd dition 321

40 A 3 Framework Area echnology Business trategy s & Artifact # and ame -3: ystem Accreditation Document he ystem Accreditation Document uses a standard format for evaluating the security status of information systems throughout the enterprise. here are a number of parts to a system security accreditation as are illustrated in the example. xample utline 1. ystem ecurity lan. his opening section of the ystem Accreditation Document provides an overview of the business context that the information system operates in, states the current security status of the system (last accreditation), and summarizes the contents and finding of the other accreditation documents. 2. ystem Risk Assessment. his section of the document uses a standardized format for showing areas of risk to the information system in the four primary areas security threat areas that are covered in artifact -2; physical, data, operational, and personnel. Assigns a level of risk based on the business context for system operations and the type of system data to be protected. rovides security risk remediation strategies (how to avoid a security risk, or deal with it if a problem occurs) for each area of risk that is identified. 3. ystem est and valuation. Also called a system penetration test. he ystem est and valuation (&) section of the document provides the results of a live test that attempts to enter the system through other-than-normal log-in procedures, as well as attempts to overwhelm the system (denial of service attack), or infect the system with an active virus, worm, or other type of problematic element that reduces or eliminates information system functionality. 4. Remediation lan. his section of the document provides the status of corrective actions taken to fix all of the security risks found during the risk assessment/&. 5. Approval to perate. his section of the document is the formal (signed) approval to operate the information system that is provided by the designated person in the enterprise (usually the hief fficer or the I ecurity anager). An Introduction to nterprise Architecture 3 rd dition 322

41 A 3 Framework Area echnology Business trategy s & Artifact # and ame -4: ontinuity of perations lan he ontinuity of perations lan () uses a standard format for describing where all or part of the enterprise will relocate to if the normal operating location cannot be occupied for an extended period (more than a few days) due to a natural or man-made event. xample ontents he activation of the relocation site may have to be accomplished in the midst of a local or national disaster that makes clarity, brevity, completeness, and flexibility (backups) key to success. he following are some of the recommended elements in a document: 1. Activation. onditions for Activating the. 2. Roles and Responsibilities. A matrix of the roles and responsibilities (by position) of all personnel throughout the enterprise who are involved in activating the. Alternates are provided for each position. 3. hecklist. A step-by-step checklist of actions for each person participating in the. 4. Relocation ite ap and Directions. How to get to the site from various probable routes. 5. Relocation ite Activation. he process for activating the site, establishing internal/external communications, and reconstituting key enterprise functions at the site. 6. Relocation ite Inventory. An inventory of systems, equipment, and supplies at the relocation site, along with the person(s) responsible for ensuring that the systems are operational and the equipment is present when needed. 7. Relocation ite De-Activation. rocedures for de-activating the site and restoring it to a ready status after a real relocation event or training exercise. nterprise Functions Have to Relocate An Introduction to nterprise Architecture 3 rd dition 323

42 A 3 Framework Area echnology Business trategy s & Artifact # and ame -5: Disaster Recovery lan he Disaster Recovery lan is an assessment matrix and set of procedures to handle outages in various business and/or technology capabilities that do not require the enterprise to relocate its operations. utages can be caused by natural or man-made events (e.g. fire, flood, power outage). xample ontents he activation of the Disaster Recovery lan may have to be accomplished in the midst of a natural or man-made disaster that makes clarity, brevity, completeness, and flexibility (backups) key to success. he following are some of the recommended elements in a Disaster Recovery lan: 1. Disaster Recovery Activation. onditions for Activating the. 2. Recovery Roles and Responsibilities. A matrix of the roles and responsibilities (by position) of all personnel throughout the enterprise who are involved in activating the. Alternates are provided for each position. 3. Disaster Impact and Recovery Assessment. A standard matrix for assessing the type and duration of the outage, as well as the systems and functions throughout the enterprise that are affected. Depending on the type of outage and the projected period of outage (minutes, hours, days), the recovery procedure may differ. 4. Recovery rocedures. he procedures that are used to restore the business and/or system functions that have been disrupted. xamples include: lectrical utage Air onditioning/heating utage Building Damage (Fire, Flood, arthquake) Room Damage (Fire, Flood, arthquake) Virus Infection of ystem(s) Loss of Internal or xternal Data ommunications Loss of Internal or xternal elephone ommunications nterprise Functions Do ot Relocate An Introduction to nterprise Architecture 3 rd dition 324

43 A 3 Framework Area echnology Business trategy s & Artifact # and ame -1: echnology tandards rofile he echnology tandards rofile is a listing of business services and associated technologies that are accepted by the enterprise as being a primary or secondary standard. Further detail can be added regarding particular types of standards (e.g. data, telecommunications) and vendor products. xample Item Description ystems Hardware echnical tandards rofile International tandard 1 International tandard 2 ational tandard Local tandard tandard roduct Alternative roduct Router I I asco 7300 IronBox 300H erver I I Gell 2000 owbox 710 rinter I I icop 85 HV 550 Desktop I I Gell 1650 owbox 200 ystems oftware erver perating ystem I I acrowift Blueap Linux Desktop perating ystem I I acrowift Linux Desktop Desktop ffice Automation uite I I acrowift uitero Kona Big uite omputer Aided Design I I Grafex AD acroad elecommunications ystem Hardware BX entral witch I 877.1F 7306 I 735 Verizo 679 Westel 7200 Blamoel 80X BX entral witch I 877.1F 7306 I 735 Verizo 679 Westel 7202 Blamoel 83B Desk elephone I 877.1F 7306 I 735 Verizo 679 Westel 58J Blamoel 10J elecommunications ystem oftware BX witching ontroller I 877.1F 7306 I 735 Verizo 679 Westel BX ax Blamo BX VI Interface I 877.1F 7306 I 735 Verizo 679 Westel VI ax Blamo VI Video onferencing ystem Hardware Roll-Around V Unit I I A845 hotovox 1300 Humbel 850 Desktop V Unit I I A845 hotovox 350 icturehi 75G V ultiplexer & ontrol Box I I A845 hotovox 46 Video onferencing ystem oftware Desktop Video onferencing I I A845 acrowift eet An Introduction to nterprise Architecture 3 rd dition 325

44 A 3 Framework Area echnology Business trategy s & Artifact # and ame -2: echnology Forecast he echnology Forecast supports and relates to the -1 echnology tandards rofile. he echnology Forecast documents expected changes in any of the standards listed in the -1 artifact, where future changes appear to be happening or about to happen. xample aptures expected changes in technology related standards and conventions Identifies critical technology standards, their fragility, and impact of changes to the architecture ontains specific predictions about the availability of emerging standards, and relates to specific ystem/application (A) framework elements Forecast Area perating ystems ffice Automation uite Desktop s echnology Forecast hort erm (ext id-erm 12 onths) (12-24 onths) acrovox G basic perating ystem will be supported until late 2007 Kona Big uite upgrade finished in early 2005 acrovox G-2 will be launched in early 2006 Kona Big uite II is due out in late 2006, will provide xml data exhange between applications and a bundled graphics and photo editor. Gell 2000 became standard in 2004, is Gell 2000 units will installed on 70% of remain desktops; will be 100% in mid Long erm (2-3 Years Away) Linux is gaining in capability and reliability, should consider migration to Linux in mid 2006 as an alternative to acrovox G upgrade. Kona roject X is going to incorporate a database application onduct vendor flyoff in early 2006 based on updated application and performance requirements Desktop onitors ersistent torage ersonal Digital Assistants 15" olor Rs being replaced by 21" olor LDs as Desktops are replaced; 100% in mid 2005 LD units will remain onduct vendor flyoff in early 2006 based on desktop compatability and user requirements 5 Gigabyte IA type 2 card available 10GB card expected 40+GB cards xecutive level only - Greenberry X400 ffice Directors also get Greenberry X400s onduct vendor flyoff in early 2006 based on updated application and performance requirements An Introduction to nterprise Architecture 3 rd dition 326

45 A 3 Framework Area echnology Business trategy s & Artifact # and ame W-1: Workforce lan he Workforce lan provides a high-level description of how human capital is managed throughout the enterprise. he Workforce lan includes strategies for hiring, retention, and professional development at the executive, management, and staff levels of the enterprise.. xample Workforce lan utline ummary of Human apital anagement trategy Line of Business Requirements xecutive Level ompetencies and rofessional Development lans anagement Level ompetencies and rofessional Development lans o o o o Line of Business A Line of Business B Line of Business Line of Business D taff Level ompetencies and rofessional Development lans o o o o Line of Business A Line of Business B Line of Business Line of Business D erformance Review rocess Benefits rogram raining and uition Assistance rogram An Introduction to nterprise Architecture 3 rd dition 327

46 A 3 Framework Area echnology Business trategy s & Artifact # and ame W-2: rganization hart he rganization hart shows how positions and personnel are organized in hierarchical diagrams or matrix formats. rganization harts help to show lines of authority, working relationships, as well as ownership of resources, products, and processes. xample Administrative Assistant I hief ounsel H F V anagement V ales V anufacturing V Administration Director, Finance hief Architect / Region 1 Director Director, R&D Director, Accts Receivable ecurity anager Region 2 Director Director, roduction Director, Accts ayable Director, perations Region 3 Director Director, Distribution Region 4 Director Director, ervice An Introduction to nterprise Architecture 3 rd dition 328

47 A 3 Framework Area echnology Business trategy s & Artifact # and ame W-3: Knowledge & kills rofile he Knowledge and kills rofile provides a detailed inventory of what a person should know and be able to do in a particular position within the enterprise. he example provided is a Knowledge, kills, and Abilities List for nterprise Architects developed by arnegie ellon University in 2004 and updated in xample arnegie ellon University nterprise Architecture ducation tandards Knowledge and kill Areas (KAs) Institute for oftware Research International nterprise Architecture ducation tandards - opyright U/IRI Developed by Dr. cott A. Bernard Junior Architect A Apprentice (0-2 Years) id-level Architect A Journeyman (3-5 Years) enior Architect A aster (5+ Years) 1.0 A ractice and heory 1.1 Governance: lanning and Decsion-aking x 1.2 rganizational heory: ulture and ommunication x x 1.3 he Age: Driver of Architectures x x x 1.4 nterprise Architecture Frameworks x x x 1.5 Architectue Implementation ethodologies x x x 1.6 nterprise Architecture ritical uccess Factors x x x 1.7 Architecture Use in lanning/decision-aking x x x 1.8 Architecture aturity valuation x 2.0 A Documentation 2.1 trategic Goals,, and lans x x x 2.2 Business ub-architecture x x x 2.3 and Data ub-architecture x x x 2.4 ervice ub-architecture x x x 2.5 ystems ub-architecture x x x 2.6 echology ub-architecture x x x 2.7 ecurity ub-architecture x x x 2.8 Architecture tandards and Artifact ypes x x x 3.0 A Implementation 3.1 A rogram and roject stablishment x x 3.2 A Requirements and cope x x 3.3 A Framework and ethodology election x x 3.4 A ool and Repository election x x 3.5 Documenting the urrent Architecture x x 3.6 Documenting the Future Architecture x x 3.7 Architecture ransition anagement x x 3.8 Architecture onfiguration anagement x x 4.0 A roject & rogram anagement 4.1 A roject and rogram anagement Basics x 4.2 Requirements Determination x 4.3 roject and rogram chedules x 4.4 roject and rogram Budgets x 4.5 Alternatives Analysis x 4.6 anaging Risk x 4.7 arned Value anagement x 4.8 A eam Development x otes An Introduction to nterprise Architecture 3 rd dition 329