ICTDBS502: Design A Database

ICTDBS502
DESIGN A DATABASE
ASSESSMENT
This material is developed by Enhance
Your Future Pty Ltd for Australian Institute of Science and Technology (AIST)
ASSESSMENT INFORMATION FOR LEARNERS
Developed by Enhance Your Future Pty Ltd 2

ICTDBS502 - Design a database Version 3
Course Code and Name
Throughout your training we are committed to your learning by providing a training and assessment
framework that ensures the knowledge gained through training is translated into practical on the job
improvements.
You are going to be assessed for:

 Your skills and knowledge using written and observation activities that apply to the
workplace.
 Your ability to apply your learning.
 Your ability to recognise common principles and actively use these on the job.
All of your assessment and training is provided as a positive learning tool. Your assessor will guide
your learning and provide feedback on your responses to the assessment materials until you have
been deemed competent in this unit.
How you will be assessed
The process we follow is known as competency-based assessment. This means that evidence of your
current skills and knowledge will be measured against national standards of best practice, not
against the learning you have undertaken either recently or in the past. Some of the assessment will
be concerned with how you apply your skills and knowledge in the workplace, and some in the
training room as required by each unit.
The assessment tasks have been designed to enable you to demonstrate the requirements of the
performance criteria and knowledge in this unit to successfully demonstrate competency at the
required standard.
Your assessor will ensure that you are ready for assessment and will explain the assessment process.
Your assessment tasks will outline the evidence to be collected and how it will be collected, for
example; a written activity, case study, or demonstration and observation.
The assessor will also have determined if you have any special needs to be considered during
assessment. Changes can be made to the way assessment is undertaken to account for special needs
and this is called making Reasonable Adjustment.
What happens if your result is ‘Not Yet Competent’ for one or more assessment tasks?

Our assessment process is designed to answer the question “has the desired learning outcome been
achieved yet?” If the answer is “Not yet”, then we work with you to see how we can get there.
In the case that one or more of your assessments has been marked ‘NYC’, your trainer will provide
you with the necessary feedback and guidance, in order for you to resubmit your responses.
What if you disagree on the assessment outcome?
You can appeal against a decision made in regards to your assessment. An appeal should only be
made if you have been assessed as ‘Not Yet Competent’ against a specific unit and you feel you have
sufficient grounds to believe that you are entitled to be assessed as competent. You must be able to
adequately demonstrate that you have the skills and experience to be able to meet the requirements
of units you are appealing the assessment of.
Your trainer will outline the appeals process, which is available to the learner. You can request a
form to make an appeal and submit it to your trainer, the course coordinator, or the administration
officer. The RTO will examine the appeal and you will be advised of the outcome within 14 days. Any
additional information you wish to provide may be attached to the appeal form.
What if I believe I am already competent before training?
If you believe you already have the knowledge and skills to be able to demonstrate competence in
this unit, speak with your trainer, as you may be able to apply for Recognition of Prior Learning (RPL).
Assessor Responsibilities
Assessors need to be aware of their responsibilities and carry them out appropriately. To do this
they need to:
 Ensure that participants are assessed fairly based on the outcome of the language,
literacy and numeracy review completed at enrolment.
 Ensure that all documentation is signed by the learner, trainer, workplace supervisor and
assessor when units and certificates are complete, to ensure that there is no follow-up
required from an administration perspective.
 Ensure that their own qualifications are current.
 When required, request the manager or supervisor to determine that the learner is
‘satisfactorily’ demonstrating the requirements for each unit. ‘Satisfactorily’ means
consistently meeting the standard expected from an experienced operator.
 When required, ensure supervisors and learners sign off on third party assessment forms
or third party report.
 Follow the recommendations from moderation and validation meetings.
How should I format my assessments?
Your assessments should be typed in an 11 or 12 size font for ease of reading. You must include a
footer on each page with the learner name, unit code and date. Your assessment needs to be
submitted as a hardcopy or electronic copy as requested by your trainer.
How long should my answers be?
The length of your answers will be guided by the description in each assessment, for example:
Type of Answer Answer Guidelines
Short Answer 4 typed lines = 50 words, or
5 lines of handwritten text
Long Answer 8 typed lines = 100 words, or
1
10 lines of handwritten text = of a foolscap page
3
Brief Report 500 words = 1 page typed report, or
1
50 lines of handwritten text = 1 foolscap handwritten pages
2
Mid Report 1,000 words = 2 page typed report
Long Report 2,000 words = 4 page typed report
How should I reference the sources of information I use in my assessments?
Include a reference list at the end of your work on a separate page. You should reference the sources
you have used in your assessments in the Harvard Style. For example:
 Website Name – Page or Document Name, Retrieved insert the date. Webpage link.
 For a book: Author surname, author initial Year of publication, Title of book, Publisher,
City, State.

ASSESSMENT GUIDE
The following table shows you how to achieve a satisfactory result against the criteria for each type
of assessment task. The following is a list of general assessment methods that can be used in
assessing a unit of competency. Check your assessment tasks to identify the ones used in this unit of
competency.
Assessment Method Satisfactory Result Non-Satisfactory Result
You will receive an overall result of Competent or Not Yet Competent for this unit. The assessment
process is made up of a number of assessment methods. You are required to achieve a satisfactory
result in each of these to be deemed competent overall. Your assessment may include the following
assessment types.
Questions All questions answered Incorrect answers for one or

correctly more questions
Answers address the question Answers do not address the

in full; referring to appropriate question in full. Does not refer
sources from your workbook to appropriate or correct
and/or workplace sources.
Third Party Report Supervisor or manager Could not demonstrate

observes work performance consistency. Could not
and confirms that you demonstrate the ability to
consistently meet the achieve the required standard
standards expected from an
experienced operator
Written Activity The assessor will mark the Does not follow
activity against the detailed guidelines/instructions
guidelines/instructions
Attachments if requested are Requested supplementary

attached items are not attached
All requirements of the Response does not address

written activity are the requirements in full; is
addressed/covered. missing a response for one or
more areas.
Responses must refer to One or more of the

appropriate sources from your requirements are answered
workbook and/or workplace incorrectly.

Assessment Method Satisfactory Result Non-Satisfactory Result
You will receive an overall result of Competent or Not Yet Competent for this unit. The assessment
process is made up of a number of assessment methods. You are required to achieve a satisfactory
result in each of these to be deemed competent overall. Your assessment may include the following
assessment types.
Does not refer to or utilise

appropriate or correct sources
of information
Observation/Demonstration All elements, criteria, Could not demonstrate

knowledge and performance elements, criteria, knowledge
evidence are demonstrated at and performance evidence at
the appropriate AQF level the appropriate AQF level
Case Study All comprehension questions Lack of demonstrated

answered correctly; comprehension of the
demonstrating an application knowledge required to
of knowledge of the topic case complete the case study
study. questions correctly. One or
more questions are answered
incorrectly.
Answers address the question Answers do not address the

in full; referring to appropriate question in full; do not refer to
sources from your workbook appropriate sources.
and/or workplace
Practical Activity All tasks in the practical Tasks have not been
activity must be completed completed effectively and
and evidence of completion evidence of completion has
must be provided to your not been provided.
trainer/assessor.
All tasks have been completed
accurately and evidence
provided for each stated task.
Attachments if requested are Requested supplementary

attached items are not attached

ASSESSMENT COVER SHEET
Assessment Cover Sheet
Learner’s name: MUKHTAR SINGH
Date
Assessors Name:
Submitted:
The following questions are to be completed by the assessor:
Is the Learner ready for assessment? Yes No
Has the assessment process been explained? Yes No
Does the Learner understand which evidence is to be collected

Yes No
and how?
Have the Learner’s rights and the appeal system been fully
Yes No
explained?
Have you discussed any special needs to be considered during

Yes No
assessment?
The following documents must be completed and attached:
 Written Activity and Checklist
The learner will complete the written activity provided to them by S NYS
the assessor. The Written Activity Checklist will be completed by
the assessor.
 Practical Activity Checklist
The learner will demonstrate a range of skills and the assessor will S NYS
observe where appropriate to the unit. The Practical Activity
Checklist will be completed by the assessor.
 Questions and Questions Checklist
The learner will answer a range of questions either verbally or S NYS

written. The Questions Checklist will be completed by the assessor.
Learner Declaration
I agree to undertake assessment in the knowledge that information gathered will only be used for
professional development purposes and can only be accessed by the RTO
I declare that:
 The material I have submitted is my own work

 I have kept a copy of all relevant notes and reference material that I used in the production of
my work
 I have given references for all sources of information that are not my own, including the words,
ideas and images of others
Learner Signature: Date:
Result and Feedback
Feedback to Learner:
Overall Outcome Competent Not yet Competent
Assessor Signature: Date:

WRITTEN ACTIVITY
Your task is to write the answers to each of the following questions. Answers should exceed 50
words but no more than 100 words for each questions:
1. Reflect on the process of data analysis, including its role in determining data types and data
structures, in query and in report design.
Answer
A system is a database of data that has been arranged into a method that makes it easy to
find for, choose, or analyse a bit of data based on specified features that characterize each
quantity of data.
Databases come in a variety of forms, including:
Database packages that are commercially available off-the-shelf (COTS).
Object-relational databases (ORBs)
Exclusive databases
Relational database systems
2. Describe data modelling as it relates to developing a conceptual data model.
Building visual representations of databases is the activity of providing a method of a

database.
The following are examples of conceptual models:
What kind of data items are stored in a database?
How the things are related to one another
What are the rules that govern the data objects?
Conceptual data models have three elements, which are as follows:
Entities, which are real-world objects that may be utilised to populate database fields.
Attributes, which are unique features or characteristics to each entity
Relationships are dependencies or relationships that exist between things.
Conceptual data models depict the contents of a database. Conceptual models are used to
define the scope, organise data, and establish business concepts and procedures.
Designers are the most likely to build conceptual models in collaboration with
stakeholders using user-needs assessments.
3. Explain what data redundancy is, and how it might be identified.

Answer

A database situation that is likely to be produced is data redundancy, in which the
identical piece of data is maintained in two different places. Redundant data is defined as
data that is present in more than one location in a database; as a result, the database is
bigger than it should be. Data redundancy would most likely be discovered during the
normalisation, indexing, searching, and data modelling procedures.
4. Describe the fundamentals of DBMS, particularly as these are applicable during the design
phase.
Answer
The principles of DBMS are as follows:

 Physical databases must be constructed in accordance with the individual DBMS in order
for data to be read and interpreted by the DBMS.
 The database engine would be addressed throughout the database design process to
guarantee that data can be accessed appropriately to use queries and be changed as
needed by the user.
A database scheme is a framework of database and data that must be completed in
accordance with the needs of the DBMS used to guarantee two things are compatible
with each other.
5. What is encryption and authentication, and how do these apply to database security
features?
Answer
Database encryption is the process of applying algorithms to data transmitted and

received from a database in order for it to be turned into cypher and encoded text in
order to prevent hackers from understanding it if it is intercepted. The various encryption
options are to be adjusted based on the kind of stored data and the security plan
requirements that apply to the organisation.
Authentication is the process of guaranteeing that only authorised parties who are
authorised to execute specific approved actions in the database may access the database.
6. Explain the functions and the features of data types and data structures.
Answer
Understanding the roles and characteristics of data types and data structures aids in the
creation of a functional database. Data structure allows data to be arranged in tables
according to the kind of database and would have specified properties and IDs to organise
data in a database so that queries and searches can be performed.

The data types are determined in order to create a database that meets the criteria of the
data kinds. The role of different data types is to guarantee that data may be sequenced
and organised in order for information to be received and used as needed.
7. Describe the features and the functions of databases.

Answer
Databases not only allow complicated data to be kept in a searchable, organised, and
usable manner, but they also allow an organization's data to be managed in a structured,
reportable, and queryable manner.
Databases allow data to be provided to ensure that queries are answered and that
information is displayed to users via a user interface in a variety of ways. Databases allow
data to be stored in a secure location in accordance with the organization's security policy,
as well as allowing users to add, delete, and update data. Databases handle information
according to business needs and provide various searching and indexing functions.
8. Describe the concepts of logical design, particularly as they relate to designing data
structures, queries screens and reports.
Answer
The process of developing many associations among diverse data structures, which are
likely to be based on the manner in which they are logically related to each other through
business processes or needs, is defined as logical database design. The fundamentals of
logical design include grouping data into entities, relationships, and attributes. Logical
design is important for the development of data structures, queries, screens, and reports,
and it can be used to lay out data and make decisions about how it should be used.
9. Explain the concepts of object model design, particularly as they relate to the design of data
structures, queries, screens and reports.
Answer
Object-oriented programming is a paradigm centred on the management of objects that

include data in the form of attributes and code. After that, variables might be used to
define how objects relate to and communicate with one another. In order to use class
variables, class-based object-oriented programming languages must be controlled. The
data should be categorised into the object group and behaviours when using these
principles to construct data structures, queries, displays, and reports. The data is
organised according to the rules, allowing for object-oriented programming language
queries, screens, and reports.
10. In relation to databases, explain the term ‘scalability’.

Answer
The ability of something to change size in response to demand is referred to as scalability.

Database administration requires a high level of scalability, which can be achieved in a
variety of methods. Set size databases, automatically scalable databases, partitions,
vertical or horizontal scaling, and the utilisation of distributed computers or servers are all
ways to manage and regulate database scalability.

WRITTEN ACTIVITY CHECKLIST
Written Activity Checklist
For this assessment, the learner must complete the written activity.
The written activity is a stand-alone activity that will allow the learner to display the requirements
of the performance criteria and knowledge evidence in this unit that are essential when deciding
overall competency.
Learner Name: MUKHTAR SINGH
Assessor Name:
Has the learner satisfactorily

completed the written activity?
Yes No
Did the Learner provide evidence of their ability to:
Reflect on the process of data analysis, including its role in

determining data types and data structures, in query and in  
report design.
Describe data modelling as it relates to developing a conceptual

 
data model.
Explain what data redundancy is, and how it might be

 
identified.
Describe the fundamentals of DBMS, particularly as these are

 
applicable during the design phase.
What is encryption and authentication, and how do these apply

 
to database security features?
Explain the functions and the features of data types and data
 
structures.
Describe the features and the functions of databases.  
Describe the concepts of logical design, particularly as they

 
relate to designing data structures, queries screens and reports.
Explain the concepts of object model design, particularly as they  

relate to the design of data structures, queries, screens and

reports.
In relation to databases, explain the term ‘scalability’.  
Result  Satisfactory  Not Yet Satisfactory
Assessor’s Signature: Date:

PRACTICAL ACTIVITY
The following task is to be demonstrated and assessed in conditions that are safe and replicate the
workplace. Noise levels, production flow, interruptions and time variances must be typical of those
experienced in the database field of work, and include access to:
 Equipment and materials

 Current industry accepted database software
 Network or other system for remote or multi-user access
 Business requirements
 Computer-aided software engineering (CASE) or diagramming software
For this task you are to complete the following activity to demonstrate your ability to design a
database.
Prepare for the task by completing the following actions to determine the database requirements:
1. Meet with the client, and conduct a user-needs analysis to determine database functionality.
Provide the documented user-needs analysis.
2. Analyse the results of the user-needs analysis to identify the technical requirements. Record
this analysis, including the technical requirements.
3. Develop a conceptual model of the database, and submit this to the client for review.
4. Evaluate the client feedback on the conceptual model, making changes as required.
Document this evaluation, and record any changes made.
Develop a logical data model through completion of the following steps:
5. Identify the attributes and determine the data types.

6. Undertake the normalisation of attributes.
7. In order to clarify the cardinality of relationships, develop an entity-relationship (ER)
diagram.
8. Accurately document the attributes, normalised data, and the ER diagram, and forward this
documentation to the client for confirmation. Provide evidence of the client confirmation.
Complete the following actions to design the data structures:
9. Confirm, and record, the primary and foreign keys for the tables.
10. Review and record the client business rules.
11. Identify, and document, the referential integrity constraints.

12. Establish, and document, the database management system constraints, and incorporate
these into the database design.
13. Develop, and document, the validation rules for data.
14. Design the indexes and develop the data dictionary.
15. Accurately document the database design.
Design the queries, screens and reports through completion of the following steps:
16. Design and document the user interface for the database, including the menus, input screens
and outputs.
17. Based on the requirements, design, and document, the queries and the output reports.
18. Compare the physical design with the conceptual model, or with the user-needs analysis, and
incorporate changes, as required. Document this comparison, noting any changes
incorporated.
Perform the following actions to design the access and security systems:
19. Review the business security plan as a basis for commencing the access and security design.
Document this review.
20. Design and document the password and access system for the database.
21. Identify, and record, multiple-user requirements.
22. Using the client business model, develop the client access profiles.
Confirm the database design with the client through the following actions:
23. Identify the requirements for database backup and recovery. Record these requirements.
24. Develop, and document, the procedures for database backup and restoration.
25. Submit the database, and documentation, to the client for their final approval. Provide the
final approval obtained.
Design a database
Determination of the database requirements
The client is met, and user-needs analysis is to be conducted in order to determine database
functionality:
A database is a collection of data organised in a structured system that allows pieces of data to
be identified, selected, and analysed based on predetermined attributes of each item of data.
In order to determine what database functionality is required, personnel and administrators
must meet with customers and conduct a user-needs analysis to determine the best manner
to obtain information from clients. Commercial off-the-shelf (COTS) database packages,
object-relational databases, proprietary databases, and relational databases are all popular
databases.
A user-needs analysis would assist in determining what components and functionality are
necessary to be incorporated in the design of a database in order to meet the demands of the

customer. After identifying the client's demands, information may be analysed by interpreting
each need as a function or design feature of the proposed database.
The results of the user-needs analysis must be analysed in order to determine the technical:
The information gleaned from the user-needs analysis would be used to identify technical
requirements, which are described as the elements that must be present in sequence for the
database to work in accordance with the client's expectations. A user-needs analysis is also
anticipated to reveal what technological requirements exist based on the designer's
understanding of database design and architecture, as well as information gathered during the
user-needs analysis. Following that, connections are created between technical elements of
database design and development and needs.
A user-needs analysis had to be performed, and it was discovered that the client wants a
database to hold details connected to mail orders to an online retail business, as well as all
necessary information about the clients, the product that they have bought, and shipping
information. Internal workers and external vendors will have access to the database. In this
situation, the designer is responsible for determining the ensuing technical needs.
• Amount of storage space required,
• What level of security is to be provided to external parties and organisational departments?
• The size of the data to be split into,
• Whether or not several languages are required in database architecture,
• What is the connection between data groupings and their users and uses?
A database conceptual model must be created and delivered to the
customer for approval:
Database conceptual model: The conceptual model would be developed in collaboration with
stakeholders through user-needs study. It is to be the initial model in the entire data
modelling process, and it will be used to build physical data models and answer questions
about what will go into the database, and the information will be used to define how the
information will be integrated into a full DBMS.
Submitting the conceptual database to the customer for evaluation and model review:
The conceptual database model will be given to the customer for evaluation to ensure that
the data and the method in which the data is structured is compatible with the client's
demands and needs. In conclusion, the conceptual model is being given to the customer, the
client wants revisions, and further explanation is required. After making changes, the revised
model is submitted for additional evaluation. This procedure would be continued until the
customer agreed to the conceptual model.
The customer input on the conceptual model is to be analysed in order to make
modifications as needed, and this evaluation is to be documented, as are the alterations:
Feedback evaluation:
A model is to be given to a client. The client provides feedback. Following that, necessary steps
are made to address the comments. The process of assessing feedback takes into account how
the feedback relates to the conceptual model, which allows to depict what data would be
included in the database but does not completely explain how the data would be handled.
Effective communication would be necessary to avoid errors that would have a detrimental
impact on the database's outputs as well as harm to the client-designer relationship.
Making modifications to the conceptual model:
Changes to the conceptual model would be required. Adjustments and modifications are
made to the definition of entities, relationships between entities, metadata, and data being
deleted or added to the model based on the review findings, and the model is eventually
presented to the customer for approval.
 Creation of a logical data model
The characteristics must be determined, as well as the data types.
Identifying the type of data:
Before identifying characteristics, it is necessary to understand the function and features of
various data types, as well as the data structure, which is the method in which data is
constructed. Following that, qualities that are database components such as a table, a column
or row in a table, and a field would be identified in order to use this information to help build
the database's data structures.
Identifying the data type:
In order to build a database that meets the demands, a variety of data types that must be
included in the design would be selected. Numeric, date and time, character and string,
Unicode character string, binary data, and other data types are all possible. The function of a
datatype is to guarantee that data is sequenced and organised in a way that permits
information to be accessed and used when needed.
 The following characteristics will be normalised:

Taking on attribute normalisation:
Before beginning attribute normalisation, the meaning of attribute normalisation would be
known. The practise of organising attributes to guarantee consistency of entity type and
connection based on these entity types is known as attribute normalisation. Attribute
normalisation will be carried out in order to ensure the functionality and integrity of the
database design. Data redundancy might be reduced by attribute normalisation. To maintain
consistency and integrity, a set of rules would be considered to be implemented during the
attribute normalisation process.
Recording data normalisation rules:

Data normalisation rules would be documented, as well as ensuring that all attributes are
successfully normalised for a compliant and error-free database structure that can be queried
effectively.
 To clarify the cardinality of relationships, an entity-relationship (ER) diagram has to be

created:
Model of entity relationships:
A database entity-relationship model is a diagram that is used to establish relationships. The
following data elements might be explained using an ER diagram:
The ER diagram would look like as below:

 The cardinality of relationships:
Cardinality of relationship is to be rated and explained through a number of entities that
would be included in the data, and high cardinality would contain a large number of unique
entities that would be identified by considering the following relation types: Many-to-many,
Many-to-one, One-to-many, and One-to-one, as shown below.
 The characteristics, normalised data, and the ER diagram must be correctly recorded, and
this documentation must be sent to the client for validation, as well as evidence of client
confirmation:
Data documentation:
According to organisational standards, all database characteristics, normalised data, and the
ER diagram would be recorded. Attributes must be recorded so that they may be used in
decision making. To convey normalised data, normalised data would be described using a
single business modelling language. The ER diagram would be written using the agreed-upon
ER rules and format, as well as establishing the cardinality of information.
Forwarding documentation to client for confirmation:
Once completed, documentation would be checked and assessed to ensure that it is correct
and that all required information is effectively contained in documentation in accordance with
documentation standards before being submitted to the client for confirmation. Finally, after
verifying that all documentation adheres to standards, the material would be given to the
customer for confirmation via an agreed-upon mechanism to guarantee that documentation
may be evaluated. During this step, the client receives documentation, confirms the database
architecture, and approves the next stage of development.
 Designing data structures

The following primary and foreign keys must be confirmed and documented for the tables:
Prior to validating the keys, the terms primary key and foreign key should be recognised

because they are table attributes that are used to uniquely identify the data. Once the
meanings of both keys have been determined, they must be confirmed for the tables. Various
approaches for data structure would be evaluated, as well as those that have the potential to
be employed, in order to validate which main and foreign keys are necessary to be used. The
primary key and foreign keys must then be registered in the database management system.
Foreign key in database management system;
The following client business rules must be evaluated and documented:

The client's business rules that would be applied to the database design will be examined. A
client business rule is a statement that applies a constraint to a specific component of the
database being created. This client business rule would apply to components that are allowed
in a certain field, field definition criteria, and relationship attributes. All business rules
provided by the customer would be evaluated before being recorded in the database to verify
that suitable database architecture decisions were made. Finally, the client's business rules
would be stored in a database management system (DBMS).
The following seems to be an example of a common commercial contract:
For any given order, a SHIP DATE cannot be earlier than an Appointment Time.
This enterprise rule sets a limitation on the Limit of Values aspect of a SHIP DATE field's field
specifications. It will assist in ensuring that the value of SHIP DATE is relevant in the context
of a sales invoice. Without this restriction, you may enter any date (including one previous
to the ORDER DATE), rendering the SHIP DATE field's value completely useless. The business
policy is what makes the value of the SHIP DATE column contextually relevant.
The following referential integrity restrictions must be recognised and documented:

Referential integrity would have to be understood before identifying the referential integrity
limitations, and then the referential integrity constraints would have to be grasped.
Referential integrity is a criterion for maintaining consistency in relationships. Referential
integrity constraints are limits imposed on the way entities are defined. All needed
relationships, as well as interactions, would be evaluated to verify that referential integrity
restrictions are recognised. Following the identification of the constraints, all referential
integrity constraints would be documented in the system.
The database management system restrictions must be defined and documented before
they can be integrated into the database design:
Database management system basics would be specified during the design phase in order to
create the database management system limitations and incorporate them into database
architecture. DBMS is made up of three components: the actual database, the database
engine, and the database scheme.
To guarantee that data can be viewed and comprehended by the DBMS, the physiological
database would've been constructed in accordance with the specific DBMS.
To guarantee that data can be viewed and comprehended by the DBMS, the physiological
database would've been constructed in accordance with the specific DBMS.
The database scheme, which is a database structure and the data included in the structures,
would be necessary to ensure that they are finished in accordance with the demands of DBMS
so that two things may be assured to be compatible with each other.
The following actions would be performed by DBMS: generating database data, reading
database data, updating or deleting database data, managing data, and displaying data. DBMS
restrictions are any limits imposed on database administration as a result of DBMS, such as
features.
functions, applications, and permissible acts
These DBMS restrictions would be recognised and managed throughout the design process;
nevertheless, a catastrophic scenario would compel us to pick a different DBMS.
Data validation rules must be created and documented:
Validation rules would be defined and published when the DBMS was established. The
validation rules would consist of object, field, and case milestones that would be used to test
and validate that data satisfies important criteria. Validation would be established and
implemented for all instances when forms are used to enter data into the database to
ensure that information saved to the database by users meets the business rules and can be
kept and utilised appropriately in the database. Finally, the validation rules would be written
down.
The indexes must be designed, and the data dictionary must be created:
Designing database indexes: Database indexes would be used to increase the speed of data
retrieval operations; hence, indexes would be built to allow search algorithms to be applied
to index tables. Indexes would generate parameters that might be used in searches. Indexes
would utilise unique IDs as keys to apply classifications to the data. Indexes would be
organised logically to satisfy the client's use requirements.
Creating the data dictionary:
A data dictionary, which is a document, would be created and used to specify the parts of
the data, allowing data stored in the database to be recognised and classified. A data
dictionary would have metadata, a table, a description, a name, and relationships.
The database design must be documented as follows:
Different sorts of information would be deemed to be recorded, as well as the techniques
employed to do this. Design parameters documentation, relationship and data modelling,
data structure diagrams, definitions and rules, reports on functionality, specifications sheets,
and user manuals are all examples of documentation. Documentation would adhere to
organisational standards such as format, layout, degree of detail, version control, style
guides, and design guidelines.
 Design of queries, displays, and reports
The database user interface, comprising menus, input screens, and outputs, must be
developed and documented:
The user interface would be created by taking into account the following interface elements:
input controls, navigational components, informative components, and containers. Menus
would be built logically while developing the user interface to make it easy to go to different
areas of functionality and control. Furthermore, input panels would be set to guarantee that
users may enter questions, requests, and instructions to get the required results.
Furthermore, output for user interface would be evaluated to satisfy the unique user demands
of the organisation, including kind of output, format, and visual display requirements. All best
practise components would be incorporated into interface design.
 The queries and output reports must be created and documented in accordance with the
following requirements:
Creating Queries Based on Specifications:
Queries would be created to collect information from the database based on the client's
needs. Queries would be written in accordance with the programming language and database
type. They would be determined by the data structure, type, and other criteria used
throughout the design and construction phases. Queries would be made capable of meeting
functionality requirements depending on the requirements. SQL SELECT would be used to get
data from the database, where a statement would be chosen in SQL to allow the queries
required to gather data from the database and display it on the user interface.
Example of a SELECT Column
The following SQL query pulls the columns "CustomerName" and "City" from the
"Customers" table:
SELECT CustomerName, City FROM Customers as an example;

The query selection would be customised using parameters and would be formatted as
follows:
Creating an output report based on the requirements:

Output reports would be developed depending on the needs specific to the database and the
context of its implementation within the organisation. Output reports would be developed so
that users may request reports containing the information needed to fulfil the relevant work
functions. Designing reports would need us to consider what sorts of reports would be
required, how they would be organised and requested, as well as the report output format
and location, and to guarantee that reports were based on logical design.
 The physical design should be compared to the conceptual model or the user-needs study,
and modifications should be implemented as needed. This comparison must be
documented, as well as any modifications made:
Comparing the physical design to the conceptual model and conducting a user-needs
assessment:
The physical design of the database, comprising tangible components such as data type, data
structures, user interface, queries, reports, and functions, would be compared to the
conceptual model to verify compliance with client expectations. Physical design would be
evaluated to user-need analysis to ensure that it is in accordance with the stated user needs.
Physical design components created in response to the construction of a conceptual model or
a user needs study would be evaluated so that similarities and differences with the applicable
requirements could be found.
Incorporating change as needed:

Modifications would be included after a comparison if there were any discrepancies between
the conceptual model or user needs analysis information by identifying them and preparing
changes and undertaking as a consequence. Changes would be found throughout the
identification process by comparing physical database design to conceptual design and user-
needs research. Following that, planning would be done to make adjustments to the physical
model to make it more client-friendly. It would be decided how and what modifications would
be made.
Completing changes in a controlled way:

Changes to the physical database would be performed in a controlled manner, using suitable
version control and change management procedures to guarantee work could be rolled back if
required. All modifications would be monitored, recorded, and documented, along with the
physical model with the changes integrated.
 Creating an access and security system

The company security plan must be examined before beginning the access and security
design. This review will be documented as follows:
The business security plan would be examined as a basis for the access and security design to
begin. The security strategy that relates to the protection of the organization's ICT assets
would be accessible and evaluated to ensure that all of its demands could be recognised and
included into the planning process. These security plans would include authentication,
authorization, and integrity, as well as the organization's privacy and security objectives. The
access design would adhere to the parameters governing who may access data types and
execute certain activities in the database. It would safeguard the security of various ICT and
security technologies and procedures.
Along with the review, the security design would be defined to guarantee that the review is
saved in the database, when it is accessed, and when it is transmitted and produced.
The database's password and access mechanism must be created and documented:
Passwords and access systems, a form of access and authorization system, would be used to
guarantee that only authorised and authenticated users may access the system. User profiles,
authorization and authentication processes, and needs would be established in order to create
a password and access system, and passwords would be developed to fulfil the security plan
criteria.
These passwords and access systems would be recorded, as would the process for creating
passwords and access systems.
Multiple-user needs must be recognised and documented:

Multiple-user needs would be determined and used to plan the access and password system
architecture needed to secure the database from unauthorised access and activity. As a result,
multiple-user requirements would be created in order for user profiles with the necessary
authorization to be built and implemented. The many criteria include the type of data users
can view, the queries they can run, the reports they can access, adding information to the
database, deleting information from the database, and modifying information kept in the
database.
The various user needs would be determined and documented to ensure that the information
is used to create client access profiles as needed.
The client business model will be used to build the client access profiles:
Client access profiles would be created for each of the many sorts of people in the
organisation utilising the client business model. These accounts would have various rights and
authorities assigned to them in order to secure data protection as per the demands of the
organization's security strategy. User accounts would be classified based on their access
needs, permissions, and authority.
 Database design confirmation with the customer
The following needs must be recognised and documented for database backup and
recovery:
Access to and evaluation of a variety of information, including security plans, disaster recovery
plans, organisational rules and procedures, and compliance plans, will identify backup and
recovery requirements. Database backup and recovery needs would be documented and
evaluated to ensure that backup and recovery requirements could be recognised.
 Database backup and restore processes must be designed and documented:

Database backup and restoration processes would be created in accordance with the
organization's needs, taking into account the following factors: kind of backup, frequency of
backup, who will perform the backup?, and how will the backups be accomplished., the
placement of backups, the creation of recovery points, and the location of recovery data
storage.
Then, backup and recovery processes would be defined, which would contain clear and
precise, extensive and complete, and suitably timed criteria.
 The database and supporting documents must be delivered to the customer for final
approval. The following information must be given after final permission has been
obtained:
The database and documentation would be presented for approval as an application and fully
functional and installed item, with all essential access information supplied to access and
approve the database. Design papers, user instructions, assistance manuals, specs sheets, and
process maps are examples of such documents.
Once the database and database documentation have been delivered to the customer, time
will be set aside for the client to examine the database and documentation before final
approval on the finished project is acquired in accordance with organisational processes.

PRACTICAL ACTIVITY CHECKLIST
*Multiple copies of the checklist will need to be printed if the activity is to be performed more than
once.
Practical Activity Checklist
For this assessment, the learner must complete the practical activity.
The practical activity is a stand-alone activity that will allow the learner to display the knowledge
and performance evidence that is essential when deciding overall competency.
Learner Name: MUKHTAR SINGH
Assessor Name:
Has the learner satisfactorily

completed the practical
activity?
Yes No
Did the Learner provide evidence of their ability to:
Meet with the client, and conduct a user-needs analysis to

determine database functionality. Provide the documented  
user-needs analysis.
Analyse the results of the user-needs analysis to identify the

technical requirements. Record this analysis, including the  
technical requirements.
Develop a conceptual model of the database, and submit this to

 
the client for review.
Evaluate the client feedback on the conceptual model, making

changes as required. Document this evaluation, and record any  
changes made.
Identify the attributes and determine the data types.  
Undertake the normalisation of attributes.  
In order to clarify the cardinality of relationships, develop an

 
entity-relationship (ER) diagram.
Accurately document the attributes, normalised data, and the  

ER diagram, and forward this documentation to the client for
confirmation. Provide evidence of the client confirmation.
Confirm, and record, the primary and foreign keys for the
 
tables.
Review and record the client business rules.  
Identify, and document, the referential integrity constraints.  
Establish, and document, the database management system

 
constraints, and incorporate these into the database design.
Develop, and document, the validation rules for data.  
Design the indexes and develop the data dictionary.  
Accurately document the database design.  
Design and document the user interface for the database,

 
including the menus, input screens and outputs.
Based on the requirements, design, and document, the queries

 
and the output reports.
Compare the physical design with the conceptual model, or

with the user-needs analysis, and incorporate changes, as
 
required. Document this comparison, noting any changes
incorporated.
Review the business security plan as a basis for commencing

 
the access and security design. Document this review.
Design and document the password and access system for the
 
database.
Identify, and record, multiple-user requirements.  
Using the client business model, develop the client access

 
profiles.
Identify the requirements for database backup and recovery.

 
Record these requirements.
Develop, and document, the procedures for database backup

 
and restoration.

Submit the database, and documentation, to the client for their
 
final approval. Provide the final approval obtained.

QUESTIONS
The following questions may be answered verbally with your assessor or you may write down your
answers. Please discuss this with your assessor before you commence. Short Answers are required
which is approximately 4 typed lines = 50 words, or 5 lines of handwritten text.
Your assessor will take down dot points as a minimum if you choose to answer them verbally.
Answer the following questions either verbally with your assessor or in writing.
1. Reflect on conducting a user-needs analysis with a client to determine database

functionality.
Answer
User-needs analysis is the process of determining what design features and

functionality must be accessible from a design standpoint, depending on the specified
client's requirements. To determine the customer's needs, several techniques and
approaches like as interviews or client documentation will be used.
2. List five (5) examples of technical requirements you might identify by analysing the
results of the user-needs analysis.
Answer
The amount of memory capacity needed for the database

The type of security should be incorporated for various parties
How short the knowledge should be broken down.
Whether or not various languages will be required in data modelling.
What are the links between data groupings in terms of their users and uses?
3. What is a conceptual model of a database?

Answer
Creating a conceptual model of a database is a step in the process of creating a visual

representation of a database. The conceptual models primarily illustrate what data
items are contained in a database, how the objects relate to one another, and what
rules govern the data objects.
4. Discuss the basic components of reviewing a conceptual model with a client.

Answer
These elements are as follows:

Reviews would be performed either in person or remotely.
What is intended to be included in the evaluation should be determined prior to the
start of the review process.
Who will be involved in the review process will be determined by the size, scope, and
stage of the review process.
5. What types of changes might be made in response to evaluated client feedback?

Answer
Following customer input, modifications will be made to the definition of entities,

relationships between entities, metadata, and data to be deleted and added to the
model.
6. What is the normalisation of attributes?

Answer
Attributes normalisation is the process of organising attributes in order to guarantee

that entity types are consistent, as well as that any connections based on these are
consistent, with the goal of reducing data redundancy.
7. What are the relationship types you might clarify through developing an ER diagram?
Answer
The following relationship types would be clarified by creating an ER diagram:

The first form of relationship is many-to-many.
The second form of relationship is many-to-one.
The third and fourth relationship kinds are one-to-many and one-to-one, respectively.
8. What should you consider and apply when documenting the attributes, normalised data,
and the ER diagram?
Answer
All characteristics should be recorded so that they may be utilised to make important
judgments. Data that has been normalised would be documented in an uniform
business modelling language.
During the documentation of an ER diagram, duplicate entities should be removed
while also ensuring that entities are labelled and that colour is utilised to emphasise
the relevant sections.

9. Why is it important to forward the documentation to the client for their confirmation?
Answer
Following the completion of documentation design, it is critical to send the

documentation to the customer for validation that the design is as intended and
expected. It will also be necessary to ensure that the database design has been
authorised for the next stage of development.
10. Explain primary and foreign keys.

Answer
The first key is the main key, which is used to identify data in the database and must
be one of the record qualities that will be used as a suitable unique key for each
record. A foreign key relates the main key of one object to an attribute in another.
11. When taking about databases, what are client business rules?
Answer
Client business rules are statements that apply a constraint to certain parts of the to-
be-designed database. They may be created for any component of a database and
applied to elements that can be entered into a certain field, field definition criteria,
and relationship characteristics.
12. Explain what referential integrity constraints are.

Answer
Referential integrity constraints are likely to be the constraints that are applied to the
way entities are specified to guarantee they are always in agreement and consistent.
All relationship needs and interactions must be evaluated to ensure that relevant
referential restrictions can be established.
13. What are database management system constraints?

Answer
Database management system constraints are any restrictions imposed on database

administration as a result of DBMS features, functions, applications, and allowed
activities. Identifying applicable constraints is assured in order for them to be
managed throughout the design process; nevertheless, in some situations, a new
database management system is used.
14. Discuss developing validation rules for the data.

Answer
To prevent useless or incorrectly structured data from being put into a database,
validation rules are created. These rules are described as the rules to be used to check
and confirm that data satisfies the fundamental criteria. Where forms are used to
enter data into a database, validation rules are produced and implemented.
15. What are indexes?

Answer
Database indexes, a type of data structure that may be used to speed up data retrieval
procedures necessary for database use, allow search functions to be applied to index
tables and will employ unique identifiers such as keys to apply categories to the data.
16. What information would you include in the data dictionary developed?
Answer
The data dictionary is to be created as a document used to describe data elements in

order to guarantee data can be recognised and classified, and it is likely to contain
information such as metadata, table, description, name, and relationship of each data
component.
17. What information should be included when documenting the database design? List at
least five (5) examples
Answer
The following information should be included when documenting the database design:
design parameter documentation, relationship and fata modelling, data structure
diagrams, definitions and rules, reports on functionality, requirements sheets, and
user manuals. To do this, several types of information and relevant approaches are
being examined.
18. What will need to be included when designing the user interface for database?
Answer
Keeping the interface simple, creating consistency and using common UI elements,
being purposeful in page layout, using colour and texture strategically, applying
typography to form hierarchy and clarity, ensuring system converses what's
happening, and thinking about the defaults are all practise elements considered when
designing a user interface for a database.
19. List five (5) examples of the areas of requirements you might need to consider when
designing queries.
Answer
During the query design process, the following needs are deemed to be satisfied for
functionality based on the specified requirements: application, business, database,
network, people in the organisation, platform, system, programming language, and
database type.
20. What are the typical requirements you will base and design your output reports on?
Answer
Typical criteria for developing output reports include: what report kinds will be
required, how the report will be constructed as well as requested, and report output
format and placement. The report should be organised logically.
21. Why is it necessary to compare the physical design with the conceptual model, or with
the user-needs analysis?
Answer
In order to analyse the physical design elements that have been produced in response
to the conceptual model's development or the user needs analysis's development,
necessary comparisons must be made so that similarities and differences with the
applicable requirements may be found.
22. Briefly reflect on the process for incorporating changes into the database.
Answer
Modifications to the physical model are planned to make them comply with client
demands after identifying needed changes by comparing physical database design
with conceptual design and user needs analysis. Finally, modifications are made in a
controlled way, and changes are monitored and logged using suitable version control
and change management approaches.
23. What types of information will you identify when reviewing the business security plan as
a basis for commencing the access and security design?
Answer
A security plan is a component of every organisation that outlines the standards and
methods to be used in the security of an organization's ICT assets. The security
strategy must include information such as authentication, authorization, and integrity,
as well as the organization's privacy and security objectives.

24. What information would you need to identify in order to design a password and access
system for the database?
Answer
To design a password and access system: an access and authorization system that
ensures only authorised users can access the system, the following information must
be identified, such as the user's profile and permissions, as well as authentication
procedures and requirements; however, passwords that meet the security plan
requirements should be developed.
25. Outline three (3) examples of the types of multiple-user requirements you might
identify.
Answer
The sorts of data they can view, queries they can perform, reports they can access,
adding and deleting information from the database, and changing information stored
in the database are all examples of multiple-user needs. Multiple-user requirements
are established in order for user profiles to be generated and implemented with the
necessary permissions.
26. What information is it essential to consider and use to develop client access profiles?
Answer
In order to generate client access profiles, it is probable that all of the various multiple
user needs must be recognised and recorded; therefore, identified information may
be used to develop client access profiles as needed. User accounts are organised into
groups based on their access needs, permissions, and authority.
27. What are four (4) of the types of information you would assess to identify the database
backup and recovery requirements?
Answer
Database backup and recovery needs are likely to be determined by the access and
assessment of diverse information, such as security plans, disaster recovery plans,
organisational rules and processes, and compliance plans. These papers should be
evaluated to ensure that backup and recovery requirements can be determined.
28. What do you need to ensure about the procedure documentation developed for the
database backup and restoration?
Answer
Following the creation of each and every necessity for backup and recovery processes,

the procedures must be documented, and the documentation procedure must be
clear and explicit. They should be thorough and all-inclusive. It is suggested that they
be arranged in the correct order.
29. What evidence should you obtain for client final approval of the submitted database and
documentation?
Answer
It would be necessary to get design papers and user instructions for final client
approval of database documentation. It is necessary to get not just assistance manuals
but also specs papers. Maps of the processes are also provided.

QUESTIONS CHECKLIST
Questioning Checklist
The assessor needs to indicate whether they have conducted the questioning as written questions
or as verbal questions by ticking the box below.
 Written Questioning  Verbal Questioning
The assessor must provide evidence with the assessment tool. For written questions, the assessor
must provide the learner’s original written responses. For verbal questioning, the assessor must
provide dot points as a minimum on the learner’s responses.
For details on how to conduct and contextualise this form of assessment, please refer to the
questioning checklist explanation in the assessor guide.
Learner’s name: MUKHTAR SINGH
Assessor’s name:
Satisfactory
If questions are answered verbally, the assessor must write detailed notes
response
on the learners responses. If answers are recorded separate to this
document, they must be attached to the assessment documents. Yes No
Reflect on conducting a user-needs analysis with a client to determine

1 database functionality.  
List five (5) examples of technical requirements you might identify by

2 analysing the results of the user-needs analysis.  
What is a conceptual model of a database?

3  
Discuss the basic components of reviewing a conceptual model with a

4 client.  
What types of changes might be made in response to evaluated client

5 feedback?  
What is the normalisation of attributes?

6  

What are the relationship types you might clarify through developing
7 an ER diagram?  
What should you consider and apply when documenting the

8 attributes, normalised data, and the ER diagram?  
Why is it important to forward the documentation to the client for

9 their confirmation?  
Explain primary and foreign keys.

10  
When taking about databases, what are client business rules?

11  
Explain what referential integrity constraints are.

12  
What are database management system constraints?

13  
Discuss developing validation rules for the data.

14  
What are indexes?

15  
What information would you include in the data dictionary

16 developed?  
What information should be included when documenting the

17 database design? List at least five (5) examples  
What will need to be included when designing the user interface for
18 database?  

List five (5) examples of the areas of requirements you might need to
19 consider when designing queries.  
What are the typical requirements you will base and design your
20 output reports on?  
Why is it necessary to compare the physical design with the

21 conceptual model, or with the user-needs analysis?  
Briefly reflect on the process for incorporating changes into the

22 database.  
What types of information will you identify when reviewing the

23 business security plan as a basis for commencing the access and  
security design?
What information would you need to identify in order to design a

24 password and access system for the database?  
Outline three (3) examples of the types of multiple-user requirements

25 you might identify.  
What information is it essential to consider and use to develop client

26 access profiles?  
What are four (4) of the types of information you would assess to
27 identify the database backup and recovery requirements?  
What do you need to ensure about the procedure documentation

28 developed for the database backup and restoration?  
What evidence should you obtain for client final approval of the
29 submitted database and documentation?  



ICTDBS502: Design A Database

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ICTDBS502: Design A Database

Uploaded by

Copyright:

Available Formats

ICTDBS502

ASSESSMENT INFORMATION FOR LEARNERS

Developed by Enhance Your Future Pty Ltd 2

You are going to be assessed for:

How you will be assessed

Developed by Enhance Your Future Pty Ltd 3

What if you disagree on the assessment outcome?

What if I believe I am already competent before training?

How should I format my assessments?

How long should my answers be?

Type of Answer Answer Guidelines

Short Answer 4 typed lines = 50 words, or

5 lines of handwritten text

Long Answer 8 typed lines = 100 words, or

100 lines of handwritten text = 3 foolscap handwritten pages

Long Report 2,000 words = 4 page typed report

200 lines of handwritten text = 6 foolscap handwritten pages

How should I reference the sources of information I use in my assessments?

Developed by Enhance Your Future Pty Ltd 5

Assessment Method Satisfactory Result Non-Satisfactory Result

Questions All questions answered Incorrect answers for one or

Answers address the question Answers do not address the

Third Party Report Supervisor or manager Could not demonstrate

Attachments if requested are Requested supplementary

All requirements of the Response does not address

Responses must refer to One or more of the

Developed by Enhance Your Future Pty Ltd 6

Does not refer to or utilise

Observation/Demonstration All elements, criteria, Could not demonstrate

Case Study All comprehension questions Lack of demonstrated

Answers address the question Answers do not address the

Attachments if requested are Requested supplementary

Developed by Enhance Your Future Pty Ltd 7

Assessment Cover Sheet

Learner’s name: MUKHTAR SINGH

The following questions are to be completed by the assessor:

Is the Learner ready for assessment? Yes No

Has the assessment process been explained? Yes No

Does the Learner understand which evidence is to be collected

Have you discussed any special needs to be considered during

The following documents must be completed and attached:

 Written Activity and Checklist

 Practical Activity Checklist

 Questions and Questions Checklist

The learner will answer a range of questions either verbally or S NYS

 The material I have submitted is my own work

Developed by Enhance Your Future Pty Ltd 8

Learner Signature: Date:

Result and Feedback

Overall Outcome Competent Not yet Competent

Assessor Signature: Date:

Developed by Enhance Your Future Pty Ltd 9

2. Describe data modelling as it relates to developing a conceptual data model.

Building visual representations of databases is the activity of providing a method of a

3. Explain what data redundancy is, and how it might be identified.

Developed by Enhance Your Future Pty Ltd 10

The principles of DBMS are as follows:

Database encryption is the process of applying algorithms to data transmitted and

Developed by Enhance Your Future Pty Ltd 11

7. Describe the features and the functions of databases.

Object-oriented programming is a paradigm centred on the management of objects that

10. In relation to databases, explain the term ‘scalability’.

Developed by Enhance Your Future Pty Ltd 12