DOCSLIB.ORG

The Importance of Data Models in Enterprise Metadata Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Importance of Data Models in Enterprise Metadata Management THE IMPORTANCE OF DATA MODELS IN ENTERPRISE METADATA MANAGEMENT October 19, 2017 © 2016 ASG Technologies Group, Inc. All rights reserved HAPPINESS IS… SOURCE: 10/18/2017 TODAY SHOW – “THE BLUE ZONE OF HAPPINESS” – DAN BUETTNER • 3 Close Friends • Get a Dog • Good Light • Get Religion • Get Married…. Stay Married • Volunteer • “Money will buy you Happiness… well, it’s more about Financial Security” • “Our Data Models are now incorporated within our corporate metadata repository” © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable 2. Data Models can in be incorporated into your corporate metadata repository © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable 2. Data Models can in be incorporated into your corporate metadata repository 3. ASG Technologies can provide an overall solution with services to accomplish #2 above and more for your company. © 2016 ASG Technologies Group, Inc. All rights reserved AGENDA Data model imports to the metadata collection View and search capabilities Traceability of physical and logical models End-to-End Data Lineage, impact analysis Metadata workflow and lifecycle management © 2016 ASG Technologies Group, Inc. All rights reserved DATA MODELING LANDSCAPE DATA MODELING TO ENTERPRISE METADATA MANAGEMENT – (EMM) DATA MODEL TOOLS DATA MODEL CAPABILITIES EMM • ERwin • Forward / Reverse • Metadata Repository Engineering – Data Model • IDERA Er-Studio – Business Glossary • Mapping – Reference Data • IBM InfoSphere Data – Conceptual Architect – Logical – Physical • Oracle SQL Developer DM • End-to-End Data Lineage • Data Dictionary Standards • SAP Power Designer • More … • Sparx Enterprise Architect • Others … © 2016 ASG Technologies Group, Inc. All rights reserved DATA MODELING LANDSCAPE BASF – “WE DON’T MAKE THE WATER, WE MAKE IT CLEANER” ASG – “WE DON’T MAKE THE DATA MODEL, WE INCORPORATE IT WITHIN YOUR METADATA REPOSITORY” DATA MODEL TOOLS DATA MODEL CAPABILITIES EMM • ERwin • Forward / Reverse • Metadata Repository Engineering – Data Model • IDERA Er-Studio – Business Glossary • Mapping – Reference Data • IBM InfoSphere Data – Conceptual Architect – Logical – Physical • Oracle SQL Developer DM • End-to-End Data Lineage • Data Dictionary Standards • SAP Power Designer • More … • Sparx Enterprise Architect • Others … © 2016 ASG Technologies Group, Inc. All rights reserved Populating the Metadata Repository Could be manually input for the content on the left …. • Business Glossary • Data Models – Glossary, Contexts, Terms – Entities, attributes, relationships, … • Business Packages • Relational Databases – Business Rules, Processes, Critical Data – Tables, Columns, indexes, ... Elements, Policies, Standards • Transformations • Business Applications – Task, Maps, Transformations, … – Application • Business Intelligence • Reference Data – Reports, Cubes, Fields, Maps, … – Contexts, Concepts, Values, Meanings, Permissible Values, Hierarchies • Data Structures – Files, fields, … • Big Data © 2016 ASG Technologies Group, Inc. – Tables, Files, Streams, … All rights reserved Populating the Metadata Repository Could be manually input for the content on the left …. But not for the content on the right !! • Business Glossary • Data Models – Glossary, Contexts, Terms – Entities, attributes, relationships, … • Business Packages • Relational Databases – Business Rules, Processes, Critical Data – Tables, Columns, indexes, ... Elements, Policies, Standards • Transformations • Business Applications – Task, Maps, Transformations, … – Application • Business Intelligence • Reference Data – Reports, Cubes, Fields, Maps, … – Contexts, Concepts, Values, Meanings, Permissible Values, Hierarchies • Data Structures – Files, fields, … • Big Data © 2016 ASG Technologies Group, Inc. – Tables, Files, Streams, … All rights reserved Metadata Collection / Import Metadata Collection Architecture – Modelling Bus – (Bi Directional) Enterprise Architecture Modelling Rochade Application Import • SAG Predict • ARIS Toolset Export Determine • Borland Convert to Existing • CaliberRM Item Names Import File Standard Items • Together Control/Center Format • Casewise Corporate Modeler • COOL:Biz ; COOL:gen Names File • PowerDesigner • ER/Studio • ERwin • IBM/Rational Rochade Compare • Data Architect File • Software Modeler (RSM) Tool File • Software Architect (RSA) • System Architect • Systems Developer • Rose • Rational Rose XDE • mictroTool case/4/0 © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Collection / Import Metadata Collection Architecture – Application Model – Physical and Logical Layer - Process • Scan in the models • Define rules and process • Conceptual and Logical entity names should match. • There has to be a link between physical table with the logical entity in the application model (as shown in figure) • Custom work to provide audit reports, dashboards etc. For example: • Find database tables which are based on physical model. • Find physical model entities which are not implemented in the database. • Find missing links/mismatches the enterprise model and application models • Standard model linker will link model to physical data. • Custom linker is required to create the link between conceptual and logical/physical models. © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Browser – View © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Browser – View © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Browser – Search © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Browser – Search - Account © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence MyInfoAssist – Search – Account – Logical and Physical views © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Traceability – Logical and Physical views © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Traceability – Logical Model Reporting © 2016 ASG Technologies Group, Inc. All rights reserved IMPLEMENTING DATA LINEAGE ID Critical Data Scan Lineage Automate Lineage We build out a reverse tracing methodology and base line for comprehensive and accurate end to end data lineage. Business Glossary Business Traceability Change Detection © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence End to End Zero Gap Data Lineage – Account – Business application view © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence End to End Zero Gap Data Lineage – Account – High Level view with Impact Analysis © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence End to End Zero Gap Data Lineage – Account – Detailed Level view with ETL and Impact Analysis © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence End to End Data Lineage – Account – Detailed Level view – Impact Analysis and Visualization © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence End to End Data Lineage – SnapShot – Lineage Comparison – Impact Analysis and Visualization 1) Current WIP Lineage 2) Click to Compare WIP changes with Prod (high level) within the Rochade Browser 3) WIP/Production compare at a column level Legend: Grey=same in both Red=Deleted Green=Added © 2016 ASG Technologies Group, Inc. All rights reserved Metadata Repository Data Intelligence Metadata Workflow and lifecycle management Governance Board Business & Data Stewards © 2016 ASG Technologies Group, Inc. All rights reserved ASG Enterprise Data Intelligence Core Capabilities New words here…. DATA GOVERNANCE Enterprise Metadata, Business modeling, CDE subscription, Workflow, 01 Issue management DATA LINEAGE Lineage Life Cycle, Snapshot, 02 Stitching, Impact Analysis, Data Lineage Appliance AUTO DATA COLLECTION Application discovery & 03 understanding via 230+ Scanners for structured & unstructured data DATA DISCOVERY 04 Global search, drill-down REGS & COMPLIANCE SUPPORT 05 Attestation documents and Reports © 2016 ASG Technologies Group, Inc. All rights reserved 27 SUMMARY DATA MODELING TO ENTERPRISE METADATA MANAGEMENT • Automated scanners or buses reduce complexity and increase accuracy • Look for one solution that can provide full EMM • Implementation Services will be key Training & Consulting Scanner Development Custom Development Services On-premise & SaaS Implementation Services Industry Leading Metadata Best Practices Services Packages SaaS Hosting & Maintenance Resources Metadata Practice © 2016 ASG Technologies Group, Inc. Experts All rights reserved 3 POINTS TO REMEMBER – QUIZ TIME SOURCE: 10/19/2017 DAMA NYC – NOONTIME SPEAKER SLOT – MIKE WANYO – ASG TECHNOLOGIES 1. Happiness is individually sought and achievable © 2016 ASG Technologies Group, Inc. All rights reserved 3 POINTS TO REMEMBER SOURCE: 10/19/2017 DAMA
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]
  • Powerdesigner 16.6 Data Modeling
    SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82
    [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]
  • Data Model Standards and Guidelines, Registration Policies And
    Data Model Standards and Guidelines, Registration Policies and Procedures Version 3.2 ● 6/02/2017 Data Model Standards and Guidelines, Registration Policies and Procedures Document Version Control Document Version Control VERSION D ATE AUTHOR DESCRIPTION DRAFT 03/28/07 Venkatesh Kadadasu Baseline Draft Document 0.1 05/04/2007 Venkatesh Kadadasu Sections 1.1, 1.2, 1.3, 1.4 revised 0.2 05/07/2007 Venkatesh Kadadasu Sections 1.4, 2.0, 2.2, 2.2.1, 3.1, 3.2, 3.2.1, 3.2.2 revised 0.3 05/24/07 Venkatesh Kadadasu Incorporated feedback from Uli 0.4 5/31/2007 Venkatesh Kadadasu Incorporated Steve’s feedback: Section 1.5 Issues -Change Decide to Decision Section 2.2.5 Coordinate with Kumar and Lisa to determine the class words used by XML community, and identify them in the document. (This was discussed previously.) Data Standardization - We have discussed on several occasions the cross-walk table between tabular naming standards and XML. When did it get dropped? Section 2.3.2 Conceptual data model level of detail: changed (S) No foreign key attributes may be entered in the conceptual data model. To (S) No attributes may be entered in the conceptual data model. 0.5 6/4/2007 Steve Horn Move last paragraph of Section 2.0 to section 2.1.4 Data Standardization Added definitions of key terms 0.6 6/5/2007 Ulrike Nasshan Section 2.2.5 Coordinate with Kumar and Lisa to determine the class words used by XML community, and identify them in the document.
    [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]
  • Metamodeling and Method Engineering with Conceptbase”
    This is a pre-print of the book chapter M. Jeusfeld: “Metamodeling and method engineering with ConceptBase” . In Jeusfeld, M.A., Jarke, M., Mylopoulos, J. (eds): Metamodeling for Method Engineering, pp. 89-168. The MIT Press., 2009; the original book is available from MIT Press http://mitpress.mit.edu/node/192290 This pre-print may only be used for scholar, non-commercial purposes. Most of the sources for the examples in this chapter are available via http://merkur.informatik.rwth-aachen.de/pub/bscw.cgi/3782591 for download. They require ConceptBase 7.0 or later available from http://conceptbase.cc. Metamodeling and Method Engineering with ConceptBase Manfred Jeusfeld Abstract. This chapter provides a practical guide on how to use the meta data repository ConceptBase to design information modeling methods by using meta- modeling. After motivating the abstraction principles behind meta-modeling, the language Telos as realized in ConceptBase is presented. First, a standard factual representation of statements at any IRDS abstraction level is defined. Then, the foundation of Telos as a logical theory is elaborated yielding simple fixpoint semantics. The principles for object naming, instantiation, attribution, and specialization are reflected by roughly 30 logical axioms. After the language axiomatization, user-defined rules, constraints and queries are introduced. The first part is concluded by a description of active rules that allows the specification of reactions of ConceptBase to external events. The second part applies the language features of the first part to a full-fledged information modeling method: The Yourdan method for Modern Structured Analysis. The notations of the Yourdan method are designed along the IRDS framework.
    [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 Complex Business Processes
    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes “The Business Driven Application Lifecycle” Bob Sherman Procter & Gamble Pharmaceuticals [email protected] Michael Sutherland Galactic Solutions Group, LLC [email protected] Prepared for the Telelogic 2005 User Group Conference, Americas & Asia/Pacific http://www.telelogic.com/news/usergroup/us2005/index.cfm 24 October 2005 Abstract: The fact that most Information Technology (IT) projects fail as a result of requirements management problems is common knowledge. What is not commonly recognized is that the widely haled “use case” and Object Oriented Analysis and Design (OOAD) phenomenon have resulted in little (if any) abatement of IT project failures. In fact, ten years after the advent of these methods, every major IT industry research group remains aligned on the fact that these projects are still failing at an alarming rate (less than a 30% success rate). Ironically, the popularity of use case and OOAD (e.g. UML) methods may be doing more harm than good by diverting our attention away from addressing the real root cause of IT project failures (when you have a new hammer, everything looks like a nail). This paper asserts that, the real root cause of IT project failures centers around the failure to map requirements to an accurate, precise, comprehensive, optimized business model. This argument will be supported by a using a brief recap of the history of use case and OOAD methods to identify differences between the problems these methods were intended to address and the challenges of today’s IT projects.
    [Show full text]
  • Principles of the Concept-Oriented Data Model Alexandr Savinov
    Principles of the Concept-Oriented Data Model Alexandr Savinov Institute of Mathematics and Computer Science Academy of Sciences of Moldova Academiei 5, MD-2028 Chisinau, Moldova Fraunhofer Institute for Autonomous Intelligent System Schloss Birlinghoven, 53754 Sankt Augustin, Germany http://www.conceptoriented.com [email protected] Principles of the Concept-Oriented Data Model Alexandr Savinov Institute of Mathematics and Computer Science, Academy of Sciences of Moldova Academiei 5, MD-2028 Chisinau, Moldova Fraunhofer Institute for Autonomous Intelligent System Schloss Birlinghoven, 53754 Sankt Augustin, Germany http://www.conceptoriented.com [email protected] In the paper a new approach to data representation and manipulation is described, which is called the concept-oriented data model (CODM). It is supposed that items represent data units, which are stored in concepts. A concept is a combination of superconcepts, which determine the concept’s dimensionality or properties. An item is a combination of superitems taken by one from all the superconcepts. An item stores a combination of references to its superitems. The references implement inclusion relation or attribute- value relation among items. A concept-oriented database is defined by its concept structure called syntax or schema and its item structure called semantics. The model defines formal transformations of syntax and semantics including the canonical semantics where all concepts are merged and the data semantics is represented by one set of items. The concept-oriented data model treats relations as subconcepts where items are instances of the relations. Multi-valued attributes are defined via subconcepts as a view on the database semantics rather than as a built-in mechanism.
    [Show full text]