Biology Reference
In-Depth Information
related disorders:
pregnancy-induced hypertension, gestation diabetes
mellitus, malnutrition, anemia, other related disorders;
skin:
eczema, tine
infection, scabies, leprosy, other related skin diseases;
insect/animal bites:
dog bite, scorpion bite, snake bite; other insect and animal bites;
gastro-
intestinal system:
acute diarrheal disease, abdominal colic, jaundice, worm
infection, amoebiasis, acid peptic disease, food poisoning, apthus ulcer,
other related GIT system;
genitourinary system:
urinary tract infection,
menstrual disorder, RTI, malignancy, other related diseases including
nephritic disease;
neurological disorder:
epilepsy, CVA, meningitis, other
neurological disorders;
E N T:
sinusitis, ASOM CSOM middle ear infec-
tions, hearing defects, foreign body in ear, foreign body in nose, others;
E N T:
dental carries, dental fluorosis, other dental problems, gingivi-
tis;
ophthalmic:
refractive errors, conjunctivitis, foreign body in eye, stye,
other related diseases;
nutritional disorder:
anemia, Vitamin A deficiency,
Vitamin B deficiency, malnutrition, other vitamin deficiencies;
endocrine
system:
Diabetes mellitus, goiter, others;
all other causes:
accidents and inju-
ries, burns, surgical-related diseases.
13.4. Top-Down, Bottom-Up Approach
for Requirements Analysis
This section outlines the methodology applied to gather, verify, and docu-
ment the set of User Requirement Specifications (commonly referred to as
the URS or business study in software engineering principals). Figure 13.5
summarizes the processes involved in initiating and completing the user
requirement specifications by taking up a top-down bottom-up approach
(Gadomski et al. 1998). In order to optimize resources, one should com-
plete the producing of the user requirement specifications in a single cycle.
However, if necessary, repeat the cycle as many times until the user require-
ment specifications is stable.
The methodology is analogous to applying the axiomatic framework for
designing systems and reducing system complexities; where the framework
comprises customer, functional, design, and process domains for which cus-
tomer attributes, functional requirements, design parameters, and process
variables, respectively, are defined. The framework is a zigzag scheme, first
starting with the set of functional requirements and constraints that adhere
to the customer attributes; second, deriving the set of design parameters; and
third, identifying the relevant process variable. Thereafter, we sequentially
working backwards from the set of process variables to the design param-
eters and functional requirements to adjust them to reduce system complexi-
ties (Suh 2005).
