by admin | Dec 1, 2022 | Product Design
Introduction slides
Provide 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.
by admin | Sep 18, 2022 | Product Design
Learning Goal: I’m working on a product design project and need an explanation and answer to help me learn.
Greetings,
I need assistance with completing a Heuristic Evaluation on Instagram. I will provide you with a layout. Please make sure to follow the instruction of the project: Heuristic Evaluation Checklist
User Interface Information
Provide a description about the user interface. Discuss the purpose and provide information on the tasks that you would complete using the user interface.
Overall UI/UX
Review the user interface and experience. Discuss the usability overall, including learnability, effectiveness, efficient, engaging, and forgiving.
Learnability
The application is not complex so the user doesn’t have to put an extra effort to understand what the product is about and how to work with it to achieve a goal. The application should tell a story to reveal itself.
Effectiveness
The completeness and accuracy with which users achieve their goals.
Efficient
The speed and accuracy with which this work can be done.
Engaging
How pleasant, satisfying or interesting an application is to use.
Forgiving
The design allows the users to recover from errors and prevent errors by error detection and correction.
Heuristic Evaluation Checklist
Review the user interface and experience. Complete the heuristic evaluation.
Score: 0-Deficient, 1-Needs Improvement, 2-Fair, 3-Good, 4-Great, 5-Excellent.
Visibility of system status
The system should always keep users informed about what is going on, through appropriate feedback within a reasonable time.
Score:
Comments:
Match between system and the real world
The system should speak the users’ language, with words, phrases, and concepts familiar to the user, rather than system-oriented terms.
Score:
Comments:
User control and freedom
Users often choose system functions by mistake and will need a marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
Score:
Comments:
Consistency and standards
Users should not have to wonder whether different words, situations, or actions mean the same thing.
Score:
Comments:
Error prevention
Eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
Score:
Comments:
Recognition rather than recall
Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
Score:
Comments:
Flexibility and efficiency of use
The design should be easier to use for all the user groups. Even though we have only one set of a user group, then there would be novice users and experienced ones.
Score:
Comments:
Aesthetic and minimalist design
Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
Score:
Comments:
Help users recognize, diagnose, and recover from errors
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
Score:
Comments:
Help and documentation
Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.
Score:
Comments:
Summary
Provide a summary of the results of the evaluation. Discuss the strengths and weaknesses of the user interface and experience.
Strengths
Weaknesses
Recommendations
Based on the evaluations, provide three suggestions for improvement.
by admin | Jul 22, 2022 | Product Design
Learning Goal: I’m working on a product design project and need an explanation and answer to help me learn.
This assignment is for a product Management class. Create a brief PowerPoint presentation of the Cricket Dream 5G phone. The presentation should be no more than 2-3 slides and highlight:
Features that we would recommend the customer use to present to the consumer for each of their marketing channels for the device
Features and specifications that are relevant and unique to that phone and that are a competitive differentiator from other phones in that price-point
by admin | May 7, 2022 | Product Design
Learning Goal: I’m working on a product design project and need a sample draft to help me learn.greeting , i need help on a class diagram section of a project . About the project , it is a paid service . A financial advisor on stock market. Long story short this project aim to develop a model that predicts a market stock value , and gives the user of the service better insight of the market. I can share the use case ER , Functional requirements afterwards.
by admin | Mar 14, 2022 | Product Design
Learning Goal: I’m working on a product design multi-part question and need guidance to help me learn.Create two group personas, could be 2-3 persona’s for a group. The persona’s are for people who are going to use online therapy service such as Betterhelp.com: The personas should have details about them, type of person, interests, why they would use the service and they can’t all be the same, below is the specifications: Persona name
A drawing or photo (if you use someone else’s image, you should include the name of the creator and the URL to a web page containing the image somewhere in your document)
At least 3 character attributes. These will vary based on your project. For example, if designing a music player, some relevant attributes might include favorite genres of music, places where the persona listens to music, interest in new music (high/low), use of headphones vs. speakers, etc. These are examples of attributes that might have a meaningful impact on your design – the attributes you choose should come from your data collection and your thoughts about your evolving prototype.
A list of common tasks performed by this persona.
A 1-2 paragraph description of the persona.
Formatting your personasYou should represent each persona via a 1-page summary document; we saw some examples of this in class. You can format this however you want. We’d love to see personas that are formatted in interesting ways, and that are easy to skim and read to understand the persona.Note that all personas from your group should be similarly formatted and contain the same information – you should spend time before creating the personas figuring out what information the personas should contain, and time afterward ensuring that personas are formatted consistently.Where do our personas come from?Your personas should be data-driven. In other words, the attributes and characteristics addressed in your personas should reflect the ideas and insights you gained from your user research. For example, if you were designing a music player, and your interview participants talked about how it is calming to listen to music while on public transit, you might include listening locations as a character attribute and create a few personas that show the breadth of this attribute (i.e., one persona who listens to music on transit, another who plays music on a home stereo).Your personas do not need to directly copy your interview participants (although they can). You can also mix up details from several different people into a single persona. If your persona does represent a real person, you should still give them a new name and photo to protect their identity.If you find you do not have enough user data to create the number of required personas, you can draw on your own experiences, talk to friends and family, or do some online research (e.g. for a music player, reading online reviews and discussion about the latest music player devices).Summary document (between 0.5 and 1 page)In addition to your personas, you should include a separate document that briefly summarizes how your personas reflect the data you collected. In it, you should write briefly (~1 paragraph) about your choice of persona attributes and where they came from. Then, for each persona, you should describe (~1 paragraph each) where you included details from real users (and note where that data came from)
Requirements: 1-2 pages | .doc file
by admin | Mar 14, 2022 | Product Design
Learning Goal: I’m working on a product design multi-part question and need guidance to help me learn.Create two group personas, could be 2-3 persona’s for a group. The persona’s are for people who are going to use online therapy service such as Betterhelp.com: The personas should have details about them, type of person, interests, why they would use the service and they can’t all be the same, below is the specifications: Persona name
A drawing or photo (if you use someone else’s image, you should include the name of the creator and the URL to a web page containing the image somewhere in your document)
At least 3 character attributes. These will vary based on your project. For example, if designing a music player, some relevant attributes might include favorite genres of music, places where the persona listens to music, interest in new music (high/low), use of headphones vs. speakers, etc. These are examples of attributes that might have a meaningful impact on your design – the attributes you choose should come from your data collection and your thoughts about your evolving prototype.
A list of common tasks performed by this persona.
A 1-2 paragraph description of the persona.
Formatting your personasYou should represent each persona via a 1-page summary document; we saw some examples of this in class. You can format this however you want. We’d love to see personas that are formatted in interesting ways, and that are easy to skim and read to understand the persona.Note that all personas from your group should be similarly formatted and contain the same information – you should spend time before creating the personas figuring out what information the personas should contain, and time afterward ensuring that personas are formatted consistently.Where do our personas come from?Your personas should be data-driven. In other words, the attributes and characteristics addressed in your personas should reflect the ideas and insights you gained from your user research. For example, if you were designing a music player, and your interview participants talked about how it is calming to listen to music while on public transit, you might include listening locations as a character attribute and create a few personas that show the breadth of this attribute (i.e., one persona who listens to music on transit, another who plays music on a home stereo).Your personas do not need to directly copy your interview participants (although they can). You can also mix up details from several different people into a single persona. If your persona does represent a real person, you should still give them a new name and photo to protect their identity.If you find you do not have enough user data to create the number of required personas, you can draw on your own experiences, talk to friends and family, or do some online research (e.g. for a music player, reading online reviews and discussion about the latest music player devices).Summary document (between 0.5 and 1 page)In addition to your personas, you should include a separate document that briefly summarizes how your personas reflect the data you collected. In it, you should write briefly (~1 paragraph) about your choice of persona attributes and where they came from. Then, for each persona, you should describe (~1 paragraph each) where you included details from real users (and note where that data came from)
Requirements: 1-2 pages | .doc file
