Elements Repository Presentation


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The Elements Repository is a highly scalable Oracle-based data management system specifically designed for the management and analysis of dynamic, highly-interrelated data. It is a significant extension to Oracle that allows rapid configuration of the database itself with the automatic creation of an extensive user interface that supports data entry, data review, reporting and data mining functions. The Repository Information Model can be configured to suit customer or application needs using a built-in graphical tool. The Elements Repository supports the definition of processes and rules that control the An extensive user interface
  • Enterprise Elements, Inc. is currently focused on Enterprise Architecture data management and Application Portfolio Management. Future additional planned products are listed below.
  • In other words, a significant amount of the application front-end and key enterprise-class back end features are available automatically as part of the platform. Any extension of one of the shipping applications, such as “DoDAF Elements,” or anything configured from scratch by a customer will have these features without any additional programming or configuration work.
  • Process Configuration Capabilities: -One or more state machines (processes) can be defined for each type of information in the tool -If there are multiple processes, their rules can interact (e.g. if a “sub process” is defined, then a rule could be declared that requires that sub process to be completed for the containing process continues) -The sequence of steps is constrained to the ordering defined by the process -Access control (to the attribute level) can be set differently per process step. For example, referring to the simple process illustrated in this slide, the attributes of a “Proposed” item (such as a business rule, requirements, strategic plan element, business process step, etc.) might be read/write to the authoring team and completely invisible to the production environment. When in “Review” it might then be read-only to the authoring team, read/write to the review team, and still invisible to the production environment. When it is finally “Accepted” it could then be read-only to everyone, and finally visible to the production environment (and therefore available for use). -Constraints can be applied to the transitions to further enforce the process. E.g. certain fields might have to be filled out or limited to certain ranges of values for a transition to be allowed. This is different from a direct field constraint in that it allows the constraints to be “violated” until the promotion needs to occur. For example, when something is in “Proposed,” the editor might not know all the values immediately, but would still like to fill some of them out and save the data. A field constraint would stop this. With the transition constraint, the user could come back to the record as many times as necessary to get the data complete. -Triggers on transitions. Email alerts, transitions on other processes, transactions to other systems, etc. can all be triggered by a promotion from one state to another.
  • Data can be partitioned using row-level security so a “master” view can be given to certain users, with access to all data in the system and any number of “sub-views” that have access only to the portions that are relevant to their project, organization, role, task, etc. It is also possible to have common data shared across the sub-views. Shared data might be strategic requirements, a “baselined” or “production” set of assets, the master application list (if they are doing portfolio management), regulatory requirements, etc.
  • The Elements Repository can manage metadata and data from multiple source environments in one operational instance. This allows analysis to be done across data sources for a true enterprise perspective. Security settings can be used to limit users’ or roles’ access to information originating in specific external data sources or have views across data sources.
  • Further, Elements supports CADM as one of the available metamodels out of the box and CADM XML for interoperation with the DARS or other CADM XML-compliant data sources, such as modeling tools or AARMS. Analysis can be performed across workspaces defined by data source metamodels. For example, if data is imported from both System Architect and Rose, queries or impact analysis could be executed that incorporate Use Case and IDEF0 Operational Activity information. Transformations and migrations can also be performed from one workspace to another.
  • It should also be emphasized that as all these processes and steps are taking place, no matter which UI element is in use, a single integrated data set is being accessed managed.
  • Elements Repository Presentation

    1. 1. Enterprise Elements Redefining the Repository
    2. 2. A Synthesis of Technologies
    3. 3. The Elements Repository <ul><li>The Elements Repository is ideally suited for applications that support: </li></ul><ul><ul><li>A complex information model </li></ul></ul><ul><ul><li>Complex processes </li></ul></ul><ul><ul><li>Large data volumes </li></ul></ul><ul><ul><li>A large user population </li></ul></ul><ul><ul><li>Stringent security requirements </li></ul></ul><ul><li>Customers can acquire the Elements Repository technology and use it to accelerate the development of applications that have any of the above requirements </li></ul>
    4. 4. Elements Application Roadmap <ul><li>Enterprise Architecture Data Management and Analysis </li></ul><ul><li>Application Portfolio Management </li></ul><ul><li>Systems Engineering Data Management and Analysis </li></ul><ul><li>Project and Program Planning and Control </li></ul><ul><li>Acquisition Lifecycle Management </li></ul><ul><li>Regulatory Compliance Management </li></ul><ul><li>Text-Centric Knowledge Development and Management (e.g. contracts and other legal documents) </li></ul><ul><li>Complex Knowledge Management </li></ul><ul><li>Intellectual Property Management </li></ul><ul><li>Defect/Change Request Management </li></ul><ul><li>Many Others </li></ul>
    5. 5. Enterprise Elements Solutions <ul><li>Enterprise Elements will initially be offering three product variations that will address different vertical markets within the broad area of Enterprise Architecture. </li></ul><ul><ul><li>“ DoDAF Elements” will serve as a repository, analysis and full-lifecycle management tool for all Department of Defense Architecture Framework (DoDAF) information within an agency or on a major program </li></ul></ul><ul><ul><li>“ CPIC Elements” will support the Capital Planning and Investment Control (CPIC) process of the U.S. Federal Government. It will house all the data required for this process, manage the workflow related to this process, provide the appropriate scorecards and analytics, and automatically generate the key artifacts (such as business cases) </li></ul></ul><ul><ul><li>“ Portfolio Elements” will be a private-sector variation of the CPIC product. This will address the Application Portfolio Management needs of the US commercial market. </li></ul></ul>
    6. 6. Capability Overview <ul><li>100% Web-based </li></ul><ul><ul><li>HTML and Java Applet User Interface </li></ul></ul><ul><ul><li>Role-based Views </li></ul></ul><ul><ul><li>Web-Services Layer for Integration </li></ul></ul><ul><li>Configurable Information Model </li></ul><ul><ul><li>Logical Information Model (Metamodel) allows easy configuration for any solution </li></ul></ul><ul><ul><li>MOF- and other standard-based metamodels can be imported </li></ul></ul><ul><ul><li>Complete Web-based GUI for metamodel configuration </li></ul></ul><ul><li>Relational back-end, supporting scalability and direct query </li></ul><ul><ul><li>Innovative implementation leverages the full power of Oracle. Patent –pending design. </li></ul></ul><ul><li>Automatic Diagramming </li></ul><ul><ul><li>Queries create diagrams for: </li></ul></ul><ul><ul><ul><li>Relationship visualization </li></ul></ul></ul><ul><ul><ul><li>Significant modeling productivity gains </li></ul></ul></ul><ul><li>Link Matrix </li></ul><ul><ul><li>On-line matrix view allows fast association of data elements </li></ul></ul><ul><li>On-line Querying, Reporting & Metrics </li></ul><ul><ul><li>Inter-navigation between reports and data entry and collaboration views make data “actionable” </li></ul></ul><ul><ul><li>“ Digital Desktop” look & feel to give users summaries of data, progress, status, etc. </li></ul></ul><ul><li>Collaborative Workflow Support </li></ul><ul><ul><li>Polling & Discussion Threads </li></ul></ul><ul><ul><li>Customizable enforced process at any level within application (see next slide for detail) </li></ul></ul><ul><li>Advanced Access Control </li></ul><ul><ul><li>Project-, Data type-, Object- and Attribute-level security </li></ul></ul><ul><ul><li>Enforced by Oracle – cannot be circumvented by direct database access </li></ul></ul><ul><li>History </li></ul><ul><ul><li>Any change to objects or relationships is stored and any past version can be viewed for comparison or inspection </li></ul></ul><ul><ul><li>A full audit trail is maintained so any change can be traced back to its source </li></ul></ul>
    7. 7. Process Definition and Enforcement <ul><li>Elements allows the definition and enforcement of information lifecycle processes </li></ul><ul><ul><li>An example of a possible Change Proposal process is shown on the right. </li></ul></ul><ul><ul><li>A Test Plan process might be Defined, Approved, Executed, Passed, and Failed, or something similar. </li></ul></ul><ul><li>Rules can be applied to statuses and transitions to control access, editing and movement through the process </li></ul><ul><li>Process histories are captured allowing complete analysis of churn, cycles, overall status, and bottlenecks. </li></ul><ul><li>Processes can be applied at any level. For example: </li></ul><ul><ul><li>Investment </li></ul></ul><ul><ul><li>System </li></ul></ul><ul><ul><li>Project </li></ul></ul><ul><ul><li>Diagram </li></ul></ul><ul><ul><li>Task </li></ul></ul>Access control settings can be different for different states Rules can be applied to the transitions, allowing promotion only under defined conditions Triggers can be set for transitions, causing email alerts, starts of discussion threads, automatic assignment, etc.
    8. 8. Project Security & Perspective Enterprise/ Cross-Program Organization/ Program Department/ Project Individual/ Role etc. Repository security supports an enterprise view that has visibility into the entire repository and lower levels of scoped views that have data access limitations. This allows all information for large, hierarchically-managed projects to be stored in one repository as well as multiple unrelated projects.
    9. 9. Multiple On-line Metamodels Legacy Database(s) System Architect Rose EE-Managed
    10. 10. Multiple On-Line Metamodels Multiple concurrent metamodels can be managed in the same online environment, allowing integrated analysis. Transformation rules can be applied to allow data migration between different metamodels XMI and AP233 support are in development AARMS
    11. 11. Repository Discriminators <ul><li>No other repository product: </li></ul><ul><ul><li>Provides as customizable and comprehensive process control of repository data </li></ul></ul><ul><ul><li>Provides as extensive a set of collaboration features </li></ul></ul><ul><ul><li>Leverages the full power of a relational database, while still providing the customizability of proprietary solutions </li></ul></ul><ul><ul><li>Provides the flexibility of user interface to make the information actionable </li></ul></ul><ul><ul><li>Supports version and variant sequencing and analysis in one operational data store </li></ul></ul>
    12. 12. EA Solution Discriminators <ul><li>A True Repository Approach </li></ul><ul><ul><li>For environments in which the Enterprise Architecture data is extensive, complex and requires a multitude of users to input, manage and maintain the data, a repository approach is a requirement. </li></ul></ul><ul><ul><li>The relational repository provides the added benefit of allowing unparalleled flexibility in reporting, thereby allowing the architecture data to provide decision support, analysis and day-to-day value. </li></ul></ul><ul><li>Versus Modeling Tools Alone </li></ul><ul><ul><li>No modeling tool on the market today has the robust data management, workflow, collaboration, performance, data integrity and reporting capabilities of the Elements Repository. </li></ul></ul><ul><ul><li>100% Web-based </li></ul></ul><ul><ul><li>A great number of diagrams can be generated automatically based on true SQL queries </li></ul></ul>
    13. 13. Elements Inside <ul><li>The Elements Repository can also be used as a robust starting point for creating custom enterprise solutions that require some or all of the Elements core capabilities </li></ul><ul><li>A significant portion of your “development” work will simply consist of configuration, not programming. </li></ul><ul><li>You will be able to deliver core data management capabilities to your customer in record time. </li></ul><ul><li>You can focus on delivering extra value to your customer through interfaces, reporting, ETL, and specialized add-ons. </li></ul>
    14. 14. Data Call Example Flow eGrid eDocuments eDiagrams Reports Metrics Obtain Context Data Entry Validation Feedback Inbox eDiscuss Collaboration Progress Logging Forms Task Initiation Management Interaction Peer Interaction The Elements Repository utilizes workflow and a flexible user interface to efficiently support many complex and collaborative work-processes. A data call is a common process initiated within the Elements Framework. This diagram illustrates how different components of the application are used together to support work processes. [Animated – view as presentation]
    15. 15. Investment Review Example Flow eGrid eDocuments eDiagrams Reports Metrics Perform Gap Analysis Assess Correction Scope Progress Monitoring Feedback Inbox eDiscuss Perform Correction Progress Logging Forms Task Initiation Management Interaction Peer Interaction An investment review is a common process initiated within the Elements Framework. This process would be followed in preparation for a CPIC-compliant budget submission to insure that EA data properly supports a proposed expenditure This diagram illustrates how different components of the application are used together to support work processes. [Animated – view as presentation]
    16. 16. Elements Repository Home
    17. 17. Example Portal View Charts and Graphs for “Digital Desktop” View Report Section for organizing desktop-specific reports Configurable Desktops for Different User Types
    18. 18. Detail Report – In Portal Window Detail Report, run within a portal frame Content, layout and styles are all customizable All references to other elements automatically hyperlink to reports on those elements.
    19. 19. Detail Report – In Reporting Window Detail Reports can also be viewed in separate windows
    20. 20. Listing Report Listing Report Style Items in Listing Reports automatically hyperlink to Detail Reports
    21. 21. Elements Explorer The Elements Explorer allows easy navigation of reports, data, tasks and processes. It also allows portal desktop construction a using simple drag & drop mechanism Explorer-like tree view for navigation of the Elements virtual folder structure The virtual folder structure can contain summary reports, listing reports, individual elements and more folders. If a report is selected within the tree, the results are displayed within the Explorer.
    22. 22. Query-Driven Diagramming The eDiagram Manager automatically draws diagrams, based on relationships between items placed on the canvas Filters (queries) can be used to automatically select groups of items that are of interest to the user
    23. 23. Example Data-Driven OV-2 Any icon can be used for depicting different Element types on the diagram. Data can be entered diagrammatically or through forms or grids. Once it is in the Repository, diagrams can be automatically generated for any desired set of nodes based on queries.
    24. 24. Business Function Hierarchy Example Reference information (such as FEA Reference Models) is stored in the repository and can be displayed diagrammatically as needed
    25. 25. Link Matrix Feature Link attributes are directly editable. Easy association of related element types
    26. 26. Product Architecture Detail
    27. 27. Persistence Layer <ul><li>Persistence Layer </li></ul><ul><li>Configurable Schema </li></ul><ul><li>Complete Audit Trail </li></ul><ul><li>Baseline Management </li></ul><ul><li>Attribute-Level Security </li></ul><ul><li>Role-Based Security </li></ul><ul><li>Enterprise Scalability </li></ul>The information model supporting any vertical market can be configured. The ease of configuration and additional foundation features differentiate this from a standard database Persistence Process Presentation Common Modules Integration Common Functions
    28. 28. Process Layer <ul><li>Process Layer </li></ul><ul><li>Workflow </li></ul><ul><li>Collaboration </li></ul><ul><li>Discussion Threads </li></ul><ul><li>Polling </li></ul><ul><li>Email Notification </li></ul>The Process layer allows any number of parallel life-cycles to be defined for each type of information in the system. It also provides the infrastructure to support and enforce multi-user work processes surrounding information input, review and analysis. Persistence Process Presentation Common Modules Integration Common Functions
    29. 29. Presentation Layer <ul><li>Presentation Layer </li></ul><ul><li>Thin Client </li></ul><ul><li>Configurable Portal </li></ul><ul><li>Feature Plug-In Sockets </li></ul><ul><li>Role-Based Views </li></ul><ul><li>Metrics </li></ul>The Presentation Layer provides the actual work environment for users. The configurable nature of this implementation allows the many different user types who need access to a system such as this to have different tools, reports and views available to them, according to their needs. The Feature Plug-In capability means that customers, integrators and VARs can add additional application functionality using Java. Persistence Process Presentation Common Modules Integration Common Functions
    30. 30. Common Modules <ul><li>Common Modules </li></ul><ul><li>Element Editor </li></ul><ul><li>eDocument View </li></ul><ul><li>eGrid View </li></ul><ul><li>Scorecard View </li></ul><ul><li>Tree View </li></ul><ul><li>Project Explorer </li></ul><ul><li>Reporting Wizard </li></ul><ul><li>eDiagram View </li></ul><ul><li>Charting </li></ul><ul><li>Administration </li></ul>The Common Modules are the GUI elements that are provided with the product and can be configured in the portal or in pop-up windows. They cover the key modes of data input (eDocument View, eGrid View and Element Editor) basic reporting (Charting, Scorecard View and Reporting Wizard) and advanced tools for exploring dependencies, viewing data relationships and performing impact analysis (Tree View and eDiagram View). Persistence Process Presentation Common Modules Integration Common Functions
    31. 31. Integration Layer <ul><li>Integration Layer </li></ul><ul><li>Web Services Support </li></ul><ul><li>XMI Support </li></ul><ul><li>MOF Compatibility </li></ul><ul><li>Configurable Outbound Triggers </li></ul><ul><li>Direct ODBC/JDBC Access </li></ul><ul><li>Inbound & Outbound Navigation </li></ul><ul><li>High Transaction Volume </li></ul>The Integration Layer provides a standards-based tool set for sending and receiving data to and from other systems. Persistence Process Presentation Common Modules Integration Common Functions
    32. 32. Common Functions <ul><li>Common Functions </li></ul><ul><li>Enterprise-Wide Data Gathering </li></ul><ul><li>Role-Based Reporting </li></ul><ul><li>Role-Based Decision Support </li></ul><ul><li>Alternative/What-If Analysis </li></ul><ul><li>Migration Planning </li></ul><ul><li>Knowledge Navigation </li></ul>The Common Functions These useful capabilities are available based on the core platform, irrespective of the vertical to which it is applied. They will provide customers value if they buy only the core product or extend one of the vertical solutions Persistence Process Presentation Common Modules Integration Common Functions
    33. 33. Elements Physical Architecture