Major proj term3

Hillcrest Christian College

Hillcrest Christian CollegeInformation Processing and Technology

SEMESTER 2 2011

NAME: Mark Johnman DATE: 16/08/11

ASSESSMENT ITEM NO Yr 11, Yr 12

TYPE OF ASSESSMENT Formative (Yr11) Summative (Yr12)

ASSESSMENT TECHNIQUE Major Project, Individual

ASSESSMENT CONDITIONS Unsupervised

6 weeks

DUE DATE 23/09/11

TOPIC/S ASSESSED Algorithms

Software Programming

Human-Computer Interaction

Social and Ethical Implications

CRITERIA ASSESSED Knowledge & Application

Analysis & Synthesis

Evaluation & Communication

Results

Knowledge & Application A+

Analysis & Synthesis A+

Evaluation & Communication A

CONDITIONS

of 18


All

assignments in this subject rely on the presentation of work in either word processed form or as software on h drive; as such the backup of data is essential. The loss of work through the failure of hardware or poor file management procedures will NOT be accepted as a reason for the non-submission of work. Failure to meet deadlines because of these reasons will attract the same penalty as non- completion.

DISCLAIMER

I certify that this assignment is entirely my own work and all sources that were used in its preparation were correctly acknowledged. I have not shared my work with other students.

NAME: M. Johnman SIGNATURE: __________________

of 18


ASSIGNMENT RECEIPT

This is to acknowledge the receipt of the assignment Term 3 Major Project on 23/09/11 from student Mark Johnman.

_______________________Mr Nick Miles

Task

You are required to design, implement and evaluate a single page web application for a particular functional purpose or client (proposed by you) using Javascript, HTML and any other approved W3C language (i.e. CSS, XML).

The project is broken into four phases, with submission required at each phase.

You are required to maintain a daily log that records date, location (home or school), activities undertaken, and any problems identified. This will form part of your assessment and must be submitted with each phase.

Use the Design -> Develop -> Evaluate cycle as specified below.

Required Elements

To think about:

Your completed proposal must include appropriate explanations at each stage of the software development cycle.

You will need to keep a log of work in progress and to complete a project plan and status report so that your team leader can view your progress at any time.

Your audience for your proposal is the client who will be responsible for deciding on future funding for your project.

Your purpose is to convince them you have a worthwhile concept and that your project should be supported by further development.

Once you have decided on which project to tackle, you must negotiate with your team leader (teacher) for tentative concept approval.

A suitable application should be as fool proof as possible.

of 18

Hillcrest Christian College The proposed application should reflect the aspects of good program design such as

validation, error trapping and confirmation. The resulting project should include a use of a range of data structures including text or

data files, arrays, and records and should also involve string manipulation. Your purpose of this major project is to demonstrate your competency within all design

aspects of the software development cycle. Implementation of the design into a working application is a required aspect of this

project and program code will be marked. Some assistance may be given with implementing more complex and advanced sections of the code from a prepared design (ie you must know what it is you want to do before you ask how to do it)

The program should be well documented and should come with a user manual.

of 18


Method

PHASE 1 Problem DefinitionThis step will consist of a clarification of the task as outlined above. It may be broken into two main parts: an aim for your task, and a general problem description.

The aim is a simple, clear statement of what you wish to achieve, why it needs to be completed and what will be provided at the completion of the project. This section could include a discussion of the particular needs of the identified prospective users and the areas of their work that might be improved by the use of your software solution (if developing a game discuss instead, the target audience and the requirements to make the game a success for that particular user group).

The general problem description is a restatement of the task in your own words. This may include creative detail (the name of your consultancy group, imaginary background information). Please note this is a general representation of the taskdo not go into specific detail.

Discuss assumptions, limitations, proposed users (if a game, you have addressed in the aim) and expected results of the project.

Suggested Documentation: Keep the marked copy of this step for inclusion with final documentation. Record the time spent on this step in your logbook update project plan and status report.

PHASE 2 Design

Phase 2a SpecificationWorking from your problem definition, develop a specification for the task. This will involve a detailed description, step by step, screen by screen, of how the program will run. It will clearly identify input and output data, and calculations to be performed.

To assist in developing the specification you may follow this guide: list all choices the user can make identify all outputs the program should supply establish what data must be read from and written to disk (in detail) determine what calculations the program must perform (do not yet

worry about how these are to be carried out) identify any ways you can improve the appearance, presentation,

user friendliness, or user proofing of the application.

Identify any help such as online help or a User Manual that will be included

Once the above are listed, arrange them in order as the program will run (eg. number them in sequence). Translate this information into a fluent description in coherent, connected paragraphs.

Add screen designs (sketched or using a paint program) that show how the specification will be implemented. This section should give the reader a very clear idea of what the program will look like and how it will work regardless of the programming language chosen. Decide on object names and variable names

of 18

Hillcrest Christian CollegeDocumentation: Make a copy of the specification and screen designs for final documentation. Record activities carried out in your own logbook and update project plan and status report.

Phase 2b Top Down Design Chart

Take your specification and using the top-down method prepare a Top Down design chart for the application. This chart should break the task into modules and sub-modules, as necessary. The bottom level sub-modules should be simple enough so that they can be represented in pseudocode.

Phase 2c Algorithm Design

Prepare detailed algorithms in pseudocode for each of the bottom level modules in the structure chart. Arrays should be employed where effective, and selection and iteration should be used appropriately. Where necessary include user proofing. Outline all the steps required in each module of the algorithm consistent with your top-down design, making best use of indentation and appropriate naming conventions to elaborate your code structures.

Documentation: Keep a copy of your marked structure chart and algorithms for final documentation. Record time taken and problems encountered in your logbook and update project plan and status report.

Consultation

Following submission of these first two stages, consultation will be conducted with the teacher. At this stage, a model structure chart will be presented. You have the choice of adjusting your algorithm after this consultation.

Documentation: Any amendments as a result of this consultation should be documented. Record all amendments in your logbook to assist with final documentation and evaluation.

PHASE 3 Implementation

Phase 3a Implementation

Begin coding your program using JavaScript, an object-oriented programming Web language. The program must use procedures to reflect the modular nature of the design. Appropriate data types and arrays are to be employed. It is expected that you use module testing to develop the program. The listing is to exhibit effective internal documentation, appropriate indentation and the use of meaningful names for components and variables.

If necessary assistance with the algorithm needed to run the program will be provided at this stage but any assistance received will be documented in the final production.

of 18

Hillcrest Christian CollegePhase 3b Documentation of ImplementationExplain your implementation so that your proposal may be presented at the Meeting of Directors of your company without the need for the Directors to actually view the program. Include screen captures or sample views from your program.

Documentation: Make a copy of the final code listing for final documentation. Record: time taken, problems encountered, and activities carried out in your own logbook and update project plan and status report.

of 18


PHASE 4 Testing and Evaluation

Phase 4a Testing

Ensure the program compiles and runs with no errors. Test the program with extreme conditions and values to try and cause it to “crash”. Correct if possible. Allow a non-IPT student to run the program and observe how easily they can use it and follow on-screen instructions. Try to arrange testing by prospective users. Record results and observations for your evaluation.

Documentation: Detail all tests conducted for final documentation. Record: time taken, problems encountered, and activities carried out in your own logbook and update project plan and status report.

Phase 4b Evaluation

Once the application is completed prepare an evaluation of what you have done. This will cover aspects such as:

determine if the application produced meets the specifications you established

explain which parts of your planned design have been successfully implemented

comment on the performance, reliability, and ease of use of the application (refer back to comments made at the testing stage)

suggest possible alterations and improvements that could be made

Documentation: All of the above plus logbook entries and updated project plan and status report.

Phase 4c Final Documentation

All steps will be combined (including marked work) and submitted as documentation of the project. Each individual is to submit the following (in order):

a title page indicating: name, project title, due date criteria sheet table of contents (optional but recommended) aim of the application general problem description copy of screen designs algorithms (Top Down design chart/ pseudo code) copy of the program on disk (with data file) documented explanation of the project User Manual evaluation: meeting specifications, performance and improvements logbook project plan and status report.

of 18


Conditions

1. One or two lessons per week will be allocated to prepare the project. This reflects integration with other topic areas.

2. A logbook must be kept of your participation in this project.

3. The project plan and status report must be kept up-to-date at all times throughout the project.

4 Throughout the project you will be given direction on what to do next, and feedback on how you are performing. Teacher assistance will be provided as requested to clarify methods and format and to redirect where mistakes have occurred.

5 Students who depend on teacher direction will need to clearly document that assistance and levels awarded will be adjusted accordingly.

6 Interim due dates apply. No extensions will be granted for interim work.

7 Applications for a final extension must be applied for before the due date. It is your responsibility to keep a current backup of data. Loss of data for any reason will not be accepted as grounds for an extension.

While not a requirement of the project, it is strongly recommended that all written work be word processed.

of 18

Hillcrest Christian CollegeName: .Mark Johnman

Hillcrest Christian College, Gold Coast Senior IPT 2011, SSE3

Software Programming Major Project

Standard Achieved

A=excellent, B=good, C=satisfactory, D=unsatisfactory, E=poor, not shown K&A A&S E&C

Phase 1 Definition

Synthesis of aim A A

Appreciates the importance of an accurate problem definition A A

Analysis of task and synthesis into a clearly communicated general problem description

A A

Use of appropriate language A A

Identification follows conventions of spelling, grammar and neatness A

Phase 2a Specification

Appreciates the importance of accurate program specification A A

A specification for the application that identifies and clearly communicates: A

all required inputs and outputs A

all calculations the program must carry out A

the presentation for the user interface A

a suitable sequence of events A

follows conventions of spelling, grammar and neatness A

Make appropriate use of programming terminology A A

Screen designs that are: (HCI)

detailed and complete A

indicate consideration given to user friendliness A

effective and well presented A A

Phase 2b & 2c Design

Development of specification into a sufficiently detailed chart that represents the principal elements of the task

A

Appropriate level of modularisation A

Neatly presented structure chart A A

Efficient and appropriate use of control structures to meet design goals A

Effective, workable algorithms to manage tasks A

Use of meaningful identifiers A A

Varied use of structures such as iteration and selection A

Appropriate use of arrays to manipulate data A

Inclusion of user proofing (HCI) A

No logic errors A A

of 18

Hillcrest Christian CollegeAchievementA=excellent, B=good, C=satisfactory, D=unsatisfactory, E=poor, not shown

K&A A&S E&C

Phase 3a Implementation

The application:

compiles and runs correctly with no syntax errors A

is user friendly (HCI) A

is user proof in use (HCI) A

makes use of effective typefaces and colour for display (HCI) A

has forms with well proportioned and aligned components (HCI) A

uses appropriate components A

sets appropriate and effective properties for components A

is consistent in naming components A A

reflects the modular nature of the design A

employs appropriate data types A

uses appropriate assignment of values to variables A

displays internal documentation A A

uses internal documentation effectively A

Phase 3b Documentation

Follows conventions of spelling, grammar and neatness A A

Hard copy of application provided appropriately A

Explanation of implementation is appropriate for Directors’ meeting A A

Phase 4 Testing and Evaluation

Evaluation clearly communicates:

conformity to specifications A

performance, reliability and ease of use (HCI) A

clearly documents user testing A

suggested alterations and improvements A A

follows conventions of spelling, grammar and neatness A A

Phase 4c Documentation

Well compiled, complete, and neatly presented submission A A

Appropriate user manual/user help included in the project (HCI) A A

Work-in-progress continually documented on project plan and status report

A A

Logbook complete and detailed A A

of 18


PROJECT LOG and DECLARATION

I, ................................................................................ declare that all sections of the IPT project submitted by me are entirely my own work unless otherwise indicated.

Signature: .....................................................................

Date: ............................................................................

Date Details Signature

of 18


STATEMENT of STANDARDS Major Project Algorithms Theory and Design 2, Software Programming

NAME: Mark JohnmanPhase 1 & 2

K&A Criterion A B C D EProblem Definition Detailed description of

problem identifying needs of client, likely users, limitations and assumptions.

Detailed description of problem identifying most needs of client, likely users, limitations and assumptions.

Problem definition of problem identifies some needs of client, likely users, some limitations and some assumptions.

Problem definition does not adequately describe problem to be solved.

Definition absent or inappropriate.

Solution Specification Detailed solution specification including ,

UI descriptions, All objects and properties

named appropriately. All object uses identified All inputs and outputs

Complete solution specification including most:

UI descriptions, Objects and properties named appropriately. object uses identified inputs and outputs

Majority of solution specification including:

UI descriptions, Objects and properties named appropriately. object uses identified inputs and outputs

Some of solution specification including:

UI descriptions, Objects and properties

named appropriately. object uses identified inputs and outputs

Few or no aspects of solution specification presented.

Algorithm Design Correct algorithm with appropriate structures for: sequence loops selection module callsused consistently.

Mostly correct algorithm with appropriate structures for: sequence loops selection module callsused consistently.

Majority of algorithm correct with appropriate structures for: sequence loops selection module callsused consistently.

Some of algorithm correct with appropriate: sequence loops selection module callsused consistently.

Little of algorithm correct with appropriate: sequence loops selection module callsused consistently.

Use of meaningful identifiers and data types and structures identified throughout algorithm

Mostly meaningful identifiers and data types and structures identified throughout algorithm

Some use of meaningful identifiers and data types and structures identified throughout algorithm

Few meaningful identifiers used or data structures or types identified

Little or no use of meaningful identifiers or data types identified

Presentation Complete package, title page, index. Organised & sequential. Few spelling, punctuation errors. Follows conventions and grammar.

Mostly complete package, title page, index. Organised & sequential. Minor spelling, punctuation errors. Mostly follows conventions and grammar.

Majority of package, title page, index. Organised & sequential. Some distracting spelling, punctuation errors orf grammatical.

Some elements title page, index presented. Some distracting spelling, punctuation errors and grammatical errors

Few elements presented distracting spelling, punctuation and grammatical errors.

of 18


A&S Criterion A B C DSolution Specification Comprehensive analysis of

task and synthesis into a clearly communicated detailed and complete solution specification

Analysis of task and synthesis into a clearly communicated detailed and complete solution specification over most aspects

Analysis of task and synthesis into a clearly communicated detailed and complete solution specification over some aspects

Analysis of task and synthesis into a clearly communicated detailed and complete solution specification over few aspects

Algorithm DesignAnalysis

Algorithm shows ability to break down problem into modules is detailed and complete. All elements of problem have been addressed.

Algorithm shows ability to break down problem into modules and is complete. Most elements of problem have been addressed.

Algorithm shows some ability to break down problem into modules. Some elements of problem have been addressed.

Algorithm little or no ability to break down problem into modules few elements of problem have been addressed.

Algorithm logic correct & ordered, accurately traces required step for problem solution.

Algorithm logic mostly correct & ordered, traces required step for problem solution.

Some aspects of algorithm logic correct for problem solution.

Few aspects of algorithm logic correct for problem solution.

Algorithm successfully combines all elements of specification into a sufficiently detailed Top-Down Design

Algorithm successfully combines most elements of specification into a sufficient Top-Down Design

Algorithm successfully combines some elements of specification into a Top-Down Design

Algorithm combines few or no elements of specification into Top-Down Design

Communication Documents successfully convey intent of project with correct genre and format used throughout.

Intent of project successfully conveyed and correct genre and format used through most of document.

Intent of project successfully conveyed and correct genre and format used through some of document.

Intent of project not conveyed and correct genre and format not used through most of document.

of 18


Phase 3 & 4 K&A Criterion A B C D E

Implementation Effective and consistent use of colour, space, font, suitable form objects across suite of modules

Effective and consistent use of colour, space, font, suitable form objects across most modules

Effective and consistent use of most aspects of colour, space, font, suitable form objects across most modules

Effective and consistent use of colour, space, font, suitable form objects across some modules

Ineffective and/or inconsistent use of colour, space, font, suitable form objects across modules

Code Appropriate data types/structures used throughout the project

Mostly appropriate data types/structures used throughout the project

Some data types/structures used are appropriate

Few data types/structures used are appropriate

Data types/structures used are not appropriate

Meaningful names following convention consistently given to controls and variables

Meaningful names following convention given to most controls and variables

Meaningful names following convention given to some controls and variables

Meaningful names following convention given to few controls and variables

Variable and object names lack meaning or do not follow convention

Extensive and affective use of comments to explain and identify structures and their purposes

Wide use of comments to explain and identify structures and their purposes

Some use of comments to explain and identify structures

Little use of comments to explain and identify structures

No use of comments to explain and identify structures

Consistently appropriate use of loops structures and branching/testing.

Appropriate use of loops structures and branching/testing.

Use of loops structures and branching/testing.

Either loop or branch statements present

No looping or branching present

Evaluation clearly documents an extensive testing procedure

Evaluation documents an adequate testing procedure

Evaluation documents some testing procedure

Evaluation documents little testing

No testing documented

Documentation All documents present and formatted consistently to a high standard with few or no spelling or grammatical errors

Most documents present and formatted consistently to a high standard with few or no spelling or grammatical errors

Majority of documents present and formatted consistently with few some spelling or grammatical errors

Some documents presented little consistency of formatting with spelling or grammatical errors

Few or no documents presented little consistency of formatting with spelling or grammatical errors

A&S Criterion A B C DCode Program complete and

working to solution specification. No errors or bugs.

Program complete and working to solution specification. Some errors or bugs.

Program mostly complete and working to solution specification. Some errors or bugs.

Some aspects of program complete and working to solution specification. Some errors or bugs.

Code matches algorithm closely with any variations documented and explained

Code matches algorithm with some variations documented and explained

Code matches algorithm some variations

Code bares little resemblance to algorithm and

Documentation All aspects of documentation presented to a high level with appropriate format and layout

Most aspects of documentation presented to a high level with appropriate format and layout

Some aspects of documentation presented to a high level with appropriate format and layout

Few or no aspects of documentation presented to a high level with appropriate format and layout

Evaluation Comprehensive alterations and improvements identified and communicated

Appropriate alterations and improvements identified and communicated

Some alterations and improvements identified and communicated

Few or no alterations and improvements identified and communicated

Very high level of communication used to convey a. constructive

High level of communication used to convey a. constructive assessment of project

Good level of communication used to convey a. constructive assessment of project

Poor level of communication used to convey an assessment of project.

of 18


assessment of project.

HCI

K&A Criterion A B C D EInterface Design All elements of UI screen

designs detailed and complete and incorporate consideration for user

Most elements of UI screen designs detailed and complete and incorporate consideration for user

Majority elements of UI screen designs detailed and complete and incorporate consideration for user

Some elements of UI screen designs presented or are not detailed nor complete

Some elements of UI screen designs presented or are not detailed nor complete

All UI designs effective and well presented

Most UI designs effective and well presented

Majority of UI designs effective and well presented

Some of UI designs effective and well presented

Few or no UI designs effective and well presented

ImplementationScreen Designs

Effective and consistent use of colour, space, font, suitable form objects across suite of modules

Effective and consistent use of colour, space, font, suitable form objects across most modules

Effective and consistent use of most aspects of colour, space, font, suitable form objects across most modules

Effective and consistent use of colour, space, font, suitable form objects across some modules

Ineffective and/or inconsistent use of colour, space, font, suitable form objects across modules

User Help Detailed and effective on line help and user manual incorporated throughout project

Good level of effective on line help and user manual incorporated throughout project

Some on line help and user manual incorporated in most parts of project

Some on line help or user manual incorporated in most parts of project

Little or no on line help or user manual incorporated in most parts of project

Code Appropriate user proofing such as error traps, passwords incorporated into project

Appropriate user proofing such as error traps, passwords incorporated into most of project

Some user proofing such as error traps, passwords incorporated into most of project

Little user proofing such as error traps, passwords incorporated into project

No user proofing such as error traps, passwords incorporated into most of project

A&S Criterion A B C DUser Interface Consideration of aspects

user friendliness identified at all stages of development

Consideration of aspects user friendliness identified at most stages of development

Consideration of aspects user friendliness identified at some stages of development

Little or no recognition of aspects of user friendliness.

Components combine to form an intuitive UI, appropriate screen messages (clear/timely). Appropriate help/tool tips

Most components combine to form an intuitive UI, appropriate screen messages (clear/timely). Some appropriate help/tool tips

Some components combine to form an intuitive UI, appropriate screen messages (clear/timely). Few help/tool tips

Few components completed and little effort to make a coherent interface. Few or no help/tool tips

Code Appropriate error catching devised for all modules

Appropriate error catching devised for some modules

Some error catching devised for some modules

Np error catching devised

Communication Appropriate level of communication used in all aspects of user manual and online help.

Appropriate level of communication used in most aspects of user manual and online help.

Appropriate level of communication used in some aspects of user manual and online help.

Little or no user manual or online help

Evaluation Testing and evaluation assesses design and functionality of interface to a very high level

Testing and evaluation assesses design and functionality of interface to a high level

Testing and evaluation assesses design and functionality of interface to a satisfactory level

Little evidence of testing and evaluation

of 18


Standards matrixDimensio

nA B C D E

Kn

ow

led

ge

and

ap

plic

atio

n

The student work has the following characteristics: detailed description

and explanation of links between information technology concepts, terminology, processes, and principles

The student work has the following characteristics: description and

explanation of information technology concepts, terminology, processes, and principles

The student work has the following characteristics: description of

information technology concepts, terminology, processes, and principles

The student work has the following characteristics: statements of

information technology facts

The student work has the following characteristics: reproduction of

isolated information technology facts

detailed and effective application of set processes to solve simple and familiar problems.

effective application of set processes to solve simple and familiar problems.

application of set processes to solve simple or familiar problems.

elements of set processes to partially solve simple or familiar problems.

elements of set processes used.

An

alys

is a

nd

syn

thes

is

The student work has the following characteristics: detailed interpretation

and analysis of problems and situations from multiple perspectives

The student work has the following characteristics: interpretation and

analysis of problems and situations

The student work has the following characteristics: analysis of problems

and situations

The student work has the following characteristics: identification and

classification of problems or situations

The student work has the following characteristics: restated problems or

situations

designed and developed effective solutions to unrehearsed or complex problems.

designed and developed solutions for unrehearsed or complex problems.

designed and developed partial solutions for unrehearsed or complex problems.

designed or developed elements of solutions for unrehearsed or complex problems.

superficial elements of unrehearsed or complex problems.

of 18


Dimension

A B C D E

Eva

luat

ion

an

d c

om

mu

nic

ati

on

The student work has the following characteristics: comprehensive testing

of processes and solutions, application of self-determined and prescribed criteria, reasoning and evidence to draw conclusions and make supported recommendations.

The student work has the following characteristics: reliable testing of

processes and solutions, application of prescribed criteria, reasoning and evidence to draw conclusions and make supported recommendations

The student work has the following characteristics: testing of process or

solutions, application of prescribed criteria, reasoning or evidence to draw conclusions and make recommendations

The student work has the following characteristics: elements of testing of

processes or solutions to draw inferences

The student work has the following characteristics: elements of testing

comprehensive construction of documentation and fluent presentation of information using suitable communication conventions to convey meaning appropriate to the context.

effective construction of documentation and effective presentation of information using suitable communication conventions to convey meaning appropriate to the context.

construction of documentation and presentation of information using communication conventions to convey meaning.

presentation of information using elements of communication conventions.

presentation of information.

of 18

Major proj term3

Technology

Transcript of Major proj term3