14-1
Chapter Preview
In this chapter, we will study:
Planning process for IS application development The process of developing systems as outlined in the SDLC Alternatives to the SDLC and why they are useful Ways to obtain applications from outside the organization Methods that are useful in developing Internet/intranet applications
14-2
IS Strategic Plan New Information Technology Architecture IS Operational Plan IS Development Projects
14-3
IS Strategic Plan
Objectives Align with the organizations strategic plan Provide for an IT architecture that enables users, applications, and databases to be seamlessly networked and integrated Allocate IS development resources efficiently among competing projects, so the projects can be completed on time, within budget, and have required functionality Issues - efficiency; effectiveness; competitiveness
14-4
IS Operational Plan
information needs of the functional areas and of the organization as a whole Objectives - the IS functions current best estimate of its goals Constraints - technological, financial, and personnel limitations on the IS function Long-term systems need - a summary of the processes needed by a company and the IS projects selected to support them and reach organizational goals Short-range plan - an inventory of current projects, and a detailed plan of projects to be developed or continued during the current year
14-5
14-6
(6) Implementation (7) Operation (8) Maintenance Go Back to a previous Stage or Stop
14-7
System Investigation
Phases in SDLC
Feasibility study determines the probability of success of proposed systems development project. Includes
Technical feasibility (will we be able to build the system?) Economic feasibility (how much will it cost to build the system and how much will it benefit us?) Behavioral feasibility (if we build the system, will it be accepted and used?)
Systems Analysis
Examines the business problem(s) that the organization plans to solve with information systems Determines what the new system must do by examining:
Strengths and weaknesses of the existing system Functions that the new systems must have to solve the business problem(s) User information requirements for the new system
14-8
Programming
the translation of the design specifications into computer code structured programming techniques improve the logical flow of the program by decomposing the computer code into modules
14-9
Implementation
The process of converting from the old system to the new system Four major conversion strategies Parallel conversion: the old and new systems operate simultaneously for a period of time Direct conversion: the old system is cut off and the new systems is turned on at a certain point in time Pilot conversion: introduces the new system in one part of the organization Phased conversion: introduces components of the new system in stages
14-10
SDLC Phases
Operation
the new system will operate for a period of time, until it no longer meets its objectives
Prototyping
Starts with only a general idea of user requirements, and develops models of the system until its right
Advantages:
Speeds up the development approach Gives the users the opportunity to clarify their information requirements Useful in the development of decision support systems and executive information systems Replaces the systematic analysis and design stages of the SDLC - quality may be sacrificed Can result in an excess of iterations
Disadvantages:
14-12
Advantages:
Saves time Greater support for, and acceptance of new systems Produces higher quality systems Easier implementation Lower training costs Very difficult to get all users to JAD meetings All the problems that may be caused by any group process
Disadvantages:
14-13
Advantages:
Active involvement of users in the development process Speeds the development process Reduces development costs Can create applications that are easier to maintain and modify
May result in systems with limited functionality and adaptability for change
14-14
Disadvantages:
Advantages:
Produces systems with a longer effective operational life Speeds up the development process and result in systems that are more flexible and adaptable to changing business conditions Results in excellent documentation
Disadvantages:
More expensive to build and maintain initial system Requires more extensive and accurate definition of user needs and requirements Difficult to customize and may be difficult to use with existing systems
14-15
Object-Oriented Development
Advantages:
Disadvantages
End-users (usually) dont produce adequate documentation or perform adequate testing Security may be breached
14-17
14-18
14-19
14-20
Guidelines: Write short-period contracts or have flexibility since business needs are dynamic Use of subcontractors should be controlled Use selective outsourcing only for those functions where it makes sense
14-21
Much future development will likely be Web pages due to their simplicity and ease of development
14-22
Summary
IS Strategic and Operational Plans derive from the organizations strategic plan and current IT architecture The SDLC provides a basic framework for the process of development information system applications There are several alternatives to the SDLC, including prototyping and RAD IS applications can also be obtained outside the IS organization, including end user development, package purchases, ASPs, and outsourcing Development for Internet/intranet applications generally follows prototyping process
14-24