Biosphere-UGRADS_Pres Try 2

even though we were able to implement the apps that

you just saw in the demo, we did have some

challenges along the way.

In particular.

We had four challenges, but we were able to solve

each and every one of them first we have a

problem with visualizing the data.

So in the fall semester, when were originally researching the

software's, we didn't really find one that would be able

to take all of the data that we would be

given and make sure that it would display properly.

But then in the beginning of the semester of the

spring we were able to find a software called that

was able to visualize the data exactly how we wanted

it to.

Up next we had the AWS lambda has a six

megabyte max and most of the files that are going

to pass in our program are 20 to 30 megabytes.

So we kind of had a problem and we need

to figure out a way to pass smaller chunks.

So originally we were going to limit the user to

an 800 km radius.

But then we thought that was counterintuitive, since our apps

should be able to allow the user just like any

area. So instead we decided to implement a layered approach.

So we're going to start off with a small circle

and then we're going to keep analyzing the circles until

we get to the user selected size and then some

ate all the circles together to get the whole circle

together. Next we have a similar problem, but this was

with the Api Gateway timing out so after 30 seconds

of transferring the information that api gateway would time out.

So we had to find a way to transport less

information. So we're gonna separate the variables in the front

and back.

And we're going to do a layered approach for the

front and then do a layered approach for the second

part and emerge them together at the end.

The next challenge we had was getting data from the

clients. So as science is always evolving and we learn

new material.

We realize that the Mattingly model is incomplete, that at

the moment because the information is not available yet.

So it's important for us to be able to allow

the user to select this in the future.

Next we have our schedule in the fall, we were

focusing on mainly the requirements and a lot of the

logistical stuff.

So as you can see in the beginning, we did

team standards.

Then we did possible software as there's a lot of

different software possibilities that we could have selected.

And it was important to narrow down once it would

work best for us and then we have requirements acquisition.

So with the client, we focused on the main parts

of what they want in the finished product.

And then we have a technical demo that implemented all

the software that we researched before.

Next we have the spring schedule.

So on the top in the gray and the light

blue, you can see some front end components that we

completed at the beginning and then the back end components

and then in purple are some also front end components.

And then we're currently testing our application as well, writing

them and then based on some testing we did I

want to highlight that.

We did implement a large radius warning so once it

goes over large radius it might take longer and the

user needs to know that.

Then we add a description for the results variables.

And we are currently finishing up on notifying user when

no data exists.

So next we have our testing.

It was important that we were able to test our

app in particular.

We have three main three main goals.

Unit testing, integration testing and user testing.

So the unit testing is the foundation of our testing

because it focuses on the individual components.

And in order for us to move on the integration

testing, we need to make sure that they work by

themselves. Then we take the integration and we make sure

that they all work together seamlessly.

And then finally, if all that works out, then we

give it to the user to see if they can

use the app properly.

So for our project in particular for unit testing, we

have the AWS S three buckets that's going to store

our information.

We need to make sure it stores it properly and

the API gateway, we need to make sure that it

can transfer the information from the front end to the

back end properly.

And then the google maps ap can properly select to

get the users selected location.

Next we have integration testing.

So in the like green up here you can see

that one of them is to make sure that the

Api gateway can get the information, send the information to

the back end and then the back end can properly

send it and retrieve the information to the Api gateway.

And then in the bottom light blue you can see

the google maps needs to properly send the selected coordinates

to the back end.

And then, as I was mentioning earlier usability testing, it's

important for different users outside of our group to be

able to use our app without running into errors.

In particular, we had two scientists groups, three general user

groups and one policymaker who were able to test their

app. So in the future, since we have a pretty

working app, we, as we mentioned in the challenges section,

it's important for us to be able to implement new

scenarios as a science progresses.

And then in addition, a lot of the information of

our app is focused on areas in the tropics.

So, for example, in Africa and south America.

So it can be able very important for us to

reach these audiences.

We need to make sure that it's in their languages.

So we already have support for french and spanish but

maybe adding Portuguese or german will be important in the

future.

Biosphere-UGRADS_Pres Try 2

Chapters

Audio TranscriptAuto-generated