Assignment help
Join our 150Π of happy users
Get original papers written according to your instructions and save time for what matters most.
Pearson BTEC International Level 3 β Information Technology
Unit 2: Creating Systems to Manage Information
The RAR archive contained 3 files. Here is the full content of each:
File 1: Assignment Brief β Learning Aim A
Unit 2: Creating Systems to Manage Information
| Field | Details |
|---|---|
| Qualification | Pearson BTEC International Level 3 National Extended Diploma in Information Technology |
| Unit number and title | Unit 2: Creating Systems to Manage Information |
| Learning aim(s) | A: Understand the purpose and structure of relational database management systems |
| Assignment title | A Relational Database |
| Assessor | |
| Issue date | |
| Hand in deadline |
Vocational Scenario or Context
You are an IT consultant and have been asked to work with Go Wild Wildlife Park to advise on how a relational database management system (RDBMS) could help them manage their information. The wildlife park has provided you with a CSV dataset containing records about animals, their keepers, and enclosures.
Although you will not yet design or develop the database, you must explain, analyse and evaluate how the features and functions of a relational database could be used to manage this dataset effectively.
The owner of the park is not familiar with relational databases and wants to understand how such a system would support:
- Storing and organizing data from the CSV file (animals, staff, enclosures)
- Managing relationships between data (e.g., one keeper to many animals, many animals per enclosure)
- Supporting data integrity, validity, and accuracy
- Enabling useful queries and reporting for decision-making
Task 1
Produce a report for the park owner that evaluates the purpose and structure of a relational database management system. You should include:
- An explanation of how relational database features (tables, records, fields, primary keys, foreign keys, relationships, queries, forms, reports, validation, etc.) are used for database management. (A.P1)
- An analysis of how these features would contribute to a suitable database solution for managing the provided dataset. (A.M1)
- An evaluation of how the features and functions of a relational database contribute to an effective final solution for managing the dataset. (A.D1)
Checklist of evidence required: Report
Criteria Covered by Task 1
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/A.D1 | Evaluate how the features and functions of a relational database contribute to a final solution for database management. |
| 2/A.M1 | Analyse how the features of a relational database contribute to a final solution for database management. |
| 2/A.P1 | Explain how the features of a relational database are used for database management. |
π File 2: Assignment Brief β Learning Aims B and C
Unit 2: Creating Systems to Manage Information
| Field | Details |
|---|---|
| Qualification | Pearson BTEC International Level 3 Subsidiary / Foundation / Diploma / Extended Diploma in IT |
| Unit number and title | Unit 2: Creating Systems to Manage Information |
| Learning aim(s) | B: Design a relational database to meet client requirements C: Develop a relational database to meet client requirements |
| Assignment title | Managing Information at the Wildlife Park |
| Assessor | |
| Issue date | |
| Hand in deadline |
Vocational Scenario or Context
You have been asked to create a relational database for Go Wild Wildlife Park. The database will store records on animals and their keepers. The park looks after animals from across the world. The park is based in Wollombi, New South Wales, Australia.
The data provided in the data file is presented in one large table. This table is inefficient because it has repeated data. You will split up this large table into five linked tables that record the:
- Animals β animal ID, name, gender, year of arrival, and primary keys from other tables
- Species β species ID, species type, species group, lifestyle, conservation status
- Diet β diet ID, diet type, number of feeds per day
- Keepers β keeper ID, name, date of birth, rank
- Enclosures β enclosure ID, type, location
The park employs keepers of varying ranks: Senior, Standard, and Junior. Each animal is assigned to one keeper who cares for several animals. The park uses a variety of enclosures (e.g., moat), each housing several animals. Each animal is fed a specific diet a set number of times a day.
Task 1
Create a data dictionary and entity relationship diagram (ERD) for the database. The database structure must:
- Accept the data provided
- Avoid unnecessary duplication
- Use recognised naming conventions
- Ensure data integrity
The data dictionary must demonstrate appropriate validation which may include:
- Presence checks
- Length checks
- Value lookups
- Table lookups
- Range checks
- Format checks
Comment on your designs to evaluate how your decisions meet the purpose of the database.
Checklist of evidence required: A database dictionary + design comments
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/B.D2 | Evaluate the design against client requirements. |
| 2/BA.M2 | Justify design decisions made, showing how the design will fulfil its purpose and client requirements. |
| 2/B.P2 | Produce designs for a relational database that meets client requirements. |
Task 2
Use your data dictionary and ERD to create the relational database structure.
Task B β The owner wants you to create data entry forms for:
- Animals in the park
- Animals' species
- Animals' diet
- Keepers
- Enclosures
Forms must include features to ensure validity and integrity of data, and include at least one automated feature.
Checklist of evidence required: A written report
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/C.M5 | Implement an automated function. |
| 2/C.P3 | Create and populate a relational database to meet client requirements. |
| 2/C.P4 | Create features in data entry forms to ensure validity and integrity of data. |
Task 3
Import the data from the CSV file into your database. Create the following queries (show design view and datasheet view for each):
- Alphabetical sorted list of keepers β showing ID, name, and rank
- Count of animals in each type of enclosure
- Parameter query β user enters keeper rank; displays keeper name and date of birth
- Total animals per species with more than 3 feeds per day
- Omnivores who are critically endangered β showing animal ID, arrival date, species ID, keeper ID
- Number of animals in each enclosure location (North, South, East, West)
- Animals that arrived from 2016 onwards β displaying ID, name, year, species type, keeper ID
Checklist of evidence required: A written report
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/C.M3 | Import data from an external source. |
| 2/C.M4 | Use advanced features and functions to manipulate data within the database. |
| 2/C.P3 | Create and populate a relational database to meet client requirements. |
| 2/C.P5 | Perform queries using multiple tables and multiple criteria. |
| 2/C.P6 | Use database features and functions to manipulate data within the database. |
Task 4
Create database reports that:
- Display animals supervised by Dave and Temi, grouped by keeper with animal details, count per keeper, and overall total
- Show how many animals belong to each Conservation Status category (Endangered, Vulnerable, Least Concern, etc.)
- Group animals by Enclosure Type, displaying species type and total number of animals per group
Checklist of evidence required: A written report
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/C.M4 | Use advanced features and functions to manipulate data within the database. |
| 2/C.P5 | Perform queries using multiple tables and multiple criteria. |
Task 5
Create a test plan to test:
- Input forms including calculations, validation, and macros/code
- Use appropriate test data: normal, erroneous, and extreme
- Complete the plan showing expected outcomes, actual outcomes, and how errors were fixed
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/C.M6 | Use testing outcomes to improve and refine the database solution. |
| 2/C.P7 | Test the database for correctness, functionality and acceptance. |
Task 6
Evaluate your database against the given scenario, justifying:
- How well your solution meets the requirements of the scenario
- The quality, performance and usability of the database
- The changes made during the development and testing process
| Unit/Criteria Reference | To achieve the criteria you must show that you are able to: |
|---|---|
| 2/C.D3 | Evaluate the quality of the testing and the refined database solution. |
Internal Verification β Assignment Brief
| Field | Details |
|---|---|
| Programme Title | HND Information Technology Level 3 |
| Assessor Name | Muqaddas Bin Tahir |
| Internal Verifier Name | Uroosha Tanveer |
| Unit/Component | Unit 20: Business Process Modeling Tools |
| Assignment title | Planning business change |
| Assessment criteria | P1, P2, M1, D1, P3, P4, M2, D2, P5, P6, M3 |
| Authorised Assignment Brief (Pearson)? | Yes |
| Submitted to Assignment Checking Service? | No |
Internal Verifier Checklist:
| Check | Y/N |
|---|---|
| Are the programme and unit details accurate? | Yes |
| Are clear deadlines for assessment given? | Yes |
| Is the time frame of an appropriate duration? | Yes |
| Is there a suitable vocational scenario or context? | Yes |
| Are the assessment criteria to be addressed stated accurately? | Yes |
| Does each task show which criteria are being addressed? | Yes |
| Do the tasks meet the assessment requirements of the unit/s? | Yes |
| Is it clear what evidence the learner needs to generate? | Yes |
| Is it likely to generate evidence that is valid and sufficient? | Yes |
| Overall, is the Assignment fit for purpose? | Yes |
| Role | Name | Date |
|---|---|---|
| Internal Verifier | Uroosha Tanveer | 23rd Aug, 2023 |
| Assessor | Muqaddas Bin Tahir | 23rd Aug, 2023 |
| Lead Internal Verifier | Harum Saghir | 23rd Aug, 2023 |
π File 3: Data Dictionary (CSV) β Go Wild Wildlife Park
| Animal ID | Animal name | Gender | Year of arrival | Species ID | Species type | Species group | Lifestyle | Conservation Status | Diet ID | Diet type | No of feeds per day | Keeper ID | Keeper name | Keeper DoB | Keeper rank | Enclosure ID | Enclosure type | Enclosure location |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| A3 | Taro | M | 2018 | S3 | Tiger | Bird | Colony | Endangered | D1 | Herbivore | 6 | K1 | Bob | 6/18/1964 | Junior | E2 | Cave | North |
| A4 | Zuri | M | 2011 | S4 | Python | Mammal | Colony | Least Concern | D1 | Carnivore | 4 | K1 | Alice | 6/18/1964 | Senior | E1 | Moat | West |
| A6 | Milo | M | 2000 | S6 | Giraffe | Mammal | Colony | Vulnerable | D2 | Herbivore | 4 | K2 | Henry | 1/21/1985 | Junior | E3 | Moat | South |
| A7 | Simba | M | 2013 | S7 | Iguana | Mammal | Colony | Critically Endangered | D3 | Carnivore | 4 | K2 | Alice | 1/21/1985 | Junior | E3 | Forest | East |
| A8 | Taro | M | 2016 | S8 | Kangaroo | Bird | Colony | Threatened | D2 | Herbivore | 3 | K2 | Alice | 1/21/1985 | Junior | E4 | Ice Pool | South |
| A9 | Arlo | M | 2012 | S9 | Panda | Mammal | Troop | Vulnerable | D1 | Herbivore | 6 | K2 | Carlos | 1/21/1985 | Junior | E5 | Ice Pool | East |
| A10 | Nala | M | 2015 | S10 | Python | Bird | Herd | Threatened | D2 | Omnivore | 2 | K2 | Frank | 1/21/1985 | Senior | E5 | Forest | East |
| A11 | Taro | F | 2011 | S11 | Tiger | Reptile | Colony | Least Concern | D3 | Omnivore | 5 | K3 | Henry | 9/8/2005 | Junior | E4 | Ice Pool | South |
| A12 | Milo | M | 2017 | S12 | Iguana | Mammal | Solitary | Least Concern | D1 | Herbivore | 2 | K3 | Grace | 9/8/2005 | Junior | E5 | Ice Pool | South |
| A13 | Simba | F | 2018 | S13 | Python | Mammal | Solitary | Endangered | D3 | Herbivore | 6 | K3 | Eva | 9/8/2005 | Standard | E3 | Moat | South |
| A14 | Zuri | F | 2013 | S14 | Tiger | Mammal | Solitary | Critically Endangered | D2 | Omnivore | 5 | K3 | Bob | 9/8/2007 | Junior | E5 | Ice Pool | South |
| A15 | Milo | M | 2000 | S15 | Leopard | Mammal | Solitary | Threatened | D1 | Omnivore | 6 | K3 | Grace | 9/8/2007 | Standard | E3 | Grassland | North |
| A16 | Milo | F | 2017 | S16 | Leopard | Reptile | Troop | Vulnerable | D1 | Omnivore | 4 | K4 | Bob | 4/16/2021 | Senior | E2 | Terrarium | West |
| A17 | Nala | F | 2015 | S17 | Seal | Bird | Solitary | Least Concern | D1 | Carnivore | 5 | K4 | Carlos | 4/16/2016 | Senior | E2 | Cave | East |
| A18 | Kiki | M | 2018 | S18 | Python | Mammal | Colony | Endangered | D1 | Herbivore | 4 | K4 | Bob | 4/16/2021 | Senior | E3 | Grassland | South |
| A19 | Simba | F | 2001 | S19 | Leopard | Reptile | Pair | Endangered | D2 | Omnivore | 2 | K4 | Alice | 4/16/2016 | Senior | E4 | Ice Pool | South |
| A20 | Max | M | 2003 | S20 | Tiger | Mammal | Solitary | Threatened | D2 | Herbivore | 2 | K4 | Henry | 4/16/2017 | Standard | E3 | Moat | South |
| A22 | Milo | F | 2003 | S8 | Seal | Mammal | Troop | Least Concern | D2 | Carnivore | 5 | K2 | Eva | 1/21/1985 | Junior | E4 | Forest | North |
| A23 | Kiki | M | 2000 | S3 | Tiger | Mammal | Troop | Critically Endangered | D1 | Carnivore | 5 | K1 | Diana | 6/18/1964 | Senior | E2 | Ice Pool | South |
| A24 | Max | M | 2017 | S7 | Seal | Mammal | Solitary | Least Concern | D3 | Omnivore | 6 | K2 | Bob | 1/21/1985 | Junior | E3 | Moat | South |
| A25 | Simba | F | 2015 | S11 | Python | Bird | Pair | Threatened | D3 | Carnivore | 6 | K3 | Grace | 9/8/2007 | Standard | E4 | Terrarium | South |
| A26 | Luna | F | 2018 | S12 | Iguana | Mammal | Solitary | Threatened | D1 | Herbivore | 4 | K3 | Alice | 9/8/2010 | Standard | E5 | Ice Pool | West |
| A27 | Arlo | M | 2001 | S16 | Giraffe | Mammal | Troop | Least Concern | D1 | Omnivore | 5 | K4 | Diana | 4/16/2017 | Standard | E2 | Forest | North |
| A28 | Kiki | M | 2003 | S16 | Eagle | Bird | Herd | Threatened | D1 | Herbivore | 2 | K4 | Eva | 4/16/2017 | Senior | E2 | Moat | South |
| A29 | Nova | F | 2003 | S16 | Iguana | Mammal | Colony | Least Concern | D1 | Herbivore | 6 | K4 | Diana | 4/16/2022 | Junior | E2 | Moat | East |
| A30 | Luna | F | 2013 | S18 | Penguin | Mammal | Troop | Vulnerable | D1 | Carnivore | 6 | K4 | Alice | 4/16/2022 | Junior | E3 | Moat | East |
| A31 | Arlo | M | 2016 | S11 | Tiger | Mammal | Solitary | Least Concern | D3 | Carnivore | 2 | K3 | Henry | 9/8/2010 | Junior | E4 | Terrarium | East |
| A32 | Nala | F | 2012 | S3 | Penguin | Bird | Colony | Least Concern | D1 | Carnivore | 6 | K1 | Henry | 6/18/1964 | Standard | E2 | Ice Pool | North |
| A33 | Taro | F | 2015 | S4 | Iguana | Mammal | Solitary | Threatened | D1 | Carnivore | 4 | K1 | Frank | 6/18/1964 | Senior | E1 | Terrarium | North |
| A34 | Zuri | M | 2011 | S4 | Seal | Mammal | Solitary | Threatened | D1 | Carnivore | 5 | K1 | Henry | 6/18/1964 | Standard | E1 | Cave | East |
| A35 | Nova | F | 2017 | S13 | Eagle | Mammal | Herd | Endangered | D3 | Omnivore | 2 | K3 | Frank | 9/8/2010 | Standard | E3 | Cave | South |
| A36 | Nala | F | 2018 | S6 | Eagle | Mammal | Colony | Endangered | D2 | Herbivore | 5 | K2 | Diana | 1/21/1985 | Junior | E3 | Ice Pool | North |
| A37 | Simba | F | 2013 | S15 | Panda | Mammal | Colony | Vulnerable | D1 | Herbivore | 6 | K3 | Carlos | 9/8/2013 | Standard | E3 | Terrarium | East |
| A38 | Nala | F | 2000 | S7 | Eagle | Reptile | Herd | Endangered | D3 | Herbivore | 6 | K2 | Grace | 1/21/1985 | Junior | E3 | Forest | East |
| A39 | Taro | F | 2017 | S8 | Giraffe | Reptile | Troop | Least Concern | D2 | Herbivore | 2 | K2 | Grace | 1/21/1985 | Senior | E4 | Moat | South |
| A40 | Simba | M | 2015 | S7 | Eagle | Bird | Solitary | Threatened | D3 | Carnivore | 4 | K2 | Diana | 1/21/1985 | Junior | E3 | Moat | West |
| A41 | Nova | F | 2018 | S20 | Iguana | Mammal | Pair | Endangered | D2 | Herbivore | 3 | K4 | Bob | 4/16/2022 | Senior | E3 | Ice Pool | North |
| A42 | Taro | M | 2017 | S6 | Panda | Mammal | Solitary | Endangered | D2 | Omnivore | 2 | K2 | Bob | 1/21/1985 | Junior | E3 | Cave | South |
| A43 | Max | F | 2018 | S11 | Iguana | Reptile | Solitary | Vulnerable | D3 | Omnivore | 3 | K3 | Henry | 9/8/2013 | Standard | E4 | Cave | East |
| A44 | Zuri | M | 2013 | S12 | Iguana | Mammal | Troop | Vulnerable | D1 | Herbivore | 3 | K3 | Grace | 9/8/2013 | Standard | E5 | Moat | East |
| A45 | Nova | F | 2000 | S16 | Kangaroo | Mammal | Solitary | Least Concern | D1 | Herbivore | 4 | K4 | Grace | 4/16/2023 | Senior | E2 | Ice Pool | South |
| A46 | Max | F | 2000 | (missing) | Panda | Mammal | Herd | Threatened | D2 | Omnivore | 3 | K2 | Frank | 1/21/1985 | Senior | E4 | Terrarium | North |
| A47 | Arlo | M | 2017 | S13 | Iguana | Mammal | Herd | Vulnerable | D3 | Omnivore | 3 | K3 | Carlos | 9/8/2014 | Senior | E3 | Cave | West |
| A48 | Nova | F | 2015 | S14 | Kangaroo | Mammal | Colony | Endangered | D2 | Carnivore | 4 | K3 | Alice | 9/8/2014 | Junior | E5 | Terrarium | West |
| A49 | Arlo | M | 2018 | S15 | Kangaroo | Bird | Pair | Threatened | D1 | Omnivore | 3 | K3 | Bob | 9/8/2014 | Junior | E3 | Cave | East |
| A50 | Simba | M | 2017 | S3 | Panda | Bird | Solitary | Threatened | D1 | Carnivore | 3 | K1 | Grace | 6/18/1964 | Senior | E2 | Cave | North |
Note: Animal A46 has a missing Species ID in the original data β this is worth noting for your data integrity checks in your data dictionary (presence check).
Note: This report is provided as a sample for reference purposes only. For further guidance, detailed solutions, or personalized assignment support, please contact us directly.

Unit 2: Creating Systems to Manage Information
Sample Solution β Go Wild Wildlife Park
Learning Aim A β Task 1 Report
Introduction
Go Wild Wildlife Park currently stores its data in a single CSV file, which leads to duplication, inconsistency, and difficulty in managing relationships between data. A relational database management system (RDBMS) provides a structured way to store, manage, and retrieve data efficiently. This report explains, analyses, and evaluates how an RDBMS would support the parkβs operations.
A.P1 β Explanation of Relational Database Features
A relational database uses several key features:
Tables
Data is organised into tables such as Animals, Species, Diet, Keepers, and Enclosures. Each table stores related data.
Records and Fields
A record represents a single entry (e.g., one animal), while fields represent attributes (e.g., name, gender).
Primary Keys
Each table contains a unique identifier, such as AnimalID or KeeperID, ensuring that each record is unique.
Foreign Keys
Foreign keys link tables together. For example, SpeciesID in the Animals table links to the Species table.
Relationships
Relationships define how tables are connected. For example:
- One keeper can manage many animals
- One enclosure can contain multiple animals
Queries
Queries are used to retrieve specific data, such as animals that arrived after a certain year or animals in a particular enclosure.
Forms
Forms provide a user-friendly interface for entering and editing data.
Reports
Reports summarise data for decision-making, such as the number of animals per enclosure.
Validation
Validation rules ensure data accuracy, such as:
- Presence checks (no empty required fields)
- Range checks (valid year values)
- Format checks (correct date format)
A.M1 β Analysis
The use of an RDBMS improves data management in several ways:
- Reduction of duplication: Data is split into separate tables, avoiding repeated entries (e.g., keeper details stored once).
- Improved accuracy: Validation rules prevent incorrect or missing data.
- Better organisation: Logical structure makes data easier to manage and understand.
- Efficient querying: Users can quickly retrieve specific information.
For example, instead of storing keeper details repeatedly for each animal, the system stores them once and links them through a foreign key. This reduces redundancy and ensures consistency.
A.D1 β Evaluation
An RDBMS is highly suitable for managing the wildlife parkβs data:
- Data integrity is maintained through primary and foreign keys
- Consistency is ensured by eliminating duplication
- Flexibility allows new data to be added easily
- Performance is improved through efficient queries
However, implementing an RDBMS requires:
- Initial design effort
- Staff training
Overall, the advantages outweigh the limitations, making it an effective solution for managing the parkβs data.
Learning Aim B β Task 1 Design
Data Dictionary (Sample)
Animals Table
| Field Name | Data Type | Description | Validation |
|---|---|---|---|
| AnimalID | Text | Unique ID | Primary Key |
| Name | Text | Animal name | Required |
| Gender | Text | M/F | Value check |
| YearOfArrival | Number | Year animal arrived | Range check |
| SpeciesID | Text | Links to Species | Foreign Key, Required |
| DietID | Text | Links to Diet | Foreign Key |
| KeeperID | Text | Links to Keepers | Foreign Key |
| EnclosureID | Text | Links to Enclosures | Foreign Key |
Validation Example (Important)
Animal A46 has a missing Species ID.
To prevent this:
- Apply a presence check on SpeciesID
- Use a lookup constraint to ensure valid entries
Entity Relationship Design (ERD Explanation)
- Animals β Species (Many-to-One)
- Animals β Keepers (Many-to-One)
- Animals β Diet (Many-to-One)
- Animals β Enclosures (Many-to-One)
This design removes redundancy and ensures efficient data management.
Design Justification (M2 & D2)
The design:
- Eliminates duplicate data
- Uses keys to maintain relationships
- Ensures data integrity through validation
- Supports all required queries and reports
It fully meets the clientβs requirements by providing a structured and scalable solution.
Learning Aim C β Development
Task 2 β Database Creation
- Created five tables: Animals, Species, Diet, Keepers, Enclosures
- Defined primary keys and foreign keys
- Established relationships between tables
Forms
Forms created:
- Animal Form
- Species Form
- Diet Form
- Keeper Form
- Enclosure Form
Features included:
- Drop-down lists (lookup fields)
- Required field validation
- Automatic ID generation
Task 3 β Queries
Queries created include:
- List of keepers sorted alphabetically
- Count of animals in each enclosure
- Parameter query based on keeper rank
- Animals with more than 3 feeds per day
- Critically endangered omnivores
- Number of animals per location
- Animals that arrived from 2016 onwards
These queries support decision-making and data analysis.
Task 4 β Reports
Reports include:
- Animals grouped by keeper
- Animals by conservation status
- Animals by enclosure type
These reports provide clear summaries for management.
Task 5 β Testing
| Test Type | Example | Expected Result |
|---|---|---|
| Normal | Valid data entry | Record saved |
| Erroneous | Missing SpeciesID | Error message |
| Extreme | Very high year value | Rejected |
Errors were identified and corrected through validation rules.
Task 6 β Evaluation
The database meets the requirements by:
- Providing accurate and structured data storage
- Supporting efficient queries and reporting
- Ensuring data integrity through validation
During testing, improvements were made such as:
- Adding stricter validation rules
- Refining relationships
Overall, the database is effective, reliable, and suitable for the wildlife park.
Send Your assignment brief
Share your assignment brief and after Checking assignment requirement expert Will share the quote
Get Quote and pay
Once quote is sent, you can make Payment through secure option after which our team will start work
Get Assignment
Our team will Deliver the work you can share If any feedback

