Welcome to the ITGS homepage

Criteria G - Due Thurs 12th May 2005

Identifying the Problem In a Social Context

Make sure that you have properly described the inadequacies of the present situation.  Also, that you describe the problem in a social context and that you have identified an end-user

Criteria H - Due Thurs 19th May 2005

Analysis and Feasibility Study

Make sure that you have described two distinct IT approaches that address the problem.  Ensure that you have compared the advantages and disadvantages of each approach.  Also that you have justified your chosen approach with reference to its feasibility and finally that you have justified your chosen approach by explaining how it solves the problem

Criteria I - Due Thurs 26th May 2005

Planning the Chosen IT Solution

Have you provided a detailed schedule of the events involved in the planning, implementation and testing of the product? This includes who does what, and when.

Have you provided visual evidence of the design of the product, either as a storyboard or as detailed diagrams?

Have you fully described the software required (including title, company, version) and explained how it is used?

Have you fully described the hardware required (including model and specifications) and explained how it is used? Web Specs Dell.com

Have you fully described the collection of the appropriate data required for a comprehensive solution to the problem?

Criteria J - Due by the end of February 2006

Testing and Evaluating the Solution

At this stage you create the product. During this process, you modify the product as necessary and collect informal testing information and opinions from me (Mr. Whitmore) and your fellow students. This phase is considered alpha testing and an ongoing process until you feel that the product is ready for beta testing (formal testing).

The following key questions should be considered.

• Does the product work technically?

• Does the product contain all the data that is required?

• Does the product meet the needs of the end-user(s)?

• Is the product effective and fully functional?

Formal testing is conducted by requiring the beta tester and the end-user to record their observations on a questionnaire. The questionnaire and the responses must be included in the appendices.

For your report, you must include:

•  the names of the persons who are involved in the beta testing and end-user testing and 

• state why they are qualified to do this formal testing.

• You must explain the process by which the solution was beta tested (formally tested for technical flaws), refined and then beta tested again by a different person. 

• You must explain the modifications. Before and after screenshots can be included to assist in explaining how the change has improved the product.

The last phase of formal testing is by the end-user who was identified in the “Identifying the Problem” phase. The end-user must evaluate the solution to ensure that the product meets the social need.

The following key questions should be considered.

• Has the product been beta tested for technical and design flaws?

• Has the product been tested for content?

• Has the product been formally tested by the end-user?

• Have all testing processes been formally documented?

Criteria K - Due by the end of February 2006

Assessing the social significance of the product

You must identify and explain two distinct social impacts of the product.

• The observed social impact must emerge from the development or use of the product.

• The projected social impact arises from the student’s perspective of how this product could be used in the future in a wider setting.

The social impact of the product may emerge as you observe the end-user in the testing process and the reactions of users when the final product is made available. You should record your observations in your log book. You should consider what the impact of the product would be if its use was expanded or used in a wider setting.

Criteria L - Due by the end of March 2006

The Product

The product is submitted with the project report and the log book.

Two marks are awarded if the product is technically fully functional, another two marks if the product is appropriately designed and a further two marks if you have developed a comprehensive solution for a complex task.

Criteria M - Due by the end of March 2006

The Log Book

The log book contains regular, dated entries from analysing, planning, testing, implementing and evaluating the process and product. These include references for information, sketches and designs, evaluative comments and other appropriate entries.

INADEQUACIES

State what is wrong with the current situation

Is it inefficient? - Does it take a long time to do or does it take a lot of effort (maybe both)

Is it ineffective? - Does the current way of doing things actually work properly?

Is the current method expensive?  Is it wasteful of resources like paper or power?

Go Back

SOCIAL CONTEXT

Who is involved in the problem?  Who will be helped by your solution.  Who might be effected by your solution?  How will your solution make life easier for people?

Go Back

END-USER

Who will make use of your solution.  Who will further develop it or manage what you have created?  Who will access it?  

Go Back

DISTINCT

Different, not the same, clearly or evidently not like the other

Go Back

COMPARED

Described the two situations and also presented the similarities and the differences between them

Go Back

JUSTIFIED

Given you reasons for why you think it is so.  Offered a reasoned and acceptable argument with proof or evidence

Go Back

FEASIBILITY

Is it possible?  Can it be done? Is it practical?  Is it more than just an idea? 

Go Back

With thanks to Elizabeth Schloeffel at St Peter's College for original content