Systems Analysis & Modelling
|
Gather detailed information
|
Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions
|
|
Define requirements
|
Modeling functional requirements and non-functional requirements
|
|
Prioritize requirements
|
Essential, important, vs. nice to have
|
|
Develop user interface dialogs
|
Flow of interaction between user and system
|
|
Evaluate requirements with users
|
User involvement, feedback, adapt to changes
|
|
Interviewing users and other stakeholders
|
|
Distributing and collecting questionnaires
|
|
Review inputs, outputs, and doc
|
|
Observe & document business processes
|
|
Research vendor solutions
|
|
Collectt active user comment / suggestions
|
|
Functional Requirements
|
– the activities the system must perform. Business uses and functions system must carry out
|
|
Non-Functional Requirements
|
Other system characteristics. Constraints and performance goals.
|
|
Prepare detailed questions
|
|
Meet with individuals or groups of users
|
|
Obtain and discuss answers to the questions
|
|
Document the answers
|
|
Follow up as needed in future meetings or interviews
|
No comments yet.
Cheatography n. The art of mapping complex subjects into clear, instantly navigable reference guides.
