Modern Systems Analysis And Design Ch 7

Front 1

1) Streamlining Processes
2) Minimizing Waste
3) Process Reengineering
4) Introducing Automation

Back 1

Ways to make the system more efficient

Front 2

Identify the need, study feasibility, define the scope of the system, and allocate the resources

Back 2

Phase 1: System Planning

Front 3

Study the existing system, determine requirements, structure those requirements, create alternative designs, and then select the best alternative

Back 3

Phase 2: System Analysis

Front 4

Convert the recommended solution from systems analysis into logical and physical specifications

Back 4

Phase 3: System Design

Front 5

Get required hardware/software, write the code, test the code, train users, operation, and maintenance

Back 5

Phase 4: System Implementation and Operation

Front 6

Users, reports, forms, and procedures

Back 6

Sources of information for determining requirements

Front 7

Joint Application Design (JAD), Group Support Systems (GSS), CASE tools, Prototyping

Back 7

Modern Methods for determining requirements

Front 8

Business Process Reengineering (BPR), Disruptive Technologies

Back 8

Radical Methods for determining requirements

Front 9

No pre-specified answers

Back 9

Open Ended Questions

Front 10

Multiple choice

Back 10

Closed ended questions

Front 11

Valid, reliable, easy to use

Back 11

Characteristics of good questionairres

Front 12

Mostly closed ended questions
Can be administered via email or over phone

Back 12

Questionairres

Front 13

Cost more but gain more information

Back 13

Interviews

Front 14

Supplements interviews
Obtain first hand knowledge
Difficult to get unbiased data

Back 14

Direct observation

Front 15

Reports
Work Procedures
Policies
Documentation of current system
Business forms

Back 15

Types of documents to be examined

Front 16

1) Problems with the existing system
2) Opportunities to meet a new need
3) Direction for organization
4) Names of big shots
5) Organization's values
6) Special circumstances in information processing
7) Rules for data processing

Back 16

Information discovered from documentation

Front 17

1) Brings together key users
2) Collects system requirements simultaneously from these users
3) Is conducted offsite

Back 17

Joint Application Design (JAD)

Front 18

Repetitive process in which a rudimentary version of the system is built to develop concrete specifications for THE ULTIMATE SYSTEM! Replaces or augments SDLC

Back 18

Prototyping

Front 19

1) Session Leader
2) Users
3) Managers
4) Sponsor
5) Systems Analysts
6) Scribe
7) IS Staff

Back 19

Participants in JAD

Front 20

1) Meeting can be difficult to manage
2) A few participants may dominate the meeting
3) Personal styles and political issues influence participation
4) It's expensive

Back 20

Disadvantages of JAD

Front 21

1) User requests are not clear
2) Few users are involved in the system
3) Designs are complex and require concrete form
4) There is a history of communication problems between analysts and users
5) The tools are easily available to build the prototype

Back 21

Times when prototyping is useful

Front 22

1) Avoids formal documentation
2) Difficult to adapt to a more general user audience
3) Sharing data with other systems may not be considered
4) SDLC checks are often bypassed

Back 22

Drawbacks of prototyping

Front 23

Search for and implement radical change in a business to achieve breakthrough improvements in products and services

Back 23

Business Process Reengineering (BPR)

Front 24

Technologies that enable the breaking of business rules that are slowing down an organization from making radical changes

Back 24

Disruptive technologies

Front 25

1) Reduces the length of analysis and design phases
2) Reduces cost of system development by correctly defining and prioritizing system requirements
3) Increases the user satisfaction with the system
4) You now have a document of the existing system and features of the proposed systems

Back 25

Results of JAD

Front 26

1) Reorganize the flow of data in major sections of an organization
2) Eliminate unnecessary steps
3) Combine steps
4) Become more responsive to future change
5) Reduce work force needed
6) Build customer relationships
7) Increase efficiency and profits

Back 26

Goals of BPR

Front 27

1) Shortened development time
2) Increased user participation and satisfaction
3) Developed concrete specifications for ultimate system (but do not build it)

Back 27

Goals of prototyping

Front 28

Interviews with individuals or groups, questionairres, observing users, business document and procedure analysis

Back 28

Traditional methods for determining requirements

Front 29

Making this system more efficient and helping managers to make better decisions

Back 29

The job of a systems analyst

Front 30

Relaxation of Constraints
Attention to detail
Reframing: view in new ways
Impertinence: question everything
Impartiality: find the best solution for the organization

Back 30

Requirements for information gathering