Lecture 23 CS 507.

Slides:



Advertisements
Similar presentations
1 9 Moving to Design Lecture Analysis Objectives to Design Objectives Figure 9-2.
Advertisements

Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
SYSTEMS ANALYSIS AND DESIGN TOOLS
Systems Documentation Techniques
ITEC113 Algorithms and Programming Techniques
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition © 2005 Pearson Prentice.
Chapter 9 Describing Process Specifications and Structured Decisions
Advanced Accounting Information Systems
Computers: Information Technology in Perspective By Long and Long Copyright 2002 Prentice Hall, Inc. Developing Business Information Systems Chapter 11.
Lesson-21Process Modeling Define systems modeling and differentiate between logical and physical system models. Define process modeling and explain its.
Systems Analysis I Data Flow Diagrams
Introduction to Computer Technology
Copyright © 2016 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior written consent of McGraw-Hill Education.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
1 Chapter 2 Revision: Documentation DFD System FC.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Chapter 9 Describing Process Specifications and Structured Decisions
Lecture 6 Data Flow Modeling
Process Models: Data Flow Diagrams Chapter 2. Process Modeling Objective: Understand the concept of business processes Understand and create Data Flow.
Systems Analysis and Design
Flowcharting A Quality Improvement Tool. Quality = Inspection Statistical methods assisted in prevention of defects – The need for inspection declined.
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
Advanced Accounting Information Systems
Hoi Le. Why database? Spreadsheet is not good to: Store very large information Efficiently update data Use in multi-user mode Hoi Le2.
Learning Objectives Today we will Learn: How to identify the data requirements of a IT system using a Data Flow Diagram.
Learning Objectives Today we will Learn: The different types of test data.
 Problem Analysis  Coding  Debugging  Testing.
Systems Analysis and Design in a Changing World, Fourth Edition
Introduction to DBMS Purpose of Database Systems View of Data
The Components of Information Systems
Tools Of Structured Analysis
Chapter 11 Designing Inputs, Outputs, and Controls.
Chapter 6 The Traditional Approach to Requirements.
Modern Systems Analysis and Design Third Edition
Chapter 1: Introduction
Fundamentals of Information Systems, Sixth Edition
Architecture Concept Documents
Chapter 6 Data flow diagramming ACCOUNTING INFORMATION SYSTEMS
Computer Aided Software Engineering (CASE)
Modern Systems Analysis and Design Third Edition
DATA MODELS.
System Design.
Programming Flowcharts
Chapter Ten Managing a Database.
Developing Information Systems
SDLC Phase III: Structuring System Requirements
Algorithms An algorithm is a sequence of steps written in the form of English phrases that specific the tasks that are performed while solving the problem.It.
Lecture 2 Introduction to Programming
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
The Components of Information Systems
Basic Concepts in Data Management
Unit# 9: Computer Program Development
Introduction to Systems Analysis and Design
Modern Systems Analysis and Design Third Edition
Structured Program Design
Modern Systems Analysis and Design Third Edition
CSC128 FUNDAMENTALS OF COMPUTER PROBLEM SOLVING
Analysis models and design models
Introduction to DBMS Purpose of Database Systems View of Data
SYSTEM ANALYSIS & DESIGN PHASE
Systems Design Project Deliverable 3
Chapter 11 Describing Process Specifications and Structured Decisions
Chapter 4: documenting information systems
Chapter 22, Part
Information System Building Blocks
Documenting Accounting Information Systems
Flowchart Symbols DFD Symbols Processes Input/Output Storage
Presentation transcript:

Lecture 23 CS 507

System Design Designing usable and complete input Designing file or database Designing user interface (input screen as it would be seen by the user) Designing well defined and usable output with flexibility to redefine presentation of outputs in any form.

Designing Usable and Complete Input The input forms should be Accurate Easy to use Consistent Simple Preferably the input forms should be as much near to what is already being used by a business. Primary parameters should also be defined as part of input design e.g. basic information pertaining to various entities suppliers, customers, employees and chart of accounts.

Designing Output Designing should focus on Assuring purposeful output Providing output as defined and required by users Providing appropriate information Assuring distribution of output as per client specified requirements. Minimize throughput time and Query time. Ensuring that output is available in client required mode.

Designing File or Database Accessibility – data is accessible when the user wants to use it. Consistency – data updates in master file will automatically update the data in the whole system. Efficiency -- data is efficiently processed & stored Integrity – correctness of data

Designing User Interface Design should allow the users to access the system in a way that is according to their individual needs. The information should be entered in a logical sequence.

Benefits of Good System Design Better understanding by the developer of the system. System development becomes efficient. Early detection of problems in critical areas, if any. Better quality of reporting formats. Modifications can be made easily in the system. Little maintenance is required in the operations phase.

System Analysis & Design Methods Two approaches are followed for system analysis and design Structured analysis and design – Which includes various tools, such as. Flowcharting Data Flow diagram (DFD) Entity Relationship Diagram (ERD) Object oriented analysis and design

Structured Analysis and Design Structured analysis and design follows a set of good practices and generally accepted standards Proper documentation of the system is made by following the standard rules

Flow Chart "A schematic representation of a sequence of operations, as in a manufacturing process or computer program."

Symbols Arrow Terminator

Symbols Process Decision

Symbols Connectors Predefined Process

Symbols Single Document Off-Page Connector Input / Output

Symbols Input / Output