Assignment help

Join our 150К of happy users

Get original papers written according to your instructions and save time for what matters most.

Card image cap

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

FieldDetails
QualificationPearson BTEC International Level 3 National Extended Diploma in Information Technology
Unit number and titleUnit 2: Creating Systems to Manage Information
Learning aim(s)A: Understand the purpose and structure of relational database management systems
Assignment titleA 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 ReferenceTo achieve the criteria you must show that you are able to:
2/A.D1Evaluate how the features and functions of a relational database contribute to a final solution for database management.
2/A.M1Analyse how the features of a relational database contribute to a final solution for database management.
2/A.P1Explain 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

FieldDetails
QualificationPearson BTEC International Level 3 Subsidiary / Foundation / Diploma / Extended Diploma in IT
Unit number and titleUnit 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 titleManaging 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:

  1. Animals β€” animal ID, name, gender, year of arrival, and primary keys from other tables
  2. Species β€” species ID, species type, species group, lifestyle, conservation status
  3. Diet β€” diet ID, diet type, number of feeds per day
  4. Keepers β€” keeper ID, name, date of birth, rank
  5. 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 ReferenceTo achieve the criteria you must show that you are able to:
2/B.D2Evaluate the design against client requirements.
2/BA.M2Justify design decisions made, showing how the design will fulfil its purpose and client requirements.
2/B.P2Produce 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 ReferenceTo achieve the criteria you must show that you are able to:
2/C.M5Implement an automated function.
2/C.P3Create and populate a relational database to meet client requirements.
2/C.P4Create 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):

  1. Alphabetical sorted list of keepers β€” showing ID, name, and rank
  2. Count of animals in each type of enclosure
  3. Parameter query β€” user enters keeper rank; displays keeper name and date of birth
  4. Total animals per species with more than 3 feeds per day
  5. Omnivores who are critically endangered β€” showing animal ID, arrival date, species ID, keeper ID
  6. Number of animals in each enclosure location (North, South, East, West)
  7. Animals that arrived from 2016 onwards β€” displaying ID, name, year, species type, keeper ID

Checklist of evidence required: A written report

Unit/Criteria ReferenceTo achieve the criteria you must show that you are able to:
2/C.M3Import data from an external source.
2/C.M4Use advanced features and functions to manipulate data within the database.
2/C.P3Create and populate a relational database to meet client requirements.
2/C.P5Perform queries using multiple tables and multiple criteria.
2/C.P6Use database features and functions to manipulate data within the database.

Task 4

Create database reports that:

  1. Display animals supervised by Dave and Temi, grouped by keeper with animal details, count per keeper, and overall total
  2. Show how many animals belong to each Conservation Status category (Endangered, Vulnerable, Least Concern, etc.)
  3. Group animals by Enclosure Type, displaying species type and total number of animals per group

Checklist of evidence required: A written report

Unit/Criteria ReferenceTo achieve the criteria you must show that you are able to:
2/C.M4Use advanced features and functions to manipulate data within the database.
2/C.P5Perform 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 ReferenceTo achieve the criteria you must show that you are able to:
2/C.M6Use testing outcomes to improve and refine the database solution.
2/C.P7Test 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 ReferenceTo achieve the criteria you must show that you are able to:
2/C.D3Evaluate the quality of the testing and the refined database solution.

Internal Verification β€” Assignment Brief

FieldDetails
Programme TitleHND Information Technology Level 3
Assessor NameMuqaddas Bin Tahir
Internal Verifier NameUroosha Tanveer
Unit/ComponentUnit 20: Business Process Modeling Tools
Assignment titlePlanning business change
Assessment criteriaP1, P2, M1, D1, P3, P4, M2, D2, P5, P6, M3
Authorised Assignment Brief (Pearson)?Yes
Submitted to Assignment Checking Service?No

Internal Verifier Checklist:

CheckY/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
RoleNameDate
Internal VerifierUroosha Tanveer23rd Aug, 2023
AssessorMuqaddas Bin Tahir23rd Aug, 2023
Lead Internal VerifierHarum Saghir23rd Aug, 2023

πŸ“„ File 3: Data Dictionary (CSV) β€” Go Wild Wildlife Park

Animal IDAnimal nameGenderYear of arrivalSpecies IDSpecies typeSpecies groupLifestyleConservation StatusDiet IDDiet typeNo of feeds per dayKeeper IDKeeper nameKeeper DoBKeeper rankEnclosure IDEnclosure typeEnclosure location
A3TaroM2018S3TigerBirdColonyEndangeredD1Herbivore6K1Bob6/18/1964JuniorE2CaveNorth
A4ZuriM2011S4PythonMammalColonyLeast ConcernD1Carnivore4K1Alice6/18/1964SeniorE1MoatWest
A6MiloM2000S6GiraffeMammalColonyVulnerableD2Herbivore4K2Henry1/21/1985JuniorE3MoatSouth
A7SimbaM2013S7IguanaMammalColonyCritically EndangeredD3Carnivore4K2Alice1/21/1985JuniorE3ForestEast
A8TaroM2016S8KangarooBirdColonyThreatenedD2Herbivore3K2Alice1/21/1985JuniorE4Ice PoolSouth
A9ArloM2012S9PandaMammalTroopVulnerableD1Herbivore6K2Carlos1/21/1985JuniorE5Ice PoolEast
A10NalaM2015S10PythonBirdHerdThreatenedD2Omnivore2K2Frank1/21/1985SeniorE5ForestEast
A11TaroF2011S11TigerReptileColonyLeast ConcernD3Omnivore5K3Henry9/8/2005JuniorE4Ice PoolSouth
A12MiloM2017S12IguanaMammalSolitaryLeast ConcernD1Herbivore2K3Grace9/8/2005JuniorE5Ice PoolSouth
A13SimbaF2018S13PythonMammalSolitaryEndangeredD3Herbivore6K3Eva9/8/2005StandardE3MoatSouth
A14ZuriF2013S14TigerMammalSolitaryCritically EndangeredD2Omnivore5K3Bob9/8/2007JuniorE5Ice PoolSouth
A15MiloM2000S15LeopardMammalSolitaryThreatenedD1Omnivore6K3Grace9/8/2007StandardE3GrasslandNorth
A16MiloF2017S16LeopardReptileTroopVulnerableD1Omnivore4K4Bob4/16/2021SeniorE2TerrariumWest
A17NalaF2015S17SealBirdSolitaryLeast ConcernD1Carnivore5K4Carlos4/16/2016SeniorE2CaveEast
A18KikiM2018S18PythonMammalColonyEndangeredD1Herbivore4K4Bob4/16/2021SeniorE3GrasslandSouth
A19SimbaF2001S19LeopardReptilePairEndangeredD2Omnivore2K4Alice4/16/2016SeniorE4Ice PoolSouth
A20MaxM2003S20TigerMammalSolitaryThreatenedD2Herbivore2K4Henry4/16/2017StandardE3MoatSouth
A22MiloF2003S8SealMammalTroopLeast ConcernD2Carnivore5K2Eva1/21/1985JuniorE4ForestNorth
A23KikiM2000S3TigerMammalTroopCritically EndangeredD1Carnivore5K1Diana6/18/1964SeniorE2Ice PoolSouth
A24MaxM2017S7SealMammalSolitaryLeast ConcernD3Omnivore6K2Bob1/21/1985JuniorE3MoatSouth
A25SimbaF2015S11PythonBirdPairThreatenedD3Carnivore6K3Grace9/8/2007StandardE4TerrariumSouth
A26LunaF2018S12IguanaMammalSolitaryThreatenedD1Herbivore4K3Alice9/8/2010StandardE5Ice PoolWest
A27ArloM2001S16GiraffeMammalTroopLeast ConcernD1Omnivore5K4Diana4/16/2017StandardE2ForestNorth
A28KikiM2003S16EagleBirdHerdThreatenedD1Herbivore2K4Eva4/16/2017SeniorE2MoatSouth
A29NovaF2003S16IguanaMammalColonyLeast ConcernD1Herbivore6K4Diana4/16/2022JuniorE2MoatEast
A30LunaF2013S18PenguinMammalTroopVulnerableD1Carnivore6K4Alice4/16/2022JuniorE3MoatEast
A31ArloM2016S11TigerMammalSolitaryLeast ConcernD3Carnivore2K3Henry9/8/2010JuniorE4TerrariumEast
A32NalaF2012S3PenguinBirdColonyLeast ConcernD1Carnivore6K1Henry6/18/1964StandardE2Ice PoolNorth
A33TaroF2015S4IguanaMammalSolitaryThreatenedD1Carnivore4K1Frank6/18/1964SeniorE1TerrariumNorth
A34ZuriM2011S4SealMammalSolitaryThreatenedD1Carnivore5K1Henry6/18/1964StandardE1CaveEast
A35NovaF2017S13EagleMammalHerdEndangeredD3Omnivore2K3Frank9/8/2010StandardE3CaveSouth
A36NalaF2018S6EagleMammalColonyEndangeredD2Herbivore5K2Diana1/21/1985JuniorE3Ice PoolNorth
A37SimbaF2013S15PandaMammalColonyVulnerableD1Herbivore6K3Carlos9/8/2013StandardE3TerrariumEast
A38NalaF2000S7EagleReptileHerdEndangeredD3Herbivore6K2Grace1/21/1985JuniorE3ForestEast
A39TaroF2017S8GiraffeReptileTroopLeast ConcernD2Herbivore2K2Grace1/21/1985SeniorE4MoatSouth
A40SimbaM2015S7EagleBirdSolitaryThreatenedD3Carnivore4K2Diana1/21/1985JuniorE3MoatWest
A41NovaF2018S20IguanaMammalPairEndangeredD2Herbivore3K4Bob4/16/2022SeniorE3Ice PoolNorth
A42TaroM2017S6PandaMammalSolitaryEndangeredD2Omnivore2K2Bob1/21/1985JuniorE3CaveSouth
A43MaxF2018S11IguanaReptileSolitaryVulnerableD3Omnivore3K3Henry9/8/2013StandardE4CaveEast
A44ZuriM2013S12IguanaMammalTroopVulnerableD1Herbivore3K3Grace9/8/2013StandardE5MoatEast
A45NovaF2000S16KangarooMammalSolitaryLeast ConcernD1Herbivore4K4Grace4/16/2023SeniorE2Ice PoolSouth
A46MaxF2000(missing)PandaMammalHerdThreatenedD2Omnivore3K2Frank1/21/1985SeniorE4TerrariumNorth
A47ArloM2017S13IguanaMammalHerdVulnerableD3Omnivore3K3Carlos9/8/2014SeniorE3CaveWest
A48NovaF2015S14KangarooMammalColonyEndangeredD2Carnivore4K3Alice9/8/2014JuniorE5TerrariumWest
A49ArloM2018S15KangarooBirdPairThreatenedD1Omnivore3K3Bob9/8/2014JuniorE3CaveEast
A50SimbaM2017S3PandaBirdSolitaryThreatenedD1Carnivore3K1Grace6/18/1964SeniorE2CaveNorth

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 NameData TypeDescriptionValidation
AnimalIDTextUnique IDPrimary Key
NameTextAnimal nameRequired
GenderTextM/FValue check
YearOfArrivalNumberYear animal arrivedRange check
SpeciesIDTextLinks to SpeciesForeign Key, Required
DietIDTextLinks to DietForeign Key
KeeperIDTextLinks to KeepersForeign Key
EnclosureIDTextLinks to EnclosuresForeign 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:

  1. List of keepers sorted alphabetically
  2. Count of animals in each enclosure
  3. Parameter query based on keeper rank
  4. Animals with more than 3 feeds per day
  5. Critically endangered omnivores
  6. Number of animals per location
  7. 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 TypeExampleExpected Result
NormalValid data entryRecord saved
ErroneousMissing SpeciesIDError message
ExtremeVery high year valueRejected

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