Enterprise Data Architecture: Development Scenarios Using ORM
This paper describes the enterprise wide use of ORM to drive individual project development through requirements, design, construction, and implementation process using SDLC practices within Boston Scientific. Components used to construct, track, administer, and manage data models using nORMa for conceptual data models and interfaces to an industry standard tool for the logical and physical data models are laid out in one of the three following scenarios: 1) New customized application development, 2) OTSS configuration and customization (Off the Shelf System), and 3) Reverse Engineering Existing Applications. This paper illustrates how the second scenario “OTSS configuration and customization” leverages Object Role Modeling to provide the data architect with a fact based conceptual model that is integrated with a business glossary. The ultimate goal is to provide a common understanding of the business at a conceptual level and at the same time provide a comprehensive and deep ‘where used’ capability that supports a variety of common functions for Data Architects at the Enterprise level and Data Architects at the Project level.
KeywordsDevelopment Scenario Enterprise Architecture Database Management System Business Domain Enterprise Architect
Unable to display preview. Download preview PDF.
- 1.Chevalier, J., Pramann, M.: Boston Scientific Corporation, Enterprise Organizational Governance, Enterprise Architecture White Paper (2009)Google Scholar
- 2.Chevalier, J., Pramann, M.: Boston Scientific Corporation, Enterprise Architecture Value, Enterprise Architecture White Paper (2009)Google Scholar
- 5.Excerpt from Wikipedia, Commercial off-the-shelf (2011)Google Scholar
- 6.Silver, C.: Why cloud computing must evolve Commentary: Unstructured data are a challenge to current technologies. MarketWatch Commentary (July 11, 2011)Google Scholar