ITGS: IA Project - ITGS (G12)

ItISS 1 ITGS: IA Project

ITGS: IA Project A Detailed Guide 2011 -‐2012 (HL & SL)

ITGS: Project

ISS International School

Introduction

The ITGS project is a chance for you to put what you have learnt about “Information Technology in a Global Society” into practice. It is therefore important that you approach the project with a passionate open mind because it is this passion that will lead you to solve the problem in the best possible way, thus gaining you the very highest grade. The IB have created a very good overall frame work for you to follow and it is made-‐up of the following three key areas; 1) Log Book. 2) Report 3) Product In this guide we will look at all three sections and list out what you must do and why (and when). As well as the guide, I will list out the steps that you must follow to gain the very best result. However, before you start we must explore the key words that we will use through the project: 1) Client: This is the person that you have selected to create the project for and you are therefore responsible for implementing their project. You need to talk (correspond) regularly with this person. This is the person who has the “social” problem and you only have one client. 2) End User: The end user is anyone who would benefit or use this product. There may be many “end users”. If, for example, you are writing for a teacher who wants to create a “welcome” guide for new teachers, than the possible end user will be the new teachers. 3) IT Solution: This is the product that you will create to solve the problem that the “client” has specified. The solution (also know as the project) must be complex and involve at least 3 IT skills. 4) IT Skills: These are the skills that you will use to create the project. Examples of appropriate IT skills include image editing, video editing, sound editing, using a programming language (C+, Java Script, or Visual Basic) to make a program, using markup language (HTML or CSS) to create a website, creating and editing a database.

Mr Ricketts 2011

V0.1

Log Book The log book shows you and me the process that you go through to complete the project, from your first idea to meetings and everything in between. It is designed to show your thoughts and is very similar to your “MYP” personal project process journal. It is therefore VERY important in order to gain the very highest grade. It should be kept in the best condition and, most importantly, up-‐to-‐date and on paper. You should make sure that it contains the following (minimum requirement): a) Thoughts: these are your thought from day one until the end of the project (handover day). b) Meetings: questions that you want to ask, questions that you have asked (and their response), personal thoughts and anything else to do with the meeting. c) Data: anything that you need to include into the project (facts, figures). d) Sketches: hand drawn ideas of what it might look like or anything else you feel like drawing. e) To-‐do lists: stuff you must do and when. f) Calendars: dates of meetings, timelines, Gantt Charts, etc. g) Screen shots: this is very similar to your grade 10 process journal and should include all that you have done with screen shots and comments. h) ….. Anything else important?!?! Below is an example of what the IB think is a good Journal:

ITGS: Project


Logbook sample

Your log book entry must have the following information: 1. The Date (Formatted like this: 23 January 2000) 2. The Criteria (You may either write out the full criteria or abbreviate it as you see below) 1. Criterion G – Identifying the problem 2. Criterion H – Analysis and feasibility study 3. Criterion I – Planning and developing 4. Criterion J – Testing and evaluating 5. Criterion K – Assessing the social significance 3. Detailed and reflective description of where you are in the process. 4. An illustration, drawing, screenshot, or something visual to go along with the text. You must also make sure that you include an entry for “every” day of the project.

Mr Ricketts 2011

V0.1

The Report

The report is the “bread and butter” of the project and must be completed to the exact formula that has been setout by the IB including using the “correct” form. Roughly speaking it should contain the following: a) 2,000 words (no more than 2000) b) Screenshots c) Storyboards d) Graphs e) Photos f) Appendix (questionnaires, surveys) The following is taken from the IB syllabus: Documentation To assist students in the development and submission of the project, the ZIP file contains the cover page, analysis form, project schedule form and product design form. The documentation must consist of eight files. The final documentation consists of the following. • Information added to forms to provide evidence of the analysis, a project schedule and the design of the product. The information added to the forms must be in the following style(s): –– bullet points or tables to list information –– scanned diagrams or other appropriate images as part of the design process –– other styles of non-extended writing or diagrammatic representation such as flow charts, Gantt charts or spider diagrams where appropriate. This information is not included in the word count unless the student includes extended writing. In this case, the words will be included in the word count. The templates in the ZIP file must be used. • A series of documents that use text (continuous writing) that: –– identifies the client’s problem and explains how the present scenario is inadequate –– justifies the rationale behind the choice and development of the IT solution –– evaluates the success of the product in resolving the existing inadequacies. This is the only information included in the word count and must not exceed 2,000 words. It is recommended that the templates in the ZIP file are used. • Evidence of consultation with the client, such as a written record of the interview (either a summary or transcript), a sound file, a video, or an exchange of emails that may be supported by a questionnaire, providing evidence of the initial consultation and the gathering of feedback from the client after the product is completed. This information must be referenced under the appropriate criterion heading, and is not included in the word count. It is recommended that the name of the client and their occupation and the date of the consultation are clearly stated. Because of the different media that can be used, there are no templates in the ZIP file for evidence of consultation between the student and the client.

ITGS: Project


The Product This is the entertaining part! The product should show 3 IT skills (images, video, web, database, desktop publishing…), but most importantly it “Must” work and be live (completed). Below is an example of a project. In this example the student makes sure that he has a topic and aim that he can achieve in the time allowed (30 class hours) and that he has access to the correct resources that he will need to complete the project.

Video link: http://tinyurl.com/ITGS-sample

Mr Ricketts 2011

V0.1

ITGS Project Steps

1) 2) 3) 4) 5)

Create your journal. First thoughts Keeping your journal Creating your project Writing your report

Step 1: Create (start) Your Journal The very first thing you need to do is to “start” your journal. Select your style of journal and then write your name on the cover. Step 2: First thoughts In your journal you need to write your first thoughts following the guidelines. A) Brainstorm: using the correct software (mind map software), you need to create a detailed brainstorm on your project, using what you have discussed with your end user to create basic structure. (Glue this into your journal) Example:

B) Basic project details: Who (who are you creating the project for), What (what are you creating, When (when is the project due) Why (why are you creating the project/ social significance). C) First Interview: when is this going to be and what are your possible questions. The following key questions should be considered: • What is the present system? • How does it work? • What are the limitations of the current system? • What is the problem? • Who will benefit from an IT solution? A specific IT solution must not be identified at this stage. • Has the need been determined through discussions with relevant people and end-‐user(s)?

ITGS: Project


D) Possible Alternatives: You need to list what ideas you have and what are the possible alternatives. Step 3: Keeping your journal. Your journal will be checked every lesson and must therefore be kept up-‐to-‐date. You must aim to update your journal once a day, even if you are not completing a major part of the project. Please follow the guide above for more details.

Mr Ricketts 2011

V0.1

Appendix

ITGS: Project


Appendix 1: Student Checklist Students should consider the following checklists when completing the project. It is recommended that once each section is completed the student uses the appropriate checklist to ensure they are on course.

Criterion A: Initial investigation Initial investigation A client has been identified. A problem that requires an IT solution has been identified from the consultation with the client. The inadequacies of the current system have been explained from the consultation with the client. The word count for the initial investigation is approximately 250. The initial investigation is linked to the cover page.

Initial consultation with client Evidence of the consultation with the client has been included. The evidence of consultation has been linked to the cover page.

Criterion B: Analysis The analysis form has been used. The solution has been identified.

Requirements specification The proposed product is realistic in terms of time constraints, resources and the student’s ability to develop it.

Specific performance (success) criteria Specific performance criteria have been drawn up that make it possible to evaluate the success of the product in criterion F.

Justification of the proposed solution A feasible solution has been identified. The choice of the solution has been selected that resolves the inadequacies identified in criterion A. The justification of the proposed solution is approximately 350 words.

Criterion C: Project schedule The project schedule form has been used. The project schedule refers to the solution identified in criterion B. The project schedule is updated during the lifetime of the project. The project schedule provides a realistic plan and timeline for managing the project including the gathering of necessary information, the development of the product and the

Mr Ricketts 2011

V0.1

testing process.

Criterion D: Product design The product design form has been used. The product design refers to the solution identified in criterion B and the project schedule in criterion C. The product design includes a range of design levels. The product design includes a table of assets and a table of techniques required in the development of the product. The product design identifies at least three advanced techniques that will be used in the development of the product. The product design is presented in sufficient detail for an IT-literate third party to understand how the product was created. The test plan proposed addresses the main types of test appropriate to the product and relates to the specific performance criteria identified in criterion B. There is evidence of agreement with the client to develop the product.

Criterion E: Product development The different techniques used to develop the product have been identified. The product includes at least three complex techniques identified in criterion D. The appropriateness of the product structure has been justified. Screenshots along with justifications have been used to illustrate the choice of the techniques used to develop the product. All sources have been cited using an appropriate referencing style (for example, Harvard, MLA). The technical documentation is approximately 1,000 words.

Criterion F: Product evaluation and future product development Feedback from client Appropriate feedback has been obtained from the client. The evidence for the consultation to obtain feedback from the client has been linked to the cover page.

Product evaluation The evaluation refers to the requirement specifications in criterion B and the test plan in criterion D. The evaluation explicitly refers to the feedback obtained from the client.

Future product development The recommendations are appropriate to the client for the future development of the product.

ITGS: Project


The product evaluation and future product development is approximately 400 words.

Criterion G: Required elements Evidence of testing and functionality The product has sufficient extent to enable its effectiveness and functionality to be evaluated. The product has been thoroughly tested in a range of situations to ensure that no tests will fail. The tests used to ensure the functionality correspond to those in the completed test plan.

Cover page The cover page template has been used. The student’s details have been added where appropriate. The cover page has been saved in HTM/HTML format.

File naming and folder structures One folder called “product” has been created, which holds the product. The product folder structure is intuitive and allows files to be located easily. One folder called “documentation” has been created, which holds the eight documentation files: there are no other files or subfolders within this folder. The documentation is easy to navigate and uses the file names prescribed in the guide. All links within the project are relative. There is appropriate use of file names throughout the project.

Final check The organization of the project prescribed in the guide has been adhered to. The project is no more than 2,000 words. The links within the product and documentation (where appropriate) are relative, allowing portability. The project has been tested in more than one location under different conditions. The correct forms have been used for the cover page, analysis, project schedule and product design. There are no appendices in the project.

Mr Ricketts 2011

V0.1

Appendix 2: Assessment criteria Internal assessment criteria—SL and HL

Criterion A: Initial investigation Marks

Level descriptor

0

The work does not reach the standard described by the descriptors below.

1

A client and a problem with the present situation are identified.

2–3

A client is identified. The inadequacies of the present situation are explained with cited reference to the consultation with the client.

Criterion B: Analysis Requirements specification The specific performance criteria within the requirements specification will be used in criterion F to evaluate the effectiveness of the product. Justification of proposed solution This is completed in extended writing. Marks Level descriptor 0


1

The analysis form is used, refers to the scenario described in criterion A and includes either a requirements specification that can be used to partially evaluate the effectiveness of the IT solution or a limited explanation of why the IT solution was chosen.

2–3

The analysis form is used, refers to the scenario described in criterion A and includes a requirements specification that can be used to partially evaluate the effectiveness of the IT solution and an adequate explanation of why the IT solution was chosen.

4–5

The analysis form is used, refers to the scenario described in criterion A and includes a requirements specification that can be used to effectively evaluate the success of the IT solution and a detailed justification of why the IT solution was chosen.

Criterion C: Project schedule The project schedule must include the following. • Dates • Actions • Details Marks Level descriptor 0


1

The project schedule uses the project schedule form and refers to the

ITGS: Project


proposed IT solution identified in criterion B, providing an outline schedule of the tasks involved in planning, designing, developing, testing and implementing the IT solution.

2–3

The project schedule uses the project schedule form and refers to the proposed IT solution identified in criterion B, providing a detailed schedule of the tasks involved in planning, designing, developing, testing and implementing the IT solution. The project schedule can be used as a basis for the development of the IT solution.

Criterion D: Product design There are four significant components to the product design. • Overall structure • Internal structure • List of resources • List of techniques The following information should also be included as part of the product design. • Test plan • Agreement of client Marks Level descriptor 0


1–2

The product designs for the IT solution identified in criterion B use the product design form but have significant omissions. It is possible for the student to create the product from them, but they lack sufficient detail for an IT-‐literate third party to see how the product was created.

3–4

The product designs for the IT solution identified in criterion B use the product design form and include sufficient detail for an IT-‐literate third party to see how the product was created.

Criterion E: Product development The student must demonstrate the techniques, with screenshots, that were used to develop the IT solution identified in criterion B for the client identified in criterion A and justify why they have been used. A complex product is defined as one that includes at least three appropriate advanced techniques. The list of techniques will be posted on the OCC annually. Marks Level descriptor 0


1–2

The IT solution identified in criterion B is created. The techniques used to develop the complex product are identified or the techniques used to develop the simple product are described.

3–4

The IT solution identified in criterion B is created. The structure of the

Mr Ricketts 2011

V0.1

complex product and the techniques used to develop it are described (with screenshots) or the structure of the simple product and the choice of techniques used to create it are justified (with screenshots). 5–6

The IT solution identified in criterion B is created. The structure of the complex product and the choice of techniques used to develop it have been explained (with screenshots), with minor omissions. Sources have been acknowledged.

7–8

The IT solution identified in criterion B is created. The structure of the complex product and the choice of techniques used to develop it have been fully justified (with screenshots). Sources are cited appropriately.

Criterion F: Product evaluation and future product development The student must evaluate the effectiveness of the finished product, based on feedback from the client. This must include direct references to the specific performance criteria identified in the requirements specification as part of criterion B. The student must recommend proposals for future improvements of the product. Marks Level descriptor 0


1–2

A limited evaluation of the product, based on feedback from the client is completed, and superficial and impractical recommendations are made for its further development. There is limited reference to the specific performance criteria identified in the requirements specification.

3–4

The product is evaluated, based on feedback from the client and the specific performance criteria identified in the requirements specification, and appropriate recommendation(s) are made for future development of the product.

Criterion G: Required elements This criterion assesses the extent to which the three formal requirements are met. • The content within the product is sufficient for an IT-‐literate third party to reliably evaluate its effectiveness and the product functions as required. • The prescribed cover page is used and functions as required. • Appropriate file names and folder structures are used throughout the project. Marks Level descriptor 0

None of the formal requirements are met.

1

Any one of the formal requirements is met.

2

Any two of the formal requirements are met.

3

All three of the formal requirements are met.