Information system analysis and design

Slides:



Advertisements
Similar presentations
Chapter 11 Describing Process Specifications and Structured Decisions
Advertisements

Systems Analysis Requirements structuring Process Modeling
CSC 123 Systems Analysis & Design
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Chapter 4 Enterprise Modeling.
L ECTURE 12 – P ROCESS S PECIFICATION Definition, Motivation and Elements Structured English Decision Tables Decision trees Software Project Management.
Chapter 4.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Systems Analysis and Design 9th Edition
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
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
Data and Process Modeling
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
© Copyright 2011 John Wiley & Sons, Inc.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Chapter 4.
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
File and Database Design; Logic Modeling Class 24.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Systems Analysis and Design 10th Edition
Chapter 9 Structuring System Requirements: Logic Modeling
Prof. Mohammad Moizuddin
Data and Process Modeling
MBI 630: Class 6 Logic Modeling 9/7/2015. Class 6: Logic Modeling Logic Modeling Broadway Entertainment Co. Inc., Case –Group Discussion (Handout) –Logic.
Chapter 9 Describing Process Specifications and Structured Decisions
Phase 2: Systems Analysis
The Structured Specification. Why a Structured Specification? System analyst communicates the user requirements to the designer with a document called.
Chapter 11 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall and Kendall Fifth Edition.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Structured Analysis.
CORE 1: PROJECT MANAGEMENT Designing. This stage is where the actual solution is designed and built. This includes describing information processes and.
+ Information Systems and Databases 2.2 Organisation.
Chapter 4 enterprise modeling
CHAPTER 5 1 DATA AND PROCESS ANALYSIS. Chapter Objectives Describe data and process modeling concepts and tools, including data flow diagrams, a data.
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
Systems Analysis and Design 8th Edition
© 2005 by Prentice Hall Chapter 9 Structuring System Requirements: Logic Modeling Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
To play, start slide show and click on circle Access 1 Access 2 Access 3 Access 4 Access Access
Business System Development
Tools Of Structured Analysis
Data dictionary Chapter 8.
Business Process Modeling
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Software Specification Tools
Process Specifications and Structured Decisions
Chapter 9 Structuring System Requirements: Logic Modeling
Data Dictionaries ER Diagram.
Process Analysis I: Flow Charts, Decision Tables, Decision Trees
Databases and Information Management
MANAGING DATA RESOURCES
CIS 210 Systems Analysis and Development
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Lessons Vocabulary Access 2016.
Describing Process Specifications and Structured Decisions
Databases and Information Management
Information Systems Development MIS331
Chapter 11 Describing Process Specifications and Structured Decisions
Chapter 9 Structuring System Requirements: Logic Modeling
Chapter 9 Structuring System Requirements: Logic Modeling
Databases and Information Management
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Information system analysis and design Dr. Dina Tbaishat

Recap Last two lectures we looked at DFDs as a graphical tool to look at what happens in a system Today we shall look at data dictionaries and other tools used to analyse structured decisions ; these are: decision tables, decision trees and structured English)

Data Dictionaries Can be called meta data repository Data dictionary provides a descriptive list of names, definitions, and attributes of data elements to be captured in an information system This indeed helps programmers understand the system Data dictionary is built for certain context, it associates context with elements of the structure Used to develop and maintain a database

Data dictionary benefits: Improved data quality Improved documentation and control Reduced data redundancy Reuse of data Consistency in data use Easier data analysis Improved decision making based on better data Simpler programming

Field name Data type Other information Customer ID Auto-number Primary key Name Text Size: 15 Number Size: 10

Decision Tables Decision tables are used to model complicated programming logic. They can make it easy to see that all possible combinations of conditions have been considered; when conditions are missed, it is easy to see this. In the top left corner the conditions are listed, they can be in the form of a question with a Yes or No answer or simply, given some alternative (ex: Male and Female) In the bottom left part actions are listed The combinations of responses are called rules (the columns)

If there are n conditions, there are 2n rules (columns), ex: 2 conditions  22 =2 x 2 = 4 rules)

Condition one Y N Condition two Action 1 X Action 2 Action 3

Powerful presentation Less errors Decision tables are appropriate when the number of actions is large – they handle complexity better Group related rules into single table and combine tables to achieve decisions However, they have less graphical structure and not very easy to construct (compared to decision trees) No indication is given about the sequence of actions

Decision Trees A diagram that is read from left to right. The leftmost node in a decision tree is called the root node The branches from a decision node to the right represent the set of decision alternatives that are available One, and only one, of these alternatives can be selected The small circles in the tree are called chance nodes

The number shown in parentheses on each branch of a chance node is the probability that the outcome shown on that branch will occur at the chance node The right end of each path through the tree is called an endpoint

Structured English Using English language with the syntax of programming, to represent the logic of the system It can be kept in automated format For beginners, it might take time to build It also seems to be more formal than it is An example is shown next:

Process 1.1 - Validate Customer Enter customer number Seek customer number in Customer file if customer number found then    create order record in Order file    go to process 1.2 else    display error message    ask user if he/she wants to create new customer record in Customer file    if yes then       go to process 1.3    else       terminate order entry process    endif endif