Chapter 1 - TERMS

Question 1

System analyst

Answer 1

Systems analysts must understand how to apply technology to solve business problems. Skills: technical, business, analytical, interpersonal, management, and ethical.

Question 2

System development life cycle (SDLC)

Answer 2

Idé -> Planering -> Analys -> Design -> Implementering -> System success

Question 3

Project initiation

Answer 3

During project initiation, the system’s business value to the organization is identified—how will it lower costs or increase revenues?

Question 4

System request (planning)

Answer 4

A system request presents a
brief summary of a business need, and it explains how a system that supports the
need will create business value.

Question 5

Analysis phase

Answer 5

The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used.

Question 6

Analysis Strategy

Answer 6

An analysis strategy is developed to guide the project team’s efforts. Such a strategy usually includes a study of the current system (called the as-is system) and its problems, and envisioning ways to design a new system (called the to-be system).

Question 7

System proposal (analysis)

Answer 7

The analyses, system concept, and models are combined into a document called the system proposal, which is presented to the project sponsor and other key decision makers (e.g., members of the approval committee) who will decide whether the project should continue to move forward.

Question 8

Feasibility analysis

Answer 8

■ The technical feasibility (Can we build it?)
■ The economic feasibility (Will it provide business value?)
■ The organizational feasibility (If we build it, will it be used?)

Question 9

Approval committee

Answer 9

The system request and feasibility analysis are presented to an information systems approval committee (sometimes called a steering committee), which decides whether the project should be undertaken.

Question 10

Design strategy

Answer 10

This clarifies whether the system will be developed by the company’s own programmers, whether its development will be outsourced to another firm.

Question 11

Architecture design

Answer 11

The system that describes the hardware, software, and network infrastructure that will be used.

Question 12

Interface design

Answer 12

Specifies how the users will move through the system.

Question 13

Database and file specifications

Answer 13

These define exactly what data will be stored and where they will be stored.

Question 14

Program design

Answer 14

The programs that need to be written and exactly what each program will do.

Question 15

Construction within implementation

Answer 15

The system is built and tested to ensure that it performs as designed.

Question 16

Installation

Answer 16

Installation is the process by which the old system is turned off and the new one is turned on.

Question 17

Support plan

Answer 17

This plan usually includes a formal or informal post-implementation review, as well as a systematic way for identifying major and minor changes needed for the system.

Question 18

Business process management (BPM) (implementation)

Answer 18

BPM is a methodology used by organizations to continuously improve end-to-end business processes. “Process optimization process”

1. defining and mapping the steps in a business process,
2. creating ways to improve on steps in the process that add value,
3. finding ways to eliminate or consolidate steps in the process that don’t add value,
4. creating or adjusting electronic workflows to match the improved process maps.

Question 19

Business process automation

Answer 19

BPA the automation of business processes
Technology components
are used to complement or substitute for manual information management
processes with the intent of gaining cost efficiencies.

Question 20

Business Process Reenginering

Answer 20

BPR means changing the fundamental way in which the organization operates—“destroying” the current way of doing business and making major changes to take advantage of new ideas and new technology.

Question 21

Operational costs

Answer 21

The tangible costs that are required to operate the system, such as the salaries for operations staff, software licensing fees, equipment upgrades.

Operational costs are usually thought of as ongoing costs.

Question 22

Tangible benefits

Answer 22

It includes revenue that the system enables the organization to collect, such as increased sales. In addition, the system may enable the organization to avoid certain costs, leading to another type of tangible benefit: cost savings.

Question 23

Intangible benefits

Answer 23

Subjective benefits that cannot be measured in monetary terms.

Example is faster checkout times on websites.

Question 24

Champion

Answer 24

The champion is a high-level executive and is usually, but not always, the project sponsor who created the system request.

The champion supports the project by providing time and resources.

Person som brinner för projektet.

Question 25

Stakeholder

Answer 25

A stakeholder is a person, group, or organization that can affect (or can be affected by) a new system. In general, the most important stakeholders in the introduction of a new system are the project champion.

Question 26

System users

Answer 26

They will use the system once it has been installed in the organization.

Question 27

Project management

Answer 27

Once the project is approved, it enters project management. During project
management, the project manager creates a work plan, staffs the project, and
puts techniques in place to help the project team control and direct the project
through the entire SDLC.

Question 28

Requirements gathering

Answer 28

Information gathered from interviews, group workshops,
or questionnaires —in conjunction with
input from the project sponsor and many other people—leads to the development
of a concept for a new system.

Question 29

Break down planning in phases

Answer 29

1. Project initiation
2. System request
3. Feasibility analysis
4. Project management

Question 30

Break down analysis in phases

Answer 30

1. Analysis phase
2. Analysis strategy
3. Requirements gathering
4. System proposal

Question 31

Break down design in phases

Answer 31

1. Design strategy
2. Architecture design
3. Database and file specification
4. Program design

Question 32

Break down implementation in phases

Answer 32

1. Construction
2. Installation
3. Support plan

Question 33

System specifications

Answer 33

Architecture design, interface design, database

and file specifications, and program design

Question 34

Business process Improvement

Answer 34

Studying the business processes, creating new, redesigned processes to improve the
process workflows, and/or utilizing new technologies enabling new process structures.