310 likes | 329 Views
Explore the impact of developing new systems on organizations, the steps needed to create information systems, available development methods, and approaches for e-business applications.
E N D
OBJECTIVES • How could developing a new system change the way an organization works? • What are the steps required to develop a new information system? • What methods for developing information systems are available? • What system-building approaches can help us develop e-business applications more rapidly?
SYSTEMS AS PLANNED ORGANIZATIONAL CHANGE • The Spectrum of Organizational Change • Automation: • Speeding up performance • Rationalization of Procedures: • Streamlining of operating procedures • Business Process Reengineering: • Radical re-design of business processes • Paradigm Shift: • Radical re-conceptualization
10.2 BUSINESS PROCESS REENGINEERING AND PROCESS IMPROVEMENT Figure 10.3 (A)
Figure 10.3 (B) 10.2 BUSINESS PROCESS REENGINEERING AND PROCESS IMPROVEMENT Business Process Re-engineering
OBJECTIVES • How could developing a new system change the way an organization works? • What are the steps required to develop a new information system? • What methods for developing information systems are available? • What system-building approaches can help us develop e-business applications more rapidly?
OVERVIEW OF SYSTEMS DEVELOPMENT • Systems Analysis • Analysis of a problem that the organization will try to solve with IT • Feasibility Study • determines whether the solution is achievable, given the organization’s resources and constraints • Establishing Information Requirements • Identifying who needs what information, and when, where, and how the information is needed • Failure here is a leading cause of systems failure
OVERVIEW OF SYSTEMS DEVELOPMENT Systems Design • Details how a system will meet the information requirements determined by systems analysis • Specifications for the system solution • Should reflect user business priorities and information needs, not biases of IT experts • lack of end-user involvement is a major cause of system failure
OVERVIEW OF SYSTEMS DEVELOPMENT • Programming • Process of translating system specifications into program code • Testing • Checks whether the system produces desired results under known conditions • Critical step – all programs have bugs! • Need: • Unit testing • System testing • Acceptance testing
OVERVIEW OF SYSTEMS DEVELOPMENT • Conversion • Process of changing from old system to new system • Conversion Strategies include: • Parallel • Direct cutover • Pilot study • Documentation – why is this vital? • Ongoing throughout system development • Finalized here – why?
OVERVIEW OF SYSTEMS DEVELOPMENT • Production and Maintenance • Production: • The stage after new system is installed and the conversion is complete • Maintenance • Changes in hardware, software, or documentation of production system to correct errors, or meet new requirements • 20% - fix programming errors • 20% - adapt to changes • 60% - improve design – this is avoidable!
OBJECTIVES • How could developing a new system change the way an organization works? • What are the steps required to develop a new information system? • What methods for developing information systems are available? • What system-building approaches can help us develop e-business applications more rapidly?
ALTERNATIVE SYSTEM-BUILDING APPROACHES • Systems Development Lifecycle (SDLC) • Traditional methodology for developing information system • Partitions systems development process into formal stages that must be completed sequentially • Formal division of labour between end users and information system specialists
ALTERNATIVE SYSTEM-BUILDING APPROACHES • Prototyping • Process of building experimental system quickly and inexpensively • Use for demonstration and evaluation • Allows users to better determine information requirements • Easy to involve users, good for designing end-user interface • Result may not be scalable, secure etc.
ALTERNATIVE SYSTEM-BUILDING APPROACHES • Application Software Packages • Set of prewritten application programs commercially available • Often selected via RFP • detailed list of specs submitted to vendors • determines how well vendor’s product can meet organization’s needs • May need to be customized to meet organization’s unique requirements
ALTERNATIVE SYSTEM-BUILDING APPROACHES “Good software is not (alas!) written, it is re-written” (An old programming adage)
ALTERNATIVE SYSTEM-BUILDING APPROACHES End-User Development • Development of information systems by end users with minimal assistance from ‘techies’ • Advantage -higher level of user involvement and satisfaction • Limitations -systems likely to lack scalability, security, testing, documentation etc. • Facilitated by an Information Centre - facility that provides support for end-user computing
ALTERNATIVE SYSTEM-BUILDING APPROACHES Outsourcing • Practice of contracting applications development (and perhaps system operation) to external vendors • Can get expertise not available in firm • External source benefits from economies of scale • May result in loss of control, dangerous reliance on stability of outside firm
(A) 10.4 ALTERNATIVE SYSTEM-BUILDING APPROACHES
(B) 10.4 ALTERNATIVE SYSTEM-BUILDING APPROACHES
OBJECTIVES • How could developing a new system change the way an organization works? • What are the steps required to develop a new information system? • What methods for developing information systems are available? • What system-building approaches can help us develop e-business applications more rapidly?
APPLICATION DEVELOPMENT FOR THE DIGITAL FIRM Object-Oriented Software Development • Shifts focus from modeling business processes and data to combining data and procedures to create objects • Applications can be created by reusing existing objects (without reprogramming), adding new objects as needed • More iterative and incremental than SDLC • Requires large investment in training and programming
APPLICATION DEVELOPMENT FOR THE DIGITAL FIRM Web Services • Software components deliverable over Internet • E.g. IBM Web sphere, MS .Net • Real life example in text? • Uses standards to allow information interchange between applications: • XML – standard description of data in web pages allows data exchange • SOAP – rules for data exchange • UDDI – directory of web services