Viability of Design solution

8.1a Critically evaluating how a design solution has met its intended requirements, including:

1. Functionality. The functionality of a product can be described as 'The purpose that something is designed or expected to fulfil'.
2. Ease of use and inclusivity of the solution. Usability is the ease of use and learnability of a human-made object such as a tool or device. In software engineering, usability is the degree to which a software can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use.
3. User needs. User needs are the needs that a user has of a service, and which that service must satisfy for the user to get the right outcome for them. Services designed around users and their needs: are more likely to be used.

8.1b Demonstrate an understanding of the needs and methods for testing design solutions with stakeholders throughout the design development, and when testing the success of a product or system

1. The first step in user testing is to get in contact with the users of your solution. Go back to your problem statement, and remember your potential users. You will want to test your solution on this group of people.
2. When it comes to testing, there is no such thing as too many testers! The more people that you are able to test with the more you will find out. So try to find as many users as you can who are willing to help you. A good goal to reach for is three to five users for each round of testing.
3. The second step, after you have located three to five users, is to present your solution to these users while the users are in the problem environment. The problem environment is the situation or atmosphere in which the problem you are trying to solve happens.
   1. If your solution is a product, give the product to the users in the environment where they would use it. For example, if you designed a pair of sunglasses, you would give your sunglasses to the users outside while the weather is sunny. You wouldn't ask them to try the sunglasses at night or indoors, because those aren't situations where they would be using sunglasses.
   2. If your solution is a website or software product, ask users to test it on computers. You wouldn't want to just show them pictures or explain the website, because how they interact with the computer itself is also important.
   3. If your solution is an environment or experience, place your user in that environment or experience, and see how they react. For example, if you designed an after-school program for students, invite users to attend this program or a mock version of it. However, in many cases, having your users actually visit your designed environment or go through your designed experience will not be possible. An example is a student who designed a new school bus but obviously does not have an actual bus to use for testing. In a case like this, use a storyboard to present your solution to the users.
4. The third and final step of user testing is observing the interaction between the user and your solution. Record your observations in your design notebook. Watch closely as people use your product, navigate your website, or go through your designed environment or experience. Listen to what they say, but also watch what they do, see how they react, note where or when they get confused, and write down everything that happens during their interaction with the solution. Below are three questions to ask during testing. The answers will be helpful when you move onto the redesign phase of test and redesign.
5. Are your users able to overcome the problem by using or interacting with your solution?
   1. If yes, why are they successful?
   2. If no, what problems do they encounter that prevent them from being successful?
6. Do the users ever need to ask you any questions when using or interacting with your solution?
   1. If yes, what questions do they ask? During what part of their interaction do they ask these questions?
7. Do the users interact with your solution exactly the way that you intended for them to?
   1. If no, what do they do differently?
   2. If you have measurable targets for your solution, did you meet them?

8.1c Demonstrate an understanding of the importance of testing the feasibility of getting a product to market including considerations of cost, packaging and appeal.

1. This assessment is based on an outline design of system requirements, to determine whether the company has the technical expertise to handle completion of the project. When writing a feasibility report, the following should be taken to consideration:
2. A brief description of the business to assess more possible factors which could affect the study
   1. The part of the business being examined
   2. The human and economic factor
   3. The possible solutions to the problem
3. At this level, the concern is whether the proposal is both technically feasible (assuming moderate cost).
4. The technical feasibility assessment is focused on gaining an understanding of the present technical resources of the organization and their applicability to the expected needs of the proposed system. It is an evaluation of the hardware and software and how it meets the need of the proposed system.

8.1d Understanding the relevant standards that need to be met and how to ensure these are delivered

British Standards Institute (BSI)

1. Click here to go to the BSI webpage.

International Organisation for Standardisation (ISO) specific to the subject

1. Click here to go to the ISO website. Assess whether the design solution meets the criteria of the technical specification

Design Engineering homepage