Please enable JavaScript.
Coggle requires JavaScript to display documents.
REQUIREMENTS ENGINEERING (requirements elicitation) (interviewing users…
REQUIREMENTS ENGINEERING
(requirements elicitation)
interviewing users and stakeholders
prepare details q
open ended q
encourage discussion n explanation
close ended q
get specific facts
meet w individuals/groups of users
obtain discuss ans to d q
doc the answes
followup as needed in future meetings or interview
distributing n collecting questionnaires
collect info from large num of stakeholders
xsesuai for faham buss process,workflows,teknik
creativity - brainstorming(CPRE)
variations of brainstorming
classical
Moderator initiates ideas and leads discussion to assess the ideas.
variations
Participants initiate ideas and gathered by the moderator. Moderator provides criteria for appraisal, later appraised by the participants on group level
brainstorming paradox
determine unwanted things to happen n preventions
change of perspective
participants take diff viewpoints
eg:six thinking hats(green,re,black,white,yelllow,blue)
analogy
hidden(participants know only analogy)
open(participants know real prob and analogy)
reviewing input,output,procedures(CPRE)
observing and documenting business procedures(CPRE)
watch n learn buss process
fhm buss process n see how to improve
doc w activity diagram
apprenticing
executing end user works under their supervisions
researching vendor solutions
(many vendors have solved problems)
use existing knowledge/solutions
tgk wht others have done for same situations
adv
generate new ideas(hw to perform buss functions better)
reduce likehood of dev obdelete sys)
less risky to buy solution)
collecting active user comments and suggestions
recall sys dev across multiple iterations
feedback from models n tests - prototyping
users x able give complete n accurate during interview,discussion,model review. they know when they see it