GR 11 IT PAT 2023 Eng

INFORMATION TECHNOLOGY
GUIDELINES FOR
PRACTICAL ASSESSMENT TASK (PAT)
Grade 11
2023
These guidelines consist of 28 pages.
Copyright reserved Please turn over

Information Technology Grade 11 PAT 2023
Contents
Contents 2
What is the PAT? 3
Mark allocation 5
Topic 6
What you need to be able to do the PAT 8
Malpractice 8
Non-compliance 8
PAT requirements 9
Instructions 10
Annexure A: Assessment tools 18
Annexure B 27
Learner declaration – Task/ ____ 27
Annexure C 28
Declaration of authenticity 28
2
What is the PAT?

The Practical Assessment Task (PAT) is a software development project in which you will have the
opportunity to demonstrate your software development and programming skills.
The purpose of the PAT is to:
 Work extensively with content knowledge to improve your programming and organisational
skills,
 Implement computational thinking, other higher order thinking skills and formulate strategies
and to solve problems on different levels,
 Develop good working practices to prepare you for the real world, such as -
o Time management.
o Thorough planning.
o Perseverence to achieve and to excel in what you set out in your plan.
o Presentation and marketing of your product.
You will need to demonstrate knowledge and understanding of the software development life cycle
through analysis, design, coding and testing of your project. You will have to show effective use of
the software design tools and techniques which you have studied.
3
The PAT is divided into TEN TASKS as named below:
Task no. Task description Stage of application

development
Task 0 Problem definition and research Requirements
Task 1 Task definition, user story and Requirements

acceptance test
Task 2 Data dictionary Requirements

 Arrays
 Text files
 User defined methods
Task 3 Database design Requirements
Task 4 Navigation / flow between screens Requirements

and GUI design
Task 5 IPO table and data validation Design
Task 6 Create GUI application Design
Task 7 Create a Database and connect to Implementation

application
Task 8 Coding Implementation
Task 9 Testing and data validation Implementation
Task 10 Documentation and Interview Review and evaluation
LEARNERS NEED TO STRICTLY ADHERE TO THE DUE DATES
NOTE:
Submission dates: Specific dates will be determined by your subject educator.
TASK 0: Does not carry any marks; Preparation for PAT and the research thereof.
TASK 1-5: Not later than the end of Term 3
TASK 6-10: Not later than the three weeks before examination in Term 4.
NOTE:
You will be required to demonstrate and discuss your application during various interview
sessions as you progress.
4
Mark allocation
The PAT counts 20% of your final examination mark for Information Technology. It is therefore
crucial that you strive to produce work of a high standard.
Tasks Task description Maximum Mark Grouping
Task 1 Task definition, user story and acceptance test 12
Data dictionary
 Arrays
Task 2 16
 Text files
User defined methods
Task 3 Database design 12

Navigation / flow between screens and GUI
Task 4 4
design
Task 5 IPO table and data validation 20 64
Task 6 Create GUI application 6
Task 7 Create a Database and connect to application 6
Task 8 Coding 50
Task 9 Testing and data validation 8 70
Task 10 Documentation and Interview 16 16
Total: 150
NOTE:
 The PAT mark is a compulsory component of the final certification mark for all candidates re-
gistered for Information Technology.
 Your PAT will be moderated at district and provincial level by subject experts.
5
Topic
B USINESS M ANAGEMENT P ROGRAM

There are many types of activities where a business needs a program to capture, manage and
calculate data to create reports for decision making. The business management program can
range from financial, stock control to human resource management and various internal business
activities. For this year, learners are expected to design and develop a Delphi program for an
interactive “Business Management Program”.
Projects in this scenario could include the following topics related to business management:
 Tuck shop management program

 School bookstore management program
 Business invoicing programs used to keep track of finances
 Asset management system used to keep track of stock
 Point of sale system used to keep track of sales
 Payroll system used to keep track of employee salaries and payments made
 Reservation system, that facilitates appointment-based businesses, such as medical of-
fices, salons, and restaurants, and can keep track of all appointments/reservations
 Schedule management system that allows business managers and employees to access,
create and alter schedules
 System to manage projects and keep track of all activities at a business
 System to apply for different jobs at a business
Choose an application related to business management and do research on the information

system requirements.
You are not limited to the list of ideas above, but you need to keep within the overall theme of
business management. Note that you need to choose data and functionalities (services) in such a
way as to develop a well-rounded application related to the topic.
This business management software program is targeted at the business manager/employee in

charge of the program.
NOTE: Your final program must comprise one single program with logically related parts.
Resources that could provide some background:
 https://www.proofhub.com/articles/best-business-management-software
 https://biz30.timedoctor.com/task-management-software/
 https://userguiding.com/blog/hr-software/
 https://www.goodfirms.co/asset-tracking-software/blog/the-best-7-free-and-open-source-
asset-tracking-software
 https://www.lovelycoding.org/book-store-management-system/
6
Business management examples:
What you need to be able to do the PAT

To be able to do the PAT, you need the following:
 The Delphi IDE (Integrated Development Environment)
 Word processing and database software.
 Storage media to save and backup your work electronically, for example a flash drive or online /
cloud storage.
Malpractice
As the PAT is an individual project that is part of your final promotion mark, you may NOT:
 Get help from others without acknowledgement.
 Allow others to do programming code for you.
 Submit work which is not your own.
 Share your work with other learners.
 Include work directly copied from books, the Internet or other sources without acknowledge-
ment.
The above actions constitute malpractice, for which a penalty will be applied, depending on the
seriousness of the offence.
Non-compliance
You will be given up to a part of term four to submit outstanding work or present yourself for the
PAT. Should you fail to fulfil the Practical Assessment Task requirements, you will be awarded a
zero ('0') for the PAT component of IT. This will result in an incomplete promotion mark, and it may
result in you not passing your grade.
7
PAT requirements
The project must include the following:
 A database connection and database manipulation that entail performing different CRUD
(Create, Read, Update and Delete) operations.
 A multi-form GUI with good functionality and usability, based on sound HCI principles
 The use of a text file for input/output purposes, for example to populate data structures and to
provide reports.
 Other data structures eg. Arrays and user defiened methods that will be relevant to your pro-
gram
Database
The database must:
 have at least TWO tables
 contains sufficient data volumes and uses a variety of field types
 be accessed and manipulated by the program using code constructs
GUI
The graphical user interface (GUI) must
 have at least TWO forms/screens that allows for navigation between forms depending on the
user choices
 interact with the database and other data studtures to provide the necessary input, pro-
cessing and output
 comply with relevant HCI principles
Text files
Your application needs to make use of a text file(s) for input and/or output.
Arrays
The appropriate use of array(s).

Your application needs to make use of user defined methods.
NOTE: The mark obtained for your project will be greatly influenced by the quality of the
programming code that manipulates the data successfully to adhere to the user
requirements in the best possible way. Quantity cannot replace variety, effectiveness, and
quality.
8
Instructions
During these tasks you must show that you have done a proper and thorough user requirement
analysis and design. This needs to be done to determine who the users are and what the users of
the program would require it to do.
TASK 0: Research
Task 0 is a discussion and preparation task that does not carry any marks and has no
deliverables.
 Topic is the Business Management Program.
 Purpose of program
Describe the purpose of your program – why does the organiser need your program. Re-
search a few different Business Management Programs and write down the positives of
each.
 Possible solution
What will the program do to meet these needs above. Describe how your program will
work. Include a description of the program and how the user will interact with your pro-
gram.
 Scope
Explain what your program can do AND what your programs limitations are.
INTRODUCTION: TASK 1 - 5
During the following tasks you have to show that you have done a proper and thorough user
requirement analysis. This needs to be done to determine who the users are and what the users
of the program would require it to do. The following can be used as a guideline:
TASK 1A: Define the Task
Write a brief description (approximately 200 words) in your own words to describe, in general
terms, the problem/task and how the project will solve the problem.
Your explanation must highlight that:

 You understand the needs of the task that you have chosen.
 Your solution will solve the needs of the task.
 Provide a simple/ brief description of the scope of the project.
TASK 1B: User story and acceptance test
User stories:
The user is the target audience and will determine the needs and requirements of the program.
Determine the user needs and processing requirements.
9
The aim is to identify the user(s), user needs and processing requirements of the program. Use a
table or a 'use case diagram' to explain the role and activity of each user of the program.
For example:
As a learner I want to register so that I can play the Mathematics game to improve
my skills
WHO WHAT WHY
As a … I want to … So that …
User/Actor/role Goal/program feature Value or benefit
required
Verb and noun analysis:
Nouns:
 Learner: The person who wants to register and play the Mathematics game.
 Register: The action the learner wants to take to create an account or profile.
 Mathematics game: The game the learner wants to play to improve their skills.
Verbs:
 Want: Indicates the learner's desire to complete a certain action.
 Register: The action the learner wants to take in order to create an account or profile.
 Play: The action the learner wants to take in order to engage in the mathematics game.
 Improve: The outcome the learner hopes to achieve by playing the mathematics game -
that their mathematics skills will become better.
Acceptance test:
An acceptance test – use the user stories to identify the goals that represent a functionality
(functional requirement) that can be used or performed in isolation. For example, how does the
programmer know that the user stories have been satisfied.
From the example user story listed above, when does the programmer know the following:
 A learner registered
 A learner can play the Math game
 A learner can improve their skills
Note: A total of FIVE acceptance tests need to be identified from the TWO user stories.
TASK 2: Data Dictionary
A data dictionary is used to describe where the programmer will use different variables,
components and data structures.
10
Variables and components:

Your application should contain a variety and correct use of appropriate:
 variables types and components
 local and global variables
 naming conventions for variables and components
Array(s)
Your application must use an array(s). Explain where an array can be used in your program so
that it adds value to the program.
Text file(s)
Your application must use a text file(s) for input and/or output. Explain where a text file can be
used in your program so that it adds value to the program.
Your application must make use of user defined methods. Explain where you will create methods
that will be reused in your program to add value to the program.
Other data structures
Your application may include other data structures such as parallel/two-dimensional arrays,
classes and objects, and applying programming concepts such as polymorphism, overloaded
methods, method binding, etc.
Note: Your application must make use of a database. Task 3 will focus on the database aspects.
TASK 3: Database design
The aim is to design a database to serve as a data source as well as to manipulate data
contained in the database using programming code. A description of the database and how data
will be manipulated in the program should be included.
Show the design of the database, including at least TWO tables with field names, field types, field
sizes and a description of the fields.
The database should provide data to the program to be processed and create reports.
The Delphi program must be able to manipulate the content of database tables, for example
update/edit/delete/add data, provide results of queries, provide reports, et cetera.
NOTE: A relational database is optional, and the relationship between the tables should
then clearly be indicated.
TASK 4: Navigation / flow between screens

GUI design
Clearly indicate the logical program flow and navigation between screens/forms. Use a flow
diagram or any other form of illustration to present a global overview of the project.
11
TASK 5: Input, Processing, Output (IPO) table and data validation
Use an IPO illustration/table to:
 Design the overall solution, considering all constituent parts and the interrelationships
between the various parts of the program.
 Specify the following aspects of input (at least TWO interfaces):
o Format data types, source and component used
o Validation of input – at least FOUR different input validation types, example: Valid-
ate for NULL/empty field AND test if value was selected in a selection component
o Error checking mechanisms – data types and inputs validated with associated
messages
 Specify the layout, readability, format, data types, and appropriate output.
 Specify processing that needs to be done of at least EIGHT processes and provide
algorithm(s)/formulae to show how the processing will be done of at least FOUR
processes.
 Provide a clear description to indicate the input, processing and output requirements of the
program for at least TWO of the main interfaces.
TASK 6: Create the GUI application
Developing the GUI according to the planning document that was developed during Task 1-5. Use
appropriate components to ensure easy use and effective navigation. Follow HCI principles to
ensure that the application is user friendly and provides all necessary requirements for the user(s)
to use the program effectively and navigate through the options/functionalities easily.
The aim is to produce a GUI design that considers good human-computer-interface (HCI)
principles. Your design should include measures that prevents errors occurring due to invalid input
and that minimises the amount of information a user must enter.
Use HCI design principles and design a GUI that considers the following:
 The user, type of user and context of user.
 User requirements, usability.
 Dialogues – must be relevant, simple, and clear.
 Icon usage and presentation – well selected and relevant, well placed and purposely used.
 Colour – appropriate use of and combination of colours.
 Feedback – neat, clear and well presented.
 Helpful error messages.
 Exits – clearly marked, placed correctly.
 Shortcuts.
 Flow of information on the screen – top to bottom and left to right.
12
 Sensible use of space on the screen.

Provide examples of planned data capture and data entry designs (screenshots) and of planned
output design.
Show the GUI design following HCI principles of interface(s), excluding introductory screens.
NOTE: Screenshots may be used from a prototype of the project but must be annotated.
TASK 7: Create a Database and connect to application
Construct the database according to the planning document that was developed during Task 1 - 5.
Apply appropriate techniques and sound database development rules.
Pay attention to the following:
 Table names should start with a prefix “tbl” for example tblSuppliers.
 The use of spaces in field names might affect reading data from fields into the Delphi
application.
 The size of text fields must be restricted/limited as the columns in the DBGrid in the Delphi
application will be affected by the field size.
 The data types of fields must be well thought out as this information will ultimately connect
to components in the Delphi application, for example, the difference between the Number
and AutoNumber data types, the difference between saving a date as text or as a
DateTime data type, etcetera.
 Keep the purpose of the project in mind when setting up fields and tables.
 Ensure that the database connects correctly to the program and interacts with the program
in a meaningful and effective way that supports the program once you have written the
Delphi code.
TASK 8: Coding
Write code to develop the program according to the planning document that was developed during
Task 1-7. Note the following:
 Use good programming techniques and structures.
 Implement effective algorithms and sound defensive programming techniques to produce a

robust program.
 Use appropriate structures to satisfy the requirements of the algorithms.
 Use nested loops and conditional structures.
 The following data structures are compulsory in addition to the database:
13
o Text file - reading OR writing OR appending
o Array(s)
o User defined methods
 The use of any other data structures not already tested / advanced programming construct /
dynamic component.
 Use relevant validation procedures and components.
 Develop a well-designed and user-friendly GUI.
 Rename relevant components to add to readability of your code.
 Input data using the most effective method, for example a text file, database, keyboard,
components.
 Process the data using the most appropriate methods.
 Generate output of data using the correct components and structures, with formatting
where needed.
 Ensure smooth interaction between forms/tabs.
 Correctly manipulate the data in the database (CRUD).
TASK 9: Testing and data validation
Test the program using clearly defined normal/expected data, erroneous data, and boundary
(extreme) data.
Marks will be allocated for the validating of coding and error catching.
Guidelines:
“What must be tested? Why must it be tested? When will it be tested? How will it be tested?”
Use the use case scenarios (generally the additional scenarios) to derive test cases. Test cases
must be executable.
Provide suitable test inputs, e.g. test data (normal/expected data, erroneous data and boundary
data)
Provide expected results for normal data, erroneous data and boundary data.”
14
Example (from alternative scenario: Empty required fields)

Test case Input data Expected Result
Verify if Name field is filled Text field not empty Success
Text field empty Warning message
Another chance to enter

name
“Why? To ensure the user entered all the data that the program requires
When? On completion of the Registration unit /When the submit button is clicked”
TASK 10: Documentation and Interview
Documentation:
Project notes for the user
These project notes must describe how the user should interact with the program. It can include
notes on how to navigate through the program, specific requirements such as passwords and
installation procedures if applicable. The notes must also describe any known bugs or problems.
Project notes can be written as part of the help function of the program. Tool tip texts can also be
provided.
Project notes for developers

These project notes could include specifications/limitations applicable to the project to ensure that
the program is installed and set up correctly, e.g., the connection to the database.
Project notes related to the programming code added as comments. Document the code so that
other programmers will be able to interpret the code and understand the purpose of individual
pieces of code. It should also include comments to explain sections of complex code.
15
Interview
Demonstrate your program and answer questions about the program and the code during an
interview session.
Guidelines for the demonstration of the project:

 The teacher will schedule dates and times for demonstrations. About 15 minutes per project
will be allowed.
 You should hand in all the documentation before the demonstration takes place – at least one
week in advance.
 The demonstrations must be done electronically on the computer.
 You must execute your computer program and show all the features of the program to the
teacher for evaluation.
 The teacher can require you to execute test procedures to make sure that the entire program
is working correctly.
 As part of the demonstration, the teacher will identify random pieces of programming code in
the project and ask you to explain the purpose and working thereof. This is done to ensure
that you did the coding yourself. A similar type of procedure will be followed during
moderation. If you cannot explain the code used in the project, no marks can be awarded for
the project.
 You must hand in the electronic copy of the project that was demonstrated. The teacher will
use this copy to allocate any outstanding marks to finalise the mark.
Hand In
Hand in:
 The completed Delphi project (Delphi code, text files, database and any other resources
required to execute the program successfully) and project notes.
 The declaration of help received (Annexure B).
 The declaration of authenticity (Annexure C).
16
Annexure A: Assessment tools

Learner Name:
Task 1A 4 3 2 1 0
Define the Task Excellent – All four aspects Good – Three aspects Satisfactory – Two aspects Limited – Only one aspect No aspects covered
(Short description ±150 - 200 covered covered covered covered
words)
• Task is clearly described
• The need of the task is
4
identified.
• The possible solution will
solve the task.
• A description of the scope of
the project is provided.
Task 1B 4 3 2 1 0
User story: (Use Case diagram Role, activity, value of all Role, activity, value of all Many shortcomings in Major shortcomings in Not done or incorrect or
OR table format) users (at least 2 different users (at least 2 different discussion of role, activity, discussion of role, activity, irrelevant
Role, activity, value types of users) of the types of users) of the value of users, e.g. two value of users, e.g. many
(who, what, why) system thoroughly and system described but minor instances where goal is not parts left out or incorrect
• Who will use the system? correctly described. shortcomings e.g. one clear, value not clear, etc. information 4
• What are the goals/ activities Well documented, clear and instance where goal is not Only 1 type of user of the Poorly documented – not
that user will perform? to the point. clear, value not clear, etc. system discussed. acceptable
• Why do they want/need it? Well documented, but minor Not well documented but
shortcomings. still acceptable
Detailed list which clearly Fairly detailed list which A list which defines 3 A list which defines 2 No list of functions included
User stories (Acceptance
and correctly defines at clearly and correctly defines functions containing some functions but lacking in Very rudimentary, no detail
Tests)
least 5 functions 4 functions detail detail Not derived from user 4
List of functions the program
All functions derived from At least 3 functions derived Only 2 functions derived Only 1 function derived from stories
should perform
the user stories from the user stories from user stories user stories
12
17
Learner Name:
Task 2: Data Dictionary 4 3 2 1 0
Variables and components Excellent – All four Good – Three aspects Satisfactory – Two Limited – One aspect Totally inappropriate or
• Correct planning for the variety / aspects applied correctly applied correctly aspects applied correctly applied correctly incorrectly applied
appropriate components
• Correct planning for the variety /
appropriate variable types 4
• Correct planning for the use of local
and global variables
• Proper naming convention of variables
and components
Data Structures (Excl. Database) 4 3 2 1 0
Excellent and relevant Good planning for the use Limited planning for the An attempt to plan for the Not done or irrelevant.
Text files(s) planning for the use of a of a text file use of a text file. use of a text file with 4
text file short comings.
Excellent and relevant Good planning for the use Limited planning for the An attempt to plan for the Not done or irrelevant.
Array(s) planning for the use of an of an array use of an array with minor use of an array with many 4
array shortcomings short comings.
Excellent and relevant Good planning for the use Limited planning for the An attempt to plan for the Not done or irrelevant
planning for the use of of User Defined Methods use of User Defined use of User Defined
User defined methods User Defined Methods Methods with minor Methods. Shows potential 4
shortcomings but is not planned
correctly.
16
18
Learner Name:
Task 3: Database 3 2 1 0
Role of DB Manipulation and interaction well Manipulation and interaction not Manipulation and interaction not well No database or incorrect or
(How DB will be manipulated, described and well-motivated. clearly described or substantiated in described or motivated in two irrelevant or no interaction
e.g. within a dataset, access Most appropriate to meet one instance. instances.
fields and records, navigate requirements Adequate to meet requirements Mostly not meeting requirements
records, modify individual fields 3
and records and apply changes,
etc.)
Role of manipulation in program
described/motivated
Well-chosen fields. All fields One field does not contribute to the More than one field do not contribute No database or incorrect or
contribute to the solution solution to the solution irrelevant
Choice of fields AND OR OR 3
Contains no field that could be One field that could be calculated More than one field that could be
calculated from other data calculated
All fields well-chosen in terms of One field not well-chosen in terms of More than one field not well chosen No database
Field types and size 3
type and field size type or field size in terms of type or size
Appropriateness – Tables Excellent – All three aspects clearly Good – Two aspects clearly covered Satisfactory – Only one aspect No database.
• At least 2 tables covered clearly covered
• Tables have fields that are
3
correctly related.
• Primary key correctly
assigned
12
Task 4: Navigation / flow between screens & GUI design

4 3 2 1 0
A diagrammatical repres- An excellent attempt to show A good attempt to show the A satisfactory attempt to show A poor attempt to show the No diagram
entation of the design and the sequence of all steps and sequence of all steps and the sequence of steps and flow sequence of steps and flow OR
flow of events when the flow of events when the pro- flow of events when the pro- of events when the program is of events when the program Incorrect, irrelevant or un- 4
program is used gram is executed with no gram is executed with minor executed with significant short- is executed with major short- suitable for the application
shortcomings shortcomings comings comings
4
19
Learner Name:
Task 5: IPO – Software design tool
4 3 2 1 0
INPUT: Interfaces (at least TWO) Clearly describes all inputs Minor shortcomings in Clear description Poor attempt to describe No inputs described
• Source of input, such as from the according to all FOUR describing all inputs according to THREE points input values OR
keyboard, text file, array or points listed according to all FOUR listed Incorrectly described
database points listed OR
4
• Data type Major shortcomings in
• Format of input, e.g. date, gender describing all inputs
(M/F) according to all FOUR
• GUI component used points listed
INPUT: Validation Clearly describes all points Clearly describes TWO Clearly describes ONE Poor attempt to describe No validation described
• At least FOUR different data types listed points listed point listed validation OR
validated OR OR Incorrectly described 4
• At least FOUR inputs validated Minor shortcomings in Major shortcomings in
• Associated error messages describing all points listed describing all points listed
PROCESSING List at least EIGHT List SIX to SEVEN List THREE to FIVE Only ONE or TWO No processes listed
What processing will need to be processes processes processes processes listed 4
done
PROCESSING Clearly describes how at Clearly describes how Clearly describes how Clearly describes how Processes not described
How processing will be done – least FOUR processes will THREE processes will be TWO processes will be ONE process will be done or incorrect or irrelevant
supply algorithms, formulas, etc. be done done done OR An attempt to OR A poor attempt to 4
describe how FOUR describe TWO or THREE
processes will be done processes
OUTPUT: Interfaces (at least TWO) Clearly describes all Minor shortcomings in Clear description of all Poor attempt to describe No output described
• Data to output outputs by addressing all describing all outputs by outputs by addressing outputs OR
• Format of the output, e.g. cur- THREE points listed addressing all THREE TWO points listed Incorrectly described
4
rency, date points listed OR
• Output component, such as db- Limited outputs described
Grid, rich edit, label, etc.
20
20
Learner Name:
Task 6 3 2 1 0
HCI principles Good GUI design, considering Satisfactory GUI design, Limited GUI design, considering Poor GUI design considering less
(How GUI will meet the users’ almost all (at least 5) of the considering most (at least 4) of the only 50% (at least 3) of the than 50% (less than 2) of the
needs). Does it consider: principles for at least 2 of the principles for at least 2 of the main principles for at least two of the principles considered.
• Purpose of program and user main interfaces, excluding the interfaces, excluding the main interfaces, excluding the
• Standard GUI design principles introductory screen. introductory screens. introductory screens. 3
• Ease of use, logic flow
• Clearly marked navigation
• Friendly dialogue
• Helpful error messages
Components Appropriate components used In one or two cases another In three or four cases another Inappropriate components used in
in all cases component would have been more component would have been more more than four cases. 3
appropriate appropriate
6
Task 7 3 2 1 0
Construct the database Excellent – All three aspects Good – Two aspects clearly covered Satisfactory – Only one aspect No database.
• Appropriate naming convention of clearly covered clearly covered
tables, fields. 3
• Appropriate field sizes
• Appropriate data types for fields
Connecting the database Excellent – All three aspects Good – Two aspects clearly covered Satisfactory – Only one aspect No database.
• Connect DB with ADO/similar clearly covered clearly covered
connection/code
• Connect tables with appropriate 3
component/code
• Connect data source with appro-
priate component/code
6
21
Learner name:
Task 8 4 3 2 1 0
Variables and components Excellent – all four aspects Good – one aspect omitted Satisfactory – two aspects Limited – more than two Totally inappropriate
• Variety of appropriate variable applied correctly in all or not used well omitted or not used well aspects omitted or not used or incorrectly
types instances well applied
• Correct use of local and global
variables 4
• Proper naming convention of
variables, e.g., iNumber, sName
• Correct prefix for components,
e.g., edt, red, cmb
Text files(s) Effective, excellent and Good use of a text file(s) Limited use of a text file An attempt to use a text file Not done
4
relevant use of a text file(s) with shortcomings
Arrays Effective, excellent and Good use of array(s) OR Limited use of array(s) with An attempt to use an array. Not done
relevant use of arrays OR parallel arrays minor shortcomings Shows potential but not used
4
parallel arrays for a suitable purpose or
does not work correctly.
User defined methods Effective, excellent and Good use of User Defined Limited use of User Defined An attempt to use User Not done
relevant use of User Methods Methods with minor Defined Methods. Shows
Defined Methods shortcomings potential but not used for a 4
suitable purpose or does not
work correctly
Input data Excellent application of all Minor shortcomings in the Approximately 50% of the Limited application of the No application of the
• Variety of sources of input, e.g. FOUR aspects listed application of all aspects listed correctly aspects listed aspects listed
from the keyboard, text file, array FOUR aspects listed applied
or the database
4
• Correct data types
• Appropriate format used, e.g.
date, gender (M/F)
• Correct GUI component used
PROCESSING All algorithms used are Appropriate algorithms that 50% of the algorithms used Algorithms are mostly Totally inadequate or
Algorithm correctness/ appropriate, work correctly work correctly but ONE are appropriate, work inadequate/not working not working correctly
Processing and meet all processing processing requirement not correctly and meets most correctly, processing 4
requirements met processing requirements requirements not all met
PROCESSING All algorithms provide the Most algorithms provide the Limited efficiency of Poor efficiency of algorithms Totally inadequate or 4
22
Learner name:
Task 8 4 3 2 1 0
Algorithm efficiency most efficient solution. most efficient solution. algorithms used. used. not working correctly
Good programming Acceptable programming Few algorithms use good Algorithms do not use good
techniques used. techniques used. programming techniques. programming techniques.
Effective modular design Limited modular design with Poor modularity with limited Attempted use of own
with correct use of own correct use of own functions use of own functions and functions and procedures.
functions and procedures and procedures. procedures.
PROCESSING Excellent use of complex Works correctly. Works correctly with minor An attempt has been made No attempt has
Relevant and appropriate code that works correctly. Adds value to the system shortcomings. with major shortcomings. been made.
4
use of complex code, e.g. Adds value to the system
Dynamic component
OUTPUT Excellent application of all Minor shortcomings in the Approximately 50% of the Limited number of aspects None of the
• Layout FOUR aspects listed application of all FOUR aspects listed applied listed applied correctly aspects listed
• Readability/Clarity, e.g., columns, aspects listed correctly applied correctly
headings 4
• Formatted, e.g., currency
• Most appropriate component/
data structure used for output
Database manipulation 2 1 0
Delete record(s) and apply changes 2
Insert record(s) and apply changes Mostly meaningful, 2
Not done or
Edit/Update records/selected fields in record(s) and apply changes Meaningfully, appropriately appropriate and correctly 2
totally
Validate field(s) (when record is inserted/modified) and correctly done done 2
inappropriate or
Read/View selected fields and records Contributes to solution Mostly contributes to 2
not meaningful
Navigate through records in a dataset (first, next, previous, etc.) using methods solution 2
At least 1 report (output displayed/text file) as a result of processing/data transformation 2
50
23
Learner Name:
Task 9 4 3 2 1 0
Data validation A variety of validation/error limited validation/error Limited validation/error Validation/error catching No effort at validation/er-
catching for relevant input. catching for relevant input catching poorly done or inappropri- ror catching
Clear and appropriate error Mostly clear and appropriate Error messages and excep- ate/not meaningful 4
messages and exception error messages and exception handling sometimes in-
handling mechanisms tion handling mechanisms appropriate/ not meaningful
Testing (verified during interview) Excellent – all three aspects Good – mostly meaningful Satisfactory – two aspects Limited – more than two as- Totally inappropriate or in-
• Test for valid data applied correctly in all in- for all three aspects with omitted or not used well pects omitted or not used correctly applied
4
• Test for extreme data stances minor shortcomings well
• Test for invalid data
8
Task 10 4 3 2 1 0
Comments/Notes Code clearly annotated to Code clearly annotated to Code annotated to explain Code annotated to explain No comments or no
fully explain all necessary explain all necessary parts. most necessary parts. certain parts. project notes
parts. Project notes present and of Project notes present and of Inadequate project notes
Extensive project notes a very good quality a moderate standard present 4
present and of an excellent
standard. Clearly explains
working of the program
Does the program meet the Exceeds requirements Meets the requirements Meets most of the Only meets some Does not meet the
requirements? stated in Phase 1. stated in Phase 1. requirements, but some requirements, and some requirements.
Comprehensive program. Less comprehensive. don't function well don't function well. Less than basic.
All elements function as All elements function as Only some program Basic program. Limited scope.
4
specified. specified. elements function as Basic scope.
Shows insight in all aspects. Shows insight in most specified in Phase 1. Very limited insight.
aspects. Shows insight in one or two
aspects.
Interview 8 6 4 2 0
Explained all selected code Explained selected code Unable to explain some of Unable to explain most of Unable to explain any
clearly and with confidence. with minor shortcomings. the selected code the selected code, limited selected code, no insight.
Explain selected code 8
Shows excellent insight. Shows insight adequately. insight.
Shows some insight
16
24
Assessment Summary
Phase Tasks Task description Maximum Mark Mark Obtained Moderated Mark
Phase 1 Task 1 Task definition and user story and acceptance test 12
Task 2 Data dictionary, Arrays, Text files and User defined methods 16
Task 3 Database design 12
Task 4 Navigation / flow between screens and GUI design 4
Task 5 IPO table and data validation 20
Phase 2 Task 6 Create GUI application 6
Task 7 Create a Database and connect to application 6
Task 8 Coding 50
Task 9 Testing and data validation 8
Phase 3 Task 10 Documentation and Interview 16
Final mark 150
I hereby declare that the work assessed is solely that of the learner (except where there is clear acknowledgement and record of any substantive advice/assistance given
to the learner) concerned and was conducted under supervised/controlled conditions to ensure that the work has not been plagiarised, copied from someone else or
previously submitted for assessment by anyone.
Comment:
____________________________________________________________________________________________________________________________________________________________________
____________________________________________________________________________________________________________________________________________________________________
Teacher name: _________________________________________________________ Teacher signature:_______________________________________Date:
25
Annexure B
Learner declaration – Task/ ____
I understand that work submitted for assessment must be my own.

Have you received help/information from anyone to produce this work?
No Yes (provide details below)

Help/information Nature of the help/information (provide evidence):
received from (person):
_________________________ ___ / ___ / 2023

Signature of Learner Date
26
Annexure C
Declaration of authenticity
Learner name ID Number
Grade 11 Year 2023
Subject Information Technology
Practical Assessment Task (PAT) Teacher
I hereby declare that the contents of this assessment task are my own original work
(except where there is clear acknowledgement and appropriate reference to the work of
others) and have not been plagiarised, copied from someone else or previously
submitted for assessment by anyone.
_________________________ ___ / ___ / 2023

Signature of Learner Date
27

GR 11 IT PAT 2023 Eng

Uploaded by

Copyright:

Available Formats

GR 11 IT PAT 2023 Eng

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

GR 11 IT PAT 2023 Eng

Uploaded by

Copyright:

Available Formats

INFORMATION TECHNOLOGY

These guidelines consist of 28 pages.

Copyright reserved Please turn over

What is the PAT?

The purpose of the PAT is to:

o Presentation and marketing of your product.

The PAT is divided into TEN TASKS as named below:

Task no. Task description Stage of application

Task 0 Problem definition and research Requirements

Task 1 Task definition, user story and Requirements

Task 2 Data dictionary Requirements

Task 4 Navigation / flow between screens Requirements

Task 6 Create GUI application Design

Task 7 Create a Database and connect to Implementation

Task 8 Coding Implementation

Task 9 Testing and data validation Implementation

Task 10 Documentation and Interview Review and evaluation

LEARNERS NEED TO STRICTLY ADHERE TO THE DUE DATES

Submission dates: Specific dates will be determined by your subject educator.

TASK 1-5: Not later than the end of Term 3

Tasks Task description Maximum Mark Grouping

Task 1 Task definition, user story and acceptance test 12

Task 3 Database design 12

Task 6 Create GUI application 6

Task 7 Create a Database and connect to application 6

Task 9 Testing and data validation 8 70

Task 10 Documentation and Interview 16 16

B USINESS M ANAGEMENT P ROGRAM

 Tuck shop management program

Choose an application related to business management and do research on the information

This business management software program is targeted at the business manager/employee in

Resources that could provide some background:

Business management examples:

What you need to be able to do the PAT

User defined methods

TASK 1A: Define the Task

Your explanation must highlight that:

TASK 1B: User story and acceptance test

Verb and noun analysis:

TASK 2: Data Dictionary

Variables and components:

TASK 3: Database design

TASK 4: Navigation / flow between screens

TASK 5: Input, Processing, Output (IPO) table and data validation

Use an IPO illustration/table to:

 Specify the following aspects of input (at least TWO interfaces):

o Format data types, source and component used

TASK 6: Create the GUI application

 Sensible use of space on the screen.

TASK 7: Create a Database and connect to application

Pay attention to the following:

 Use good programming techniques and structures.

 Implement effective algorithms and sound defensive programming techniques to produce a

 Use appropriate structures to satisfy the requirements of the algorithms.

 Use nested loops and conditional structures.

 The following data structures are compulsory in addition to the database:

o Text file - reading OR writing OR appending

o User defined methods

 Use relevant validation procedures and components.

Teacher name: ___________________ Teacher signature:_Date:

_______________________ _ / ___ / 2023

_______________________ _ / ___ / 2023