ITGS Project Screencasts

We'll need to create screencasts that show your completed projects at work. Check this link for more info:

http://www.itgsnews.com/2013/01/creating-the-itgs-project-screencast.html

Here's an example:

http://www.youtube.com/watch?v=T4Q_f-uTZgo

Criterion C - Project Schedule

At this point, you should have collected quite a bit of material (or at least know what material you need to collect). Over the break, please create the Project Schedule, which will outline the steps you need to take in order to achieve the results you want.

Here's Yoga's example from last year:

ITGS Project Mark Scheme

Take a look at the descriptions below for achieving and 'Advanced' grade for your Project (I think this will make some of you less nervous about the project):

For info on Cascading Style Sheets (CSS), click here.

ITGS Project Deadlines

Alright 12s, the Project is going to consume a large amount of your ITGS time this year. Please take a look at the following dates:

Criterion A - 7th September

Criterion B - 24th September

Criterion C - 22nd October

Criterion D - 2nd November (Use Comic Life)

Criterion E - 12th December

Criterion F - 18th Jan

Click here for further information on the Criteria.

The dates are subject to change (but they won't change too much!).

Secondly, I want you to look in your ITGS Google Folder where you'll find the 'Forms' for the project. The IB requires that we follow a strict template for submitting work, so make sure you hang onto these files (it would be a good idea to make a blank copy of the Forms right now, in case you want to work on them offline).

Dreamweaver Tutorial #1

Watch the following Dreamweaver tutorial and follow along with the program open. We'll be experimenting with making websites for the remainder of the year.

Feasibility Study

This is the stage where you determine whether or not your proposed solution is even possible.

You need to consider:

Time
Money
Ease of creation

Will you be able to make your product?

Investigation of Existing Systems

Basically, there are two major ways that we will be investigating the current setup of our client.

Questionnaire/follow-up
Interview

By sending the initial questionnaire to your client, you find out what they need assistance with, and you should find out what sort of system they have in place at the moment. It's important that you have a clear picture in your mind of what your client wants to accomplish.

After sending the initial email (or having the initial interview), you need to follow it up with another conversation to get more details. *Remember to document all of this stuff with screenshots, video, sound recordings, etc*

Product Development Life Cycle

Today, we are going to start looking at the PDLC. This is like a more sophisticated version of the Design Cycle that you might remember from your MYP IT classes. The overall process is very similar, but there are more steps and you are required to look deeper into the requirements of your client. Additionally, since your product in this case will be more technologically advanced than those you did in MYP, you'll be creating Instructions for your client.

Here are the major steps in the PDLC:

Investigation of Existing Systems
Feasibility Study
Requirements Specification
Project Schedule
Project Design
Project Development and Technical Documentation
Client and End-User Evaluation, Integration

All of this is covered in section 3.9 (pg 247-252) in your textbooks. Also, check out our Collaborative Document (you need to be logged into your Gmail account to access).

ITGS Major Project

Today, we'll begin discussing the specific format and purpose of the ITGS Project. For more detailed information, check out this document: ITGS MAJOR PROJECT DESCRIPTION. (Whenever you need guidance on what is required for the Project, please refer back to this document!). Here is another really good resource. And another one.

 

Our goal for today is to identify a specific client for whom you will create an IT solution. There are a couple of guidelines:

- the client must be a real person with a real need

- I suggest that the solution be web-based (ie. a webpage), but this is not set in stone. (see the ITGS Mark Scheme)

- all of the official IB documentation policies must be followed in order to get marks for the various Criteria (see ITGS Project Forms)

 

So today, we need to brainstorm potential clients. Who do you know in your life that could potentially benefit from an IT-related creation? This could be a family member, friend, teacher, business-owner, etc. Post some initial ideas about clients on your blog (including some potential problems they might have).

 

Please note the timeline for the project.

Activity	Description(A-D also reviewed by the ITGS teacher before the student can begin to develop the product and has set the Due Date for each stage.)
Informal Contact	Student and client informally meet to discuss the ITGS Project.A date is arranged for an interview.
A:Initial Investigation of the Problem and Interview	Interview is held with the client regarding the problem and requirements and possible solution. Recording methods for the interview could include: written record of the interview (either a summary or transcript) signed and dated by the client, a sound file, a video, or an exchange of emails that may be supported by a questionnaire.The following key questions should be considered in the interview: • What is the problem? • What is the present situation? • What are the inadequacies of the present situation? • What IT solutions could be used to solve the problem?
B:Analysis	The client has reviewed the analysis consisting of two parts:• A completed requirements specification • Justification for the proposed solution
C:Project Schedule	A plan is discussed with the client based on the research into the proposed IT solution and factors involved (stakeholders, software, hardware, network requirements, data, input and output, processes and policies). The plan addresses:• key events in planning, designing, developing, testing and implementing the product in the form of a timeline • any other issues that may arise which may affect the development of the product.
D: Product Design   and client’s signature on the Product Design Form	The Product Design form is discussed with the client. It should include:• design methodologies appropriate to the type of IT product being designed • different levels of draft design, such as the overall structure as well as the internal layout of the product itself. This can also include investigation into specific elements used within the product (such as fonts, graphic elements, effects) • identification of a range of appropriate resources and techniques required for the development of the product • evidence of a test plan that addresses the main areas of functionality of the product • signature of the client to develop the product on the Product Design form
EProduct Development and  on-going consultation with the client as the product is developed	During the product development there must be on-going consultation with the client. The final report will contain a detailed account including:• The structure of the product and why it is appropriate • Complex techniques used including screenshots, in the development of the product, and reasons why they are appropriate for the IT solution. • Additional technical information, if appropriate, that will support the functionality of the product, such as web hosting or security information Any reference material such as templates, program code, applets or other materials that have been used or modified must be acknowledged.
FProduct evaluation and future product development	The first part of this section of the report addresses the evaluation of the product by the client, including any feedback and any problems identified. The second part makes recommendations for the future development of the product. The student will use the client feedback and the evaluation of the specific performance criteria to recommend possible future developments to the product. These recommendations should succinctly explain how possible future developments of the product will be of benefit to the client and/or other stakeholders. Methods such as a written record of the interview (either a summary or transcript) with the client’s signature, a sound file, a video, or an exchange of emails that may be supported by a questionnaire.
G	Technical requirements for submission of the product
Handover	The product is turned over to the client with the necessary documentation and training to use and maintain the product.