Information Technology PAT GR 12 2018 Eng hlayiso.com

Downloaded from hlayiso.com INFORMATION TECHNOLOGY GUIDELINES FOR PRACTICAL ASSESSMENT TASK 2018 These guidelines consist of 31 pages. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 2 DBE/PAT 2018 NSC INTRODUCTION The 16 Curriculum and Assessment Policy Statements subjects which contain a practical component all include a Practical Assessment Task (PAT), for example a Practical or Performance Assessment Task. These subjects are: • AGRICULTURE: Agricultural Management Practices, Agricultural Technology • ARTS: Dance Studies, Design, Dramatic Arts, Music, Visual Arts • SCIENCES: Computer Applications Technology, Information Technology • SERVICES: Consumer Studies, Hospitality Studies, Tourism • TECHNOLOGY: Civil Technology, Electrical Technology, Mechanical Technology and Engineering Graphics and Design A Practical Assessment Task (PAT) mark is a compulsory component of the final promotion mark for all candidates offering subjects that have a practical component and counts 25% (100 marks) of the end- of-year examination mark. The PAT is implemented across the first three terms of the school year, which is broken down into different phases or a series of smaller activities that make up the PAT. The PAT allows for learners to be assessed on a regular basis during the school year and also allow for the assessment of skills that cannot be assessed in a written format, for example test or examination. It is therefore important for schools to ensure that all learners complete the Practical Assessment Tasks within the stipulated period to ensure that learners are resulted at the end of the school year. The planning and execution of the PAT differs from subject to subject. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 3 DBE/PAT 2018 NSC What is the PAT? The Practical Assessment Task (PAT) is a software development project in which you will have an opportunity to demonstrate your programming skills and understanding of the connections between the different areas of solution development. You will also be required to demonstrate your 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. You need to provide the following outputs: • Phase 1: A report where you o Provide a brief description of the problem to be solved o Discuss the research/investigation/analysis done regarding the project o Provide a brief description of the purpose and scope of your project o Do a detailed design of your solution • Phase 2: A working Delphi program that implements the planned solution NOTE: You will be required to demonstrate and discuss your program during an interview session. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 4 DBE/PAT 2018 NSC Mark allocation The PAT counts 25% of your final examination mark for Information Technology. It is therefore crucial that you strive to produce work of a high standard. Phase Development phase Maximum Mark % Phase 1 Analysis and Design 60 40 Phase 2 Coding and Testing 72 48 General Final product and impression 18 12 Total: 150 100 NOTE: • The PAT mark is a compulsory component of the final certification mark for all candidates registered for Information Technology. • Your PAT will be externally moderated by subject experts and quality-assured by Umalusi. You need to complete your PAT before you start the Grade 12 end-of-year examination. Not submitting your PAT or any part of the PAT, will mean that you will be awarded a zero (“0”) for the PAT component of the examination or the parts not submitted. NOTE: Submission dates: Specific dates will be determined by your subject educator. Phase 1: Not later than the end of Term 1 Phase 2: Not later than the first week of Term 3. YOU NEED TO STRICTLY ADHERE TO THE DUE DATES FOR EACH PHASE. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 5 DBE/PAT 2018 NSC The Topic The food, beverage and confectionary industry NOTE: The topic EXCLUDES any form or reference to alcoholic beverages. In the discussion and examples below, the term 'beverage' refers to cool drink. The food, beverage and confectionary industry is a significant, global collective of diverse businesses that supplies the food, beverages and confectionary consumed by the world's population. This industry ranges from simple home industries to modern, highly technological companies manufacturing and transporting food supplies. Some of the activities are also directed at the preparation, preservation, serving, packaging and the retailing of food supplies. You are required to plan and develop a software program that is associated with any aspect related to the food industry. Examples of topics are: • Farming and agriculture: vegetables, dairy, chicken, cattle, etc. • Industrial fishing • Companies manufacturing packaging required for food, beverages and confectionary • Home industries/Service providers used for baking and the hosting of functions • Modern technology and equipment used/supplied for manufacturing food • Transporting food and beverage supplies • Supermarkets that retail food and beverages • Stock control at warehouses that distribute food and beverages • Restaurants and food outlets • Magazines and recipe books used for the preparation of food • Jobs, careers related to this industry • Health companies that carry out hygiene tests on food • Chemicals used in preserving food • Import and export of food and beverages • Advertising, marketing, television and radio shows Choose an application/environment that relates to the food, beverage and confectionary industry and do research on the information system requirements. You are not limited to the above-mentioned list of ideas, but you need to choose data and functionalities (services) in such a way as to develop a well-rounded application related to the topic. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 6 DBE/PAT 2018 NSC Specific requirements: • The project must include the major development tools, for example a database and programming language constructs, appropriately integrated. • Include all the aspects mentioned in the PAT requirements (see page 8) and Phase 2 marking guidelines. NOTE: Your final project must consist of one single program, with logically related parts. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 7 DBE/PAT 2018 NSC Overview PHASE 1 – ANALYSIS AND DESIGN The purpose of this phase is to analyse the problem, i.e. to determine what should be done and what the user requirements are. This includes the following activities: • Identify the problem • Research/Investigate the topic/scenario/the (potential) users from whom facts about the nature/functionality of the program you intend to produce can be gathered • Define the task by determining the following: o WHAT will the system do? o HOW will the system be used? o WHO will use the system? This will be followed by determining how the program/system will meet the requirements and the planning and design of the solution to the problem: • Clarify the requirements by using available software design tools to design the solution, clearly indicating the logical program flow and navigation between screens. • Design the database and other data structures to be used. • Design the GUI(s) and data capturing mechanisms. • Identify what processing will need to be done and define how the processing will be done. • Indicate what the output will be and design appropriate data output components/ mechanisms. PHASE 2 – CODING AND TESTING The purpose of Phase 2 is to implement the design by writing the code and testing the program. The following must be done: • Write the programming code to implement the design and to complete the program. • Test and debug the program. • Clarify sections of the code by adding comments. • Write project notes for the program. • Demonstrate your program and answer questions about the program and the code during a debriefing session. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 8 DBE/PAT 2018 NSC PAT requirements The project should include the following, appropriately integrated: • Database manipulation through programming language constructs and SQL statements • Text file(s) for input-output purposes, e.g. to populate data structures, provide reports • A multi-form/multi-screen GUI with good functionality and usability, based on sound HCI principles • Manipulation/Transformation of data through: o Mathematical/Statistical processes o String/Text processes Database The database component: • Must be accessed and manipulated using your own programming code as well as using SQL statements • Should not only involve data storage/retrieval and possibly trivial processing by the package with virtually no code of your own (resulting in a simple solution) • Must include at least TWO relational tables • Must involve sufficient data volumes and use a variety of field types Text file Your program must use input from a text file to manage data that could have been captured elsewhere. This must include mechanisms to transfer and process data between the database and text file/s. The data from the text file could be used to: • Do calculations and manipulations in combination with data from the database • Update existing data (add records, delete records, update records, etc.) At least one report should be provided in a text file format. GUI The graphical user interface (GUI ) must be functional and based on sound HCI principles. The GUI must have at least: • Three forms/screens • One component created dynamically Variables and data structures • Use appropriate variables and data structures • Carefully consider the scope of variables (local vs. global) Modular Programming Incorporate your own methods/procedures/functions, e.g. to validate data or to transform/ manipulate data Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 9 DBE/PAT 2018 NSC Further requirements Apply good programming principles and techniques • Descriptive names for variables, data structures, fields, components, etc. • Well-structured, readable code • Write comments/annotations to explain pieces of code, especially on the manner in which variables/data structures and output variables/components are used. Write project notes • Describe how to use/interact with the program • Describe any known bugs or problems Project notes can be written as a help function that is part of the program General programming aspects that will be assessed: • Programming style • Graphical user interface (GUI) • Use of human-computer interaction (HCI) and software engineering principles • Use of OOP principles • Functionality of the program • Level of expert programming • Robustness of the program, including the use of defensive programming techniques • Whether the project matches the original aims and goals • Internal documentation to explain sections of the program Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 10 DBE/PAT 2018 NSC What you need to be able to do the PAT To be able to do the PAT, you need the following: • Delphi programming software, including a GUI IDE (Integrated Development Environment) • An office suite with the following software: o Word processing software o Database software • Internet access to find data and information • Access to other sources, such as printed media (for example magazines, newspapers, brochures, textbooks) or other electronic material (for example e-books, e-articles). • Access to facilities to convert hard copies to electronic documents, for example a scanner, digital camera • Storage media to save and backup your work electronically, for example a flash drive, rewritable CD/DVD, etc. 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 • Submit work which is not your own e.g. programming code that was written by someone else • Share your PAT work with other learners • Allow other learners to obtain or use your research/code (this does not mean that you may not exchange books/links to informative websites) • Use research or code that other learners obtained and used in their PAT projects • include work directly copied from books, the Internet or other sources without acknowledging it. The above actions constitute malpractice, for which a penalty will be applied, depending on the seriousness of the offence. NOTE: If you use work from other resources, it may not exceed 20% of the work that you submit. Non-compliance You will be given up to three weeks before the commencement of the final end-of-year examination 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. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 11 DBE/PAT 2018 NSC Instructions for Phase 1 The aim of Phase 1 is to: • Define the task in your own words • Do research in order to get a clear understanding of the problem/task at hand • Analyse the problem/task at hand by doing research to identify what the system should do, how the system will be used and who the users would be. If possible, consult with them to determine the requirements/functionality of the program. • Determine HOW you will go about solving the problem and plan the detail. • Produce the plan showing the high-level overview of how the solution will be constructed using explained/annotated pseudocode/diagrams (or a suitable alternative). The plan must show the main blocks within the proposed solution. • Specify and document an overall design that meets the requirements using an IPO table as a software design tool. DEFINE THE TASK The aim is to provide an overall picture of the purpose and scope of the project, but not the details. Write a brief description (approximately 100 words) in your own words to describe the problem/task in general terms and how the project will solve the problem. In other words, the description should clearly indicate that: • You understand the requirements of the project • Your solution will address the requirements • Your project adheres to the PAT requirements/specification. DO RESEARCH The aim is to gather basic background knowledge and facts about the identified task and the nature of the program you are developing. Your research should help you to • Understand the topic/scenario • Clarify the nature/type of program you are required to develop • Look at some existing solutions, where possible, to gather ideas • Understand what particular type of program(s) is suitable for this project The outcome is a report (± 150 words/1 page) that indicates, for example, what a software solution for the problem may include, similarities, missing features and general working/flow of existing solutions. The report should be written in clear unambiguous language. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 12 DBE/PAT 2018 NSC DO THE ANALYSIS The aim is to • Present a clear explanation of what the problem/task is and what the solution should be capable of doing in terms of the needs of the user (company)/task and their stated objectives. • Provide an analysis of how the system will be used • Determine who will use the system, identify the prospective user(s) and identify the user needs and acceptable limitations. BASIC SOLUTION DESIGN Use a diagram/illustration to show the flow of the PAT from the start to the end. The diagram must illustrate the use of tabs/forms, navigation and any other significant aspects of the design. Use an IPO-diagram as a software design tool to clearly design/indicate the logical program flow and navigation between screens. The aim is to: • Determine how you will go about solving the problem and plan the detail. • Produce the plan, showing a high-level overview of how the solution will be constructed and using explained/annotated pseudocode/diagrams (or suitable alternatives). The plan must show the main blocks within the proposed solution. • Specify and document an overall design that meets the requirements, using an IPO- diagram. DATA DICTIONARY Design a database to serve as data source that can provide data to manipulate/transform, e.g. through mathematical/statistical processes using programming instructions. Clearly indicate the fields, the field types and the primary key. Describe the role of the database in the program. The Delphi program must also be able to manipulate the contents of the database tables, e.g. update/edit/delete/add records, provide results of queries, provide reports as a result of processed/manipulated data, etc. Plan and design other data structures that will be used. These include objects, arrays and text files. Clearly indicate how and where these data structures will be used. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 13 DBE/PAT 2018 NSC DATA CAPTURING (INPUT) Design a GUI that considers good human-computer-interface (HCI) principles, that prevents errors occurring from invalid input and that minimises the amount of information a user has to input. Use HCI design principles and design a GUI that considers the following: • The user – type and context • User requirements/needs, usability • Dialogue – must be relevant, simple and clear • Icon usage and presentation – well selected and relevant, well placed with a clear purpose • Colour – use and combination of colour • 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 • Sensible usage of space on the screen Provide sample(s) of planned data capture and data entry designs (prototype screen dumps may be used but must be annotated) and of planned valid output designs. Plan and design how validation and error catching will be handled for all relevant components. DATA PROCESSING Identify and list the processing that will need to be done. Design the necessary algorithms to do the required processing. Provide: • A detailed list of all processing to be done • Algorithms/Methods that will be used to do the required processing. This can include: o Specific formulas and/or functions that will be used o Pseudocode solutions and diagrams DATA OUTPUT Identify and list the output that will be required. Select/Design the necessary output components and how the output will be formatted. Provide: • A detailed list of all required output • Output components that will be used and how output will be formatted Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 14 DBE/PAT 2018 NSC HAND IN Once you have completed Phase 1 of the project, submit a detailed report that covers the following: • Problem identification • Research/Investigation on the topic/scenario/(potential) users to gather facts about the nature/functionality of the program you intend to produce. This should include proof of research with proper referencing. • A detailed task definition/analysis indicating the following: o WHAT will the system do? o HOW will the system be used? o WHO will use the system? • Basic design –flow diagram • Data dictionary – including detailed database design • GUI design • IPO o Data input – what will be the input, validation and error catching techniques o Data processing – what will need to be processed, how will it be processed o Data output – required output, components and format of output NOTE: Your report should NOT include that you must write a Delphi program that should be user-friendly and include a database. These are obvious requirements. You should focus on the ONE specific problem you have chosen. Also include your declaration of authenticity for Phase 1 (Annexure A). Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 15 DBE/PAT 2018 NSC Instructions for Phase 2 The aim is to implement your design by using appropriate software tools (programming language, database software, IDE, etc.) and to use techniques to code a solution to the problem. After completing your project, you will also demonstrate the program and answer questions about your program, the process and the code. DEVELOP THE DATABASE Implement the design and construct the database by applying appropriate techniques. Ensure that the database connects correctly to the program and interacts with the program in a meaningful and effective way that supports the solution. DEVELOP THE GUI Implement the design by developing the GUI and using appropriate components to ensure easy use and navigation. The user should have a good experience when using the program. WRITE THE CODE Use the planning documents of Phase 1 and Phase 2 to write the code for all units/parts. Use good programming techniques and structures. Implement effective algorithms and sound defensive programming techniques to produce a robust program. Document the code so that other people will be able to interpret the program and understand what individual pieces of code do. The database must be embedded in the program. TEST THE PROGRAM/SYSTEM Perform tests to determine: • The functionality of the program/system – to confirm that the program/system satisfies the system requirements (user acceptance testing) • Whether units of code (single functions, procedures, interface(s), etc. – one feature at a time) are working correctly (unit testing). Test the program/system using clearly defined typical data, erroneous data and boundary (extreme) data. Compare test input results with expected results to determine success or failure. Debug where necessary. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 16 DBE/PAT 2018 NSC DOCUMENT THE PROGRAM Use any appropriate facility of the programming language to write project notes that a user can access to describe how to interact with the program. The notes must also describe any known bugs or problems. Add comments to explain sections of code. HAND IN On completion of Phase 2, hand in the following: • The completed Delphi project, including the comments and project notes • The declaration of authenticity (Annexure A) INTERVIEW Demonstrate the program for evaluation. 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. • The teacher can use the mark sheet for Phase 3 as a guideline and allocate marks accordingly during the demonstration. • 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 in order to finalise the mark. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 17 DBE/PAT 2018 NSC Assessment Tools Phase 1 - Analysis and Design Learner name: Investigation: 4 3 2 1 0 Clearly outlines the current Acceptable outline of the Limited outline of the current Weak outline of the current No clear problem/task Problem identification problem/task. current problem/task. problem/task. problem/task. defined. 4 Extensive research done. Large amount of research done, Research done, but not Limited research and/or No research/references Research is relevant. but with limited relevance. always relevant. references included Report on research Proof of own research and/or Proof of own research and/or Limited references/proof 4 at least 3 references. at least 2 references. Problem analysis/definition 4 3 2 1 0 Clear description covering all Clear description with minor Complete description, but Incomplete description, with Incorrect, irrelevant or not WHAT will the system do detail. detail missing lacks clarity. limited use. described at all. 4 Clear description covering all Clear description with minor Complete description, but Incomplete description, with Incorrect, irrelevant or not HOW will the system be used detail. detail missing lacks clarity. limited use. described at all. 4 Clear description covering all Clear description with minor Complete description, but Incomplete description, with Incorrect, irrelevant or not WHO will use the system detail. detail missing lacks clarity. limited use. described at all. 4 BASIC DESIGN 4 3 2 1 0 Navigation/Description An excellent attempt to show A good attempt to show the A satisfactory attempt to show A poor attempt to show the No diagram OR incorrect, the sequence of all steps and sequence of all steps and the sequence of all steps and sequence of all steps and irrelevant or unsuitable for A diagrammatical execution of processes for the execution of processes for the execution of processes for the execution of processes for the the application. representation of the design solution with no solution with no shortcomings. solution with shortcomings. solution. and flow of the PAT shortcomings. DATA DICTIONARY 4 3 2 1 0 A variety of data structures A variety of data structures Data structures include not Data structure definition No or poor definition of data Choice of data structures, that all contribute to the included, but is not always the only appropriate variables but covers basic variables, with structures used. Arrays, text files, variable, etc. solution and are clearly best option for solution or not also other structures like text appropriate types that are 4 (How data will be stored) defined. clearly defined. files or arrays. needed for solution. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 18 DBE/PAT 2018 NSC Database basic design All database design Good database design with Average design with several Database design done, but No database or incorrect or • All fields are relevant requirements met. minor shortcomings. shortcomings. with limited value. irrelevant. • Type and size of fields 4 well-chosen Database advanced design A well-designed relational A relational database A relational database with A poor attempt to normalise a No relational database • Relational database normalised normalised with minor more than one inappropriate relational database. Database is not normalised 4 • Normalised appropriately. shortcomings. field. GUI DESIGN 4 3 2 1 0 • Design fits to program's Good GUI design, Satisfactory GUI design, Limited GUI design, Poor GUI design considering GUI design is not functional intended use considering all of the considering most (at least 4) of considering (at least 3) of the less than 50% (less than 2) of or does not support the • Appropriate components principles in a variety of the principles in a variety of principles in a variety of the principles. intended use at all. • Ease of use, logical flow applications eg. Data applications eg. Data capturing, applications eg. Data 4 • Clearly marked navigation capturing, output, navigation output, navigation capturing, output, navigation • Friendly dialogue / Help Software Design Tool: IPO DATA INPUT 4 3 2 1 0 Clearly describes all inputs in Minor shortcomings in Limited description. More Poor description. Most inputs Input requirements not Input data terms of the data that will be describing all inputs in terms of than two inputs not clearly not clearly described. described, incorrect or (What input will be provided) stored, sources and format of the data that will be stored, described. irrelevant input. sources and format of input. 4 Input Format and source (How input will be stored) Validation/Error catching Clearly describes appropriate Techniques, to ensure only valid Validation/error-catching Validation/error catching No effort at validation • Validation/error catching and effective techniques, to data is entered are mostly limited and sometimes poorly described or for relevant input ensure only valid data is appropriate and effective inappropriate/not meaningful. inappropriate/not meaningful. 4 • Associated error entered. messages DATA PROCESSING 4 3 2 1 0 Clearly lists all processing/ One or two Most Many processing/ Most WHAT processing will need to be done manipulation that will need to processing/manipulations not processing/manipulations manipulations not clearly Processing/manipulations 4 be done. correctly listed. correctly listed. Limited detail. listed. not listed. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 19 DBE/PAT 2018 NSC HOW processing will be Clearly describes how all One or two Some processing/ Many processing/ Processing/manipulation managed - algorithms, processing/manipulation will processing/manipulations not manipulations not clearly manipulations not clearly not described, incorrect or 4 formulas, etc.) be done. clearly described. described. Mostly correct. described. Many errors. irrelevant DATA OUTPUT 4 3 2 1 0 Output Data Clearly describes all outputs Minor shortcomings in Limited descriptions. More Poor descriptions. Most Output requirements not (What output will be provided) in terms of the data that will descriptions. One or two than two outputs not clearly outputs not clearly described. described, incorrect or be provided and how sources outputs not clearly described. described. irrelevant 4 Output Format of output will be used and (How output will be presented) formatted. Total: 60 Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 20 DBE/PAT 2018 NSC Phase 2 Coding: Learner name: DATABASE DESIGN 4 3 2 1 0 Database design correctly Database design correctly Uses at least two tables, but Use of a relevant database. Totally inappropriate or implemented, with at least two implemented, with at least two database design not properly One table. incorrect or not used Implementation of Database relational tables, suitable fields, relational tables, suitable fields, implemented. Errors in fields, design data types and sizes. data types and sizes. data types and sizes OR Few suitable fields, data 4 types and sizes. Large/Adequate data volume Limited volume of data used. Small amounts of data used. used. GUI DESIGN 4 3 2 1 0 Ease of use/HCI principles Excellent – all four aspects have Good – one aspect omitted or Satisfactory – two aspects Limited – more than two Poor GUI design. • Excellent layout and been met and used correctly. not used well. omitted or not used well. aspects omitted or not used Little/no thought given communication (screen tips, well. to HCI principles. feedback, help et cetera) • Most appropriate components • Readable/Relevant 4 input/output • Excellent use of effects/ colour/ icons/shortcuts/ tool tip text, et cetera DATA STRUCTURES 4 3 2 1 0 Variety of appropriate variable Variety of variable types, use of Limited variety of variable Poor variety of variable Totally inappropriate or types, correct use of local and local and global variables, types and use of local and types. incorrectly used Variables used global variables, proper naming Choice, use and naming of global variables AND/OR Incorrect use of local and 4 convention of variables and variables not always suited poor naming of variables. global variables. Poor components naming of variables. Used at least two data structures Used at least two data Used at least one data Used at least one data Totally inappropriate or (e.g. array and text file) correctly structures (e.g. array and text structure (e.g. array or text structure (e.g. array or text incorrect or not used Data structures used and appropriately file) with minor shortcomings file) correctly and file) but not always correctly 4 (User defined, excl. DB) appropriately and appropriately Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 21 DBE/PAT 2018 NSC INPUT 4 3 2 1 0 Variety of input mechanisms Different input mechanisms Limited variety of input Limited variety of input Totally inappropriate or Input data used. used, not always the most mechanisms used, often mechanisms used, mostly ineffective (Mechanisms/components, appropriate type, format or not the most appropriate not the most appropriate 4 Most appropriate type, format type, format etc.) components. type, format or component. type, format or component. and components used. Extensive validation/error Variety of validation/error Limited validation/error Validation/error catching No effort at validation catching for relevant input catching for relevant input catching. Error messages poorly described or Clear and appropriate error Mostly clear and appropriate and exception handling inappropriate/not Validation/Error catching sometimes meaningful. 4 messages and exception- error messages and exception handling mechanisms. handling mechanisms. inappropriate/not meaningful. PROCESSING 4 3 2 1 0 All solution algorithms used are Appropriate solution algorithms Most solution algorithms Solution algorithms are Totally inadequate or not Algorithm correctness/ appropriate, work correctly and that work correctly but one used are appropriate and mostly inadequate or mostly working correctly meet all processing processing requirement not work correctly and meet not working correctly, 4 Processing requirements. met. most processing processing requirements not requirements. all met. All algorithms used are the most Most algorithms used are the Limited efficiency of Poor efficiency of algorithms Totally inadequate or not efficient solution. most efficient solution. algorithms used. used. working correctly Algorithms use good Algorithms use acceptable Few algorithms use good Algorithms do not use good Algorithm efficiency programming techniques. programming techniques. programming techniques. programming techniques. 4 Effective modular design with Limited modular design with Poor modularity with limited Attempted use of own correct use of own functions and correct use of own functions use of own functions and functions and procedures procedures and procedures procedures • Non-trivial, excellent layout • Good layout and appropriate • Satisfactory layout and • An attempt has been • No attempt has been Use of creative/complex code and placements. placement. placements. made, with major made. to create a graph/map or • Works correctly, adds value to • Works but could be • Works with minor shortcomings. 4 timer the solution. improved. shortcomings. • Relevant and appropriate. • Relevant and appropriate. • Relevant and appropriate Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 22 DBE/PAT 2018 NSC OUTPUT 4 3 2 1 0 In all cases: In all cases: In most cases In some cases No output or unreadable • Excellent display, well • Most appropriate display, well • Appropriate display. o Ouput difficult to read formatted/readable/ formatted/readable/ • Satisfactory layout. o Inconsistent layout Output structured, for example structured, but with minor 4 headings repeated on next shortcomings in one instance page/screen where • Good layout. applicable. • Excellent layout Database - High Level Language interaction 4 3 2 1 0 Excellent use of code Good use of code constructs to Adequate use of code Limited use of code Totally inadequate or not constructs to view, navigate view, navigate data. constructs to view, navigate constructs to view, navigate working correctly data. data. data. Effective use of data queries Good use of code to Adequate use of code to Limited use of code to Few examples of using code 4 filter/sort/search when filter/sort/search when selecting filter/sort/search when to filter/sort/search when selecting data. data. selecting data. selecting data. Excellent use of Good use of processing/ data Adequate use of processing/ Limited use of processing/ Totally inadequate or not processing/data transformation. data transformation. data transformation. done. transformation. Good use of calculated values. Limited use of calculated No calculated values. Complexity of data queries Excellent use of calculated Variety of complex queries. values. No complex queries. 4 values. Variety of complex Few complex queries. queries, including the use of relationships between tables. Uses all data maintenance Uses all data maintenance Uses all data maintenance Uses some data Totally inadequate or not actions. actions. actions. maintenance actions. done. Data maintenance - All actions correctly used. All actions correctly used. All actions correctly used. All actions not correctly Insert/Update/Delete All applications contribute to a Some applications do not Most applications do not used. 4 records functional system. contribute to a functional contribute to a functional Applications do not system. system. contribute to a functional system. Database - SQL 4 3 2 1 0 Excellent use of a variety of Good use of SQL statements to Adequate use of statements to Limited use of Totally inadequate or not Effective use of SQL in SQL statements to filter/sort/search when selecting filter/sort/search when filter/sort/search when working correctly queries. filter/sort/search when data. selecting data. selecting data. 4 selecting data. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 23 DBE/PAT 2018 NSC Excellent use of Good use of processing/data Adequate use of processing/ Limited use of processing/ Totally inadequate or not processing/data transformation. data transformation. data transformation. done. transformation. Excellent use Good use of formatting for Limited use of formatting for Poor formatting of Complexity of SQL of formatting for calculated calculated fields. calculated fields. calculated fields. interaction fields. Variety of complex queries. Few complex queries. No complex queries. 4 Variety of complex queries, including the use of relationships between tables. Uses all data maintenance Uses all data maintenance Uses all data maintenance Uses some data Totally inadequate or not actions. actions. actions. maintenance actions. done. Data maintenance - Insert/ All actions correctly used. All actions correctly used. All actions correctly used. All actions not correctly Update/Delete records using All applications contribute to a Some applications do not Most applications do not used. 4 SQL functional system. contribute to a functional contribute to a functional Applications do not system. system. contribute to a functional system. Documentation 4 3 2 1 0 Code clearly annotated to fully Code clearly annotated to Code annotated to explain Code annotated to explain No comments or no explain all necessary parts. explain all necessary parts. most necessary parts. certain parts. project notes Explanation shows excellent Explanation shows good insight. Explanation shows some Explanation shows little Comments/Notes insight. Project notes present and of a insight. insight (Explanation of program and 4 code) Extensive project notes very good quality Project notes present and of a Inadequate project notes present and of an excellent moderate standard present standard. Clearly explains working of the program Overall 4 3 2 1 0 Exceeds requirements stated Meets the requirements stated Meets most of the Only meets some Does not meet the in Phase 1. in Phase 1. requirements, but some don't requirements, and some requirements. Comprehensive program. Less comprehensive. function well don't function well. Less than basic. Does the program meet the All elements function as All elements function as Only some program elements Basic program. Limited scope. requirements? function as specified in Phase 4 specified. specified. Basic scope. 1. Shows insight in all aspects. Shows insight in most aspects. Very limited insight. Shows insight in one or two aspects. Total (implementation): 72 Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 24 DBE/PAT 2018 NSC Assessment Summary Phase Focus Maximum Mark Mark Obtained Phase 1 Analysis and Design 60 Phase 2 Coding and Implementation 72 General Final product and impression 18 Total 150 Final mark Declaration of Authenticity 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/Feedback: __________________________________________________________________________________________________________________________________________ __________________________________________________________________________________________________________________________________________ Teacher name: ____________________________________________ Teacher signature: ___________________________ Date: _____________________________________________ Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 25 DBE/PAT 2018 NSC Annexure A – Declaration of Authenticity Learner's name ID Number Grade 12 Year 2018 Subject Information Technology Practical Assessment Task (PAT) Teacher I hereby declare that the contents of this assessment task are my own original work (except for items listed below or 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. List of assistance received: Nature of assistance Person who provided assistance _________________________ ___ / ___ / 2018 SIGNATURE OF LEARNER DATE Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 26 DBE/PAT 2018 NSC Guidelines for teachers to provide guidance What are the learners required to do and provide? Learners are required, with appropriate supervision, to: • Choose an area of interest within the topic/scenario provided • Identify the focus area to be investigated/researched • Plan, research and carry out the project • Write a report to a specified audience • Develop a software solution according to requirements • Provide evidence of all stages of the project for assessment How will learners go about it? The learner will: • Plan and complete an individual project, applying a range of programming and software engineering skills and strategies to meet the objectives as set out by the PAT requirements • Identify questions to ask • Obtain, critically select and use selected information from a range of sources; process and analyse data, apply it relevantly and demonstrate understanding of appropriate linkages, connections and complexities of the topic and focus question • Select and use a range of skills, including design tools and algorithms, solve problems, take decisions critically, creatively and flexibly, to produce a software solution • Evaluate outcomes both in relation to PAT requirements and own learning and performance. • Use appropriate communication skills and media to present evidence in appropriate format. Skills required The learner must be able to: • Do research on the topic and document research findings properly, including citations as specified in the Phase 1 marking grid. • Do a complete user requirement analysis which includes a complete description of the role, activities, requirements and limitations of at least TWO different users of the planned system. • Bring together information to suit the content and purpose • Apply decision-making and problem-solving skills • Extend planning, research, critical thinking, analysis, synthesis, evaluation and presentation skills • Develop confidence in applying the content, programming and software engineering principles and techniques they have studied • Develop and apply skills creatively, demonstrating initiative and enterprise • Seek advice and support when needed Copyright reserved

Downloaded from hlayiso.com Information Technology 27 DBE/PAT 2018 NSC What must the learners be taught beforehand? Before embarking on the PAT the learner needs to be taught the following: • Programming code, principles and techniques • Software engineering principles and techniques including the use of software design • Project management skills including time, resource and task management • The format and structure of accepted forms of research report to include abstract, introduction, discussion with all sources cited, conclusion, references Malpractice Learners may NOT: • Get help/guidance from others without acknowledging this help (complete Annexure A for EACH phase) • Allow other learners to do the programming code of their project • Submit work which is not their own • Lend their PAT work to other learners • Allow other learners to access or use their own work (this does not mean that they may not lend or borrow books to or from another learner, but they may not plagiarise other learners’ research or work) • Include work directly copied from books, the internet or other sources without acknowledgement and recognition (this may not exceed 20% of the work you submit) These actions constitute malpractice, for which a penalty will be applied. If malpractice is identified, the assessment authorities must be notified and details of any work which is not the learner's own must be recorded. Learner declaration of authenticity of the PAT For each phase, learners complete a declaration (Annexure A) for the work done during that specific phase. All substantive advice/help given to the learners should be recorded as part of the phase documents. Copyright reserved

Downloaded from hlayiso.com Information Technology 28 DBE/PAT 2018 NSC Role of the teacher The teacher will teach the information management content, skills and strategies prior to the project. While managing the project and supervising the learners, the teacher will: • Conduct an initial planning review to discuss the topic/scenario, requirements, objectives and development of the project • Facilitate pre-reading to gain background information about the topic/scenario • Give regular feedback to learners, e.g. on their investigation and analysis. • Assess the work of the learners at the end of each phase using the standardised assessment tool and record feedback given. • Endorse each learner's assessment by signing the assessment tools for each phase, including a final declaration that the evidence submitted for assessment is the unaided work of the learner. • Confirm their general evaluation based on continuous observation and feedback to provide a final impression regarding independent work, planning, insight and problem-solving. • Make the assessment of the work of the learners by following any standardising and internal moderation procedures required • Conduct a debriefing session to determine the learner’s understanding and insight of his/her project The teacher will assess the potential project (analysis and design) against the following checklist. • Is the focus area suitable for the project? • Does the focus allow the learner to investigate and to access the higher-level concepts and skills in the assessment objectives, for example to plan, research, analyse, evaluate and explain, rather than simply describe and narrate? • Is the focus area and proposed action clear and focused on an issue which can be managed within the timeframe and available resources? • Do the focus and proposed action indicate that the learner will be capable of investigating and researching the topic and carrying out the activity or task independently and within appropriate ethical or methodological guidelines? • Is the learner likely to face difficulties in understanding the task and issues associated with the focus? The teacher will authenticate the PAT: • Teacher will confirm on the assessment tool that the work assessed is solely that of the learner concerned and was conducted under supervised/controlled conditions • Teacher will sign the assessment tool of each phase Copyright reserved

Downloaded from hlayiso.com Information Technology 29 DBE/PAT 2018 NSC Supervised/Controlled conditions The PAT must be managed in such a manner to be able to confirm that the work assessed is solely that of the learner concerned. Managing the PAT The teacher must plan his/her work schedule according to the time allocated for the PAT in the CAPS document for Information Technology (teaching plan for Grade 12). There are different possible approaches to managing the PAT: Option 1: • The teacher could dedicate a portion of the time on a weekly basis to the PAT while simultaneously continuing with normal teaching to complete the Grade 12 curriculum in the rest of the week. • If he/she chooses this option, he/she should start with the PAT process towards the end of the first term. Option 2: • The teacher could dedicate a continuous period of time to the PAT, for example the week(s) at the end of the second term and the start of the third term. It is suggested that the teacher records the learners' topics/focus when they start with Phase 1 to avoid 'instant projects' that might possibly not be the learner's own work. Evidence of assessment Evidence presented for assessment must show how the individual learner has met the assessment objectives and criteria and include the planning, feedback and progress of the project. The evidence for assessment will include the following: • The project product, including the documentation submitted for each phase • The completed learner assessment tool (for each phase) Copyright reserved

Downloaded from hlayiso.com Information Technology 30 DBE/PAT 2018 NSC Requirements (National Protocol for Assessment Grades R–12, Chapter 3) Practical Assessment Task components must: • Comprise assessment tasks that constitute the learners' PAT mark as contemplated in Chapter 4 of the Curriculum and Assessment Policy Statement for IT • Include a mark awarded for each assessment task (phase), as well as a consolidated mark • Be guided by assessment components as specified in Chapter 4 of the Curriculum and Assessment Policy Statement for IT • Be available for monitoring and moderation • Be evaluated, checked and authenticated by the teacher before being presented as the learner's evidence of performance Non-compliance (National Protocol for Assessment Grades R–12, Chapter 3) The absence of a PAT mark in IT, without a valid reason, will result in the learner, not being resulted for the subject. The learner will be given until three weeks before the commencement of the final end-of-year examination to submit outstanding work or present himself or herself for the PAT. Should the learner fail to fulfil the outstanding PAT requirements, such a learner will be awarded a zero ('0') for the incomplete PAT components. In the event of a learner not complying with the requirements of the PAT, but where a valid reason is provided: • He or she may be granted another opportunity to be assessed in the assigned tasks, based on a decision by the Head of the assessment body. • The learner must, within three weeks before the commencement of the final end-of-year examination, submit outstanding work or present himself or herself for the PAT. • Should the learner fail to fulfil the outstanding PAT requirements, the mark for the PAT component will be omitted and the final mark will be adjusted for promotion purposes in terms of the completed of the tasks. NOTE: In the instance of IT, such a situation is not very likely (unless a learner’s illness spans a long period) as the PAT is not a once-off sitting/assessment. Valid reasons in this context include the following: • Illness, supported by a valid medical certificate, issued by a registered medical practitioner • Humanitarian reasons, which includes the death of an immediate family member, supported by a death certificate Copyright reserved

Downloaded from hlayiso.com Information Technology 31 DBE/PAT 2018 NSC • The learner appearing in a court hearing, which must be supported by written evidence • Any other reason as may be accepted as valid by the head of the assessment body or his or her representative In the event of a learner failing to comply with the Practical Assessment Task requirements of a particular subject, and where valid reasons are provided, the evidence of such valid reasons must be included with the evidence of learner performance. Copyright reserved