Data modelling

    CITY & GUILDS LIMITED
    Vocational

    Data modelling involves understanding basic concepts of logical data modelling and using simple techniques to create logical data models. This includes entities, attributes, and relationships.

    9
    Learning Outcomes
    15
    Assessment Guidance
    15
    Key Skills
    9
    Key Terms
    18
    Assessment Criteria

    Assessment criteria

    City & Guilds Level 2 Diploma in ICT Professional Competence
    City & Guilds Level 3 Diploma in ICT Professional Competence

    Topic Overview

    The City & Guilds Level 2 Diploma in ICT Professional Competence is a vocational qualification designed to equip students with the practical skills and theoretical knowledge needed for a career in ICT. It covers a broad range of topics including hardware, software, networking, cybersecurity, and digital communication. This diploma is ideal for those looking to enter the IT industry at a support or technician level, providing a solid foundation for further study or apprenticeships.

    Students will engage with real-world scenarios, learning how to set up and maintain computer systems, troubleshoot common issues, and understand the principles of data security. The qualification emphasizes hands-on experience, with assessments often based on practical tasks and projects. By the end of the course, learners should be able to demonstrate competence in using ICT tools effectively and safely in a professional environment.

    This diploma fits into the wider subject of Computer Science by bridging the gap between theoretical concepts and practical application. While A-Level Computer Science focuses more on algorithms and programming theory, this vocational route prioritizes employability skills and industry-relevant practices. It is particularly valuable for students who prefer a more applied approach to learning and want to enter the workforce directly after their studies.

    Key Concepts

    Core ideas you must understand for this topic

    • Hardware and Software: Understanding the components of a computer system (CPU, RAM, storage) and the role of operating systems and application software.
    • Networking: Basics of LAN, WAN, IP addressing, and network topologies; setting up and configuring network devices like routers and switches.
    • Cybersecurity: Principles of data protection, common threats (malware, phishing), and security measures such as firewalls and encryption.
    • Digital Communication: Effective use of email, collaborative tools, and professional online etiquette in a business context.
    • Troubleshooting: Systematic approach to diagnosing and resolving hardware, software, and network issues using logical problem-solving.

    Learning Objectives

    What you need to know and understand

    • Know the basic concepts of logical data modelling, Use simple data modelling techniques to create logical data models
    • Apply entity relationship modelling to construct a logical data model from a given business scenario
    • Analyse business requirements to determine appropriate entities, attributes, and relationships
    • Implement normalisation techniques up to third normal form to eliminate data redundancy
    • Evaluate a logical data model against specified user requirements and propose improvements
    • Distinguish between primary keys, foreign keys, and composite keys in a data model
    • Interpret business rules and represent them accurately using cardinality and optionality
    • Understand the concepts of logical data modelling, Use data modelling techniques to create logical data models, Use data modelling techniques to refine logical data models
    • Understand the concepts of logical data modelling, Use data modelling techniques to create logical data models, Use data modelling techniques to refine logical data models

    Assessment Criteria

    Key criteria assessors look for in your portfolio

    • Define key data modelling concepts such as entity, attribute, and relationship.
    • Create a logical data model using appropriate notation.
    • Identify entities and attributes from a given scenario.
    • Define relationships between entities with cardinality.
    • Award credit for correct identification and naming of entities that match the business domain
    • Evidence must include an entity relationship diagram (ERD) with properly labelled relationships and multiplicity (e.g., 1:M, M:M)
    • Candidate demonstrates steps of normalisation from unnormalised form to 3NF with clear justification
    • Primary and foreign keys are correctly assigned and documented in the logical model
    • Attributes are atomic and depend solely on the primary key in each normalised table
    • Clear mapping of business rules to relationship constraints (cardinality and optionality) is evident
    • Award credit for demonstrating identification of entities, attributes, and relationships with clear cardinality and optionality definitions.
    • Award credit for producing a logical data model that conforms to third normal form, evidencing removal of partial and transitive dependencies.
    • Award credit for documenting the refinement process, including rationale for denormalization decisions where performance trade-offs are justified.
    • Award credit for validating the model against user requirements through use of sample queries or data scenarios.
    • Understands concepts of logical data modelling (entities, attributes, relationships).
    • Creates a logical data model using appropriate notation.
    • Refines the model through normalisation or validation.
    • Documents the model clearly for stakeholders.

    Assessment Guidance

    Guidance for achieving higher grades

    • 💡Practice drawing entity-relationship diagrams.
    • 💡Learn standard notation like crow's foot.
    • 💡Understand the purpose of normalisation.
    • 💡Always start by reading the business case carefully to identify all relevant entities before drawing the ERD
    • 💡Use standard notation consistently (e.g., Crow's Foot or UML) as per the qualification specification
    • 💡When normalising, clearly show each normal form with the corresponding table structures and explain the rationale
    • 💡Check your model for redundant relationships or many-to-many relationships that require resolution
    • 💡Practice with varied scenarios to build confidence in translating narrative requirements into accurate logical models
    • 💡When creating a logical data model, always start by identifying core business entities from the given scenario before drawing relationships.
    • 💡Clearly annotate your diagrams with meaningful entity names, attribute lists, and relationship descriptions to demonstrate thorough analysis.
    • 💡In refinement tasks, justify each change with a concrete business reason, such as query performance or data access patterns, rather than generic statements.
    • 💡Practice reverse-engineering models from sample data sets or existing database schemas to strengthen your modelling intuition.
    • 💡Practice drawing entity-relationship diagrams (ERDs).
    • 💡Learn normalisation forms (1NF, 2NF, 3NF).
    • 💡Use consistent naming conventions for entities and attributes.
    • 💡For practical assessments, always follow the instructions carefully and double-check your work. Show your working or reasoning in troubleshooting tasks to demonstrate your thought process.
    • 💡In written exams, use specific terminology (e.g., 'RAM' instead of 'memory') and give examples from real-world scenarios to illustrate your points.
    • 💡Manage your time effectively: allocate more time to higher-mark questions and ensure you attempt all parts of a question, even if you're unsure.

    Common Mistakes

    Common errors to avoid in your coursework

    • Confusing logical and physical data models.
    • Incorrect cardinality notation.
    • Missing attributes or entities.
    • Confusing logical data modelling with physical database design, such as including storage details
    • Incorrectly defining cardinality and optionality, leading to misrepresented business rules
    • Failing to normalise data beyond first normal form, resulting in update anomalies
    • Using vague or generic entity names that do not reflect the specific business context
    • Omitting crucial attributes or including derived attributes without justification
    • Confusing logical data models with physical database design, such as prematurely specifying data types or storage details.
    • Failing to resolve many-to-many relationships during logical modelling, leading to implementation anomalies.
    • Overlooking the impact of business rules on relationship optionality and incorrectly assuming all relationships are mandatory.
    • Applying normalization mechanically without understanding the functional dependencies, resulting in unnecessary decomposition.
    • Confusing logical and physical data models.
    • Missing or incorrect cardinality in relationships.
    • Failing to normalise data properly.
    • Misconception: ICT is just about using computers. Correction: ICT involves understanding how systems work, managing data, and ensuring security, not just basic computer use.
    • Misconception: Networking is only about connecting cables. Correction: Networking includes configuration, protocols, and security; physical cabling is just one small part.
    • Misconception: Cybersecurity is only for IT experts. Correction: Everyone in an organization has a role in cybersecurity, such as using strong passwords and recognizing phishing attempts.

    Frequently Asked Questions

    Common questions students ask about this topic

    Pass / Merit / Distinction Evidence Checklist

    How your portfolio evidence is graded for CITY & GUILDS LIMITED Data modelling

    Every vocational unit is marked against named criteria rather than an exam percentage. Your tutor's brief lists the exact codes for this unit — here is what each band is asking you to do.

    Pass (P)

    Demonstrate baseline knowledge, accurate terminology, and core practical application.

    Merit (M)

    Provide detailed analysis, structured explanations, and clear workplace reasoning.

    Distinction (D)

    Deliver thorough evaluation, original problem solving, and fully justified recommendations.

    Before You Start

    Prior knowledge that will help with this topic

    • Basic digital literacy: ability to use a computer, browse the internet, and manage files.
    • Understanding of simple mathematical concepts like binary numbers and data units (KB, MB, GB).
    • No formal programming experience required, but an interest in how technology works is beneficial.

    Coursework AI Review

    Paste your assignment brief and check your draft against its P/M/D criteria

    Key Terminology

    Essential terms to know

    • Know the basic concepts of logical data modelling, Use simple data modelling techniques to create logical data models
    • Entity relationship diagramming
    • Normalisation and normal forms
    • Attribute and key identification
    • Business rule translation
    • Data integrity constraints
    • Conceptual vs. logical models
    • Understand the concepts of logical data modelling, Use data modelling techniques to create logical data models, Use data modelling techniques to refine logical data models
    • Understand the concepts of logical data modelling, Use data modelling techniques to create logical data models, Use data modelling techniques to refine logical data models

    Ready to learn?

    AI-powered learning tailored to this unit