SEG3430 Tutorial 1

							SEG3430 Tutorial 1

  Review on System Development
  Life Cycle (SDLC)
Definition of SDLC

  the process of (1) understanding how an
   information system can support business
   needs, (2) designing the system, (3)
   building it and (4) delivering to the users
  a conceptual model that describes the
   stages involved in an information system
   development project
Different Phrase for SDLC

    a systematic approach to problem
     solving and is made up of several
     phases, each comprised of multiple
     steps:
      Planning: Why
      Analysis: Who, What, Where and When

      Design: How

      Implementation
Planning

    Identifying business value
      Gain an appropriate understanding of the
       business problem domain
      Estimate the investment and reward on the
       project
    Analyze feasibility
      Technical, economical and organizational
      Analyzes the information needs of the end
       users
Planning

    Develop work plan
        Decide the sequence of process completion
             Stock checking = merchandising system > login
              system
        PERT Chart
  Staff the project
  Control and direct project
        Prioritize - requirements can be classified as
         ‘mandatory’, ‘desirable’, or ‘optional’.
Analysis

    Analysis strategy
        As-is system and to-be system
    Gathering business requirements:
        Interview or questionnaire
    Use Case Analysis:
      Describe how an external user triggers an
       event to which the system must respond
      Eg: A library patron borrow or return a book.
Analysis

    Process modeling
      Representing how business operates
      Data flow diagram (DFD)

    Data modeling
      Balance with process models
      Entity-Relationship Diagram (ER diagram)

    Deliverable: System Proposal
Design

    Design Strategy
        In-house or outsource and purchase
         existing software package
    Architecture design
        specifications for the hardware, software,
         and network infracstructure
    Interface design
        implement the interfaces between the new
         system and existing systems
Design

    Data storage design
        RDBMS, XML or raw text file
    Program design
        existing systems must be integrated in the
         design
    Deliverable: System Specification
Implementation

    Construction
        Program building
             creates and programs the final system
        Program and system testing
           evaluates the system's actual functionality in
            relation to expected or intended functionality
           Done systematically and results documented
            carefully
           Avoid patches delivery after software release
Implementation

    Installation
        Conversion strategy
             Direct, parallel or pilot conversion
        Training plan
             Helping users accomplish their tasks
        Support plan
             On-demand training , online support or helpdesk
Waterfall SDLC model
  One of the classic approach
  describes a development method that is linear
   and sequential
  Once the work has started and down to next
   phrase, it cannot turn back
  Advantage
        allows for departmentalization and managerial
         control
        without any overlapping or iterative steps
    Disadvantage
        not allow for much reflection or revision
Waterfall SDLC model
Project Team Roles