DOCSLIB.ORG

Dod Architecture Framework Version

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dod Architecture Framework Version Technical Standards View Version 1.5 w e i V s e c vi r e S / DoD Architecture Framework s m e t s y All View S Operational View 23 April 2007 Core Architecture Data Model Volume II: Product Descriptions TABLE OF CONTENTS SECTION PAGE EXECUTIVE SUMMARY .....................................................................................................XIV 1 INTRODUCTION...................................................................................................................1-1 1.1 VOLUME II PURPOSE AND INTENDED AUDIENCE..............................1-1 1.1.1 Product Description Structure..............................................................1-2 1.2 OVERVIEW.......................................................................................................1-2 2 ARCHITECTURE BASICS - VIEWS, PRODUCTS, AND ARCHITECTURE DATA .2-1 2.1 ARCHITECTURE VIEWS...............................................................................2-1 2.1.1 Definition of the Operational View ......................................................2-1 2.1.2 Definition of the Systems View .............................................................2-1 2.1.3 Definition of the Technical Standards View........................................2-2 2.1.4 Definition of the All-Views ....................................................................2-2 2.2 ARCHITECTURE PRODUCTS......................................................................2-2 2.3 ARCHITECTURE PRODUCT DEVELOPMENT........................................2-6 2.3.1 Product Development Methodology Support......................................2-6 2.3.2 Architecture Products and Levels of Detail.........................................2-8 2.3.3 Iterative Development of the Products ..............................................2-10 2.3.4 Product Templates...............................................................................2-10 2.3.5 Object-Orientation and the Unified Modeling Language Support .2-10 2.4 PRODUCT AND ARCHITECTURE DATA ELEMENT RELATIONSHIPS........................................................................................... 2-11 2.5 NET-CENTRIC GUIDANCE FOR ARCHITECTURE PRODUCTS.......2-12 2.6 CADM SUPPORT FOR ARCHITECTURE PRODUCTS .........................2-18 2.6.1 Overview and Summary of Common Data Structures – Data Element Definitions.............................................................................. 2-20 3 ALL-VIEWS PRODUCTS.....................................................................................................3-1 3.1 OVERVIEW AND SUMMARY INFORMATION (AV-1) ...........................3-1 3.1.1 Overview and Summary Information (AV-1) – Product Description.............................................................................................. 3-1 3.1.2 UML Representation .............................................................................3-2 3.1.3 Net-Centric Guidance for Overview and Summary Information (AV-1)...................................................................................................... 3-2 i 3.1.4 CADM Support for Overview and Summary Information (AV-1) ..3-3 3.2 INTEGRATED DICTIONARY (AV-2).........................................................3-16 3.2.1 Integrated Dictionary (AV-2) – Product Description.......................3-16 3.2.2 Taxonomies...........................................................................................3-17 3.2.3 UML Representation ...........................................................................3-19 3.2.4 Net-Centric Guidance for Integrated Dictionary (AV-2).................3-19 3.2.5 CADM Support for Integrated Dictionary (AV-2)...........................3-20 4 OPERATIONAL VIEW PRODUCTS..................................................................................4-1 4.1 HIGH-LEVEL OPERATIONAL CONCEPT GRAPHIC (OV-1)................4-1 4.1.1 High-Level Operational Concept Graphic (OV-1) – Product Description..............................................................................................4-1 4.1.2 UML Representation .............................................................................4-3 4.1.3 Net-Centric Guidance for High-Level Operational Concept Graphic (OV-1) ...................................................................................... 4-3 4.1.4 CADM Support for High-Level Operational Concept Graphic (OV-1)...................................................................................................... 4-4 4.2 OPERATIONAL NODE CONNECTIVITY DESCRIPTION (OV-2).......4-10 4.2.1 Operational Node Connectivity Description (OV-2) – Product Description............................................................................................4-10 4.2.2 UML Representation ...........................................................................4-13 4.2.3 Net-Centric Guidance for Node Connectivity Description (OV-2) .4-14 4.2.4 CADM Support for Operational Node Connectivity Description (OV-2).................................................................................................... 4-15 4.3 OPERATIONAL INFORMATION EXCHANGE MATRIX (OV-3) ........4-24 4.3.1 Operational Information Exchange Matrix (OV-3) – Product Description............................................................................................4-24 4.3.2 UML Representation ...........................................................................4-26 4.3.3 Net-Centric Guidance for Operational Information Exchange Matrix (OV-3)....................................................................................... 4-26 4.3.4 CADM Support for Operational Information Exchange Matrix (OV-3).................................................................................................... 4-27 4.4 ORGANIZATIONAL RELATIONSHIPS CHART (OV-4) .......................4-34 4.4.1 Organizational Relationships Chart (OV-4) – Product Description............................................................................................4-34 4.4.2 UML Representation ...........................................................................4-35 ii 4.4.3 Net-Centric Guidance for Organizational Relationships Chart (OV-4).................................................................................................... 4-35 4.4.4 CADM Support for Organizational Relationships Chart (OV-4)...4-36 4.5 OPERATIONAL ACTIVITY MODEL (OV-5)............................................4-40 4.5.1 Operational Activity Model (OV-5) – Product Description.............4-40 4.5.2 UML Representation ...........................................................................4-43 4.5.3 Net-Centric Guidance for Operational Activity Model (OV-5).......4-44 4.5.4 CADM Support for Operational Activity Model (OV-5).................4-45 4.6 OPERATIONAL ACTIVITY SEQUENCE AND TIMING DESCRIPTIONS (OV-6A, 6B, AND 6C) ...................................................... 4-52 4.6.1 Overview of Operational Activity Sequence and Timing Descriptions .......................................................................................... 4-52 4.6.2 CADM Support for Operational Activity Sequences and Threads (OV-6)....................................................................................................4-52 4.6.3 Operational Rules Model (OV-6a) .....................................................4-54 4.6.4 UML Representation ...........................................................................4-56 4.6.5 Net-Centric Guidance for Operational Rules Model (OV-6a).........4-56 4.6.6 CADM Support for Operational Rules Model (OV-6a)...................4-57 4.6.7 Operational State Transition Description (OV-6b) ..........................4-61 4.6.8 UML Representation ...........................................................................4-64 4.6.9 Net-Centric Guidance for Operational State Transition Description (OV-6b)............................................................................. 4-64 4.6.10 CADM Support for Operational State Transition Description (OV-6b) ................................................................................................. 4-65 4.6.11 Operational Event-Trace Description (OV-6c).................................4-68 4.6.12 UML Representation ...........................................................................4-71 4.6.13 Net-Centric Guidance for Operational Event-Trace Description (OV-6c).................................................................................................. 4-72 4.6.14 CADM Support for Operational Event-Trace Description (OV- 6c) .......................................................................................................... 4-73 4.7 LOGICAL DATA MODEL (OV-7) ...............................................................4-76 4.7.1 Logical Data Model (OV-7) – Product Description ..........................4-76 4.7.2 UML Representation ...........................................................................4-77 4.7.3 Net-Centric Guidance for Logical Data Model (OV-7)....................4-78 4.7.4 CADM Support for Logical Data Model (OV-7) ..............................4-79 iii 5 SYSTEMS AND SERVICES VIEW PRODUCTS ..............................................................5-1 5.1 SYSTEMS AND SERVICES INTERFACE DESCRIPTION (SV-1)...........5-1 5.1.1 Systems Interface Description (SV-1) – Product Description............5-1 5.1.2 UML Representation .............................................................................5-5 5.1.3 Net-Centric Guidance for Systems and
Load more

Recommended publications
  • Ewsolutions Enterprise Architecture, Data Architecture, Data
    EWSolutions Enterprise Architecture, Data Architecture, Data Governance, Metadata Management Case Study Leveraging Existing Investments in Systems, Data and Personnel to Improve Logistics and Supply Chain Management for Defense Operations Enterprise architecture planning and development, data architecture, metadata management, data governance, and enterprise data integration combined to ensure the success of the world's largest defense logistics and supply chain. EWSolutions, Inc. 1/25/2017 Developing and Implementing a New Defense Logistics Supply Chain: A Case Study in How EWSolutions Enabled Success for the US Department of Defense The Department of Defense (DoD) is America's oldest and largest government agency. It employs a civilian force of 742,000, along with over 1.3 million men and women on active duty; it is the United State's largest employer. Another 826,000 people serve in the National Guard and Reserve forces. The national security depends on defense installations, people, and facilities being in the right place, at the right time, with the right qualities and capacities to protect the security of the United States and allies. These military service members and civilians operate in every time zone and in every climate. More than 450,000 employees are overseas, both afloat and ashore. This complexity extends to the logistics, communication, and supply chain needed to connect and furnish these employees and dependents with all the required resources (food, clothing, weapons, etc.) The mission of the US Department of Defense is to provide the military forces needed to deter war and to protect the security of the United States. Fulfilling this mission requires a large variety of resources; securing and delivering those resources to the right place at the right time in the right quantities requires accurate information that comes from complete and valid data.
    [Show full text]
  • Enterprise Architecture
    Enterprise Architecture Dr. Adnan Albar Faculty of Computing & Information Technology King AbdulAziz University - Jeddah 1 Enterprise Architecture Methods Lecture 5 Week 5 Slides King AbdulAziz University - FCIT 2 Overview . Description Languages for Business & IT Domains . IDEF . BPMN . Testbed . ARIS . Unified Modeling Language . Service-Oriented Architecture (SOA) Slide 3 Description Languages . In domains such as business process design and software development, we find established description languages for modeling these domains. For software modeling, UML is of course, the single dominant language. In organization and process modeling, on the other hand, a multitude of languages are in use: there is no standard for models in this domain. We will focus on languages that either find widespread use or have properties that are interesting from the perspective of our goals in developing an enterprise architecture language. Slide 4 IDEF – Integrated DEFinition Methods .IDEF is a family of languages .Used to perform enterprise modeling and analysis .Currently, there are 16 IDEF methods. Of these methods, IDEF0, IDEF3, and IDEF1X (‘the core’) are the most commonly used. Slide 5 IDEF – The Scope it Covers .Functional modeling, IDEF0: The idea behind IDEF0 is to model the elements controlling the execution of a function, the actors performing the function, the objects or data consumed and produced by the function, and the relationships between business functions (shared resources and dependencies). .Process modeling, IDEF3: IDEF3 captures the workflow of a business process via process flow diagrams. These show the task sequence for processes performed by the organization, the decision logic, describe different scenarios for performing the same business functions, and enable the analysis and improvement of the workflow.
    [Show full text]
  • Infrastructure) IMS > J
    NE DO-IT-O 0 16 <i#^^0%'IW#^#^#(Hyper-Intellectual-IT Infrastructure) IMS > J TO 1 3 ¥ 3 M NEDD H»* r— • ^ ’V^^ m) 010018981-0 (Hyper-Intellectual-IT fr9, (Hyper IT) i-6Z 6 & g 1% ^ L/bo i2 NEDO-IT-0016 < (Hyper-Intel lectual-IT Infrastructure) 9H3E>J 1 3 # 3 ^ lT5fe (%) B^f-r^'a'W^ZPJf (Summary) -f — t 7-j'<7)7*0- K/O- % -y f-7-? ±K*EL/--:#<<7)->5a.v-j'^T*-j'^-7OTSmiLr1 Eft • Skit • tWs§ (Otis ti® o T S T V' £ „ Ltf' U - 7- L*{Hffi,»ftffiIBIS<7)'> 5 a. V- -> 3 >^x- ? ^-Xfijfflic-7V>TI±#<<7)*®»:C0E@»S»6L, -en<b»sili*5tL^itn(i\ *7h Ty — t’ 4-^hLfcE&tt>fc1SSSeF% • Eft • KS& k" f> $ $ & b ttv>, (1) 3>ti- (2) f -^ (3) $-y t-7-7 (4) ->i ( 5 ) 7 7 t 73H7ft#-9— fxwilttas Sti:, ±EP$t t k ic, KSUWSSiaBF^ ■ Elt ■ # ## k T-<7)FB1«6 4-$v>tti u iirn *iiM LrtlSS-S k a6* 0 (1) Hyper-IT 4 7 —-y OEE$l&teH k $l!$ (2 ) Hyper-IT -f7-y*k##<7)tbK (3) KS<7)i5tv^k (4) #@<7)SEE • IISE<7)#S (5) Hwif^silftftkn-KvyT ’tt Summary In recently years, we have broad band network and The Internet environment , using these infrastructure, we will develop knowledge co-operate manufacturing support system, which can be use various kinds of simulators and databases. But knowledge co-operate manufacturing support system has a lot of problems, such as data format, legal problems, software support system and so no.
    [Show full text]
  • Integrating IT Portfolio Management with Enterprise Architecture Management 79
    Enterprise Modelling and Information Systems Architectures Vol. 8, No. 2, December 2013 Integrating IT Portfolio Management with Enterprise Architecture Management 79 Daniel Simon, Kai Fischbach, Detlef Schoder Integrating IT Portfolio Management with Enterprise Architecture Management The management of information technology (IT) as a business has become a crucial factor in today’s complex and dynamic environments. Many firms thus have implemented IT portfolio and enterprise architecture (EA) management practices, and academic research has paid increasing attention to these concepts. However, their integration seems poorly substantiated; this article therefore seeks to answer two main questions: (1) What are differences and common characteristics of IT portfolio and EA management, and in what way can they be integrated? and (2) what factors and types might describe an integrated process design of EA management and project portfolio management in particular? To answer these questions, this study synthesises previous research and surveys EA practitioners to propose an EA management process map, as well as three descriptive factors and four clusters, which provide an integrated process design with project portfolio management. The interrelations with organisational aspects and software tool support are also explored. This article thereby clarifies and systematises the subject area while also offering advice for researchers and practitioners. 1 Introduction structured, business-like approach to IT manage- ment that comprises application, infrastructure, The notion of managing information technology service, and project portfolio management (Ben- (IT) as a business (Lientz and Larssen 2004) has son et al. 2004; Kaplan 2005). attracted significant attention, particularly as IT environments grow steadily more complex and Integration is equally critical to EA management, thus more difficult to manage.
    [Show full text]
  • Best Practices in Business Instruction. INSTITUTION Delta Pi Epsilon Society, Little Rock, AR
    DOCUMENT RESUME ED 477 251 CE 085 038 AUTHOR Briggs, Dianna, Ed. TITLE Best Practices in Business Instruction. INSTITUTION Delta Pi Epsilon Society, Little Rock, AR. PUB DATE 2001-00-00 NOTE 97p. AVAILABLE FROM Delta Pi Epsilon, P.O. Box 4340, Little Rock, AR 72214 ($15). Web site: http://www.dpe.org/ . PUB TYPE Collected Works General (020) Guides Classroom Teacher (052) EDRS PRICE EDRS Price MF01/PC04 Plus Postage. DESCRIPTORS Accounting; *Business Education; Career Education; *Classroom Techniques; Computer Literacy; Computer Uses in Education; *Educational Practices; *Educational Strategies; Group Instruction; Keyboarding (Data Entry); *Learning Activities; Postsecondary Education; Secondary Education; Skill Development; *Teaching Methods; Technology Education; Vocational Adjustment; Web Based Instruction IDENTIFIERS *Best Practices; Electronic Commerce; Intranets ABSTRACT This document is intended to give business teachers a few best practice ideas. Section 1 presents an overview of best practice and a chart detailing the instructional levels, curricular areas, and main competencies addressed in the 26 papers in Section 2. The titles and authors of the papers included in Section 2 are as follows: "A Software Tool to Generate Realistic Business Data for Teaching" (Catherine S. Chen); "Alternatives to Traditional Assessment of Student Learning" (Nancy Csapo); "Applying the Principles of Developmental Learning to Accounting Instruction" (Burt Kaliski); "Collaborative Teamwork in the Classroom" (Shelia Tucker); "Communicating Statistics Measures of Central Tendency" (Carol Blaszczynski); "Creating a Global Business Plan for Exporting" (Les Dlabay); "Creating a Supportive Learning Environment" (Rose Chinn); "Developing Job Survival Skills"(R. Neil Dortch); "Engaging Students in Personal Finance and Career Awareness Instruction: 'Welcome to the Real World!'" (Thomas Haynes); "Enticing Students to Prepare for and to Stay 'Engaged' during Class Presentations/Discussions" (Zane K.
    [Show full text]
  • Integration Definition for Function Modeling (IDEF0)
    NIST U.S. DEPARTMENT OF COMMERCE PUBLICATIONS £ Technology Administration National Institute of Standards and Technology FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) » Category: Software Standard SUBCATEGORY: MODELING TECHNIQUES 1993 December 21 183 PUB FIPS JK- 45C .AS A3 //I S3 IS 93 FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) Category: Software Standard Subcategory: Modeling Techniques Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Issued December 21, 1993 U.S. Department of Commerce Ronald H. Brown, Secretary Technology Administration Mary L. Good, Under Secretary for Technology National Institute of Standards and Technology Arati Prabhakar, Director Foreword The Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official publication relating to standards and guidelines adopted and promulgated under the provisions of Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235. These mandates have given the Secretary of Commerce and NIST important responsibilities for improving the utilization and management of computer and related telecommunications systems in the Federal Government. The NIST, through its Computer Systems Laboratory, provides leadership, technical guidance,
    [Show full text]
  • Fielder Elected
    • ——— •—- •^ »!• m«g -mmiMMa&rr »• t-^ •iwiiiiiiiwum I*T The Leading and Most Widely Circulated Weekly Newspaper in Union County WESTFIELD, NEW JERSEY, WEDNESDAY, NOVEMBEB, 5, 1913, FOURTEEN PAGKS—2 CENTS NOVEMBER 5, 1913 Money deposited in our Savings Department on or before the above date, will draw interest at 4 per cent, from NOVEMBER FIRST. Check Accounts—largo or small- ? A FEW DID The Two Clark's ore Re-elected in Westfield with Many received on liberal terms. Votes to the Good—Casey Polls Big Vote in the COUNTY DEMOGRATiO ASSETS OVER $1,000,000.00 T l/OTE YESTERDAY Fourth and is Returned to the Council ASSEMBLYCANDIDATES The Early Returns Showed Traynor Running Strong for The Oldest Banking Institution in Westfield sgistsrcd Men Were Goif- Assessor, but Denman Receives Majority Elected by About Six Hundred inp or Motoring in ' of Over Two Hundred Votes Majority and Run Far Other Placos Behind Ticket MITCHELL AND ENTIRE FOSION TICKET WINS IN NEW YORE VOTES THE TOTAL CAST MAYOR EVANS WAS DEFEATED Fielder Elected "v ivory 1.308 volt's uasi in ilnyir Kvans proved his jni|m- !<i ui tiis vlcctinn nnii 17 litritv in Westiiold by luimiup •IN liii' noxt. Governor ul" New di'i-scy. 1 rejected. There were 'J2S iiliciid of l'.'.s uriiiTSl opjuMi- voters in Wcsl- cnt but imt'oHuiiiiU'ly went down Kledcd becmise of failhfu! and cfllcionl Rcrvice it tiiis t lection which prows with liis tiok«t fur tin1 Di'inncrntic in tile past. i did not avail Uiomselvcs AsKi'inlily in llio county won out right or sufTrap-d.
    [Show full text]
  • A Study on Process Description Method for DFM Using Ontology
    Invited Paper A Study on Process Description Method for DFM Using Ontology K. Hiekata1 and H. Yamato2 1Department of Systems Innovation, Graduate School of Engineering, The University of Tokyo, 5-1-5, Kashiwanoha, Kashiwa-city, Chiba 277-8563, Japan 2Department of Human and Engineered Environmental Studies, Graduate School of Frontier Sciences, The University of Tokyo, 5-1-5, Kashiwanoha, Kashiwa-city, Chiba 277-8563, Japan [email protected], [email protected] Abstract A method to describe process and knowledge based on RDF which is an ontology description language and IDEF0 which is a formal process description format is proposed. Once knowledge of experienced engineers is embedded into the system the knowledge will be lost in the future. A production process is described in a proposed format similar to BOM and the process can be retrieved as a flow diagram to make the engineers to understand the product and process. Proposed method is applied to a simple production process of common sub-assembly of ships for evaluation. Keywords: Production process, DFM, Ontology, Computer system 1 INTRODUCTION (Unified Resource Identifier) is assigned to all the objects, There are many research and computer program for and metadata is defined for all objects using the URI. supporting optimization of production process in Metadata is defined as a statement with subject, shipyards. And knowledge of experienced engineers is predicate and object. The statement is called triple in embedded into the system. Once the knowledge is RDF. Two kinds of elements, Literal or Resource, can be embedded into computer system, the knowledge is not a component of a statement.
    [Show full text]
  • Enterprise Architecture for Project Managers
    Enterprise Architecture for Project Managers JK Corporate Services (JKCS) Authored by: Stan Ketchum, PMP Enterprise Architecture for Project Managers by Stan Ketchum is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License Enterprise Architecture for Project Managers Table of Contents Introduction .................................................................................................................................... 1 Purpose ........................................................................................................................................... 2 What Is Enterprise Architecture? ................................................................................................... 2 Why Is EA Needed? ..................................................................................................................... 2 What are the benefits of EA? ...................................................................................................... 3 EA vs Projects .............................................................................................................................. 3 What Does EA Consist of? ............................................................................................................... 4 EA Domains ................................................................................................................................. 4 Business Architecture ............................................................................................................
    [Show full text]
  • Architecting Software the SEI Way Twitter #Seiarchitecture © 2012 Carnegie Mellon University Outline Essential Problems for Architects
    Analyzing and Evaluating Enterprise Architectures John Klein Senior Technical Staff John has over 20 years experience developing systems and software. He joined SEI in 2008. Before joining SEI, John was a chief architect at Avaya, Inc. There his responsibilities included development of multimodal agents, architectures for communication analytics, and the creation and enhancement of the Customer Interaction Software Product Line architecture. Prior to that, John was a software architect at Quintus, where he designed the first commercially successful multi- channel integrated contact center product and led the technology integration of the product portfolio as Quintus acquired several other companies. See his full bio at: www.sei.cmu.edu/go/architecting-software-the-sei-way Architecting Software the SEI Way Twitter #SEIArchitecture © 2012 Carnegie Mellon University Outline Essential problems for architects - • How do we efficiently translate business goals into quality attribute requirements? • How do we ensure that these quality attribute requirements are reflected in the tradeoffs and decisions that shaped the architecture? Agenda • Review of the SEI perspective on architecture-centric engineering • Scaling from software context to systems of systems and enterprise architectures • An approach to developing quality attribute requirements for enterprise architectures • An approach to first-pass evaluation of enterprise architectures • Tying together EA and system/software analysis and evaluation Architecting Software the SEI Way 1 Twitter #SEIArchitecture © 2012 Carnegie Mellon University Architecture-centric Engineering – Software and Systems IMPLEMENT AND EVOLVE DESIGN IMPLEMENT BUSINESS AND MISSION GOALS ARCHITECTURE SYSTEM SATISFY CONFORM SATISFY Architecting Software the SEI Way Twitter #SEIArchitecture © 2012 Carnegie Mellon University Principles of Architecture-Centric Engineering Every system has an architecture, regardless of scale.
    [Show full text]
  • 4.3 NWS ENTERPRISE ARCHITECTURE Bobby Jones
    4.3 NWS ENTERPRISE ARCHITECTURE Bobby Jones*, Chief IT Architect Barry West, Chief Information Officer NOAA’s National Weather Service 1 INTRODUCTION An Enterprise Architecture (EA) is a comprehensive blueprint that aligns an organization’s business In 1996, Congress required Federal Agency Chief processes with its Information Technology (IT) Information Officers (CIO) to develop, maintain, and strategy. It is documented using multiple facilitate integrated systems architectures with the architectural models or views that show how the passage of the Clinger-Cohen Act. Additionally, current and future needs of an organization will be Office of Management and Budget (OMB) issued met. The key components of the EA are: guidance that requires agency information systems investments to be consistent with Federal, Agency, • Accurate representation of the and bureau architectures. Enterprise Architectures business environment, strategy and (EA) are “blueprints” for systematically and critical success factors completely defining an organization’s current • Comprehensive documentation of (baseline) or desired (target) environment. EAs are business units and key processes essential for evolving information systems and • Views of the systems and data that developing new systems that optimize their mission support these processes value. This is accomplished in logical or business • A set of technology standards that terms (e.g., mission, business functions, information define what technologies and flows, and systems environments) and technical products are approved to be used terms (e.g., software, hardware, communications), within an organization, and includes a sequencing plan for transitioning complemented by prescriptive from the baseline environment to the target enterprise-wide guidelines on how environment. to best apply these technology standards in creating business If defined, maintained, and implemented effectively, applications.
    [Show full text]
  • Using Telelogic DOORS and Microsoft Visio to Model and Visualize
    Using DOORS & Visio to Model and Visualize Complex Business Processes Bob Sherman - [email protected] [email protected] Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] 1 © Telelogic AB Agenda • The Unmet Need • The Solution – Strategy: Business Driven Application Lifecycle – Tactics: Business Modeling via DOORS & VISIO – Tactics: DOORS/VISIO Integration • Case Study Results Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] 2 © Telelogic AB Chronic IT Project Problems Top IT Project Problems • User/Stakeholder Engagement Outages • Unclear Objectives • Incomplete or Changing Requirements *Standish Group Chaos Studies Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors: Bob Sherman ([email protected]), [email protected] 3 © Telelogic AB Chronic IT Project Problems Rework • 35-65% of project budget *Standish Group spent on rework. • ~50% of rework is due to requirements errors * IEEE & University of Southern California Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes - v1.0 © 2005 Galactic Solutions Group LLC – Authors:
    [Show full text]