A cohesive series of data which is a part of an application.
Description
A data component is always bound to the application of which it is a part. This means that its underlying structure is a description of how data has been realized in that application. Therefore, it is important to always mark the affiliation to the application in the name of the data component so that it does not risk being reused as part of another application.
A simple rule of thumb is that there is a data component for each application module.
Example
- Order data (Sales System x)
- Customer data (CRM System Y)
- Accounts Receivable Data (Financial System Z)
Links
View types
Application Context Description (ACD)
Application Context Model (ACM)
Application Flow Description 2 (AFD-2)