What is a Relationship Map?

Slides:



Advertisements
Similar presentations
CAPE INFORMATION TECHNOLOGY – Unit 2
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
IFS310: Week 3 BIS310: Structured Analysis and Design 5/4/2015 Process Modeling and Data Flow Diagrams.
Chapter 7 Structuring System Process Requirements
Data Flow Diagram Purpose – visually depict how data moves and changes through a top-down, logical model Logical model – requirements and the relationship.
ACG 4401 Data Modeling: Data Flow Diagrams Flow Charts.
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
How to : Data Flow Diagrams (DFDs)
Visual Formal Methods R J Walters. Introduction Motivation The Language The tools An example Conclusion.
IS IS 788 [Process] Change Management  Wednesday, September 9  Pacific Bell Case – Ricky Medina  Lecture: Modeling Organizations (2 of 2)
RWJF Common Ground-Using Work Flow Mapping Tools to Improve Chronic Disease Management Processes Adapted from presentations by: Minnesota Department of.
Use Case Diagram (UCD) Yong Choi BPA.
Chapter 7 Structuring System Process Requirements
Data Flow Diagrams (DFDs). Data flow diagram (DFD) is a picture of the movement of data between external entities and the processes and data stores within.
ICOM 5016 – Introduction to Database Systems Lecture 4 Dr. Manuel Rodriguez Department of Electrical and Computer Engineering University of Puerto Rico,
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
SDLC Phase II: Structuring System Requirements IS 582 Dr. Dania Bilal Spring 2008.
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
Chapter 7 Structuring System Process Requirements
Department of Electrical Engineering and Computer Science University of Central Florida Fall 2014.
Staffordshire UNIVERSITY School of Computing Version Jan 08 original by K.Ingram & J.Westlake1 Use Case Diagrams What are they? What do they look like?
DFDs vs. Use Case Modeling COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University.
1 Structuring Systems Requirements Use Case Description and Diagrams.
Systems Analysis and Design in a Changing World, 6th Edition
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Social Roles and Relationships.
How can you multiply a two digit by digit number using an area model?
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.
Literature Circles Introduction.
 Discussion Director: Your role demands that you identify the important aspects of your assigned text and develop questions your group will want to discuss.
Requirements1. Structured Analysis Method Structured system analysis and design (SSAD) Formal structured dev method Developed by UK Gov. in the 1980’s.
Software Analysis 1 PROCESS MODELING: Data Flow Diagrams (DFDs)
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Step 1: Find the Cumulative Frequency for each class. < 99.5 <
Ondřej Přibyl Faculty of Transportation Sciences, CTU DESIGN OF ITS SYSTEMS Project support 1 3 PROJECT SUPPORT Use cases.
Course Instructor: Kashif I hsan 1. Chapter # 6 2.
Locate your Inner Asset Yellow Belt Ninja - Quest for the Strategic Guru.
Use Cases. 2 A use case... –Specifies the behavior of a system or some subset of a system. –Is a system-level function. –Does not indicative how the specified.
DBM 380 Week 3 DQ 2 Why do you think the use of icons in entity-relationship diagrams as described in the Masri (2008) article resulted in a better understanding.
You are a newly hired employee for Arkansas Entergy.
WHAT IS A Context Diagram?
Business Process and Functional Modeling
Analysis Classes Unit 5.
5/11/2018.
WHAT IS A Process Map? Illustration of the sequence of activities, inputs and outputs to the activities, and relationship across multiple functions, or.
Business System Development
Structuring System Process Requirements
Business System Development
IS 334 information systems analysis and design
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
CH#3 Software Designing (Object Oriented Design)
Concept Maps.
CBSE 2014 Modeling Components with UML
BUTTERFLY EFFECT DIAGRAM
Chapter 9 Use Cases.
Object Oriented Analysis and Design
Use Cases.
COP 4331 Recitation #1 University of Central Florida
WHAT IS A Use Case Diagram?
Name of Famous Explorer
CIS 375 Bruce R. Maxim UM-Dearborn
Systems Design Project Deliverable 3
Political Effects of Colonization
STEP ONE. STEP ONE. STEP ONE. STEP ONE. STEP ONE. 02
Introduction to IFSM 303 Human Factors in Computer Systems Design
Requirements I Peter Dolog dolog [at] cs [dot] aau [dot] dk
Keng Siau Department of Management University of Nebraska - Lincoln
COP 4331 Recitation #1.
Presentation transcript:

What is a Relationship Map? A high-level, broad depiction of the connections or exchange between business entities or functions Also known as: Business Interaction Model Organizational Context Diagram Organizational Relationship Map

EXAMPLE

Step 1: Identify Entities Make a list of entities For each entity, draw a box The entity name is placed inside the box Entities can be: Departments Groups Business units Computer applications that have automated processes Stakeholder roles

Step 2: Connect the Entities Draw lines to connect entities With arrowheads OR Without arrowheads

Step 3: Label the Connections Add text labels on the line connectors to describe why a relationship exists

Step 4: Identify Boundary Group similar or closely-related entities Boundary is not itself an Entity