Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

IS 401 > Midterm > Flashcards

Midterm Flashcards

1
Q

information systems development

A

The actual approach used to develop a particular information system - Agile development is an example of IS development.

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

iterative development

A

An approach to system development in which the system is “grown” piece by piece through iterations

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

Benefits of iterative development

A

Portions of one system can be deployed sooner, many tough problems can be addressed early in the project, by taking a small portion and developing it first, lastly, developing a system in iterations makes the entire development process much more flexible and able to address new requirements throughout the project

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

iterative

A

the six core development processes are repeated over and over again to add additional functionality to the system

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

systems analysis

A

Those activities that enable a person to understand and specify what the new system should accomplish - systems analysis = visionary. Keywords here are “understand” and “specify”, the “What”

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

Systems analysis activities

A

1) Gather Detailed Information
2) Define Requirements
3) Prioritize Requirements
4) Develop User-Interface Dialogs
5) Evaluate Requirements with User

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

systems design

A

Those activities that enable a person to define and describe in detail the system that solves the need - Keyword here is “solves”, how are you going to design the system to make sure it “Solves” your problem

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

SDLC

A

Systems Development Life Cycle

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

6 Steps of SDLC

A 
Identify problem or need
Plan resources
Discover and understand problem
Design system
Build and test components
Implement system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

activity diagram

A

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

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

client

A

Person or group that provides the funding for a system development project

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

functional requirements

A

The activities a system must perform or support and the constraints that the system must meet EX. Business Processes and rules

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

FURPS+

A 
Functionality
Usability
Reliability
Performance
Security
\+ design constraints as well as implementation, interface, physical, and supportability requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Model

A

Representation of some aspect of a system, create models after collecting information

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

Types of Models

A

Graphical Model - diagram, schematic
Textual Model - Something written down, described
Mathematical Models - formulas, statistics, algorithms

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

nonfunctional requirements

A

System characteristics other than the activities it must perform or support

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

Performance requirements

A

Operational characteristics related to measures of workload, such as throughput and response time.

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

Reliability Requirements

A

Requirements that describe system dependability

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

Security Requirements

A

Requirements that describe how access to the application will be controlled and how data will be protected during storage and transmission.

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

Stakeholders

A

Persons who have an interest in the successful implementation of the system.

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

Internal Stakeholders

A

People within the organization

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

External Stakeholders

A

People outside the organization

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

Operational Stakeholders

A

People who interact regularly with the system

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

Executive Stakeholders

A

People who don’t interact directly, but use information or have financial interest.

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

Swimlane heading

A

Activity diagram column containing all activities for a single agent or organizational unit.

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

Synchronization bar

A

Activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent paths.

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

System requirements definition

A

The activities a system must perform or support and the constraints that the system must meet.

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

Systems requirements include what two combined requirements?

A

Functional requirements and nonfunctional requirements

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

Unified modeling language

A

Standard set of model constructs and notations defined by Object Management Group

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

Usability requirements

A

Operational characteristics related to users, such as the user interface, related work procedures, online help, and documentation (ie user interface, ease of use)

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

Workflow

A

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

32
Q

Actor

A

An external agent; a person or group that interacts with the system by supplying or receiving data.

33
Q

Automation boundary

A

The boundary between the computerized portion of the application and the users who operate the application but are part of the total system. Shown in a use case diagram.

34
Q

CRUD

A

Create, Read, Update, Delete.

A technique to validate or refine use cases.

35
Q

Elementary Business Processes

A

The most fundamental tasks in a business process, which leaves the system and data in a quiescent state; usually performed by one person in response to a business event.

36
Q

Event

A

Something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system.

37
Q

Event decomposition technique

A

Starts with identifying all the business events that will cause the information system to respond, and each event leads to a use case

38
Q

External event

A

An event that occurs outside the system; usually initiated by an external agent.

39
Q

Perfect technology assumption

A

Assumption that system runs under perfect operating and technological conditions.

40
Q

State event

A

Occurs when something happens inside the system.

41
Q

System controls

A

Checks or safety procedures to protect integrity of the system and the data.

42
Q

Temporal event

A

Occurs as a result of reaching a point in time.

43
Q

Use case

A

Activity the system performs, usually in response to a request by a user.

44
Q

Type of requirements defined by use cases?

A

Functional requirements

45
Q

Pattern for naming each use case

A

Verb-noun

46
Q

Use case diagram

A

UML model used to graphically show use cases and their relationships to actors

47
Q

User goal technique

A

Identifies use cases by determining what specific goals or objectives must be completed by a user.

48
Q

Alt frame

A

Notation on a sequence diagram showing if-then-else logic

49
Q

True/False Condition

A

Shown in brackets. Part of message between objects that is evaluated prior to transmission to determine whether message can be sent.

50
Q

Lifeline

A

Dashed vertical line under object on system sequence diagram to show the passage of time for the object.

51
Q

Loop frame

A

Notation on sequence diagram showing repeating messages. A rectangle containing message and its response. Also includes rectangle at top to describe what is causing loop.

52
Q

Opt frame

A

Notation on sequence diagram showing optional messages.

53
Q

Preconditions

A

Condition that must be true before a use case begins, indicating what objects must already exist, information that must already be available, and condition of the actor prior to beginning use case.

54
Q

Postconditions

A

Conditions that must be true upon completion of use case. Indicate what new objects are created or updated by use case and how objects need to be associated.

55
Q

System sequence diagram

A

Diagram showing sequence of messages between external actor and system during use case or scenario. Shows flow of information into and out of information system.

56
Q

What kind of diagram is a system sequence diagram?

A

Interaction diagram

57
Q

Use case description

A

Textual model that lists and describes the processing detail for a use case description.

58
Q

Break-even point

A

The point in time at which dollar benefits offset dollar costs.

59
Q

Business benefits

A

The benefits that accrue to the organization; usually measured in dollars.

60
Q

Cost/benefit analysis

A

Process comparing costs and benefits to see whether investing in a new system will be beneficial.

61
Q

Critical path

A

Sequence of tasks that can’t be delayed without causing the entire project to be delayed if any task that is on a critical path slips from the schedule, the entire project is delayed.

62
Q

Detailed work schedule

A

The schedule that lists, organizes, and describes the dependencies of detailed work tasks.

63
Q

Gantt chart

A

A bar chart that portrays the schedule by the length of horizontal bars superimposed on a calendar.

64
Q

Intangible benefit

A

Benefit that accrues to an organization but that can’t be measured quantitatively or estimated accurately.

65
Q

Net present value

A

Present value of dollar benefits and dollar costs of a particular investment.

66
Q

Organizational risks

A

Risk dealing with employee worries, or structure, or loss of employment due to automation.

67
Q

Payback period

A

The time period after which the dollar benefits have offset the dollar costs.

68
Q

Project iteration schedule

A

List of iterations and use cases or user stories assigned to each iteration.

69
Q

Resource risks

A

Risk involving availability of team members, money, key skilled members being transferred or leaving.

70
Q

Schedule risks

A

Requires assumptions and estimates without adequate information.

71
Q

System capabilities

A

Required capabilities of new system. Part of System Vision Document

72
Q

System Vision Document

A

Document to help define scope of new system.

73
Q

Tangible benefit

A

Benefit that can be measured or estimated in terms of dollars.

74
Q

Technological risks

A

Risk in dealing with availability of skills or vendors lack of capability

75
Q

Users

A

Person or group of people who will use new system.

76
Q

Work breakdown structure

A

List or hierarchy of activities and tasks of a project; used to estimate the work to be done and to create a detailed work schedule.

IS 401 (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions