Untitled Quiz

Seventh Edition Systems Analysis and Design

• Covers systems analysis and design in a changing world
• Authored by John Satzinger, Robert Jackson, and Stephen Burd
• Copyright 2016, Cengage Learning

Lecture 1 - Systems Analysis and Design (SAND6221)

• Lecturer: Zahra Bulbulia
• Email: [email protected]
• WhatsApp: 0761185552

Chapter 1: Outline

• Software development and systems analysis and design
• Systems development lifecycle (SDLC)
• Iterative development
• Introduction to Ridgeline Mountain Outfitters (RMO)
• Developing RMO's Tradeshow Systems
• Where you are headed - the rest of the book

Learning Objectives (1 of 2)

• Describe the purpose of systems analysis and design when developing information systems
• Explain the purpose of the system development life cycle and identify its six core processes
• Explain how information system methodologies provide guidelines for completing the six core processes
• Describe the characteristics of Agile methodologies and iterative system development

Learning Objectives (2 of 2)

• Based on the Ridgeline Mountain Outfitters Tradeshow System example:
  • Describe how the six core processes of the SDLC are used in each iteration
  • Identify key documents used in planning a project
  • Identify key diagrams used in systems analysis and systems design

Overview

• Focuses on developing information systems that solve organizational needs
• Chapter 1 details the process of developing a smaller information system
• Remainder of the textbook expands on the basic processes introduced in chapter 1

Software Development (1 of 3)

• Computer application (app): A software program running on a computer carrying out specific functions.
• Modest scope
• Information system: A set of interconnected components that collect, process, store, and provide information to complete business tasks. A broader concept than an app and includes databases and related manual processes.

Software Development (2 of 3)

• Systems analysis: Activities to understand and specify an information system's purpose.
• Systems design: Activities to define and detail the system.

Software Development (3 of 3)

• Seven activities:
  • Understand the need (business need)
  • Capture the vision
  • Define a solution
  • Communicate the vision and solution
  • Build the solution
  • Confirm that the solution meets the need
  • Launch the solution system

System Development Life Cycle (SDLC) (1 of 3)

• The process for building, starting, and maintaining an information system.
• Six core processes:
  • Identify the problem or need and obtain approval
  • Plan and monitor the project
  • Discover and understand the problem/need details
  • Design the system components to solve the problem
  • Build, test, and integrate system components
  • Complete system tests and deploy the solution

System Development Life Cycle (SDLC) (2 of 3)

• Project: A planned undertaking with a beginning and end, producing a result (an information system).
• Requires knowledge of systems analysis and systems design tools and techniques.

System Development Life Cycle (SDLC) (3 of 3)

• System development process (methodology): The actual approach used to develop the information system. Includes:
  • Unified process (UP)
  • Extreme programming (XP)
  • Scrum
• Most modern methodologies involve Agile and iterative development

Iterative Development

• Agile development: An information system development process emphasizing flexibility to handle new requirements. Fast and responsive to change.
• Iterative development: Developing the system in small parts throughout multiple iterations, refining and adding more until complete.

Ridgeline Mountain Outfitters (RMO) (1 of 2)

• Large outdoor sporting goods retailer.
• Operates through mail order, online, and retail stores in the Rocky Mountain and Western States.
• Includes an extensive e-business component. (Skiing, mountain biking, water sports, hiking, camping, mountain climbing)

Ridgeline Mountain Outfitters (RMO) (2 of 2)

• Website screenshots shown.
• Website features outlined (Shop for clothing, shop for gear, wish list, store locator, my account, my orders, etc).

RMO Tradeshow System (1 of 2)

• Sample project illustrating one iteration of a small project.
• Part of a larger supply chain management system
• Iteratively goes through the six core processes of the SDLC
• Planning for this chapter involves completing one iteration in 6 days.

RMO Tradeshow System (2 of 2)

• Problem: Purchasing agents attend trade shows to buy merchandise.
• Need: An application to easily collect and track information about suppliers and new products.
• Proposed system includes:
  • Supplier information subsystem
  • Product information subsystem

Initial Activities - pre-project

• Identify the problem and document its objective (core process 1).
• Preliminary investigation.
• System Vision Document
• Obtain approval to start the project (core process 1).
• Meeting with key stakeholders (including executive management)
• Decision-making for plan and budget approval.

System Vision Document

• Problem description: Trade shows have become more important.
• System capabilities: Focuses on collecting and storing information about suppliers and products.
• Business benefits: Improved speed and quality of purchase orders, improved communication, facilitating the development of catalogs, and web pages, purchase orders will be quicker to process.

Problem Description

• Trade shows important sources for new products, fashions, and fabrics.
• Obtaining detailed photos, and information about products.
• Facilitating the creation of online product pages.

System Capabilities

• Collecting and storing data about manufacturers/wholesalers (suppliers).
• Collecting data about sales representatives and other personnel.
• Collecting product information
• Taking pictures of products (and uploading stock images.)

Business Benefits

• Improved communication.
• Maintaining current and accurate supplier data
• Correct product information and image availability
• Expedited purchasing orders.

Day 1: Activities

• Core Process 2: Plan the Project
  • Determine major components (e.g., supplier information, product information).
  • Define the iterations and assign each function to an iteration.
  • Decide to do Supplier Subsystem, first.
  • Plan one iteration as it's small and straightforward.
  • Determine team members and their responsibilities.

Work Breakdown Structure

• Steps to discover, understand, and solve the problem in a project.
• Includes meetings with managers and agents
• Includes identifying use cases.
• Includes defining information requirements.
  • Design components of the solution: screens, database creation, architectural elements, and specific program details
  • Build component parts
  • Integrate everything

Day 2: Activities

• Core Process 3: Discover and Understand Details
  • Preliminary Fact-Finding to understand requirements
  • Develop a preliminary list of use cases and a use case diagram.
  • Develop a preliminary list of classes and a class diagram.

Identify Use Cases: Both Subsystems

• Descriptions of use cases for looking up suppliers, contacts, and products.
• Includes entering, updating information.
• Includes uploading product images.

Identify Object Classes: Both Subsystems

• Attributes defining classes (supplier, contact, product, product picture.)
• (supplier name, address, description)
• (contact name , address, email, role)
• (product category, name, description, gender, image)

Preliminary Class Diagram: Both Subsystems

• Relationships between classes (supplier, contact, product, product picture).

Day 3: Activities

• Core Process 3: Discover and Understand Details

  • In-depth fact-finding about requirements
  • Understanding and documenting detailed workflows for each use case

• Core Process 4: Design System Components

  • Define the user experience with screens and report sketches.

Supplier Information Subsystem

• Use cases: Look up supplier, enter/update supplier information, lookup contact information, enter/update contract information.

Activity - Look Up

• Activity diagrams showing how a purchasing agent or the tradeshow system interacts to get the required information.

Draft Screen Layout: Look Up Supplier

• Web search page layout showing fields for supplier's name, product categories, etc.

Day 4: Activities

• Core Process 4: Design System Components
  • Design database schema.
  • Design high-level system architecture (e.g., browser, Windows, Smart phone).
  • Architectural configuration (components)
  • Design the class diagram
  • Subsystem architectural design.

Database Schema (1 of 2)

• Definition of the database table, "Supplier," including key attributes.

Database Schema (2 of 2)

• Definition of the database table, "Contact," including key attributes.

Architectural Configuration Diagram

• Diagram showing the system's high-level structure (browser, internet, internet server, tradeshow systems, subsystem components).

Preliminary Design Class Diagram

• Diagrams showing the classes (e.g., supplier, contact, product) and their relationships.

Subsystem Architectural Design Diagram

• Illustrates the view layer (e.g. SupplierView) and domain layer (e.g. Supplier, and Contact) along with the interactions between them using Javascript, PHP, and SQL.

Notes on Managing the Project

• Diagrams support a multi-level design process
• Designers support each other through diagrams
• Program development occurs concurrently with design activities.

Day 5: Activities

• Core Process 4: Design System Components

  • Continued design details for system components
  • Defining use cases and their related tasks.

• Core Process 5: Build, Test, and Integrate System Components

  • Continuing programming activities (building the system)
  • Performing unit and integration testing

Code Example for One Class

• Example snippet of code from a class (SupplierView)
  • PHP code illustrating methods (constructor, lookup supplier, and display supplier).

Day 6: Activities

• Core Process 6: Complete System Testing and Deploy the System
  • System functional testing
  • User acceptance testing
  • Potential deployment of parts of the system

Workflow of Testing Tasks

• Diagram showing the testing workflow (Start, Create test data, Conduct tests, Document errors and issues, Fix errors, End).

First Iteration Recap

• Six-day iteration for a small project.
• Most iterations are longer (two to four weeks).
• Most projects involved multiple iterations.
• End users involved in Day 1, 2, 3 and 6.
• Days 4 and 5 involve design and programming concurrently.

Core Processes and Iterations

• Table shows the core processes and the iterations they cover.

System Example (Varsity College)

• Varsity College Online Registration System Example
  • System problem/need
  • How the system solved the problem
  • System vision document
  • Description of initial user goals and user case examples.

Where You Are Headed - The Rest of the Book (1 of 7)

• Introduction to Systems Development
• Chapter 1: From Beginning to End (small project overview and iterative development of online registration examples).
• Online Chapter A: The Systems Analyst (role of systems analysts, various systems development concepts, and careers.)

Where You Are Headed - The Rest of the Book (2 of 7)

• Systems Analysis Activities
• Chapter 2: Investigating System Requirements (in-depth description of core process activities).
• Chapter 3: Identifying Use Cases (techniques for use case identification and modeling).

Where You Are Headed - The Rest of the Book (3 of 7)

• Domain Modeling (Techniques for identifying and modeling domain classes, use cases).
• Use Case Modeling (Modeling more detailed information about use cases).
• Online Chapter B: The Traditional Approach to Requirements (Modeling using Data Flow Diagrams.)

Where You Are Headed - The Rest of the Book (4 of 7)

• Essentials of Systems Design
• Chapter 6: Foundations of Systems Design (Design activities, Controls, and Security.)
• Chapter 7: Defining the System Architecture (Understanding the environment, configuring the application.)

Where You Are Headed - The Rest of the Book (5 of 7)

• Advanced Design and Deployment
• Chapter 8: Designing the User Interface (Input and output design).
• Chapter 9: Designing the Database (Schema, tables, data types, and keys).

Where You Are Headed - The Rest of the Book (6 of 7)

• Part IV: Projects and Project Management
• Chapter 10: Approaches to Systems Development (Predictive and adaptive approaches, SDLC models.)
• Chapter 11: Project Planning and Project Management (Core processes 1 and 2.)
• Online Chapter C: Project Management Techniques (NPV Pert charts, PMBOK knowledge areas.)

Where You Are Headed - The Rest of the Book (7 of 7)

• Advanced Design and Deployment
• Chapter 12: Object-Oriented Design (Fundamentals, Design Classes, CRC Cards.)
• Chapter 13: Object-Oriented Design (Use Case Realization, Communication, sequence diagrams, three-layer design).
• Chapter 14: Deploying the New System (Testing, deployment, support activities).

Summary

• This textbook details the development process for information systems.
• Chapter 1 focuses on one small system, its development steps, and the 6 processes in SDLC.

Summary - Terms (1 of 3)

• Terms to review and know: Computer application, Information system, Project, Systems analysis, System design, System development lifecycle (SDLC), Information system development process.

Summary - Terms (2 of 3)

• Agile development, Iterative development, System vision document, Work breakdown structure, Work sequence draft, Use cases, Use case diagram, Object classes.

Summary - Terms (3 of 3)

• Class diagram, Design class diagram, High-level structural design, Database schema, Screen layout.