1 CP2236 Information Systems Design Business & Technical System Options Required System Logical Data Flow Modelling Larger versions of slides 17,20,23,24.

Slides:



Advertisements
Similar presentations
Business System Options
Advertisements

Required System DFM Develop Required DFDs from selected BSO
Current DFDs 1 Current Physical DFDs Produced while developing Requirements Catalogue and Current Environment Logical Data Structure Gather information.
Technical System Options
Requirements Specification and Management
Johnb DFDs and Design John Bell The DeMarco notation.
Software Engineering-II Sir Zubair Sajid. 3 Data Flow Diagrams (DFD)  DFDs describe the flow of data or information into and out of a system what does.
DFD Rules and Guidelines Yong Choi BPA CSUB. 2 DFD example - Hoosier Burger’s food ordering system I * One process (level 0 - the whole system) * No data.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
User Guide. Service Benefits  Full on-line management of client accounts  Paperless direct debit – no signatures required  Standing orders fixed not.
Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.
General Financial Supply Website & E-Commerce Solutions This presentation will demo the GFS corporate website and On-Line Order Inquiry options available.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
PROCESS MODELING Transform Description. A model is a representation of reality. Just as a picture is worth a thousand words, most models are pictorial.
Modern Systems Analysis and Design
Identifying system improvements: Logicalisation
Function Definition  From Investigation to Specification  Defining Functions  The Universal Function Model  Identifying and Documenting Functions.
Physical design. Stage 6 - Physical Design Retrieve the target physical environment Create physical data design Create function component implementation.
Overview of Software Requirements
Database Design Concepts Info 1408 Lecture 2 An Introduction to Data Storage.
Systems Analysis and Design. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis Feasibility Maintenance.
QMS Documentation Click the mouse to advance slides and animations in this slide show…
Introduction to SAP R/3.
Process Modelling Using Data Flow Diagrams - Building and Levelling Them; Process Modelling Using Function Decomposition CSE Information Systems.
Systems Analysis I Data Flow Diagrams
Copyright © 2015 Pearson Education, Inc. Systems Documentation Techniques Chapter
Process Modeling SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
IT Job Roles Task 20. Software Engineer Job Description Software engineers are responsible for creating and maintaining software of various different.
Logical Database Design Nazife Dimililer. II - Logical Database Design Two stages –Building and validating local logical model –Building and validating.
Objectives of the Lecture :
National Diploma in Systems Analysis and Design Data Flow Modelling.
staffs.ac.uk Process Model. staffs.ac.uk Contents Provide definitions Explain the components and representations Introduce a step.
1 Structured Analysis Techniques. 2 Data Flow Diagrams.
Data Flow Diagrams (DFDs)
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
IT323 - Software Engineering 2 Tutorial 1. 0 The system 1.0 A Function 1.1 Activity of the function Task Task Task 1.2 Another activity.
Classroom User Training June 29, 2005 Presented by:
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
Requirements Analysis
Data Flow Diagrams A structured analysis technique that employs a set of visual representations of the data that moves through the organization, the paths.
DATA FLOW DIAGRAMS Learning Units
Data Flow Diagrams (DFD). ScenarioCriteriaTasks Data flow diagram(DFD) is a diagram of the movement of data between external entities.
MSF Requirements Envisioning Phase Planning Phase.
1 Ref: Prof Sarda Process Modeling…… Lecture Outline Data flow diagram (DFD)
ITEC224 Database Programming
1 Data Flow Diagrams. 2 Identifying Data Flows During the analysis stage of a project it is important to find out how data flows through a system:  Where.
Chapter 9 Moving to Design
DFDs.
NHSBT Purchase to Pay Improvement Plan NHSBT Finance Operations Team.
Databases. What is a database?  A database is used to store data. The word DATA is actually Latin for FACTS. A database is, therefore, a place, or thing.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
1 DATA FLOW DIAGRAM. 2 Outline Process decomposition diagrams Data flow diagram (DFD)
G045 Lecture 08 DFD Level 1 Diagrams (Data Flow Diagrams Level 1)
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
CSE300 EAIusing EJB & XML CSE Enterprise Application Integration Using EJB and XML by Prithwis Sett Mumtaz Lohawala Nayana Paranjape.
Systems Analysis & Design
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.
Analysis. This involves investigating what is required from the new system and what facilities are available. It would probably include:
Tools Of Structured Analysis
LESSON 2 SYSTEM ANALYSIS & DESIGN PHASE
We now will look at options for saving searches in CINAHL
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
Business Requirements
LO2 - Be Able to Design IT Systems to Meet Business Needs
Chapter 11 The Accounting Information System
AICT5 – eProject Project Planning for ICT
Information Systems Development (ISD) Systems Development Life Cycle
Reportnet 3.0 Database Feasibility Study – Approach
Presentation transcript:

1 CP2236 Information Systems Design Business & Technical System Options Required System Logical Data Flow Modelling Larger versions of slides 17,20,23,24 & 28 can be found at the end of of this handout

2 Business & Technical System Options Rare for only one solution to be possible. Analyst/Designer should be able to suggest several solutions to the business’s requirements. Business Systems Options (BSOs) provide a range of possible solutions for the business to consider. Each BSO may have more than one way of being implemented technically. These are known as Technical System Options (TSOs)

3 Business System Options (BSOs) Aim - To agree the functionality of the req. system. BSOs - done after the Requirements Catalogue (RC) has been formalised. Each entry in RC is considered, if any are excluded - document reasons. Develop 2-6 options. Using RC, project team establish & develop a list of : Minimum Functional Requirements (which all options must satisfy) & Non-Functional Requirements.

4 Functional Requirements - dictate what the system should do. What facilities are required & what activities the system should carry out: descriptions of required functions outline of reports - hard/soft copies on-line queries & updates data storage, retrieval & transfer, etc.

5 Non-Functional Requirements - address other facilities (limitations & constraints) Required Service/Performance Levels (response times for on-line functions, rate of data transfer) Security & Access Requirements Technical Constraints (make use of existing hardware) Project Constraints (system delivery deadlines & cost limits) Quality of user interfaces (how intuitive and easy to learn, and to use the technology to perform the task)

6 BSOs - consider the following factors: Approximate cost of each option Development time scale Known technical constraints Organisation of the system - types of access (on-line or off-line), interfaces with other systems Approximate data and transaction volumes Training requirements Benefits & impact on the organisation

7 Business System Options Upto 3 shortlisted. Each Option presented formally to the management. Strengths & Weaknesses explained to facilitate a decision. Opportunity to reassess the viability of the project (to carry on / cancel it). Selected BSO could be one option or an hybrid. Document selected BSO (reasons for selection & rejection others). Form the basis for the rest of the project and for the final system.

8 Technical System Options (TSOs) Addresses how the req. system is to be implemented. Define the TSOs: Identify constraints - external & internal Develop outline options (Up to 6) Select 2 or 3 main options for detailed dev’t Refine selected options - check performance Select the final TSO: Present options Fully document selected TSO (rationale for the selected option)

9 Technical System Options (TSOs) Each Full TSO contains 5 main parts: Technical environment description System description Impact analysis Outline development plan Cost / Benefit analysis

10 Current System DFDs There are 2 versions of this: 1.Current PHYSICAL DFD Representation of the current system as it is. May show letters, filing cabinets, manual data stores etc. 2.Current LOGICAL DFD Removes all physical references to the system. The process is referred to as Logicalisation.

11 Steps in Logicalisation (revision) Replace Physical Data Stores with main Logical Data Stores. Remove Transient Data Stores Remove/separate out processes that cannot be automated and/or require subjective decisions or will remain subjective. Remove processes which only reorganise data (e.g. sorting).

12 Combine processes which are joined by a data flow only, and which form part of the same or a very similar process Combine processes performing the same functions (appear separate only because of physical location). Minimise Data Flow Contents. Remove all physical references. Remove processes which do not alter data (ad hoc retrievals without creation or update. Remove processes which exist due to tradition or politics

13 Required System Logical DFMs: Current Physical DFM Current Logical DFM Required Logical DFM Requirements Catalogue Selected BSO

14 Required System Logical DFDs The broad aim is to take the current logical DFD and to map the Requirements Catalogue and BSO’s on to it.

15 Required System Logical DFMs - MethodStep1 Decide which processes on the current logical DFD are needed, then include these on the required logical DFD. Step 2 Look at the requirements catalogue, see what new processes are needed to meet the new requirements, add these to the required logical DFD. Generally, any process that could be done by computer is a candidate for automation. Any process that requires human judgement must be ruled out.

16 Current Logical Context Level DFD:

17 Current Logical Level 1 DFD:

18 Requirement Catalogue entries: 1.Manager can produce a list of members monthly, and then select members who will be eligible for monthly bonuses. 2.Generate and send monthly bonus letters to selected members. 3.Incorporate purchasing of new videos from suppliers - an order for new videos is generated and sent to suppliers. Suppliers send the invoice and the videos to the store. A payment is sent to the supplier on receipt of the invoice.

19 Requirements Catalogue Requirements 1 & 2 A new process (7) is added to incorporate requirements 1 & 2. The existing Loan details and Member data stores are included. Members details are sent to the manager and a bonus list is generated. The bonus letter is sent to the customer.

20 Process 7 DFD

21 Required System Logical DFMs - Method Step3 To maintain data, new data stores may need to be added. Identify these and add to the required logical DFD.

22 Requirements Catalogue Requirement 3 Another process (8) is needed to incorporate Requirement 3 into the logical DFD. In this example, a new data store ‘Video order’ is also added.

23 Process 8 DFD

24 Required Logical Level 1 DFD:

25 Context Diagram The Context Level required system logical DFD. follows same principles as for current physical and current logical DFDs. Any Level 1, Level 2 diagrams should balance with the context diagram.

26 Required Logical Context Level DFD:

27 Exercise Incorporate the following entry from the Requirements Catalogue into the required system DFM Requirements Catalogue Storecard holders should have the facility to close their accounts.

28 Requirements Catalogue Storecard holders should have the facility to close their account.

29 PRINT INSTRUCTIONS Handout- pp 1-16,18,19,21,22,25,26,27 2 per page for 17,20,23,24,28