Professional Documents
Culture Documents
2.2 Finding Information For Your Research Paper: - How To Find Information?
2.2 Finding Information For Your Research Paper: - How To Find Information?
2.2 Finding Information For Your Research Paper: - How To Find Information?
Properly cite the original source of all Do not cite where the information came from
information
Easy for other people to find or obtain Difficult for others to obtain
2.3 Bibliography & References
• Make a list to keep track of ALL the books, magazines, and websites
you read as you follow your background research plan. Later this list of
sources will become your Bibliography.
• For every fact or picture in your research paper you should follow it
with a citation telling the reader where you found the information.
• Difference between Bibliography & References?
• A list of references contains only the sources that you specifically cite within
your paper or essay.
• A bibliography, on the other hand, can contain sources you read and which
readers might find valuable to know about even though you didn't specifically
cite them within the body of your writing.
2.3 Bibliography & References
• A citation is just the name of the author and the date of the
publication placed in parentheses like this: (Author, date). This is
called a reference citation when using APA format and if IEEE format
is being used, citation is just number in square bracket i.e. [1], [5],
[20-23]
• Its purpose is to document a source briefly, clearly, and accurately.
2.3 Bibliography
Collect this information for each Collect this information for each Web
printed source: Site:
•author name
•title of the publication (and the title of the
article if it's a magazine or encyclopedia) •author and editor names (if available)
•title of the page (if available)
•date of publication •the company or organization who posted the
•the place of publication of a book webpage
•the publishing company of a book •the Web address for the page (called a URL)
•the volume number of a magazine or printed •the last date you looked at the page
encyclopedia
•the page number(s)
3. Specify Requirements
• Design requirements state the important characteristics that your
solution must meet to succeed.
• What’s the best ways to identify the design requirements?
• Analyze the concrete example of a similar, existing product, noting each of its
key features.
• But how to analyze?
3.1 How to Analyze a Physical Product
• When you start to identify your design requirements, you already
know what problem you are trying to solve.
• But what does "solving" your problem really mean?
• Your design requirements are the specific needs that must be met in order to
call your design a solution.
• For a physical product, your problem is likely making a task possible or
easier for a user to complete.
3.1 How to Analyze a Physical Product
• An example is a pair of crutches. The problem statement is:
• People need a way to walk while using only one foot, because they still need
to be able to get around when one of their feet or legs is injured.
• From the problem statement, you can
• start asking the right questions to create a list of design requirements.
• Pull the major needs of your solution from your problem statement.
Example: The Major Needs of a pair of crutches are that they help
the user to:
• Walk while using only one foot
• Get around and mobilize
3.1 How to Analyze a Physical Product
• Few questions about analyzing physical product:
• What are absolutely essential to satisfy this need?
• What are physical requirements/limits?
• What are conceptual requirements/limits of the product?
• Do other products exist similar to your future design?
• Do you future product will have to compete with the other products?
• Will you include any features that are not present in the competing product?
What are they?
• How many requirements should you have?
3.1 How to Analyze a Physical Product
• For each need, ask yourself: "What is absolutely essential to satisfy
this need?"
• Right now, do not brainstorm. Instead, figure out what MUST happen
to meet the need in your future solution.
• Your answers to these questions are your first design requirements.
(Note: if you can remove your answer to the question and still meet
the need, then your answer is not a design requirement.)
3.1 How to Analyze a Physical Product
• The "Needs" table illustrates how to find the first design requirements
for the crutches example.
• Look at the right side of your table. Which functions listed here will your product
need to fulfill?
• Circle these functions, and look at the feature on the left for each.
• Is the feature absolutely essential in meeting the need on the right?
• If yes, then this is a design requirement, and you should circle it.
• If it is not, it is a possibility that could contribute to your design, but not a requirement.
3.1 How to Analyze a Physical Product
• Is the product that you are designing going to have to compete with
the other products?
• If yes, then look more closely at the features on the left side of your table.
• If you feel that your design needs to include the feature in order to
keep up with current products, then that feature becomes another
design requirement.
3.1 How to Analyze a Physical Product
• Will you include any features that are not present in the competing
product? What are they?
• If they are features that you consider to be "must haves" in order to
make your design successful, then they can be considered your final,
additional design requirements.
3.2 How Many Design Requirements?
• How many requirements should you have?
• That's a really good question without a good answer. You should have neither too many
nor too few.
• What is "too many" depends on the product.
• An airliner might have thousands of design requirements, and that could be just right.
• For a university project, two or three, or maybe five design requirements are
appropriate.
• The reality is that experience is very important in deciding how many design
requirements are important.
• If you have too many design requirements, it can become very difficult to
actually design and build a product.
3.2 How Many Design Requirements?
• Why might too few design requirements be a problem?
• If you have too few requirements, you might get a result that you don't really
want.
• Let's say that you do not specify a cost requirement. You might end up
designing something that costs many times more than what people
would be willing to pay for it. Your design would be a failure. So, don't
be a slacker on your design requirements.
Over • if it has too many requirements
Constrained Design
Under • one with too few requirements
Constrained Design