1. Insourcing (in-house IT specialists)

2. Selfsourcing (do-it-yourself approach many end users take with little or no help from IT specialists)

-Reduces invisible backlog

 - Inadequate end user expertise leads to inadequately developed systems.

3. Outsourcing (A third party organization i.e. let someone do the work and pay them for it)

A structured step-by-step approach for developing information systems.

7 distinct phases, each with well defined activities.

Also called waterfall methodology, an approach in which each phase of the SDLC is followed by another, from planning through implementation.

1. Planning

2. Analysis

3. Design

4. Development

5. Testing

6.  Implementation

7. Maintenance

During the planning phase, you create a solid plan for developing your information system.

3 Primary Activities:

1. Define the system to be developed.

2. Set the project scope.

3. Develop the project plan including tasks, resources, and timeframes.

During the design phase, you build a technical blueprint of how the proposed system will work.

Two Primary Activities:

1. Design the technical architecture required to support the system.

2. Design system models

During the development phase, you take all your detailed design documents from the design phase and transform them into an actual system.

Two Primary Activities:

1. Build the technical architecture.

2. Build the database and programs.

The testing phase verifies that the system works and meets all the business requirements defined in the analysis phase.

Two Primary Activities:

1. Write the test conditions.

2. Perform the testing of the system.

During the implementation phase, you distribute the system to all the users and they begin using the system to perform their everyday jobs.

Two Primary Activities:

1. Write detailed user documentation.

2. Provide training for the system users.

You monitor and support the new system to ensure it continues to meet the business goals.

Two Primary Activities:

1. Build a help desk to support the system users.

2. Provide an environment to support system changes.

The detailed set of knowledge worker requests that the system must meet in order to be successful.

Business requirements address the "why" and "what" of your development activities.

Prioritizes the business requirements and places them in a formal comprehensive document.

Again, you probably can't do everything, so prioritizing is important.

Users sign off on this document which clearly sets the scope the project.

Part of the design phase.

Defines the hardware, software, and telecommunications equipment required to run the system.

In the implementation phase.

Highlights how to use the system.

In the implementation phase.

Runs over the Internet or off a CD-ROM.

In the Maintenance phase.

A group of people who responds to knowledge workers questions.

1. Using already-developed components to build systems quickly.

2. Building new components as needed that can be used in all future systems.

Rapid application development (RAD)

Extreme Programming

Agile methodology

Also called rapid prototyping.

Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process.

Prototypes are models of the software components.

The development team continually designs, develops, and tests the component prototypes until they are finished.

Perspective that focuses on the development, use, and reuse of small self-contained blocks of code (called services) to meet all application software needs.

All CBD methodologies adhere to an SoA.

Services are the same as components, which are the same as small self-contained blocks of code.

Are easy to use

Support multiple platforms

Offer low cost of ownership

Support a wide range of data types

The process of building a model that demonstrates the features of a proposed product, service, or system.

- Proof-of-concept prototype: Used to prove the technical feasibility of a proposed system.

- Selling prototype: Used to convince people of the worth of a proposed system.

1. Identify basic reqirements.

2. Develp initital prototype.

3. User review.

4. Revise and enhance the prototype.

Encourages active user participation.

Helps resolve discrepancies among users.

Gives users a feel for the final system.

Helps determine technical feasibility.

Helps sell the idea of a proposed system.

Leads people to believe the final system will follow.

Gives no indication of performance under operational conditions.

Leads the project team to forgo proper testing and documentation.

Globilization

The Internet

Growing economy and low unemployment rate

Technology

Deregulation

1. Purchase existing software

2. Purchase exisitng software and pay the publisher to make certain modifications.

3. Purchase existing software and pay the publisher for the right to make modifications yourself.

4. Outsource the development of an entirely new and unique system for which no software exists.

Formal document that describes in excruciating detail your logical requirements for a proposed system and invites outsourcing organizations (vendors) to submit bids for its development.

In outsourcing, you must tell another organization what you want developed. You do that with a RFP

Formal contractually obligated agreement between two parties.

In outsourcing, it is the legal agreement between you and the vendor and specifically identifies what the vendor is going to do (and by when) and how much your going to pay.

1. Onshore outsourcing

2. Nearshore Outsourcing

3. Offshore Outsourcing

India

China

Eastern Europe (including Russia)

Ireland

Israel

Phillippines

Focus on unique core competencies.

Exploit the intellect of another organization.

Better predict future costs.

Acquire leading-edge technology.

Reduce costs.

Improve performace accountability.

Reduces technical know-how for future innovation.

Reduces degree of control.

Increases vulnerability of your strategic information.

Increases dependency on other organization.