SAD

• Systems development


  A systematic process which includes phases such as planning, analysis, design, deployment, and maintenance
• Systems Analysis


  A process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components
• System Analysis


  Specifies what the system should do
• Systems Design


  A process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements
• System Design


  Focuses on how to accomplish the objective of the system
• System Analysis and Design (SAD) focuses on

  • Systems analysis
  • Systems design
  • Systems
  • Processes
  • Technology
• System


  An orderly grouping of interdependent components linked together according to a plan to achieve a specific goal
• Constraints of a System

  • Structure
  • Behavior
  • Objectives
• Properties of a System

  • Organization
  • Interaction
  • Interdependence
  • Integration
  • Central Objective
• Elements of a System

  • Inputs and Outputs
  • Processor(s)
  • Control
  • Feedback
  • Environment
  • Boundaries and Interface
• Types of Systems


  • Physical or Abstract Systems
  • Open or Closed Systems
  • Adaptive and Non Adaptive System
  • Permanent or Temporary System
  • Natural and Manufactured System
  • Deterministic or Probabilistic System
  • Social, Human-Machine, Machine System
• Man-Made Information Systems


  An interconnected set of information resources to manage data for particular organization, under Direct Management Control (DMC)
• Types of Man-Made Information Systems

  • Formal Information System
  • Informal Information System
  • Computer Based System
• Types of System Models

  • Schematic Models
  • Flow System Models
  • Static System Models
  • Dynamic System Models
• Categories of Information


  • Strategic Information
  • Managerial Information
  • Operational information
• System Development Method: Structured Analysis, Object Oriented Analysis, Agile / Adaptive Method
• Structured Analysis


  • Represents the system in terms of data and the processes that act upon that data
  • System development is organized into phases, with deliverables and milestones to measure progress
  • It is called process centered technique because it focuses on processes that transform data into useful information
  • Modelling tool - Data Flow Diagram (DFD)
• Object Oriented Analysis


  • Views the system in terms of objects that combine data and processes
  • The objects represent actual people, things, transactions, and events
  • O-O phases tend to be more interactive
  • Modelling tool - Various object-oriented diagrams
• Agile/Adaptive Methods


  • Breaks development process down into cycles, or iterations that add functionality
  • Each iteration is designed, built, and tested in an ongoing process
  • Attempts to reduce major risks by incremental steps in short time intervals
  • Modelling tool - Tools that enhance communication, such as collaborative software, brainstorming, and whiteboards, business process modeling
• Structured Analysis is NOT based on the principle of Bottom-Up Approach
• Waterfall method is a fairly rigid approach, good for traditional type of projects, and not as good for many of the new types of interactive and highly complex applications
• Main goal of the object-oriented approach

  Reusability
• Agile methods seem to work best when team members have a relatively high skill level
• Disadvantage of Agile Methodology: Documentation and designing take a back seat
• System Development Life Cycle (SDLC)

  1. Planning

  2. Analysis

  3. Design

  4. Development

  5. Testing

  6. Implementation

  7. Maintenance
• SDLC of Clinic Management System: Project Initiation

  1. Head of Outpatient Clinic (Client) has a business idea to enhance the current system and sends a formal request to IT dept

  2. Head of IT Department (Project Manager) arranges a meeting/discussion
• SDLC of Clinic Management System: Planning


  1. Understand the problem and why the system should be developed

  2. Deliverables: Feasibility Analysis/Study, Project plan, Gantt Chart, Cost and Benefit Report

  3. Project manager and client bring the system request and feasibility analysis to the steering committee for approval

  4. Staff project (Designer, Programmer, DBA, Software tester, Network Manager)

  5. Create work breakdown structure, Identify scope, Identify and manage risk, Gather requirements (interviews, questionnaire, observation)
• SDLC of Clinic Management System: Analysis

  1. Discuss the requirements gathered in detail (Functional and non-functional requirement)

  2. Develop Requirements Definition, Use cases, Data Flow Diagrams, Entity Relationship Model (ER-D)

  3. Deliverable: Software Requirement Specification (SRS)
• SDLC of Clinic Management System: Design


  1. Architecture design (Client side, server side, web-based)

  2. User interface design (layout, color scheme)

  3. Program design (programming language: ASP)

  4. Framework (Javascript, MySQL, MariaDB)
• System Development Methods include Structured Analysis, Object Oriented Analysis, and Agile/Adaptive Methods
• Structured Analysis


  • Represents the system in terms of data and the processes that act upon that data
  • System development is organized into phases, with deliverables and milestones to measure progress
  • It is called process centered technique because it focuses on processes that transform data into useful information
  • Modelling tool - Data Flow Diagram (DFD)
• Object Oriented Analysis


  • Views the system in terms of objects that combine data and processes
  • The objects represent actual people, things, transactions, and events
  • O-O phases tend to be more interactive
  • Modelling tool - Various object-oriented diagrams
• Agile/Adaptive Methods


  • Breaks development process down into cycles, or iterations that add functionality
  • Each iteration is designed, built, and tested in an ongoing process
  • Attempts to reduce major risks by incremental steps in short time intervals
  • Modelling tool - Tools that enhance communication, such as collaborative software, brainstorming, and whiteboards, business process modeling
• The SDLC waterfall model typically consists of five phases: Planning, Analysis, Design, Development, Testing, Implementation, Maintenance
• Planning


  1. Identify problem

  2. Gather requirement
• Analysis


  Analyze detail requirement
• Design


  1. System server design

  2. Database relationship

  3. Business rule – clear session on logout

  4. User interface Layout

  5. Color scheme

  6. Programming Language

  7. Supported browser
• Development


  Developer start writing code
• Testing


  1. Validate all the requirement has been met

  2. Make sure all the functionality are working as expected

  3. Find as many possible bug
• Implementation


  Real user use the application