기업과 정보 (Management Information Systems)
Building
Information Systems
Chapter 13
기업과 정보 (Management Information Systems)
Systems as Planned Organizational Change
• BPR(Business Process Reengineering) and Systems Development : Ford’s BPR
• Employees in accounting dept: 75% reduced (500 → 125)
• Errors reduced: manual comparisons 14 → 3
• Correct inventory information available.
Copy of Request to
order Invoice
Suppliers Inventory
Accounting Dept
Supplies Receipt
Payment Request to Order
Purchasing Dept
Purch Dept Supplier
Inventory Supplies Request to order
Acct dept Payment No receipt, no invoice
Chapter 13: Building Information Systems
기업과 정보 (Management Information Systems)
Systems as Planned Organizational Change
Organizational Change Carries Risks and Rewards
Figure 13-1
• Most common organizational changes are automation and rationalization (conversion to follow general rules. E.g.
standardization).
• These present modest returns but little risk.
• More comprehensive change
—reengineering or paradigm shifts — carries high rewards but very risky.
Chapter 13: Building Information Systems
PI (BPM, TQM, ..)
BPR PI 1 time
continuous B
Return
(ex. 자동화)(ex. 표준화) (ex. BPR)
(ex. 공유경제)
Risk
Management Information Systems, Global Edition기업과 정보 (Management Information Systems)
Systems as Planned Organizational Change
AS-IS BUSINESS PROCESS FOR PURCHASING A BOOK FROM A PHYSICAL BOOKSTORE Chapter 13: Building Information Systems
기업과 정보 (Management Information Systems) REDESIGNED PROCESS FOR PURCHASING A BOOK ONLINE
REDESIGNED PROCESS FOR PURCHASING A BOOK ONLINE
FIGURE 13-3
Chapter 13: Building Information Systems
기업과 정보 (Management Information Systems)
THE SYSTEMS DEVELOPMENT PROCESS
Systems Development Life Cycle (SDLC)
• System Development
• Producing an IS to solve organizational problems
• Planning
• Determine the goal and scope of the project
• Feasibility study: organizational, financial, and technical feasibilities
• Systems Analysis (What)
• Produces functional and
informational requirements to solve the problems
• System analysts and end users work together
Chapter 13: Building Information Systems
Management Information Systems, Global Edition기업과 정보 (Management Information Systems)
Overview of Systems Development
• Systems design (How)
• Produces the detailed specification of the target system (system design) that fulfill the requirements.
• HW design, SW design, and network designs.
• End users must participate actively in design process.
• Implementation
• Produces working system by purchasing HW and programming SW
• Testing
• Unit testing: error testing for individual units
• System testing: overall performance such as time, error rate.
• Acceptance testing: testing in real operational environments
• Conversion
• Process of converting from old system to the new system
• Maintenance
Chapter 13: Building Information Systems
Management Information Systems, Global Edition기업과 정보 (Management Information Systems)
Alternative Systems Building Approaches
• Water fall approach
• One step is completed before next step starts
• Useful for well-understood systems
• Prototyping
• Steps are repeated starting from a simple system of basic functions until full functional systems
• Useful for new and unfamiliar systems
• End-user development
• End user develops the system himself using 4th generation languages. (E.g., Excel macros)
• Application software packages
• Instead of development, buy sw packages (may need customization)
• Outsourcing
• Using ASP(application service provider): pay for usage
Chapter 13: Building Information Systems
Management Information Systems, Global Edition기업과 정보 (Management Information Systems)
Alternative Systems Building Approaches
• Structured modeling:
models of process, data and flows
• Object-oriented modeling
• CASE (Computer-aided software engineering) modeling tool: code generator, report generator,
analysis and testing tools, etc.
• RAD (Rapid application
development): Visual programming (Visual Basic, Visual C++, etc.)
Chapter 13: Building Information Systems
