Systems analysis activities
-Gather detailed info(interviews,questionnaires,observing business processes)
-Define requirements(Modelling 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
Gather detailed information
System analysts obtain information from people who will be using the system, either by interviewing them or watching them do work
Define requirements
The analysts uses info gathered from users and documents to define requirements for the new system
Prioritize requirements
Establish which requirements are most crucial for the system
Develop user
Interface dialogs
System requirements
The activities a system must perform or support and the constraints that the system must meet
-Functional requirements
-Non-functional requirements
Functional requirements
The activities the system must perform
-Business uses,functions the user carry out
Non-functional requirements
Other system characteristics
-Constraints and performance goals
FURPS(Non-functional)
-Functional requirements
-Usability requirements
-Reliability requirements
-Performance requirements
-Security requirements
Model
A representation of some aspect of the system being built
Types of models
-Textual models:something written down, described
-Graphical model-diagram, schemate
-Mathematical models-formulas,stats,algorithms
Unified modeling language
Standard graphical modeling symbols terminology used for IS
Reasons for modeling
-Learning from the modeling process
-Reducing complexity by abstraction
-Remembering all the details
-Communicating with other development team members
-Communicating with a variety of users and stakeholders
-Documenting what was done for future maintenance/enhancement
Stakeholders
Persons who have an interest in the successful implementation of the system
Types of stakeholders
-Internal stakeholders
-External stakeholders
-Operational stakeholders
-Executive stakeholders
Internal stakeholders
Persons within the org who interact with the system or have a significant interest in its operations or success
External stakeholders
Persons outside the orgs control and influence who interact with the system or have a significant interest in its operation or success
Operational stakeholders
Persons who regularly interact with the system
Executive stakeholders
Persons who don’t directly interact, but use the info or have financial interest
Information gathering techniques
-Interviewing users and other stakeholders
-Distributing and collecting questionnaires
-Reviewing inputs,outputs and documentation
-Observing and documenting business procedures
-Researching vendor solutions
-Collecting active user comments and suggestions
Interviewing users and other stakeholders
-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
Additional techniques
1)Observe and document business processes
-Watch and learn
-Document with activity diagram
2)Research vendor solutions
-See what others have done for similar situations
-White papers,vendor literature, competitors
3)Collect active user comments and suggestions
-Feedback on models and tests
-Users know it when they see it
Usability requirements
Operational characteristics related to users, such as the user interface, related work procedures,online help amd documentation
Reliability requirements
Describe the dependability of a system-how often a system exhibits such behaviours as service outages and incorrect processing and how it detects and recovers from these problems
-
Marketing Chap 136
-
Marketing Chap 219
-
Marketing Chap 342
-
Marketing chap 513
-
Marketing Chap 623
-
Marketing Chap 715
-
Marketing chap 842
-
Marketing Chapter 929
-
Marketing chap 1018
-
Marketing chap 1123
-
Marketing Chap 1228
-
Marketing Chap 1321
-
Marketing Chap 1416
-
Marketing Chap 159
-
Marketing Chap 1613
-
Systems week 140
-
Systems week 218
-
Systems week 324
-
Unit 113
-
Unit 218
-
Unit 327
-
Unit 453
-
Unit 516
-
Unit 6(1)7
-
Unit 6(2)7
-
Unit 7(1)16
-
Unit 7(2)7
-
Unit 8(1)8
-
Unit 96
-
Unit 1024
