Enterprise Elements will initially be offering three product variations that will address different vertical markets within the broad area of Enterprise Architecture.
“ 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
“ 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)
“ 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.
Elements allows the definition and enforcement of information lifecycle processes
An example of a possible Change Proposal process is shown on the right.
A Test Plan process might be Defined, Approved, Executed, Passed, and Failed, or something similar.
Rules can be applied to statuses and transitions to control access, editing and movement through the process
Process histories are captured allowing complete analysis of churn, cycles, overall status, and bottlenecks.
Processes can be applied at any level. For example:
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.
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.
Multiple On-line Metamodels Legacy Database(s) System Architect Rose EE-Managed
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
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.
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.
Versus Modeling Tools Alone
No modeling tool on the market today has the robust data management, workflow, collaboration, performance, data integrity and reporting capabilities of the Elements Repository.
A great number of diagrams can be generated automatically based on true SQL queries
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
A significant portion of your “development” work will simply consist of configuration, not programming.
You will be able to deliver core data management capabilities to your customer in record time.
You can focus on delivering extra value to your customer through interfaces, reporting, ETL, and specialized add-ons.
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]
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]
Example Portal View Charts and Graphs for “Digital Desktop” View Report Section for organizing desktop-specific reports Configurable Desktops for Different User Types
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.
Detail Report – In Reporting Window Detail Reports can also be viewed in separate windows
Listing Report Listing Report Style Items in Listing Reports automatically hyperlink to Detail Reports
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.
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
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.
Business Function Hierarchy Example Reference information (such as FEA Reference Models) is stored in the repository and can be displayed diagrammatically as needed
Link Matrix Feature Link attributes are directly editable. Easy association of related element types
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
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
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
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
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