Module_7_with_narration_text - Module 7: Systems...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Module 7: Systems development 1. Introduction In this lecture, we discuss the ways to make new information systems available in your organization: by using the traditional systems development lifecycle approach, by using rapid applications development and agile development, or by outsourcing systems development, or even the whole business processes dependent on IT to other organizations. 2. Systems development lifecycle (SDLC) System development life cycle (SDLC) is a structured step-by-step approach to developing information systems intended to coordinate systems development activities and to manage risks. The five phases in the SDLC are: system definition, requirements analysis, component design, implementation, and system maintenance. 3. System definition In the system definition phase, you achieve a high-level view of what the system is going to do and how you will develop it. In defining the system scope, your organization decides the overall purpose of the system - how it is going to contribute to realizing the organization's strategy. System scope is often defined by high level management. A system scope document often spells out both what the system is supposed to do, and, to delineate the scope more clearly, what the system is not supposed to do. Scope definition is followed by a feasibility study, the aim of which is to determine if a system suggested by the scope definition document can, indeed, be developed and implemented. Is it possible to develop the system at a cost within the bounds of the available budget (cost feasibility)? Is it possible to develop the system fast enough for it to be available to address the problem or the opportunity it is intended to address (schedule feasibility)? Are current capabilities of information technology sufficient to develop the system (technical feasibility)?
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Module 7: Systems development 2 A less obvious, but highly important aspect of feasibility is organizational feasibility. Does your organizatio nal culture, “the way things are done" in your organization, make it likely that the system is going to be accepted and used by its intended users? Would the system change the balance of power in the organization in ways that are going to evoke hostility from some of the intended users, or from some of the managers? Ultimately, your investment in developing the system is only going to bring returns if the system is accepted and becomes part of the social fabric of your organization. You complete the system definition phase by devising a project plan documenting the activities involved in developing the system, their dependencies, and the resources (such as appropriately qualified people) required to complete them. You appoint a project manager responsible for coordinating the activities, and you set project milestones. It is highly likely that in the course of system development the allocation of resources and the milestones will have to be negotiated - any upfront estimates are bound to be approximate. 4. Analysis
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 06/01/2010 for the course PN 115.107 taught by Professor Ivan during the Spring '10 term at Massey Palmerston North.

Page1 / 8

Module_7_with_narration_text - Module 7: Systems...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online