The ANSI-SPARC architecture is a conceptual framework for designing database management systems proposed in the late 1970s. It consists of three levels: external, conceptual, and internal, each serving different functions for user views, community views, and data storage respectively. This architecture provides advantages such as separation of concerns, data independence, and flexibility for robust database system design.

1. 
﷽

2. By:
Saeed-ul-Hussain
Mehfooz Ahmad
Waleed Ahmad
Hussnain Tahir

3. 
 The ANSI-SPARC Architecture is a conceptual
framework for designing and organizing database
management systems (DBMS).
 It was proposed by the Standards Planning and
Requirements Committee (SPARC) of the American
National Standard Institute in the late 1970s.
 ANSI-SPARC Architecture provides a clear and
organized way to understand the complexities of
database systems.
Introduction

4. 
Levels
External
Conceptual
Internal

5. 
The External Level represents the user view of
the database.
It defines how individual users or user groups
perceive data.
External schemas provide a customized view of
the data, hiding unnecessary details and
complexities
Changes to external schemas do not affect other
users or the overall database structure.
External level

6. 
The Conceptual Level describes the
community view of the database.
It defines the structure, constraints, and
relationships of the data stored in the
database.
Changes to the conceptual schema impact the
entire database and all external schemas.
Conceptual level

7. 
 The internal level deals with the physical storage
and organization of data.
 It defines how data is stored, indexed, and accessed
within the system.
 Changes to the internal schema do not affect external
views but may impact performance.
Internal level

8. 
Separation of concerns
Data independence
Flexibility
Advantages

9. 
 The ANSI-SPARC Architecture provides a solid
foundation for designing robust and flexible
database systems.
 By understanding the three levels and their
interactions, database designers can create efficient
and maintainable solutions.
Conclusion