Thursday, February 1, 2018

Final Screencast

I took all the previous points I scripted a screencast around it. I was aiming for the entire screencast to be around 5 minutes long. From rough estimations, approximately 300-400 words should be enough for the whole video (excluding a demonstration and client feedback). 

My introduction briefly introduces my client.

Next I talked about how I would attempt to solve the solution I came up with.
After that I went through each of my 3 videos explaining what I did and why I did it. I covered all the major making steps and how I did it.

The last section is the handover and feedback section. I gave the client a few questions to answer and after that I included a short evaluation of my own just covering what I could've improved on.

Here's the video:




Here is a copy of my script:

Introduction to the client:
My client for my ICT project was my school’s student council. Just like the name dictates, it is a council where students from the higher years hold regular meetings to make changes to the school.

Problem & Solution:
Recently, the student council is currently facing an issue of transparency. By having a more specialized website, they hope to improve communications with the student body and inform them about the projects they’ve been working on. Furthermore, the website would be a great place to share the council’s weekly minutes; allowing the rest of the school to indirectly listen into the council’s meetings.

Development:
Before I started making the website, I had to design the website. I started out by creating a brief wireframe that I’d show the client for feedback. This client liked the idea so I went on to make the page. At first, I started at looking how I could use the template fullPage.js as it looked rather similar to the webpage I’d be creating. I went on finding an alternative as the template was too hard to modify. I ended taking the first page of the template though, as that looked rather nice. For the other pages, I used a mixture of Bootstrap and code to create each section. I took inspiration of different professional websites for some aesthetical aspects, as I was unable to think of any.

After I’d make section, I could then put them all together on my final home page.

For the CMS, I had to do quite a bit of research first. Once I figured out how to link the information from the database to the website, I made myself a CMS, where I could change the content from the database from a user-friendly site that I made myself. Here’s a demonstration.

Client handover:
Q: Please give an overview of what the project's aim is?
A: (Talks about the question)

Q: Does the website fullfill all of your design specifications?
A: (Talks about the question)

Q: What do you think of the aesthetic?
A: (Talks about the question)

Q: Any overall comments? 
A: (Talks about the question)

Mini-evaluation:

Overall, I recieved a lot of positive feedback on the project. Both the customer and I are incredibly happy about the technical and aesthetical level of the website. I believe I've fullfilled the specifications and much more and am incredibly grateful for being able to work alongside the council. Thank you.

No comments:

Post a Comment

Evaluation and Reflection

Once I finished my project, I had to fill in a self-assessment sheet for my project evaluation. I went through each category and gave mysel...