COP2271 – Spring 2020 Design Project

Team name: ____Gator Hacks________________________ Team # ___2___

Milestone 7 (M7): Beta 1.0

HYBRID MILESTONE

In this milestone, your team will prepare a Beta 1.0 version of your project solution.
Remember, in engineering, we work with incremental prototypes, and you add
functionality every time you have one prototype working. Be sure to share all files with
team members often! At no time during this project should only one member
of your team be in possession of project work and documentation.

Specific milestone steps

A. Revise previous documents

Revising Specially M2 and M6
We are now in a phase of this project where each milestone is a revision of the previous one.
M7 will be easier to do if you make sure you have revised specially your problem scoping
document (M2), and your M6 document:
 M2: you make sure your solution is responding to the problem you state in that
document. This means, you consider all the customer needs, the program outputs that
satisfies the needs, the inputs you need to create the outputs and that your program has to
create. Your program also satisfies all the functional and non/functional requirements and
abides the constraints.
 M6: Make sure you have thought about the functionality and logic of your project before
starting to code your solution
 Review and complement the other documents (M1 to M5) to make sure they all coherent
and traceable from each other.

B. Function
By the end of this milestone, your team will deliver a program with the following
functionality working:
 At the end of this milestone, your project must launch when
MATLAB_PROJECT_team# is typed at the MATLAB Command Window prompt
(when your Current Directory is set to your MATLAB_PROJECT folder). A screen with
your project title, your section number, your team number, your team member names, and
the options to see the citation screen, continue, or exit (see M6) must be shown to the user
as well according to your navigation plan.
 If the user selects the citations option, your program must launch the function
Citation_team#.
 If the user selects the option exit, the program should end.
 If the user selects the option continue, the functionality of your program should start.

Mendoza-Garcia page 1 M7 Beta 1

COP2271 – Spring 2020 Design Project

 The interactive functions that show the functionality of your program should be totally or
at least partially developed. For instance, it should be able to accept some user input and
if possible, respond in an appropriate fashion.
 If the user selects another option, you should make a validation, which typically will tell
the user their error, and throws back the program to the first screen.
It should be clear which team member is responsible for which interactive Function.
This is to be accomplished both in the naming of the individual Function as
yourinitials_MATLAB_team#, and in the comments section at the top of each function
m-file. It should also appear every time the function is called.
For this milestone M7, these functions may be called separately from the MATLAB
command window prompt. That is, all interactive Functions do not have to be connected into
one cohesive program at this point. But all files should be in all team members’ project directory
so that they can be run from any team member’s computer.

 As you have planned, all functions and main program must have a means of
exiting gracefully without shutting down MATLAB.

C. Commenting
Be sure to adequately comment all code that your team has developed within all .m files.
This is so if you are asked to open your files during the demo, the teaching team can interpret
your code. Your team could be asked during the demo to open any one of your .m files.

D. Beta 1.0 Demo

Next class, a member of your team will be randomly selected to demonstrate your
team’s Beta 1.0 version and collect feedback while the rest of your team keeps working
in the final deliverables. This means that all team members should have all of the files
necessary to demonstrate your project in a MATLAB_PROJECT folder.

The contents of your MATLAB_PROJECT folder should include only current .m, and
whatever input data, images, functions, or other supporting files you need to run your
program. DO NOT include your version control files.

E. Prepare final deliverables

Beyond your MATLAB program, your team should start thinking/preparing the following
deliverables to be submitted as part of the final submission:
1. Executive report (15): As any engineering team, you will have to write a summary report
of your work.
 You will assume that your audience are for example an executive board (e.g. your
customer if you have one), investors, or other people or group who could give you the
funding you need to make real this solution. Accordingly, you will create a report that
focus on presenting the problem, and the solution you are providing to that problem.
2. Final prototype (30): The final prototype will include all the documentation that shows
evidence that support the fact that your design solution was developed following a
rigorous process, and it will also include the code of your program:

Mendoza-Garcia page 2 M7 Beta 1

COP2271 – Spring 2020 Design Project

 Documents from M1 to M6, modified and aligned with your final solution. Your
documents will support and will be the evidence you need to support that your
solution was the result of a rigorous process.
o One way is to think that you are creating a story that is evidence-based.
 Functional MATLAB code that runs a final prototype (much more advanced than
Beta1 submission)
3. Final presentation video (10 points): Your team will create a “Shark-Tank”
style video showing the well-defined problem and how your design solution
(program) is addressing this problem (Please, spend in your “Shark Tank” video
style more time in explaining your problem than the one used by inventors in the
TV show. Still, think that you want your specific “audience” to connect with the
need ant that they easily agree with you that the problem is relevant and needs to
be funded. Watch this video for an idea on how you can talk about your design
solution in MATLAB: Watch and Learn From This Startup's Pitch to VC Tim
Draper ).

In your video, all the members of the team should appear. Although it is ideal
that as engineers you think about budget and the cost of your project, you will not
need to show how much your solution could cost or how much money you need
to make it a real product. Still, focus on what the problem is, and how you have
created a good possible (“the best?”) solution for it. Think about the idea of
advocating for, or “selling” your solution.
4. If you have a real customer, and can show proof of getting feedback from them
about your solution (10 extra-points). For example, you can add an email from the
customer in which he/she provides feedback about their perception of the solution.

F. Teammate contributions: Individually, write a short specific description of what you

contributed to this M7. Please use the sentence stems we provide to help structure these.
Please also keep in mind these guidelines:

1. Write your own contribution description including which interactive Function you wrote
the code for, and any additional team-level contributions, and provide to the recorder for
your team to compile into the team’s milestone document.
2. If you did not contribute to this milestone, then write “I did not contribute to this week’s
milestone” and send to the Milestone leader.
3. If one of your team members does not write his/her contribution description, then the
milestone leader should write “this team member did not provide a contribution
description this week.”
4. If one of your team members did not send a contribution description AND did not
contribute to the milestone, the milestone leader should write “this team member did not
provide a contribution description this week and did not contribute to this week’s
milestone.”
5. If any of you feel that one of your team member's descriptions is not accurate, please send
an email to your instructor so we can help resolve.
Mendoza-Garcia page 3 M7 Beta 1
COP2271 – Spring 2020 Design Project

Compile your contribution list with that of your teammates in the provided space in the
Design Worksheet. Save this completed M7 document (you can erase the instructions
section) as M7__team#.docx. One copy should be submitted.

G. Deliverables M7
 An updated web page all new material for M7 milestone in the M7 section, and your draft
versions of M9-ExecSumm, your iterated M1 to M6 (make sure you put a version name for
each). Be prepared to have your deliverables reviewed by a peer.
 Submission in Canvas of your MATLAB program as a zip file MATLAB_PROJECT, M7
milestone document (the design worksheet), and the draft version of M9-ExecSumm.
 A complete, up-to-date MATLAB_PROJECT folder should be available on each
teammate’s computer; one of you, chosen randomly, will demonstrate your solution.

Mendoza-Garcia page 4 M7 Beta 1

COP2271 – Spring 2020 Design Project

DESIGN WORKSHEET

Quality Control Checklist Checked by:___Camila Del Sol Pina

__________________________
Leader’s name for this Milestone
Quality submission, including web page and Canvas
Using a check mark for each box, check that:
 M7_team#.docs is complete, Submitted to Canvas, and uploaded to the web Page.
 Draft of M9-ExecSumm.docx is submitted to Canvas and uploaded to the Web page.
 your MATLAB_PROJECT zip file is uploaded to Canvas
 Evidence of data collected from direct users (if real) is included in your Web Page
 Improved documents from previous iterations are included (docx and pptx files).

E. Teammate contributions. Individually, identify your contribution to M7. Please use the
following stem sentences to help structure your description, as well as including what you’ve
learned about writing these contributions from previous milestones:

1. (replace with Team member 1’s name and use Track changes optionTuoxin Li)
contribution was:
 I contributed this work to the team’s work (i.e. not my individual function).
 I am working on this MATLAB program: [replace with function(s) name]coding
the input for users as staffs and designing screens by using GUI
 I accomplished these tasks towards my individual Function:

2. (replace with Team member 2’s name and use Track changes optionCamila Del Sol Pina)
contribution was:
 I contributed this work to the team’s work (i.e. not my individual function). I
uploaded new and updated files to the website
 I am working on this MATLAB program: [replace with function(s) name]loops,
inputs, outputs, and functions
 I accomplished these tasks towards my individual Function:

3. (replace with Team member 3’s name and use Track changes option) Karl Moody Jr
contribution was:
 I contributed this work to the team’s work (i.e. not my individual function).
 I am working on this MATLAB program: [replace with function(s) name]energy
usage and solar lifespan
 I accomplished these tasks towards my individual Function:

4. (replace with Team member 4’s name and use Track changes option) contribution was:
Kamila Hernandez
 I contributed this work to the team’s work (i.e. not my individual function).

Mendoza-Garcia page 5 M7 Beta 1

COP2271 – Spring 2020 Design Project

 I am working on this MATLAB program: [replace with function(s) name]

deleloping code to convert cost of power in the reitz union to cost of power in the
reitz union is solar panels were installed. Developed a code to determine how
much parking will cost on campus. Created the model of the Reitz parking garage
to use as a prototype for the “Live camera footage”. Began the GUI for the parking
suggestion.
 I accomplished these tasks towards my individual Function: backbode of the code,
correct values will be inputted once more information is obtained from UF staff.

Mendoza-Garcia page 6 M7 Beta 1