Information Technology PAT GR 12 2017 Eng

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

Downloaded from hlayiso.com Information Technology 2 DBE/PAT 2017 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 2017 NSC 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 • To implement higher order and critical thinking skills, formulate strategies and to solve problems on different levels • To develop good working practices to prepare you for the real world, such as: o Time management o Thorough research and 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. In order to achieve good results for your final product, you would have to: • Provide a comprehensive and methodical report that clearly outlines the research and investigation done on the purpose and scope of the project • Provide a possible solution for the task that was identified • Provide a suggested design of what the product will look like The PAT is divided into THREE phases, as explained below: Phase 1: Outlines the project task and solution and provides the relevant research methods Phase 2: A possible design of the project Phase 3: A working, fully documented Delphi program that implements the planned solution NOTE: Submission dates: Specific dates will be determined by your subject teacher. Phase 1: Not later than one week before the end of Term 1 Phase 2: Not later than one week before the end of Term 2 Phase 3: Not later than three weeks before the start of the Grade 12 final examination LEARNERS NEED TO STRICTLY ADHERE TO THE DUE DATES FOR EACH PHASE. 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 2017 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 Research and analysis 30 Phase 2 Design 40 Level 1: Coding and testing (80) Phase 3 100 Level 2: Higher-order solutions (20) General Final product and impression 10 Total: 180 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. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 5 DBE/PAT 2017 NSC The Topic The Entertainment Industry The entertainment industry forms an important part of the economy and includes a large number of sub-industries committed to keeping society continuously engaged in entertainment activities. You are required to plan and develop a software program to manage a local entertainment centre or facility. NOTE: This topic does NOT include sport as a part of entertainment. Examples of topics: • Theatre productions showcasing local talent – keeping a record of details of artists, shows, bookings etc. • Community radio stations – storing details of presenters, programmes, popularity levels, sponsors, advertising, etc. • Community movie centres including titles of movies, dates/times of showing, a booking system, rating system, etc. • Advertising and marketing – local shows can be advertised in newspapers, pamphlets and in other media. • Amusement park – details of rides, gaming, stalls, organisers and other activities at the park. • Museums, aquariums, snake parks etc. Store on site details, staff details, events, number of visitors etc. • Local talent competitions such as best amateur cook, top dancer, top musician, top hair stylist, top fashion model etc.The program must allow the community to register, view events that will take place, view prizes that will be awarded etc. Choose an application/environment that relates to the entertainment 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 on the entertainment industry. 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 9) and Phase 3 marking guidelines (Annexure A). General programming aspects that will be assessed in your project: • Programming style • Graphical user interface (GUI) • Use of sound human-computer interaction (HCI) and software engineering principles • Input/Output management • 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 NOTE: Your final program must comprise one single project with logically related parts. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 6 DBE/PAT 2017 NSC Overview PHASE 1 – ANALYSIS During this phase you have to show that you have done a proper and thorough user requirement analysis in order to determine what users of the system would require it to do. The following can be used as a guideline: • Use the scenario to identify the task, and to outline the purpose, content scope of the task. • Determine the clients/users and their requirements. • Perform the necessary research, for example interviews, surveys, photographic material et cetera. • Provide a methodical report based on the research/investigation carried out. • Provide a list of references and the evidence of research. • Compile detailed requirements and specify what your solution should provide for in order to meet these requirements. NOTE: The user is the target audience and will thus determine the needs and requirements of the program. PHASE 2– DESIGN The purpose of phase 2 is to determine how the program/system will meet the requirements. It needs to provide a well-planned solution. The following must be done: • Clarify the user requirements, indicating specifically how each requirement will be met in your program/solution. • Provide a clear IPO chart to indicate the input, processing and output requirements of the system for at least THREE of the main interfaces. • Use at least ONE relevant software planning tool to clarify the user requirements. NOTE: The following tools can be used in the design process: o TOE charts, ERD diagrams. o Flow charts, UML diagrams (class diagrams and use case diagrams). • Show the design of the database, including the tables, relationships, field names, field types and field sizes • Clearly indicate the logical program flow and navigation between screens. • Show the GUI design following HCI principles of at least THREE different screens, excluding the introductory screens. • Give at least TWO examples of how you would ensure the entry of valid data for the system, using the GUI interfaces that you have provided. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 7 DBE/PAT 2017 NSC PHASE 3 – CODING AND TESTING The purpose of Phase 3 is to implement the design by writing the code and testing the program. The following must be done: Level 1 requirements: Coding and Testing • Write the programming code to implement the design and complete the program. • Use appropriate structures to satisfy the requirements of the algorithms. • Use multi-nested loops and conditional structures. • The use of at least ONE text file is compulsory. Use other data structures where applicable. • Use local and global variables. • Use OOP principles, re-use code, use functions, procedures, methods and objects. • Use relevant validation procedures and components. • Clarify sections of the code by adding comments. • Write project notes to help navigate through the program; provide tool tip texts. These project notes must describe how to interact with the program. The notes must also describe any known bugs or problems. Project notes can be written as part of the help function of the program. • Develop a good GUI and rename relevant components. • Input data using the most effective method, for example a text file, database, keyboard, components. • Process data using the most appropriate methods. • Generate output of data using the correct components and structures, with formatting where needed. • Compile a complex code/string using string-handling techniques. • Ensure smooth interaction between frames/forms/tabs. • Use at least TWO different dynamic components. • Correctly manipulate and query the database. • Demonstrate your program and answer questions about the program and the code during an interview session. Level 2 requirements: Higher-order solutions • Display a drawing/animation/graph/map or timer. • Play a video/thread/networking mobile app or a time-based simulation. • Ensure there are at least THREE calculations, ONE of which must be complex. • Include a variety of at least THREE SQL statements and programming code for file querying and maintenance, such as using aggregate functions, calculated fields, inserting of data, deleting of data and updating of data. • Include complex programming code such as dynamically parameterised queries, that is assigning parameters at runtime. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 8 DBE/PAT 2017 NSC PAT requirements The project must include the following: • Database manipulation through programming language constructs • A multi-form/multi-screen 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. Database The database must: • Have at least TWO linked tables (relational tables) • Involve sufficient volume of data and use a variety of field types (approximately 10 records) • Must be accessed and manipulated by the program using code constructs • Must be accessed and manipulated by the program using SQL statements Text files Your application must use a text file(s) for input and/or output. The data from the text file could be used to: • Do calculations and manipulations in combination with data from the database • Update existing data • Insert/Update records in the database AND/OR • Create report(s) by writing to a text file • Could be used as a help file GUI The graphical user interface (GUI) must have at least: • THREE forms/screens and • TWO components (different types) that are created dynamically NOTE: The mark obtained for your project will be greatly influenced by the quality of the programming code that manipulates the data successfully in order to adhere to the user requirements in the best possible way. Quantity cannot replace variety, effectiveness and quality. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 9 DBE/PAT 2017 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 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 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 30% 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 10 DBE/PAT 2017 NSC Instructions for Phase 1 You need to clearly understand the problem/task at hand. Research/Investigate the topic well so that you have a good idea of what is expected of the software you need to develop. Select a specific application to apply the specifications described in this document. Use relevant research strategies; for example interviews, surveys, photographic material and the Internet. Carefully analyse the needs or application requirements to determine what the programming solution should do and provide. The deliverable of this phase is 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. DEFINE THE TASK Write a brief description (approximately 150 words) in your own words to describe in general terms the problem/task and how the project will solve the problem. In other words, the description should be written to explain your choice of scenario within the topic based on health. 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 The description must give the overall picture of what the purpose and scope of the project is, but not the details. DO RESEARCH The research stage is where you gather facts about the nature of the program you are developing. There must be a minimum of TWO different research methods. Your research should help you clarify the type of program, provide some useful examples that can guide you and should provide a clear understanding of why the particular type of program is suitable for this project. The outcome/summary of the research is a report (approximately 600 words). The report should be written in clear, unambiguous language and should include the following aspects: • Key areas pertaining to the topic • A summary of results derived from the research • The scope and limitations Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 11 DBE/PAT 2017 NSC Provide evidence of research: All/Most material used in the research process must be submitted References: A list of references must be provided to authenticate the research carried out. User requirements: The aim is to derive and establish the user, data and processing requirements of the system, including a consideration of the human aspects (for example a suitable user interface) and the physical environment (for example hardware requirements). Identify the prospective user(s) and identify the user needs and acceptable limitations. • Use a table or a 'use case diagram' to explain the role, activity, requirements and limitations of each user of the program. • Provide evidence of a user acceptance test for users of the program. HAND IN Hand in a document that contains the following: • The project description (approximately 150 words) • A report (approximately 600 words) which contains the following: o A summary outlining the research/investigation/analysis o A conclusion • References • Detailed information on user requirements stating the role, activities and limitations of each user • Evidence of research Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 12 DBE/PAT 2017 NSC Instructions for Phase 2 This is where you plan the detail and provide information on HOW you will go about solving the problem. The aim is to specify and document an overall design that meets the requirements, using software design tools such as IPO diagrams, TOE charts, flow charts, ER diagrams, UML diagrams (use case and class diagrams), clearly annotated. The outcome is a plan showing a high-level overview of how the solution will be constructed using explained/annotated diagrams (or suitable alternative. The plan must show the main blocks/aspects within the proposed solution. Specify and document: • The method of solving the problem • The functions of the constituent parts of the program/system • The interrelationships between the various parts of the program/system • The algorithms, data types and data structures as well as any other requirements of the solution • The effectiveness of the proposed solution in meeting the requirements of the problem DESIGN THE DATABASE The aim is to design a relational database to serve as a data source as well as to manipulate data contained in the database using programming instructions. 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. DESIGN THE GRAPHICAL USER INTERFACE (GUI) The aim is to produce a GUI design that considers good human-computer-interface (HCI) principles that prevents errors occurring due to invalid input and that minimises the amount of information a user has to 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 Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 13 DBE/PAT 2017 NSC • Helpful error messages • Exits – clearly marked, placed correctly • Shortcuts • Flow of information on the screen – top to bottom and left to right • Sensible use of space on the screen. Provide examples of planned data capture and data entry designs (screen dumps may be used from a prototype of the project but must be annotated) and of planned output designs. DESIGN THE SOLUTION (FLOW, ALGORITHMS, DATA TYPES/STRUCTURES, ET CETERA) Use appropriate design tools to design the overall solution, considering all constituent parts and the interrelationships between the various parts of the program/system: • Description of modular structure of the program/system • Definition of data requirements o Structures o File organisation and processing (for example text files) o Validation required • Identification of processes and suitable algorithms for data transformation • Diagrams/Definitions and details of classes, objects, their attributes and methods • Description of measures to ensure security and integrity of data HAND IN Hand in a document that provides the following: • A planned database design • A GUI design • A list of data structures and its use in the program • Software tools used. The IPO design is compulsory PLUS ONE other tool from the given list • Validation techniques • Overall solution design Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 14 DBE/PAT 2017 NSC Instructions for Phase 3 This is where you implement your design by using appropriate software tools (programming language, database software, IDE, et cetera) and techniques to construct 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 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. 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. TEST THE PROGRAM/SYSTEM Test the program/system using clearly defined typical data, erroneous data and boundary (extreme) data. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 15 DBE/PAT 2017 NSC HAND IN Hand in: • The completed Delphi project, including the comments and project notes • The declaration of help received (Annexure C) • The declaration of authenticity (Annexure D) 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. CONCLUSION Upon completion of the Practical Assessment Task, learners should be able to demonstrate their understanding of the industry, enhance their knowledge, skills, values and reasoning abilities as well as establish connections to life outside the classroom and address real world challenges. The PAT furthermore develops learner's life skills and provides opportunities for learners to engage in their own learning Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 16 DBE/PAT 2017 NSC Annexure A: Assessment Tools Phase 1: Name of learner: Scenario (approximately 4 3 2 1 0 150 words) • Task is clearly stated • Task is clearly stated • Purpose and audience • Vague, unsure of the • Totally (purpose and audience) (purpose and audience) not that clear. purpose of the inadequate or • Thorough understanding • Good understanding of • Shortcomings in program. not applicable Scenario of what the problem/task what the problem/task understanding and • Minimal understanding • Poor or no 4 (Short description) involves. involves. coverage of required of what the problem coverage of • Explains a possible • Covers almost all aspects. involves and minimal aspects. solution for the aspects. coverage of aspects. problem/task. Evidence of 6 5 4 2 0 research • Two or more relevant • Two or more relevant • Two or more relevant • One relevant example • No evidence Examples: examples given. examples given. examples given given. of research • Documents • Excellent structure. • Good structure. • Satisfactory structure. • Acceptable structure. provided. (pricelist/invoice • Supports the summary. • Supports the summary. • Supports the • No screenshots, /reports, et cetera) • Excellent presentation. • Well presented. summary. printouts, et cetera. 6 • Screen shots • Presentation • Includes only a few • Interview satisfactory. aspects outlined in • Questionnaires investigation section Report on research 6 4 2 1 0 (approximately 600 words) • Extensive research done. • A large amount of • Acceptable amount of • Limited research • No evidence • Explains deductions from research done. research done. done. of research. each research method • Clearly explains all key • Discussed most key • Vague, too little • No key areas used. areas. areas. coverage of key areas. discussed or • Clearly explains all key • Well explained summary • Acceptable summary. • Brief, incomplete incorrect and Report: Summary of areas. of what the program • Shows reasonable summary. irrelevant or 6 research • Excellent, clear direction should do. understanding. • Minimal not done. for the project, for • Shows thorough understanding. example clearly defines understanding. the scope of the program • Conclusion. • Conclusion Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 17 DBE/PAT 2017 NSC References 3 2 1 0 • All references (at least • All references (at • Some (only 2) • No references All relevant 3) using Harvard/APA least 3) but not using references included or included 3 research style Harvard/APA style incorrect style User requirements 7 5 3 1 0 • Role, activity, • Some shortcomings in • Shortcomings in • Serious shortcomings • Not done or requirements and discussion of role, discussion of role, in discussion of role, incorrect or limitations of at least activity, requirements activity, requirements activity, requirements irrelevant. Role, activity, 2 different types of and limitations of at and limitations of and limitations of users requirements and users of the system least 2 different types users, for example for example most of limitations of the discussed. of users of the system. sections left out. the section were left user 7 • Well documented, • Documented well but • Only 1 user of the out or incorrect neat and to the point. can improve slightly. system discussed. information. (In table format or a • Not well documented • Only 1 user of the use case diagram) but still acceptable. system discussed. • Poorly documented – not acceptable. Presentation 4 3 2 1 0 • Met deadline, all work • One day late but • One day late and • One day late and • More than one Time Management done. complete. almost complete. sections not done or day late, or not 4 – Phase 1 incomplete. done Total 30 Comment/Feedback: __________________________________________________________________________________________________________________________________________ __________________________________________________________________________________________________________________________________________ Teacher name: ____________________________________________ Teacher signature: ___________________________ Date: ___________________________________ Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 18 DBE/PAT 2017 NSC Phase 2: Name of learner: Database design 3 2 1 0 Choice of fields • Well-chosen fields. • The majority of the fields • Most fields do not • No database or • All fields contribute to the contribute to the solution contribute to solution incorrect or irrelevant solution. OR OR 3 • No redundant fields. • One redundant field • More than one redundant field Field types and size • All fields well-chosen in type • Most fields well chosen, • Poor selection of • No database. and size. some poor choices in fields, field types and 3 field types or sizes. sizes in most cases. Appropriateness – • At least two normalized tables • At least two tables. • Only one table/only • Only one table/only the Tables & relationships for solution. • Correct use of fields for the fields listed – no fields listed – no • Appropriate relationship/s relationships between relationships. relationships. between tables. tables. • Correct primary key. • No/incorrect primary 3 • Keys correctly specified in all • Keys incorrectly used in key tables. some instances. OR • No database Role of database (DB) • Clearly describes how the • Manipulation and • Manipulation not well • No database or Describes how the DB will be database will be manipulated in interaction mostly well motivated or mostly incorrect, irrelevant or manipulated, for example the program and how it will described and not suitable to meet unsuitable to the within a dataset, access fields contribute to the solution reasonably motivated. requirements. application. 3 and records, navigate records • All manipulation clearly • Mostly suitable to meet et cetera. motivated requirements. Role of manipulation in program described/motivated. GUI design 3 2 1 0 HCI principles • Well-designed GUI considering • Satisfactory. • Limited consideration • Poor GUI design Does GUI design consider: all 6 aspects for at least three • GUI design considers/ of requirements • Less than three • Purpose of program & user of the main interfaces, meets at least four • At least three requirements • Standard GUI design excluding the introductory requirements for at least requirements for at considered. principles screens. three of the main least three of the interfaces, excluding the main interfaces, 3 • Ease of use, logical flow • Clearly marked introductory screens. excluding the navigation introductory screens • Friendly dialogue • Help Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 19 DBE/PAT 2017 NSC Components 3 2 1 0 Components • Most appropriate components • Appropriate components • Appropriate • Mostly inappropriate used in all cases. used in most cases components used in a components used • Excellent layout. • Satisfactory layout. few cases. OR 3 • All choices clearly substantiated. • Some choices • Layout not satisfactory • Choices not substantiated. • Mostly not substantiated substantiated. Data structures used 3 2 1 0 (excluding database) • Excellent variety of the most • Variety of appropriate • Variety of appropriate • Not described or not appropriate data structures data structures. data structures. substantiated Choice of data • All choices clearly contributes to • One or two data • More than two data OR structures, for example solution, are clearly substantiated structures could have structures could have • No variety arrays, 3 and used in a relevant manner. been replaced with more been replaced with text files et cetera appropriate structures. more appropriate ones (How data will be stored) • Most choices • Some choices substantiated. substantiated. Software Tools: 3 2 1 0 IPO design • Clearly describes all input: • Most input described. • Only some input • No input requirements o Format of the input, for • Minor shortcomings in described. described Input example type, size. descriptions. • Limited description. OR (How input will be o Source of input, such as from Incorrect 3 obtained and managed) the keyboard, text file, array or the database. o GUI component used. • Clearly describes all processing/ • Most processing/ • Only some processing/ • Processing/manipulation Processing manipulation in terms of how data manipulation described. manipulation described. not described. (How processing will be has to be processed/ manipulated • Minor shortcomings. • Mostly limited, • Incorrect or irrelevant. 3 managed – including (algorithms, formulas, validated et incomplete or incorrect database manipulation) cetera). descriptions. • Clearly describes all outputs • Most outputs clearly • Only some outputs • Output requirements not o Format of the output, for described. described. described. example type, size • Minor shortcomings. • Mostly limited, • Incorrect or irrelevant. Output o Source of output, for example incomplete or incorrect (How output will be 3 if the values will be written to a descriptions. managed) text file, array, database or displayed in the GUI o GUI component used Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 20 DBE/PAT 2017 NSC (Any ONE other software 3 2 1 0 development tool) Task-object-event chart • Excellent use of tool that clearly • Tool constructed with • Tool not clearly • No tool, incorrect use of (TOE), Use case diagrams, defines the program. shortcomings. constructed. tool, irrelevant to class diagrams or entity- application. 3 relationship diagrams (ERD) Validation/Error catching 3 2 1 0 • Clearly describes appropriate, • Techniques, • Techniques, • Validation/error catching meaningful, effective validation/error catching validation/error catching not described or totally o Techniques to ensure IPO mostly appropriate and only in some instances inappropriate. (How integrity of input, meaningful for IPO appropriate and processing and output will integrity 3 o Validation/Error catching for meaningful for IPO. be managed) relevant IPO • Only described once or o Error messages associated twice. with validation/error catching Overall 4 3 2 0 • Met deadline. • Good presentation. • Good presentation. • Did not hand in a phase • Excellent presentation. • All work completed. • Some aspects 2. Presentation and time • All work completed. • One day late. incomplete. 4 management • Did not meet deadline. • Not entirely co- operative. Total 40 Comment/feedback: ________________________________________________________________________________________________________________________________________ ________________________________________________________________________________________________________________________________________ Teacher name: ____________________________________________ Teacher signature: ___________________________ Date: _____________________________________________ Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 21 DBE/PAT 2017 NSC Phase 3: Level 1 – Implementation Name of learner: Program aspects 4 3 2 1 0 • All solution algorithms used • Appropriate solution • Most solution • Mostly inadequate • Totally inadequate in solving the problem are algorithms used are algorithms used are solution algorithms or solution Algorithms the most appropriate and effective, with one or appropriate and not effective. algorithms. effective, for example nested two showing minor effective Solution not What does it do? shortcomings. effective. If Else-statement used 4 Does the algorithm effectively instead of multiple solve the task? If-statements and works correctly. It enhances the project. • Used appropriate and most • Used appropriate and • Appropriate and • Inappropriate or • Totally Control structures effective control to solve the most effective control effective use of ineffective use of inappropriate or problem in all instances. structures to solve the control structures in control structures in ineffective. (Conditions, 4 problem in all most instances. some instances. iterations ,et cetera) instances, with minor shortcomings • Most appropriate and • Most appropriate and • Appropriate and • Appropriate and • Totally effective data structures, effective data effective data effective data structures inappropriate or Data structures correctly used (for example structures, correctly structures in most in some instances. ineffective or not (User-defined, arrays, text files, et cetera) to used to solve problem instances. used. 4 excluding DB) solve problem in all all instances – minor instances. shortcomings • At least one text file. • Excellent/Proficient • Mostly good, • Some, interaction • Limited communication • No interactivity. Interactivity/Data flow proficient interaction between modules between interaction between modules (User-defined with parameter passing in at between modules with with parameter modules/units/parts. 4 parameter passing) least two cases. parameter passing in passing in one place. at least two places. • Excellent variety, most • Good variety, • Appropriately and • Appropriately and • Totally appropriate, effective input appropriately and effectively used in effectively used in inappropriate or strategies (database, text effectively used in all most instances. some instances ineffective Input 4 files, user input) used in all instances, but with Limited variety (for • Very limited input (no instances. minor shortcomings. example only two variety/only one type) types) • No logical errors. • One minor logical • Two logical errors. • Many logical errors. • Many logical • All the results of processing error • Some of the results • Many results incorrect. errors. Processing • One result are not correct. • All the results are 4 are correct. problematic. incorrect. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 22 DBE/PAT 2017 NSC • In all cases: • In all cases: • In most cases • In some cases • No output or o Most appropriate o Most appropriate o Appropriate o Ouput difficult to unreadable display, well display, well display. read formatted/readable/stru formatted/readable/str o Satisfactory layout. o Inconsistent layout Output ctured, for example uctured/ 4 headings repeated on understandable, but next page/screen where with minor applicable. shortcomings in one o Excellent layout instance o Good layout • Every effort made to • Good use of defensive • Reasonable degree • Minimal amount of • No attempt at produce a robust program programming where of error checking error checking or validation. Defensive using appropriate necessary but there are with a few obvious defensive programming; 4 defensive programming minor aspects that bugs still present. programming visible. Data validation could be improved on. techniques correctly where necessary. Database design and 4 3 2 1 0 HLL interaction • Use of a relevant • Use of a relevant • Use of a relevant • Use of a relevant • No interaction database with at least two database with at least database with at database or manipulation tables and one two tables and one least two tables and • One table or no database. relationship. relationship. one relationship. • Little interaction with Database design and • Correct fields, types and • Correct fields, types and • Acceptable fields, HLL. sizes. sizes. types and sizes. manipulation within 4 • Excellent, smooth • Good, smooth • Satisfactory HLL interaction with HLL. interaction with HLL. interaction with HLL. • Well-chosen manipulation • Good manipulation • Satisfactory through HLL code through HLL code manipulation through constructs that all constructs that all HLL code constructs contribute to the solution. contribute to the that contribute to the solution. solution. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 23 DBE/PAT 2017 NSC Database manipulation using code constructs. 2 1 0 A separate data module with ADO connection components 2 Correct with no shortcomings Works with minor shortcomings Insert a new record to a table 2 Not done or incorrect Delete a record from a table 2 Edit selected fields in a record 2 View all fields/records; View selected fields/records 2 At least two calculations such as minimum, maximum, sum and average 2 At least one query involving two tables 2 Navigate through records in a dataset, from first, to next, to previous records 2 using methods Filter/sort/search (at least one) 2 GUI 4 3 2 1 0 Ease of use/HCI principles Excellent – all four Good – one aspect Satisfactory – two Limited – more than Poor GUI design. Screens well planned and aspects have been omitted or not used well. aspects omitted or two aspects omitted or Little/no thought designed met and correctly not used well. not used well. given to HCI • Excellent communication used. principles. (screen tips, feedback, help et cetera) • Most appropriate 4 components • Readable/understandable output • Excellent use of effects/ colour/icons/shortcuts, tool tip text, et cetera At least two different At least one dynamically Dynamic Dynamic No dynamic dynamically instantiated component, component(s) used component(s) used component. Dynamic components instantiated meaningfully and meaningfully but that work correctly but 4 components, both correctly used does not work not meaningful meaningfully and correctly correctly used Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 24 DBE/PAT 2017 NSC Documentation 4 3 2 1 0 • Code clearly • Code clearly annotated • Code annotated to • Code annotated to • No comments or no annotated to explain to explain all necessary explain most explain certain parts. project notes. all necessary parts. parts. necessary parts. • Explanation shows • Explanation shows • Explanation shows • Explanation shows little insight. excellent insight. good insight. some insight. • Inadequate project Comments/Notes • Project notes • Project notes • Extensive project notes present. (Explanation of program and 4 notes presentand present of a code) ofaverygoodquality. moderatestandard. presentandofanexcel lentstandard. • Clearly explains working of the program. Scope of variables 3 2 1 0 Use of local and global Use of local and Limited number of No variables used or variables appropriately global variables; but variables – local only or inappropriate use of 3 and effectively – not always global only variables. enhances program. appropriately used. Manipulating string 3 2 1 0 processes Combine multiple string Standard – Combine Simple – single No string methods methods to do complex at least two string manipulation only (only used. manipulation, for example methods use one string method) generate code/key, extracting parts from 3 several DB fields/variables using a combination of several string methods and/or calculations Modular programming 3 2 1 0 (Re-use of code) Re-use of code – Good Re-use of code – Used – inappropriate or No evidence of use of Good use of no parameter modular programming functions/procedures/met functions/procedures/ passing or not working 3 hods/ objects/parameter methods/objects/para correctly passing meters. Limited use of parameter passing. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 25 DBE/PAT 2017 NSC Overall 4 3 2 1 0 • Well exceeds • Exceeds requirements • Slightly exceeds • Meets minimum • Does not meet requirements stated stated in Phase 1. requirements. requirements. minimum in Phase 1 • Less comprehensive. all • Some program • Basic program. requirements. • Comprehensive elements function as elements function • Basic scope. • Less than basic. Does the program meet the specified. as specified in program, all • Very limited insight. • Limited scope. 4 requirements? Phase 1. elements function as • Shows insight in most specified. aspects. • Shows insight in • Shows insight in all one or two aspects. aspects. Presentation 1 0 Time Management – Phase 3 Met deadline, all work done Did not meet deadline or not given in 1 Total (implementation): 80 Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 26 DBE/PAT 2017 NSC Higher-order Programming: The table below determines the complexity level of the program to discriminate between different levels of programs. Phase 3: Level 2 – Higher-order programming skills Name of learner: Aspects 4 3 2 1 0 Play a video/thread/ • Works correctly, is relevant and • Works but could be • Works with minor • Works with major • No attempt has networking mobile app/ appropriate. improved. shortcomings. shortcomings. been made. a time-based simulation • Adds value to the solution. • Relevant and • Relevant and • Relevant and appropriate. appropriate. appropriate. 4 appropriately or any form of complex code. Borrowed code allowed. • Non-trivial, excellent layout and • Good layout and • Satisfactory layout • An attempt has • No attempt has placements. appropriate placement. and placements. been made, with been made. Display a drawing/ • Works correctly, adds value to • Works but could be • Works with minor major animation/graph/map or 4 the solution. improved. shortcomings. shortcomings. timer • Relevant and appropriate. • Relevant and • Relevant and appropriate. appropriate. • Three correct calculations • Three correct • -Two correct • One correct • No calculations. Calculations including one complex calculations. calculations. calculation. 4 calculation. • Three different correct SQL • Three different, correct • Two different correct • One correct SQL • No statements used, one of which SQL statements used, SQL statements statement using SQLstatements or SQL statements 4 must use data from two tables. using one or two tables. using one or two one or two tables. all statements tables. incorrect. • At least 10 records in a table. • Standard, significant • Limited data • Only one record in • No data in tables • Non-trivial input/output and data volume. • Involve only data table • No complex code processing, for example data • Complex, non-trivial storage/retrieval and • Complex code attempted extracted must be processed programming code possibly trivial attempted with further (transformed) to obtain used but could be processing by the major Database package virtually no shortcomings desired result, assigning query improved. Excluding CRUD parameter values at runtime; own code – limited operations modular approach, for example use of programming 4 Complex code and use of procedures/functions language data volume /separate units. • Complex code used • Dynamically parameterised with minor queries (parameters set at shortcomings runtime, embedded in programming language statements by learner). Total (Higher-order programming skills) 20 Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 27 DBE/PAT 2017 NSC General: Final product and impression Name of learner: Aspect 5 4 3 2 1 0 Mark • Each phase of • -Had to re-address • Had to re-address a • More than 50% of • A few of the original development flows minor issues and goals number of issues and original requirements requirements were No requirements met logically from the from previous phases. goals from previous were not met. met. previous phase. • -At least 80% of phases. • Many of original • Did not deviate from requirements were • More than 50% of aspects had to be Flow of development original scope. The met. requirements were changed or scaled up initial goal was • -Some aspects initially met. or down. reached and all the planned were not • Some aspects had to set requirements accomplished. be changed or scaled stated in Phase 1 up or down. were met. • Useful and can be • -Can be implemented • Can be implemented • Not ready to be • Not ready to be implemented as a as a real-life as a real-life implemented as a real- implemented as a real-life application. application with minor application with life application, but has real-life application. • Compares well with adjustments. significant some potential. • Contains limited proprietary software. • -Compares adjustments. • Does not compare with professional features, No requirements met • Contains professional satisfactorily with • Compares to a lesser proprietary software. for example help features, for example proprietary software. extent with proprietary • Contains limited functions, well- help functions, well- • -Contains professional software. professional features, designed GUI layout, designed GUI layout, features for almost all • Contains professional for example help no unexpected errors. Professional project no unexpected errors, aspects, for example features for a functions, well- • User-friendly user-friendly feedback help functions, well- satisfactory number of designed GUI layout, feedback on limited on all aspects and designed GUI layout, aspects, for example no unexpected errors. aspects and features. features. no unexpected errors, help functions, well- • User-friendly feedback user-friendly feedback designed GUI layout, on limited aspects and on most aspects and no unexpected errors, features. features. user-friendly feedback on some aspects and features. • All phases of • Almost all phases of • At least two phases of • One phase of • None of the phases No requirements development were development were development were development was of development were complete and well complete and well complete and well complete and well complete and well designed and designed and designed and designed and designed. Completeness met executed. executed. executed. executed. • None of the phases • All stages and phases • Mostly all stages and • At least two stages • One stage and phase were well well documented. phases well and phases well well documented. documented. documented. documented. Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 28 DBE/PAT 2017 NSC • All phases were handed • Almost all phases • At least two phases • At least one phase • None of the phases in on time and were well were handed in on were handed in on was handed in on handed in on time. designed. time and were well time and were well time and was well Not well designed No requirements met • Work was done designed. designed. designed. • Work was not done regularly. Showed • Work was done • Work was done with • Work was not done regularly. Showed no exceptional commitment regularly. Showed intervals. Showed regularly. Showed commitment and Attitude and and pride in work done commitment and some commitment limited commitment pride in work done. commitment during each stage. pride in work done and pride in work and pride in work • Showed no growth in • Showed exceptional during each stage. done. done. knowledge and skills. growth in knowledge • Showed definite • Showed some growth • Showed limited and skills. growth in in knowledge and growth in knowledge knowledge and skills. and skills. skills. Maximum: 20/2 = 10 Adjustment % Interview 100% of total mark 90% of total mark 75% of total mark 60% of total mark 50% of total mark • Explained all selected • Explained selected code • Unable to explain some • Unable to explain most of • Unable to explain any Explain selected code clearly and with with minor shortcomings of the selected code the selected code selected code % code confidence • Shows insight adequately • Lacks insight • No insight • Shows excellent insight. • Shows some insight Final Project Mark: Copyright reserved Please turn over

Information Technology Downloaded from hlayiso.com 29 DBE/PAT 2017 NSC Assessment Summary Phase Focus Maximum Mark Mark Obtained Phase 1 Analysis 30 Phase 2 Design 40 Phase 3 Coding and implementation 80 Phase 3 Higher order programming skills 20 General Final product and impression 10 Total 180 Adjustment % Final mark (Total x Adjustment %) 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 30 DBE/PAT 2017 NSC Annexure B Anatomy of a report This document informs you of the specific requirements of the report. If you follow these guidelines you will be assured of a successful report. You are expected to use a style sheet so that your report is neat as well as correctly structured. See column 1 below for formatting suggestions. (You can generate a table of contents automatically if you use formatting as outlined in column 1). Report title TITLE PAGE Your name and grade Submission date <title> Overview of the report s essential information and recommendations SUMMARY <heading> TABLE OF CONTENTS List of numbered sections in the report and their page numbers <table of contents> Terms of reference, the scenario and outline of the report's structure INTRODUCTION <heading1> Headings and subheadings which reflect the contents of each section. BODY Includes information on important ideas about the topic, and a discussion of programs relevant to the scenario. Headings <heading1> Subheadings <heading2> States the conclusions that can be drawn from the information found. CONCLUSION Makes recommendations about the direction the learner will follow in the project. <heading1> List of reference material consulted during research for report. REFERENCE LIST Use the Simplified Harvard style/APA style <heading1> Pictures and information that support your research but is not APPENDIX essential to your explanation. <heading1> Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 31 DBE/PAT 2017 NSC Annexure C Learner declaration – Phase ____ 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): _________________________ ___ / ___ / 2017 SIGNATURE OF LEARNER DATE Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 32 DBE/PAT 2017 NSC Annexure D Declaration of authenticity Learner name ID Number Grade 12 Year 2017 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. _________________________ ___ / ___ / 2017 SIGNATURE OF LEARNER DATE Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 33 DBE/PAT 2017 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 • Formulate a focus question that can be investigated/researched • Plan, research and carry out the project • Deliver a report to a specified audience • 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 Please turn over

Downloaded from hlayiso.com Information Technology 34 DBE/PAT 2017 NSC What must the learners be taught beforehand? The taught elements include: • Application software and ICT skills that will enhance the production of the report and the development of the project covering research, analysis and execution • Solution development content and skills, including the ability to define a task • Project management skills, including time, resource and task management • The format and structure of accepted forms of research report to include the abstract, introduction, discussion with all sources cited, conclusion, references Malpractice Learners may NOT: • Get help/guidance from others without acknowledgment (complete Annexure C for EACH phase) • Allow others to do the programming code for their project • Submit work which is not their own • Lend work to other learners • Allow other learners access to, or the use of, their own independently-sourced source material (this does not mean that candidates may not lend their books to another candidate, but candidates should be prevented from plagiarising other learners' research) • Include work copied directly from books, the Internet or other sources without acknowledgement and attribution • Submit work typed or word-processed by another person 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 C) 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. After completing the PAT, learners should sign the declaration of authenticity (Annexure D) to confirm that the work submitted is their own. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 35 DBE/PAT 2017 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 • Agree on the focus question (learners should record the guidance given as part of the Phase 1 documents, for example where appropriate, record their own initial question with clear evidence of the guidance and the final question) • Give regular feedback to learners, for example to formulate a focus question that is suitable and manageable • 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 evaluation based on continuous observation and feedback as well as an interview session to provide a final judgement regarding independent work, insight and problem-solving • Make the assessment of the work of the learners following any standardising and internal moderation procedures required The teacher will assess the potential project (task definition and scope) 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? • Are the focus question 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 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 Please turn over

Downloaded from hlayiso.com Information Technology 36 DBE/PAT 2017 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, completing one phase per term. Option 2: • The teacher could dedicate a continuous period of time to the PAT, for example the last week(s) of each term, also completing one phase per term. 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 a written report of approximately 600 words (content only, without the cover page, table of contents, references, graphics), design documents, final program (fully documented) and other evidence (for each phase) • The completed learner assessment tool (for each phase) Interview Guidelines for the evaluation of the project: • Schedule dates and times for demonstrations – allow about 15 minutes per project. • Take in all the documentation before the demonstration takes place – at least one week in advance – and evaluate the documentation before the demonstration session. • Learners should demonstrate their projects electronically on the computer. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 37 DBE/PAT 2017 NSC • During the demonstration session learners should execute test procedures to show that the entire program is working correctly. • Use the mark sheet for Phase 3 as a guideline and allocate marks accordingly during the demonstration. • As part of the evaluation, identify random pieces of programming code in the project and ask the learner to explain the purpose and working of the randomly selected code. This is done to ensure that the learner did the coding him- or herself. A similar type of procedure will be followed during moderation. If a learner cannot explain the code used in the project, a mark of zero should be awarded for the project. • Make sure that the learner hands in the electronic copy of the project that was demonstrated. Use this copy to allocate any outstanding marks in order to finalise the mark. 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 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 PAT component for IT. 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 tasks. Copyright reserved Please turn over

Downloaded from hlayiso.com Information Technology 38 DBE/PAT 2017 NSC 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 • 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 Copyright reserved