Scribd
Upload
17 views27 pages

CSE4005

Uploaded by

sonalchandrarathna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views27 pages

CSE4005

Uploaded by

sonalchandrarathna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 27

01.

Task 01 – Data models

A data model is a conceptual framework that shows the data structures required for a given information
domain. It describes the structure and relationships between data items, making it easier to handle data in
an organized manner for activities like creation, modification, and retrieval. Data models serve as a guide
for database architecture, guaranteeing the accuracy, consistency, and effectiveness of data management
procedures by outlining linkages and hierarchies. These models, which provide an organized method for
storing and retrieving data, are essential for directing the creation of database systems. Whatever the
model type—relational, hierarchical, network, or object-oriented—each has advantages specific to the
needs and intricacies of the data domain. In the end, data models are crucial in determining how databases
are built, which in turn affects how reliable and successful data-driven systems and applications are.
1) Hierarchical Data Model
 Arranges data into a single root tree-like structure, with numerous child nodes for each parent
node.
 A hierarchical representation of the relationships between data pieces is used.
 Complicated navigation, redundant data, and challenges in displaying many-to-many
relationships are among the drawbacks.

2) Network Data Model


 Allows each child node to have several parent nodes, extending the hierarchical paradigm and
creating a network structure.
 Permits more adaptable connections and improved complicated data relationship representation.
 Pointers and linkages between nodes make it still difficult to navigate and manage.

4) Object-Oriented Data Model


 incorporates ideas from object-oriented programming, such as classes, objects, and inheritance, to
expand the relational model.
 enables the depiction of actual things as having properties and functions.
 better supports relationships and sophisticated data structures.
 However, because of its complexity and lack of standards, adoption has been restricted.

5) Document Data Model


 instead of using hard tables to store data, it uses flexible, semi-structured documents (like JSON
and XML).
 Complex data can be represented more naturally in documents by using arrays and hierarchical
data structures.
 extensively utilized in NoSQL databases and web development to manage unstructured or
dynamically changing data.
 Scalability and agility are provided, but certain relational aspects, like as ACID transactions, may
be lost.

Why are older data models being replaced by new ones?

Performance

Performance issues with huge datasets or complicated relationships might arise with traditional relational
databases. In other usage circumstances, newer models—like graph databases—can perform better
because they are better suited for navigating complex relationships.

Complexity

The design, navigation, and maintenance of older data models, such as network and hierarchical models,
can be challenging. Relational databases greatly reduced the complexity of data management; but, more
recent models, such as document and graph databases, further simplify data management by offering
more user-friendly data structures.

Real-World Representation

Modern application development processes and objectives are better met by object-oriented and
document data models, which provide a more realistic representation of real-world entities and
relationships.
2 Bottom-up approach
This starts with the subtleties and climbs to the general. This is finished by first recognizing the
information components (things) and gathering them in informational collections afterwards. This
strategy acknowledges the properties and afterwards bunches them to frame substances (Database
Management, 2010)
Task 06 Travel Classics SQL Database
Task 07 - Travel Classics SQL Queries

1) List of Travelers of a particular location:

2) Sum of transactions received within a given duration of a particular hotel:

3) List of hotels and their room availability


Conclusion

Functionality, correctness, and dependability have all been extensively evaluated in the Travel Classics
database and related SQL queries. The test plan addressed a number of topics, such as error management,
query performance, and data integrity.

All things considered, the database schema follows normalization guidelines, guaranteeing effective data
retrieval and storage. The SQL queries are well-organized and offer the features that the application
needs.

During testing, all test cases passed successfully, demonstrating that the system meets the specified
requirements. Any issues identified were promptly addressed, ensuring a robust and dependable database
system.

In conclusion, the Travel Classics database, along with its SQL queries, is ready for deployment, offering
a solid foundation for building travel management applications. Ongoing monitoring and maintenance
will be essential to uphold the system's performance and reliability over time.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy