In-house Project - Away Days

By: Alex - Karwan - Patrick - Suraj

Hosted on AWS Away Days

Setup:

Make sure you have Git and Node (v18) installed.

Clone this repo and cd into the directory.

Run npm install to install all the dependencies.

To run the server npm start

Reach out to us for access to the dev environment.

User stories:

Core

• As a sports enthusiast I would like to see sporting events around the world
• As a host I would like to share/host new experiences so that I can meet new people
• As a curious person I would like to view detailed information about the hosts so that I can feel safe
• As a concerned host I would like to know more about the person that's potentially staying with me
• As a concerned user I would like to see what other people have to say about the host I will stay with

Stretch

• As a traveller I would like to know how far the events are from the house.
• As a social user I would like to get information about nearby facilities
• As a person that doesn't recall names, I would like to have a visual representation of where the event will be
• As a person concerned with my privacy I would like to know that my personal details are safe
• As a generous person I would like to invite people to sporting events so that I give back to the community

Documentation

What are you building?

• It became apparent that there was a hole to be filled with platform to bring together sports fans. What if Couchsurfing met Meetup? This mashup is what we decided to build.

Why are you building it?

• To make it easier for people to find tickets for sporting events with a place to stay.

Project scope

What are you not building?

• We're not building a complete copy of couchsurfing.

How did you decide what features were important?

• We conducted user research using a lo-fi wireframe and flow in Figma. From user feedback and our website inspirations, we managed to determine what would be the core functionality and features for our website.

Project plan

How are you going to structure your sprints?

• We split our project idea into multiple features - features that will be used across the platform. Once those main features were identified we decided to work on them first. The features would be built in a self-contained environment to later bring them together.

What order are you going to build in?

1. Folder structure
2. Database
3. Essential Features to deliver a minimal viable product
4. Create the product pages using the components/features we built

How did user research inform your plan?

• We changed various aspects of each page, according to what our users told us. Thanks to the feedback received, it was brought to our attention that safety was a big factor in the product. How the users would interact with each other, how they would find out about each other before said interaction. Those became the priority for us - which was not the case before the user research.

Requirement analysis

Project learnings

• AWS Amplify, React, SASS

Did your team work effectively?

• Worked efficiently to build the components and features.

What would you do differently next time?

• Finish the feature functionality.

Research and findings

What did you find out from user testing?

• That reviews are very important and user bio.

Project outcomes

Recommendations and conclusions

What features would you prioritise to build next?

A chat feature

Was the project a success?

We are quite happy with what we produced.

Software Development Lifecycle stages

Planning

What roles did your team take on?

Explain the roles and responsibilities of all people working within the software development lifecycle, and how they relate to the project (K2)

Did these roles help your team work effectively?

Outline how teams work effectively to produce software and how to contribute appropriately (K6)

Compare and contrast the requirements of a software development team, and how they would ensure that each member (including themselves) were able to make a contribution (K6)

Analysis

What might be the intended and unintended consequences of building this product?

Design

How did you plan a user experience?

Using Figma

What technical decisions did you make?

Server-render vs client-render vs both

Client-render

Relational or non-relational or no DB

Non-relational DB

Self-hosted or platform-as-a-service

Frontend first vs DB first

Did you create a technical specification?

Review methods of software design with reference to functional/technical specifications and apply a justified approach to software development (K11, S11, S12)

Implementation/Build

How did you ensure your code was good?

We had the best QA.

Create logical and maintainable code to deliver project outcomes, explaining their choice of approach. (S1)

What interesting technical problems did you have to solve?

How to query and add data to our AWS Amplify database.

Outline and apply the rationale and use of algorithms, logic and data structures. (K9, S16)

How did you debug issues that arose?

Searched in Google. Asked the other people in our group.

Apply structured techniques to problem solving to identify and resolve issues and debug basic flaws in code (S7)

Test

How did you verify your project worked correctly?

Identify and create test scenarios which satisfy the project specification (S6)

Did writing automated tests catch any bugs?

Analyse unit testing results and review the outcomes, correcting errors. (S4)

Deploy

Where/how did you deploy your application?

AWS Amplify

Review and justify their contribution to building, managing and deploying code into the relevant environment in accordance with the project specification (S10)

What problems did you encounter during deployment?

Right at the end of the build we had deployment problems.

Maintain

Is it easy for someone make changes to the codebase?

Could a new person quickly be onboarded to contribute?