CORE 1: PROJECT MANAGEMENT Designing. This stage is where the actual solution is designed and built. This includes describing information processes and.

Slides:



Advertisements
Similar presentations
CAPE COMPUTER SCIENCE UNIT 2
Advertisements

Steps of a Design Brief V Design Brief  Problem, identification, and definition Establish a clear idea of what is to be accomplished. Identify.
CAPE INFORMATION TECHNOLOGY – Unit 2
Systems Analysis Requirements structuring Process Modeling
Data Flow Diagram (DFD) Review
SYSTEMS ANALYSIS AND DESIGN TOOLS
Using Data Flow Diagrams
Chapter 7 Structuring System Process Requirements
Using Dataflow Diagrams
Chapter 4 Enterprise Modeling.
Chapter 4.
System Modelling System modelling helps the analyst to understand the functionality of the system and models are used to communicate with customers. Different.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
Systems Analysis and Design 9th Edition
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Jump to first page Chapter 2 System Analysis - Process Modeling.
Using Dataflow Diagrams
Structuring System Requirements: Process Modeling
Data and Process Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 8 Structuring.
Process Modeling Fundamentals. Three Ways to Understand a System By its processes What are the systems main processes? What are the systems main processes?
Chapter 4.
Chapter 7 Structuring System Process Requirements
6 Systems Analysis and Design in a Changing World, Fourth Edition.
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.
Chapter 8 Structuring System Requirements: Process Modeling
Systems Analysis and Design in a Changing World, Fifth Edition
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Chapter 6 The Traditional Approach to Requirements
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 6.1.
Data and Process Modeling
Systems Analysis and Design in a Changing World, Fifth Edition
SDLC Phase II: Structuring System Requirements IS 582 Dr. Dania Bilal Spring 2008.
Lesson 7 Guide for Software Design Description (SDD)
Accounting systems design & evaluation 9434SB 12 April 2002.
DATA FLOW DIAGRAMS Learning Units
Phase 2: Systems Analysis
Computer System Analysis Chapter 8 Structuring System Requirements: Process Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
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 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Chapter 7 System models.
Information Systems & Databases 2.2) Organisation methods.
Slide 1 System models. Slide 2 Objectives l To explain why the context of a system should be modelled as part of the RE process l To describe behavioural.
System models l Abstract descriptions of systems whose requirements are being analysed.
Structured Analysis.
SYSTEMS ANALYSIS AND DESIGN TOOLS DATA FLOW DIAGRAMS.
Chapter 4 Home Page – Welcome! To navigate the slide presentation, use the navigation bar on the left OR use your right and left arrow keys. Move your.
Chapter 4 enterprise modeling
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 5 Structuring.
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.
Structuring User Requirements IS 592 Dr. Dania Bilal Spring 2005.
Systems Analysis and Design 8th Edition
1Lecture 8 Introduction to Systems Analysis l Objectives –Explain how systems analysis relates to business needs, problems, and opportunities –List and.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
© 2005 by Prentice Hall Chapter 7 Structuring System Process Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
C_ITIP211 LECTURER: E.DONDO. Unit 3 : PROCESS MODELING.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Tools Of Structured Analysis
Chapter 6 Structuring System Requirements: Process Modeling
Business Process Modeling
Chapter 8 Structuring System Requirements: Process Modeling
SDLC Phase III: Structuring System Requirements
Data Flow Diagram (DFD) Review
Requirement Analysis using
Members: Keshava Shiva Sanjeeve Kareena
Presentation transcript:

CORE 1: PROJECT MANAGEMENT Designing

This stage is where the actual solution is designed and built. This includes describing information processes and specifying system resources (participants, data/info, IT) to perform these processes. DESIGNING

System Tools for understanding, Explaining and documenting the operation of a system Information processes are the link between a systems resources which will operate the new system. Describing the detail of these processes is critical and as such we use a number of detailed models to do so. The following ‘design’ tools are typically used… Context Diagrams Data Dictionaries Data Flow Diagrams Decision Tree’s and Decision Tables Storyboards DESIGNING // SYSTEM TOOLS

In small groups (2-3) read one of the following Context Diagrams (p65-66) Data Dictionaries (p66-67) Data Flow Diagrams (p68-70) Decision Tree’s and Decision Tables (p71-72) Storyboards (p73-74) Create a single A4 summary poster that provides the following: Clear Heading “Design Tools: ___________” Definition Example Key Terms DESIGNING // SYSTEM TOOLS

Context Diagram Context Diagrams represent the entire system as a single process. They don’t attempt to describe IP’s rather they identify: Data Entering the system Information Leaving the system Sources Destination (sink) The sources and sinks are called “external entities”. Context diagrams are really top level data flow diagrams and are often referred to as level 0 data flow diagrams. DESIGNING // SYSTEM TOOLS

Context Diagram Squares are used to represent each of the external entities. Commonly users, other organizations or systems. These entities are not part of the system and do not perform any information processes. The entire system is represented using a circle. The system collects or receives data from each source entity and displays or transmits information to each sink entity. Labeled data flow arrows describe the data and its direction of flow between the system and its entities. DESIGNING // SYSTEM TOOLS

Example Context Diagram from the text. DESIGNING // SYSTEM TOOLS

Context Diagram Think about a student using a swipe on card to record attendance at school in the morning. What might the context diagram look like? DESIGNING // SYSTEM TOOLS Student Sign in Process Student barcode Collected Sign in confirmation Displayed Student

Data Dictionaries Data dictionaries are used to detail each of the data items used by the system. They are made up of tables, where each row describes particular item, and each column describes a detail or attribute of the item. The name or identification of the item has to be included, along with the data type, storage size, description, etc. Data dictionaries are most commonly associated with Databases, documenting details of each field, but we can use them as a design tool to specify details for each data item in a system. DESIGNING // SYSTEM TOOLS

Data Flow Diagrams The aim of a DFD is to represent a system by describing the changes in data as it passes through processes. This is done in an illustrative fashion. An example is a computer that is summing a series of numbers. Rather than explain the step-by-step process of how they are summed, a DFD would focus on where the numbers came from and where their output lies. DESIGNING // SYSTEM TOOLS

Data Flow Diagrams As well as the symbols used in a context diagram (level 0 data flow diagram) we also represent data stores as open sided rectangles. A data store is where data is maintained prior to and after is has been processed. Additionally circles now represent processes rather than the entire system. DESIGNING // SYSTEM TOOLS Entity Process Data Movement Data Store

Data Flow Diagrams We have already said that a context diagram is a level 0 DF diagram, representing the complete system as a single process. A level 1 DF diagram expands this single process into multiple processes. A series of level 2 DF diagrams are drawn to expand each level 1 process into further processes. Level 3 DFD’s similarly expand each level 2 process and so on. This process is called “top-down design”. DESIGNING // SYSTEM TOOLS

Data Flow Diagrams DESIGNING // SYSTEM TOOLS

Decision Tables Decision tables are tools for documenting the logic upon which decisions are made; they describe a strict set of rules where each rule leads to a particular decision alternative or action. Each rule is composed of one or more conditions that must be satisfied for the rule to be true. DESIGNING // SYSTEM TOOLS

Decision Tables For example, if you are an Australian citizen and you 18 years or older then you can vote. This rule contains two conditions namely; “Australian citizen” and “18 years or older” and the single action “can vote”. In this rule both conditions must be true for the action to take place. We could produce further rules for when either or both conditions are false, which would result in the action “can NOT vote”. DESIGNING // SYSTEM TOOLS

Decision Trees A decision tree is a decision support tool that uses a tree-like graph or model of decisions and their possible consequences, including outcomes, resource costs and utility. Used in operations research specifically decision analysis to identify a strategy most likely to reach a goal. They describe a strict set of rules where each rule leads to a particular decision alternative or action. With a decision tree each condition is split into two parts, the first being a variable written above the tree and the second being the value (or range of values) for that variable within the tree. DESIGNING // SYSTEM TOOLS

Decision Tree vs. Decision Table DESIGNING // SYSTEM TOOLS

For the above example of data which do you think would be the best tool for describing this decision situation? Tree or Table? Create the model using either a decision table or a decision tree…

Storyboard A storyboard is a part of graphic organisers that shows the layout of each step or stage in a document or project. They are often hand drawn sketches or diagrams and have notes and ideas on the side. They are used in many types of ways such as in comics, film, theatre, business, novels and interactive media. They benefit in allowing easy changes to the project and helps with visual thinking and brainstorming bigger and better ideas. Storyboards can be created using either dedicated software or pencil and paper. DESIGNING // SYSTEM TOOLS

Storyboard DESIGNING // SYSTEM TOOLS

Designing the Information Technology Having used design tools to model the systems treatment of data into information it is now important to choose the Information Technology that will be involved. The ability of a system’s hardware and software to perform information processing is crucial and so the following should be considered. Are spare parts available for hardware now and into the future? Is the software user friendly? Is the software human centered or machine centered? Can it be customized to meet new requirements? Is it maintainable and upgradeable? DESIGNING