Please enable JavaScript.
Coggle requires JavaScript to display documents.
[Soft D] Understanding Requirements - Coggle Diagram
[Soft D] Understanding Requirements
requirements engineering
elaboration
inception
elicitation (gathering)
specification
validation
requirements management
negotiation
groundworks (inception)
identify
stakeholders
viewpoints/prespectives
marketer interested in good design
engineers interested in good architecture
nonfunctional requirement
elicitation
collaborative meeting
structured
quality function deployment
normal requirement
expected requirement
exciting requirement
requirements creep
usage scenario
prespectives
get user stories (agile)
service oriented
define all services
analogy:hotel
doorperson to open door
clerk checks guest in
bellhop manages bag
concierge assist guest
elicitation work products
list of customer/users
system technical environment
usage scenario
develop use cases
define actors
type
primary
secondary
goals
main tasks
exceptions (errors)
use case diagram
analysis model (elaboration)
requirements modeling
scenario based
user's prespective
diagrams
use case
user stories
class based
system's prespective
diagrams
uml class
behavioral based
adapter
requirements to design model
validating requirements
consistent?
proper abstraction?
prespective
technical
non technical
necessary? or add on?
unambigious?
achieveable?