DOCSLIB.ORG

Telelogic Strengthens Its Enterprise Architecture and Development Lifecycle Tool Suite

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Telelogic Strengthens Its Enterprise Architecture and Development Lifecycle Tool Suite News Release Contacts: Ingemar Ljungdahl Catharina Paulcén Chief Technology Officer EVP Corporate Communications Phone +46 40 174701 Phone +46 40 174730 E-mail: ingemar.ljungdahl telelogic.com E-mail: catharina.paulcen telelogic.com Telelogic Strengthens Its Enterprise Architecture and Development Lifecycle Tool Suite - SYSTEM ARCHITECT and SYNERGY/Change Help Manage the Architecture and Development Lifecycle at the Enterprise Level - Malmö, SWEDEN – May 16, 2006 – Telelogic (Stockholm Exchange:TLOG), the leading provider of software solutions that align advanced systems and software development with business objectives, today announced major updates to Telelogic’s SYSTEM ARCHITECT enterprise architecture and modeling tools to increase the efficiency of business operations and SYNERGY/Change, an enterprise change management tool to improve the effectiveness of any development environment. These new offerings are included as part of the Telelogic Lifecycle Suite, a complete package of Telelogic software tools designed to empower organizations in implementing and managing their enterprise architecture and system and software development at the enterprise level. “Telelogic’s open, flexible product suite delivers a best-in-class, scalable family of products that extend the development environment into the executive suite,” said Ingemar Ljungdahl, Chief Technology Officer, Telelogic. “Our goal is to offer organizations the tools to connect business requirements and processes with customer needs and ensure that requirements remain an integral part of the engineering and development process. Our product suite is being updated to support innovation and drive value into the design and development of systems and software for both businesses and agencies worldwide.” SYSTEM ARCHITECT Telelogic SYSTEM ARCHITECT enables organizations worldwide to design, visualize, analyze and publish business models and enterprise architectures that help them understand the relationships among their technology, processes and data. With this information, organizations can be more agile and flexible in addressing their ever- changing technology and business objectives. Telelogic’s SYSTEM ARCHITECT was recently placed in the leaders quadrant of Gartner’s “Magic Quadrant for Enterprise Architecture Tools, 1Q06” released on April 5, 2006, and authored by Greta A. James and Robert A. Handler.. (The MQ report is not a ranking.) Page 1 of 4 SYSTEM ARCHITECT 10.4 now offers the following new options: • SYSTEM ARCHITECT/XT. This new, streamlined, Web-based addition to the SYSTEM ARCHITECT family makes enterprise architecture development actionable by offering live access from anywhere. By increasing communication and collaboration in a distributed workforce, SYSTEM ARCHITECT/XT transforms geographically dispersed workgroups into an integrated team and encourages greater participation across the organization. SYSTEM ARCHITECT/XT does this by extending real-time access to its live repository to users anywhere in the world through a central portal. Users can make changes to the repository at any time; all information in the repository is centrally managed. SYSTEM ARCHITECT/XT‘s highly intuitive user interface enables users to do repository searches and view models. Role-based templates, including everything from high-level graphical pie charts to more complex process diagrams or use cases, can be created or customized by an architecture team for key stakeholder groups. Specialized templates are being offered for the Dept. of Defense Architectural Framework (DoDAF). Like any Web browser, users can create bookmarks in a favorites menu to help them more quickly find the information they need. SYSTEM ARCHITECT/XT facilitates the user’s ability to comment on the architecture while it is in development. XT is available as an option to SYSTEM ARCHITECT 10.4. • SYSTEM ARCHITECT/ERP. Telelogic now offers completely integrated support for all major ERP systems, including SAP and Oracle (Peoplesoft, Siebel Systems and JD Edwards). SYSTEM ARCHITECT/ERP gives organizations a thorough understanding of their ERP implementation and helps reduce the risks associated with changing processes and applications over time without a detailed knowledge of the underlying ERP system. This is possible with SYSTEM ARCHITECT/ERP’s auto- discovery features to directly import ERP metadata into SYSTEM ARCHITECT for analysis. Data, metadata, data relationships, applications and data warehouses can be modeled and visualized so organizations can understand how applications interact with the ERP system. This feature is available as an option to SYSTEM ARCHITECT 10.4. SYSTEM ARCHITECT 10.4 offers the following integrated features: • Service-oriented architecture (SOA) Support. Integrated into SYSTEM ARCHITECT 10.4 are new BPEL upgrades that automate modeling support as a first step in the linking of Web services. Using SYSTEM ARCHITECT 10.4, organizations can translate business process models into business process execution language (BPEL). Developers can then use the resulting data in a workflow tool to begin linking Web services to create composite applications. SYSTEM ARCHITECT 10.4’s new XSD Management (XML Schema) capability ultimately enables linking of schema to BPEL messages via its (Business Process Modeling Notation) BPMN and UML modeling notations, an integral step in any SOA implementation. Page 2 of 4 • New User Interface. SYSTEM ARCHITECT 10.4 user interface has been fully redesigned and optimized to provide an improved user experience. The Microsoft windows look-and-feel of the toolbars and icons gives users an easier way to navigate throughout SYSTEM ARCHITECT and quicker access to frequently used areas. The user interface continues to support complete customization by users for personalized workflow. “Boosts in application development productivity and quality come most readily from consistent execution of two approaches, a balance of effective management processes and repeatable low-level development processes,” said Jim Duggan, Research Vice President, Gartner. “What is required is a suite of enterprise-level tools to help accomplish organizations combine these two approaches easily and effectively.” SYNERGY/Change Telelogic also announced a new release of its SYNERGY/Change for more flexible and user-friendly enterprise-level change management. A Web-based change management solution, SYNERGY/Change provides enterprise-wide lifecycle change control for an organization’s digital assets during the systems and software development lifecycle. It enables users to assess and authorize change, from both internal and external sources, using a change control workflow customized to organizational needs. With its recent enhancements, SYNERGY/Change can be used for managing incidents, problems and changes in IT Service Management improvement programs, such as ITIL (ISO 20000). New features in SYNERGY/Change 4.5 include: • Enterprise Scalability. A new and streamlined user interface makes the tool easier to adopt and deploy across globally distributed development community. The tool is now scalable to the enterprise level so stakeholders worldwide can be part of the change management process, quickly assess the impact of change and monitor performance in the development process, regardless of their location or language. • IBM/Rational ClearCase Support. SYNERGY/Change has been extended to support IBM/Rational ClearCase. Users can now track changes to requirements in Telelogic DOORS, and make software configuration changes in either Telelogic SYNERGY/CM and/or IBM/Rational ClearCase from a single change management repository. They can also more easily combine software development environments as a result of an acquisition, contractual obligation, or legacy development. Organizations avoid the training and implementation burdens associated with integrating multiple change management solutions. SYNERGY/Change also offers the following new option: • Development Management Dashboard. A totally redesigned Telelogic Dashboard is also being released in conjunction with SYNERGY/Change, and Telelogic DOORS. The Dashboard features core software metrics for Six Sigma and Capability Maturity Model Integration (CMMI) initiatives. Using the Dashboard, users gain insight into the product development process, including tracking defect rates, scope creep and requirements churn, and can proactively address trends in development performance and optimization. With Dashboard, product managers also have access to a rolled-up view of performance metrics across all development environments. Page 3 of 4 Telelogic Lifecycle Suite Integrated Licensing Update Telelogic also announced the addition of the SYSTEM ARCHITECT enterprise architecture tools and FOCAL POINT, Telelogic’s decision support tool for portfolio management, to the Telelogic Lifecycle Suite (TLS 2006). This Suite offers a complete package of six Telelogic products with a common installation process and licensing structure. An innovative, token-based licensing structure allows users to move among Telelogic products by allocating tokens as needed. Telelogic products featured in the TLS 2006 now include: DOORS, FOCAL POINT, SYNERGY/Change, SYNERGY/CM, SYSTEM ARCHITECT and TAU. “Our latest product announcements deliver on Telelogic’s commitment to offering its customers an enterprise-wide lifecycle management product suite,” said Anders Lidbeck President & CEO, Telelogic. “Organizations are faced with the challenge of first aligning development with business
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]
  • 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]
  • Sysml Distilled: a Brief Guide to the Systems Modeling Language
    ptg11539604 Praise for SysML Distilled “In keeping with the outstanding tradition of Addison-Wesley’s techni- cal publications, Lenny Delligatti’s SysML Distilled does not disappoint. Lenny has done a masterful job of capturing the spirit of OMG SysML as a practical, standards-based modeling language to help systems engi- neers address growing system complexity. This book is loaded with matter-of-fact insights, starting with basic MBSE concepts to distin- guishing the subtle differences between use cases and scenarios to illu- mination on namespaces and SysML packages, and even speaks to some of the more esoteric SysML semantics such as token flows.” — Jeff Estefan, Principal Engineer, NASA’s Jet Propulsion Laboratory “The power of a modeling language, such as SysML, is that it facilitates communication not only within systems engineering but across disci- plines and across the development life cycle. Many languages have the ptg11539604 potential to increase communication, but without an effective guide, they can fall short of that objective. In SysML Distilled, Lenny Delligatti combines just the right amount of technology with a common-sense approach to utilizing SysML toward achieving that communication. Having worked in systems and software engineering across many do- mains for the last 30 years, and having taught computer languages, UML, and SysML to many organizations and within the college setting, I find Lenny’s book an invaluable resource. He presents the concepts clearly and provides useful and pragmatic examples to get you off the ground quickly and enables you to be an effective modeler.” — Thomas W. Fargnoli, Lead Member of the Engineering Staff, Lockheed Martin “This book provides an excellent introduction to SysML.
    [Show full text]
  • On Using Sysml, Dodaf 2.0 and UPDM to Model the Architecture for the NOAA's Joint Polar Satellite System (JPSS) Ground System (GS)
    https://ntrs.nasa.gov/search.jsp?R=20120009882 2019-08-30T20:31:32+00:00Z On Using SysML, DoDAF 2.0 and UPDM to Model the Architecture for the NOAA's Joint Polar Satellite System (JPSS) Ground System (GS) Jeffrey L. Hayden' and Alan Jeffiies' Jeffries Technology Solutions, Inc. (JeTSI), Herndon, VA, 20170, USA The JPSS Ground System is a lIexible system of systems responsible for telemetry, tracking & command (TT &C), data acquisition, routing and data processing services for a varied lIeet of satellites to support weather prediction, modeling and climate modeling. To assist in this engineering effort, architecture modeling tools are being employed to translate the former NPOESS baseline to the new JPSS baseline, The paper will focus on the methodology for the system engineering process and the use of these architecture modeling tools within that process, The Department of Defense Architecture Framework version 2,0 (DoDAF 2.0) viewpoints and views that are being used to describe the JPSS GS architecture are discussed. The Unified Profile for DoOAF and MODAF (UPDM) and Systems Modeling Language (SysML), as ' provided by extensions to the MagicDraw UML modeling tool, are used to develop the diagrams and tables that make up the architecture model. The model development process and structure are discussed, examples are shown, and details of handling the complexities of a large System of Systems (SoS), such as the JPSS GS, with an equally complex modeling tool, are described. I. Introduction N February 2010, the US Government restructured the National Polar-orbiting Operational Enviromnental Satellite S),stem (NPOESS) into the National Oceanic and Atmospheric Administration (NOAA)lNational Aeronautics and Space Agency (NASA) Joint Polar Satellite System (JPSS) and the Department of Defense's Defense Weather I Satellite System (DWSS).
    [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]
  • Sodiuswillert Product Brochure
    UNLOCKING ASSETS TO EMPOWER INNOVATION THROUGH ENGINEERING DATA INTEGRATION PRODUCT SHEET Move Models from Rhapsody® to MagicDraw™ Whether your goal is to migrate to MagicDraw or deliver in the MagicDraw format, the Publisher for Rhapsody makes model recreation easy and repeatable. AUTOMATE MODEL TRANSFORMATION FROM RHAPSODY TO MAGICDRAW Creating MagicDraw models may be a necessary step in today’s multi-tool Use Cases: environment. We understand the retention of model elements, structure, and diagram layouts are critical and required in any workflow. The Publisher • Publish: maintain your for Rhapsody enables your team to explore the business’s needs of tool knowledge base in Rhapsody flexibility with confidence. but deliver to a customer to integrate in MagicDraw. Explore And Deliver Mandated File Formats • Migrate: move your data out of Publish your Rhapsody models to MagicDraw to deliver mandated file Rhapsody and further develop formats for a customer. Explore your Rhapsody models in MagicDraw for in MagicDraw. projects that mandate the use of MagicDraw for development. Keep your team, training, and licenses with your Rhapsody investment and still deliver to the program’s requirements. $ SAVE ENGINEERING TIME MAINTAIN DATA INTEGRITY IMPROVE YOUR ROI Save months or years of critical Manually migrating data from one Building complex Rhapsody models engineering resources converting SysML tool to another can be prone and correctly converting them into and validating re-written models. to error. The Publisher for Rhapsody MagicDraw can take engineering With the Publisher for Rhapsody, accurately migrates model elements, teams months or even years to users of Rhapsody can automate the diagram and, layouts created in your complete.
    [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]
  • 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]
  • 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
    [Show full text]