Lakhasly

The system is designed to ensure both program and data independence, enabling it to serve diverse user groups simultaneously.Multiple User Views: By offering customized interfaces for customers, employees, and managers, the system addresses diverse functional requirements without overlapping responsibilities, enhancing its overall adaptability and efficiency.External Schema (User Views)
External schemas cater to the differing needs of various user groups by providing tailored perspectives on the same data.For instance, information such as passenger details, flight schedules, and booking records could be maintained in tables, indexed formats, or specialized storage solutions to optimize data retrieval and utilization.The airline's IT team can reorganize storage configurations--such as modifying indexes for faster searches--without affecting the way booking agents, customers, or managers interact with the system.Managers interact primarily with composite reports such as booking trends or revenue analytics.Each group's interface remains unaffected by modifications to internal or conceptual schemas, ensuring usability and transparency.Conceptual Schema (Logical Level)
At this layer, a unified logical depiction of the entire database is presented.2.

The system is designed to ensure both program and data independence, enabling it to serve diverse user groups simultaneously. Here's an overview of how the schema hierarchy functions:

Internal Schema (Storage Level)

This level defines how data is physically stored within the system. For instance, information such as passenger details, flight schedules, and booking records could be maintained in tables, indexed formats, or specialized storage solutions to optimize data retrieval and utilization. The airline’s IT team can reorganize storage configurations—such as modifying indexes for faster searches—without affecting the way booking agents, customers, or managers interact with the system. This separation maintains flexibility in adapting to performance needs while safeguarding user experience.

Conceptual Schema (Logical Level)

At this layer, a unified logical depiction of the entire database is presented. It encompasses core entities like flights, bookings, travelers, payments, and their interconnections. This schema ensures consistency and shields users from changes in underlying storage mechanisms. Even if the airline decides, for example, to introduce loyalty program points or restructure its internal data organization, the logical architecture remains steady. This abstraction allows data and functionality to evolve while preserving the overall integrity of relationships between entities.

External Schema (User Views)

External schemas cater to the differing needs of various user groups by providing tailored perspectives on the same data. Customers browsing online see views focused on available seats, prices, and booking confirmations. Airline staff at service desks or call centers access passenger info, payment statuses, and flight updates. Managers interact primarily with composite reports such as booking trends or revenue analytics. Each group’s interface remains unaffected by modifications to internal or conceptual schemas, ensuring usability and transparency.

Key Benefits: Independence and Multi-user Support

1. Data Independence: The system provides resilience against changes in how data is stored (internal schema) or structured logically (conceptual schema). External applications seamlessly function regardless of these backend updates.


2. Multiple User Views: By offering customized interfaces for customers, employees, and managers, the system addresses diverse functional requirements without overlapping responsibilities, enhancing its overall adaptability and efficiency.