2. EITHER WE
BUILD THE WRONG THINGS OR
BUILD THE THINGS WRONG
LEARN BEFORE YOU DIVE IN
SYSTEM ANALYST ROLES & RESPONSIBILITIES
3. ACTIVITIES
Activities Details
Collect Details
Information
Q&A, Observing Data, Process etc. Flow in and out, Relationships, Resource Allocation &
Limitation between point to point users involves
Define
Requirements
Design Model for Functional & Non Functional Requirements
[?]
Prioritize
Requirements
Categorized Task, Activities in RF, RNF in order by Essential, Important, Nice to have
(Extended)
Develop UI
Dialogs
Mapping Flow as Ref of Human Computer Interaction
Evaluate
Requirements
Create Scenario, Get user/s involve, get/set feedback as Accepted Criteria
4. GATHERED
DETAILS INFORMATION
About Industry, Product,
Market, Processes, Data, Relationships, Resource
and Limit
About Voice/Users(Who Uses so Frequent, not
so often, have interest, indirect, Management,
Owner)
* your view must be clients or users view not Analyst/Developer View
Techniques
• Interview Users & All Stake Holders
• Distribution & Collections Q&A
• Review Input, Output & Documents
• Observe Business Process and Document it
• Research Vendor Existing System
• Collect User Comments and Suggestion
• Web Scrawling Techniques Like Python
facilitated
5. STAKE HOLDERS
Not too big and not to small is best fit for group
Internal – persons within the organization
External – persons outside the organization
Operational – persons who regularly interact with the
system
Executive – persons who don’t directly interact, but use
the information or have financial interest Persons who
have an interest in the successful implementation of the
system
Stake Holder Like
Book keepers
Accountants
Sales Executive
Internal Auditors
Stake Holder Like
Suppliers or Vendor
Customers
Stake Holder Like
Product Manager
Head of Business
Board Of Directors
Owners
Stake Holder Like
Investors
Regulators
Internal
External
Operational Executive
6. INTERVIEW
• Prepare Questions (Close & Narrative Questions)
• Meet (Individual and Group of Users) or Distribute over Internet
• Discuss answer to the questions to obtain actual question to
answer
• Summarize the answers and document it Standard Way
• Follow-up, Repeat the whole process as needed
Its best the survey to Prepare users reachable online survey
forms, don’t forget to put some score or remuneration for the
users are involve
Users & All Others Stakeholders
7. MODELLING
Event List to be perform
• Event list let's assume
• Buy a Vehicle
• Sell a vehicle
• Get vehicle services
• Resale vehicle
Functional & Non-Functional Requirement
You can use
Use case Diagram
Business Process Diagram
User Activities Diagram
Storyboard
Functions
or actionsEvents
Properties
Event Handler
Task
Buy
Events
Properties
Handler
Sell
Events
Properties
Handler
Service
Events
Properties
Handler
Define Object wise functional which consist of events,
properties and handler as a parameter
Define FunctionalRequirements
8. MODELLING
Functional & Non-Functional Requirement
Define Non-Functional
Requirements
Usability
• Ease
• Failure Rate
Relaibility
• Accuracy, Recovery
Methods
Performance
• Response Time
• Data Trips with
Formats, Size etc
Security
• Access Control
• Encryption Hardware
9. PRIORITIZE
ESSENTIAL-IMPORTANT-EXTEND (NICE TO HAVE)
Task Priority
Level
%
Status
Due
Date
Assign To Task Type
Event ID: #
Name: ""
High 50% DD-MM-
YY
hh:mm
Team Id:# Functional
Event ID: #
Name: ""
High 50% DD-MM-
YY
hh:mm
Team Id:# Non
Functional
A Complete List of Excel Prioritize Templates for you
11. ACCEPTED
CRITERIA
Observe Different events either its functional or non-
functional and Collect each events flows and document the
event properties and behavior and finally
Match the active users
current feedback and actual
requirements
This is the major questions of all: Did we build the wrong thing or the thing wrong, To Better understand use some basic formation or framework to evaluate it
You must put users shoes to see yourself how its fits for better view to the problems
You must put users shoes to see yourself how its fits for better view to the problems
You must put users shoes to see yourself how it fits for better view to the problems
Author
Md Masududzaman Khan
Head of Information technology & Chief Technical Officer
A3IT Bangladesh
Special Thanks to Natalie Moore