Escolar Documentos
Profissional Documentos
Cultura Documentos
Saketh Gutti
Table of Contents
1 Introduction...............................................................................................4
2 Needs Analysis..........................................................................................4
2.1 Operations Analysis..............................................................................4
2.1.1 Analysis of Projected Needs...........................................................4
2.1.2 Operational Objectives...................................................................4
2.2 Functional Analysis...............................................................................6
2.3 Feasibility Definition.............................................................................6
2.4 Needs Validation..................................................................................7
2.5 System Operational Requirements.......................................................8
2.5.1 Operational Scenarios....................................................................8
2.5.2 Operational Requirements Statements........................................10
3 Concept Exploration................................................................................10
3.1 Operational Requirements Analysis...................................................10
3.1.1 Operational Scenarios..................................................................12
3.2 Performance Requirements Formulation............................................14
3.3 Implementation Concept Exploration.................................................15
3.3.1 Concept 1.....................................................................................15
3.3.2 Concept 2.....................................................................................16
3.3.3 Concept 3.....................................................................................16
3.3.4 Concept 4.....................................................................................17
3.3.5 Concept 5.....................................................................................18
3.4 Performance Requirements Validation...............................................19
4 Concept Definition...................................................................................20
4.1 Performance Requirements Analysis..................................................20
4.2 Functional Analysis and Formulation..................................................21
4.3 Functional Allocation..........................................................................21
4.3.1 Sensor: Concept 1........................................................................21
4.3.2 Sensor: Concept 2........................................................................22
4.3.3 Valve/Control: Concept 1..............................................................23
4.3.4 Valve/Control: Concept 2..............................................................24
4.3.5 Valve/Control: Concept 3..............................................................25
4.4 Concept Selection..............................................................................26
2 | Page
4.5 Summary of Final Concept.................................................................28
4.5.1 Operational View..........................................................................28
4.5.2 Logical View..................................................................................30
4.5.3 Physical View................................................................................31
5 References...............................................................................................32
3 | Page
1 Introduction
In this 21st century, we still follow the conventional way of grading an answer
sheet. Tutors go through each word and line in an essay or each step in a
math problem in order to grade the answer sheet. This method takes time
and effort. The project helps to develop a robotic system that can grade an
answer sheet in no time.
2 Needs Analysis
2.1 Operations Analysis
2.1.1 Analysis of Projected Needs
Consider a professor who teaches a population of 60 in a class. He knows
that multiple choice questions are a terrible way of measuring a students
knowledge on the subject. If he dared to ask written explanations on the
quiz, he has to spend hours of time grading the quiz. On the other hand,
grading a fill in the bubble quiz is quite easy. But grading essay answers in a
quiz is quite time taking, which otherwise, this time can be used for some
productive work.
2.1.1.1 Stakeholders
The stakeholders include:
The grader or professor or a tutor who grades
Students
The school or the university which allows the usage of the robotic
system
The company which builds the software and the system
The companies that provide raw material to build the system
The grader or professor needs to have the software more reliable which can
exert better results and which give the results in no time so saving a lot of
time. He also need the system to be easy to operate.
Students need the software to be accurate about the results. They need the
results to be impartial and unbiased.
The school or the university requires the software to be bug free so it does
not surface any problems. They need the software not to be too expensive.
The companies that provide raw materials want a good deal to sell their
products
4 | Page
The manufacturer needs to be able to produce robotic system with better
interface at a cost point that is competitive with other systems on market.
5 | Page
OO-2 Efficient assembly the parts for the robotic system
OO-3 Provide a software that is robust
OO-4 Provide an easy user interface
OO-5 Provide a low cost system
OO-6 Provide a bug free software
T ABLE 2: S TAKEHOLDERS
Stakeholder Description
Customer In this context, the university or college is the
customer. They are the ones who buy the robotic
system.
User/Operator Professor or tutor is the User in this context. He is
the one who installs and operates the system.
Student Body The student body is the population which gives
feed to the robotic system.
Supply chain Everyone involved in the production and
distribution of the product. They are the ones who
comes to aid in case of any wrong or bugging with
the system.
Governing bodies This is any governing organizations that provide
rules, regulations and laws that may affect the
product use.
6 | Page
F IGURE 2: S YSTEM C ONTEXT D IAGRAM
7 | Page
F IGURE 3: F UNCTIONAL BLOCK DIAGRAM
8 | Page
key
There are two major scenarios in which this system will function.
9 | Page
Our biggest concern is MOE 1 and MOE 2. As there isnt any development in
automatic interpretation of ones handwriting, it will cost a lot to find a way
to do that.
2.5.1.1 Scenario 1
2.5.1.1.1 Mission Objectives
The main mission objectives are
to develop a software which can understand different handwritings and
interpret the information in it.
to buy the raw products at reasonable price and assemble them.
2.5.1.1.2 Architecture
We buy the raw components for a reasonable price like any other product.
And use man work in assembling those parts.
Later in this scenario companys store will be the physical environment which
is where the finished robotic system is sold.
2.5.1.1.4 Competition
There were graders available already in the market. So we have to make the
customer to purchase our system.
10 | P a g e
2.5.1.1.5 General Sequence of Events
Need to buy the required raw parts from companies
Need to assemble all the parts
Need to program to scan the sheets and save it to interpret
Need to program to assess score on organizing the words, development of
it, sentence structure, word choice, grammar usage and mechanics
Need to work on numbers, signs, formulas and math principles
Need to combine software to the system to result in a robotic system.
Need to sell the system at some reasonable price
2.5.1.2 Scenario 2
2.5.1.2.1 Mission Objectives
The main mission objective is
to install the system and explain the working to the consumer
to rectify any errors which occur while installation
2.5.1.2.2 Architecture
The robotic system is purchased and is set to install. The robotic system
need to connect with electricity. We need to check the working and for any
errors.
2.5.1.2.4 Competition
The main competition for this scenario is in rectifying the errors and to
maintain low temperatures in the room.
11 | P a g e
Changes have to be made in the prompts of the robotic system, so that
the grades given are similar
3 Concept Exploration
3.1 Operational Requirements Analysis
Each operational requirement from the previous section was examined
against the operational objectives and against each other. The seven
features were examined and reported in the table. Each requirement was
first examined to see if it was traceable to an operational objective. Then
each was examined for redundancy, consistency and unambiguousness by
examining the relation to the other requirements. If a possible solution
exists, then it was deemed feasible. If the solution was comparable to what
exists then it was marked affordable. Finally, the requirement was examined
to determine if it was verifiable.
12 | P a g e
With reference to the table of operational requirements, and the operational
objectives, each requirement will be analyzed as stated in each column. The full
question to be answered is stated below:
1. Is the requirement traceable to a user need or operational requirement?
2. Is the requirement redundant with any other requirement?
3. Is the requirement consistent with other requirements?
4. Is the requirement unambiguous and not subject to interpretation?
5. Is the requirement technologically feasible?
6. Is the requirement affordable ($)?
7. Is the requirement verifiable?
Requireme 1 2 3 4 5 6 7
nt Number Traceab Redunda Consiste Unambiguo Feasibl Affordabl Verifiable
le nt nt us e e
OR-1 OO-2 N Y Y Y Y Y
OO-4
OR-2 OO-1 N N N Y Y Y
OO-3 Always be
OO-4 questioned
OR-3 OO-1 N Y Y Y Y Y
OO-2
OO-3
OO-4
OR-4 OO-5 N Y Y Y Y Y
OR-5 OO-1 N N N Y Y Y
OO-3 Always be
OO-4 questioned
OR-6 OO-4 N Y Y Y Y Y
OO-5
OR-7 OO-6 N Y Y Y Y Y
Items marked in red in the previous table indicate a need for updating. Based
on the analysis in the previous table, a new set of requirements was
developed.
13 | P a g e
After updating the table of operational requirements, each operational
objective was analyzed to see if at least one operational requirements maps
to it. This will identify if the set of requirements cover all of the user needs
and operational objectives. Some of this is taken from Table 1Table 6.
T ABLE 8: O PERATIONAL O BJECTIVE TO O PERATIONAL R EQUIREMENT
M APPING
OO Objective UOR # that relates to the OO
#
OO- Provide high reliability by greatly UOR-1, UOR-4
1 minimizing time and effort
OO- Efficient assembly the parts for UOR-1
2 the robotic system
OO- Provide a software that is robust UOR-2, UOR-3
3
OO- Provide an easy user interface UOR-1, UOR-2, UOR-3
4
OO- Provide a low cost system UOR-5
5
OO- Provide a bug free software UOR-4
6
3.1.1.1 Scenario 1
3.1.1.1.1 Mission Objectives
The main mission objectives are
to provide high quality assembly of the mechanical system at low price
14 | P a g e
to provide a robust software
to sell the robotic system at reasonable price
3.1.1.1.2 Architecture
Raw materials for the system is brought at low price and assembled.
Standard AC power is used to do that.
For the software to build many patterns of mathematical signs and numbers
are needed to interpret.
For the software to build engineers of the company are provided with
different styles of writing patterns in their offices.
3.1.1.1.4 Competition
Competition occurs from getting hands on variety of writing patterns. The
more writing patterns one can interpret, the more chance to improve the
software.
Need to make the system with low price so that it can be sold at reasonable
prices.
One competition to the system is other systems available in the stores. We
want the customer to purchase our system.
3.1.1.2 Scenario 2
3.1.1.2.1 Mission Objectives
The main mission objective is
to install the system and do trial and error with quizzes
to eliminate any errors and provide good customer service
15 | P a g e
3.1.1.2.2 Architecture
For this scenario, the system is installed and is required to updated with the
help of the tutor. Quizzes conducted are interpreted to minimize the
constraints.
3.1.1.2.4 Competition
The main competition comes with the time taken to set the system and time
taken to minimize the constraints from the quiz or exam conducted by the
tutor. It is required only for the first time.
Time taken to get back to the customer to rectify any problems gives
competition in the current market.
16 | P a g e
F IGURE 4: U PDATED F UNCTIONAL BLOCK DIAGRAM
For each of the functions the characteristics for that function were
determined. Also, the required performance for each characteristic was
determined.
T ABLE 10: P ERFORMANCE R EQUIREMENTS
Performa Function Characteristic Requirement
nce
Require
ment
Number
PR-1 Material Provide raw materials Quality products
Supplier
PR-2 Sample Required many of them Versatile
writing
patterns
PR-3 Software Need to provide with Efficient
Engineers software
PR-4 Company Assemble the parts Reliability
PR-5 Company Assemble hardware Reliability
with the software
PR-6 Company Helps tutor to minimize Good customer
the constraints service
PR-7 Company Get back to tutor to In no time
17 | P a g e
rectify errors
PR-8 Tutor Conducts exams and Unbiased
minimize the
constraints for one time
PR-9 Students Take the exams or Perform efficiently
quizzes
PR-10 Robotic Scans the papers and Fast and Efficient
System evaluate them
18 | P a g e
3.3.2 Concept 2
This is very similar to the Concept 1, but the information of the scanned data
is send from robotic scanner to computer through transmitter.
3.3.3 Concept 3
For this concept, the papers are fed automatically through the rollers. The
scanned papers are exited automatically through rollers on the other side of
the system. The scanned information is send to the computer through wires,
where the info is evaluated through software system.
19 | P a g e
F IGURE 7: C ONCEPT 3 DIAGRAM
3.3.4 Concept 4
This concept is just similar to Concept 3, except the information is send to
the computer though transmitter and received by receiver in the computer.
20 | P a g e
F IGURE 8: C ONCEPT 4 DIAGRAM
21 | P a g e
Supplier
VPR-2 Sample Required many of them Versatile
writing
patterns
VPR-3 Software Need to provide with Efficient
Engineers software
VPR-4 Company Assemble the parts Reliability
VPR-5 Company Assemble hardware Reliability
with the software
VPR-6 Company Helps tutor to minimize Good customer
the constraints service
VPR-7 Company Get back to tutor to In no time
rectify errors
VPR-8 Tutor Conducts exams and Unbiased
minimize the
constraints for one time
VPR-9 Students Take the exams or Perform efficiently
quizzes
VPR-10 Robotic Scans the papers and Fast and efficient
System evaluate them
4 Concept Definition
4.1 Performance Requirements Analysis
The MTTF of the product as defined by FOR-6 is 5.5 years. So the product will
be in service at least that long on average. Once the product has reached its
end of life, it may be disposed of in a landfill or recycled. In either case, toxic
chemicals and components should be avoided. In particular, lead should not
be used in the PCB manufacture. Also, BPA should not be used in the plastic
components of the product.
22 | P a g e
PRT -3 Need to provide with Efficient Yes
software
PRT -4 Assemble the parts Reliability Yes
PRT -5 Assemble hardware Reliability Yes
with the software
PRT -6 Helps tutor to Good customer Yes
minimize the service
constraints
PRT -7 Get back to tutor to In no time Yes
rectify errors
PRT -8 Conducts exams and Unbiased Yes
minimize the
constraints for one
time
PRT -9 Take the exams or Perform efficiently Yes
quizzes
PRT -10 Scans the papers Fast and efficient Yes
and evaluate them
23 | P a g e
F IGURE 9: F UNCTIONAL A NALYSIS AND F ORMULATION D IAGRAM
24 | P a g e
F IGURE 10: M ANUALLY F ED W IRED C ONCEPT DIAGRAM
25 | P a g e
F IGURE 11: M ANUALLY F ED W IRELESS C ONCEPT DIAGRAM
26 | P a g e
F IGURE 12: A UTOMATIC F ED W IRED C ONCEPT DIAGRAM
27 | P a g e
F IGURE 13: A UTOMATIC F ED W IRELESS C ONCEPT DIAGRAM
4.5.1.1 Scenario 1
4.5.1.1.1 Mission Objectives
The main mission objectives are
28 | P a g e
to build a software system and assemble it with the hardware
to provide the product for the purchase of the user
4.5.1.1.2 Architecture
Raw materials for the system is brought at low price and assembled.
Standard AC power is used to do that.
For the software to build many patterns of mathematical signs and numbers
are needed to interpret.
For the software to build engineers of the company are provided with
different styles of writing patterns in their offices.
4.5.1.1.4 Competition
Competition occurs from getting hands on variety of writing patterns. The
more writing patterns one can interpret, the more chance to improve the
software.
Need to make the system with low price so that it can be sold at reasonable
prices.
One competition to the system is other systems available in the stores. We
want the customer to purchase our system.
4.5.1.2 Scenario 2
4.5.1.2.1 Mission Objectives
The main objective of this scenario is:
to install the system and do trial and error with quizzes
29 | P a g e
to eliminate any errors and provide good customer service
4.5.1.2.2 Architecture
For this scenario, the system is installed and is required to updated with the
help of the tutor. Quizzes conducted are interpreted to minimize the
constraints.
4.5.1.2.4 Competition
The main competition comes with the time taken to set the system and time
taken to minimize the constraints from the quiz or exam conducted by the
tutor. It is required only for the first time.
Time taken to get back to the customer to rectify any problems gives
competition in the current market.
30 | P a g e
F IGURE 14: L OGICAL V IEW S YSTEM C ONTEXT D IAGRAM
The functional flow diagram of the system is shown in Figure 15.
31 | P a g e
F IGURE 15: F UNCTIONAL F LOW D IAGRAM
5 References
Web site
[1] http://www.edweek.org/ew/articles/2014/03/13/25essay-grader.h33.html?
r=197925939&preview=1&user_acl=0
[2] Working of a scanner
https://en.wikipedia.org/wiki/Image_scanner
[3] http://mfeldstein.com/si-ways-the-edx-announcement-gets-automated-essay-grading-wrong/
32 | P a g e