Initiating systems development

Slides:



Advertisements
Similar presentations
Technical System Options
Advertisements

Develop an Information Strategy Plan
Acquiring Information Systems and Applications
Systems Analysis and Design 9th Edition
GROUP THREE: QUESTION THREE
Chapter 2.
IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer 2003.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Health Informatics Series
System Development Life Cycle (SDLC)
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Acquiring Information Systems and Applications
Chapter 17 Acquiring and Implementing Accounting Information Systems
Introduction to Computer Technology
Picture 1 model: ICT lifecycle in a company 1. business needs & business strategy 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical.
Introduction ► This slide deck provides a suggested framework for the financial evaluation of an investment project. When evaluating any such project,
12 Building and Maintaining Information Systems.
Foundation Degree IT Project Methodologies (for reference)
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
CHAPTER 13 Acquiring Information Systems and Applications.
 System Development Life Cycle System Development Life Cycle  SDLC Phases SDLC Phases Phase 1: Preliminary Investigation Phase 2: Feasibility Study.
SDLC 1: Systems Planning and Selection Dania Bilal IS 582 Spring 2008.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Chapter 11: Alternative Approach - Purchasing Systems.
Week 1a: Introduction to the Module Graham Logan Building 303, Room 30 CO5021 Systems Development.
Diploma in Procurement & Supply Business needs in Procurement & Supply Session 1 Business Needs and Procurement Decisions.
Cis339 Chapter 2 The Origins of Software 2.1 Modern Systems Analysis and Design Fifth Edition.
第 11 組 MIS 報告. Phases of any information system ~ recognition of a business problem or opportunity ~ recognition of a business problem or opportunity.
CHAPTER 13 Acquiring Information Systems and Applications.
The Feasibility Study The objective of a feasibility study is to find out if an project can be done and if so, how The objective of a feasibility study.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Accounting systems design & evaluation 9434SB 18 March 2002.
Phase 1 Systems Planning
Diploma in Procurement & Supply
Slide 1 Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition Chapter 3: Project Initiation.
The Information Systems Development Processes Chapter 9.
ITEC 275 Computer Networks – Switching, Routing, and WANs
IS Development Methodology
IFS 231 Business Analysis LECTURE 2 The Business Case.
Information Systems Development
Systems Analysis and Design in a Changing World, 4th Edition
Principles of Information Systems Eighth Edition
Fundamentals of Information Systems, Sixth Edition
Developing Information Systems
System Development Life Cycle (SDLC)
Chapter 4 Systems Planning and Selection
Project Specification
INFS 211: Introduction to Information Technology
VENDORS, CONSULTANTS AND USERS
Introduction to Information Systems
Foundation Degree IT Project
Systems analysis and design, 6th edition Dennis, wixom, and roth
Introduction to Projects
Chapter 2 The Origins of Software
Systems analysis and design, 6th edition Dennis, wixom, and roth
Systems Analysis and Design
Human Resource Planning (HRP) Dr. Salim AlShukaili
EC Strategy, Globalization, and SMEs
System Development Life Cycle (SDLC)
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Today’s Agenda Dealing with Vendors Consultants Contracts
Project Procurement Management
Chapter 13 Preparing The Systems Proposal
Presentation transcript:

Initiating systems development Chapter 8 Initiating systems development 1

Learning objectives After this lecture, you will be able to: explain the importance of conducting a structured initiation phase for a BIS project; identify typical tangible and intangible costs and benefits associated with the introduction of an information system; apply different techniques to select the most appropriate options from different software, hardware and supplier alternatives; describe the importance of contracts to a successful outcome to information systems projects. 2

Management issues From a managerial perspective, this lecture addresses the following areas: How should we assess the feasibility of a project? What are the stages and techniques that can be applied to assess feasibility? How can the return on investment of a BIS project be assessed? How can we manage the risks associated with IS projects? 3

Initiation and feasibility Initiation phase: The first phase in an information systems development project. Its aims are to establish whether the project is feasible and prepare to ensure that the project is successful. Feasibility study: The activity that occurs at the start of the project to ensure that the project is a viable business proposition. The feasibility report analyses the need for and impact of the system and considers different alternatives for acquiring software. 4

Figure 8.1  Sequence of main activities involved with project initiation 5

Initiation activities 6

Initiation activities (Continued) 7

6Cs benefits of IS 8

Feasibility type Organisational feasibility: Reviews how well the solution meets the needs of the business and anticipates problems such as hostility to the system if insufficient training occurs. (Considers the effect of change, given a company’s culture and politics.) Question answered: Will the system meet the business’ needs and help improve its performance? Technique used to control: Critical success factors and key performance indicators. Change management. 9

Feasibility type (Continued) Economic feasibility: An assessment of the costs and benefits of different solutions to select that which gives the best value. (Will the new system cost more than the expected benefits?) Question answered: Will the costs outweigh the benefits? Technique used to control: Cost/benefit analysis Return-on-investment and payback calculations. 10

Costs and benefits Tangible costs: A measure of cost can be calculated for each tangible cost. Intangible costs: A monetary value cannot be placed on an intangible cost. Tangible benefits: A definite measure of improvement can be calculated for each tangible benefit. Intangible benefits: It is not possible to measure intangible benefits. 11

IS costs Hardware and software purchase costs Systems development staff costs if a bespoke or tailored solution is chosen Installation costs including cabling, physically moving equipment and bringing in new furniture to house the computers Migration costs such as transferring data from an existing system to the new system or running the new and original systems in parallel until the reliability of the new system is established Operating costs including maintenance costs of hardware such as replacing parts or upgrading to new versions of software. Staff costs in maintaining the hardware and software and trouble-shooting any problems must also be factored in. Operating costs may also include an environmental audit of the amount of energy and consumables used Training costs Wider organisational costs, for example, redundancy payments may need to be made if computerisation leads to loss of jobs. 12

IS benefits Improved accuracy Improved availability and timeliness Improved usability (easier to understand and then act on information) Improved utilisation Improved security of information 13

Feasibility type (Continued) Technical feasibility: Evaluates to what degree the proposed solutions will work as required and whether the right people and tools are available to implement the solution. Question answered: Will it work efficiently (performance, availability and stability)? Technique used to control: Risk analysis Capacity planning Performance and availability modelling. 14

Feasibility type (Continued) Operational feasibility: An assessment of how the new system will affect the daily working practices within the organisation. Question answered: Is the system workable on a day-to-day basis? Will the system be accepted by end-users into their day-to-day work? Technique used to control: Risk analysis Change management Usability analysis. 15

Risk management Risk management: Aims to anticipate the future risks of an information systems project and to put in place measures to counter or eliminate these risks. 16

Risk factors 1. Project size 2. Project complexity 3. People issues 4. Project control 5. Novelty 6. Requirements stability 17

Request for proposals (RFP) Request for proposals (RFP): A specification drawn up to assist in selecting the supplier and software. 18

Factors in selecting systems Functionality: Does the software have the features described to support the business requirements? Ease of use: For both end-users and initial setup and administration. Performance: For different functions such as data retrieval and screen display. If used in a customer-facing situation, this will be a critical factor. Compatibility or interoperability: How well does your solution integrate with other products? This includes what you are using now and what you will be using based on your strategic direction. 19

Factors in selecting systems (Continued) Security: This includes how easy it is to set up access control for different users and the physical robustness of methods for restricting access to information. Stability or reliability of product: Early versions of products often have bugs and you will experience a great deal of downtime and support calls; hence the saying ‘never buy one dot zero’. Prospects for long-term support of product: For example, if the vendor company is small or likely to be taken over by a predator, will the product exist in three years’ time? Extensibility: For example, are the features available to accommodate your future needs? 20

Contracts Contracts should define the following main parameters: business requirements and features of system; deliverables such as hardware, software and documentation; timescales and milestones for different modules; how the project is managed; division of responsibilities between different suppliers and the customer; costs and method of payment; long-term support of system. 21