You are on page 1of 20

Management

Information
Systems
MIS 300

Textbook/material required: Haag, S., & Cummings, M.


(2009). Management information systems for the
information age. 9 th ed. McGraw-Hill, Inc.
Chapter 6: Systems Development

Pages: 160 - 185


Lesson Content (Part 1)
Case Study: Camera Films
What is a System Development Life Cycle (SDLC)?
Introduction to SDLC:
• Traditional methods:
• Linear approach*
• Waterfall approach
• Sourcing our system development
Component-Based Development
• Rapid Application Development
• Extreme Programming Methodology
• Agile Methodology
Prototyping

3
Systems development life cycle (SDLC) :

SDLC Phases &


Major
Activities

4
Linear Approach

• These are the exact steps used for the


Linear Approach.
1. Planning: Making sure you have the
resources to do the project.
2. Analysis: Understanding everything
you need to know about the project.
3. Design: Process of turning the
requirements into plans for the
developers

Planning Analysis Design

5
Linear Approach

• These are the exact steps used for the Linear Approach.
4. Development: The programming stage.
5. Testing: Checking the final application meets your
requirements.
6. Implementation: Making sure appropriate support
and training are provided as a part of the closing of
the project.
7. Maintenance: Continuously support and improve it.

Planning Analysis Design Development Testing Implementation Maintenance

6
Linear Approach

• Problems with the Linear Approach:


• Very strict: Does not allow going back to fix problems.
• Not client oriented enough: Client contacts only limited
to the first two stages
• Assumes that the clients and customers know what they
want from the start.

Planning Analysis Design Development Testing Implementation Maintenance

7
Waterfall Approach
Planning

Analysis

Design

Development

Testing
Similar to the Linear Approach, we
move forward down the stream.
Implementation

Maintenance

8
Waterfall Approach
Planning

Analysis

Design

Development

Testing
Unlike the Linear Approach, we go
back up the stream if we find
problems that have to be fixed. Implementation

maintenance

9
Ways of developing a system
• When developing a new system, you have 3 “who” choices…
1. Insourcing: IT specialists inside your organization
2. Outsourcing: A third-party organization (i.e., let someone do the
work and pay them for it)
3. Selfsourcing: Do-it-yourself approach many end users take with
little or no help from IT specialists
Outsourcing Process:
• Outsourcing process looks similar to the traditional SDLC
• Big exception here is that you “outsource” most of the work to another company

The first few steps are similar again to previous developments we saw:
1. Planning
2. Defining Project Scope
3. Selecting a target system
New steps:
4. Establish Logical Requirements
5. Develop a Request for Proposal (RFP)
6. Evaluate RFP returns and select the company
7. Create a Service Level Agreement (SLA)
8. Test and Accept the Solution
9. Monitor and Re-evaluate.
Notice that outsourcing here means the Design, Development, testing, and
implementation is turned over to another company.
11
Outsourcing: RFP
• Request for proposal (RFP) – a formal document that describes in intensive/
excruciating detail your logical requirements for a proposed system and invites
outsourcing organizations to submit bids for its development
• In outsourcing, you must tell another organization what you want to be developed; you
do that with an RFP
• Therefore, the RFP must be very detailed
• Some RFPs can take years to develop

12
Outsourcing: SLA

• Service level agreement (SLA) - 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
you’re going to pay
• Supporting SLA documents – service level specifications and service level
objectives – contain very detailed numbers and metrics

13
Ways to source our IS project: p.182
• Geopolitical Outsourcing Options:
• Outsourcing decisions may sometimes depend on the
location of the providers.
1. Onshore Outsourcing: The provider is in the same
country as you.
2. Nearshore Outsourcing: The provider is in a country that
shares a border with your country.
3. Offshore Outsourcing: The provider is in a country that is
far away*.

14
Ways to source IS project: p.183
• Advantages of Outsourcing*:
• Reduce Costs: Big money saver.
• Better predict cost: When you sign a contract you know exactly how much a
system will cost.
• Improve Accountability: It guarantees you will get what you asked for.
• Focusing on core systems: By outsourcing none critical systems, some
companies can focus their insourcing on critical systems.
• Use other companies’ expertise: which would be specialists in this area.
• Getting the latest skills and technology in that field.

15
Ways to source IS project: p.183
• Disadvantages of Outsourcing:
• Reduce the ability to develop your own skills in the future, your company
becomes completely reliant on others.
• Reduce control: you will need that company for changes, updates, and
upgrades.
• Increases the risk of exposing your strategic information systems. There is a
risk the external company may share your system with competitors.
• Overall: increases your dependency on other organizations.

16
Prototyping: P.174

• Prototyping is an iterative process in which you


build a model of the:
• business requirements
• Using prototypes at each stage
• Helping users give better feedback
• and enhancing the prototype to include users’ input.
• The users of the project (system) will see, work with, evaluate, and
suggest changes to the models.
• This increases the success of the system.

17
Prototyping: P.176
•Prototyping
process:
1. Identify basic
requirements of the
user.
2. Develop initial
prototype.
3. End user evaluates
and gives feedback.
If everyone is happy
skip step 4 – finish*!
4. Revise and enhance
prototype. Go back
to step 3.

18
Advantages of Prototyping: P.177
1. Encourages users’ participation.
2. Helps resolve differences between users.
3. Gives users a feel of the system before it develops.
4. Helps determine if it is technically possible to do.
5. Sells the idea better to the users.

19
Disadvantages of Prototyping: P.177
1. Leads people to believe the final system will come soon!
2. Gives no indication of the operational limitations*.
3. This may lead the team not to document or test the final work
properly.

20

You might also like