Www.monash.edu.au IMS1805 Systems Analysis Topic 3: Doing analysis (cont from Monday)

Slides:



Advertisements
Similar presentations
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Advertisements

IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Managing Data Resources
IMS1805 Systems Analysis Topic 2: Introduction to some key techniques for systems analysis in IS.
IMS1805 Systems Analysis Topic 4: How do you do it? Guidelines for doing analysis (continued from last week)
© 2005 by Prentice Hall Chapter 3a Database Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
System Design and Analysis
IMS1805 Systems Analysis Topic 3: Doing analysis (cont from Monday)
IMS1805 Systems Analysis Topic 3 (revisited and continued): Doing analysis – a ‘soft’ systems perspective.
IMS1805 Systems Analysis Topic 3: Doing analysis (cont)
Data Management Design
IMS1805 Systems Analysis Topic 4: How do you do it? Guidelines for doing analysis.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
Chapter 2 Topics –Context-Level DFD –Entity-Relationship Diagrams.
IMS1805 Systems Analysis Topic 1(c): Analysis and Information Systems.
WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.
IMS1805 Systems Analysis Topic 6: Analysis as a process within a process.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
IMS1805 Systems Analysis Topic 3: Doing analysis (cont from last week)
IMS1805 Systems Analysis Topic 2: Introduction to some key techniques for systems analysis in IS.
Information Storage and Retrieval CS French Chapter 3.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Chapter 7 Structuring System Process Requirements
6 Systems Analysis and Design in a Changing World, Fourth Edition.
UML CLASS DIAGRAMS. Basics of UML Class Diagrams What is a UML class diagram? Imagine you were given the task of drawing a family tree. The steps you.
Technology and Enterprise Systems Forms and attributes: A system is a combination of parts that work together to achieve a specific result. Some systems.
Systems Analysis and Design in a Changing World, Fifth Edition
Entity-Relationship modeling Transparencies
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
Chapter 6 The Traditional Approach to Requirements
Entity-relationship Modeling Transparencies 1. ©Pearson Education 2009 Objectives How to use ER modeling in database design. The basic concepts of an.
Systems Analysis and Design in a Changing World, Fifth Edition
5.1 © 2007 by Prentice Hall 5 Chapter Foundations of Business Intelligence: Databases and Information Management.
DATA MODELLING TOOLS FOR ORGANISING DATABASES. For a database to be organised and logical, it must be well-designed and set out. In such cases, the databases.
Chapter 5CSA 217 Design in Construction Chapter 5 1.
Systems Analysis and Design in a Changing World, Fifth Edition
Concepts of Database Management, Fifth Edition Chapter 1: Introduction to Database Management.
Business Process Management. Key Definitions Process model A formal way of representing how a business operates Illustrates the activities that are performed.
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
ITEC224 Database Programming
Section 11 : Normalisation
Chapter 9 Designing Databases Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
2005 SPRING CSMUIntroduction to Information Management1 Organizing Data John Sum Institute of Technology Management National Chung Hsing University.
Lecture 2 An Overview of Relational Database IST 318 – DB Admin.
5 Systems Analysis and Design in a Changing World, Fourth Edition.
10/3/2012ISC329 Isabelle Bichindaritz1 Logical Design.
CORE 2: Information systems and Databases NORMALISING DATABASES.
I Information Systems Technology Ross Malaga 4 "Part I Understanding Information Systems Technology" Copyright © 2005 Prentice Hall, Inc. 4-1 DATABASE.
Lecturer: Gareth Jones. How does a relational database organise data? What are the principles of a database management system? What are the principal.
ICT Assessment – Key stage 3 ICT Meeting 14/12.09.
Chapters 15 &16 Conceptual and Logical Database Design Methodology.
GLOBAL SCHOOL OF PROJECT MANAGEMENT UNIVERSITY FOR INTERNATIONAL COOPERATION Ing. Osvaldo A. Martínez Gómez, MAP, MSc. Essential Topics - Project Management.
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.
Chapter 8 Configuring and Managing Shared Folder Security.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Chapter 10 Designing Databases. Objectives:  Define key database design terms.  Explain the role of database design in the IS development process. 
Information Design Trends Unit 4 : Sources and Standards Lecture 1: Content Management Part 1.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Lecture 3 : Hard Systems Modelling UFCE8V-20-3 Information Systems Development SHAPE Hong Kong 2010/11.
Logical Design 12/10/2009GAK1. Learning Objectives How to remove features from a local conceptual model that are not compatible with the relational model.
Guide to Functional Decomposition
1 CS 430 Database Theory Winter 2005 Lecture 3: A Fifty Minute Introduction to Data Modeling.
Lesson 10 Databases.
DATA REQIREMENT ANALYSIS
Unified Modeling Language
IST 318 Database Administration
Presentation transcript:

IMS1805 Systems Analysis Topic 3: Doing analysis (cont from Monday)

2 Recap of last lecture The importance of understanding the purpose of analysis Some important purposes: Organisational; Technological; Development team The purposes behind process models (FDD/DFD)

3 Agenda Aim: To develop further your understanding of the main purposes for which IS analysis is done To identify the purpose of diagram-based data analysis techniques in IS To work through some examples of the use of process-oriented and data-oriented analytical techniques

4 2(c) Why draw data models? Data models enable us to focus on: the information which needs to be stored about things in a system; and the information inter-connections which have to maintained between these things Entity-relationship diagrams tell us what things (entities) we need to store information about, and what the characteristics are of the relationships between these things

5 Data in organisations Organisations always have to store data about things Every entity has many attributes associated with it Key data items may be used very widely across an organisation for a huge range of purposes (often unrelated) by a wide variety of people Inconsistencies in data between different parts of an organisation may lead to confusion and inefficiencies in storages

6 Analysing data in organisations We analyse entities: To identify all the entities which have to be stored and the attributes of each one To define what linkages (relationships) must be kept between these entities and what rules apply to these relationships By doing this, we aim to: Develop a sound basis for design and construction of databases to store information consistently and non- redundantly Identify areas of shared data/overlapping and conflicting data needs Determine the rules for validating data in databases

7 2(c): Data Models: Reminder of E-R basics (covered in database unit) Entities are represented as boxes Every entity is connected in the hierarchy can be broken down (decomposed) into the connected processes (functions) on the level below Every process (function) in the hierarchy is a component of the process (function) to which it is connected on the level above

8 Why draw an FDD (organisational purpose)? All human processes are done by combining a number of simpler processes (catching a ball example) FDD enables us to identify the many simple individual processes which make up a complex system Going up the hierarchy allows us to see how many different activities contribute to higher- order processes

9 Why draw an FDD (technological purpose)? Computers can only perform very simple operations (read input, write output, add, compare); packaged software can do more complex tasks, but only what it is designed for Therefore, any human information processing task needs to be decomposed into the simple operations which the computer can do or the standard tasks the package can do FDD enables us to break complex human information processes into the simpler operations which a computer can do

10 Why draw an E-R diagram (team purpose)? Development of a complex system will include storage of many data items in complex data structures – multiple databases/database tables/database fields/etc Breaking the development into component pieces allows different members of the development team to work simultaneously on different parts An FDD enables the development team to break a large information system into separate components, while ensuring everyone knows where each component fits