Story Board Updated

[blackm61]

Low-fidelity mockup of the application

http://www.betterprojects.net/2009/09/storyboarding-as-requirements-tool.html

Can use tools like Balsamiq

[Isaiahensley]

I'm going to create story boards for pages other than the homepage

[Isaiahensley]

I'm going to continue our story board by visualizing the pages each button will redirect you to

[Isaiahensley]

[Isaiahensley]

Keyvan made these critiques on the previous storyboard I did. I will be implementing this into our updated storyboard. Critique of Aquatic Rig's "Storyboard":

Definition Clarity:

Positive: The description provides a clear visualization of the home page's layout and the elements it contains. Critique: While the described content is valuable, it doesn't necessarily fit the traditional definition of a storyboard. A storyboard typically depicts a series of actions or user flows across multiple screens or stages of an application. Content Breakdown:

Positive: The buttons like Data Management, Robotic Information Gathering, Customer Support, and About suggest a well-thought-out categorization of the site's primary functions. The imagery and textual information seem relevant to the application's purpose. Critique: How do these buttons function? For instance, what happens when a user clicks on the "Data Management" button? This is where a traditional storyboard would come in handy, showcasing the user's journey through the application. Visualization & Functionality:

Positive: The emphasis on data visualization, robotic trajectories, and the use of deep neural networks indicates a strong focus on the application's core functionalities. Critique: How does the user interact with these visualizations? How do they upload a dataset? What feedback or results can they expect? Again, a storyboard could depict this flow. Footer Information:

Positive: Highlighting partners and having a copyright notice enhances the site's credibility and professionalism. Critique: It's good practice to ensure that any partner logos or names are used with permission. General Observations:

User Experience: While the layout provides an overview of what users can see, it's equally important to consider how users will interact with the site and what kind of experience they'll have.

Storyboard vs. Wireframe: The description sounds more like a wireframe (a skeletal layout of a webpage) than a storyboard. A storyboard would depict sequences, like how a user would move from the home page after clicking the "Data Management" button, what they'd see next, what actions they could take, and so on.

Interactivity & Flow: A genuine storyboard for Aquatic Rig might depict scenarios such as: "A researcher logs in, uploads a dataset, visualizes it, sets up a robot trajectory, and then sees predictions based on water currents."

In conclusion, while the described content for Aquatic Rig is valuable and provides insight into the application's layout, it might be beneficial to create a true storyboard that depicts user interactions and flows across the platform. This would offer a more comprehensive view of how the website will function from a user's perspective.

[spaude11]

We need to start using material design themes and UI for the updated storyboard.

[Isaiahensley]

[spaude11]

Looks good, we have to follow up with Keyvan's requirements for whats gonna be better design on storyboard.

[rpeters47]

Looks good.

[Isaiahensley]

I plan to use a similar format to this for the Data visualization selection screen with buttons at the top giving different options like graphs, charts,

[Isaiahensley]

[blackm61]

Looks good !

[spaude11]

Looks really great. Thanks for your work. We can close the issue now.

[rpeters47]

Closing Issue

[Isaiahensley]

I've completely changed our story board so that it gives a better illustration of how everything will work with uploading, processing, and visualizing datasets. I still need to work on the login/register section with a terms of service for example. I have not given any descriptions or guidance on how everything works in the story board on purpose to get your guys feedback on what is confusing without an explanation. Give me some ideas on what could be changed or additional features we could implement. @spaude11 @blackm61 @rpeters47

[spaude11]

Looks great, need to figure out what we gonna add as a index page. Also I feel like we are trying to change a lot of items since we started and till now. We have to figure out if we are in the same road as from the start.

[blackm61]

It looks good so far. But we also need to work on our log in page. And create a terms and conditions for it as well.

Also add something to our about us page too if we are keeping that section of the website. @Isaiahensley

[Isaiahensley]

Looks great, need to figure out what we gonna add as a index page. Also I feel like we are trying to change a lot of items since we started and till now. We have to figure out if we are in the same road as from the start.

I believe this new storyboard still followed our original idea but with more detail. Before, the storyboard said a user would upload a dataset and then, without any uploading or processing time, visualize the data. Now it clearly shows what’s happening in the backend for users. Along with this, it now gives a better illustration for how we will handle users datasets. They will have them saved on our website and be able to add and remove multiple .nc files

[Isaiahensley]

Changes: Added buttons on the home page for our About and Support pages Added our logo to the visualization tool Added a checkbox for terms & conditions in the login/register screen

ToDo: Provide a redirect and info for our terms & conditions links Completely remake the About page to show how the website functions Make tweaks to the support page to make it more intuitive Email confirmation popup when registering an account Various error screens for misuse of the websites functionality

[blackm61]

You should add a way to get back to the home screen on the page with the visualizations updated. Or maybe a way to get back to the visualizations upload page. @Isaiahensley

[blackm61]

Also---will the login page be a popup window, or will it be it's own separate page?????? If it is it's own separate page then you should put a way to get back to the regular homepage. @Isaiahensley

[rpeters47]

Whenever I register on a website, it usual ask me to confirm my password. That could be added to the register thingy.

[Isaiahensley]

The login/Register page is now just a popup on the main website page when you press the buttons in the top left. It allows you to switch between logging in and Creating an account. I added a text field to confirm your password using Richard's advice. The Login screen now has an option for "Forgot your password?". I honestly have no idea how we will have our website send out email confirmation and allow password changes so we will need to figure that out.

[Isaiahensley]

Whenever I register on a website, it usual ask me to confirm my password. That could be added to the register thingy.

I took this into consideration in the updated login/register screen I just uploaded.

[blackm61]

That looks a lot better @Isaiahensley We just need the about and support pages updated now.

[spaude11]

Looks good. We will review it with Professor keyvan and work on finalizing it

[rpeters47]

Everything looks good.