Function Definition  From Investigation to Specification  Defining Functions  The Universal Function Model  Identifying and Documenting Functions.

Slides:



Advertisements
Similar presentations
Required System DFM Develop Required DFDs from selected BSO
Advertisements

Chapter 11 Designing the User Interface
System Development Life Cycle (SDLC)
Requirements Specification and Management
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Alternative Approach to Systems Analysis Structured analysis
Information Systems Analysis and Design
Structured Systems Analysis and Design Methodology
The System Development Life Cycle
SSADM vs UML We examine the two Methods { SSADM And UML}
1 CP2236 Information Systems Design Business & Technical System Options Required System Logical Data Flow Modelling Larger versions of slides 17,20,23,24.
System Design and Analysis
Chapter 7 Using Data Flow Diagrams
Relational Data Analysis Learning outcomes  understand the process of normalisation;  perform Relational Data Analysis;  recognise the importance of.
Lecture 13 Revision IMS Systems Analysis and Design.
Physical design. Stage 6 - Physical Design Retrieve the target physical environment Create physical data design Create function component implementation.
Types of Requirements  Functional Requirements  Descriptions of actions or processes that create or update information.  Outlines of reports or on-line.
Computers: Tools for an Information Age
Chapter 9 Using Data Flow Diagrams
Chapter 7 Using Data Flow Diagrams
Lecture Nine Database Planning, Design, and Administration
Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.
Lesson-21Process Modeling Define systems modeling and differentiate between logical and physical system models. Define process modeling and explain its.
Chapter 13: Designing the User Interface
User Interface Design Window Navigation Models Window Specifications Prototyping Menu Structures User Object Modelling.
Chapter 7: The Object-Oriented Approach to Requirements
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Introduction to Information System Development.
1 Structured Analysis Techniques. 2 Data Flow Diagrams.
Introduction to Systems Analysis and Design Trisha Cummings.
Systems Analysis and Design: The Big Picture
Overview of the Database Development Process
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
CSI315 Web Applications and Technology Overview of Systems Development (342)
Managing the development and purchase of information systems (Part 1)
Data Flow Diagrams A structured analysis technique that employs a set of visual representations of the data that moves through the organization, the paths.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
1 Lecture 3: Introducing Data Flow Diagrams (DFDs) Section 1 - The Concept of Diagrams Why use Diagrams? Diagrams as Working Documents Systems Analysis.
Chapter 7 Using Data Flow Diagrams
Chapter 14 Information System Development
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Systems Analysis What is it?. 2 A Systems Development Life Cycle The need for change is recognised or planned for Outline requirements may be issued,
1 Introduction to Software Engineering Lecture 1.
Chapter 1 Program design Objectives To describe the steps in the program development process To introduce the current program design methodology To introduce.
Structured Systems Analysis and Design Methodology Contains 5 modules: Feasibility Study (Stage 0) Requirements Analysis (Stages 1 and 2) Requirements.
Systems Analysis and Design in a Changing World, Fourth Edition
Systems Development Life Cycle
CISB113 Fundamentals of Information Systems IS Development.
Lecture 2 System Development Lifecycles. Building a house Definition phase Analysis phase Design phase Programming phase System Test phase Acceptance.
 An Information System (IS) is a collection of interrelated components that collect, process, store, and provide as output the information needed to.
GCSE ICT 3 rd Edition The system life cycle 18 The system life cycle is a series of stages that are worked through during the development of a new information.
Accounting systems design & evaluation 9434SB 18 March 2002.
Management Information System (MIS) MIS is short for management information system or management information services. Management information system,
The System Development Life Cycle
Fundamentals of Information Systems, Sixth Edition
Architecture Concept Documents
Systems Analysis and Design
LESSON 2 SYSTEM ANALYSIS & DESIGN PHASE
The System Development Life Cycle
Engineering Processes
Introduction to Systems Analysis and Design
Business Activity Modeling
Public Management Information Systems System Analysis & Design Tuesday, December 04, 2018 Hun Myoung Park, Ph.D. Public Management & Policy Analysis.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Members: Keshava Shiva Sanjeeve Kareena
Information Systems Development (ISD) Systems Development Life Cycle
UNIT No- III- Leverging Information System ( Investing strategy )
Public Management Information Systems System Design Monday, July 01, 2019 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program Graduate.
Presentation transcript:

Function Definition  From Investigation to Specification  Defining Functions  The Universal Function Model  Identifying and Documenting Functions  Function Navigation Models  Dialogues

Investigation Derive Logical View of Current Services Assemble Investigation Results Investigate and Define Requirements Develop Business Activity Model FEASIBILITY Investigate Current Processing Investigate Current Data Feasibility Report Overview LDS BAM Overview DFM BAM Requirements Catalogue BAM Current Environment LDM Requirements Catalogue Current Physical DFM Task Models User Catalogue Logical DFM Current Environment LDM Requirements Catalogue Task Models

Specification Define Required System Processing Develop Required Data Model Enhance Required Data Model Derive System Functions Assemble Requirements Specification Develop Users’ Conceptual Models Develop Specification Prototypes Develop Processing Specification BSO Requirements Catalogue Logical DFM BSO Requirements Catalogue Current Environment LDM Define Work Practice Model BSO User Catalogue Task Models User Catalogue Task Models User Roles Required System DFM Task Models User Object Models Req. System LDM Function Definitions Function Definitions User Object Model Task Models Requirements Catalogue Function Definitions Window Specifications Window Navigation Models Task Models Help System Specifications Requirements Catalogue User Object Models Dialogue Structures Entity Life Histories Required System LDM Effect Correspondence Diagrams Enquiry Access Paths Requirements Catalogue Investigation

Defining Functions The technique of Function Definition serves a number of different purposes:  To define the services that the computerised system will offer its users;  To help analysts and users towards a shared understanding of what the system will do;  To provide the basis for the system’s specification;  To ensure that all design products are traceable to requirements.

Defining Functions Functions  The services offered by a computerised information system to its users are known as Functions user’s role  The Functions that are available to a given user depend on that user’s role menus  Functions are usually accessed through a series of one or more menus dialogue  Functions usually involve the user in some sort of dialogue with the system

Defining Functions For each Function we will have to:  Design the human computer interface (and where applicable interfaces with other computer systems).  Specify the database processing that supports each Function.  Consider ways of preventing erroneous data from ending up in the database.  Gather information that can be used to predict and tune the performance of the Function.  Ensure that the work done on each Function is not duplicated elsewhere and make use of work already done elsewhere.  Ensure that the Function is included in the user’s training manual.

Function Definition Concepts  We can define the concept of a Function in several ways, which together give a good idea of what a Function actually is: A Function is a set of processing that users wish to carry out at the same time A Function is a set of processing designed to handle the effects of an event (or group of events) on the system A Function is the basic unit of processing for input to Physical Design (where programs will be specified to implement it)

Function Types  Enquiry or Update  User or System Initiated  On-line or off-line We classify each Function in three main ways:

Function Components Input Function Input Process Events Enquiry Triggers Control Errors Syntax Errors Database Integrity Errors Event & Enquiry Output Function Output Process Function Error Process Valid Output Error Output Function Definition Boundary Update or Enquiry Process

Identifying Functions Maintain Purchase Order Purchase Orders D1 Purchaser b Depot D6 Suppliers D7 Supplier a Products D3 Stock Clerk i * Create Proposed Purchase Order 1.1 * Confirm Purchase Order 1.2 * Arrange Delivery 1.3 Proposed P.O. Amended P.O. Purchase Order P.O.Quantities Depot Address Supplier Details Delivery Details Product Details Delivery Schedule Availability Amended P.O. Delivery Schedule

Identifying Functions  Enquiry functions (other than those which form a major part of the systems functionality) will be documented in the Requirements Catalogue, rather than the Required System Data Flow Model. Each enquiry entry in the Requirements Catalogue will initially be identified as a function in its own right.

Documenting Functions  An identifier  The Function’s Name  The Function’s type  A description  The business event  The business activity  Error handling  The system event or enquiry  The User Role  DFD Processes For each Function we record  I/O Structures & Descriptions and Dialogues  Requirements  Tasks  User Object Model  Windows  Common Processing  Service Level Requirements  Volumes

Function Navigation Models  the Function is very large and it is more manageable to break it down into several parts  the Function contains more that one event/enquiry: we can define one or more components for each event and enquiry  there are parts of the function that will be used by other functions too: again events and enquiries will often feature in more than one function. Functions may be broken down into components when:

Function Navigation Models Web Browse and Buy Place Order Make Payment

Identifying Dialogues A good way of identifying dialogues is to use the Function Definitions and User Role documentation to identify exactly who will require access to each function. The easiest way of documenting this is by using a User Role/Function Matrix

Identifying Dialogues Delivery Scheduler Goods In Clerk Purchaser P. O. Clerk Stock Keeper Function User Role X X X XX X XX X X

Critical Dialogues Delivery Scheduler Goods In Clerk Purchaser P. O. Clerk Stock Keeper Function User Role X X X XX X XX X X

The Place of Function Definition Decision Structure Policies and Procedures User Organisation Investigation Construction Specification Conceptual Model Internal design External Design BAM RD WPM DFM FD LDM RDA BSO