Roadblocks to the Systems Development Life Cycle

1
Roadblocks to the SystemsDevelopment Life Cycle

• Presented By
• Iona Montgomery, Mike McLeish, Andy Wu, and
  Dorian Bush

2
Overview

• In this presentation we will provide a brief
  definition of the Systems Development Life Cycle
  and describe the six phases that make up the
  process.
• We will then discuss Dr. Deming's obstacles to
  getting the job done and attempt to relate them
  to the SDLC.

3
SDLC A definition

• Systems Development Life Cycle refers to a
  methodology for developing systems. It provides a
  consistent framework of tasks and deliverables
  needed to develop systems.
• The SDLC is divide into 6 phases and is commonly
  represented graphically as the waterfall model
  and/or linear cycle.(See figure)

4
The 6 phases of SDLC(phases are equivalent to
those shown in the waterfall model)

• Phase 1 Concept and Initiation
• Phase 2 System Analysis
• Phase 3 System Design
• Phase 4 Programming
• Phase 5 Conversion and
  Implementation
• Phase 6 Post implementation
  Evaluation

5
Phase 1 - Concept and Initiation

• Phase 1 includes
• Developing an overview of the project,
• Determining project objective and scope,
• Documentation of the present system,
• Identifying alternative system solutions as well
  as a preferred solution,
• Conducting a cost and benefit analysis,
• Determining resource commitments and support
  mechanisms
• This information is used to prepare the
  feasibility study which is used to acquire
  approval to proceed with the development of the
  system.

6
Phase 2 - System Analysis

• Phase 2 consists of
• Completing a High-Level analysis of the proposed
  system,
• Identifying systems acceptance criteria, user
  documentation and training needs,
• Identifying an implementation strategy
• The information gathered in Phase 2 is compiled
  into a preliminary action plan and documentation
  of the new system.

7
Phase 3 - System Design

• Phase 3 results in a more detailed action plan
  and preliminary testing and conversion plans.
  This phase describes how the systems
  requirements will be met.
• Data specifications,
• Forms,
• Screen layouts,
• Database requirements,
• Test scenarios,
• Security needs,
• occur in this phase and the design is finalized
  (frozen) before moving on to phase 4.

8
Phase 4 - Programming

• Phase 4 includes
• Preparation of software module development
  schedule,
• Module development,
• Preparation of test modules and procedures,
• User testing
• Phase 4 results in the development of all
  software required to support the system.

9
Phase5 Conversion and Implementation

• Introduction of the system occurs in this phase
  which includes
• User acceptance testing,
• User training,
• Transition strategy development,
• Parallel operation (if necessary)

10
Phase 6 Post Implementation Evaluation

• Phase 6
• A system review schedule is developed to ensure
  periodic system reviews take place.
• As indicated by the waterfall model the SDLC
  should be a continuous process.

11
Our brief overview of the SDLC is complete and we
will now move to Obstacles to getting the Job
Done
12
Obstacles

• Obstacle
• Anything or anyone that gets in the way of
  reaching a goal.
• Realizing there will be obstacles along the path
  makes it easier to plan for them.

13
Obstacles to SDLC Operations

• Benchmarking
• Hope for Instant Pudding
• Looking for Quick Fixes
• I wanted it Yesterday!
• Tables of Acceptance are Lethal

14
Benchmarking

• Taking another companys methodology or strategy
  and applying it to your own in expectation of
  success.
• Affects the 1st phase of SDLC
• Lack of understanding for why it worked for that
  company
• Costs, goals, targeted solution

15
Hope for Instant Pudding

• Experts are frequently hired to install or
  fix quality in an organization.
• Top management doesnt understand the problem
• Person accepting job doesnt either
• Can be likened to trying to buy happiness.
• Real changes needs to come from within.

16
Looking for Quick Fixes

• Lack of detailed research for solutions makes
  first solution look best.
• Short-term fixes to improve Profit Loss fail in
  the long run
• New system will never overcome the original
  problem.
• Affects 1st phase of SDLC
• Choosing a system that may not actually work for
  your company

17
I wanted it Yesterday!

• The company wants results fast, meaning
  shortcutting through phases of SDLC.
• Similar to Quick Fixes, except all processes are
  trimmed. New system is very prone to downtime
  and periodic success.
• Affects all phases of SDLC
• SDLC phases are thorough, without them the final
  solution may not work

18
Tables of Acceptance are Lethal

• Guarantee someone will get a bad part
• Actually, increases costs overall
• Becomes leading factor in choosing a system for
  the company.
• Affects 2nd phase of SDLC
• Choosing the system that may not actually work
  for your company

19
How to remove obstacles
20
How to remove obstacles

• Before you can remove the roadblock, you have to
  recognize the problem.
• Start by listing your obstacles.
• Narrow your focus.

21
Identify the Obstacles

• Identifying potential obstacles can help you plan
  ways to deal with them.
• You can list roadblocks in two categories
• Personal obstacles
• External obstacles

22
List your obstacles

• Personal obstacles
• Attitude
• Fear/anxiety
• Low self-esteem
• Lack of time manage
• Lack of ambition
• Lack of education
• Lack of experience
• Lack of skills

• External obstacles
• Economy
• Lack of information
• Competition
• Lack of financial resources
• Lack of supports
• Stereotyping

23
How to remove obstacles

• To move forward in achieving the goals we must
  optimize our surroundings to the best of our
  ability.
• Nothing will happen without a long term plan and
  a goal sheet.
• A plan is simply the map you write yourself to
  arrive at your destination point.

24
How to remove obstacles

• Ninety-nine percent of the failures come from
  people who have the habit of making
  excuses. -George Washington Carver
• Excuses are another form of roadblock.

25
Tips for overcoming obstacles

• Identify your obstacles.
• Ask yourself, What can I do about it?
• Think of as many possible solutions as you can.
• Choose the best one for you.
• Write down your plan.
• Set a realistic time frame.
• Take action.

26
Move the clouds from blue sky

• How you look at things in general will determine
  as to whether you can move the clouds away from
  your skyline or not.
• Remember to focus on your plan.
• Plan each step, think positively and never ever
  lose track of your target.
• Think successfully.

27
Real Life Stories of the SDLC
28

• Story 1 Do what they tell us
• Company Name Anonymous
• Company Type Bank
• Situation Forced to migrate operating system
  and applications to parent company

29
Story 1 in relation to SDLC

• Concept and Initiation
• - company used a combination of 2 operating
  systems Windows and OS/2
• - entire company must use a Windows OS in 30
  days
• - used the Lotus Suite / Office Suite of
  applications
• - entire company must use only Office Suite

• System Analysis
• - would this be installed one machine at a time
  or over server?
• - good times to actually perform installs
• - when to alert the user of action about to be
  taken

30
Story 1 in relation to SDLC

• System Design
• - not much to design application wise
• - do a mass install to a set of test machines
  on test server
• then test if applications worked afterwards
• - make sure security of server still remained
  after installations

• Programming
• - Made sure that all applications needed were
  on hand
• for installation
• - Selected a group of users throughout bank to
  test with
• - Decided to do a modular installation instead
  of a mass install

31
Story 1 in relation to SDLC

• Conversion and Implementation
• - sent out letters and email regarding the
  migration
• - prepared to endure rejection of migration
• - have training/information sessions of the
  new OS and applications
• - prepared to switch to backup OS and
  applications if necessary

• Post Implementation
• - constantly checking with users
• - preparing for next massive migration

32

• Story 2 Wouldnt It Be Great If
• Company Name Anonymous
• Company Type Aerospace Company
• Situation Creating a Database for Quality
  Assurance inspections

33
Story 2 in relation to SDLC

• Concept and Initiation
• - Department used combination of paper, Excel
  and
• Access to map trail of QA inspections
• - unable to cross reference with each other
• - a great idea to put into one huge DB

• System Analysis
• - find out who is using what application to
  record inspections
• - were they all following the same procedure?
• - map out default criteria for inspections
• - find application that would cover criteria

34
Story 2 in relation to SDLC

• System Design
• - Decided to use MS Access
• - test application against criteria

• Programming
• - make sure each user has access to
  application
• - Selected a group of users in dept to test
  application
• - move all data to tables

35
Story 2 in relation to SDLC

• Conversion and Implementation
• - notified everyone in department of actions
• - have training/information sessions of the
  new OS and applications
• - parallel updates with current system

• Post Implementation
• - constantly checking with users
• - continued training

36
References

• users.foxvalley.net OMIS 351/507 Special Topics
  Systems Development Life Cycle
• www.swt.edu - System Development Life Cycle
  Methodology
• www.sasknetwork.gov - Identifying Obstacles
• www.selfgrowth.com - remove the clouds from your
  clear blue sky!
• Four Days with Dr. Deming Latzko Saunders
  CPT 352 text