Please enable JavaScript.
Coggle requires JavaScript to display documents.
TOPIC 3.1 : PRELIMINARY ANALYSIS - Coggle Diagram
TOPIC 3.1 : PRELIMINARY ANALYSIS
1) SYSTEM REQUIREMENTS
a. system developers must identify and describe all system requirements.
b. characteristic or feature that must be included in a information system to satisfy business requirements and be acceptable to users.
c. serve as benchmarks to measure the overall acceptability of the finished system.
d. fall into 5 general categories
iii) Processes
:star: the human resources system must interface properly with the existing payroll system.
:star: the prescription system must automatically generate an insurance claim form.
iv) Performance
:star: response time must not exceed 4 seconds.
:star: the system must support 25 users online simultaneously.
ii) Inputs
:star: the department head must enter overtime hours on a sperate screen.
:star: student grades must be entered on machine-scannable forms prepared by the instructor.
v) Controls
:star: all transactions must have audit trails.
:star: the system must create an error log file that includes the error type, description and time.
i) Outputs
:star: the web site must report online volume statistic every 4 hours and hourly during peak periods.
:star: the contact management system must generate a daily reminder list for all sales reps.
2) FACT FINDING TECHNIQUES
a. user must identify the information need.
b. develop a fact-finding plan can involve series of questions (4W1H) or use structured approach such as Zachman Framework.
c. some example of these question 4W1H.
WHO :question:
who performs each of the procedures within the system?
are the correct people performing the activity?
WHAT :question:
what is being done?
what procedures are being followed?
WHERE :question:
where are operations being performed?
could they be performed more efficiently elsewhere?
WHEN :question:
when is a procedure performed?
is this the best time?
HOW :question:
how is a procedure performed?
why is it performed in that manner?
d. the Zachman Framework.
for Enterprise Architecture
help managers and users understand the model.
e. the techniques used in fact finding
:check: questionnaires
starts with a heading which include title, brief statement of purpose, the name and anything else
type of questionnaires
open-ended questions
close-ended question
:check: documentation review
can help your understand how the current system is supposed to work
can obtain document samples during interview with the people who perform that procedure
:check: sampling
collect example pf actual documents using a process called sampling
sampling techniques include
ii. stratified sampling
iii. random sampling
i. systematic sampling
:check: interviews
step 4 : prepare for the interview
step 5 : conduct the interview
step 3 : develop interview questions
step 6 : document the interview
step 2: establish objective for the interview
step 7 : evaluate the interview
step 1 : determine the people to interview
:check: research
another important fact-finding technique
can include the internet, IT magazines and book to obtain background information
:check: observations
seeing the system in action gives you additional perspective and a better understanding of the system procedures
you observe people at work, consider a factor called the Hawthorne Effect
3) ANALYZE THE GATHERED INFORMATION
a. step to analyze the gathered information
step 3 : decide how to analyze the information
step 4 : analyze quantitative information
step 2 : organize the information
step 5 : analyze qualitative information
step 1 : review the questions
step 6 : integrate the information
4) MODELING TOOLS AND TECHNIQUES
b. can use various tools
c. help them understand use
:explode: Functional Decomposition Diagrams (FDD)
:explode: Unified Modeling Language (UML) diagrams
a. involves graphical methods and nontechnical language that represent the system at various stage of development
5) FUNCTIONAL DECOMPOSITION DIAGRAMS
a. top-down representation of a function or process
b. an analyst can show business function and break them down into lower-level functions and processes
c. use FDD to model business function and show how they organized into lower-level processes
6) UNIFIED MODELING LANGUAGE
a. UML provide various graphical tools
:fire: use case diagrams
visually represents the interaction between users and the information system
use case modelling
:check: actor
:check: symbol for use case is an oval with label
:check: use cases also can interact with other use cases
:fire: sequence diagrams
show the timing of interaction between object as they occur
include symbols the represent
:check: lifelines
:check: messages
:check: classes
:check: focuses
