Ch2 Flashcards

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

A

Stakeholders

23
Q

persons within the organization

A

Internal Stakeholders

24
Q

persons outside the organization

A

External stakeholders

25
Q

persons who regularly interact with the system

A

Operational stakeholders

26
Q

persons who don’t directly interact, but use the information or have financial interest

A

Executive stakeholders

27
Q

Information Gathering Techniques

A

•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
Q

Interviewing Users and Other Stakeholders

A

•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
Q

Additional Techniques in Gathering information

A

•Observe and Document Business Processes
•Research Vendor Solutions
•Collect Active User Comments and Suggestions

30
Q

Observe and Document Business Processes

A

Watch and learn
Document with Activity diagram

31
Q

Research Vendor Solutions

A

See what others have done for similar situations
White papers, vendor literature, competitors

32
Q

Collect Active User Comments and Suggestions

A

Feedback on models and tests
Users know it when the see it

33
Q

a representation of some aspect of the system being built

A

Model

34
Q

Types of Models

A

•Textual model
•Graphical models
•Mathematical models

35
Q

something written down, described

A

Textual model

36
Q

diagram, schematic

A

Graphical models

37
Q

formulas, statistics, algorithms

A

Mathematical models

38
Q

Standard graphical modeling symbols/terminology used for information systems

A

Unified Modeling Language (UML)

39
Q

Reasons for Modeling

A

•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
Q

Evant and use case description watch type of Model?

A

Textual

41
Q

Use case diagram watch type of Model?

A

Graphical models

42
Q

Location diagram, class diagram, sequence diagram, communication diagram, state machine diagram

watch type of Model?

A

Mathematical models

43
Q

sequence of processing steps that completely handles one business transaction or customer request

A

Workflow

44
Q

describes user (or system) activities, the person who does each activity, and the sequential flow of these activities

A

Activity Diagram

45
Q

Systems analysis activates correspond to the core SDLC process

A

Discover and understand details