System Analysis and Design Flashcards

(59 cards)

1
Q

A collection of activities and elements organized to accomplish goal

A

System

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

Reasons to change information systems

A

◼ Organizational growth
◼ Mergers and acquisitions
◼ New marketing opportunities
◼ Revisions in governmental regulations
◼ Availability of new technology

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

A six-phase problem-solving procedure for examining and improving information
systems

A

System analysis and design

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

System’s Life Cycle

A
  1. Preliminary investigation
  2. Systems analysis
  3. Systems design
  4. Systems development
  5. Systems implementation
  6. Systems maintenance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

the information problems or needs are identified

A

Preliminary Investigation

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

The present system is studied in depth. New requirements
are specified.

A

System Analysis

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

A new or alternative information system is designed

A

Systems design

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

New hardware and software are acquired, developed and
tested

A

Systems development

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

The new information system is installed and adapted to the
new system, and people are trained to use it

A

Systems implementation

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

In this ongoing phase, the system is periodically evaluated
and updated as needed

A

Systems Maintenance

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

Computer professionals studying an organization’s systems to determine what actions to take and how to use computer technology to assist them.

A

Systems Analysts

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

2nd top job classification after Computer Engineer (in terms of salary, prestige and security)

A

Computer Systems Analysts

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

Why it is important that end user understand how the systems life cycle works

A

▪ You may have to use the procedure
▪ More and more end users are developing their own information systems
▪ Will raise your computer competency
▪ Give you skills to solve wide range of problems
▪ Make you more valuable to an organization

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

◼ Determine the need for new information system
◼ Requested by an end user or a manager who
wants something done that is not presently
done

A

Phase 1 Preliminary Investigation

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

Three tasks Systems Analysts/End User is concerned with

A
  1. Briefly defining the problem
  2. Suggesting alternative solutions
  3. Preparing a short report
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

◼ examine whatever current information system is in use
◼ determine what information is needed, by whom, when, and why is accomplished by
interviewing and making observations
▪ Large information systems => Survey is done by a systems analysts
▪ Small information systems => Survey can be done by the end user

A

Defining the problem

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

Suggest some possible plans as alternatives to the present arrangement

A

Suggesting alternative solutions

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

The systems analyst writes a report summarizing the results of the preliminary investigation and suggesting alternative systems
▪ Report may include schedules for further development of the project.
▪ This document is presented to higher management, along with a recommendation to continue or discontinue the project
▪ Management then decide whether to finance the second phase

A

Preparing a short report

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

Problem -> Alternative -> Report -> Analysis

A

Phase 1 Preliminary Investigation

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

◼ Data is collected about the present system
▪ This data is then analyzed, and new requirements are determined
▪ Not concerned with a new design
▪ Only with determining the requirements for a new system
◼ Concerned with gathering then analyzing the data
◼ Completed by documenting the analysis in a report

A

Phase 2 Systems Analysis

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

Gather -> Analyze -> Report -> Design

A

Phase 2 systems analysis

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

◼ The systems analyst/end user doing systems analysis-expands on the data gathered during Phase 1
▪ Add details about how the current system works
◼ Data is/may be obtained
▪ Observations and interviews
▪ From questionnaires given to people using the system
▪ Studying documents that describe the formal lines of authority and standard operating procedures

A

Gathering Data

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

◼ Shows levels of management and formal lines of authority
◼ Resembles the hierarchy of three levels of management
▪ Top managers
▪ Middle managers
▪ supervisors

A

Organizational Chart

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

◼ The idea is to learn how information currently flows and to pinpoint why it isn’t flowing appropriately
◼ Apply logic to existing arrangement to see how workable it is

A

Analyzing the data

25
Analysis tools
◼ Checklists ◼ Top-down Analysis Method ◼ Grid Charts ◼ Decision Tables ◼ Systems Flowcharts ◼ Data Flow Diagrams ◼ Automated Design Tools
26
◼ A list of questions ◼ Helpful in guiding the systems analyst/end user through key issues for the present system
Checklist
27
◼ Identify the top-level components of a complex system ◼ Each component is then broken down into smaller and smaller components ▪ Makes each component easier to analyze and deal with
Top-down Analysis Method
28
◼ Shows the relationship between input and output documents
Grid charts
29
◼ Show the decision rules that apply when certain conditions occur
Decision Tables
30
◼ Show the flow of input data to processing and finally to output, or distribution of information
System flowcharts
31
◼ Show the data or information flow within the system ◼ The data is traced from its origin through processing, storage and output
Data Flow diagram
32
◼ Software packages that evaluate the hardware and software alternatives according to requirements given by the systems analyst ◼ also called Computer-Aided Software Engineering (CASE) tools ◼ These tools are not limited to system analysis ▪ Used in system design and development as well ◼ Relieve the systems analysts of many repetitive tasks ◼ Develop clear documentation, ◼ Coordinate team member activities (for larger projects)
Automated Design Tools
33
◼ Systems analysis report describes - the current information system - the requirements for a new system - a possible development schedule
Documenting Systems Analysis
34
Consist of 3 tasks ◼ Designing alternative systems ◼ Selecting the best system ◼ Writing a systems design report
Phase 3: Systems Design
35
Feasibility ◼ Economic feasibility ◼ Technical feasibility ◼ Operational feasibility
Designing Alternative Systems
36
◼ Will the cost of the new system by the benefits it promises ◼ How long will it take for the new system to pay for itself
Economic feasibility
37
◼ Are reliable hardware, software, and training available to make the system work? ◼ If not, can they be obtained?
Technical feasibility
38
◼ Can the system actually be made to operate in the organization, or will people – employees, managers, clients – resist it?
Operational Feasibility
39
Managers must consider these four questions ◼ Will the system fit in with the organization’s overall information system? ◼ Will the system be flexible enough so it can be modified in the future? ◼ Can it be made secure against unauthorized use? ◼ Are the benefits worth the costs?
Selecting the best system
40
◼ Is prepared for higher management and describes the alternative designs ◼ Presents the costs versus the benefits and outlines the effect of alternative designs on the organization ◼ Usually concludes by recommending one of the alternatives
Writing a systems design report
41
3 steps ◼ Acquiring software ◼ Acquiring hardware ◼ Testing the new system
Phase 4: Systems Development
42
2 ways to obtain application software ◼ Purchased as off-the-shelf software and possibly modified ◼ Custom designed
Acquiring Software
43
◼ The equipment needed and the places where they are to be installed must be determined ▪ a very critical area ◼ Switching or upgrading equipment can be tremendously expensive proposition ▪ Will a computer system be sufficient as a company grows? ▪ Are networks expandable? ▪ Will people have to undergo costly training?
Acquiring hardware
44
◼ After the software and equipment have been installed, the system should be tested. ◼ Sample data is fed into the system. ◼ The processed information is then evaluated to see whether results are correct. ◼ Testing may take several months if the new system is complex.
Testing the new system
45
Another name for Phase 5
Conversion
46
◼ Direct Approach ◼ Parallel Approach ◼ Pilot Approach ◼ Phased Approach
Types of Conversion
47
Types of Conversion
◼ Direct Approach ◼ Parallel Approach ◼ Pilot Approach ◼ Phased Approach
48
- Abandon the old - Very risky; not recommended
Direct Approach
49
- Run old and new side by side - Very low risk; however, very expensive; not generally recommended
Parallel Approach
50
- Convert part of organization first - Less expensive but riskier than parallel conversion; recommended for situations that many people performing similar operations
Pilot Approach
51
- Implement gradually - Less risky but more expensive than parallel conversion; Recommended for situations with many people performing different operations
Phased Approach
52
◼ Training people is important ◼ One of the most commonly overlooked activities
Training
53
◼ Very important, ongoing activity ◼ Most organization spend more time and money on this phase than on any of the others.
Phase 6: Systems Maintenance
54
2 parts of systems maintenance
◼ Systems Audit ◼ Periodic Evaluation
55
◼ The system’s performance is compared to the original design specifications ▪ To determine whether the new procedures are actually furthering productivity ▪ If they are not, some redesign may be necessary
Systems Audit
56
◼ After the systems audit, the new information system is further modified, if necessary. ◼ All systems should be evaluated from time to time ▪ to determine whether they are ▪ meeting the goals ▪ providing the service they are supposed to
Systems Evaluation
57
Alternative Approaches that require much less time
◼ Prototyping ◼ Rapid Applications Development
58
◼ Means building a model or prototype that can be modified before the actual system is installed ◼ Users would try it out and provide feedback to the systems analyst ◼ The systems analyst would revise the prototype until the users felt it was ready to put into place.
Prototyping
59
◼ Involves the use of powerful development software, small specialized teams, and highly trained personnel.
Rapid Applications Development