Business object
Business object (English Business Object ) is a term used in object-oriented software development. Business objects are used to represent objects in the business world within information systems. Business objects contain not only data (see below definition to entities ), but also processing logic.
Example
Examples of business objects are customers, products and orders an application system. If the order system, for example, 1,000 customers, 2,000 products and 3,000 contracts managed, then it contains a total of 6,000 business objects. An example of the processing logic from business objects, see below example.
Task
Business objects form a bridge between
Benefits
If you build an information system along the structures of its managed business objects, it is easier for users and software developers to understand. Due to the high correlation between perceived reality and the structure of the software user take such a system as "simple" true and software developers can be found faster in its development and maintenance cope. Therefore, accompanied by fewer errors, there are fewer misunderstandings and by the more rapid development also brings down costs.
Implementation
In object-oriented programming business objects are implemented directly as object classes of the language. In older, non- object-oriented programming languages such as COBOL or C, you can store objects only indirectly, implement, for example, using the CORBA OMG standards.
In contrast to business objects technical objects represent the other or the rest of the objects of information systems. Technical objects are eg the windows, controls, and database tables that you need to view and save business objects.
Method
Software developers should first take care to describe the business objects of their systems properly. They do this by creating an object model. An object model accomplishes the same task as a technical drawing for example, a machine or a house.
Only when the object model is correct, should software developers finish the software system by making it complementary to the technical objects.
An object model is correct if it meets all the requirements. The object model fulfills a requirement if it meets all acceptance criteria. And it satisfies an acceptance criterion if the measurement is described by the acceptance criterion leads within the object model to the expected result.
Generalization
A generalization of the term " business object " are domain objects. The word " domain " refers to the case of use of the software system, such as the control of a washing machine. In this example, it would be inappropriate, the motor, the temperature sensor and the other key for the software components of the washing machine to be described as " business objects ".
Demarcation to entities
Business objects are a resultant approximately 1993 further development of entities. They differ from the latter in that they are not restricted to the database, but also processing logic (methods) included. Often it is seen as beneficial, all the processing logic of IT systems subordinate to the business objects.
Example
- Situation: A job with Article 2 rows. In the first item line are 5 computer monitors and in the second 10 computers. A monitor costs 100 EUR and a computer 500 EUR. This situation contains 5 business objects: an order and each 2 order lines and products.
- Action: The job is asked about his contract value.
- Expected result: 5.500 EUR.
- Expected expiry: The order asks the 1st line: what is your price per line?
- The first line asks the article " Monitor": what is your price?
- The monitor replies: 100 EUR
- The first line is calculated ( quantity times price) at a price: 5 monitors of 100 EUR = 500 EUR
- This line price (500 EUR ), it returns to the job.
- The order asks the 2nd line that calculates their line price in the same manner as the first line
- The second line gives their line price (10 computer of 500 EUR =) 5000 EUR back
- The order adds the two line prices and outputs the sum (500 plus 5,000 =) back 5500 EUR