0%
Exam Sidemann Logo Light Mode

DATABASE ANALYSIS & DESIGN

Learning Outcome 1: Understand database concepts and their importance.

Listen to an Overview of Database Concepts

LEARNING OUTCOME 1

Topic 1: What is a Database?

Imagine you have a big notebook where you write down all important information. For example, if you are a class monitor, you might write down:

  • All student names
  • Their ages
  • Their contact numbers
  • Maybe their grades for tests

This notebook, if it's very well organized, is like a simple database.

Official Definition (Simple Version):

A database is like a super organized electronic filing cabinet or a very neat collection of information stored on a computer.

[Database yakafanana nekabhodhi kemafaira rakarongeka chaizvo riri pakombiyuta. Inzvimbo yatinochengetera mashoko akawanda akanyatsorongwa.]

This information is usually structured, meaning it's arranged in a neat way, like in lists or tables.

[Mashoko aya anenge akarongeka, kureva kuti akamira zvakanaka semalista kana matafura.]

The Helper: Database Management System (DBMS)

Now, to use this electronic filing cabinet (the database), we need a special helper. This helper is a software program called a Database Management System (DBMS).

[Kuti tishandise kabhodhi aka kemafaira kepakombiyuta, tinoda mubatsiri. Mubatsiri uyu ipurogiramu yepakombiyuta inonzi Database Management System (DBMS).]

Think of the DBMS as the librarian for your digital filing cabinet. The DBMS helps you:

  • Create new space for information. [Kugadzira nzvimbo yemashoko matsva.]
  • Retrieve (find) information you need. [Kutsvaga mashoko aunoda.]
  • Update (change) information if it's old or wrong. [Kuchinja mashoko kana akasakara kana asiriwo.]
  • Manipulate (work with) the information in different ways. [Kushandisa mashoko nenzira dzakasiyana.]

Example:

Imagine your school uses a computer system to keep track of all students.

  • The database is where all student names, classes, parent contacts, and exam results are stored.
  • The DBMS is the software (like a school admin program) that the school secretary uses to add new students, find a student's contact details, or enter exam marks.

Key Database Concepts (Zvinhu Zvakakosha Kuziva NezveDatabase)

Let's learn some important words used with databases:

1. Data:

This is the raw, basic stuff. Individual facts and figures before they are fully organized or understood.

[Data ndizvo zvinhu zvidiki-diki zvemashoko, zvisati zvanyatso rongwa kana kunzwisiswa.]

Examples for a Zimbabwean student:

  • A name: "Tendai"
  • An age: "14"
  • A subject: "Shona"
  • A mark: "75%"
  • A village name: "Murewa"
  • Price of sadza at the tuckshop: "$1"

2. Information:

When data is organized and given meaning, it becomes information. It’s data that now tells us something useful.

[Kana data rarongeka rikapiwa zvarinoreva, rinobva raita information. Mashoko aya anenge ava kutitaurira chinhu chinobatsira.]

Example:

  • Data: "Tendai", "14", "Form 2", "75%", "Shona"
  • Information: "Tendai is a 14-year-old student in Form 2 who scored 75% in Shona." This is now useful for the teacher or parents.

3. Metadata:

This is "data about data." It describes your data.

[Metadata mashoko anotsanangura mamwe mashoko (data). Anotirondedzera kuti data rakamira sei.]

Think of it like the label on a file in a filing cabinet. The label tells you what kind of information is inside the file (e.g., "Student Reports") without you having to open and read everything.

Example: For the data "Tendai", metadata might say "This is a student's first name" or "Text, maximum 20 letters".

4. Data Hierarchy: (Matanho ekurongwa kweData)

Data in a database is usually organized in levels, from small pieces to bigger collections.

[Data rinowanzorongwa nematanho, kubva pazvidimbu zvidiki kusvika kuzvikwata zvikuru.]

Imagine your school's student records:

  • Columns (Fields): These are like categories, e.g., "First Name", "Surname", "Class", "Date of Birth".
  • Rows (Records): Each row is all the information for one student. E.g., one row for Tendai, another for Rudo.
  • Table (File): All the rows and columns together for a specific group (e.g., "Form 1 Students Table", "Teachers Table"). A table is like one of your exercise books for a specific subject.

5. Data Dictionary:

This is like a special dictionary for your database. It holds all the metadata.

[Iri iduramazwi rinotsanangura data rese riri mudatabase.]

It tells you what each piece of data means, what format it should be in (e.g., date, number, text), and any rules for that data.

Example: The data dictionary would say that "Date of Birth" must be a valid date, or that "Exam Mark" must be a number between 0 and 100.

The History of Databases (Nhoroondo yeMadatabase)

Databases weren't always like they are today. They have changed a lot!

  • Early Days (1960s - Nguva dzekare kare):

    When big computers (mainframes) first came out.

    Databases were simple and not very flexible. Imagine very rigid filing systems.

    [Pakabuda makombiyuta makuru ekutanga. Madatabase ainge akareruka uye asina kunyatsoshanduka-shanduka.]

  • Relational Databases (1970s - Kuzvarwa kwematafura):

    A very clever man named Edgar F. Codd came up with a new idea: the relational model.

    This meant organizing data into tables with rows and columns (like we discussed in Data Hierarchy). This made it much easier to work with data.

    [Mumwe murume akachenjera, Edgar F. Codd, akauya nepfungwa yekuronga data mumatafura ane mitsara nemacolumns. Izvi zvakaita kuti kushanda nedata kuve nyore.]

    A special language called SQL (Structured Query Language) was developed to talk to these relational databases. We still use SQL a lot today!

    [Mutauro unokosha unonzi SQL wakagadzirwa kutaura nemadatabase aya.]

  • Rise of DBMS (1980s - Kubuda kwevaManager veData):

    Powerful DBMS software like Oracle, MySQL, and Microsoft SQL Server were created.

    These made it easier for more people and companies to create and manage databases.

    [Mapurogiramu eDBMS ane simba akagadzirwa, zvichiita kuti vanhu nemakambani vakwanise kugadzira nekutarisira madatabase.]

  • Modern Era (1990s-Present - Nguva dzanhasi):

    Things keep getting better!

    NoSQL databases: For handling huge amounts of data that isn't always neatly structured (like social media posts or website data).

    Cloud databases: Databases stored on the internet, so you can access them from anywhere (like Google Drive, but for structured data).

    More focus on keeping data secure and private.

Why Organizations Need Databases (Sei Masangano Achida Madatabase?)

Think about any organization in Zimbabwe:

  • Your school
  • A clinic or hospital (like Parirenyatwa)
  • A shop (like OK Zimbabwe or TM Pick n Pay)
  • A bank (like CBZ or Stanchart)
  • A government department (like ZIMRA for taxes)

All these places need databases! Here's why:

  1. Data Centralization (Kuisa Data Panzvimbo Imwe):

    A database puts all important information in ONE place.

    Imagine a school: Instead of teachers keeping student records in different exercise books, and some on scraps of paper, a database puts all student information in one safe, central computer system. Everyone who needs it can find the same correct information.

    [Database rinoisa mashoko ese akakosha panzvimbo IMWE. Funga nezvechikoro: pane kuti vadzidzisi vachengete marekodhi evadzidzi mumabhuku akasiyana, database rinoisa zvese pakombiyuta imwe.]

  2. Improved Efficiency (Kushanda Zviri Nane uye Nekukurumidza):

    It's much faster to find information in a database.

    Imagine trying to find how many students in your school come from Highfield by looking through hundreds of paper forms. With a database, the secretary can do a quick search and get the answer in seconds!

    [Zvinokurumidza zvikuru kutsvaga mashoko mudatabase. Semuenzaniso, kutsvaga kuti vangani vadzidzi vanobva kuHighfield zvinotora nguva diki pane kutsvaga mumapepa.]

  3. Data Integrity (Kuve neData Rakarurama):

    Databases help make sure the information is accurate and consistent (the same everywhere).

    They can have rules. For example, a rule that a student's birth year cannot be in the future, or that an exam mark must be between 0 and 100. This reduces mistakes.

    [Madatabase anobatsira kuona kuti mashoko akarurama uye haapikisane. Panogona kuve nemitemo, sekuti gore rekuzvarwa kwemudzidzi harigone kunge riri mune ramangwana.]

  4. Data Security (Kuchengetedzwa kweData):

    Databases can protect information. Not everyone can see or change everything.

    For example, at a bank, only certain bank tellers can access your account details, and they need a password. This keeps your money information safe.

    [Madatabase anogona kuchengetedza mashoko. Havasi vese vanokwanisa kuona kana kuchinja zvese. Semubhanga, vanhu vakati chete ndivo vanokwanisa kuona nezveakaundi yako.]

  5. Data Analysis and Reporting (Kuongorora Data neKugadzira Mishumo):

    Organizations can use the data in databases to understand things better and make good decisions.

    A shop like OK Zimbabwe can look at its sales data to see which products are selling the most in which branch (e.g., more Mazoe Orange Crush sold in Bulawayo than Mutare). This helps them decide what to stock.

    [Masangano anogona kushandisa data kuti anzwisise zvinhu zviri nani. Chitoro chinogona kuona kuti ndezvipi zvigadzirwa zviri kutengwa zvakanyanya.]

  6. Scalability and Growth (Kukwanisa Kukura neSangano):

    As an organization grows and gets more data, the database can grow with it.

    A small clinic might start with a few hundred patient records. As it becomes a big hospital with thousands of patients, a good database system can handle the extra information.

    [Sangano parinokura, database rinokwanisawo kukura richibata data rakawanda.]

Characteristics of a Database (Hunhu hweDatabase Rakanaka)

Good databases have these qualities:

  1. ACID Properties (Atomicity, Consistency, Isolation, Durability):

    This is a fancy term, but it's super important. It means transactions (like saving data or changing data) are reliable.

    [Izwi rehunyanzvi, asi rinoreva kuti mashandiro edata (sekuchengeta kana kuchinja) akavimbika.]

    • Atomicity (Zvese kana Pasina): A transaction is "all or nothing."

      Example: When you send money using EcoCash, either the money leaves your account AND reaches the other person, OR the transaction fails and nothing changes. The money won't just disappear.

      [Basa rinoitwa rese kana kuti haritombotanga. Semuenzaniso, paunotumira mari neEcoCash, kana mari ichibva kwauri ichienda kumunhu, zvese zvinoitika, kana kuti hapana chinoitika. Mari haingonyangarika.]

    • Consistency (Kutevedzera Mitemo): The database always follows its rules. Data stays valid.

      Example: If a rule says a student's age must be a number, you can't enter "fifteen" as words. The database will be consistent.

      [Database rinogara richitevera mitemo yaro. Data rinoramba riri chokwadi. Semuenzaniso, kana mutemo uchiti zera remudzidzi rinofanira kuva nhamba, haugone kunyora kuti "gumi neshanu" nemazwi.]

    • Isolation (Kushanda Pasina Kukanganiswa): If many people are using the database at the same time, their actions don't interfere with each other.

      Example: If you and your friend are trying to book the very last seat on a ZUPCO bus online at the exact same moment, the database makes sure only one of you gets it, and things don't get mixed up.

      [Kana vanhu vakawanda vari kushandisa database panguva imwe chete, mabasa avo haakanganisane. Semuenzaniso, kana vaviri vari kuyedza kubhuka chigaro chekupedzisira muZUPCO online panguva imwe chete, database rinoona kuti mumwe chete ndiye anowana chigaro.]

    • Durability (Kusimba Kwekuchengeta): Once data is saved, it stays saved, even if there's a power cut (magetsi akaenda) or the computer crashes.

      Example: If the school secretary enters your exam marks and saves them, those marks should still be there tomorrow, even if the computer was switched off.

      [Kana data rachengetwa, rinoramba rakachengetwa, kunyangwe magetsi akaenda kana kombiyuta ikafa. Semuenzaniso, kana mabharani wechikoro akaisa mamakisi ako akaachengeta, anofanira kuramba aripo mangwana.]

  2. Structured Data (Data Rakarongeka):

    Data is organized neatly, usually in tables with rows and columns. This makes it easy to find and use.

    [Data rakarongeka zvakanaka, kazhinji mumatafura ane mitsara nemacolumns.]

  3. Query Languages (Mitauro Yekubvunza):

    Databases use special languages like SQL to "ask questions" or get specific information.

    [Madatabase anoshandisa mitauro yakadai seSQL "kubvunza mibvunzo" kana kutora mashoko chaiwo.]

    Example: A teacher could use SQL to ask the database: "Show me all students in Form 1 who got above 80% in Maths."

  4. Concurrency Control (Kugona Kushandiswa Nevakawanda Panguva Imwe):

    Many users can access and use the database at the same time without messing things up. The DBMS manages this.

    [Vashandisi vakawanda vanogona kushandisa database panguva imwe chete pasina matambudziko.]

  5. Backup and Recovery (Kuchengeta Kopi neKudzoreredza):

    Good databases have ways to make copies (backups) of the data. If something goes wrong (like a computer breaks), the data can be recovered from the backup.

    [Madatabase akanaka ane nzira dzekuita makopi edata. Kana chimwe chinhu chikakanganisika, data rinogona kudzoreredzwa kubva pakopi.]

Challenges in Information Centre Database Development and Management
(Matambudziko Mukugadzira Nekutarisira Madatabase eZvikoro Zveruzivo)

Think of an Information Centre (IC) like your school library, a community library, or even a place that keeps historical records. They have special challenges with databases:

  1. Data Variety (Mhando dzakasiyana dzeData):

    ICs deal with many types of information: books, old newspapers, magazines (like Moto or Parade), photos, videos, student research papers. These are all in different formats. It's hard to put them all neatly into one type of database structure.

    [Nzvimbo dzeruzivo dzinobata nemhando dzakawanda dzemashoko: mabhuku, mapepanhau ekare, mapikicha, mavhidhiyo. Izvi zviri mumafomati akasiyana, zvichiita kuti zviome kuzviisa mudatabase rimwe chete.]

  2. Data Integration (Kubatanidza Data Kubva Kwakasiyana):

    Getting all this different data from different sources into one database so people can search it easily is a big job. You need to make formats the same and ensure quality.

    [Kuisa data rese iri kubva kwakasiyana mudatabase rimwe chete kuti vanhu vakwanise kutsvaga zviri nyore ibasa guru.]

  3. Metadata Management (Kutarisira Mashoko Anotsanangura Data):

    For every book, photo, or article, you need good metadata (like author, date, subject, keywords) so people can find it. Creating and updating this metadata for thousands of items takes a lot of time.

    [Kune bhuku rega rega kana pikicha, unoda metadata yakanaka (semunyori, zuva, musoro wenyaya) kuti vanhu vazviwane. Izvi zvinotora nguva yakareba.]

  4. Scalability and Growth (Kukura KweData):

    ICs get new information all the time. The database needs to be able to handle more and more data without slowing down. Old information still needs to be findable.

    [Nzvimbo dzeruzivo dzinogara dzichiwana mashoko matsva. Database rinofanira kukwanisa kubata data rakawanda risinganonoke.]

  5. User Needs and Skills (Zvinodiwa neVashandisi neUnyanzvi Hwavo):

    Some people using the IC database might be good with computers, others might not. The database needs to be easy for everyone to use. Staff also need training.

    [Vamwe vanhu vanoshandisa database vanogona kunge vachigona makombiyuta, vamwe vasingagone. Database rinofanira kuva nyore kushandisa kune wese wese.]

  6. Security and Access Control (Kuchengetedzeka neKodzero dzeKushandisa):

    Some information might be sensitive or private (e.g., old personal letters in an archive). The IC needs to protect this but still allow authorized people to see what they need.

    [Mamwe mashoko anogona kunge ari chakavanzika. IC inofanira kuchengetedza izvi asi ichibvumira vanhu vane mvumo kuona zvavanoda.]

  7. Budgetary Constraints (Kushaikwa Kwemari Yakakwana):

    Building and maintaining a good database system costs money (for computers, software, and skilled people). ICs, especially in schools or communities, often don't have a big budget (mari shoma).

    [Kuvaka nekuchengetedza database kunoda mari. Nzvimbo dzeruzivo dzinowanzove dzisina mari yakawanda.]

Strategies to Mitigate Challenges (Nzira dzeKuderedza Matambudziko)

How can ICs deal with these challenges?

  1. Standardization (Kuisa Mitemo Yakaenzana):

    Use common ways to describe and format data. This makes it easier to combine data and for people to search. For example, always writing dates as DD/MM/YYYY.

    [Kushandisa nzira dzakafanana dzekutsanangura nekugadzira data. Semuenzaniso, kunyora mazuva ese se DD/MM/YYYY.]

  2. Metadata Management Tools (Zvishandiso zveKutarisira Metadata):

    Use software that can help create and manage metadata, sometimes even automatically.

    [Kushandisa mapurogiramu anobatsira kugadzira nekutarisira metadata.]

  3. Scalable Database Solutions (Madatabase Anokwanisa Kukura):

    Choose database systems that can easily grow. Cloud-based databases can be good for this as you can pay for more storage as you need it.

    [Kusarudza madatabase anokwanisa kukura zviri nyore. Madatabase epaIndaneti anogona kubatsira.]

  4. User-Friendly Interfaces (Nzira dzeKushandisa Dziri Nyore):

    Make the database search screen look simple and easy to understand, even for beginners. Provide training.

    [Kuita kuti nzvimbo yekutsvaga mudatabase ive nyore kunzwisisa, kunyangwe kune vachangotanga. Kupawo dzidziso.]

  5. Role-based Access Control (Kodzero dzeKushandisa Zvinoenderana neBasa):

    Give people access only to the information they need for their job. A student might search, but only a librarian can add or delete books.

    [Kupa vanhu mvumo yekuona mashoko avanoda chete pabasa ravo.]

  6. Open Source Solutions (Mapurogiramu Asingabhadharwe):

    Use free, open-source DBMS software if the budget is very tight. These can be very good, but might need more technical skill to set up.

    [Kushandisa mapurogiramu eDBMS asingabhadharwe kana mari iri shoma. Anogona kunge akanaka asi achida hunyanzvi hwekuamisa.]

Topic 2: Traditional File Systems vs. Database Systems
(Kuenzanisa Mafaira Akareruka neMadatabase Systems)

Before we had fancy databases, and even now for simple things, we use Traditional File Systems.

Traditional File Systems (Nzira dzeKare dzeKuchengeta Mafaira)

Think of the folders on your computer (like "My Documents", "Pictures", "Music") or on your phone. Inside these folders, you save individual files (a Word document, a photo, an MP3 song). This is a traditional file system.

[Funga nezvemafodha ari pakombiyuta yako kana pafoni yako. Mukati memafodha aya, unochengeta mafaira ega ega. Iyi ndiyo traditional file system.]

It's like a digital version of putting papers into different physical folders in a filing cabinet.

[Zvakafanana nekuisa mapepa mumafolda akasiyana mukabhodhi.]

Advantages of Traditional File Systems (Zvakanakira Mafaira Akareruka):

  1. Simplicity (Kureruka): Easy to understand and use for basic things. You don't need to be a computer expert to save a file in a folder.
  2. Speed and Efficiency (for some tasks): Reading or writing one single file can be quick.
  3. Customization (Kugadzira Nenzira Yako): You can create folders and name them however you like to organize your own stuff.
  4. Offline Access (Kukwanisa Kushandisa Usina Indaneti): You can access your files even if you are not connected to the internet.
  5. Lower Cost (Mutengo Wakaderera): Usually doesn't cost extra; it's part of your computer's operating system (like Windows or Android).

Disadvantages of Traditional File Systems (Zvakaipira Mafaira Akareruka):

  1. Data Redundancy (Data Rakawanda Risina Basa):

    You can easily have the same information saved in many different folders.

    [Unogona kuva neruzivo rumwe chete rwakachengetwa mumafolda akawanda akasiyana.]

    Example: You might save a photo of your family in a folder called "Family Pics" AND also in a folder called "Holiday 2023". It's the same photo, taking up space twice. If you edit one, the other stays old.

    [Semuenzaniso, unogona kuchengeta pikicha yemhuri yako mu "Family Pics" uye zvakare mu "Holiday 2023". Iyo pikicha imwe chete, inotora nzvimbo kaviri.]

  2. Data Integrity Issues (Matambudziko eKururama kweData):

    If you have the same info in different places, and you change it in one place but forget to change it in others, then your data becomes inconsistent and confusing. Which one is correct?

    [Kana uine mashoko akafanana munzvimbo dzakasiyana, ukachinja pane imwe ukakanganwa pane dzimwe, data rako rinobva rasanganisa.]

  3. Limited Sharing and Collaboration (Zvinetso paKugovana neKushanda Pamwe):

    It's hard for many people to work on the same files easily. You might have to email files back and forth, which can be messy.

    [Zvakaoma kuti vanhu vakawanda vashande pamwe chete pamafaira amwe. Mungatofanira kutumirana nemaemail.]

  4. Scalability Limitations (Zvinetso paKukura kweData):

    When you have thousands and thousands of files, it becomes very hard to manage and find things.

    [Kana uine zviuru zvemafaira, zvinova zvakaoma kwazvo kutarisira nekutsvaga zvinhu.]

  5. Security Challenges (Zvinetso zveKuchengetedza):

    It can be harder to control who sees which files properly.

    [Zvinogona kuoma kudzora kuti ndiani anoona mafaira api.]

Database Systems (Recap) (Madatabase Systems - Kuyeuchidza)

We already learned about these! A database is an organized collection of structured data, managed by a DBMS.

[Takatodzidza nezveizvi! Database muunganidzwa wakarongeka wedata, unotarisirwa neDBMS.]

Advantages of Database Systems (Zvakanakira Madatabase Systems):

  1. Data Organization and Structure (Kurongeka kweData): Data is in tables – neat and tidy. [Data riri mumatafura – zvakarongeka.]
  2. Data Integrity and Consistency (Kururama kweData): Rules help keep data accurate. [Mitemo inobatsira kuti data rive chokwadi.]
  3. Reduced Data Redundancy (Kuderedza Data Risina Basa): Information is stored once centrally, so less duplication.

    [Mashoko anochengetwa kamwe chete panzvimbo imwe, saka hapana kudzokorora kwakawanda.]

    Example: A student's address is stored once. If it changes, you update it in one place, and everyone sees the new address.

    [Kero yemudzidzi inochengetwa kamwe chete. Ikachinja, unochinja panzvimbo imwe chete, uye wese anoona kero itsva.]

  4. Enhanced Data Sharing and Collaboration (Kugovana Nekushanda Pamwe Zviri Nane): Many people can use the data at the same time.
  5. Data Security and Access Control (Kuchengetedzwa kweData neKodzero dzeKushandisa): Good control over who can see or change what.
  6. Powerful Query Capabilities (Kugona Kubvunza Zvakawanda): You can ask complex questions to find exactly what you need using languages like SQL.
  7. Scalability and Growth (Kukwanisa Kukura): Can handle large amounts of data and more users as needed.

Disadvantages of Database Systems (Zvakaipira Madatabase Systems):

  1. Complexity (Kuoma Kunzwisisa): Designing and managing a database can be complicated. It needs special skills.
  2. Cost (Mutengo): Database software, powerful computers (hardware), and skilled staff can be expensive.
  3. Steeper Learning Curve (Zvinoda Kudzidza Zvakawanda): Users might need to learn query languages (like SQL) and understand how data is structured.
  4. Performance Overhead (for very small tasks): For very, very simple tasks with little data, a database might seem slower than just opening a single file because there's more software involved. But for most real-world needs, databases are much more efficient.

File Systems vs. Databases: Which one to use?
(Mafaira Akareruka neMadatabase: Ndechipi chekushandisa?)

Let's compare them side-by-side:

Feature Traditional File System Database System
Structure (Kurongeka) Folders and files. Data can be in any format (text, pic) Tables with rows and columns. Structured data.
Data Management (Kutarisira Data) Limited. You manage it yourself. Risk of errors. Strong! DBMS helps. Rules for integrity, less redundancy.
Sharing (Kugovana) Can be clumsy (emailing files). Hard for many to edit. Designed for sharing. Many users can access/edit safely.
Scalability (Kukura) Gets hard to manage with lots of data. Can handle very large amounts of data and users.
Security (Kuchengetedzeka) Basic. Can be hard to set detailed permissions. Strong! User permissions, encryption.
Cost & Complexity (Mutengo neKuoma) Simple, usually no extra cost. Can be complex and expensive (software, hardware, staff).

When to use which:

  • Use a Traditional File System for:
    • Your personal documents, photos, music on your own computer.
    • Small projects where you are the only one working on the files.
    • Simple storage where you don't need complex relationships between data.
  • Use a Database System for:
    • A school's student records (names, grades, addresses, fees).
    • A shop's inventory (list of all products, prices, stock levels).
    • A hospital's patient records.
    • A bank's customer accounts.
    • Any situation where data needs to be accurate, shared by many, secure, and easily searched or analyzed.

Quiz: Database Concepts (LO1)

1 of 20

Question text will load here.

    Quiz Results

    Score: 0%

    Answered: 0 out of 0

    Correct: 0

    Review Incorrect/Skipped Answers: