University of Wisconsin Automated Home Waste Collection & Disposal Machine Paper Please follow the template to finish the research paper. The template has all the required instructions. Project Title
Author
Table of Contents
1
Introduction ……………………………………………………………………………………………………………. 3
2
Needs Analysis ………………………………………………………………………………………………………… 3
2.1
3
Operations Analysis ……………………………………………………………………………………………. 3
2.1.1
Analysis of Projected Needs………………………………………………………………………….. 3
2.1.2
Stakeholders ………………………………………………………………………………………………. 3
2.1.3
Operational Objectives ………………………………………………………………………………… 4
2.2
Functional Analysis …………………………………………………………………………………………….. 4
2.3
Feasibility Definition …………………………………………………………………………………………… 5
2.4
Needs Validation ……………………………………………………………………………………………….. 5
2.5
System Operational Requirements ………………………………………………………………………. 6
2.5.1
Operational Requirements Statements ………………………………………………………….. 6
2.5.2
Operational Scenarios ………………………………………………………………………………….. 6
References ……………………………………………………………………………………………………………… 7
Attachment 1 …………………………………………………………………………………………………………………. 9
System Operational Requirements Version 1.0……………………………………………………………….. 9
Operational Requirements ……………………………………………………………………………………….. 9
Operational Scenarios ………………………………………………………………………………………………. 9
2|Page
1 Introduction
Introduction to the problem the project is intended to address. Be brief. Describe the system
you are designing in terms of functionality (ie. What the system does). If there is a predecessor
system, briefly explain what it does, and then very briefly explain what it needs to do that it
currently does not do, that your project will address. It should not be simply an exact repetition
of the problem statement you were given; there should be some evidence that you understand
why the problem has not been trivially solved already.
If you find yourself describing how your new system will do this, or describing technologies that
your system will use to solve this problem, you not doing this step correctly! There will be a
time for this much later in the project, but not here or in the needs analysis.
2 Needs Analysis
2.1 Operations Analysis
2.1.1 Analysis of Projected Needs
Describe the need for a new system. What is driving the need for the system? Is it a deficiency
in the current system? Is it a need for better sales? Is it a need to add new technology to a
system? Is the current system becoming obsolete?
Describe the deficiencies in the current system, if there is one.
This section should explore these matters in more depth than the Introduction.
2.1.2 Stakeholders
Identify all the people and organizations that would care if a solution to this problem is
developed. Some may be glad the system is being developed because it will make their lives
better in some way. Others may be concerned about the impact the new system will have on
other existing systems and processes. In some cases there may be people who are negatively
impacted. In each case, identify the stakeholder and the concerns they have about how the
“problem” could be solved.
T ABLE 1: S TAKEHOLDERS
Stakeholder
Description
What they care about
3|Page
2.1.3 Operational Objectives
Describe your analysis process for determining the operational objectives.
Determine the operational objectives for the system. The objectives should have these
properties as stated in the book:
• Objectives should address the end state of the operational environment or scenario — it
focuses on what the system will accomplish in the large sense.
• Objectives should address the purpose of the system and what constitutes the satisfaction
of the need.
• Taken together, objectives answer the “why” question — why is the system needed?
• Most objectives start with the infinitive word “provide,” but this is not mandatory.
The objectives should describe what you want the system to do or how you want it to function.
The list will generally start with the main things you want the system to do for the primary user,
but to the extent possible you want to address the needs of the other stakeholders. It may not
be possible for the system to address all the perceived needs of all the stakeholders, but you
should have at least identified those needs and discussed why it is not practical to address them
in the system.
T ABLE 2: O PERATIONAL O BJECTIVES L IST
Objective #
OO-1
OO-2
OO-3
OO-4
OO-5
Objective
Put the objectives in an objectives tree like Figures 6.3 & 6.4 (functions are not part of the tree).
Draw a system context diagram (like figures 3.2 and 3.3). Remember that the context diagram
primarily answers the questions What functionality is INSIDE my system?, What functionality is
OUTSIDE my system that my system interacts with?, and What kinds of interactions are there at
the system boundary?
This is a good reference on how to develop operational objectives.
http://www.ops.fhwa.dot.gov/publications/fhwahop10027/chap_2.htm
2.2 Functional Analysis
Describe how you performed the functional analysis.
4|Page
Define functions necessary to meet objectives. High level functions are stated in a very general
way in Table 3.2. Start with the objectives from the previous section and determine what
functions are needed to achieve each of those objectives.
Draw a block diagram showing the interactions with the environment from the system context
diagram and the functions needed in the system.
2.3 Feasibility Definition
Describe the feasibility of the system. To do this you should relate your system ideas to the
current system and the available technology. Could a feasible system be developed? For the
functions defined in Functional Analysis, is it possible to design a system that has those
functions?
T ABLE 1: F UNCTION FEASIBILITY
Function
Existing System
New System
High Cost (Y/N)
2.4 Needs Validation
In the section you should demonstrate that the there is a need for a new system and it is
feasible to meet that need at an affordable cost and at an acceptable risk.
Describe the major scenarios in which the system will function and system responses. Develop
system performance parameters and measures of effectiveness (MOE) for each of the
scenarios. There will likely be more than one MOE for each scenario. The MOEs are metrics of a
system’s overall performance and always refers to the system as a whole.
T ABLE 2: T ABLE OF MOE S
MOE # Metric
MOE-1
MOE-2
MOE-3
MOE-4
MOE-5
Units
Conditions (Scenario #)
5|Page
2.5 System Operational Requirements
This section is to describe how you developed the Operational Requirements statements and
Operational Scenarios, which is the primary product of Needs Analysis and is the input to the
next phase of development (Concept Exploration). The result of your work in this section is to
be documented in Attachment 1: System Operational Requirements, Version 1.0 (below).
2.5.1 Operational Requirements Statements
This section should be an analysis and description of how you generated your list of operational
requirements. The operational requirements are things the system must be able to do in order
for all of the scenarios above to work. They generally should involve more detail than the
operational objectives presented earlier. They must be stated in measurable terms, at least in
the sense that it must be possible to definitively say whether the requirement has been met or
not. The rationale for all requirements must be stated. Some will address a single operational
need, while others result from the interaction of multiple needs. Operational requirements are
described on p. 145 in the text.
2.5.2 Operational Scenarios
The book states that each Scenario usually has the 5 items within it. The outline here shows
what those items are. The number of Scenarios needed is dependent on how the project
system will be used. Also, the type of content is also dependent on the project. It could be
mostly text or it could be text with many diagrams.
Develop and discuss the Scenarios here, but formally document them in Attachment 1.
Summarize here your work and thinking on how many Scenarios there are and the reasoning as
you developed them. Once you are done, you do not need to include the outline (2.5.2.1) here
unless you want to show the primary Operational Scenario or an example of a Scenario that you
developed.
Later in the design process we will revisit scenarios, but inside the system. They will be related
to, but NOT be identical to the scenarios presented here.
2.5.2.1 Scenario n
2.5.2.1.1 Mission Objectives
What are the mission objectives this scenario is attempting to address? These may be
operational objectives from those identified above, or may be even higher level
objectives in which the system being designed may be only one small element. One
scenario may address multiple objectives, and an objective may be partially or fully
addressed by more than one scenario.
2.5.2.1.2 Architecture
What is the structure being assumed by the scenario sequence description below? This
is NOT the structure of the system to be designed (we haven’t gotten there yet!) but the
6|Page
structure of the people, organizations, and larger systems in which this sequence of
steps that will use our system will play out.
2.5.2.1.3 Physical Environment
What is being assumed about the environment outside the system in the scenario
sequence description below?
2.5.2.1.4 Competition
What forces or entities are actively resisting, impeding, or threatening the successful
execution of the scenario and/or the completion of the higher level mission?
2.5.2.1.5 General Sequence of Events
What is the sequence of steps by which the outside actors accomplish their purposes at
least partially by using the project system?
3 References
These are the acceptable types of references and acceptable formats. Make sure you have
references and that you refer to them in the text. If you use images or other material from a
reference you need to have that shown in your document.
Article in a collection
[1]
A.J. Albrecht, “Measuring Application-Development Productivity,” Programmer Productivity Issues
for the Eighties, 2nd ed., C. Jones, ed., IEEE CS Press, 1981, pp. 34-43.
Article in a conference proceedings
[2]
M. Weiser, “Program Slicing,” Proc. 14th Int’l Conf. Data Eng. (ICDE 98), IEEE CS Press, 1998, pp.
439-449.
Article in a journal or magazine
[3]
I.E. Sutherland, R.F. Sproull, and R.A. Schumaker, “A Characterization of 10 Hidden-Surface
Algorithms,” ACM Computing Surveys, Mar. 1974, pp. 1-55.
Entries in a blog:
[4]
M. Sahami, “About the Google Education Summit,” blog, 26 Oct. 2007,
http://googleblogspot.com/2007/10/about-google-education-summit.html.
[5]
“Reinforcement Learning is Cool,” blog, 24 Oct. 2007, http://smartmachines.blogspot.com/2007/10/reinforcement-learning-is-cool.html. (no named author)
To cite the blog itself:
[6]
The Official Google Blog, Google, http://googleblog.blogspot.com. (Google is listed as the publisher
here.)
[7]
M. Watson, Artificial Intelligence Blog, http://markwatson.com/aiblog.
Book
[8]
W.M. Newman and R.F. Sproull, Principles of Interactive Computer Graphics, McGraw-Hill, 1979, p.
402.
[9]
M.A. Arbib, ed., The Handbook of Brain Theory and Neural Networks, MIT Press, 1998.
7|Page
Book series
[10] Y. Yao et al., “Web Intelligence (WI): Research Challenges and Trends in the New Information
Age,” Web Intelligence: Research and Development, LNAI 2198, N. Zhong et al., eds., SpringerVerlag, 2001, pp. 1-17.
Dissertation or thesis
[11] B. Fagin, “A Parallel Execution Model for Prolog,” doctoral dissertation, Dept. Computer Sciences,
Univ. of California, Berkeley, 1987.
Online-only publication
[12] F. Kaplan, “From Baghdad to Manila: Another Lousy Analogy for the Occupation of Iraq,” Slate, 21
Oct. 2003; http://slate.msn.com/id/2090114/.
Web site
[13] R. Bartle, “Early MUD History,” Nov. 1990; http://www.ludd.luth.se/aber/mud-history.html.
Patent
[14] M. Hoff, S. Mazor, and F. Faggin, Memory System for Multi-Chip Digital Computer, US patent
3,821,715, to Intel Corp., Patent and Trademark Office, 1974.
Pending publication
[15] R. Lee, “New-Media Processing,” to be published in IEEE Micro, Nov./Dec. 2006.
Specification
[16] MPEG-21 Overview, ISO/MPEG N5231, MPEG Requirements Group, Oct. 2002.
8|Page
Attachment 1
System Operational Requirements
Version 1.0
This section is the primary product of Needs Analysis and is the input to the next phase of
development (Concept Exploration).
Operational Requirements
This section should show the list of Operational Requirements. Do a brief description here of
what you are showing in the Table below so this attachment will read as a standalone
document of the results of your Needs Analysis.
T ABLE 3: O PERATIONAL R EQUIREMENTS S TATEMENTS
OR #
OR-1
OR-2
OR-3
OR-4
OR-5
OR-6
Operational Requirement
Rationale
Operational Scenarios
This section should show the Operational Scenarios. Do a brief description here of what you are
showing in the descriptions below so this attachment will read as a standalone document of the
results of your analysis of the Scenarios during the Needs Analysis.
Develop as many scenarios (1-n) as needed by YOUR system and project.
Scenario 1
Mission Objectives
What are the mission objectives this scenario is attempting to address? These may be
operational objectives from those identified above, or may be even higher level
objectives in which the system being designed may be only one small element. One
scenario may address multiple objectives, and an objective may be partially or fully
addressed by more than one scenario.
Architecture
What is the structure being assumed by the scenario sequence description below? This
is NOT the structure of the system to be designed (we haven’t gotten there yet!) but the
9|Page
structure of the people, organizations, and larger systems in which this sequence of
steps that will use our system will play out.
Physical Environment
What is being assumed about the environment outside the system in the scenario
sequence description below?
Competition
What forces or entities are actively resisting, impeding, or threatening the successful
execution of the scenario and/or the completion of the higher level mission?
General Sequence of Events
What is the sequence of steps by which the outside actors accomplish their purposes at
least partially by using the project system?
Scenario 2
Using the system to accomplish a different mission objective…
Mission Objectives
Architecture
Physical Environment
Competition
General Sequence of Events
Continue as many Scenarios as needed for your system…
Scenario n
Using the system to accomplish a different mission objective…
Mission Objectives
Architecture
Physical Environment
Competition
General Sequence of Events
10 | P a g e
Project Title
Author
Table of Contents
1
Introduction ……………………………………………………………………………………………………………. 3
2
Needs Analysis ………………………………………………………………………………………………………… 3
2.1
3
Operations Analysis ……………………………………………………………………………………………. 3
2.1.1
Analysis of Projected Needs………………………………………………………………………….. 3
2.1.2
Stakeholders ………………………………………………………………………………………………. 3
2.1.3
Operational Objectives ………………………………………………………………………………… 4
2.2
Functional Analysis …………………………………………………………………………………………….. 4
2.3
Feasibility Definition …………………………………………………………………………………………… 5
2.4
Needs Validation ……………………………………………………………………………………………….. 5
2.5
System Operational Requirements ………………………………………………………………………. 6
2.5.1
Operational Requirements Statements ………………………………………………………….. 6
2.5.2
Operational Scenarios ………………………………………………………………………………….. 6
Concept Exploration…………………………………………………………………………………………………. 6
3.1
Operational Requirements Analysis ……………………………………………………………………… 6
3.1.1
Operational Scenarios ………………………………………………………………………………….. 8
3.2
Performance Requirements Formulation ……………………………………………………………… 8
3.3
Implementation Concept Exploration …………………………………………………………………… 9
3.4
Performance Requirements Validation ……………………………………………………………….. 10
4
Concept Definition …………………………………………………………………………………………………. 10
5
References ……………………………………………………………………………………………………………. 10
Attachment 1 ……………………………………………………………………………………………………………. 12
System Operational Requirements Version 1.0 ………………………………………………………….. 12
Operational Requirements ……………………………………………………………………………………… 12
Operational Scenarios …………………………………………………………………………………………….. 12
Attachment 2 ……………………………………………………………………………………………………………. 14
System Operational and Performance Requirements Version 2.0 ………………………………… 14
Updated Operational Requirements ………………………………… Error! Bookmark not defined.
Performance Requirements …………………………………………………………………………………….. 14
Operational Scenarios …………………………………………………….. Error! Bookmark not defined.
2|Page
1 Introduction
Introduction to the problem the project is intended to address. Be brief. Describe the system
you are designing in terms of functionality (ie. What the system does). If there is a predecessor
system, briefly explain what it does, and then very briefly explain what it needs to do that it
currently does not do, that your project will addr…
Purchase answer to see full
attachment
