Week 2 - Intro to SAD (1).pptx

Introduction to Systems Analysis and Design

  • Course Information: ITSS 4330, Week 2, Professor Khan

Learning Objectives

  • Understanding the necessity of SDLC (Systems Development Life Cycle) and project management techniques.

  • Overview of the SDLC phases.

  • Team roles & required skill sets.

  • Importance of change management in systems development.

  • Introduction to Unified Modeling Language (UML).

  • Overview of Work Breakdown Schedule/Structure.

Systems Analysis and Design

Necessity of Formal Processes

  • Project failures are common: Projects are often late, over budget, or lacking in features.

  • A formal process is required to design systems that add business value and to understand business processes.

  • The role of the system analyst is crucial; it requires specific skill sets.

Project Management Performance (2018 Statistics)

  • Success Rates:

    • 78% of projects met original goals.

    • 67% completed within budget.

    • 64% completed on time.

  • Challenges:

    • 45% experienced scope creep.

    • 12% were deemed failures (Source: PMI).

Causes of Project Failure in 2017

  • Change in organization’s priorities (39%).

  • Change in project objectives (37%).

  • Inaccurate requirements gathering (35%).

  • Inadequate vision for the project (29%).

  • Poor communication and defined risks (29%).

  • Inaccurate cost and time estimates (28% to 26%) (Source: PMI).

Systems Development Life Cycle (SDLC)

Phases of the SDLC

  • Implementation

  • Planning

  • Design

  • Analysis

Execution of SDLC Phases

  • Phases are executed sequentially, incrementally, and iteratively with documentation (deliverables) for each phase.

Questions for Each SDLC Phase

Planning

  • Why build this? What value does it provide? How long will it take?

Analysis

  • What does the current system look like? What should it do? When, where, and how will it be used?

Design

  • Design structure, user interface, and database implementation. How to implement the build in production?

Detailed Phases of the SDLC

Planning Phase

  • Develop/receive system enhancement requests.

  • Conduct a feasibility analysis.

Analysis Phase

  • Model the current system and develop an analysis strategy.

  • Create business models with UML diagrams for business data and processes.

Design Phase

  • Develop design strategies, architecture, and user interfaces.

  • Specify databases and functionalities of the programs.

Implementation Phase

  • Build (code), test, and implement the system.

  • Create transition plans and train users.

Agile vs Waterfall Methodologies

Agile Process

  • Features:

    • Continuous cycles and customer involvement.

    • Flexibility and collaboration.

    • Focus on high-priority projects.

Waterfall Process

  • Features:

    • Sequential stages with upfront planning & documentation.

    • Best for simple, unchanging projects.

Key Skills for Analysts

  • Identifying improvement opportunities and motivating others.

  • Technical knowledge, business process understanding, strong analytical skills.

  • Proficient communication to bridge technical and non-technical audiences.

  • Strong interpersonal and ethical standards.

Analyst Roles

  • Business Analyst: Focus on business issues.

  • Systems Analyst: Focus on IS-related issues.

  • Infrastructure Analyst: Technical concerns.

  • Change Management Analyst: People and change dynamics.

  • Project Manager: Ensures timely and budget-compliant project completion.

Project Manager Values

  1. Problem solver: Overcomes project roadblocks.

  2. Cultural awareness: Minimizes conflicts.

  3. Leadership: Motivates teams.

  4. Effective communication: Critical in project execution.

  5. Credibility: Builds respect through experience.

  6. Knowledge of frameworks: Agile, program, and portfolio management.

  7. Optimism: Embraces change.

  8. Digital savviness: Stays updated with PM tools and techniques.

Change Management Overview

  • Definition: Managing organizational shifts and transformations.

  • Importance in systems analysis involves the implementation of new technologies and behavioral transitions.

  • Who Is Responsible: Everyone, including sponsors, managers, adopters, and developers.

Barriers to Change

  • Resistance reflects preference for familiarity; common phrases show reluctance to adapt.

Change Phases

  • Current State: Preference for existing conditions.

  • Transition State: Causes stress and anxiety.

  • Future State: Often unknown and intimidating.

Resistance Motivations

  • Perceptions of cost vs. benefit influence their assessment of change.

Motivating Adoption of Change

  • Providing evidence of the need for change, supporting ready adopters, and nurturing reluctant ones.

Unified Modeling Language (UML)

  • Version 2.5 includes 15 diagrams in two major groups: structural and behavioral.

  • Provides object-oriented modeling vocabulary from analysis to implementation.

Behavioral Diagrams

  • Depict dynamic relationships in the information system.

    • Types include activity, sequence, and communication diagrams.

Structural Diagrams

  • Represent data and static relationships within an information system.

    • Include class diagrams, component diagrams, etc.

Work Breakdown Structure (WBS)

  • A deliverable-oriented grouping of project components defining total project scope.

  • Essential for project scheduling, monitoring, and control.

WBS Example: Construction of a House

  • Provides a detailed breakdown of tasks, subtasks, and budgets for project components.

Summary

  • The Unified Process consists of defined phases and workflows.

  • The role of the systems analyst is integral, requiring diverse skills.

  • Combining project management techniques with SDLC increases success potential.