Design and Testing: Syllabus

Downloaded From: www.EasyEngineering.
net
UNIT - III
3 Design and Testing
ww
Syllabus
Conceptualization - Industrial Design and User Interface Design - Introduction to Concept
w
generation Techniques – Challenges in Integration of Engineering Disciplines - Concept
.Ea
Screening & Evaluation - Detailed Design - Component Design and Verification –
Mechanical, Electronics and Software Subsystems - High Level Design/Low Level Design
syE
of S/W Program - Types of Prototypes, S/W Testing- Hardware Schematic, Component design,
Layout and Hardware Testing – Prototyping - Introduction to Rapid Prototyping and Rapid
ngi
Manufacturing - System Integration, Testing, Certification and Documentation.
Contents
nee
3.1
3.2
Conceptualization
Industrial Design and User Interface Design rin
3.3
3.4
Introduction to Concept Generation Techniques
Challenges in Integration of Engineering Disciplines
g .ne
3.5
3.6
3.7
Concept Screening and Evaluation
Detailed Design
Component Design and Verification
t
3.8 Mechanical, Electronics and Software Subsystems
3.9 High Level Design / Low Level Design of S/W Program
3.10 Software Testing
3.11 Hardware Schematic
3.12 Prototyping
3.13 System Integration Testing
3.14 Certification and Documentation
Two Marks Questions with Answers [Part A]
Review Questions [Part B]
Downloaded From: www.EasyEngineering.net

(3 - 1)
Foundation Skills in Integrated Product Development 3-2 Design and Testing
3.1 Conceptualization
Product design conceptualization is an important step during the early design phase of
a new product development, or during an upgrade of an existing product. Design
conceptualization services are needed when there is no clear idea or direction of how the
product will function or what would be the product final look.
Imaginationeering offers product design conceptualization services to help our clients
in providing them with few different concepts to choose from. The design
conceptualization phase will allow your company to explore possible concept solutions
ww
for your current product, problem, or challenge.
The Design Conceptualization section focuses on developing methods and tools for
w
understanding how products and services fit in people’s lives, in their full complexity.
.Ea
These methods and tools help designers understand the context of use for which they
design (e.g., contextmapping), and explore new possibilities of interaction (research
syE
through design, iterative interactive prototyping). They can be used as well as ways to
empower people to arrange their own lives (self-empowerment).
ngi
Keywords are: Context, Empathy, Empowerment, Participation, and Prototyping.
nee
Context: how does the product or service fit into the users’ everyday lives ‘world’, how
can we learn about the user’s needs and values, in research- and design sessions and
especially in their everyday contexts?
rin
them her, such as children, elderly, or people in other cultures? g
Empathy: how can designers step into the shoes of users that are very different from
.ne
Empowerment: how can design be used to increase involvement of citizens and
communities of users in matters that affect their wellbeing?
Participation: how can we involve diverse stakeholders, such as end-users and experts,
t
in design processes to increase the quality and adoption of products and services?
Prototyping: how can we quickly make working, interactive setups or visualize future
scenarios to experience situations that do not exist yet, and explore potential interactions?
3.2 Industrial Design and User Interface Design

Industrial Design (ID) is the professional practice of designing products, devices,
objects, and services used by millions of people around the world every day. Industrial
designers typically focus on the physical appearance, functionality and manufacturability
of a product, though they are often involved in far more during a development cycle. All
of this ultimately extends to the overall lasting value and experience a product or service
TECHNICAL PUBLICATIONS® - An up thrust for knowledge
provides for end-users. Every object that you interact with on a daily basis in your home,
office, school, or public setting is the result of a design process. During this process,
myriad decisions are made by an industrial designer (and their team) that are aimed at
improving your life through well-executed design. A user interface (UI) is the part of a
machine, product, or device with which a person interacts. Usually visual and tactile in
nature, a user interface is what an individual uses to make a machine or product do what
he wants it to do. The user interface should be intuitive and simple to use. Now that
people are using mobile devices and the digital age is flourishing, user interfaces are a
common part of physical product design. User interface designers and product designers
ww
work together to create products that seamlessly integrate the screen and the device itself,
as human interaction is embedded in products to combine the physical with the virtual.
w
User interface design is an important part of the user experience, as UI designers work to
.Ea
enhance the user’s interaction with products, both physical and digital. While the core
principles and goals of UI design are similar across physical and digital products, the two
syE
are not identical, with UI design for physical products requiring additional considerations
such as durability, actuation force, and other concerns not as applicable to designing the
ngi
UI for a digital product, while digital product UIs have their own unique considerations
nee
as well. User interface design includes expertise in human-machine interface, integrated
systems, user experience design, wireframes, graphic user interface (GUI) design, and
rin
developer’s toolkits. User interface design for products involves making items such as car
dashboards, LCD refrigerators, smart remote controls and TVs, and others that have a
display in the physical space.
g .ne
3.2.1 User Interface Design Principles
User interface designs must be functional and purposeful. Each element of the UI
design should meet users’ needs and help them accomplish the goal they set out to
t
achieve by using the product. Designers need to be problem solvers and understand how
their UIs will deliver a solution to the individuals who interact with them. As a result,
user interface designers also need to make their UIs as clear and usable as possible.
People do not want the UI to get in the way of using a product or device.
3.3 Introduction to Concept Generation Techniques

This is a creative phase of the design process, where several ideas or concepts are
generated. It is the divergent phase where many possibilities are considered without too
much judgment. For a typical design project, at least three conceptual design alternatives
should be generated. These concepts should be well documented, using sketches and
descriptions. There is no formula or set of rules to generate ideas out of thin air! Rather, a
set of practical strategies to help designers to enhance their inherent creativity, and to
facilitate the generation of new ideas, are presented next:
3.3.1 Concept Generation Strategies

 Strategy 1) Study and review existing design examples on a periodic basis.
Creativity cannot occur in a vacuum of knowledge! It often comes from exposure to
many other ideas, previous experience, and practical lessons.
 Strategy 2) Illustration and drawing is an important way to generate new ideas and
wwrecord them. Some designers are abstract thinkers while others are visual and
spatial thinkers. By preparing a drawing, limitations can be revealed, or ideas can
w
be built upon.
.Ea
 Strategy 3) Work within a team environment to generate new ideas. In this case,
techniques such as: Brainstorming, or the 6-3-5 method, can be an effective group
syE
activity for the generation of new ideas.
 Strategy 4) Morphological analysis is a technique that encourages a designer to
ngi
consider the combination of two seemingly unrelated concepts. Morphological
nee
analysis often leads to impractical ideas, however, those ideas may eventually lead
to practical ones.
rin
 Strategy 5) Allow ample time for reflection on ideas, and allow for iteration.
g
Creativity cannot be rushed, and setting a strict time-line for the creative phase may
limit the best solutions from emerging. Iteration is important, since often the
.ne
original concept leads to a better idea. Sometimes an idea suddenly emerges for a
t
design solution, while the designer is in the midst of another unrelated activity. This
is sometimes referred to as an “Ah-ha moment”, which is more likely to occur when
the creative process is given ample time.
3.4 Challenges in Integration of Engineering Disciplines

Integrated Engineering is a multi-disciplinary, design-project-based engineering
degree program.
Integrated Engineering is a program created to meet the demand for engineers skilled
in various disciplines, combining aspects from traditional engineering studies and liberal
arts. The demand arises from the current state of industry, where both the products
manufactured and the plants which make the products are progressing towards greater
diversity and sophistication. Recent studies had shown concern in both Canada and in the
United States that engineering graduates were not well-prepared for many of today's
multi-disciplinary and project-based workplaces. Several committees have been formed

to study this and have published some material. One Canadian study was done by the
Canadian Academy of Engineering and two of its main conclusions were:
 Engineering faculties should ensure that breadth of learning, beyond the technical
aspects of the specialist engineering discipline, is a major thrust in engineering
education.
 The engineering curriculum should emphasize problem-solving, design, and the
development of the learning skills of their students.
Integrated Engineers acquire background in core disciplines such as: materials, solid
ww
mechanics, fluid mechanics, and systems involving chemical, electro-mechanical,
and biological components.
w .Ea
3.5 Concept Screening and Evaluation
After generating ideas, use a variety of tools to analyze and filter the ideas to end up
syE
with those worth pursuing in more detail. These techniques can be applied iteratively as
new ideas emerge or as existing ideas are refined. The goal of concept screening and
ngi
scoring is to evaluate concepts before investing too much energy in detailed design work.
nee
Screening and scoring is about reducing many ideas into a smaller and more manageable
set. The quality of ideas in the final set depends on the quality of ideas in the initial set.
rin
Therefore, it is important to put good effort into the front end processes of customer
research and ideation.
g .ne
The outcomes are not always precise, i.e. a clear "winner" may not emerge. In that case,
devise an experiment (prototype) or new question(s) to use in evaluating concepts.
Perhaps the group needs to conduct more internal research (brainstorming, concept
sketching, cardboard mock-ups) or external research (web search, patent search, catalog
t
search).
3.5.1 Concept Screening

Concept screening is used to eliminate ideas that are not worth pursuing. The team
makes a go/no-go decisions using simple criteria
 Is the idea feasibile?
 Is the idea desirable?
 Does the technology exist, or does it need to be developed?
 If it needs to be developed does the team have the resources (skill, time, money) to
do the development?
The screening process may lead to new ideas or ways to combine ideas. The process
can be repeated, but it makes sense to use screening early in the design process when
there are several, high-level ideas. As the ideas become more detailed, other techniques
are more beneficial.
3.5.2 Concept Scoring

After specific design concepts have been evolved, concept scoring is used to establish a
qualitative hierarchy of design options. The concepts are scored numerically using simple
scales relative to a benchmark.
ww
1. Create a set of criteria to evaluate (score) the concepts : 3 to 7 is criteria is a good
number.
2.
3. w Identify a benchmark design
.Ea
Use a simple scale : -1, 0, 1 relative to the benchmark design. (A more detailed
scale -2, -1, 0, 1, 2 could be used if more detailed information on each concept is
available.)
syE
4.
ngi
Work across the criteria, not across the concepts. For example suppose that cost
and weight are two (of several) criteria. Rate all of the design concepts first by
5.
cost, and then by weight.
Tally and rank the scores nee
rin
The outcome is a smaller number of design concepts that the group decides to pursue.
to combine design concepts. g

The scoring exercise may generate additional ideas for new design concepts or for ways
.ne
The team may decide that future research is necessary. Any additional research should
be focused on answering specific questions. Failure to obtain clarity should not set the
team back to open-ended searches. To do so implies that the team did not learn much in
t
the scoring process.
3.6 Detailed Design

The detail design phase defines the complete specification of the geometry, materials,
and tolerances of all the parts through the provision of detail drawings, assembly
drawings, and general assembly drawings. It also includes the specification of all the
bought-out parts complete with preferred suppliers and component designations. The
result of this phase is the complete and precise physical description of all the parts in the
product. These drawings can then be issued to the manufacturing function for precise
manufacture and assembly. The detail drawings require an index in order to be
understood and coordinated. Along with the detail drawings, therefore, there should be a
general parts list, which will act as a “map” and precisely instruct the manufacturing
function to group components into assemblies and, further, assemblies into the full
product. Fig. 3.6.1 shows a portion of a typical parts list, which lists all the parts along
with raw material sizes and specifications. It should be noted that this particular parts list
shows elements of three subassemblies. The detail design phase takes the concept design
and applies it to the material components and, in effect, plans the manufacture and
assembly of the product. During this process, the designers consider the selection of
materials, manufacturing techniques, machine tools, and processes such as forging,
ww
injection molding, and casting. Further processes such as chromium plating and painting
are added to the specification. It must be emphasized here that every single component
w
and process required to complete the product and which, therefore, adds cost to the
.Ea
product requires a detailed specification at this stage. The detail design often relates to the
product, but once the product has been defined precisely in terms of technical drawings,
syE
other manufacturing elements may be pursued such as specialist machine tools, jigs, and
other specialist manufacturing equipment.
ngi
nee
rin
g .ne
t
Fig. 3.6.1 Detail design process
3.7 Component Design and Verification

DESIGN VALIDATION is the process of evaluating the software during or at the end
of the product development, to ensure the manufactured system satisfies the specification
in end-user application or product and environment.
Validation is concerned with demonstrating the consistency and completeness of

design with respect to the user needs. This is the stage where you actually build a version
of the product and validate against the user requirements. The image below represents
design validation process.
ww
The purpose is to prove with objective evidence that the product satisfies the
w
documents of user needs. The objective evidence is nothing but any physical proof of the
.Ea
output such as an image, text or audio file which indicates that the procedure has been
accomplished.
syE
ngi
nee
rin
g .ne
t
Through objective evidence, this process will consistently examine that the product
meets the predefined requirements. This process involves testing activity, inspection and
analysis, and so on.
3.7.1 What is Design Verification ?

DESIGN VERIFICATION is a method of confirmation by examining and providing
evidence that the design output meets the design input specifications. An essential
process during any product development that ensures the designed product is the same
as the intended use.

Design input is any physical and performance requirement that is used as the basis for
designing purpose. Design output is the result of each design phase and at the end of
total design effort. The final design output is a basis for device master record.
Difference between Design Verification and Validation
There are always misconceptions between verification and validation. These are
different activities which are performed at every stage of development process.
Design Verification Design Validation
Design verification is used where the actual Design Validation is used to define that the
ww
design output should be same as expected
design output which satisfies the
final design is as per the expectations of the
user need.
w
specifications of the product.
.Ea
Design Verification ask: Did you design the Design Validation ask: Did you design the
product right?
syE right product?
ngi
Design verification includes unit and Design validation includes secondary or
primary integration level testing. higher-level integration and system level
testing.
Certain aspects of design validation can be nee

Design validation follows successful design
accomplished during the design
verification, but design verification is not a
verification.
rin
substitute for design validation.
g .ne
Design verification can be conducted on
the individual module or on the completed
system under any conditions.
a specified condition as per the user
requirement.
t
Design validation shall be conducted under
Design verification may use Static Design Validation consists of the final
techniques. It includes system inspections, report (test execution results) that are
analysis, and formal verification (testing) reviewed, approved, and signed. These
activities. documents are stored for future references.
3.7.2 Design Verification Process

Identification and preparation :
 During the development stage of a specification, the identification of verification
activity is done parallel. This enables the designer to make sure that the
specification is verifiable. So a test engineer can start detailed test plan and
procedures. Any changes in the specification should be communicated.
Foundation Skills in Integrated Product Development 3 - 10 Design and Testing
 Identifying the best approach to conduct verification, define measurement methods,

required resources, tools, and facilities.
 The completed verification plan will be reviewed with the design team to identify
issues before finalizing the plan.
Planning :
 Planning for verification is a concurrent activity with core and development teams.
This occurs throughout the project life cycle. This will be updated as and when any
changes are made to design inputs.
 During this phase, the software or system under test shall be documented in scope.
ww
 Preliminary test plan and test plan refinement are made at this stage. Test plan
w
captures the critical milestone reducing the project risk.
 Tools, test environment, development strategy and identifying the requirements
.Ea
through inspection or analysis.
Developing : syE
 The test case development will coincide with SDLC methodology implemented by a
ngi
project team. A variety of test methods are identified during this stage.
nee
 The design inputs must be developed including simplest verification activities
which are unambiguous and verifiable.
rin
 Verification time shall be reduced when similar concepts are conducted in sequence.
Even the output of one test can be used as input for subsequent tests.
g .ne
 Tractability links are created between test cases and corresponding design inputs, to
ensure that all the requirements are tested and the design output meets the design
inputs. t
Execution :
 The test procedures created during the development phase is executed in
accordance with the test plan, strictly following them in verification activity.
 If any invalid results occur or if any procedures required modification, it is
important to document the changes and get proper approval.
 Any issues are identified and logged as a defect at this stage.
 Tractability matrix is created to verify that all the design input identified in the
verification test plan has been tested and determine the pass ratio.

Reports :
 This activity is performed at the end of each phase of verification execution.
 The design verification report gives the detailed summary of verification results
which includes the configuration management, test results for each type of testing
and issues found during the verification activity.
 Design verification traceability report is created between requirements and
corresponding test results to verify all the requirements have been tested and
provided with appropriate results.
 Any non-conformance will be documented and appropriately addressed.
ww
 Reviews are done upon the completion of design verification activity and are
approved respectively.
w
Design Validation Process
.Ea
 Some of the designs may be validated by comparing with similar equipment
syE
performing similar purpose. This method is particularly relevant for validating
configuration changes for existing infrastructure, or standard designs that are to be
incorporated in a new system or application. ngi
nee
 Demonstration and/or inspection may be used to validate requirements and other
functionality of the product.
rin
 Analyzing the design can be done such as mathematical modeling, a simulation
which can recreate the required functionality.
g
 Tests are performed on the final design that validates the ability of the system to
.ne
operate as per the specified design.
 Test plan, execution, and results should be documented and maintained as a part of
design records. Thus, Validation is a collection of the results of all validation
t
activities.
 When equivalent products are used in the final design validation, the manufacturer
must document the similarity and if any difference from initial production.
Example
 Let us take an example of the simple product, a waterproof watch.
 The product requirement document might state that "the watch must be waterproof
during swimming."
 The design specification might state "the watch should function even if the user
swims for a prolonged time."

 The testing results should confirm that the watch should meet these requirements
else the redesign iterations are done until it satisfies the requirement.
3.7.3 Advantages of Design Validation and Verification

 We can continuously monitor the designs which enable us to meet the user-defined
requirements at every stage.
 Validating the design will point out the difference between how the functionality
works and how it is expected to work.
 Documenting the validation procedures will help to easily understand the
wwfunctionality at any stage in the future if there might be any change or enhancement
made.
w
 Development time will be consistently reduced improving productivity, which
.Ea
enables to deliver the product as expected.
 This process includes range and scope of each validation methods that are required
to be employed.
syE
 The validation can be carried out using detailed design data that represent the final
user requirements.
ngi
 Any difference between the outcome and the user need documents must be
captured. nee
 Changes in validation design lead to revalidation activity.
rin
 It is important to document every activity that occurs during validation, which
adequately proves that the design meets the user requirements. g .ne
3.8 Mechanical, Electronics and Software Subsystems
The mechanical assembly concept used in CubETH was developed by eSpace
t
partner ELSE SA. The structure allows a flexible and reliable assembly of different
subsystems of the satellites in a versatile configuration.
CubETH is now at the end of its phase B development, which means that the satellite
Electrical Model shall validate the majority of embedded functionalities. During the past
semesters, the electrical subsystems were independently implemented by the students,
based mainly on the SwissCube heritage.Most recently, master student Adrien Corne
could combine all subsystems together and validate inter-board communication
capabilities. As seen in the diagram below, the Electronic Model architecture embeds
most of the subsystems.

3.9 High Level Design / Low Level Design of S/W Program

High-level design (HLD) explains the architecture that would be used for developing a
software product. The architecture diagram provides an overview of an entire system,
identifying the main components that would be developed for the product and their
interfaces. The HLD uses possibly nontechnical to mildly technical terms that should be
understandable to the administrators of the system. In contrast, low-level design further
exposes the logical detailed design of each of these elements for programmers.
Purpose
ww
Preliminary design—In the preliminary stages of a software development, the need is
to size the project and to identify those parts of the project that might be risky or time
w
consuming. Design overview—As the project proceeds, the need is to provide an
.Ea
overview of how the various sub-systems and components of the system fit together. In
both cases the high-level design should be a complete view of the entire system, breaking
syE
it down into smaller parts that are more easily understood. To minimize the maintenance
overhead as construction proceeds and the lower-level design is done, it is best that the
ngi
high-level design is elaborated only to the degree needed to satisfy these needs.
High-level design document high-level design document or HLDD adds the necessary
nee
details to the current project description to represent a suitable model for coding. This
rin
document includes a high-level architecture diagram depicting the structure of the
system, such as the database architecture, application architecture (layers), application
flow (navigation), security architecture and technology architecture.
Design overview a high-level design provides an overview of a system, product,
g .ne
service or process.
Such an overview helps supporting components be compatible to others.
t
The highest-level design should briefly describe all platforms, systems, products,
services and processes that it depends on and include any important changes that need to
be made to them.
In addition, there should be brief consideration of all significant commercial, legal,
environmental, security, safety and technical risks, issues and assumptions.
The idea is to mention every work area briefly, clearly delegating the ownership of
more detailed design activity whilst also encouraging effective collaboration between the
various project teams.
Today, most high-level designs require contributions from a number of experts,
representing many distinct professional disciplines.
Finally, every type of end-user should be identified in the high-level design and each
contributing design should give due consideration to customer experience.
Low-level design (LLD) is a component-level design process that follows a
step-by-step refinement process. This process can be used for designing data structures,
required software architecture, source code and ultimately, performance algorithms.
Overall, the data organization may be defined during requirement analysis and then
refined during data design work. Post-build, each component is specified in detail.[1]
3.9.1 Low Level Design of S/W Program
ww
The LLD phase is the stage where the actual software components are designed.
During the detailed phase the logical and functional design is done and the design of
w
application structure is developed during the high-level design phase.
Design phase .Ea

syE
A design is the order of a system that connects individual components. Often, it can
interact with other systems. Design is important to achieve high reliability, low cost, and
ngi
good maintain-ability. We can distinguish two types of program design phases :
Architectural or high-level design
 Detailed or low-level design nee

rin
Structured flow charts and HIPO diagrams typify the class of software design tools
g
and these provide a high-level overview of a program. The advantages of such a design
.ne
tool is that it yields a design specification that is understandable to nonprogrammers and
it provides a good pictorial display of the module dependencies.
A disadvantage is that it may be difficult for software developers to go from graphic-
oriented representation of software design to implementation. Therefore, it is necessary to
t
provide little insight into the algorithmic structure describing procedural steps to
facilitate the early stages of software development (generally using PDLs).[3]
Purpose
The goal of LLD or a low-level design document (LLDD) is to give the internal logical
design of the actual program code. Low-level design is created based on the high-level
design. LLD describes the class diagrams with the methods and relations between classes
and program specs. It describes the modules so that the programmer can directly code the
program from the document.
A good low-level design document makes the program easy to develop when proper
analysis is utilized to create a low-level design document. The code can then be
developed directly from the low-level design document with minimal debugging and
testing. Other advantages include lower cost and easier maintenance.
We frequently come across different types of prototypes and their applications but do
not clearly understand the real purpose or necessity of the application of the prototype.
We get questions like how good should the prototype be? Does it need to work properly?
A prototype is a basic working model, mock-up or a simple simulation of the product
which leads us to create a minimal viable product to final product and variations. The
main reason for prototyping is to validate the idea and this is the step in converting an
idea to a real product. A prototype could be a working model, representational (non-
ww
working) model, miniature or a scale model, video or a photo demonstration based on the
factors like a problem to be solved, the mandate of the end customer, investor/industry
w
requirements or prototype that best satisfies the purpose. Ideally, the first type should be
.Ea
a working model which is actually functional, so people can get their hands on it and try
it out. Also, it good to get the wrinkles ironed out before presenting the prototype to
syE
industry —as not very often a second meeting is given in case prototype fizzles at a
meeting. But sometimes it isn’t possible to have a working model, in such cases another
ngi
kind of prototypes is used which best suits the situation.
nee
A prototype can be in the following forms paper, 3D printing, digital, small model or
limited usage product. These prototypes can fall into one of the following area functional,
rin
display or a small model. The functional prototype focus on the functions and not on the
g
looks. The display prototype focuses on the looks and not so much on the function. The
small model combines both and is a smaller version of the final product. They type of
prototype to develop must be decided based on the intended purpose of the prototype, .ne
the medium of use and the expected longevity of the prototype.
Prototypes can be throwable or non-throwable types. Both have their own benefits a
t
throwable type is done just to get an idea of a product, a non-throwable is one which
improvements can be made to arrive at the final product.
There are many types of the prototype here is ten of those types: -
1. A film (movie) prototype : Here a prototype is made using video just to show
others the idea in a graphical/visual format.
2. Feasibility Prototype : This type of prototype is usually developed to determine
the feasibility of various solutions. It is applied to the resolve technical risks
attached to the development in terms of performance, compatibility of
components etc.

3. Horizontal Prototype : This is the user interface in the form of screenshots,

demonstrating the outer layer of the human interface only, such as windows,
menus, and screens. The prototype is used to clarify the scope and requirements
of the product.
4. Rapid Prototype : The rapid prototyping technique is used to quickly engineer
an initial model of a product using a three-dimensional computer-aided design
when you want to produce something in a short span.
5. Simulations : Simulation prototype is digitally creating of a physical product to
predict the performance of the product in the real world.
ww
6. Storyboard : A storyboard describes a product in a form of a story and
demonstrates a typical order in which information needs to be presented. It helps
7.
w in determining useable sequences for presenting information
.Ea
Vertical Prototype : A vertical prototype is the back end of a product like a
syE
database generation to test front end. It used to improve database design, test
key components at early stages or showcase a working model, though
8.
unfinished, to check the key functions.
ngi
Wireframe : This is a skeleton a product. Depicted in the form of illustrations or
nee
schematics that capture an aspect of design such as an idea, layout, form,
architecture or sequence.
9. rin
Animations : These are images drawn and put in a sequence that walks you
through the proposed 3D structure of the product/solution.
g .ne
10. Mock-up : This is with no functionalities, just to get overall visual of the product.
It is an unpolished version of the product with no active features.
3.10 Software Testing

t
Software testing is a process, to evaluate the functionality of a software application
with an intent to find whether the developed software met the specified requirements or
not and to identify the defects to ensure that the product is defect-free in order to produce
the quality product.
3.10.1 Definition of Software Testing

Software Testing Definition according to ANSI/IEEE 1059 standard – A process of
analyzing a software item to detect the differences between existing and required
conditions (i.e., defects) and to evaluate the features of the software item.

3.10.2 Software Testing Types

Manual Testing: Manual testing is the process of testing software by hand to learn
more about it, to find what is and isn’t working. This usually includes verifying all the
features specified in requirements documents, but often also includes the testers trying
the software with the perspective of their end user’s in mind. Manual test plans vary from
fully scripted test cases, giving testers detailed steps and expected results, through to
high-level guides that steer exploratory testing sessions. There are lots of sophisticated
tools on the market to help with manual testing, but if you want a simple and flexible
place to start, take a look at Testpad.
ww
Automation Testing: Automation testing is the process of testing the software using
an automation tool to find the defects. In this process, testers execute the test scripts and
w
generate the test results automatically by using automation tools. Some of the famous
.Ea
automation testing tools for functional testing are QTP/UFT and Selenium.
Testing Methods :
1) Static Testing
syE
2) Dynamic Testing
ngi
nee
1) Static Testing : It is also known as Verification in Software Testing. Verification is a
static method of checking documents and files. Verification is the process, to ensure that
rin
whether we are building the product right i.e., to verify the requirements which we have
and to verify whether we are developing the product accordingly or not.
Activities involved here are Inspections, Reviews, Walkthroughs g .ne
2) Dynamic Testing : It is also known as Validation in Software Testing. Validation is a
dynamic process of testing the real product. Validation is the process, whether we are
building the right product i.e., to validate the product which we have developed is right
t
or not.
3.11 Hardware Schematic

A schematic, or schematic diagram, is a representation of the elements of
a system using abstract, graphic symbols rather than realistic pictures. A schematic
usually omits all details that are not relevant to the key information the schematic is
intended to convey, and may include oversimplified elements in order to make this
essential meaning easier to grasp.

For example, a subway map intended for passengers may represent a subway station
with a dot. The dot is not intended to resemble the actual station at all but aims to give
the viewer information without unnecessary visual clutter.
A schematic diagram of a chemical process uses symbols in place of detailed
representations of the vessels, piping, valves, pumps, and other equipment that compose
the system, thus emphasizing the functions of the individual elements and the
interconnections among them and suppresses their particular physical details. In an
electronic circuit diagram, the layout of the symbols may not look anything like the circuit
as it appears in the physical world: instead of representing the way the circuit looks, the
ww
schematic aims to capture, on a more general level, the way it works.
The Component Design Activity is an activity of the product design activity for
w
creating a component design. The Product Architecture identifies a set of Adaptable
.Ea
Components that may be used to implement a work product family. A Component
Design is a design specification for one of these Adaptable Components. Application
syE
engineers, using the Generation Procedure, may adapt and compose a set of these
components to implement certain work products, or portions thereof. Each component
ngi
must be designed to satisfy relevant aspects of the Product Requirements and all design
structures of the Product Architecture.
nee
Objectives
The objective of the Component Design Activity is to produce a design for anrin
g
Adaptable Component that satisfies applicable Product Requirements in accordance with
its role in the Product Architecture. .ne
Required Information
The Component Design Activity requires the following information:
t
 Product Requirements
 Product Architecture
 Legacy Products
Required Knowledge and Experience

The Component Design Activity requires domain and software knowledge and
experience in:
 How components of systems in the domain are designed
 The principles and use of an appropriate design method
 The concepts and practice of abstraction-based reuse (Parnas 1976; Campbell 1989)
PRODUCT DESCRIPTION
Name :
Component Design
Purpose :
A Component Design is a specification for an Adaptable Component that can
be used to construct a draft application work product.
Content :
Each Component Design represents a family of components. A Component
ww Design consists of two parts:

 Adaptation Specification. The Adaptation Specification for an Adaptable
w Component describes the ways that the component can be tailored via a
.Ea
set of parameters. Each parameter has a name and type to indicate its
range of variations. Constraints identify invalid combinations of parameter
syE
variations.
 Interface Specification. The Interface Specification describes the desired
ngi
characteristics of the implementation of the component. The exact content
nee
of the interface specification is particular to the component type and the
design method used. To describe the entire family, the interface
rin
specification is parameterized with respect to the variations in the
Adaptation Specification.
Form and Structure :
g
The Adaptation and Interface Specifications each include textual and tabular .ne
information. The form of an Adaptation Specification is the same for all types of
components and includes the following information :
t
 Name. Name of the Adaptable Component.
 Instantiation Parameters. Adaptation parameters for the component,
including the name, type, and description of each parameter.
 Instantiation Constraints. Constraints on the instantiation of the Adaptable
Component (e.g., constraints on the legal combination of parameter values).
The interface part of Adaptable Components is different for software and
documentation. The content of the software interface is specific to the design method(s)
used to create the members of the family. The following types of information are
examples: definitions of interface programs (names, parameters, parameter types,
returned values), definitions of exported types, descriptions of the effects of interface
programs, assumptions about the environment in which the software is to be used.
The interface for a documentation component does not require the same type of
detailed information. It consists of a brief statement of the content of the component. It
should provide enough information to determine the importance of selecting this
component as part of a Generation Procedure.
Software and hardware engineers alike have heard some form of this advice: “Build
lots of prototypes; iterate as fast as you can.”
For those of us in the Hardware Industry, these prototypes can cost a lot of time and
money. So while we should strive to iterate quickly, we must also get as much
information as possible out of each round of prototypes to inform improvements in the
ww
next iteration.
This is the purpose of hardware testing.
w
If you’re an Industrial or UX Designer, you might be most familiar with user testing. If
.Ea
you’re a Mechanical Engineer, you might picture things being smashed to bits (and it’s
syE
oddly satisfying). Electrical and Firmware Engineers might think of a bed-of-nails fixture.
All of the above are part of a comprehensive test plan for hardware products—
ngi
different tests are beneficial at different stages and each test is an indispensable part of the
hardware development process.
nee
In this introductory article, I’m going to give an overview of the different types of tests
rin
to consider at each major stage of hardware product development and share some best
practices for building a testing schedule to help you get started.
Early Stage Testing g

With even the crudest prototypes, you can do a lot of useful tests. There are 3 major .ne
test types you’ll want to build into your schedule during early stage development:
1. Usability tests to help refine the industrial design of the product

t
2. Material and finish tests to assess different options for durability
3. Critical components tests to analyze different mechanisms in isolation before a

complete looks-like, works-like prototype is ready.
Here’s an example of what some early stage tests might look like for a mobile phone
product for kids :

Example : Mobile Phone for Kids – Early Stage Tests
Test Type Example Test
Usability Test Give look-like model to kids, see if the

form is easy to hold for little hands
Material and finish test Scratch test, UV test with material
samples
Critical component test Mount the speaker in a rough housing

prototype, drop it repeatedly, does it still
ww work ?
w
These tests will give you the feedback you need to iterate on your designs and
.Ea
ultimately build a working prototype.
Pre-Production Testing
syE
As your prototypes become closer to the real thing, your tests need to evolve as well.
ngi
Pre-production builds (EVT, DVT, PVT) give you prototypes that are much closer to the
final product vision.
nee
With these high fidelity prototypes, you can finally do system-level stress tests,
rin
environmental tests, and life tests. Compliance certification tests (e.g. FCC, CE) can be
done at this stage as well.
Here’s an example of some of the proto-build stage tests you might do:
1. Thermal shock / thermal cycling
g .ne
2.
3.
High temperature, high humidity operation
UV exposure
t
4. Salt spray
5. Household chemical reaction
6. Water spray for IPX4 certification
7. Water immersion for IPX7 certification
8. Dust ingress
9. Electrostatic Discharge (ESD), contact and air
10. RF emissions
11. 6-Face Drop
12. Tumble
13. Vibration
14. Abrasion
15. Switch cycling
To develop these tests, you’ll want to work in partnership with your contract
manufacturer.
3.12 Prototyping
Prototyping is an experimental process where design teams implement ideas into
tangible forms from paper to digital. Teams build prototypes of varying degrees of
ww
fidelity to capture design concepts and test on users. With prototypes, you can refine and
validate your designs so your brand can release the right products.
w
“They slow us down to speed us up. By taking the time to prototype our ideas, we avoid costly
.Ea
mistakes such as becoming too complex too early and sticking with a weak idea for too long.”
1. syE
The advantages of prototyping are that you:
Have a solid foundation from which to ideate towards improvements—giving all
ngi
stakeholders a clear picture of the potential benefits, risks and costs associated
with where a prototype might lead.
2.
nee
Can adapt changes early—thereby avoiding commitment to a single, falsely-ideal
rin
version, getting stuck on local maxima of UX and later incurring heavy costs due
to oversights.
3.
g
Show the prototype to your users so they can give you their feedback to help
pinpoint which elements/variants work best and whether an overhaul is .ne
4.
required.
Have a tool to experiment with associated parts of the users’ needs and
problems—therefore, you can get insights into less-obvious areas of the users’
t
world (e.g., you notice them using it for additional purposes or spot
unforeseen accessibility issues such as challenges to mobile use).
5. Provide a sense of ownership to all concerned stakeholders—therefore fostering
emotional investment in the product’s ultimate success.
6. Improve time-to-market by minimizing the number of errors to correct before
product release.
7. Rapid prototyping is a group of techniques used to quickly fabricate a scale
model of a physical part or assembly using three-dimensional Computer Aided
Design (CAD) data. Construction of the part or assembly is usually done
using 3D printing or "additive layer manufacturing" technology.
8. The first methods for rapid prototyping became available in the late 1980s and
were used to produce models and prototype parts. Today, they are used for a
wide range of applications, and are used to manufacture production-quality
parts in relatively small numbers if desired without the typical unfavorable
short-run economics. This economy has encouraged online service bureaus.
Historical surveys of RP technology start with discussions
of simulacra production techniques used by 19th-century sculptors. Some
modern sculptors use the progeny technology to produce exhibitions and
various objects. The ability to reproduce designs from a dataset has given rise to
ww issues of rights, as it is now possible to interpolate volumetric data from one-

dimensional images.
9.
w As with CNC subtractive methods, the computer-aided-design – computer-aided
.Ea
manufacturing CAD -CAM workflow in the traditional rapid prototyping
process starts with the creation of geometric data, either as a 3D solid using a
syE
CAD workstation, or 2D slices using a scanning device. For rapid prototyping
this data must represent a valid geometric model; namely, one whose boundary
ngi
surfaces enclose a finite volume, contain no holes exposing the interior, and do
nee
not fold back on themselves. In other words, the object must have an "inside".
The model is valid if for each point in 3D space the computer can determine
rin
uniquely whether that point lies inside, on, or outside the boundary surface of
the model. CAD post-processors will approximate the application vendors'
g
internal CAD geometric forms (e.g., B-splines) with a simplified mathematical
form, which in turn is expressed in a specified data format which is a common .ne
feature in additive manufacturing: STL file format, a de facto standard for
transferring solid geometric models to SFF machines.
t
To obtain the necessary motion control trajectories to drive the actual SFF, rapid
prototyping, 3D printing or additive manufacturing mechanism, the prepared geometric
model is typically sliced into layers, and the slices are scanned into lines (producing a "2D
drawing" used to generate trajectory as in CNC's toolpath), mimicking in reverse the
layer-to-layer physical building process
3.13 System Integration Testing

System Integration Testing is defined as a type of software testing carried out in an
integrated hardware and software environment to verify the behavior of the complete
system. It is testing conducted on a complete, integrated system to evaluate the system's
compliance with its specified requirement. System Integration Testing (SIT) is performed
to verify the interactions between the modules of a software system. It deals with the
verification of the high and low-level software requirements specified in the Software
Requirements Specification/Data and the Software Design Document.
It also verifies a software system's coexistence with others and tests the interface
between modules of the software application. In this type of testing, modules are first
tested individually and then combined to make a system.
For Example, software and/or hardware components are combined and tested
progressively until the entire system has been integrated.
ww
w .Ea
syE
3.14 Certification and Documentation
ngi
nee
The following is a guide to help you prepare your certified documents correctly.
Certified documents are copies of important documents which need to be certified as true
copies of the originals by a person authorized to do so.
rin
g
At certain stages of the application process, for approval as a higher education
provider and VET provider, you will be asked to produce ‘certified documents”. These
are copies of important documents which need to be certified as true copies of the .ne
originals by a person authorized to do so.
The following is a guide to help you prepare your certified documents correctly.
t
A certified copy is a copy (often a photocopy) of a primary document that has on it an
endorsement or certificate that it is a true copy of the primary document. It does not
certify that the primary document is genuine, only that it is a true copy of the primary
document.
Who can certify a copy?

It is usual for documents to be certified by a person who is authorised as a witness for
statutory declarations under Statutory Declarations Regulations 1993– Schedule 2. This
schedule provides a wide range of authorised occupations and office holders who may
certify a document, so finding a suitable person should not normally present a significant
difficulty.
Documents in languages other than English

A certifier should not certify a document in a language other than English unless they
can be sure that the original and the copy are identical. A solution to this is to have the
original photocopied in the presence of the certifier.
Two Marks Questions with Answers
Part - A
Q.1 What is Design Verification ?

Ans. : DESIGN VERIFICATION is a method of confirmation by examining and
ww
providing evidence that the design output meets the design input specifications
Q.2
Ans. w
What are the Keywords of Conceptualization ?
:
Prototyping. .Ea
Keywords are: Context, Empathy, Empowerment, Participation, and
Q.3
syE
Define Software Testing.
Ans. : Software testing is a process, to evaluate the functionality of a software
ngi
application with an intent to find whether the developed software met the specified
nee
requirements or not and to identify the defects to ensure that the product is defect-free
in order to produce the quality product.
Q.4

Write the Advantages of Design Validation and Verification
rin

We can continuously monitor the designs which enable us to meet the user-
defined requirements at every stage. g
Validating the design will point out the difference between how the functionality.ne

works and how it is expected to work.
Documenting the validation procedures will help to easily understand the
t
functionality at any stage in the future if there might be any change or
enhancement made.
 Development time will be consistently reduced improving productivity, which
enables to deliver the product as expected.
 This process includes range and scope of each validation methods that are
required to be employed.
Q.5 Define Prototyping.
Ans. : Prototyping is an experimental process where design teams implement ideas into
tangible forms from paper to digital. Teams build prototypes of varying degrees of
fidelity to capture design concepts and test on users. With prototypes, you can refine
and validate your designs so your brand can release the right products.
Q.6 What are the two Testing Methods in verification?

Ans. : 1) Static Testing 2) Dynamic Testing
Static Testing: It is also known as Verification in Software Testing. Verification is a
static method of checking documents and files. Verification is the process, to ensure
that whether we are building the product right i.e., to verify the requirements which we
have and to verify whether we are developing the product accordingly or not.
Activities involved here are Inspections, Reviews, Walkthroughs
Dynamic Testing: It is also known as Validation in Software Testing. Validation is a
dynamic process of testing the real product. Validation is the process, whether we are
ww
building the right product i.e., to validate the product which we have developed is
right or not.
Q.7
Ans. :
w .Ea
Differentiate Design Verification and Design Validation.
syE
Design Verification Design Validation
Design verification is used where the actual ngi

Design Validation is used to define that the
design output should be same as expected
design output which satisfies the nee
final design is as per the expectations of the
user need.
specifications of the product.
rin
Design Verification ask: Did you design the
product right?
g .ne
Design Validation ask: Did you design the
right product?
Design verification includes unit and Design validation includes secondary or

t
primary integration level testing. higher-level integration and system level
testing.
Q.8 Define System Integration Testing.

Ans. : System Integration Testing is defined as a type of software testing carried out in
an integrated hardware and software environment to verify the behavior of the
complete system. It is testing conducted on a complete, integrated system to evaluate
the system's compliance with its specified requirement.

Q.9 Define Design Validation

Ans. : It is the process of evaluating the software during or at the end of the product
development, to ensure the manufactured system satisfies the specification in end-user
application or product and environment.
Q.10 Define High-level design (HLD)
Ans. : High-level design (HLD) explains the architecture that would be used
for developing a software product. The architecture diagram provides an overview of
an entire system, identifying the main components that would be developed for the
product and their interfaces.
ww
Review Questions
Q.1
w .Ea
Part - B
Define prototyping and explain its types in detail.
Q.2
Q.3
syE
Compare High Level Design / Low Level Design of S/W Program.
Discuss briefly about User interface design.
Q.4
ngi
Write about concept screening and evaluation in detail.
Q.5
nee
What are the different concept generation techniques ? Explain in detail.
rin 
g .ne
t

Notes
ww
w .Ea
syE
ngi
nee
rin
g .ne
t


Design and Testing: Syllabus

Uploaded by

Copyright:

Available Formats

Design and Testing: Syllabus

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Design and Testing: Syllabus

Uploaded by

Copyright:

Available Formats

Downloaded From: www.EasyEngineering.

3 Design and Testing

Downloaded From: www.EasyEngineering.net

3.2 Industrial Design and User Interface Design

3.3 Introduction to Concept Generation Techniques

3.3.1 Concept Generation Strategies

3.4 Challenges in Integration of Engineering Disciplines

multi-disciplinary and project-based workplaces. Several committees have been formed

3.5.1 Concept Screening

3.5.2 Concept Scoring

to combine design concepts. g

3.6 Detailed Design

Fig. 3.6.1 Detail design process

3.7 Component Design and Verification

Validation is concerned with demonstrating the consistency and completeness of

3.7.1 What is Design Verification ?

Downloaded From: www.EasyEngineering.net

Design Verification Design Validation

Certain aspects of design validation can be nee

3.7.2 Design Verification Process

 Identifying the best approach to conduct verification, define measurement methods,

Downloaded From: www.EasyEngineering.net

Downloaded From: www.EasyEngineering.net

3.7.3 Advantages of Design Validation and Verification

Downloaded From: www.EasyEngineering.net

3.9 High Level Design / Low Level Design of S/W Program

3.9.1 Low Level Design of S/W Program

Design phase .Ea

 Detailed or low-level design nee

Downloaded From: www.EasyEngineering.net

3. Horizontal Prototype : This is the user interface in the form of screenshots,

3.10 Software Testing

3.10.1 Definition of Software Testing

Downloaded From: www.EasyEngineering.net

3.10.2 Software Testing Types

3.11 Hardware Schematic

Downloaded From: www.EasyEngineering.net

Required Knowledge and Experience

ww Design consists of two parts:

Early Stage Testing g

1. Usability tests to help refine the industrial design of the product

3. Critical components tests to analyze different mechanisms in isolation before a

Downloaded From: www.EasyEngineering.net

Example : Mobile Phone for Kids – Early Stage Tests

Test Type Example Test

Usability Test Give look-like model to kids, see if the

Critical component test Mount the speaker in a rough housing

ww issues of rights, as it is now possible to interpolate volumetric data from one-

3.13 System Integration Testing

Who can certify a copy?

Documents in languages other than English

Two Marks Questions with Answers

Q.1 What is Design Verification ?

Q.6 What are the two Testing Methods in verification?

Design verification is used where the actual ngi

Design verification includes unit and Design validation includes secondary or

Q.8 Define System Integration Testing.

Downloaded From: www.EasyEngineering.net

Q.9 Define Design Validation