Accounting Information Systems: 9 Edition
Accounting Information Systems: 9 Edition
Accounting Information Systems: 9 Edition
9th Edition
Marshall B. Romney Paul John Steinbart
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-1
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-2
Learning Objectives
1.
1.
1.
Explain the five phases of the systems development life cycle. Discuss the people involved in systems development and the roles they play. Explain the importance of systems development planning and describe planning techniques.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-3
Learning Objectives
4.
1.
1.
Discuss the various types of feasibility analysis, and calculate economic feasibility. Explain why systems change triggers behavioral reactions, what form this resistance to change takes, and how to avoid or minimize the resulting problems. Discuss the key issues and steps in systems analysis.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-4
Introduction
Ann Christy was promoted to controller of Shoppers Mart (SM). She determined the following:
Store
managers cannot obtain information other than what is contained on SMs periodic, preformatted reports. The sales and purchasing departments cannot get timely information about what products are or are not selling well.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-5
Introduction
Ann is convinced that Shoppers Mart needs a new information system. She has the following questions:
1.
2.
What process must the company go through to obtain and implement a new system? What types of planning are necessary to ensure the systems success?
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-6
Introduction
3. 4.
5.
How will employees react to a new system? How should the new system be justified and sold to top management? How can expected costs and benefits be quantified to determine whether the new system will indeed be costeffective?
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-7
Introduction
first topic is the system development life cycle (Objective 1). The second topic is the planning activities that are necessary during the development of the life cycle (Objectives 2 and 3). The third topic is the process of demonstrating the feasibility of a new AIS (Objective 4).
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-8
Introduction
The
fourth topic is the behavioral aspects of change that companies must deal with to successfully implement a new system (Objective 5). The last topic is a discussion of systems analysis, the first step in the development cycle (Objective 6).
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-9
Learning Objective 1
Explain the five phases of the systems development life cycle.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-10
What are the five steps in the systems development life cycle (SDLC)?
1. 1. 1. 1. 1.
Systems analysis Conceptual design Physical design Implementation and conversion Operations and maintenance
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-11
Conceptual Design
16-12
Physical Design
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-13
16-14
Life
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-15
Life
Feasibility analysis and decision points: Economic Feasibility Technical Feasibility Legal Feasibility Scheduling Feasibility Operational Feasibility
16-16
Learning Objective 2
Discuss the people involved in systems development and the roles they play.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-17
The Players
Management Accountants Information systems steering committee Project development team Systems analysts and programmers External players
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-18
The Players
providing support and encouragement establishing system goals and objectives determine information requirements
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-19
The Players
determine their information needs may be members of the project development team play an active role in designing system controls
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-20
The Players
set policies that govern the AIS ensures top-management participation guidance and control facilitates coordination and integration of IS activities
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-21
The Players
plan each project monitor project make sure proper consideration is given to the human element
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-22
The Players
study existing systems design new systems and prepare specifications write computer programs
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-23
Learning Objective 3
Explain the importance of systems development planning and describe planning techniques.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-24
16-25
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-26
Planning Techniques
Two techniques for scheduling and monitoring systems development activities are:
1
Gantt chart
A bar chart with project activities listed on the lefthand side and units of time across the top
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-27
16-28
Learning Objective 4
Discuss the various types of feasibility analysis, and calculate economic feasibility.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-29
Feasibility Analysis
Systems analysis is the first step in the systems development life cycle (SDLC). A feasibility study (also called a business case) is prepared during systems analysis and updated as necessary during the remaining steps in the SDLC. The steering committee uses the study to decide whether to terminate a project, proceed unconditionally, or proceed conditionally.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-30
Feasibility Analysis
Technical feasibility Operational feasibility Legal feasibility Scheduling feasibility Economic feasibility
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-31
Feasibility Analysis
Economic feasibility is the most frequently analyzed of the five aspects. What is the basic framework for feasibility analysis?
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-32
Feasibility Analysis
payback period net present value (NPV) internal rate of return (IRR)
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-33
Learning Objective 5
Explain why systems change triggers behavioral reactions, what form this resistance to change takes, and how to avoid or minimize the resulting problem.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-34
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-35
personal characteristics and background manner in which change is introduced experience with prior changes communication disruptive nature of the change process fear
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-36
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-37
meet needs of the users keep communication lines open maintain a safe and open atmosphere obtain management support allay fears solicit user participation make sure users understand the system
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-38
provide honest feedback humanize the system describe new challenges and opportunities reexamine performance evaluation test the systems integrity avoid emotionalism present the system in the proper context control the users expectations keep the system simple
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-39
Learning Objective 6
Discuss the key issues and steps in systems analysis.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-40
Systems Analysis
When a new or improved system is needed, a written request for systems development is prepared. The request describes the current systems problems, why the change is needed, and the proposed systems goals and objectives. It also describes the anticipated benefits and costs.
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-41
Systems Analysis
Initial investigation Systems survey Feasibility study Information needs and systems requirements Systems analysis report
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-42
Case Conclusion
that the corporate office would gather daily sales data from each store
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-43
End of Chapter 16
2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart
16-44