Final documentation file link:
https://github.com/deco3500-2017/Frying_Nemo/blob/master/Documentation.md
A healthy and balanced diet is integral towards developing minds and concentration. However, despite this nearly 33% of all school aged children fail to receive a balanced and healthy diet whilst at school according to a study conducted by the New York Times (2015). Further, of the 68% who do get a healthy lunch, based upon a study by the Johns Hopkins Bloomberg School of Public Health, 25% of them even bother to eat it all (Medical Daily, 2014).
Taking this into consideration the team, ‘Frying Nemo’, is dedicated towards developing and implementing an application which helps parents in creating and maintaining a meal plan for their children which is easy, healthy and above all tasty.
Given the picky eating habits of young children, this application allows you to search for healthy recipes and meals which do/don’t include, certain ingredients/vegetables. This also allows parents to cater towards specific diets, such as nut intolerances and celiacs.
Whilst the application does initially draw upon recipe websites, through RESTful api’s, the design is intended towards a more community outlook, allowing parents to rate recipes as well as upload their own. This would ideally create a more balanced meal plan which caters towards children’s diets and preferences as the application becomes more available.
This idea has a strong starting platform, as there are no other applications out there which have these features implemented. Whilst, there are quite a few meal planners none of them are designed with children in mind, in particular their picky and constant changing food preferences and diets. Further, no other application exists which allows the user to craft their own recipes for the community or for themselves.
| Key features | Description |
|---|---|
| Sharability | Parents have the option to share their prefered recipes to the communities while parents also have the option to view and access the shared recipes from the other parents to compare the costs, ingredient or nutritions of different recipes for the delicacies of the food |
| Rating System | Parents have the option to vote and rate for their prefered recipes, having a parents and children preferences will be able to help parents to prepare food for the children much easier and healthier. |
| Nutrition Diagram | All calculated nutrition data will be display in the user profile in the form of a data driven documation diagram-D3 diagram in order to have a better representation of nutrition data to the users. |
| Calculation of Nutrition data | When user is creating a new recipe or combination of food or browsing shared recipe, nutrition of each ingredients will be caculated and displayed. In this case, user will have a better understanding of the nutrition of each ingredient. |
Parents, teachers, anyone who are running out of ideas for their lunchbox or do not have the time to think of any nutritious combination of food for their lunchbox.
- Persona A - Ming Lee
Single father of 2 young children, one in kindergarten and one in primary school. He has a day job from 9am to 6pm (not inclusive of over-time) and barely have time to pack lunch for his two children in the morning. Consequently, due to time constraints the lunch boxes packed for his kids contain unhealthy food, such as chips, pre-packaged food and soft drinks.
- Persona B - James Kappa
Married father with 1 young children who is studying in the primary schools. He loves to prepare lunchboxes for his son but lately, he has ran out of ideas for it. James wants to seek out other creative and healthy recipes for his son's everyday lunchbox, as well as sharing his with others.
For more information about the person, please use this link
- Persona A - Ashley Candleson
Ashley Candleson has been a single mother for several years now. Most of her time is spent working and providing for her two children, who mean the world to her. Because she has to work so much Ashley has very little time to spend with her children, and most of that time is spent preparing meals for them to eat, both in the evening and throughout the day whilst they are at school. A lot of time is spent preparing these meals since she struggles to find recipes which she knows the children will enjoy, since they are both picky eaters. As such, the variety present in their meals throughout the day is quite limited, as she tends to fall back upon several well-known recipes which she knows they like rather than risking new and untried meals.
- Persona B - Gerald McWilliams
Gerald has been married for ten years, he has a single child from that marriage. This child suffers from multiple allergies which make it difficult for them to introduce much variety into their diet. Further, it is difficult to make and prepare lunches with which his child can eat throughout the day since most meals contain the ingredients from which they could suffer an allergic reaction. Gerald wants some way to be able to track his child's food intake, to ensure they are getting enough variety. Also, he wishes to teach his child healthy eating habits for the future.
For more information about the person, please use this link
Breakdown of sprint dates and deliverables are as follows:
| Sprint | Dates | Week | Deliverables |
|---|---|---|---|
| 1 | 01/09/2017 | 6 | Project Proposal |
| 2 | 25/09/2017 | 10 | Minimum Viable Product |
| 3 | 27/10/2017 | 13 | Fully Interactive Application |
Breakdown of tasks and week for the project
| Tasks | Week | Description |
|---|---|---|
| Research | 7 - 8 | Collecting research and data for target audience and further technology for implementation |
| Design | 7 | Designing wireframe and mockups for the application |
| Design | 7 | Paper prototype for UX testing |
| Product Implementation | 8 - 9 | Beginning the implementation of prototype for MVP |
| Product Implementation | 10-11 | Further development on prototype and user testing for feature performance |
| Product Implementation | 12-13 | Make improvement after user testing and finalizing for the final submission |
| Team member | Student ID | Roles |
|---|---|---|
| Ned Gordon | S4266224 | Back-end |
| Edi Yik Chuen Cheung | S4384750 | UX designer, Front-end |
| Wei Sheng Ding Kelvin | S4460136 | Front-end, Back-end |
| Yung Hau Ng Jeremy | S4384837 | Front-end |
| Minh Tram Julien Tran | S4453638 | UX designer |
Completing my final year in a duel degree in Psychology and Information Systems. I have experience in web information systems through SQL, JSP, PHP and Javascript, as well as experience in mobile applications using Java. I have knowledge in user experience and user interfacing through my degree in psychology.
Third year undergraduate IT student majoring in Human Computer Interaction. I have experience in being UX designers, I am also confident in front ended work such as HTML, CSS, UI designing, graphics some PHP..
Studies Bachelor of Information Technology Studied Diploma in Information Communication Technology (Web Technology and Services) in Singapore Polytechnic Experienced with android application development and its life cycle, Software and Hardware testing, Google’s material design, Basic IOS development, Data Communication System, Computer Hardware and System Operation, Web development and database management. Have basic knowledge of scripting for automation of software installation and configuration of windows environment. Also experienced in planning schedules for different task (planned schedules for training flights in the air force previously) and testing of softwares and hardwares. Conducted the Windows Phone 7 Training Workshop which taught many interested students the basics of creating applications in Microsoft Silverlight.
Studying my final semester in Bachelor of Information Technology (Human Computer Interaction) I have experience in mostly front-end development, which includes HTML, SASS, Javascript and Angular. I also have knowledge in user experience and user interfacing.
Studying Bachelor or Information Technology with major in User Experience. Had experiences in interactive design and multimedia from having done a Diploma in Interactive in Digital Media. Despite having done mostly front end development and graphic designs, I'm also capable of working with programming in Java as well as Database design.
Wireframe is the skeleton framework of the interface of the web application, it is used for creating a better representation of idea through lines and vectors.
Wireframe version 1 (Sprint 2, Week10, updated 1-Oct-2017 )
Conducted by: Edi Cheung
Evidence of work: https://drive.google.com/open?id=0Bz9R1CjOQ21ANUJhUG1aY0tHdE0
Wireframe version 2 (Sprint 2, Week10, updated 1-Oct-2017 )
Conducted by: Kelvin Ding Wei Sheng
Evidence of work: https://drive.google.com/open?id=0B2GxQ6YSknlCTHYyYWpNcDMtYzQ
Wireframe version 3 (Sprint 2, Week10, updated 1-Oct-2017 )
Conducted by: Ned Gordon
Evidence of work: https://drive.google.com/open?id=0B_8MdQuvq7lgcDk0TmhmTFpiNlk
User journey map is a demonstration of the user behaviour through identifying their goal, motivation, difficulties and the tasks that user looking to achieve.
User journry map version 1 (Srpint 1, Week8, updated 13-Sep-2017 )
Conducted by: Jeremy Ng, Edi Cheung
Evidence of work:
Mockup is a realistic desgin representaion of the layout of the web application with the support of the visual design, visualised content and basic functionalities of the product.
Mockup user testing 1 (Week7, updated 4-Sep-2017 )
Conducted by: Kelvin Ding Wei Sheng
Evidence of work: https://drive.google.com/open?id=0B7qYjwpry_vPN3JBeGxZMWxiQUU
Mockup user testing 2 (Srpint 1, Week8, updated 11-Sep-2017 )
Conducted by: Minh Tran
Evidence of work: https://marvelapp.com/4iga8bd/screen/32252576
Prototype is a high fidelity representation of the final product, it aims to similate the experience and interaction between the web application and the users in order to step into the final refinement for the final product.
Prototype
Conducted by: Jeremy Ng (Srpint 1, Week9, updated 18-Sep-2017 )
Evidence of work: https://marvelapp.com/4iga8bd/screen/32252576
Usability testing is a technique used in user-centered interaction design to evaluate a product by testing it on users.
Conducted by: Minh Tran & Ned Gordon (Sprint 2, Week10, 19-Sep-2017 )
Plan after user testing 1, we decided to slightly modify the design and flow of the design, work will be evenly distributed to all team members.
Evidence of work:
Script: https://drive.google.com/open?id=0B_8MdQuvq7lgdWpjeThERDBiUmc
Raw Data: https://drive.google.com/open?id=0B_8MdQuvq7lgdWpjeThERDBiUmc
Wireframe is the skeleton framework of the interface of the web application, it is used for creating a better representation of idea through lines and vectors.
Wireframe version 2 (Sprint 2, Week10, updated 1-Oct-2017 )
Conducted by: Kelvin Ding Wei Sheng, Edi Cheung
Evidence of work: https://drive.google.com/drive/folders/0B2GxQ6YSknlCTHYyYWpNcDMtYzQ?usp=sharing
User journey map is a demonstration of the user behaviour through identifying their goal, motivation, difficulties and the tasks that user looking to achieve.
User journry map version 2 (Sprint 2, Week10, updated 3-Oct-2017 )
Conducted by: Jeremy Ng, Edi Cheung
Evidence of work:
Mockup is a realistic desgin representaion of the layout of the web application with the support of the visual design, visualised content and basic functionalities of the product.
Mockup user testing 3 (Srpint 2, Week10, updated 2-Oct-2017 )
Conducted by: Kelvin Ding Wei Sheng, Minh Tran
Evidence of work: https://drive.google.com/open?id=0B7qYjwpry_vPeDZaYk1oeE15Z2c
Prototype is a high fidelity representation of the final product, it aims to similate the experience and interaction between the web application and the users in order to step into the final refinement for the final product.
Conducted by: Jeremy Ng (Srpint 2, Week11, 9-Oct-2017 )
Evidence of work: https://munch-box.appspot.com/login
Mobile Web Prototype is a representation of the final product, The aim of this product is to simulate experience on devices that do not have the application on it and also interaction between the application and the users, This will help the team to refine the final product as per feedbacks gathered from the user.
Conducted by: Jeremy Ng (Sprint3, Week12, updated 18-Oct-2017 )
Evidence of work: https://munch-box.appspot.com/login
Mobile Prototype is a representation of the final product, it's aim is to simulate the experience and interaction between the web application/mobile application and the user to help with refining the final product.
Conducted by: Kelvin Ding Wei Sheng (Sprint3, Week12, 17-Oct-2017 )
Evidence of work: https://drive.google.com/file/d/0B2GxQ6YSknlCRFJXVWFySHN6VHc/view?usp=sharing
Create and maintain sprites for the functional prototype, in order to maintain the styling and the design guidelines as per discussed during our standups and meetings. This helps ensure that the application design will be consistant throughout.
Conducted by: Edi Cheung (Sprint3, Week12, 17-Oct-2017 )
Evidence of work: https://drive.google.com/drive/folders/0Bz9R1CjOQ21AVmtENXVNa0c0SWM?usp=sharing
Create a clear flow of diagram to guide first time user running through the application.
Conducted by: Jeremy Ng (Sprint3, Week12, 20-Oct-2017 )
Evidence of work: https://drive.google.com/open?id=0B7qYjwpry_vPckF3eHVWQ3FMOVE
Creating a main promotional poster for the upcoming showcase give potential user a general overview of the munchbox concept and the aim/problem we are trying to achieve and solve.
Conducted by: Minh Tran (Sprint3, Week12, 18-Oct-2017 )
Evidence of work: https://drive.google.com/file/d/0B8g3K06eAqeOaW9rdVQ3alFLRHM/view?usp=sharing
Creating a main promotional brochure for the upcoming showcase to give potential user a detailed rundown of what the munchbox concept is about, instructions on how to use it and the aim/problem we are trying to achieve/solve with the concept.
Conducted by: Ned Gordon (Sprint3, Week12, 20-Oct-2017 )
Evidence of work:
V.1 https://drive.google.com/open?id=0B_8MdQuvq7lgaGJySGxHM1Y2MzQ
V.2 https://drive.google.com/open?id=0B_8MdQuvq7lgQ3FxUW1JMGlWQlU
Creating a promotional flyer which breifly run throught the concept, ideal user experience, and key features of the application.
Conducted by: Edi Cheung, Kelvin Ding Wei Sheng, Jeremy Ng (Sprint3, Week12, 22-Oct-2017 )
Evidence of work: https://drive.google.com/open?id=0B2GxQ6YSknlCeUxWLUFRb0JhWVk
We will hold meetings in the studio sessions - members are expected to attend, or to notify their teammates, ideally within 24 hours, if they cannot make it via the Slack group or SMS. Other meetings will be arranged as necessary, arranged a week in advance, to ensure that all members can attend. If members cannot attend, arrangements will be made to facilitate the meeting through Google Hangouts. Normal communication will be through slack and email. Members are expected to check these as often as possible and at least every 2 working days, and should notify the group if they are going to be out of contact for more than a 3 working days. Any information which is produced for the development of the project must be submitted to either the shared google drive or github repository, ‘Frying-Nemo’. Any information or links which are not required by the entire/majority of the group may be shared via Slack, where appropriate. Google Drive and Github were chosen due to the permanency of their storage options, as opposed to Slack which deletes content after a period of time, as well as the ease in which each member’s contributions towards the team can be tracked.
Tasks will be allocated using Scrum principles and through discussion within the group. Group members are expected to do their best to deliver tasks on time, and should contact the group in advance if they anticipate being unable to do so. Tasks will be posted on Trello. The division of labour in the team will be assessed halfway through the project to determine if each member has been contributing roughly the same amount of story points to the project. If one team member is contributing 15% or less story points relative to other team members, this will be considered a major breach and dealt with in the guidelines below. Dispute Resolution
A minor non-compliance issue is defined as an action that does not seriously undermine the quality of the project or function of the group but still impedes progress to a degree. Such infractions can usually be quickly amended by a willing team member with no overall impact on the project. Examples:
- Being more than 15 minutes late to two meetings or more without good reason
- Missing more than two meetings without good reason
- Not completing work by an agreed upon date, if this date is before the actual due date of the material
- Being unproductive or disruptive at meetings
- Taking on too much work, not asking for help and allowing this to impact the quality
- Altering someone else’s work without consulting them first
- Not responding to Online/Telephonic communications within 1 - 2 days
A major non-compliance issue is defined as a breach of the team agreement that severely impacts the quality of the project. Such actions may be irreparable or require a great deal of work and time to fix that the team may have to take off of other projects. Examples:
- Not completing work by the assignment due date
- Insulting/Undermining other team members during meetings or repeatedly causing non-constructive arguments
- Not attending any meetings
- Drastically changing or removing sections of the project completed by another team member without first consulting the team and abiding by their decision
- Completely ignoring all requests for communication within the Team
Minor or major non-compliance with this Agreement is likely to manifest as disputes or conflicts between team members.
The first step in resolving minor breaches will be to mention the issue with the team member/s committing the offence in a non confrontational manner, as it would be counter productive to let issues slowly mount over time and unfair to both the team member and the rest of the team. The entire team will look to find a resolution to the issue as soon as possible, so as to allow work to continue without disruption.
If this is the first or second minor breach a team member has committed then no further action will be taken. If a series of minor breaches occur then the third and subsequent breaches will be dealt with as if they were a major breach.
In the event of a major breach, a team meeting will be called to discuss the breach in a fair manner. Depending on the severity of the breach and the justification for lack of work the team may decide to redistribute the work in order to get the task complete. In any case, a member committing a first major breach will receive a verbal warning, along with a list of fair tasks allocated by the rest of the team to make up for the breach, with specific success criteria and a specific and fair deadline.
If the team member commits another major breach, or these tasks are not completed by the assigned deadline then a similar meeting will be called, where once again the other team members, by unanimous decision, may decide to redistribute the unfinished workload and the teaching staff of DECO3500 will be informed of this counterproductive attitude.. The team member will then receive a written warning and a new list of tasks to complete with specific success criteria and a specific deadline to demonstrate improvement.
If these tasks are not completed or another major breach is committed, the list of uncompleted deadlines, excuses and workload will be passed to the DECO3500 staff whereby peer assessment may be used to scale the offenders grade.
To realize and design the concept, we will need a couple of software to aid us in developing and designing our first prototype.
- MarvelApp
For User testing and prototyping our first design
- Android studio
To develop our first mobile application
- Slack
For day to day discussion of the project
- Facebook messenger
For urgent matters
- Adobe Photoshop & Illustrator
For designing of assets like application icons and etc
- Sharing Information
- Connecting
- Coordination
- Awareness
- Emotional Design
- Asynchronous Interaction
- Asynchronous Distributed interaction
OccupyTheory. (2014). Unhealthy School Lunches Statistics. [online] Available at: https://occupytheory.org/unhealthy-school-lunches-statistics/ [Accessed 22 Aug. 2017].
Tavernise, S. (2015). School Lunches Becoming Healthier, Statistics Indicate. [online] Nytimes.com. Available at: https://www.nytimes.com/2015/08/28/health/school-lunches-becoming-healthier-statistics-indicate.html [Accessed 22 Aug. 2017].