Friday, 4 September 2015

Week 6: Progress and Part A concept document

The last week or so has been spent concentrating on part A, what was needed for the pitch and the document.  While other team members concentrated on the presentation or further technical or design research, I spent this week considering the project documentaiton and writing up the part A document.

As I read through the document requirements, it seemed to partly reflect project documentation I had previously worked on in my job.  Thinking about how the major project is meant to feed into our portfolio assessment at the end of semester, I had previously only considered the technical elements I could include.  It occurred to me that project management and documentation were also important skills I could gain from this project and add to my portfolio.

While it might have been easier to just answer the couple of dot points required for the document, I thought it would be more useful to use some of my existing project documentation skills and create a more comprehensive document.  My approach was to look at the assessment requirements, look at what I would include for a real project proposal including supporting documentation and then cut or add what we needed for the project.

Matching assessment requirements with project documentation


Document requirements Project documentation
A survey of relevant background material – which published works does the design build on and how these are related. Rationale for project.
Why are we doing this? What problem are we solving? What does the research say?
Consideration of the intended audience and the experience you want them to have – who are your intended audience, how and in what context do you expect them to interact with your work, and what do you want them to experience as a result. Outcomes, benefits and impacts.
What are the users needs and how will they met? What personal/student benefits are there (learning technical skills).
Project plan including scope for implementation Scope
What is the level of detail? What is in scope and out of scope. Time is fixed, scope is flexible.
Breakdown of milestones with expected tasks & completion times for delivering the project Task Analysis
Could include: Deliverable, Effort, [Must, Should, Could, Won’t], Status, Notes.

This might be too much detail, minimum is item, week, and notes.
Breakdown of who in the team will be responsible for tasks and how the workload will be spread across the team. Proposed staffing
Team members including roles and responsibilities
Issues you think that you may encounter in the implementation of your project and suggestions for how to overcome them. Risk Analysis
List risk, impact (1-5), likelihood of risk (1-5), overall risk score(1-25) and mitigation.
This might be too much detail, minimum is risk and mitigation.
Response to feedback received in presentation Include in other areas as needed.


Other project documentation

Other items normally included in project proposals and documentation that may or may not be relevent to this project.

Item Rationale Include in Part A
Success criteria
Could be as simple as a finished product or include learning outcomes
Is a requirement of Part B documentation, will include then. No
Assumptions and constraints
What box are we working inside (fixed deadline of assessment and semester deadlines).
It is assumed that… (through a combination of formal teaching and self-directed learning that team members will be to technically deliver this project).
Probably overkill for our assessment, won't include. No
Proposed costs
Should be nil, expectation of software that each team members will have (mostly freeware)
Not neccessary for this project No
Communication plan
Internal only as there is no real client/audience stakeholders. Include github, drive, plus, facebook etc.
Could include tutors, brief (client)??
Will include internal only.  Had listed in in team charter (informal) Yes
Stakeholder analysis.
Include audience in this. What other stakeholders do we have? Could include audience, team members roles, tutors/teaching staff, team members as students (what will i get out of this course - skills). Present as stakeholder interest, expectations, and strategy.

More detail than needed for this project.
Combine audience with outcomes, benfits and impacts.
Incorporated in other section
Proposed deliverables 
Specific items we will achieve by end of semester

Proposed time frame 
Time frame for deliverables (milestones)
Not enough items/too early in the project to have separate task analysis, proposed deliverables and proposed time frame.  Combine into one section. Incorporated in other section

Thursday, 3 September 2015

Week 6: Target audience research: Interview with a teacher

One piece of feedback following our presentation of Part A was around the appropriateness of our target audience.  While I had intended to talk to a teacher before hand, I had run out of time.  Given this feedback, it became necessary as the curriculum did not give the whole picture, and a lot of the conversation we have had about the age-group revolved around anecdotal evidence.

To gain more insight on our potential audience and how our product could be used, I interviewed a high school information technology (IT) teacher who teaches grades 7-12.  Their experiences include teaching at a co-ed independent school, a state school and being involved in an Education Queensland monitoring program for IT subjects across a selection of schools (colloquially known as 'panel').

During my research, I had looked at the ACARA curriculum for Digital Technologies to see where HTML and CSS were taught. By speaking to a current teacher with first-hand experience, I was able to find more information of how this played out in a classroom.

Here are the main points from my interview.

  • The National Curriculum (NC)is still in draft, but any curriculum is only used as a guideline.  The curriculum provides the framework and topics but the depth varies between schools and resources.
    • Some GPS schools are very well resourced with IT teachers and teach in-depth HTML, CSS and Javascript.
  • At their current school, they do not teach multimedia/IT in grade 7 and 8 but will be moving in that direction sometime in the future, possibly to align with NC.
  • In grades 9 and 10 (junior) they teach a combined multimedia/IT subject and in grades 11 and 12 (senior) it is split into Information Technology Systems (ITS) and Information Processing Technology (IPT).
  • ITS includes multimedia, web design and development, with a light focus on coding
    • Grade 9
      • introduce HTML and CSS
      • use Dreamweaver but not drag and drop feature
      • code single page with nav, insert pictures, links and concepts of HTML layout
    • Grade 10
      • build on knowledge, more HTML and CSS
      • code multi-page site
  • IPT includes AI, software development, databases and focuses on coding
    • Used to do visual basic 9-12, now javascript in junior, objective c in senior 
  • W3C is used like a textbook from grade 9
  • HTML5 specifically is taught including what the '5' means, how it relates to W3C and web standards
  • Students are made aware of HTML validators but are not required to use them in assessment as Dreamweaver does a lot of that for them.

What does this mean for the target audience for our project?

Web historians is for people:
  • who are familiar with HTML and CSS but still beginners
  • might know what validation is but don't necessarily understand it's importance or how/when it can be used
  • would suit grade 10 at school but other beginners in the general public and university
  • would suit classroom use or as extension work for school students
(Originally posted on our team blog: Restoring the web)

Thursday, 27 August 2015

Week 5: 6 thinking hats activity

For this week's contact session, we ran our concept through the six thinking hats.

From http://johnkapeleris.com/blog/?p=418

Concept:

This project, Web Historians, aims to highlight the importance of archived websites and their potential decay, by providing a solution through an interactive educational experience.  It will use a combination of Trove and Wayback Machine APIs to access archived websites that are then evaluated through a HTML5 validator.  Users will be able to choose websites in a category of interest to them, select a specific site to restore, fix the highlighted problems, and save the completed, restored files for the future. Users will also be able to save their progress by creating an account.

White hat

The information in our concept is the html of archived websites.  The html is validated and is presented to the user as html mark-up, a list of errors, and the displayed website.

Red hat

Our concept has feelings of nostalgia and a respect for history and its preservation.  

Yellow hat

Best case scenario, we complete the app with all the 'if there's time' features, the technical requirements are challenging and we learn a lot but is not beyond our skill level.  The product is useful for our target audience and provides users with a positive experience of html. 

Black hat

There are a lot of technical components and it will be hard to draw a line in the sand for what we deliver.  There are a lot of things I would like to do with the project (like use web components) but not necessary to the delivery of the project.  Worst case scenario is we don't get the minimum requirements over the line and spend too much time in getting individual elements right at the expense of the bigger picture

Green hat

The initial concept is a creative way of using archived content by turning it from something static to something interactive.

Blue hat

The concept seems like a great way to both save historical content and provide a learning tool for students.

Wednesday, 26 August 2015

Week 5: Trove API limitations

We met today (meeting minutes to follow) to refine our concept and discuss our research so far.

There is an initial problem that we are currently working through regarding the brief requirement of using the Trove API.  During our research we discovered that the trove API does not provide access to the websites listed on the trove website.  We can however, use the Wayback Time-machine API (that Trove refers to) to get this information.

A closer read of what the Trove API can and can't access says:
"Search Trove newspaper articles, lists and works. (Works are made up of “versions”. They can be books, images, maps, music, sound, video, archives, journal articles…) Archived websites, people and organisations have not been included at this point."

We also looked at the search function of the API, and the 'search all' does not include archived websites:
"Search across the records in Trove. The same records you search from the Trove homepage, excluding archived websites, people and organisations."

We are in the process of discussing solutions with our tutors and course coordinator and have contact Trove to see if there is any support or workarounds for accessing archived websites.

Our current suggested fix is to organise the websites accessed via categories (e.g. sport, arts, education, government...) and to illustrate the categories (background, button?) with trove images (related to the category but not the actual websites) which are pulled using the trove API.

We would still need to use the Wayback Time-machine API to get the website details to validate but at least we are not by passing Trove altogether.

One of the risks we discussed today was having to make design decisions based solely on checking off a box in the brief and not on what would make the best product that suits our user needs.  While for the most part these two considerations are not opposites and inform decisions in consort, we are hoping that this problem is not the case of the former.

The core part of the brief that we are answering is to:
"highlight, reveal, [or] focus the content available through Trove ... something that goes beyond the simple search paradigm that they currently have and that sheds light on rarely visited corners of Trove."

We believe our concept definitely does that.  Stay tuned for more concept updates.

UPDATE: The course coordinator emailed back straight away with an OK to go ahead with our proposed suggestions.  We also chatted more with our tutor at the workshop and with the course coordinator after Friday's lecture.

(Originally posted on our team blog: Restoring the web)

Sunday, 23 August 2015

Week 5: Refining the target audience

As part of refining the target audience for the web app, I looked into the current IT curriculum for high school students, specifically when and how web languages (HTML and CSS) are taught.

The Australian Curriculum Assessment and Reporting Authority has a draft national curriculum for Information Technology (up to grade 10).  The draft curriculum introduces the concepts of HTML and CSS for grades 7 and 8 (pages 89 and 90).

As I am not a teacher (and have been told the national curriculum is open to interpretation), I  also plan on speaking to an IT teacher to confirm what they actually teach and when.

Even though this forms a minor part of our assessment, I believe having a specific target audience will help us develop a more useful application.  The target audience will also go to forming the basis of any personas we develop.

(Originally posted on our team blog: Restoring the web)

Saturday, 22 August 2015

Week 4: Forming Teams

After presenting our concepts, everyone voted on their top 3 preferences for concept/group.  During the following workshop session, we finalised our groups.  Even though my Shipwreck concept received enough votes, I chose to work on another concept:  Restoring the web.  I really liked the problem that it solved.  I will be going into more detail in the near future as our team refines the concept, but here is a brief overview:

Project Description

Restoring the Web is a web-based learning environment aimed at teaching high school students basic web design skills.


Week 4: Design Exploration Concept

This week in class we presented our final Design Exploration Concept and submitted an A3 poster.  Here is my final concept.

Early Australian Shipwrecks (-1900)

Concept

Early Australian Shipwrecks is a web app detailing shipwrecks on the Australian coast up to 1900.  The concept is aimed at people interested in Maritime History, particularly early modern history.

The web app would consist of a marked up Google Map of shipwrecks around the Australian Coast.  When you click on a particular spot.  It brings up historical photos and newspaper articles through the Trove API.

Relevant Information

The Western Australian Museum has a website on its Shipwrecks with an API with relevant data at http://www.museum.wa.gov.au/maritime-archaeology-db/wrecks/map and http://www.museum.wa.gov.au/sandbox/.  This would only be useful for part of the coast.

Wikipedia has a list of Australian Shipwrecks including dates and locations at https://en.wikipedia.org/wiki/List_of_shipwrecks_of_Australia.

The Australian Government also has a page about Early Australian Shipwrecks, which is where the definition of up to 1900 comes from at http://www.australia.gov.au/about-australia/australian-story/early-austn-shipwrecks.

Design Mock-up

Clicking on a particular article will bring up the details within the frame.

Map Research


There are many examples of maps displaying more detailed information on click.  There was a notable style in having a ‘pop-out’ for this information, headed by Google maps and maps made with the Google Maps API.

Map Research