Modeling System Requirements:

Slides:



Advertisements
Similar presentations
Systems Analysis and Design in a Changing World, 6th Edition
Advertisements

Alternative Approach to Systems Analysis Structured analysis
Chapters 7 & 9 System Scope
Systems Analysis and Design 8th Edition
Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain how.
MIS 210 Fall 2004Sylnovie Merchant, Ph. D. Lecture 4: Data Modeling Process Modeling MIS 210 Information Systems I.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Modeling System Events Adapted from: Systems Analysis and Design in a Changing World, 2nd Edition by John W. Satzinger, Robert Jackson and Stephen Burd.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Systems Analysis and Design in a Changing World, 6th Edition
Overview Objective: refine information gathered
2Object-Oriented Analysis and Design with the Unified Process Events and Use Cases  Use case  Activity the system carries out  Entry point into the.
Systems Analysis and Design in a Changing World, 6th Edition
6. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how events can be used to identify use cases that define requirements.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Chapter 5: Modeling Systems Requirements: Events and Things
Modeling Systems Requirements: Events and Things.
Modeling System Requirements:Events and Things
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
SA Capstone Requirements and Design Week 5 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso Some slides adapted from: Systems Analysis.
Systems Analysis and Design in a Changing World, Fifth Edition
Systems Analysis and Design in a Changing World, Thursday, Feb 22
Systems Analysis and Design in a Changing World, 6th Edition
SA Capstone Requirements and Design Week 5 SYST Winter 2014
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 9 Moving to Design
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 3 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH CHAPTER.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH SATZINGER.
Chapter 5 Models and UML Notation for The Object-Oriented Approach.
Systems Analysis & Design 7 th Edition Chapter 5.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
1 ITEC 3010 “Systems Analysis and Design, I” LECTURE 5: Modeling System Requirements [Prof. Peter Khaiter]
Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain.
Modeling system requirements. Purpose of Models Models help an analyst clarify and refine a design. Models help simplify the complexity of information.
1 6 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 6 The Traditional Approach to Requirements.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Modeling System Requirements: Events and Things. Objectives Explain the many reasons for creating information system models Describe three types of models.
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 3 Use Cases.
1 Chapter 5 Modeling System Requirements Finding the Use Cases Page
Software Engineering Software Engineering - Mr. Ahmad Al-Ghoul.
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
1 Models and Modeling A model: a representation of some aspect of the system being built A variety of models –Many are graphical (e.g. Data flow diagram,
CIS 321—IS Analysis & Design Chapter 5: Modeling System Requirements—Events and Things.
Chapter 4 Basic Object-Oriented Concepts. Chapter 4 Objectives Class vs. Object Attributes of a class Object relationships Class Methods (Operations)
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
DATA REQIREMENT ANALYSIS
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 6 The Traditional Approach to Requirements.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Modeling System Requirements: Chapter 5 Modeling System Requirements: Events and Things Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Objectives Explain the many reasons for creating information system models Describe three types of models and list some specific models used for analysis and design Explain how events can be used to define system requirements Identify and analyze events to which a system responds Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Objectives Explain how the concept of things in the system also defines requirements Explain the similarities and the differences between data entities and objects Identify and analyze data entities and objects needed in the system Read, interpret, and create an entity-relationship diagram Read, interpret, and create a class diagram Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Models and Modeling Analyst describes information system requirements using a collection of models Complex systems require more than one type of model Models represent some aspect of the system being built Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Reasons for Modeling Figure 5-2 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Types of Models Different types of models are used in information systems development Mathematical - formulas that describe technical aspects of the system Descriptive - narrative memos, reports, or lists that describe aspects of the system Graphical - diagrams and schematic representations of some aspect of the system Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Overview of Models Used in Analysis and Design Analysis phase activity named “define system requirements” Logical models Provide detail without regard to specific technology Design phase Physical models Provide technical details Extend logical models Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Events and System Requirements Occurrences at a specific time and place Trigger all system processing Requirement definition Determine relevant events External events first Temporal events second Decompose system into manageable units Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Events Affecting a Charge Account Processing System Figure 5-6 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Types of Events External Temporal State Outside system Initiated by external agent or actor Temporal Occurs as result of reaching a point in time Based on system deadlines State Something inside system triggers need for processing Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

External Event Checklist Figure 5-7 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Temporal Event Checklist Figure 5-8 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Identifying Events Can be difficult to determine Often confused with conditions and responses May be useful to trace a transaction’s life cycle Certain events left to design phase Systems controls Perfect technology assumption Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Sequence of Actions that Lead up to Only One Event Affecting the System Figure 5-9 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

The Sequence of “Transactions” for One Specific Customer Resulting in Many Events Figure 5-10 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Events Deferred Until the Design Phase Figure 5-11 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Information about each Event in an Event Table Figure 5-14 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Things and System Requirements What system information needs to be stored Outcomes Understanding of system Set of models Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Types of Things Figure 5-16 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Developing an Initial List of Things Step 1: Identify all nouns about the system Step 2: Add items or categories of information needed Step 3: Refine list and record assumptions or issues to explore Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Characteristics of Things Relationship Naturally occurring association among specific things Occur in two directions Cardinality/multiplicity Binary, unary, ternary, n-ary Attribute One specific piece of information about a thing Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Relationships Naturally Occur Between Things Figure 5-18 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Attributes and Values Figure 5-20 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Data Entities Things the system needs to store data about in traditional IS approach Modeled with entity-relationship diagram Generally used with relational database development Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Objects Do the work in the system and store information Behaviors and attributes Class: Type of thing Object: Specific thing Methods: Behaviors of objects Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Data Entities Compared with Objects Figure 5-21 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Simple ERD Figure 5-22 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Cardinality Symbols of Relationships Figure 5-23 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Expanded ERD with Attributes Shown Figure 5-24 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Customers, Orders, and Order Items Figure 5-25 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

The Class Diagram Classes objects rather than data entities Generalization/specialization hierarchies General superclasses to specialized subclasses Inheritance allows subclasses to share characteristics of their superclasses Aggregation (whole-part hierarchies) Relates objects and its parts Defines object in terms of its parts Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

A Generalization/Specialization Hierarchy for Motor Vehicles Figure 5-29 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Aggregation or Whole-Part Relationships Figure 5-31 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

for the Class Diagram Figure 5-32 The Class Symbol for the Class Diagram Figure 5-32 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Bank Account System Class Diagram Figure 5-33 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd

Enrollment Class Diagram with Association Class Figure 5-34 Systems Analysis and Design in a Changing World, 2nd Edition, Satzinger, Jackson, & Burd