Composition is the strong binding between the data. It means that if we destroy one part of data, where it automatically deletes all other part of data.
Composite Business Data are inevitable in all Business, where the most of composite data are in the transaction (i.e. day to day operations, like billing, depositing money to the bank and etc) of the business.
The most popular composite data generation or creation example is invoicing or billing, where header details are stored in a separate table and line details or item details or stored in a separate table.
But as per the software developer prospects, the two data tables have separate properties and even very clear about uniqueness of the two data tables.
As per the software user or data entry operator prospects where there wasn’t any different world. Software user is vice versa thinking of the developer, where he can’t see any kind of separation, because most of the invoice and bills are in single printed and bound sheet with filling data in pen, in his previous technology. And if he knew all these things then he would really thing about “The God must be crazy”.
The software project manager should govern all these three aspects i.e. the end user or the bench marker of the application, and his software business back bone or the software business driver, software developer.
The following there worlds are marking the business composite data or invoice or billing application
1. Data entry window
2. Header items (i.e. Invoice or bill number date and customer details) data table
3. Line items (i.e. Invoice or bill’s products details, unit price, quantity, total amount) data table
Now the developer makes connection between his header table world, line table or item table world by the F.K and P.K concepts.
A short form of P.K, in development world, is primary key. This is a unique value in the table i.e. if the value 8678 is in the primary key value means where it never repeats again.
Instead of using the entire header table row value, we can use only the primary key value i.e. like a postal code. By using the postal code we can tell, district, state and city.
Like a human being, every data has its own life cycle and fate.
1. Initialization
2. Propagation
3. Termination
Initialization is the birth of data, propagation is the modification of data or copy of data, and termination is the deletion of the data.
Here, the fate of data likes a human being where the data may be gone by accidental data base crash, or system crash, or the data may be copied into a platinum disk.
Composite Business Data are inevitable in all Business, where the most of composite data are in the transaction (i.e. day to day operations, like billing, depositing money to the bank and etc) of the business.
The most popular composite data generation or creation example is invoicing or billing, where header details are stored in a separate table and line details or item details or stored in a separate table.
But as per the software developer prospects, the two data tables have separate properties and even very clear about uniqueness of the two data tables.
As per the software user or data entry operator prospects where there wasn’t any different world. Software user is vice versa thinking of the developer, where he can’t see any kind of separation, because most of the invoice and bills are in single printed and bound sheet with filling data in pen, in his previous technology. And if he knew all these things then he would really thing about “The God must be crazy”.
The software project manager should govern all these three aspects i.e. the end user or the bench marker of the application, and his software business back bone or the software business driver, software developer.
The following there worlds are marking the business composite data or invoice or billing application
1. Data entry window
2. Header items (i.e. Invoice or bill number date and customer details) data table
3. Line items (i.e. Invoice or bill’s products details, unit price, quantity, total amount) data table
Now the developer makes connection between his header table world, line table or item table world by the F.K and P.K concepts.
A short form of P.K, in development world, is primary key. This is a unique value in the table i.e. if the value 8678 is in the primary key value means where it never repeats again.
Instead of using the entire header table row value, we can use only the primary key value i.e. like a postal code. By using the postal code we can tell, district, state and city.
Like a human being, every data has its own life cycle and fate.
1. Initialization
2. Propagation
3. Termination
Initialization is the birth of data, propagation is the modification of data or copy of data, and termination is the deletion of the data.
Here, the fate of data likes a human being where the data may be gone by accidental data base crash, or system crash, or the data may be copied into a platinum disk.
