|
|
| Line 1: |
Line 1: |
| − | Adempiere Enterprise Solution Conceptual Glossary Is A Unified Adempiere Language (UAL):
| + | #REDIRECT [[Glossary]] |
| − | Lets Start Learning Our New Language :+)
| + | |
| − | (Soheil Qanbari)<br>
| + | |
| − | '''Adempiere Architecture Solution UAL'''
| + | |
| − | Architecture is King... ;)
| + | |
| − | | + | |
| − | '''A'''
| + | |
| − | Application Dictionary (AD) :
| + | |
| − | AD is the most important developer tool given by Adempiere.Like Elements, Tables,
| + | |
| − | Columns, References, Windows, Tabs, Fields, etc.
| + | |
| − | Architecture:
| + | |
| − | The fundamental organization of a system, embodied in its components, their relationships
| + | |
| − | to each other and the environment, and the principles governing its design and evolution.
| + | |
| − | Architecture has two meanings depending upon its contextual usage:
| + | |
| − | 1. A formal description of a system, or a detailed plan of the system at component
| + | |
| − | level to guide its implementation
| + | |
| − | 2. The structure of components, their inter-relationships, and the principles and
| + | |
| − | guidelines governing their design and evolution over time.
| + | |
| − | Architecture Description:
| + | |
| − | An architecture description is a formal description of an information system, organized in
| + | |
| − | a way that supports reasoning about the structural properties of the system. It defines
| + | |
| − | the components or building blocks that make up the overall information system, and
| + | |
| − | provides a plan from which products can be procured, and systems developed, that will work
| + | |
| − | together to implement the overall system. It thus enables you to manage your overall IT
| + | |
| − | investment in a way that meets the needs of your business.
| + | |
| − | Architecture Framework:
| + | |
| − | An architecture framework is a tool which can be used for developing a broad range of
| + | |
| − | different architectures. It should describe a method for designing an information system
| + | |
| − | in terms of a set of building blocks, and for showing how the building blocks fit
| + | |
| − | together. It should contain a set of tools and provide a common vocabulary. It should also
| + | |
| − | include a list of recommended standards and compliant products that can be used to
| + | |
| − | implement the building blocks.
| + | |
| − | | + | |
| − | '''C'''
| + | |
| − | Callout :
| + | |
| − | A callout can be looked at as an extension at the field level.
| + | |
| − | | + | |
| − | '''D'''
| + | |
| − | Data Dictionary:
| + | |
| − | A data dictionary is a set of metadata that contains definitions and representations of
| + | |
| − | data elements. Within the context of a DBMS, a data dictionary is a read-only set of
| + | |
| − | tables and views. The data dictionary is database in its own dictionary. Amongst other
| + | |
| − | things, a data dictionary holds the following information: <br>
| + | |
| − | * Precise definition of data elements
| + | |
| − | * Usernames, roles and privileges
| + | |
| − | * Schema objects
| + | |
| − | * Integrity constraints
| + | |
| − | * Stored procedures and triggers
| + | |
| − | * General database structure
| + | |
| − | * Space allocations
| + | |
| − | | + | |
| − | '''E'''
| + | |
| − | Enterprise:
| + | |
| − | An Enterprise in this context " Enterprise Architecture" is any collection of
| + | |
| − | organizations that has a common set of goals and/or a single bottom line. In that sense,
| + | |
| − | an enterprise can be a government agency, a whole corporation, a division of a
| + | |
| − | corporation, a single department, or a chain of geographically distant organizations
| + | |
| − | linked together by common ownership.
| + | |
| − | Enterprise Modeling:
| + | |
| − | Enterprise modelling is the process of improving the enterprise performance through the
| + | |
| − | creation of enterprise models. This includes the modelling of both business processes and
| + | |
| − | IT.Also An enterprise model is a computational representation of the structure,
| + | |
| − | activities, processes, information, resources, people, behavior, goals, and constraints
| + | |
| − | of a business, government, or other enterprises.
| + | |
| − | | + | |
| − | '''M'''
| + | |
| − | Meta Data:
| + | |
| − | Metadata is structured, encoded data that describe characteristics of information-bearing
| + | |
| − | entities to aid in the identification, discovery, assessment, and management of the
| + | |
| − | described entities.Also Metadata is a set of optional structured descriptions that are
| + | |
| − | publicly available to explicitly assist in locating objects.
| + | |
| − | | + | |
| − | Module :
| + | |
| − | A New Module in Adempiere is * Table-Column structure * Input handling and validation
| + | |
| − | rules * Document Type & Print Format * Define Default Accounts * Workflow Process *
| + | |
| − | Callout definition and process-button definition consolidated via Report & Process *
| + | |
| − | Final Consolidation in Windows under the Menu tree
| + | |
| − | | + | |
| − | '''R'''
| + | |
| − | Routing:
| + | |
| − | A routing is a description of which operations (process steps) have to be carried out and
| + | |
| − | in which order to produce a material (product).
| + | |
| − | | + | |
| − | '''S'''
| + | |
| − | SQL Procedure :
| + | |
| − | An SQL Procedure can be looked at as an extension at the process level.
| + | |
| − | | + | |
| − | '''T'''
| + | |
| − | 2Pack :
| + | |
| − | It's related with Translating Dictionary Modifications from one Adempiere system to
| + | |
| − | another.
| + | |
| − | | + | |
| − | '''X'''
| + | |
| − | XML2AD :
| + | |
| − | It imports several XML files into the database in order to modify the Application
| + | |
| − | Dictionary of ADempiere.
| + | |
| − | | + | |
| − | [[Category:FAQs]] | + | |
