Please enable JavaScript.
Coggle requires JavaScript to display documents.
Mindmap 2 - Requirement Determination - Coggle Diagram
Mindmap 2 - Requirement Determination
Analysis phases
Goal: understand the requirement of the system
Has 2 challenges: right people & collect and gather info
Tasks: describe current system & identify requirements of new systems
performance: speed, volume, capacity,...
Processes: logical rules to transform data --> info
Output: info produced by the system
security: protects data from threats
Input: data enters the system
model: describing current system (physical & logical) --> logical requirements --> detailed design(new system) --> physical design.
Analyst role: as a bridge connect user & programmer to design systems and programs specifications to meet user requirements
System analysis skills
Analytical: indetify problem, develop solution, evaluate key elements
Impersonal: communicate effectively, work with all kind people, balance conflict requirements
Tools & Techniques
Case Tool: CASE tool that can create models
modeling techniques: describe business processes, requirements & user interaction with the system
Model: FDD(Functional decomposition Diagrams), DFDs(Data Flow Diagram), UML(Unified Modeling Language)
Requirement Determination
Requirements
what system must do, characteristics must have
user: what user need to do
business: what the business needs
functional: what software should do
system: how system should be built
nonfunctional: characteristics system should have
System Requirement
characteristic/ feature of IS to satisfy business requirements
benchmark to measure overall acceptability of systems
Five categories: outputs, inputs, processes, performances, controls
Requirement Elicitation Techniques
Questionnaires
Gather info from key organization members: attitudes. beliefs, behaviors, characteristics
planning
: organization member dispersed, involved in the project, exploratory work needed,...
Language
: simple, specific, short, no bias,...
Measurement scales
Nominal: classify things, weakest form
Interval: when intervals are equal, no absolute zero
Validity & Reliability
Validity: what degree questions measures what info
Reliability: consistency responses(same result same condition)
Design
: simple white space, ample space to write response, easy to mark answers, consistent in style. Order from important, clustered similar one, less controversial first
Administer
: who to receive, how administered?(all at once, self-administer, personally administer, mail, web,...)
Steps
: Select participants --> Design --> Administer --> Follow-up
Document analysis
: provide clue about current system from typical docs(forms, reports, policy manuals), look for user additions to forms, unused form elements
JAD sessions
Joint Application Design(JAD) allow analyst to gather requirements, analyze & design UI with users in group setting. 5-10 days over 3 weeks
Involves
: Executive sponsor, IS analyst, Users, Session leader, Observers, Scribe.
important
Facilitator --> ensures agenda, help understand terms, records input, Scribes: control times and notes, makes copies
Where to hold
:
Offsite
: Comfortable surrounding, less distractions,
Attendance
: when participants can attend, agenda, orientation meeting
Setting
: U-shape seating, no distractions, whiteboard/flipchart, prototyping tools, e-JAD
5 steps
: Select participants --> design JAD sessions --> prepare --> conduct --> post follow-up
Observation
: Check validity of info gathered, take note periodic activities however behaviors change, usually don't remember all
Interview
planned meeting to obtain info from another person, 2 types: One on One, Group
important method for collect data on human & system info requirements
reveal: interviewee opinions, feelings, Goals, Key HCI concerns
7 Steps
Selecting interviewees
: based on info needed, company formal & informal structures. Usually: managers, users.
Establish objectives for the interview
: areas to discuss, facts to gather(ideas, suggestions, opinions) & based on the role of interviewee
Designing interview questions
Open-ended questions: how they wish, what length they wish, good when analyst want breadth & depth of reply
Closed-ended: limit response, good for generate precise, reliable data, less skill for interviewer than open-ended
2 Types: + Structured: Specific info how business perform, questions developed prior for interviews, more closed-ended questions + Unstructured: broad & roughly defined info, few closed-ended questions more open-ended --> challenging interview
Bipolar questions: yes/no, agree/disagree questions, special kind of closed question
Probes to get more meaning, clarify previous questions, expand interviewee's point
Arrange Questions
Funnel: goes from general questions to specific ones, easy to start the interview
Diamond: combine pyramid & funnel, specific --> general --> specific, takes more time
Pyramid: goes from specific questions to general ones, may need to warm up interviewee
Preparing for the interview
: Reading background material --> establish interview objectives --> decide interviewee --> prepare interviewee --> decide questions types & structure --> prepare interview plan --> set priorities
Conducting the interview
: professional, record all info, understand issues and terms, facts vs opinions, allow interviewee to ask, thank interviewee, end on time. When closing ask"Is there anything you would like to add?"
Document the interview
: Interview report(ASAP, summary to detail, review with respondent)
Evaluate interview & post interview follow-up
: prepare notes, report, look for gaps and new questions
skills: plan, conduct, document, evaluate interview success
User Stories
focus from writing to talking, a series of conversions about the desired functionality
Isolated ones good when look for facts, analyst should look for stories capture all aspect of the organization
Purposes
Validating stories convince people the organization is right
Explanatory stories why organization act in a way
Experiential stories describe business/industry
Prescriptive stories tell the listener how to act
Can be used as a complement for other methods
Requirements Analysis Strategies
BPI(Business Process Improvement): duration analysis, activity-based costing, informal benchmarking
BPR(Business Process Reengineering): outcome analysis, technology analysis, activity elimination
BPA(Business Process Automation): problem analysis, root cause analysis
Select strategies based on characteristics of strategies: potential business value, project cost, breadth of analysis, risk
Fact finding
identify info needed by asking series of questions: Who, What, Where, When, How. Each questions must combine with Why?
Who?
Who performs procedures in the system?
Why? People is correct? Other people is more effective?
What?
What is being done? What procedures are being followed?
Is process necessary? why is it being followed?
Where?
where are operations being performed?
where could be? elsewhere more effective?
When?
When to performed?
Why that time? Best time?
How?
How to perform?
Why use that way? Perform in other way is better?
System analyst must understand current situation --> answer the question what should be done