Question

c) What is a design constraint? Give an example? d) What is scalability? What type of requirements would scalability fall under?

Answer 1

what is a design constraint? give an example?

A design constraint refers to a limitation on the requirements and / or operation conditions under which a robot is expected to operate. A design constraint can , for example, affect the robot shape,the robot operation features, and the robot functionality.

A design constraint can be also related to other aspects such as the manufacturing technology or the avilable budget for the construction of a robot.

Some specific examples of design contarints would be:

• An icon that has to be 1:1 ratio and visible form across a room to signal an exit at an airport for travelers that don't speak your language.
• A logo redesign that has to have the same colors as the previous design.
• A homepage design that coverts higher for a specific demographic
• Or, my favorite, perfessional constraints that are mandated from licensing boards. Lawyers here aren't allowed to claim a specialty within the law, so there are some design constraints around that. Licenced fiduciaries that are financial advisors can't claim any results or except any testimonials and regulated by FINRA.

What is scalability? whta type of requirements would scalability fall under?

Scalability is an attribute that describes the ability of a process, network , software or organization to grow and manage incresed demand. A system , business or software that is described as sxcalable has an advantage because it is more adaptable to the changing needs or demands of its users or clients.

Internet of things system might be designed with scalability as a basic requirement.

When defining scalability requirements, consider the following:

• Is there an anticipated increase in entry volume?
• How many new users are expacted within the next few years?
• What is the expected growth rate, over the next few years, in term of data, users, and client applications?
• Are any new business processes expected?

Increase CPU estimates to make sure that your deployment does not have to be scaled permaturely. Look at the anticipated milestones for scaling and projected load increase over time to make sure that you allow enough latent capacity to reach the milestones.