Requirements
Presentation (in-person)
| Requirement | |
|---|---|
| MUST | Top-level schematic diagram (Level 1 Data Flow Diagram) |
| MUST | Cannot exceed 5 min |
| MUST | Talk about functionality and code, how you have integrated components |
| MUST | You should have a pre-recording (not sure on the specifics of this) |
Submission Requirements
| Requirement | |
|---|---|
| MUST | Code submission should include a Declaration of Code Authorship |
Report
| Requirement | |
|---|---|
| A - B | Self-evaluation of the achieved implementation for Sections A-B (please be brief and precise, no introductions or background information needed). - Including a functional description of your program, and discussion of your - Major design decisions. - Please include top-level design diagrams only. - Do not exceed 2 pages. |
| C | - Maximum 800 words + charts or diagrams describing - System analysis discussion including: 1. deployment on cloud infrastructure (pros, cons, challenges, & alternate solutions) 2. requirements for cloud migration (look at document again didn’t make much sense) 3. analysis of QoS (aka JMeter for load testing, and Cloud Watch for other stuff), think of scalability and fault tolerance (there must be something wrong so point it out) - (for a 1st) use citations from academic sources, and concrete examples of cloud-based solutions |
| D | - Maximum 1000 words - Select 4 of the 8V’s and describe how they relate to the application, each with an example - Discuss infrastructure and software implications that big data could have on the app, select the most appropiate cloud computing model that could address the issues - (for a 1st) use citations from academic sources, and concrete examples of cloud-based solutions |
None-user Requirements
| Requirement | |
|---|---|
| MUST | Use a deployment service like AWS pipelines |
| MUST | Use a quality of service (QoS) measurement tool Load testing JMeter or Gatling Other stuff Cloud Watch |
App Requirements
| Requirement | |
|---|---|
| MUST | It is called ‘Travel Buddy Finder’ |
| API | |
| MUST | The cloud must have a REST API |
| MUST | Post a new trip idea That must have at-least these attributes: { “userID”: “123”, “tripID”: “123”, “location”: “London”, “date”: “129308122”, “weather”: “Shit”, } |
| MUST | Query for existing trips That must have at-least these attributes: { “location”: “London”, } |
| MUST | Express interest in a trip That must have at-least these attributes: { “userID”: “123”, “tripID”: “123”, } |
| MUST | Accept interest in a trip (Same as below?) View interest in the current users trip post That must have at-least these attributes: { “userID”: “123”, “tripID”: “123”, } |
| MUST | User should see weather forecast details for the trip |
| MUST | User must be able to view past & on-going trips |
| MUST | Cloud can send a new UID to client (which can be used for user or trip ID) |
| MUST | Communication must be done using JSON |
| MUST | Cloud must get any UIDs from an external API |
| MUST | Cloud must get the weather from an external API |
| MUST | Use something better for error handling than just try catch, aka DLQ or cloudwatch |
| UI | |
| MUST | UI should be at a commercial level of quality (looks wise) |
Exe 1st Requirements
| Requirement | Done | |
|---|---|---|
| MUST | Dont use Java | ✅ |
| ??? | User can communicate with other Users (does this mean messaging, or comments on trips) | |
| SHOULD (good) | Front-end updates list of trips with-out needing to press an update button | ✅ |
| MUST | Run an orchestrator service (says Tomcat on Azure), this should include ECS as it is an AWS equiverlent | ✅ |
| SHOULD (good) | Caching data from external service (could be used for weather) | ✅ |
| SHOULD (good) | Use a message queue SQS | ✅ |
| COULD (meh) | Implement some external REST API | ✅ |
| COULD (meh) | Use XML aswell as JSON | |