SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson LIS1510 Library and Archives Automation Issues Systems Analysis Andy Dawson School of Library,

Slides:



Advertisements
Similar presentations
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Advertisements

Chapter 7 Structuring System Process Requirements
© 2005 by Prentice Hall 7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey.
Dataflow modelling: Context and Data Flow Diagrams
Jump to first page Chapter 2 System Analysis - Process Modeling.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
1004INT Information Systems Week 10 Databases as Business Tools.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
SE 555 Software Requirements & Specification Requirements Analysis.
Data Flow Diagrams.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Chapter 7 Structuring System Process Requirements
6 Systems Analysis and Design in a Changing World, Fourth Edition.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
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.
Data Flow Diagrams (DFDs)
Chapter 1: Data Flow Diagram Structuring System Process Requirements
DEPARTMENT OF INFORMATION STUDIES Andy Dawson LIS1510 Library and Archives Automation Issues Systems Analysis Andy Dawson Department of Information Studies,
Structuring System Process Requirements. Learning Objectives Understand the logical modeling of processes by studying examples of data flow diagrams (DFDs).
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
10/12/2001Data Structure1 Relationships Between The Data Flow Diagram and The Systems Design Activities Mohammad A. Rob School of Business and Public Administration.
Data Flow Diagrams.
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
Chapter 7 Structuring System Process Requirements
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 8 Structuring.
Chapter 7 Structuring System Process Requirements
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models. System modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
ITEC224 Database Programming
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
1 14/08/00Arcot Sowmya Software Engineering COMP3111/COMP9008 Data Flow Diagrams.
1 Introduction to Software Engineering Lecture 1.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Modern Systems Analysis and Design Fifth Edition
Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
CS223: Software Engineering
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
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.
Software Engineering Lecture 10: System Engineering.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
7-1 Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition.
Business System Development
Data Flow Diagrams.
Chapter 6 The Traditional Approach to Requirements.
G063 - Data flow diagrams.
Business System Development
Process Modelling Chapter 6.
Structuring System Requirements: Process Modeling
Chapter 1: Data Flow Diagram Structuring System Process Requirements
Abstract descriptions of systems whose requirements are being analysed
تحلیل سیستم‌ها مدل‌سازی پردازشی.
System models October 5, 2005.
G063 - Data flow diagrams.
University of Houston-Clear Lake
Public Management Information Systems System Analysis & Design Tuesday, December 04, 2018 Hun Myoung Park, Ph.D. Public Management & Policy Analysis.
Chapter 7: Data Flow Diagram Structuring System Process Requirements
Information Systems Development (ISD) Systems Development Life Cycle
System Design and Acquisition
Public Management Information Systems System Design Monday, July 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Presentation transcript:

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson LIS1510 Library and Archives Automation Issues Systems Analysis Andy Dawson School of Library, Archive & Information Studies, UCL School of Library, Archive & Information Studies, UCL (University of Malta 2008)

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson What we will be looking at today The lifecycle concept The need for good analysis Describing the system Identifying the needs Practical exercise – process modelling

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Analysis Design Implementation Evaluation Decay Replacement The system life cycle (from yesterday)

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson The systems development lifecycle Strategic study Feasibility study Physical systems analysis Logical systems definition Logical systems design Physical systems design Implementation Maintenance

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Or more simply (Requirements) analysis Design Implementation Maintenance

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson The PARIS model Plan Ask Record Interpret Specify

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson As we said yesterday... Why do so many systems seem to “fail”? Misapprehension Miscommunication Misinterpretation Misidentification Misrepresentation

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson The role of Systems Analysis Systems analysis allows/helps us to: –identify systems –break them down –make them work (better) Good systems analysis helps organisations to succeed Necessary precursor to proper system selection

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Requirements Analysis Identify elements Model elements Verify Importance of Conceptual Modelling - Independence from physical implementation

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson The focus of analysis Systems tend to be Data-based or Process-based (transactional) Transactions deal with transformations of data, input and output Therefore we need to identify & develop transactions and data, and their interaction with the environment, to analyse a system

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson How do we do this? A process of expansion & contraction –Decomposition –Synthesis Identifying and relating static & dynamic elements –Facts –Processes

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson The value of models Why do we model? –To improve clarity and accessibility –To show different relational aspects of the system –To help understanding Different types of model –Data-based & Process-based –Varieties of model –Completeness of view

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Process modelling – The data flow diagram Basic process modelling tool –full-scale analysis involves multiple models –different tools are used for data modelling etc Top-down approach Valuable for describing –current physical system –logical/desired system Helps us to grasp system as a whole

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Key elements and considerations Relationship to other models Components –Sources/sinks (external entities) –Processes –Data stores –Data flows

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Symbology/notation Importance of notation Data flows between sources/sinks/stores via processes which transform the data SSADM notation

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson SSADM context diagram

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson SSADM notation - first level DFD

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson SSADM notation - second level DFD

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Naming Importance of naming Sources/sinks: generic descriptive Stores: simple descriptive Processes: “imperative action” concept Flows: what is tranferred Avoid ambiguity

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Hierarchies Concept of levelling –Top-down decomposition –Practical levelling Balancing –Ensure all inputs and outputs balance (match) across the levels of the hierarchy

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Referencing/numbering Basic principles –Decimal heirarchies Lower case lettering for entities Mn/Dn stores Stores within processes Single/double flow lines and direction Multiple sources/sinks/stores Process locations/roles (physical)

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Constructing data flow diagrams Follow the top-down approach Define boundary (context diagram) Identify –Static components –Key processes –Flows between them Build -expand - refine - review

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson Refining and developing the diagram Iterative process! Importance of –Balancing –Naming –Controlling complexity Document flow diagrams Data models

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson After the break: A brief exercise in process modelling!

SCHOOL OF LIBRARY, ARCHIVE AND INFORMATION STUDIES Andy Dawson That’s all for today! Any questions? Tomorrow: –Wrapping up the lifecycle –Feasibility studies and operational requirements –Systems selection and installation