Ch2 Flashcards

(45 cards)

1
Q

the set of computing hardware, network hardware and topology, and system software employed by the organization

A

Technology architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

the information systems that supports the organization (information systems, subsystems, and supporting technology)

A

Application architecture

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Systems Analysis Activities

A

1-Gather detailed information
2- Define requirements
3- Prioritize requirement
4-Develop user-interface dialogs
5- Evaluate requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Gather Detailed Information

A

Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Define Requirements

A

Modeling functional requirements and non-functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Prioritize Requirements

A

Essential, important, vs. nice to have

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Develop User-Interface Dialogs

A

Flow of interaction between user and system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Evaluate Requirements with Users

A

User involvement, feedback, adapt to changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

System Requirements =

A

Functional requirements
Non-functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

the activities the system must perform

A

Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Business uses, functions the users carry out

A

Functional requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

system characteristics
Constraints and performance goals

A

Non-Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

FURPS

A

Functional requirements Usability requirements Reliability requirements Performance requirements Security requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Functional

A

Business rules and processes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Non- functional

A

Usability: user interface , ease of use
Reliability: Failure rate,recovery methods
Performance: Response time, throughput
Security:Access controls, encryption

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Additional Requirements Categories

A

•Design constraints
•Implementation requirements
•Interface requirements
•Physical requirements
•Supportability requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Specific restrictions for hardware and software

A

Design constraints

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Specific languages, tools, protocols, etc.

A

Implementation requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Interface links to other systems

A

Interface requirements

20
Q

Physical facilities and equipment constraints

A

Physical requirements

21
Q

Automatic updates and enhancement methods

A

Supportability requirements

22
Q

persons who have an interest in the successful implementation of the system

23
Q

persons within the organization

A

Internal Stakeholders

24
Q

persons outside the organization

A

External stakeholders

25
persons who regularly interact with the system
Operational stakeholders
26
persons who don’t directly interact, but use the information or have financial interest
Executive stakeholders
27
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
28
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
29
Additional Techniques in Gathering information
•Observe and Document Business Processes •Research Vendor Solutions •Collect Active User Comments and Suggestions
30
Observe and Document Business Processes
Watch and learn Document with Activity diagram
31
Research Vendor Solutions
See what others have done for similar situations White papers, vendor literature, competitors
32
Collect Active User Comments and Suggestions
Feedback on models and tests Users know it when the see it
33
a representation of some aspect of the system being built
Model
34
Types of Models
•Textual model •Graphical models •Mathematical models
35
something written down, described
Textual model
36
diagram, schematic
Graphical models
37
formulas, statistics, algorithms
Mathematical models
38
Standard graphical modeling symbols/terminology used for information systems
Unified Modeling Language (UML)
39
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
40
Evant and use case description watch type of Model?
Textual
41
Use case diagram watch type of Model?
Graphical models
42
Location diagram, class diagram, sequence diagram, communication diagram, state machine diagram watch type of Model?
Mathematical models
43
sequence of processing steps that completely handles one business transaction or customer request
Workflow
44
describes user (or system) activities, the person who does each activity, and the sequential flow of these activities
Activity Diagram
45
Systems analysis activates correspond to the core SDLC process
Discover and understand details