Do not blindly believe what the computer (or the internet) tells you. Use common sense.
Requirement flow down ultimately is realized in the components selected.
Please show how the engineering method resulted in the selection of key electronic and mechanical components.
This may result in the generation of higher level requirements. If this occurs highlight these new requirements.
For example, Pathfinders desert environment requirement needed to be factored into the selection and design of the rotary encoder.
If your project has a user interface, (i.e. Arxterra Control App, etc.) make sure your images are screen captures of your original custom interface. Specifically, they should show the custom commands you have implemented.
All allocation reports’ format should not change from PDR (Expected, Actual, Uncertainty, Margin, Source)
Do not change “Expected” value to “Actual” value.
Leave Expected at PDR values.
Cost reports “Expected” should not change from PDR.
Do not show only money spent to date.
Table should clearly identify money spent to date and money to be spent.
Do not forget to give allocation resource report for 3D printing time if applicable
3DoT projects must follow 2,2,2 = 6 hr. print time
Multiple power reports are often required when using a 3DoT board
5v Boost current (mA)
3.7v Battery current (mA)
3.7 Battery capacity (Ahr)
Charging time (hr)
For battery capacity do not forget depth of discharge.
Finally, get your units right!
The best source of information is the datasheet, not a previous semester. For example, current capability of your battery.
Listing tasks (and only those tasks) along the Critical Path is required on the second slide in the schedule section.
Be on time to class (Your project team are counting on you).
Presentation are due an hour before class. Place in BeachBoard drop box.
Consult with your Management team (President, Project, and Division) on when they require your material so they can review.
Keep you division management in the loop! Remember, their grades are also based on the material you present.
This review material should allow time for the material to be revised if needed.
Software detailed definition, for the most part, should be completed by CDR. Software coding should not be far behind.
Clearly identify test versus actual mission ready code.
Overly simplistic PCB designs.
Duplication of tests reflects poorly on Division communication and coordination. For example; servo testing with hanging weight.
Draw a preliminary sketch of the design
Make a back of the envelope calculation
Conduct a trade-off study
Week 4: Design Process and Modeling – Models facilitate the design process. A model simplifies a system or process so that it may be better studied, understood, and used in a design. There are three common models used in engineering:
Solidworks designs are not models unless applied to a simulation. For example load testing.
Plagiarism from previous semesters leads to disaster.
You do not understand material presented.
Cable tree does not address plan for routing cables.