Presentation

Hey Guys,

As we have the presentation on Wednesday I just though we should establish what our parts are, the presentation goes for 8 min so its not long. I think this is what should be covered:

• Introduction- 1 min Charlie
  

• Touch on new design- 1 min Bernie
  

• Testing- 1 min Charlie
  

• Walk through of Site- 4 min Aleks
  

• Handover/clients role- 1 min Bernie
  

Let me know if you guys think we need to add anything or dont need anything. We can talk more when we get together.

ABC Interactive HET 402 Week 13 - 09/11/2009

ABC Interactive HET 402 Week 13 - 09/11/2009

Preparing final documentation and presentation.

Aleks has done a really good job the website so far.
He's now finishing off the collaborative art piece.


Charlie finishing off all research analysis.
I'm working on accountability.

Reevaluation of final submission:



HET402

Group Confirmation email

• Functional / Content Specification (only if starting a
new project, with subject convenor approval);

• Quality Assurance Review/Usabilit y Testing Plan.

• Project Definition – expanded from

Final Documentation – stage 2:

• Quality Assurance Review/Usabilit y Testing Report
– expanded from the QA Review / Usability Testing
Plan submitted earlier in the semester.

Technical Specification & Handover Instructions.
Resubmit Project Definition, Functional / Content
Specification. (see note below)

• Individual Contribution Summary.

Note:The original Project Definition and Functional /
Content Specification documents for HET401 must be
resubmitted for HET402 with a brief addenda for any
changes.





Documentation Assessment Weightings:

The documentation component of HET401 / HET402 is given a single mark. This mark is based on how well each of the documents are judged to address the criteria (elements) listed in the
documentation guides.

Project Proposal Document
(due week 9 so is ready for pitch)

Minimum of 1 proposal required
(loading of 5% available if submit 2nd proposal)
20% = 15% for “best” attempt + up to 5% loading for submitting 2nd proposal.

Final document Part 1
(due in exam period)
Functional Specification (or equivalent
= eg content specification / storyboard) 15%
Final document Part 2 Project Definition document – one only
required - (updated from project
proposal document) 5%
Total Documentation mark 40%


1.3 Overall document quality – structure and appearance. The documentation required for the project is expected to be of a professional standard. In each major document (except the Project Outline / Brief) the following should be included prominently and early in the document:

1.3.1 Cover information. The front cover of each document submitted must contain the following
information:

• Contractor’s logo (i.e. group logo) and / or client logo [optional].

• Document Title / Name in large font so that individual documents can be readil y identified, and any graphic / design elements the group feel will enhance the professional appearance of the documents.

• Elements contained in the document (e.g. if submitting Project Definition and Functional Specification in a single volume, this should be indicated on the cover). Also indicate whether a CD or other media is inserted into the document (make sure any such media are well secured in the document).

• Document number / total number of documents submitted (e.g. if the document is submitted in 3 separate volumes, they should be labeled document 1 of 3, document 2 of 3 and document 3 of 3 respectively).

The following footer information, is also required on the front page of every separate document. (this would not normally be necessary for “commercial” documents):

• Group name (as allocated by subject convener)
• Name and ID of each group member.

• Supervisor’s name

1.3.2 Important information about the document. The following information should be included earl y in the document, usuall y the first page inside the front cover:

• purpose of document;

• the intended “audience” or "readership" for the document (e.g. "Marketing Dept. or other non-technical personnel"; or "IT Dept. and Programmers familiar with PHP coding");

• how this document relates to other documents that need to be read in conjunction with this document (include date, version number where appropriate);

• Document Revision History – Major business documents normall y contain a Document
Revision History at the beginning. This section describes the evolution of the document through its drafting and version stages. Documents are often changed and updated as a project proceeds, so “version control” and Document Revision History ensures that the client can be aware which version of a document they are reading, and its background. Details provided would normall y include the version numbers, dates changes were made, which sections or document elements were altered, and the author and/or person responsible for the changes. This is usuall y in table format, before the table of contents.

For example, the Document Revision History (table) at the beginning of the Project Definition should identify clearl y those elements or sections of the Project Definition that have been expanded from the Project Proposal or changed in later revisions (and by which group member.

• Executive Summary This is recommended for any important project document, especiall y when you are trying to win work from a new client. It should be concise, (1 page maximum) while still covering all of the key issues (think about what these would be for a senior company executive). It may be the only page that is read by some busy key stakeholders, so make sure all bases are covered here (don't overlook any major issues that are contained in the body of the document. All of the important elements listed in the table of contents should ideall y be addressed (at least briefly) in the executive summary.

ABC Interactive HET 402 Accountability - 02/11/2009

ABC Interactive HET 402 Week 12 - 02/11/2009

2.1 Group Formation / Project Approval
Completed

2.2 Group Confirmation
Completed

Team name
ABC Interactive

Members
Aleks Witko
Bernard Winter
Charlie Lowe

Client
Design Foundation

Project
agIdeas newStar website

3.0 Project Group Meetings with Supervisor (HET402)
Completed

Supervisor
Jonathan Lang


ABC Interactive HET 402 Jonathan Lang Meeting 1 - 4/09/2009

Jonathan Lang Meeting Minutes

Got Jonathan up to speed with our project
Discussed Project goals
Discussed group member roles
Talked about the Design Foundation and there goals
Completed meeting by allocating time for next meeting

Time of meeting: 20 mins
Time of day: 1:00PM
Present: Jonathan Lang, Aleks Witko, Charlie Lowe
Next Meeting: 18/09/2009
Meeting Minutes: Aleks Witko
Location: AS Lev 3 Conference Room


ABC Interactive HET 402 Jonathan Lang Meeting 2 - 18/09/2009

Jonathan Lang Meeting Minutes

Demonstration of website and design to date
Looking at a new feature. Collaborative Art Piece
Exchange of contact details
Question of utilizing particular technologies within website
Design reference to website

Time: 25 mins
Time of day: 1:00PM
Present: Jonathan Lang, Aleks Witko, Bernard Winter, Charlie Lowe
Next Meeting: 02/09/2009
Meeting Minutes: Bernard Winter
Location: AS Lev 3 Conference Room

ABC Interactive HET 402 Jonathan Lang Meeting 3 - 02/10/2009

Jonathan Lang Meeting Minutes


Discussed Submission Requirements
Discussed Progress in regards to client and meeting expectations
Discussed PHP and appropriate appreciation of acquired knowledge
Brief Discussion about final presentation
Talked about usability testing and the actual participants and timing.

Time: 15 mins
Time of day: 1:00PM
Present: Jonathan Lang, Bernard Winter, Charlie Lowe
Next Meeting: 16/09/2009
Meeting Minutes: Bernard Winter
Location: AS Lev 3 Conference Room
ABC Interactive HET 402 Jonathan Lang Meeting 4 - 16/10/2009

Jonathan Lang Meeting Minutes

Showed Jonathan Blog and accountability location, project progress
Demonstration of website so far
Discussed client and there appreciation of project to date
Discussed methods of deliver and reiterated goals and scope
Allocation time for next meeting

Time: 23 mins
Time of day: 1:00PM
Present: Jonathan Lang, Aleks Witko (via teleconference), Bernard Winter, Charlie Lowe
Next Meeting: 30/09/2009
Meeting Minutes: Bernard Winter
Location: AS Lev 3 Conference Room


ABC Interactive HET 402 Jonathan Lang Meeting 5: 30/10/2009

Jonathan Lang Meeting Minutes


Discussed Final Assessment Date, Time and Presentation
Demonstrated website at current point
Discussed push back of usability testing, due to difficulty in getting collaborative art piece up and running.
Discussed final meeting with Design Foundation and making a note on insuring controlling client expectations so there are no surprises in final hand over presentation
Discussed final presentation and brief on final deliverables.

Time: 30 mins
Time of day: 1:00PM
Present: Jonathan Lang, Aleks Witko, Bernard Winter, Charlie Lowe
Meeting Minutes: Bernard Winter
Location: AS Lev 3 Conference Room



ABC Interactive HET 402 Design Foundation Meeting 1: 15/09/2009

Design Foundation Meeting Minutes

Introduced Eleni to the project and the team.
Reiterated project goals
Reiterated project scope
Outlined changes including possibility of collaborative art piece and gauged appreciation of idea.
Discussed design to date and changes that needed to occur
Simplification of design
Cleaner interface
Focus on students
Noted all design changes to be made
Decided on what would be completed by next meeting
Completed meeting by allocating time for next meeting

Time: 40 mins
Time of day: 3:00PM
Present: Karen Sorensen, Eleni Kaponis, Aleks Witko, Bernard Winter, Charlie Lowe
Next Meeting: 29/09/2009
Meeting Minutes: Bernard Winter
Location: Cato Purnell Partners Melbourne Office, Collingwood

ABC Interactive HET 402 Design Foundation Meeting 2: 29/09/2009

Design Foundation Meeting Minutes

Had a look at the website in it’s current form
Typography comments
Questions about the dark space like header and font colour choices
Foundation of website to date was said to be good and look forward to final website in the coming weeks.
Noted that particular things were being implemented in current website

Time: 20 mins
Time of day: 3:00PM
Present: Karen Sorensen, Aleks Witko, Bernard Winter, Charlie Lowe
Next Meeting: 20/09/2009
Meeting Minutes: Bernard Winter
Location: Cato Purnell Partners Melbourne Office, Collingwood

ABC Interactive HET 402 Design Foundation Meeting 3: 20/10/2009

Design Foundation Meeting Minutes

Brief drop in to show progress
Thought it was best to drop in, in-person for demo

Time: 10 mins
Time of day: 3:00PM
Present: Karen Sorensen, Eleni Kaponis, Bernard Winter
Next Meeting: 23/09/2009
Meeting Minutes: Bernard Winter
Location: Cato Purnell Partners Melbourne Office, Collingwood

ABC Interactive HET 402 Design Foundation Meeting 4: 23/11/2009

Design Foundation Meeting Minutes

Brief Meeting to demo the website
Prepare client expectations for final hand over presentation
Made sure client was free for allocated time

Time: 20 mins
Time of day: 3:00PM
Present: Karen Sorensen, Aleks Witko, Bernard Winter, Charlie Lowe
Location: Cato Purnell Partners Melbourne Office, Collingwood