🏢
BA Portfolio
  • 0️READING GUIDE
    • How to Read the Portfolio?
    • Front Page
    • Reading Guide
  • 1️Phase 1 - DISCOVER
    • Overview - Discover Phase
    • The TQ Building Problems
    • Acquiring deeper knowledge of the project's main topics
    • The working routines of the people at Fontys TQ - User Research
  • 2️PHASE 2 - DEFINE
    • Overview - Define Phase
    • Problem Definition and Solution Direction
    • Target Users Definition
    • First Concepts and Design Challenge Redefinition
  • 3️PHASE 3 - DEVELOP
    • Overview - Develop Phase
    • Creating the Scenario Flows
    • Creating the User Screen Flows
    • Ideation of Hardware Design
  • 4️PHASE 4 - DELIVER
    • Overview - Deliver Phase
    • Choosing Suitable Software
    • Device "Character" Face
    • Device Prototype and Validation
  • 5️Conclusions and Reflections
    • Project Conclusions
    • Personal Reflection
  • 🔎Attachments
    • Purchased Hardware Components List
    • Comparison Chart for Hardware Casts
    • Scenario Flows Test Notes
    • Hardware Designs
    • User Screen Flows
    • Scenario Flows
    • Project Proposal
    • Project Plan
    • Design Challenges Versions
    • Research Questions
    • Library Research Report
    • User Survey
    • User Interviews
    • Small Scale Prototype
Powered by GitBook
On this page
  • Phase Goals
  • Phase Approach
  • Relevant Research Questions
  • Relevant Attachments
  1. PHASE 4 - DELIVER

Overview - Deliver Phase

PreviousIdeation of Hardware DesignNextChoosing Suitable Software

Last updated 1 year ago

Phase Goals

After defining all the needed user interaction flows and hardware requirements, it was time for me to create a final prototype, that would show the concept on a more high level that I can test one last time to gain the conclusions of the project. However, creating the final prototype required first putting up some building blocks (as I had the expectation that a learning curve would be needed for the 3D environment, and the face animations). Hence, the main goals of that final phase were to:

Phase Goals:

  1. Choose a suitable software technology

  2. Create a concept for the buddy phase (give it character)

  3. Create a prototype and do the final validation

Phase Approach

As visible in the image below this triangulation is showing that circle 3 is darker. That is because, at the stage of the delivery of this portfolio, the circle was not completed. The other two circles put the building blocks for the creation of the final prototype and by the final presentation goals (circles) would be completed.

Considerations:

As mentioned in the last chapter, the time that was left at the beginning of the phase was quite short (even though I was updating the planning at every phase, it was true that the concept was quite big and no matter how many adjustments I did I needed to continue scoping down as the phases progressed). So coming into this phase me and my client knew that we would have to prioritise what results we want by the end in order to be able to prove the concept. We had discussed that our goal before delivery is to have a prototype that can lead the users through the experience but does not necessarily have to work completely (for example the communication between the buddy and the charging station could be faked, the cast of the buddy could be a LEGO/Paper prototype, etc). Therefore this phase, especially 1. and 2. was dedicated to understanding what options for development I can think of that give the experience without a fully functional prototype.

The Delivery phase continued answering the final Research question:

Relevant Research Questions:

  • What technological solution at the Fontys Strijp TQ building can be used to stimulate the productive feel of the building users?

Relevant Attachments

The list below shows an overview of the relevant attachments that would be mentioned in this phase (links are available in the respective article)

  • Small Scale Prototype

Relevant Research Questions

Used Research Methods:

4️
The focus of this Phase
research methods triangulation