A System Development Process

Where Do Systems Development Projects Come From?

System owners and system users initiate most projects. The impetus for most projects is some combination for problems, opportunities, and directives. By simplifying this discussion, we will frequently use the term problem to collectively refer to problems, opportunities, and directives. However, James Wetherbe developed a useful framework for classifying problems. He calls it PIECES because the letters of each of the six categories, when put together, spell the word pieces. The categories are: P the need to correct or improve performance. I the need to correct or improve information (and data). E the need to correct or improve economics, control costs, or increase profits. C the need to correct or improve control or security. E the need to correct or improve efficiency of people and process. S the need to correct or improve service to customers, suppliers, partners, employees. And so on.

problem an undesirable situation that prevents the organization from fully achieving its mission, vision and goals. opportunity - a chance to improve the organization even in the absence of an identified problem. directive - a new requirement thats imposed by a management, government, or some external influence.

Projects can be either planned or unplanned. The number of unplanned-project proposals can easily overwhelm the largest information systems organization; therefore, they are frequently screened and prioritized by a steering committee of system owners and IT managers to determine which requests get approved. Those requests that are not approved are backlogged until resource become available (which sometimes never happens). steering committee an administrative body of system owners and information technology executives that prioritizes and approves candidate system development projects. backlog a repository of project proposals that cannot be funded or staffed because they are a lower priority than those that have been approved for system development.

The Systems Development Phases

Most methodologies consist of phases. The number of phases will vary from one methodology to another. Scope definition first phase of a typical project. Scope definition phase is twofold. First, it answers the question Is the problem worth looking at? Second, assuming problem is worth looking at, it establishes the size and boundaries of the project.

Scope def. has several outcomes.

problem statement - a statement and categorization of problems, opportunities, and directives; may also include constraints and an initial vision for the solution. constraint - any factor, limitation, or restraint that may limit solution or the problem solving process. scope creep a common phenomenon wherein the requirements and expectation of project increase, often without regard to the impact on budget and schedule. statement of work a contract with management and the user community to develop or enhance an information system.

 Problem Analysis phase studies the existing system and analyzes the findings to provide the project team with a more thorough understanding of the problems that triggered the project. Requirements Analysis phase defines and prioritizes the business requirements. Perhaps this is the most important phase of systems development. Errors and omissions in requirements analysis result in user dissatisfaction with the final system and costly modification.