• slider2

    Generalized Enterprise Function Framework  (GEFF)

  • slide1

    Enterprise Architecture 3.0 (EA3.0) - the third wave in Enterprise Architecture approaches

  • slider3

    A3 KAM - Triple A(Architectural, Actionable and  Augmented) Knowledge Assets Management

  • slider4

    ABODE™ business transformation methodology  founded on EA3.0

Lifecycle Products & Services

These are supportive for the Lifecycle Management area, although they might be related to the Business, the Architecture, or the Transformation area. Tools used here are integrated tools for connecting the ABODE™ meta-database with fCMDB or federated Configuration Management Data Bases, Functional, Application and Technical Management, etc., to manage the lifecycle of applications and technical components.

 

The following tools and Business Solutions support Lifecycle management of Business and Information Products:

Product Service Lifecycle Management
Application Rationalization Analysis Based on several business and technological criteria applications are evaluated in groups of application supporting business areas through Quick Survey or In-Depth Survey that can be made organization-specific with the help of the SWB. When the standard approach is followed the SDW approach is not possible and a simpler evaluation of the results is offered. Next, optimizing the business and technological value of applications is based on the different scenarios.
Application Lifecycle Management

Pages to be developed per Tool including PrintScreens (if available)

a simple Scan based on the SWB (SurveyWork Bench) with a broad view on the research area
a complex Scan based on the SWB (Survey Work Bench) with a deeper view on details of the research area
Survey Work Bench with which data of a research area is collected in the form of Surveys
Decision Support System for What-If analysis on the results of surveys
these are often used Business Apps applicable for many types of organizations, like inspection Apps for quality of work control in diverse types of business like facility management, environmental checking, asset inspection, etc.
these are generic Business Processes that can be used for many types of applications, like Order-to-Delivery, Delivery-to-Pay, etc.
Business Solutions are larger and more complex collections of business areas each with several processes to fulfill parts or a larger capability. For example the processes described in ITIL, BiSL, ALM, TOGAF, etc. So typically IT4IT solutions for larger organizations. Because the fit of most of the COTS delivered solutions and the requirements of the organization form many gaps, it is almost all times cheaper, and faster to adjust these solutions based on the ABODE™ tools.
Business Models are integrated Business Solutions that form a consistent and coherent functionality like a complete set of IT4IT solutions, business models that support smaller organizations, etc.
are necessary when administrative application systems or business Apps need integration with tools like DMS, CMS, CRM, General Ledger systems, VOIP, PBX, Exchange, etc. Enterprise Architects Software Development can develop these Technical Interfaces based on the flexible architecture of EA3.0™. With our tools Enterprise Architects develops adapters, if not already at hand, to enable any connection between business Apps, etc. and third-party tools.
which supports three Knowledge Asset Management approaches, namely Architecture, Actionable, and Augmented Knowledge. With this tool the user can get access and maintain augmented knowledge described interms of documents, methodologies, techniques, tools, models, movies, etc. The other types of Knowledge Assets can be accessed with the tool, but are maintained during Architecture, Design, and Lifecycle processes.
Impact of Change Analysis
Business Case Generation based on RTF Template
Modeling the Proposition Model
Business Interaction Manager with which the Supply Demand chain interactions, derived from the PSM/PSO are managed
Generating the specific organization’s BFM based on the GEFF™, the Proposition Model and the Product/Service Catalogue
Generating the maintenance Apps for the Product/Service Catalogue
Manage the Business Product Lifecycle
Integrate Architecture and Configuration Metamodels
Manage the Information Product Lifecycle
Architecture Modeling
Integrated Architecture Management tool
Support pattern recognition for Product/Service to Business Function
Value Management tool with which the Value Vectors that the organization wants to distinguish can be defined
Defining the Value Vectors per Business Function
Business Function Modeler
Conceptual Object Modeler based on the Proposition Model
Design-to-Architecture
Generating a PSA based on the PSA template (RTF)
Generating a PSA based on the PEA template (RTF)
Support pattern recognition for Product/Service to Business Function
Direct Model Executions
Business App Store
Defining and selecting the Environment in where the transformation will take place; the number of environments and their types (Design, Testing, Acceptance, Production, etc.) and are many
Defining or adapting the actionable and augmented knowledge functions of the Business Functions
Defining Enterprise Objects for the Conceptual Object Model, Business Objects for the Logical Object Model, map each Business Object as a specialization of one Enterprise Object, and define Data Objects or Data APIs for the Data Object Model
Function Development Kit in which the business side of Business Functions are integrated in which way they become executable
User Interaction Modeling with which the User Interaction is modeled by means of Presentation Services
Business RuleSet Management with which the formal business logic is expressed in an executable natural language Business Rule Language
Integrated Service Engineering tool with which Information, Presentation, and Data Services can be designed (Messages), and defined (Services)
Used to model Business Processes by chaining together enriched Business Functions in which way the Business Process can be executed; Business Processes can formally be defined as straight-through processes (BPMN2) or case-based processes (CMMN1)
Technical Interface Modeler and Management
Product Service Lifecycle Management
Application Rationalization Analysis Based on several business and technological criteria applications are evaluated in groups of application supporting business areas through Quick Survey or  In-Depth Survey that can be made organization-specific with the help of the SWB. When the standard approach is followed the SDW approach is not possible and a simpler evaluation of the results is offered. Next, optimizing the business and technological value of applications is based on the different scenarios.
Application Lifecycle Management

The Business Function Modeler is used to define, select, and enrich Business Functions and store them in the Business Function Model for later or direct use. Business functions are enriched with Presentation Services, Information Services, and Business RuleSet by the Function Integrator. With these three components an App or Application is completely described.

 

Business Rules can be defined and maintained with the Rule Management tool. With the Object Modeler tool, the models for the three object layers are described: the Conceptual Layer with Enterprise Objects, the Logical Layer with Business Objects, and the Physical Layer with Data Objects.

 

The User Interaction Modeling tool describes how Business Objects can be used for interaction with users via so-called Presentation Objects. Because the User Interaction can be very complex, with components like widgets, tabs, buttons, colors, backgrounds, etc., the User Interaction tool is very versatile.

 

With the Integrated Service Engineering tool the data elements of the mentioned Objects can be “mapped” together and thus create Presentation Services (Presentation versus Business Objects, Information Services (Business Objects versus the integration bus), respectively Data Services (Integration bus versus Data Services or APIs for COTS packages) can be generated.

 

When a business function has been enriched with the function integrator tool, the function can be immediately executed (DME or Direct Model Execution) and thus functionally tested. When everything is functioned correctly to the requirements of the product owner, the Enriched Business Function is stored in the Business Function Model.

 

As Business Functions are described activities serving a Capability, and enriched Business Functions are executable activities, the enriched Business Functions can be used in Business Processes. These then can be modeled with the Process Modeler by selecting the enriched Business Functions and “chain them together” as beads in a process flow. Because they are enriched the Business Process can be executed (DME) and functionally tested immediately.

 

Business Functions can make use of technical interfaces to make use of generic or specific amenities or COTS products. In this way Document Management Systems, Content Management Systems, Customer Relationship Management, Archiving Systems, special ESB connections like Input and Output Management including Message Control, etc. can be used in business processes by activities that need these amenities.

 

A special area is formed by Application Rationalization. Enterprise Architects offers Application Rationalization Analysis services, in which the business and technical value of application systems is evaluated and results in scenarios to improve these values. For this a special tools were developed.

 

The different scenarios can be supported by tools for data cleansing, data migration, business functionality development, and functionality & data containment.