Ch2 Flashcards
the set of computing hardware, network hardware and topology, and system software employed by the organization
Technology architecture
the information systems that supports the organization (information systems, subsystems, and supporting technology)
Application architecture
Systems Analysis Activities
1-Gather detailed information
2- Define requirements
3- Prioritize requirement
4-Develop user-interface dialogs
5- Evaluate requirements
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
System Requirements =
Functional requirements
Non-functional requirements
the activities the system must perform
Functional Requirements
Business uses, functions the users carry out
Functional requirement
system characteristics
Constraints and performance goals
Non-Functional Requirements
FURPS
Functional requirements Usability requirements Reliability requirements Performance requirements Security requirements
Functional
Business rules and processes
Non- functional
Usability: user interface , ease of use
Reliability: Failure rate,recovery methods
Performance: Response time, throughput
Security:Access controls, encryption
Additional Requirements Categories
•Design constraints
•Implementation requirements
•Interface requirements
•Physical requirements
•Supportability requirements
Specific restrictions for hardware and software
Design constraints
Specific languages, tools, protocols, etc.
Implementation requirements
Interface links to other systems
Interface requirements
Physical facilities and equipment constraints
Physical requirements
Automatic updates and enhancement methods
Supportability requirements
persons who have an interest in the successful implementation of the system
Stakeholders
persons within the organization
Internal Stakeholders
persons outside the organization
External stakeholders
persons who regularly interact with the system
Operational stakeholders
persons who don’t directly interact, but use the information or have financial interest
Executive stakeholders
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 in Gathering information
•Observe and Document Business Processes
•Research Vendor Solutions
•Collect Active User Comments and Suggestions
Observe and Document Business Processes
Watch and learn
Document with Activity diagram
Research Vendor Solutions
See what others have done for similar situations
White papers, vendor literature, competitors
Collect Active User Comments and Suggestions
Feedback on models and tests
Users know it when the see it
a representation of some aspect of the system being built
Model
Types of Models
•Textual model
•Graphical models
•Mathematical models
something written down, described
Textual model
diagram, schematic
Graphical models
formulas, statistics, algorithms
Mathematical models
Standard graphical modeling symbols/terminology used for information systems
Unified Modeling Language (UML)
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
Evant and use case description watch type of Model?
Textual
Use case diagram watch type of Model?
Graphical models
Location diagram, class diagram, sequence diagram, communication diagram, state machine diagram
watch type of Model?
Mathematical models
sequence of processing steps that completely handles one business transaction or customer request
Workflow
describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
Activity Diagram
Systems analysis activates correspond to the core SDLC process
Discover and understand details
