Lecture-5
Uploaded by
Kagami TaigaLecture-5
Uploaded by
Kagami TaigaI.T.
200A – THESIS 1
LECTURE 5
DATA GATHERING
Conduct an interview and gather the
software requirements.
Requirements describe the “what” of a
system, not the “how”.
The input to requirements is the problem
statement prepared by the customer. The
problem statement may give an overview of the
existing system along with broad expectations
from the new system.
FUNCTIONAL REQUIREMENTS
Functional requirements describe what the
software has to do. They are often called software
product features.
Functional requirements are the details and
instructions that dictate how software performs
and behaves. Typically, software engineers create
and apply functional requirements to software during
the development stages of a project to ensure their
software is easy to use and operational.
NON-FUNCTIONAL REQUIREMENTS
Non-functional requirements are mostly quality
requirements. That stipulate how well the software does, what
it has to do.
A non-functional requirement is a function that helps
software operate efficiently. These requirements are not
mandatory for a system to have, though they typically increase
a software's overall quality, speed and storage capacity.
Non-functional requirements allow users to specific
software features that enhance their usability. For example, if a
user prefers their software to have a larger amount of data
storage, they may choose a software system that has a
NON-FUNCTIONAL REQUIREMENTS EXAMPLE
1. Speed
2. Security
3. Portability
4. Compatibility
5. Capacity
6. Reliability
7. Environment
8. Localization
DATA GATHERING
Gather the functional and non-
functional requirements of the software
project proposal.
WHAT DATA NOT TO GATHER?
Do not gather their classified or sensitive
data.
WHAT DATA TO GATHER?
Gather the field names or fill-up form.
WHAT TO DO?
1. Create the Survey Questionnaire with Face Validation
for the degree of problem and submit to three(3)
experts for face validation.
2. Gather the current procedures of the existing manual
system in responding the Objective No.2 through Client
Interview. Write the detailed steps or procedures of
their work related to your software proposal and draw a
flowchart of the current procedures.
3. Identify the features(functional requirements) of the
thesis software project in responding the Objective
No.3 through Client Interview.
“Scientific research can reduce superstition
by encouraging people to think and view things
in terms of cause and effect.”
Albert Einstein
END OF LECTURE
