Design Brief Template for Assignment 2 Use this document as an template for your Assignment 2. You are welcome to adjust this structure to suit your needs by adding extra sections, just make sure you cover all the points outlined in this document. Important: Before you start using this document, you should first make a copy and share it with your instructors. See this document for information on how to do this: https://lo.unisa.edu.au/mod/url/view.php?id=719248 Student Information Full Name Email Address   1. Overview 1.1 Aim ● Specifically, what do you need done (eg. design a website website, create a video, develop an app, etc.) ● This section doesn't need to be very long, just a paragraph or two to give the reader an idea of what the project is on a high level. 1.2 Background ● Who is the client? ● Who is the target audience of this project? ○ Is this project targeted at the organisation's existing audience, or is it aimed at a subset of their audience. It may even targeting a new demographic that the organisation currently does not cater for. ● Include the problem definition here ○ What were the areas of weakness identified in your assignment 1? ○ What specific problem(s) does this project attempt to solve? 1.3 Purpose ● What are the measurable outcomes of the solution you have come up with (eg. increase membership, improve brand awareness, increase social media presence, etc.)   2. Requirements This is the main section of the document and should outline exactly what needs to be done. Remember, this document would be something you will hand over to your design and development team, so it's important you are clear and thorough to reduce the need for revisions. The way you outline your solution depends on what it is that you are proposing. Below are some suggestions for the kinds of approaches you could take; you can use 1 or more of these suggestions, or come up with your own. The most important thing is that you are clearly explaining the scope of the project requirements, and articulating the required look and feel of the work. ● A list of sections and pages required, such as a site map Example Site Map: https://www.gliffy.com/examples/site-map ● User Journey A User Journey map is a description of how the typical user will move through the proposed software. This could be in the form of paragraph text, or a diagram. THis is especially useful if your requirements involve complex user interactions, such as an mobile or Web application. Learn more about User Journey mapping here: http://www.smashingmagazine.com/2015/01/15/all-about-customer-journey-mapping/ Another User Journey Map Example: http://www.servicedesigntools.org/sites/default/files/res_images/02.jpg ● Wireframes Basic line-art drawings to show the layout of the pages, useful for projects involving interactivity, such as Websites and apps. Here are some useful resources about wireframing: ○ The Importance of Wireframing http://www.onextrapixel.com/2009/07/15/the-importance-of-wireframes-in-web-design-and-9-tools-to-create-wireframes/ ○ The Focus of Website Wireframes Very basic introduction to wireframing http://graphicdesign.about.com/od/effectivewebsites/ss/wireframes.htm ○ The "Grey Box" Method http://v3.jasonsantamaria.com/archive/2004/05/24/grey_box_method.php ○ I Heart Wireframes This is a Tumblr that collects examples of different types of wireframes. There are many different styles of wireframes, use this site to decide on the style that best suits you. http://wireframes.tumblr.com/ ● Mood Board A collection of images that capture the look and feel you're going for. Mood Boards are generally too vague to be used on their own, but can be useful in conjunction with the other techniques listed here. ○ More info here http://www.creatively-driven.com/the-art-of-the-mood-board/ ● Style Tiles Style Tiles are a method developed by Samantha Warren and is used as an alternative to full-blown Photoshop mockups. The idea is that you create styles which give the client a clear idea of the look and feel you're going for, without the need to design the entire website. ○ More info here: http://styletil.es/ ● Storyboard - see module 6/7 for details on storyboarding ● Treatment - see module 6/7 for details on writing a treatment   3. Project Approach In this section you need to outline the way you will manage this project. How you represent this is up to you, but here are some ideas to get you started: ● List of roles required How many designers, programmers, copywriters, producers etc. will you need to complete this project? ● Which technologies to use? If you're creating a website or app, will you be targeting particular browsers or devices? If you're creating a video, will you need particular technologies of software packages? If you're creating print material, do you need special paper stock? It's important you demonstrate that you have considered the kind of technologies you need so that you can hire the right team. ● Project timings How long do you think this project will take? You could provide a breakdown or hours, or even a Gantt chart to represent the way you will run this project. ● Cost Estimates Can you give cost estimates at this stage, or will you need further project scoping and consultation in order to provide final numbers? It's recommended you give some indication of the project cost, even if they are not presented as a formal estimate.