Get 0% discount. Hurry now while offer last till 05.11.2020 12:00

MBA 815 MANAGEMENT INFORMATION SYSTEM

Course Summary

Table of Content

Share
  • OVERVIEW OF SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
  • OVERVIEW OF INFORMATION SYSTEM DEVELOPMENT METHODS
  • STRATEGIC PLANNING FOR DESIGN OF INFORMATIONSYSTEMS
  • Concept of Information System Development (ISD)
  • STRATEGIC PLANNING FOR DESIGN OF INFORMATION SYSTEMS
  • INITIATION OF SYSTEM DESIGN AND DEVELOPMENT
  • CONCEPT DEVELOPMENT AND PLANNING OF SYSTEM DESIGN
  • REQUIREMENTS ANALYSIS OF SYSTEM DESIGN
  • DESIGN OF SYSTEM
  • DEVELOPMENT, INTEGRATION AND TESTING OF INFORMATION SYSTEM
  • IMPLEMENTATION AND DISPOSITION OF SYSTEM
  • OPERATIONS AND MAINTENANCE OF SYSTEM
  • DYNAMIC SYSTEMS DEVELOPMENT METHOD
  • PROJECT MANAGEMENT
  • PROJECT PLANNING
  • Risk Management
  • DESIGN AND PLANNING FOR GIS
Sample content.
OVERVIEW OF INFORMATION SYSTEM DEVELOPMENT METHODS

3.1 SDLC Objectives

Meaning of SDLC

The System Development Life Cycle (SDLC) is a structured framework used to guide:

  • System developers

  • Project managers

  • Analysts

  • System owners/users

in developing and managing information systems effectively.


Main Objectives of SDLC

SDLC is designed to:

  1. Reduce project failure risk

  2. Consider system and data needs throughout system life

  3. Identify technical and management problems early

  4. Reveal total life-cycle costs for better decisions

  5. Create realistic expectations about system capabilities

  6. Balance technical, management, and cost factors

  7. Encourage periodic system evaluation

  8. Monitor project progress and status

  9. Support resource and budget planning

  10. Meet both current and future business requirements


3.2 Purpose, Scope and Applicability


3.2.1 Purpose

SDLC provides procedures and guidelines for:

  • System initiation

  • Planning

  • Requirements analysis

  • Design

  • Development

  • Testing

  • Implementation

  • Maintenance

  • System disposal

It ensures MIS systems are developed according to organizational policies.


3.2.2 Scope

SDLC applies to:

  • All organizational information systems

  • In-house and outsourced projects

  • All IT environments (mainframe, client-server, etc.)

 The process can be tailored depending on:

  • Project size

  • Complexity

  • Importance to organization mission.


3.2.3 Applicability

Used by:

  • Offices, divisions, departments

  • Project managers

  • Development teams

  • System users and owners

Purpose:
✔ Ensure systems meet requirements
✔ Support organizational goals
✔ Provide structured IT project management.


3.3 Key Principles of SDLC

These are the foundations of successful system development.


 Life Cycle Management

Provides a structured approach to:

  • Development

  • Maintenance

  • Operation of systems

Allows flexibility based on project needs.


 Integrated Product Team (IPT)

A multidisciplinary team supporting the project manager.

Benefits:

  • Better communication

  • Faster decisions

  • Improved project success.


 Program Sponsor Requirement

Every project must have a sponsor who:

  • Provides leadership

  • Secures approvals

  • Ensures management commitment.


 Single Project Manager

Responsible for:

  • Project success

  • Coordination

  • Decision implementation

  • Defining authority through a project charter.


Comprehensive Project Management Plan

Defines:

  • Scope

  • Tasks

  • Schedule

  • Resources

  • Project relationships

Acts as the roadmap of the project.


 Assignment of Key Roles

Important roles include:

  • Quality assurance

  • Security management

  • Database administration

  • Financial management

  • Testing and evaluation.


 Skilled Personnel Participation

Human expertise is the most critical success factor.

SDLC supports skills — it does not replace them.


 Proper Documentation

All decisions and activities must be documented to:

  • Avoid confusion

  • Maintain continuity

  • Support reviews and approvals.


 Data Management Throughout Lifecycle

Data is treated as a valuable organizational asset.
Focus on:

  • Data quality

  • Data sharing

  • Proper data definition.


 Formal System Acceptance

After implementation:

  • Sponsor formally approves system delivery.


 Oversight Consultation

Project teams work with regulatory and oversight bodies early to avoid problems.


 Resource Assurance

Projects continue only if required resources are guaranteed.


3.4 SDLC Phases

SDLC consists of several phases (often about 10), including:

  1. Initiation

  2. Concept development

  3. Planning

  4. Requirements analysis

  5. System design

  6. Development

  7. Integration & testing

  8. Implementation

  9. Operations & maintenance

  10. Disposition (system retirement)

Phases may:

  • Overlap

  • Combine

  • Run iteratively depending on project size.

    SDLC PHASES (System Development Life Cycle)

    SDLC divides system development into logical phases to ensure a system is properly planned, built, tested, and maintained.


     System Concept Development Phase

    This is the idea and feasibility stage.

    Main Activities:

    • Business need is approved.

    • Possible system solutions are evaluated.

    • Feasibility and suitability are checked.

    • System scope is defined.


     Planning Phase

    The system concept is expanded into a detailed project plan.

    Activities:

    • Define how the business will operate after implementation.

    • Identify project resources and schedules.

    • Define tools, activities, and reviews.

    • Assess privacy impacts.

    • Begin security planning.

    • Conduct high-level vulnerability assessment.

     Goal: Deliver system on time and within budget.


     Requirements Analysis Phase

    User needs are formally defined.

    Requirements include:

    • Data requirements

    • System performance

    • Security requirements

    • Maintainability requirements

     Requirements must be:

    • Measurable

    • Testable

    • Linked to business needs.


     Design Phase

    System structure is created.

    Activities:

    • Define operating environment.

    • Identify subsystems.

    • Specify inputs and outputs.

    • Prepare detailed system architecture.

    • Develop module logic specifications.

     Users review and approve designs.


     Development Phase

    Design is converted into a real system.

    Activities:

    • Software coding

    • Hardware setup

    • Unit testing

    • Integration testing

    • Hardware testing

    Result:
     Executable software and working hardware.


     Integration and Test Phase

    All system components are combined and tested.

    Activities:

    • System integration

    • Functional testing by users

    • Certification and accreditation

    • Verification that requirements are met.


     Implementation Phase

    System goes live.

    Activities:

    • Install system in production environment.

    • User acceptance.

    • System becomes operational.

    Phase ends when system runs successfully according to user needs.


     Operations and Maintenance Phase

    Longest phase of SDLC.

    Activities:

    • Monitor system performance.

    • Fix errors.

    • Update features.

    • Improve efficiency.


    Disposition Phase

    System retirement stage.

    Activities:

    • Shut down system safely.

    • Archive or migrate data.

    • Preserve important records.

    3.5 Documentation in SDLC

    Documentation is required throughout the lifecycle.

    Purpose:

    • Ensure communication

    • Maintain records of decisions

    • Support future maintenance

    • Meet legal requirements

    Key Points:

    • Some documents remain unchanged.

    • Some evolve during later phases.

    • All documents stored in project files.

    • Electronic records must follow retention policies.


    3.6 SDLC MODELS

    Different organizations use different development approaches.


    Waterfall Model

    • Linear and sequential.

    • One phase completed before next begins.

     Easy to manage
     Hard to make changes later.


     Rapid Application Development (RAD)

    Focuses on speed.

    Features:

    • Workshops for requirements

    • Prototyping

    • Frequent testing

    • Strict timelines

     Faster development.


     Joint Application Development (JAD)

    Users actively participate through workshops.

    Improves user satisfaction and accuracy of requirements.


     Prototyping Model

    • Early version (prototype) built first.

    • Tested and refined repeatedly.

     Helps users visualize system early.


     Synchronize-and-Stabilize Model

    • Multiple teams work simultaneously.

    • Code frequently synchronized and stabilized.

    Common in large software companies.


     Spiral Model

    Combination of:

    • Waterfall + Prototyping

    Best for:
     Large, complex, high-risk projects