Chapter 1 The Engineering Design

Process

HQJUµQHH(rt) 1. 2P¶ versed in the design, mrrstmctimz, /md use of machirws. 2. One who
cmplnys the imzovatirre and mrflzudical a'ppliC11tilm WIVFLPWO¿F knowledge and techrttrloguto
produce a device, 6@6OO¶O¶OO
472' process, which is Intended to satisfy human needs. ²$PHULFDQ

College Dictionary

Take a moment to read and analyze the key elements of the two GH¿QLWLRQV presented above.
if you are an
engineering strident or
practicing engineer, do you think that this GH¿QLWLRQ ap
plies to you? The first GH¿QLWLRQ use. he terms design and mristructiun. People like to think of
themselves as designers. Why is that '

. The answer
may be in the combination of the term
cortstructimz, and from the second definition, the idea of innervation. Applying innovation and

creativity to produce something new is a wonderfully rewarding process. The great thing
about being an engineer is that it allows you to be a creative designer. That is generally not the
way the profession is viewed. What is the difference between engineering design and other
types of design that are associated with creativity such as interior design, fashion design, or
webpage design? The answer is supplied in the second definition which states ´ .methodical .

application of scientific knowledge and technology. ´ As an engineering student, you have .

studied a great deal of math, science, and fundamental technology, but probably have had
limited exposure to creative and [Link] design.
lhe definition also contains me somewhat contradictory temis irzrzuvlmve and metlmdical. If
there is an established and methodical way of employing a scientific principle or process, it
does not seem to allow much room for creativity and innovation. The truth is that the two con-

cepts are in competition with each [Link], but a good engineer realizes this and utilizes both

effemvely. The definition also indicates that engineers design to satisfy human needs, an im-
portant, yet otten overlooked point. That means that when designing systems, it is necessary
to determine d1e users needs and the ethical application of the technology.
This book aims to help electrical and computer engineers become effective designers, to
better understand professional practices, and to provide guidance for executing design pro-
jecbz. This chapter presents the processes by which designs are realized, the characteristics of
successful engineers, and an overview of the book.
4 Design for Electrical and Computer Engineers

Learning Objectives
By the end of this chapter, the reader should:

0 Understand what is meant by engineering desigm.

0 Understand the phases of the engineering design process.
0 Be familiar with [Link] attributes of successful engineers.
- Understand the objectives of this book.

1.1 The Engineering Design Process

Board of Engineering and Technology) provides the
ABET (formerly known as Accreditation
following definition of engineering design [ABE03].

Engmeenng design is the process of devising a system, component, or process to meet desired
needs. It is a decision-makingprocess (ofteniterative), in which the basic sciences, mathemat-
zcs, and engineering sciences are applied to convert resources optimally to meet a stateai objec-
tive. Among the fundamentalelements of the design process are the establishment ofobjectives
and criteria, synthesis, analysis, construction, testing, and evaluation.

The GH¿QLWLRQ indicates engineering design, different phases of the process have to be
that, in

revisited and the deliverables for each phase updated as necessary. Realistic problems are
complex with many potential solutions; the goal is not to GQ¿ just any solution but the best
and available This requires the application of sound
one given the constraints resources.

judgment, decision-making skills, and patience in constantly evaluating progress toward a

solution. The definition LGHQWL¿HV some common elements of the design process, such as estab-

lishment of criteria, synthesis, construction, and testing.

of
Design processes embody the steps required to take an idea from concept to realization
the final system, and are SUREOHP²VW!OYLQJ methodologies that aim to develop a system that
best meets the FXVWRPHU¶ s need Within given constraints. This is not all that different from

some everyday processes, such as preparing dinner. Say you are hungry and need to eat din-
hour. The constraints time, money,
before go to see a movie that starts in
ner can one are
you
food, your tastes, and nutritional value if you are health-conscious. You brainstorm and come

buying something to
up with the options of making dinner at home, going to a restaurant, or

eat at the theater. On the basis of these options, you then select the solution based on your
This is si.rni_lar in to the stages of design processes where
evaluation of the best one. philosophy
you have a problem to solve, constraints, potential solutions to select from.
and a number of

A related term is known as the pmaiuct realization process. The product realization proces. s

broader in scope, including aspects such as entrepreneurship, market research, ODLFQDQ¿ plan-
ning, product pricing, and market strategy. Many technologies have their own particular de-
sign processes that have evolved over time and have been found by practitioners in die GOH¿ to
 Chapter1 The Engineering Design Process 5

be valuable. For example, different methodologies are applied in the design of integrated cir-

cuits (VLSI), embedded systems, and software degree of

systems, yet they all have some

commonality, such as requirements analysis, technical design, and system test. Design pro-
cesses continue to evolve. One GOH¿ in which this is particularly true is in software design be
cause of the constantly changing nature of software and the special challenges that large VRIW²
ware
projects pose.
Cross [Cro00] LGHQWL¿HG two types of design SURFHVVHV²SUHVFULSWLYH and descriptive. As
the name implies, prescriptive design processes set down an exact process, or systematic rec-
ipe, for realizing a system. Prescriptive design processes are often algorithmic i.n nature and

expressed on flow charts with decision logic. An example of a prescriptive process is shown in
Figure 1.], which describes the front end of the design process where the problem and re-
A decision block is included where the requirements are exam-
quirements are deten-nined.
ined to determine if they satisfy the needs of the problem. Descriptive processes are less

formal, describing typical activities involved in realizing designs with less emphasis on exact

sequencing. The distinction between descriptive and prescriptive processes is not always clear,
however, and some may be considered more
strongly assodated with one property
processes
than the other. Cross makes an
important point in stating that design processes are sometimes
viewed as common sense and thus ignored, resulting in failed products. Cross cites two good
reasons to adhere to design processes: (1) they formalize thought processes to ensure good
practices are followed, leading to better and more innovative solutions, and (2) they keep all
members of the team synchroniwed in terms of understanding where they are in the design
process.
A

/
.

/ \\
µ
Yes
LGHQW,I\O¶UREOHP
4!: Needs
µ
Determine

5³µ³³¼µƒ³
:
/Requsfmcm
\ / Needs?
\

Satisfy
T
\ /
\_ /
\
N0

Figure 1.1 A prescriptive design prooess for problem LGHQWL¿FDWLRQ and requirements selection.

A that is widely applicable design problems is shown in Figure

to 1.2.
descriptive process
In a perfect world, the process starts with the LG(O
_L¿&LµL2À of the problem, proceeds clod
to research, followed the requirements phase, and so on until the system or device is delivered
and goes into service (maintenance phase). This scenario is unrealistic, ignoring the iterative
nature of
design where the design team alternates between different phases as necessary.
Consequently, links are inserted that allow transitions between all the different phases of the
6 Design for Electrical and Computer Engineers

Problem
Idem tihca lion ,3

'/ 'ƒ³µ
ƒ¶ªµ

µ ³0 µ
/Requinements
Spedficatiun
#


Acceptance /

Concept
Gen era tion

System
Integration
µ

/ Prototype
i and J
Construct
\_ /

Figure 1.2 A descriptive overview of the design process.

design process. Of course, transitions between certain phases are unreasonable or

very costly.
it is virtually impossible to move directly from problem identification to system integration

without developing a design concept first. It is much more likely for engineers to alternate
between nearby phases in the process, such as problem LGHQWL¿FDWLRQ reseamh, requirements
specification, and concept generation. This does not mean that you FDQ¶W move between phases
that are not i_n close proximity in the model. For instance, the &XVWRPHU¶ s needs may change
while in the design phase, necessitating reevaluation of the needs, correction of the require-

ments specification, and system redesign ²DOO at a substantial cost in time and money. Studies

have shown that the cost required to corred errors or make changes increases exponentially as
the project lifetime increases, as presented in Figure 1.3.
 Chapter1 The Engineering Design Process 7

Cost to
A
implement
changes

Proiect lifetime

Figure 1.3 The cost to implement design changes increases exponentially with project liietime.

1.1.1 Elements of the Design Process

Nearly all the phases of the desi;-.;nprocess in Figure 1.2 are covered in this book, with the ex-
ception of the maintenance phase. The objective of the first phase, problem identification, is to
identity [Link] problem and mstomer needs. This occurs in a variety of ways, from someone Con-

ceiving a new idea to a client coming to you with a problem to solve. In either case, it is impor-
tant to determine the true needs for the product, device, or system (terms that are used

interchangeably throughout the book and often referred to as systems). Failure to correctly
identify the needs has negative ramifications for the entire process, [Link] resulting in costly

redesigns, or even worse, abandonment of the project.

In the research phase the design team conducts research on the basic engineering and sei-
entific principles, related technologies, and existing solutions. The objective is to become ex-
perts on the problem, save time and money by not reinventing the wheel, and be positioned to
develop new and innovative solutions.
The requirements specification articulates what the system must do for it to be successful
and to be accepted by the customer. it is important to focus on what the system must do, as
opposed to how the solution will be implemented. This is challenging since engineers tend to
focus on solutions and propose implementations early in the process. This is not surprising
[Link] engineering education fomses on solving problems instead of specifying them. The re-
quirements are the mission statement that guides the entire project, and if properly developed,

provide \WLOLEL[HÀ for creativity and innovation in developing solutions.

l.n concept generation, many possible solutions to the problem are developed. The hall-
mark of design is that it is open-ended, meaning that there are multiple solutions to the prob-

lem and the objective is to develop the one that best meets the requirements and VDWLV¿HV the
constraints. in this phase, wild creativity is encouraged, but it is ultimately tempered with
critical evaluation of the competing altematives.
8 Design [or Electrical and Computer Engineers

In the design phase, the team iteratively develops a technical solution, ultimately produc-
ing a detailed system design. Upon its completion, all major systems and subsystems are iden-
tified and described using an appropriate model that depends upon the particular technology
being employed.
l.n the prafotyping and cunstructiun phase, different elements of the system are FRQ²
structed and tested. In rapid prototyping, the objective is to model some aspect of the system,
demonstrating functionality to be employed in the ODQ¿ realization. Many prototypes are dis-
carded or PRGL¿HG as the system HYROYHV²WKH idea is to experiment, demonstrate proof-of-
and improve understanding. Prototypes may be used anywhere in the
concept principles,
SURFHVV²\RX may present the client with prototypes after the concept generation phase,
or

they may be utilized in the design phase to test a design idea or as the ODQ¿ system is tested
and developed.

During system LQWFJUD¿DQ all of the subsystems are brought together to produce a com-
plete working system. This phase is challenging and time-consuming since many different
pieces of the design must be interfaced, and the team must work closely to make it all work.
Care taken in the design phase to clearly communicam the functionality and interfaces EH²

tween subsystems aids in system integration. System integration is closely tied to the test
phase, where the overall system is tested to demonstrate that it meets the requirements.

Ultimately the system is delivered to the customer where it is lil that it will be tested by
a
mutually agreed upon process. Development does not necessarily end when the system goes
into service, as it will likely enter the maintenance phase where it is maintained, upgraded to
add new functionality, or design problems are correcmd. Following and understanding the
design process improves the probability of successful system development. The process is
flexible, and the designer needs to transition between different phases in order to bring the
system to realization. Design is an iterative SURFHVV²\RX may not fully understand every-
in and have to revisit different the evolves.
thing necessary any given phase steps as
system
That is not a license for not trying to develop the best design you can on the first DWWHPSW²E\
all means do VR²EXW realize that flexibility and a
willingness to Change the design are
necessary.

1.1.2 Technology-Specific Design Processes

Different application domains have developed specialized processes for WHG
PRORJ\²VSHFLILF

design. One such example is VLSI (very large scale integration) design. A typical VLSI design
process is shown in Figure 1.4 [Wol()2]. In this model the system specification is used to de-

velop the system architecture. The s tem architecture is composed of the major functional
units that constitute an
integrated circuit. Each functional unit is then designed at the gate
logic level, which is subsequently designed at the circuit (transistor) level, and finally the
circuit elements are laid out on the silicon chip. This is an excellent demonstration of the

GLYLGH²DQG²FRQTXHU approach to design, where a complex system is broken down into

 Chapter 1 The Engineering Design Process 9

lower levels of abstration and each of these is further broken down until the design
objectives are met.

Next, consider the design process for embedded computer systems shown in Figure 1.5.
Embedded systems are combined hardware/software systems embedded into a larger system

to perform dedicated DSSOLFDWLRQVSHFL¿F operations. Embedded systems are employed in

automobiles, DVD and
digital cameras
players, to name a few applications. Performance is-

sues dominate embedded applications, and me designer needs to partition tasks between
software and hardware to achieve optimum performance. This design process is somewhat
prescriptive, with phases For requirements gathering, VSHFL¿FDWLRQV and architectural design.
The process UHÀHFWV the unique nature of embedded systems with separate software and
hardware design blocks, married together by the interface design.

i
,
l

0µ!Lµ.IµP
I µ
Specification _
, mi /©JLF'HVLQ Lirtullrleslgn Layout

{>
Figure 1.4 A process for integrated circuit (VLS1) design [Wot02].

Requirements
Analysis

Specifications

System
Architecture

Software Design Hardivare Design

³ƒ¶
.

'³
,

-
Application
-
Architecture
6RÀZDUH
,

.
m
-
Drivers .

-
Operahlig System _
³::: Dmm bynthesis
-
Compiler
-

Compiler

Figure 15 An embedded system design process [Ern97).

10 Design for Electrical and Computer Engineers

The field of software is in which the development of different design

engineering one

models is still under considerable

today. flux complex This of
is due to the nature
process
software and the failure of computer scientists and engineers to effectively develop high-

quality software systems. There are many reasons why this is so. The sheer size of software
programs may easily exceed one million lines of code written by many different software de-
velopers. One small mistake in those millions of lines of code can Cause the system to fail, An-
other difficulty is in designing for upgrade and reuse ot software. What if the needs change
after the millions of lines of code are
developed and one of the fundamental structures or ob-

jects needs to be upgraded?

The waterfall madel shown in Figure 1.6 is one of the first proposed and most well-known
software design processes. This is a prescriptive model since the development proceeds line-
arly from the first step where the user's needs are analyzed through the phases of VSHFL¿FDWLRQ
This works for well-defined and moderately
development, design, test, and maintenance.
complex software applications, but fails as complexity grows because of the inability to move
between phases. A more flexible and descriptive software design process is known as the spi-
ral model, which is a cyclical process where phases are revisited as necessary [Som0l]. Extmvw
prognrrrrrrzingis a more recent and controversial software development process, where rela-
of software developers rapidly develop software following some strict
tively small teams
rules. Both the spiral model and extreme programming are examined in more detail in the

end-of-chapter problems.

Rmlummm ts
A n
alysis

L
spmrrcanon
Uevelopment
P .

2/

Software Design _

Test and 7

._
²

vmrrcamn

l
Maintenarice

Figure 1.6 Waterfall software development process. In this model,

development proceeds linearly
from requirements analysis, through each subsequent phase, terminating with maintenance.
 Cnapter1 The Engineering Design Process 11

1.2 The World-Class Engineer

The ability to effectively design is important for engineers, requiring strong technical skills and
an
understanding of the design process. Yet, this ability in itself is not enough to become an
ettective pradicing engineer. The Pennsylvania State University Leonhard Center for the Ad-
\ ancement of Engineering Education, in consultation with a number of industries, developed
a
description of what is referred to as a "World-Class (QJLQHHU´ [Leo95]. Shown in Table 1.1,
the description identifies the characteristics of successful engineers, and contains six major
elements: (1) Aware of the World, (2) Solidly Grounded, (3) Technically Broad, (4) Effective i.n
Group Operations, (5) Versatile, and (6) Customer Oriented. The description recognizes that

engineers must be effective in group operations, since a majority of projects are carried out in
teams. Not only mat, many projects span multiple technical disciplines and are executed in
multifunctional organizations that have diverse groups such as Inarketing, finance, human
resources, technical support, and service. It also recognizes that an engineer must be versatile,
innovative, understand ethical principles, and be Customer oriented, important themes that
are stressed throughout this book.

1.3 Book Overview

Consider d1e digital camera, the cellular phone, and the space shuttle, all complex systems that
integrate a variety of technologies. A digital camera is me synthesis of an embedded electron-
ics system, optics, a mechanical lens assembly, and the camera package itself. The embedded
electronics contain an
imaging sensor, a digital display, digital interface circuitry, flash mem-
ory storage, system control software, and the user interface. The challenges of integrating the

components of such a system and having it record and transfer huge amounts of image data,
within an
acceptable time frame, are immense. Cellular phones are another good example of a
complex system that represents a technology that has shrunk in size, but increased tremen-

dously in functionality at the same time. They encompass digital data communications, an

antenna, encryption for secure data transmission, a user interface display, and lntemet connec-
tivity. At the other end of the spectrum are largescale space and military systems, such as the
space shuttle. Despite the two shuttle accidents, the safety and reliability requirements of the
space shuttle are
incredibly high. Realizing such a system is accomplished by a tremendous
number of people from many disciplines working for different organizations. All three of
these technologies were developed by large teams that encompass multiple disciplines. The
processes and practices employed in their development represent application of the funda-
mentals that this book hopes to cover. While you ZRQ¶ be building complete space shuttles by
the end of this design course, you can expect to apply design principles that allow you to de-
sign and integrate a relatively complex system, maybe even a part of the space shuttle.
12 Design for Electrical and Computer Engineers

Table 1.1 The :RU_Gª&_DVV Engineer. (Copyright the Leonhard Center for the Advancement of

Engineering Education, The Pennsylvania State University. Repnnted by permission.)

I. Aware of the world

- sensitive to cultural dittenmces, environmental concems, and ethical principles.
- Alert to market opportunities (bothhigh and low tech).
-
cognizant or competitive talents, work ethic, and motivation.

II. Solidly Grounded

-
Thoroughly trained in the fundamentals ot a selected engineering discipline.
Has historical and remains ot advances in science that can
impact
- a
perspective aware

engineering.
Realizes that doubles at breakneck speed and is prepared to continue leamlng
o
knowledge
throughout a career.

III. Technically Broad

- Understands that rearlite problems are multidisciplinary.
-
Thinks broadly, seeing an issue in a rich context uf various alternatives, probabilities, etC., rather
than as a narrow
quest to find single answer.
a

- ls conversant in several disciplines.

I Is trained in systems modeling and the LGHQWL¿UDWORQ of critical elements. Understands the need
well specificationrequirements.
to design experiments to verify or extend analysis, as as meet

- rs psychologically prepared to embrace any GOH¿ necessary to solve the problem at hand.

IV. Effective in
Group Operations
toward creative goal that is
-
cooperative in an organimtion of individuals working a common

often multidisciplinary and multitunrrional in nature.

I Effective in written and oral communication.

-
Willing to seek and use expert advice.
of the value of time and the need to make efficient use of the time in all phases of an
-
Cognizant
endeavor.
-
Understanding and respecttul ot the many facets ot business RSHUDWLXQ²JHQHUDO management,
marketing, tinance, law, human resources, manufacturing, service, and especially quality.
V. Versatile
0 Innovative development of products and services.
in the
o sees engineering as applicable to problem solving in general.
- Considers applying engineering beyond the typical employment tocus ot engineering graduates
In the manufacturing industries, to the much broader ecnnomy ODLFQDQ¿ services, health care,
transportation, etc.) where engineering skills could make a dramatic improvement in the produc-
tivity of those segments ot the economy, which employ 80 percent ot the U.S. population.
VI. Customer Oriented
Realizes that and is the only guarantee of business success.
-
finding satlstying customers
excel in the test of custeffecu'veness in the global
I Understands that producs and services must
marketplace.
 Chapter1 The Engineering Design Process 13

J Design
Process

; Project j
\ Excellence J
\ //\




ªaaa??
µIUPWHVVLRQDLL
Skills
\
,

\\ V/

Figure 1.7 The guiding philosophy of this book. To achieve success in executing engineering and
design projects, it takes an understanding of the design process, strong technical design tools, and
professional skills.

The intention is to teach the application of

design principles to computer and electrical
engineers and to help prepare students for a professional career. The majority of engineering
education is devoted to math, science, engineering science, and problem solving. They are
important topics, required to enter this highly tedwnical GOH¿ However, it is clear that there are
other aspects beyond this that are equally important for success, including an understanding
of system design, innovation, ethical principles, teamwork, and strong communication skills.
The book is divided into three parts: ,²7KH Engineering Design Process, O
L²'HVLJQTools,
and OOO²,¶URIHVVLRQD_ Skills. This is shown in Figure 1.7 as three separate, but related FRPSR²
nents that play a key role in achieving project H[FFOOFQFH²WBKH ability to complete a project, in
an ethical manner that meets the customer's need, satisfies the constraints, and is clearly
communicated to all involved. The chapters are decoupled as much as possible so that the
reader can move between chapters as necessary. In Part I, the emphasis is on understanding
and gaining experience in the different phases of the design process. The reader is guided
through the steps of project identification, research, specification development, creative FRQ²
ccpt generation, and critical evaluation of competing solutions. Part It addresses topics that
are often employed in design, including functional decomposition, description of system be-
havior, reliability, zmd testing. Part III addresses professional skills, including teamwork
principles, project planning, ethics in design and the profession, and oral communication
skills.
Here thoughts to conclude the chapter and get started on the path to great dea
are a few

signs. You are embarking on what will likely be a fun, challenging, sometimes frustrating, and
ultimately rewarding journey. The systems that engineers work with continue to become
14 Design for Electrical and Computer Engineers

increasingly complex multidisciplinary in nature, The example problems presented in this

and
book come from the VGOH¿ of analog electronics, digital electronics, electrical systems theory,
and software systems. These four areas constitute a
significant problem-domain common to

the education of most electrical and computer engineers. Finally, consider the quote below by
Robert Hayes on the importance of design.

Frftcm yams ugu, companiescompared on price. Tudrzyit's [Link] its GHVLJU]²

Robert H, Hayes, Harvard Bzlsincss School, 1991.

What saying? Well, it is clear that the world continues

is this to move to a more know-

ledge-based society, where individuals and companies compete on the strength of their LQWHO²
lectual capital and ability to produce new and innovative products. That is what design is all
about. It is not saying that price and quality are unimportant, they certainly are; in tact quality
and reliability in design are part of this book. It is that quality and price are a given, and suc-
cessful products will be distinguished by their design characteristics. The implication is that

design will play a larger role in the development and success of products. The future Hayes

predicted is now. Design is what distinguishes between products that are seen as commodities
and those that are truly unique and profitable.

1.4 Summary and Further Reading

Engineering design is an imrative process in which the design team employs creativity and
technical knowledge to develop a solution that best meets the HQGªXVHUV¶ needs within the
constraints applied to die problem. There is no single design process that can be applied to all
situations and technologies, but there are many common elements shared, regardless of the
to successfully bring designs to fruition, it takes
technology under consideration. In order a

combination of design tools, professional skills, and a clear understanding of die process
needed to complete designs. The objective of this book is to develop your SUR¿FLHQF\ in daese

areas so that you may become an effective engineer and achieve excellence in design projects.

Engineering Design Methods by Nigel Cross [Cro00] presents the differences betweem de-
a wide array of processes in more GH²
scriptive and prescriptive design processes, and covers
tail. It also discusses the cognitive characteristics of effective designers. There are many good
books on software engineering process development methods. Software Engneering by Ian
Sommerville [Somlll] discusses the different software design process models, such as the ZDª
terfall and spiral models. This is also true of many modern software engineering texts. The
original reference to the waterfall model is by Royce [Roy70]. The Art of Innovation by Mi-
chael Kelley [Kel0l] describes the activities of ZHOO²NQRZQ design company l'DEO and is a
description of their design practices. The ABC Nightlinr news also
highly readable program
produced an interesting segment on IDEO [ABC01] that can be purchased at the ABC website.
The Circle of Innovation by Tom Peters [l"et97] is another popular book that provides his SHU²
spective on current trends in business and the importance of design.
 Chapter1 The Engineering Design Process 15

1.5 Problems
1.1. In your own words, describe [Link] difference between prescriptive and descriptive design
processes. Cite examples of each.

the problem identification, research, and requirements

1.2. Describe relationship between
the

specification phases of the design process.

the and design phases of the
1.3. Describe the relationship between Concept generation
design process.
1.4. Construct prescriptive design process for the problem identification, research, specifica-
a

be a flowchart
tion, concept, and design phases of the design process. The result should
that contains decision blocks and iteration as necessary.

1.5. Describe the main differences between the VLSI and embedded system design processes.
conduct research the spiral software design process.
1.6. Using the library or [Link], on

a) Outline the VLSZL¿FDQWelements of the spiral software design process.

Describe the advantages and disadvantages of this relative to the waterfall model.
b)
Cite all references used.

1.7. Using the library or Intemet, conduct research on the extreme programming design
process.

a) Outline the significant elements of the extreme programming paradigm.

What the pro and for this software development model?
b) are con arguments
Cite all references used.

Project Application. l_n preparation for project and team selection, develop personal
a
1.8.

inventory [Link] includes a list of five favorite technologies

or engineering subjects that
in [Link]. Also, list the strengths and weaknesses that you bring to a
you are interested
project team.