Technical proposal

Technical proposal

1. The investigation will include referencing conventions using the Harvard (APA) system of referencing.

   • recognition and description of
     • data sources
     • appropriate programming development tools
     • useability principles and user-interface components
     • existing solutions to similar problems
   • symbolisation using mind maps and one or more of constructed sketches, annotated diagrams, images or screenshots of
     • user interfaces
     • programming features communicated by algorithms
   • explanation of
     • user experiences
     • useability principles and accessibility features
     • data structures
     • programming features
   • analysis of the problem and information to identify
     • boundary or scope of the problem
       • user experience
     • constraints and limitations of the environment
     • data, programming and user-interface relationships
     • potential algorithmic implementations
     • possible personal, social and economic impacts
     • possible solutions

2. determination of

   • requirements from the user perspective for the user experience
   • programming requirements
   • required data
   • prescribed and self-determined criteria

3. synthesis of information and ideas to select the best approach for

   • user interface(s)
   • data structures of the proposed solution
   • coded components of the proposed solution

4. generation of a low-fidelity (non-coded) prototype solution including user interface, data and algorithms

   • 5. Evaluate the technical feasibility of your digital solution and obtain feedback from the target audience about useability features.

5. evaluation against criteria, of

   • personal, social and economic impacts and considerations to identify risks
   • the user-interface prototype
   • the accuracy and efficiency of the algorithms
   • the low-fidelity non-coded prototype digital solution

6. make refinements and justified recommendations for current and future improvements

7. communication of

   • – the technical feasibility of developing the prototype solution, including the technical aspects of the development process.
   • information and ideas to inform a technical audience
   • e.g. algorithms, selection and justification of development tools, user-interface sketches, user-experience requirements.

8. Examples of a multimodal presentation include:

   • a web page, in which elements such as visual effects, oral language, written language and still or moving images are combined
   • a slideshow or animation documenting the application of the problem-solving process
   • multimedia movies that may combine photographs, video, sound, text and a narrative voice

9. Data

   • pron's
   • Con's

10. mindmap

11. Usability principle

12. short form video editing

    • data
      • video file
        • mp4
        • welom
        • mov
      • meta data
        • location
          • varcahal

13. impacts

    • soical
      • sharing media
    • economic
    • perosnal

14. user persona

    • jimmy
      • age:24
      • education: master in It
      • Software Engineer
      • sport and tv
      • america
      • Goals: • Want to become best software engineer in the world
      • • Needs thing done on time and perfectly without any mistakes
      • user probemle: Does not have much support from his boss or people around him, because of his failures in past few months.

15. User Profile Picture Name Education Goals Needs & Expectations John Bachelor’s in art • 2 million in YouTube • Needs 100k sub on YouTube to starting to earn money Age Occupation Interests Pain Points/Frustrations 24 Art gallery Gaming • Not getting enough subs per month Location User Problem Summary Austrian Losing sub subs every day. because not uploading good content.

16. User Profile Picture Name Education Goals Needs & Expectations James Bachelor’s in business To starts his own business by the end of year • Needs 400k before the end of year for his business Age Occupation Interests Pain Points/Frustrations 19 It workstation Sport • Not getting enough money Location User Problem Summary Australia Not working hard due to his back injury

17. data set

18. imager colour

19. Scaffolding

    • multimodal response component must be in MP4, MOV or AVI format and have a total file size less than 500MB
    • student script or speakers notes (optional) must be in a PDF format and have a total file size less than 5MB
    • electronic documents must be submitted as a single file in the correct page order, in colour with all pages correctly oriented (no upside down or sideways pages)
    • The technical proposal multimodal presentation will include the following parts:
      • identification — a brief statement which identifies the real-world related need for developing the digital solution and relevant background information
      • interactions — specifies information relating to interactions between humans and or the environment, and information systems, this may include proto-personas
      • component specifications — specifications relating to data, user interface /experience and code

20. 1. Explore the problem and analyse relevant information, user needs and data sources.

21. 2. Develop a user-persona and ideas for possible solutions to meet the needs of your user-persona

22. 3. Evaluate your ideas for possible solutions against the prescribed criteria set by your teacher and your own self-determined criteria.

23. 4. Generate a low fidelity prototype including annotated sketches of proposed user interfaces, algorithms for coded components and data flow diagrams.

24. 6. Communicate your technical proposal to a technical audience using a video format including recommendations for improvement.

25. project objectives

    • 1. recognise and describe data sources, programming elements , user interface components and useability principles
    • 2. symbolise algorithms and user interfaces, and explain ideas and interrelationships between proposed data structures and user experiences of the identified problem
    • • accurate and discriminating recognition and discerning description of data sources, programming elements, user-interface components and useability principles
    • insightful analysis of the problem and relevant contextual information to identify the relevant elements and features of user interface, data and programming components and their relationships to the structure of the identified problem
    • coherent and logical synthesis of relevant information and ideas to determine data elements, user interface and algorithm components for digital solutions
    • discerning decision-making about, and fluent use of − written, visual and/or spoken features to communicate about a solution − language for a technical audience − grammatically accurate language structures − referencing and investigation conventions.