Chapter 1 - TERMS Flashcards
System analyst
Systems analysts must understand how to apply technology to solve business problems. Skills: technical, business, analytical, interpersonal, management, and ethical.
System development life cycle (SDLC)
Idé -> Planering -> Analys -> Design -> Implementering -> System success
Project initiation
During project initiation, the system’s business value to the organization is identified—how will it lower costs or increase revenues?
System request (planning)
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.
Analysis phase
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.
Analysis Strategy
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).
System proposal (analysis)
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.
Feasibility analysis
■ 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?)
Approval committee
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.
Design strategy
This clarifies whether the system will be developed by the company’s own programmers, whether its development will be outsourced to another firm.
Architecture design
The system that describes the hardware, software, and network infrastructure that will be used.
Interface design
Specifies how the users will move through the system.
Database and file specifications
These define exactly what data will be stored and where they will be stored.
Program design
The programs that need to be written and exactly what each program will do.
Construction within implementation
The system is built and tested to ensure that it performs as designed.
Installation
Installation is the process by which the old system is turned off and the new one is turned on.
Support plan
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.
Business process management (BPM) (implementation)
BPM is a methodology used by organizations to continuously improve end-to-end business processes. “Process optimization process”
- defining and mapping the steps in a business process,
- creating ways to improve on steps in the process that add value,
- finding ways to eliminate or consolidate steps in the process that don’t add value,
- creating or adjusting electronic workflows to match the improved process maps.
Business process automation
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.
Business Process Reenginering
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.
Operational costs
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.
Tangible benefits
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.
Intangible benefits
Subjective benefits that cannot be measured in monetary terms.
Example is faster checkout times on websites.
Champion
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.
Stakeholder
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.
System users
They will use the system once it has been installed in the organization.
Project management
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.
Requirements gathering
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.
Break down planning in phases
- Project initiation
- System request
- Feasibility analysis
- Project management
Break down analysis in phases
- Analysis phase
- Analysis strategy
- Requirements gathering
- System proposal
Break down design in phases
- Design strategy
- Architecture design
- Database and file specification
- Program design
Break down implementation in phases
- Construction
- Installation
- Support plan
System specifications
Architecture design, interface design, database
and file specifications, and program design
Business process Improvement
Studying the business processes, creating new, redesigned processes to improve the
process workflows, and/or utilizing new technologies enabling new process structures.
