Make PowerPoint slides Discuss current app design issues and considerations 1 a

Make PowerPoint slides
Discuss current app design issues and considerations 1 and 1/2 lides
Explain the relationship between mobile apps and websites. 1 slides
Discuss what YOU think the future of mobile apps will be 1slides ( think outside of box and show)
I need a full explanation of each bullet points too of slides content on a separate docs page ( simple and easy to understand ( for myself )not on PowerPoint slides. It will be helpful for me to present
Try using the 6×6 rule to keep your content concise and clean looking. The 6×6 rule means a maximum of six bullet points per slide and six words per bullet point
Keep the colors simple
Use charts where applicable
Use notes section of slide
Include transitions
Include use of graphics / animations
Note: Wikipedia and similar Websites do not qualify as quality resources.
Reference sources cannot be > 5 years of age
Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format.
This is group presentation slides so I have attached the slides of the group and u can add my slides to it.
U can take add content from the residency docs too thats my original docs

Introduction slidesProvide a problem statement for your whole team project that

Introduction slidesProvide a problem statement for your whole team project that includes the overall objective of your whole robot swarm/collection.
Remember to focus on the problem’s goal without pre-conceiving a solution. Please refer to the previous deliverable to better understand how a problem statement should be. E.g. you can say ‘Rats are a common problem in NYC subway system, we are developing an automated solution to contain rodent population’.
Briefly provide a description of the problem context /application area that the proposed design focuses on addressing, and what’s currently lacking in it. How are you adding value economically, or individually, or socially, or environmentally, or technologically.
Briefly mention direct customers: Who are the actual end-users and actual buyers?
Briefly mention indirect customers: Who are other relevant people that indirectly may affect the design? (E.g., other users, investors, policy makers, etc.)
Provide a list of design requirements that a successful robot swarm/collection must fulfill. These should be the same as (or an updated version of) what you proposed in the first/second deliverable. These are the requirements for the overall robot swarm, not the individual robots.
Also remember the rules regarding the requirements from the first deliverable. They should be measurable, quantitative (numbers), and specific. Your design requirements must come from the customer’s needs and wants. They are not the constraints artificially imposed by the course guidelines (e.g., “The design shall have at least two sensors” is not a customer-based requirement).
List what types of individual robots are included in the swarm/collection and which belong to which team member. In a few words (less than a sentence), mention what each robot does. No need to provide details that is for the next section.
List them in the order they will appear in the presentation.
Individual Robots slides
In this collection of slides each team member (one after the other) will present their individual robot (as requested below).Mechanical Design slides
While showing the detailed CAD model / assembly of your robot from multiple viewpoints (as snapshots), clearly describe how various parts of your robot are connected together and function together. Clearly mention all the mechanical parts of your design (e.g., body frame, shafts, beams, etc. as necessary). Mention (and point out) all the sensors, actuators, and electronic parts. Clearly mention how all these elements function together to make your design work. Mention the key features.
Briefly mention and justify any changes since the proposal (if any).
Only, if you made the robot using physical parts, you can just show pictures of your robot from multiple angles. You are exempt from the CAD model of the robot. You may even hold it while presenting/explaining.
Most of your CAD design may simply be a combination of boxes and cylinders with slots/holes in them. For example, a motor can just be a cylinder with a shaft (another cylinder) coming from it, an Arduino can just be a box (give it a different color though). Show all the components needed e.g. shafts and bearings, pulleys, wheels, gearbox, sensors, actuators, etc. You may idealize them as combinations of boxes, cylinders, and holes. You don’t need to show any electrical wires, or pulley cables.
There should be enough detail in your design! But don’t go way overboard. You hopefully won’t need more than 10-20 parts in your model. Don’t worry about rendering, but adding some colors will help! Surely add some dimensions. It should be at the right zoom level to see clearly.
Once again, if you made the robot using physical parts, you can show a picture of your robot from multiple angles, instead of any CAD drawing. You may even hold it while presenting/explaining.
If a 3D (isometric) view doesn’t show all the relevant inside details, you can make some component transparent (hood, roof, outer-covering) to show what’s inside. Hence, presenting multiple pictures.
Circuit Design slides
While showing the TinkerCAD circuit for your robot (or a picture of your actual circuit, made in real life), describe how various sensors and actuators of your robot are connected together and function together. Clearly mention (and point out) all the sensors, actuators, and electronic parts.
Briefly mention and justify any changes since the proposal (if any).
Make sure the circuit pictures/TinkerCAD screen has the right zoom level, otherwise you may split it over multiple slides.
Arduino Code and flowchart slidesShow and explain the overall logic of the program as a flowchart (activity diagram). Make sure the flowchart has a sufficient zoom level (or consider splitting it over multiple slides)
The structure/content of your flowchart can follow the instructions similar to those given in part-4 of the “Activity: Arduino Coding (Individual)”
Briefly mention and justify any changes since the proposal (if any).
While describing the activity diagram (flowchart)Mention what type of information will your robot receive from the others (And/or the central control hub), to initiate its designated tasks. These are the inputs to the robot.
Mention what type of information will your robot receive from the environment through the sensors. These are also the inputs to the robot.
Mention what actions will your robot do with all combinations of these inputs (e.g. if the presence of a fire is detected by a light sensor, how will the robot and its actuators react). These are the processes/outputs of the robot.
Mention what type of information will your robot transmit to the others, or the central control hub, based on the inputs/processes above. These are also the outputs of the robots.
Your activity diagram must clearly show all possible combinations of inputs and outputs, in a concise way.
Include the pictures/snippets of your actual Arduino code also (though in interest of time, you don’t need to speak about every line/concept in the code). Make sure these have sufficient zoom level to see the code. Instead of pictures/snippets, you may even very briefly just scroll through your whole code.
Demonstration
Now it is time to show how various systems of the robot all function together.
If you are demonstrating via TinkerCAD, please share the screen, run the simulation with your Arduino code and show various input-output combinations from your flowchart. Show how the robot’s actuators (motors, servomotors, etc.) move according to the information received from the other robots or the central hub, or the sensors. E.g., show the actuators move, as you manually change the light for light sensor during simulation, or obstacle in front of distance sensor etc.
The information that the robot receives from or sends to the other robots/central hub, may be coded as single alphanumeric characters (e.g. 1, 2, 3, a, A, b, B, @, !, etc. ) or as text strings (e.g. Robot1_TurnLeft). For demonstration purposesthe information to be sent can be displayed by your robot on the Serial monitor using the Serial.print() type of functions,
the information to be received can by typed by YOU during the demonstration into the serial monitor and then “sent” to the code as single alphanumeric characters or as text strings. The Arduino code shall receive this information using the Serial.read() or Serial.readString() function and then perform the designated tasks with that information. You may also use the IR remote and its sensor to send information to the robot instead of Serial.read() etc.
If you made a physical robot, you can demonstrate its functionality in real time. Your Arduino can send/receive information (alphanumeric) either through a Bluetooth module and an android phone, or a IR sensor with a remote, or just simply through the Serial monitor on your laptop and the USB wire connecting the computer to the Arduino (It is ok if your robot is tethered to the computer by a USB wire during the demonstration).
Collective Behavior slides
Clearly explain the collective behavior of the robots through an overall activity diagram (flowchart). Refer to the flowchart instructions above (from the individual robots section)
This flowchart should clearly show the interaction of input/output information between each robot (and the central hub if needed). Be concise but complete!
If you want some extra credit now show and explain the MATLAB code you wrote for the robots to collaborate. Hopefully, it does what you explained via the activity diagram. In interest of time, you don’t need to go over every line of the code. The activity diagram, well explained, should suffice. To show the code, you may include the snippets of the code (with sufficient zoom) or you may just scroll through the code while sharing it on a screen (with sufficient zoom).
Now, run the MATLAB file so that the viewer can see the robots (represented as dots) move as expected. Explain as needed.
Entrepreneurial Aspects slides
Budget: Even though you only made a prototype (a scaled version of the actual product), what will be the cost of the actual market ready system? Make a reasonably accurate estimate, justified by research and analysis of the cost of various components, labor, etc. You may provide references.
Is it a new concept? Has something similar been done before? Mention what already exists in the market (direct competitors or similar products). You may provide information/links and references for these products.
How is your design adding value to what already exists? How does it compare to others in cost and other aspects? Explain how will it better address the customer needs. Why should we/customers etc. invest in your design. (Some considerations: sometime people like to pay more for the brand value, sometimes your product can target only a special market not general population)
Summary slide(s)What lessons you have learned while working on this project, in terms of engineering design, entrepreneurial mindset, management, working in the team etc.
What would you do differently if you were to do this project again?
Summarize the whole presentation in a few sentences. Provide a layout of all that you presented today but focusing on the key points.
References slide(s)
Include the references used as a numbered list in an appropriate format. It should include citations for all the references used (e.g. source of information for problem context, budget, existing products, sources for any images/pictures, etc.). Citation number should also appear in the slide where information was referred.
In interest of time, you don’t need to go over the references just leave them as the final slide.
i have attached a sample of the project.