Hicks_Assign4
docx
keyboard_arrow_up
School
American Military University *
*We aren’t endorsed by this school
Course
222
Subject
Information Systems
Date
Apr 3, 2024
Type
docx
Pages
5
Uploaded by CaptainKoala4253
Crystal Hicks INFO222
March 31, 2024
Database Name: CHMedicalRecords
Patient
Fields:
1. PatientID (Unique Identifier): 2. Last Name: 3. First Name: 4. Date of Birth: 5. Gender:
6. Address:
7. Phone Number: 8. Email: Doctor
Fields:
1. PTAN (Unique Identifier): 2. Last Name: 3. First Name: 4. Specialty: 5. Phone Number: 6. Email: Database Design Steps & Values:
A)
Identification of Requirements
: Understand the purpose of the database, gather requirements from stakeholders, and define the scope of the project. Understanding requirements ensures the database meets the needs of its users, avoiding unnecessary features or missing critical functionalities. Clear requirements also facilitate alignment of expectations among stakeholders.
B)
Conceptual Design:
Create a high-level conceptual model depicting entities, attributes, and relationships without focusing on implementation details. Creating a conceptual design helps stakeholders visualize the structure and relationships of the database, facilitating communication and alignment of expectations, thus ensuring the database accurately represents the real-world domain.
C)
Logical Design:
Translate the conceptual model into a logical schema with tables, columns, primary keys, foreign keys, and normalization to ensure data
integrity. Logical design ensures the database is organized efficiently, reducing redundancy and improving data integrity and consistency, thus laying the foundation for the physical implementation.
D)
Physical Design:
Implementing the logical schema into a specific database management system, considering performance, storage, and indexing. By optimizing the database for performance and scalability, this step ensures that the system meets performance expectations and can handle the expected workload effectively.
E)
Testing and Evaluation:
Test the database to ensure it meets requirements,
functionality is correct, and performance is acceptable. Testing and evaluation ensure the database functions correctly and meets performance expectations before deployment, reducing the risk of errors and downtime by identifying and rectifying any issues before deployment, ensuring the reliability and usability of the database.
F)
Implementation and Maintenance
: Deploying the database into the production environment, providing necessary training, and maintaining it over time, incorporating updates and optimizations. This ensures the database remains operational and effective over time, adapting to changing requirements and technologies, thus supporting the organization's goals effectively.
Bottom-Up vs. Top-Down Design
In a bottom-up design approach, individual components or modules are developed independently and later integrated into a cohesive system. This method focuses on building from specific functionalities to a comprehensive solution. Conversely, the top-down approach begins with a broad overview of the system and progressively breaks it down into smaller components. The illustration below depicts these approaches:
If you're dealing with a straightforward database, going top-down is the way to go. Basically, you start with the big picture, sketching out the main components like what info you need and how it all fits together. It's like drawing an outline before filling in the details. This approach keeps things clear and flexible, making it easier to adjust as you go along. Plus, it's efficient since you're not getting lost in the nitty-
gritty right from the get-go. So, for a simple setup, top-down keeps it simple and manageable.
Multiplicity Relationships Examples
:
1. One-to-One Relationship:
Example: A person has exactly one passport, and a passport belongs to only one person.
2. One-to-Many Relationship:
Example: A department has many employees, but each employee belongs to only one department.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
3. Many-to-Many Relationship:
Example: Students can enroll in multiple courses, and each course can have many students.
References:
1. Ozsu, M. T., & Valduriez, P. (2011). Principles of distributed database systems (3rd
ed.). Springer. 2. Elmasri, R., & Navathe, S. B. (2016). Fundamentals of database systems (7th ed.).
Pearson.
3. Connolly, T. M., & Begg, C. E. (2014). Database systems: A practical approach to design, implementation, and management (6th ed.). Pearson.
4. Coronel, C., Morris, S., & Rob, P. (2016). Database systems: Design, implementation, and management (12th ed.). Cengage Learning.
5. Hoffer, J. A., Venkataraman, R., & Topi, H. (2017). Modern database management (12th ed.). Pearson.