Please enable JavaScript.
Coggle requires JavaScript to display documents.
Information Gathering Methods - Coggle Diagram
Information Gathering Methods
What is Requirement
Requirement Types
Business Requirement
User Requiremnts
Functional Requiremnts
Nonfunctional Requiremnts
System Requirements
A requirement is simply a statement of what the system must do or what characteristics it needs to have
Analysis Phase
Task
Inputs
Outputs
Processes
Performance
Security
The role of the analyst: understand the language of business and computers
System Analyst Skill: identify the problem, evaluate the key element, develop useful solution, communicate effectively
Modeling Tools & Techniques
Model: helps user, manager, Dev understand the design of system like: FDD, UML, DFDS,..
Modeling: describe business processes, requirements and user interaction with the system
Case tool:using the CASE tool, a system analyst can creatr model
Fact Finding
Identify information you need
Asking series question: What, Where, Who, When, How
Each question musk answer another important question: Why
Requirement Gathering Methods
Interviews
Reveal information about
Interviewee Opinions
Interviewee feelings
Goals
Key HCI concerns
Seven Basic Steps
Selecting Interviewees
Establish objective for the interview
Designing interview question
Preparing for the interivew
Conducting the interview
Document the interview
Post the interview pop-up
Questionnaries
Key organization members
Attitudes
Beliefs
Behavior
Characteristics
Question Types
Open-ended
Closed
Questionnaire language
Simple
Not patronizing
Short
Free of bias
Specific
Technically accurate
JAD Session
Who is Involed
Executive sponsor
IS Analyst
Users
Session Leader
Observers
Scribe
Benefit of JAD
Time is saved
Rapid development
Improved user ownership
Creative idea of production
Five Basic Step
Selecting Participants
Designing the JAD Session
Preparing
Conducting
Post JAD follow up
User Stories
Four Purposes For Telling a Story
Experiential stories
Explanatory stories
Validating stories
Prescriptive stories
Document Analysis
Typical of document
Forms
Reports
Policy manuals
Observation
System Requirement Checklist
5 general categories
Outputs
Inputs
Processes
Performance
Control
Server as benchmarks to measure the overall acceptability of the finished system
Requirement Analysis Strategies
BPA(Business Process Automation): problem analysis, root cause analysis
BPI(Business Process Improvement): duration activity, activity-based costing, informal benchmarking
BPR(Business Process Reengineering): outcome analysis, technology analysis, activity analysis
Characteristics of Analysis Strategies: potential business value, project cost, breadth of analysis, risk