course objectives2ndsemesternotes.yolasite.com/resources/mis chapter - 13.pdf · gane and sarson 13...

Chapter No 13 Batch 2009

1

Compiled By: Muzammil Ahmad Khan and Kashif Shaikh

Sir Syed University of Engineering and Technology

Management Information Systems


Chapter 13

Compiled By:

Muzammil Ahmad Khan

Muhammad Kashif Shaikh

13 - 2

HS-107 : Management Information SystemsHS-107 : Management Information Systems

Course Objectives:

Upon successful completion of this course, the student will be able to:

Understand the role of Information Systems (IS) in organizations.

Understand how Information Systems (IS) can be used to create competitive advantages for businesses.


2




13 - 3


Course Objectives:

Understand the key elements associated with designing Information Systems (IS).

Understand the key elements associated with planning and managing Information Systems (IS).

13 - 4


Prerequisites:

Familiarity with basic computer devices and terminologies.


3




13 - 5

MIS BooksMIS Books

Text Book

1. Management Information System, 8th EditionBy: James A. O' Brien , George Marakas

Reference Books

1. Management Information System, 9th EditionBy: Kenneth C. Laudon, Jane P. Laudon

2. Introduction to Information Systems: Supporting and Transforming BusinessBy: Rainer, Turban, Potter, 1st Edition

13 - 6

Marks DistributionMarks Distribution

Mid Term ________ 15Assignment + Class Performance + Quiz + Presentation + Report ________ 5Semester Final Paper ________ 80Total Marks ________ 100


4




13 - 7

Marks Distribution [ Sessional ]Marks Distribution [ Sessional ]

Class Test ______________ 10 PointsAssignment ______________ 10 PointsClass Presentation ______________ 15 PointsProject ______________ 15 PointsTotal Points ______________ 50 Points

Performance Bonus ______________ 10 Points

13 - 8

MIS WebsiteMIS Website

http://www.ssuet.edu.pk/courses/hs107/mis

http://taimoor/hs107/mis


5




13 - 9

Course InstructorsCourse Instructors

Muhammad Kashif Shaikh [email protected] Professor, CEDRoom No: BS-04Section A, B,E (Computer, Batch 2009)

Muzammil Ahmad Khan [email protected] Professor, CEDRoom No: BS-04Section C, D (Computer, Batch 2009)

13 - 10

ProjectProject

Comprehensive study of Information Systems of an Organization.Organization OverviewOrganizational HierarchyMain business function of the organizationAnalysis of IT Department

Role/Activities and ResourcesIllustration of Computer based Information SystemSystem Development Life Cycle

Analysis of other business SystemSales, Marketing, Supply Chain, Accounts, HRHow IT interact with other business system?

DFD of main business function and ISGantt chart and PERT chartIdentification of problems/weaknesses in the existing systemSuggestions and RecommendationsConclusion


6




13 - 11

Course OutlineCourse Outline

Module 1: IntroductionChapter 1: Foundations of IS in Business Chapter 2: Competing with Information Technology

Module 2: Hard and Soft AspectChapter 3: Computer Hardware Chapter 4: Computer Software Chapter 5: Data Resource Management Chapter 6: Telecommunications and Networks

Module 3: E-BusinessChapter 7: Electronic Business Systems Chapter 10: Decision Support Systems

13 - 12

Course OutlineCourse Outline

Module 4: IT in BusinessChapter 11: Developing Business/IT StrategiesChapter 12: Developing Business/IT Solutions

Module 5: Special TopicsChapter 13: Special Topics in MIS

- Flow Chart- Data Flow Diagram [ DFD ]- Gantt Chart- Pert Chart- System Development Life Cycle [ SDLC ]


7




Special Topics in


Special Topics in


Chapter13

Chapter13


Compiled By: Muzammil Ahmad Khan & Muhammad Kashif Shaikh

13 - 14

1. Flow Chart

2. Data Flow Diagram [ DFD ]

3. Gantt Chart

4. Pert Chart

5. System Development Life Cycle [SDLC ]

Learning ObjectivesLearning Objectives


8




13 - 15

Project Management SkillsProject Management Skills

What about your time management

skills?

How good are your project management skills?

13 - 16

What is a Flow ChartWhat is a Flow Chart

A picture of any process

Drawn with standard symbols representing different types of activities

Different styles available:DeploymentProcess


9




13 - 17

Purpose of Flow ChartPurpose of Flow Chart

Defines the system being studied

Gets agreement

Identifies “value added” activities

Identifies “dead wood” activities”

Documents changes to the process

13 - 18

SymbolsSymbols

Start/End Task Make a Decision

Yes

No

Conduct a Meeting Report Out End of Process


10




13 - 19

Flow Chart ExampleFlow Chart Example

Start

ReadN1

ReadN2

V = N1 / N2 Print V StopPrint D

D = N1 – N2

13 - 20

Flow Chart ExampleFlow Chart Example

Start ReadN

Set counter = 1

Set Nfac = 1

counter<N

1

0

Nfac = Nfac + counter

Counter = counter + 1Print X2

Stop


11




13 - 21

Process ModelingProcess Modeling

Process Modeling involves graphically representing the functions, or processes that capture, manipulate, store and distribute data between a system and its environment and among system components.

13 - 22

Data Flow Diagram [ DFD ]Data Flow Diagram [ DFD ]

A common and traditional form of process modeling techniqueGraphically illustrate movement of data between external entities and the processes and data stores within a systemGraphically characterize data processes and flows in a business system

how data flows through the organizationthe processes or transformation that the data undergoeswhat the outputs are


12




13 - 23

DFD VS Flow ChartDFD VS Flow Chart

DFD’s are not as good as flowcharts to depict details of physical systems

Flowcharts are not very useful for depicting purely logical information flows

Four symbols are used to represent both physical and logical information systems

13 - 24

Data Flow Diagram [ DFD ] SymbolsData Flow Diagram [ DFD ] Symbols

Process

Data store

Source / Sink( External Entity )

Data Flow

DeMarco & Yourdon Symbols Gane & Sarson Symbols


13




13 - 25

Data Flow Diagram [ DFD ]Data Flow Diagram [ DFD ]

Definitions and SymbolsTwo different standard sets of DFD symbols with each set consisting of four symbols that represent same things:data flow, data store, processes, sources/sinks (external)

DeMarco and Yourdan

Gane and Sarson

13 - 26

DFD Symbols DetailDFD Symbols Detail

1. Data Flow

Depicts data in motion and moving from one place to another in the system.

Example: results of query of database, contents of printed report

Data flow is data that move together


14




13 - 27


2. Data Store

Depicts data at rest

May represent one of many different physical locations for data:

File folder / Computer-based file / Notebook

Might contain data about customers, students, customer orders

13 - 28


3. Process

Depicts work or action performed on data so that they are transformed, stored or distributed


15




13 - 29


4. Source / Sink [ External Entities ]

Depicts the origin and/or destination of the data

Sometimes referred to as an external entity so they are outside system and define boundaries of system

Because they are external, many characteristics are not of interest to us

Data must originate from outside a system from one or more sources and system must produce information to one or more sinks

13 - 30


Data flow is shown as an arrow labeled with a meaningful name for data (all elements of data moving as part of one packet) in motion – sales receipt, customer order.Data store is shown as rectangle without its right vertical side and left side has a small box used to number the data store and inside the main part of rectangle is a meaningful label – student file.Source/Sink is shown as a square and has a name that states what external agent is – customer, teller.Process is shown as a rectangle with rounded corners with a line dividing it into two parts – upper part has the number of process and lower part has name of process.


16




13 - 31

DFD LevelsDFD Levels

1. Context Diagram

The highest-level view of an organizational system that shows the system boundaries, external entities that interact with the system and the major information flows between the entities and the system

All context diagrams have only one processlabeled “0”

No data stores appear on a context diagram

13 - 32

DFD LevelsDFD Levels

2. Level-0 Diagram

A data flow diagram (DFD) that represents a system’s major processes, data flows and data stores at a high level of detail

Each process has a number that ends in .0


17




13 - 33

Context DiagramContext Diagram

Context Diagram of Hoosier Burger’s Food Ordering System

13 - 34

Context Diagram – Level 0Context Diagram – Level 0

Level-0 DFD of Hoosier Burger’s Food Ordering System


18




13 - 35

Data Flow Diagramming RulesData Flow Diagramming Rules

Basic rules that apply to all DFDsInputs to a process are always different than its outputs –purpose of a process is to transform inputs to outputsObjects on a DFD always have a unique name

In order to keep the diagram uncluttered, you can repeat data stores and sources/sinks on a diagram

Process:A. No process can have only outputs ( we can’t make data from nothing). Having only outputs means it must be a source.B. No process can have only inputs. Having only inputs means it must be a sink.C. A process has a verb phrase label

13 - 36


Data store:D. Data must be moved by a process and cannot move directly from one data store to another data storeE. Data cannot move directly from an outside source to a data store. Data must be moved by a process that receives data from the source and places data into data store.F. Data cannot move directly to an outside sink from a data store. Data must be moved by a process. G. A data store has a noun phrase label

Source/Sink:H. Data cannot move directly from source to sink and has to be moved by a process else data flow is not shown on the DFD.I. A source/sink has a noun phrase label


19




13 - 37


Data flow:J. A data flow has only one direction of flow between symbols. It may flow in both directions between a process and a data storeusually indicated by two separate arrows as this happens at separate timesK. A fork in a data flow means that exactly the same data goes from a common location two or more different processes, data stores, or sources/sinks.L. A join in a data flow means that exactly the same data comes from any two or more different processes, data stores, or sources/sinks to a common locationM. A data flow cannot go directly back to the same process it leaves.N. A data flow to a data store means update (delete or change)O. A data flow from a data store means retrieve or use.P. A data flow has a noun phrase label.

13 - 38


Data Flow that Connects

YES NOA process to another process

A process to an external entity

A process to a data store

An external entity to another external entity

An external entity to a data store

A data store to another data store


20




13 - 39

DFD - ExerciseDFD - Exercise

Precision Tools sells a line of high-quality woodworking tools. When customers place orders on the company’s Web site, the system checks to see if the items are in stock, issues a status message to the customer, and generates a shipping order to the warehouse, which fills the order. When the order is shipped, the customer is billed. The system also produces various reports.

Draw a Context Diagram for the order systemDraw DFD Diagram 0 for the order system

13 - 40

Identify Entities, Process, Data Stores & Data FlowIdentify Entities, Process, Data Stores & Data Flow

EntitiesCustomerWarehouseAccounting

Processes1.0 Check Status 2.0 Issue Status Messages3.0 Generate Shipping Order4.0 Manage Accounts Receivable5.0 Produce Reports

Data StoresD1 Pending OrdersD2 Accounts Receivable

Data FlowsOrderIn-Stock RequestOrder DataStatus DataStatus MessageShipping OrderOrder DataInvoice Shipping ConfirmationPaymentAccounting DataAccounts Receivable DataOrder DataInventory Reports

1.0

2.0

3.0

4.0

5.0


21




13 - 41

Context Diagram of Order SystemContext Diagram of Order System

Context Diagram of Order System

13 - 42

Level – 0 of Order SystemLevel – 0 of Order System

Level – 0of Order System


22




13 - 43

Basics [ GANTT and PERT Chart ]Basics [ GANTT and PERT Chart ]

Gantt and PERT charts are both “CPM” (Critical Path Method) tools to:

Manage the tasks involved in big and complex projects

Let project managers organise time, people, equipment and money

Ensure the right people and equipment are in the right place and the right time

Allow managers to monitor the progress of a project

13 - 44

What is a GANTT ChartWhat is a GANTT Chart

A visual representation of a project over timeUsed to schedule, coordinate, and allocate the resources needed to complete a projectShows start, end, and specific target dates called “milestones”


23




13 - 45

Benefits of GANTT ChartBenefits of GANTT Chart

Efficiency IncreaseProject trackingSet deadlines

Communication Increase

Coordination Increase

Provides motivation through scheduling

Encourages creativity

13 - 46

Features of GANTT ChartFeatures of GANTT Chart

Easy to createFreehand Gantt chartsMicrosoft ExcelMicrosoft ProjectSmart Draw, Primavera, and other programs.

Easy to modify and adjust

Simple to understand


24




13 - 47

Disadvantages of GANTT ChartDisadvantages of GANTT Chart

Activity descriptions often lack detail

A lack of precedent and subsequent task relationships

Does not allow for uncertain situations such as late or early finish times.

13 - 48

How Can This Tool Be Used in Your Organization?

How Can This Tool Be Used in Your Organization?

Upcoming projects?Communication barriers?Time restraints?


25




13 - 49

GANTT Chart Sample GANTT Chart Sample

13 - 50

GANTT Chart FundamentalsGANTT Chart Fundamentals

Separate tasks are listed in vertical rowsTime spans horizontally along the topEach task is represented by a bar along the time horizon


26




13 - 51

GANTT Chart - StepsGANTT Chart - Steps

Step 1: List the task of the project

13 - 52


Step 2: Add Duration


27




13 - 53


Step 3: Add dependencies (which tasks cannot start before another task finishes)

13 - 54

GANTT Chart - RulesGANTT Chart - Rules

The arrows indicate dependencies.Task 1 is a predecessor of task 2 – i.e. task 2 cannot start before task 1 ends.Task 3 is dependent on task 2. Task 7 is dependent on two other tasksElectrics, plumbing and landscaping are concurrent tasks and can happen at the same time, so they overlap on the chart. All 3 can start after task 4 ends.Painting must wait for both electrics and plumbing to be finished.Task 9 has zero duration, and is a milestone


28




13 - 55


Step 4: Find the Critical Path

13 - 56


The critical path is the sequence of tasks from beginning to end that takes the longest time to complete.

It is also the shortest possible time that the project can be finished in.

Any task on the critical path is called a critical task.

No critical task can have its duration changed without affecting the end date of the project.


29




13 - 57


The length of the critical path is the sum of the lengths of all critical tasks (the red tasks 1,2,3,4,5,7) which is 2 + 3 + 1 + 1.5 + 2 + 1 = 10.5 days.In other words, the minimum amount of time required to get all tasks completed is 10.5 daysThe amount of time a task can be extended before it affects other tasks is called slack (or float).Task 6 can take an extra day and a half before it affects the project’s end date, so each has 1.5 day’s slack.

13 - 58

PERT ChartPERT Chart

ProgramEvaluation andReviewTechnique

This PERT chart follows the “Activity on Arrow” style.The tasks are shown by arrows. Task name are shown by letters, in this case.The circles are called nodes. The nodes indicate the start or end of tasks.Task durations are the shown by the numbers.


30




13 - 59


Program Evaluation and Review Technique

A network of nodes and arrowsarrows --> activitiesnodes --> events

Use to determine the critical path and slack time

13 - 60



31




13 - 61


Which task are on the Critical Path

13 - 62


Possible Paths:A,B,C,E,I = 2 + 3 + 1 + 4 + 3 = 13 daysA,B,D,F,I = 2 + 3 + 3 + 3 + 3= 14 daysA,G,H,I = 2 + 2 + 5 + 3 = 12 days

ANSWER: A, B, D, F, IThis is because this is shortest time any of the tasks, included the tasks dependants, can be completed.


32




13 - 63

Comparison of Gantt and PERT ChartsComparison of Gantt and PERT Charts

Comparison of Gantt and PERT ChartsGantt Chart

Visually shows duration of tasksVisually shows time overlap between tasksVisually shows slack time

PERT ChartVisually shows dependencies between tasksVisually shows which tasks can be done in parallelShows slack time by data in rectangles

Gantt ChartsUseful for depicting simple projects or parts of large projectsShow start and completion dates for individual tasks

PERT ChartsShow order of activities

13 - 64

HIPO ChartHIPO Chart

Hierarchical Input-Process-Output

HIPO diagrams were developed by IBM in the 1970s (see [HIPO, 1974] and [Katzan, 1976]) and have been used by some systems analysts to present a high-level view of the functions performed by a system, as well as the decomposition of functions into sub-functions, and so on.


33




13 - 65

HIPO ChartHIPO Chart

StrengthShows functional relationships

WeaknessesDoes not show non-functional requirementsNo checking mechanism, except for customer review

13 - 66

HIPO Chart – Example 1HIPO Chart – Example 1


34




13 - 67


13 - 68



35




13 - 69

Warnier / ORR DiagramWarnier / ORR Diagram

A Warnier / ORR Diagram (also known as a logical construction of a program/system) is a kind of hierarchical flowchart that allow the description of the organization of data and procedures.

A Warnier / ORR Diagram is a style of diagram which is extremely useful for describing complex processes (e.g. computer programs, business processes, instructions) and objects (e.g. data structures, documents, parts explosions).

13 - 70

Warnier / ORR DiagramWarnier / ORR Diagram

Warnier / ORR Diagram show the processes and sequences in which they are performed. Each process is defined in a hierarchical manner i.e. it consists of sets of sub processes, that define it.At each level, the process is shown in bracket that groups its components.Since a process can have many different sub processes, Warnier / ORR Diagram uses a set of brackets to show each level of the system.


36




13 - 71

Constructs in Warnier / ORR DiagramConstructs in Warnier / ORR Diagram

There are four basic constructs used on Warnier / ORR Diagram:

1. Hierarchy, 2. Sequence, 3. Repetition, and 4. Alternation.

13 - 72


1. HierarchyHierarchy is the most fundamental of all of the Warnier/Orr constructs.

It is simply a nested group of sets and subsets shown as a set of nested brackets.


37




13 - 73


1. HierarchyEach bracket on the diagram (depending on how you represent it, the character is usually more like a brace "{" than a bracket "[", but we call them "brackets") represents one level of hierarchy.

The hierarchy or structure that is represented on the diagram can show the organization of data or processing. However, both data and processing are never shown on the same diagram.

13 - 74


2. SequenceSequence is the simplest structure to show on a Warnier/Orr diagram. Within one level of hierarchy, the features listed are shown in the order in which they occur.


38




13 - 75


3. RepetitionRepetition is the representation of a classic "loop" in programming terms.

It occurs whenever the same set of data occurs over and over again (for a data structure) or whenever the same group of actions is to occur over and over again (for a processing structure).

13 - 76


4. AlternationAlternation, or selection, is the traditional "decision" process whereby a determination is made to execute one process or another. It is indicated as a relationship between two subsets of a set.

The Exclusive OR symbol (the plus sign inside the circle) indicates that the sets immediately above and below it are mutually exclusive (if one is present the other is not).


39




13 - 77


To show that an action repeats (loops), you simply put the number of repetitions of the action in parentheses below the action.

Repetition

You represent concurrency in a diagram by placing an "AND" operator between the concurrent actions. The "AND" operator looks either like AND or + .

AND

You represent choice in a diagram by placing an "OR" operator between the items of a choice. The "OR" operator looks either like OR or *.

OR

The sequence of events is defined by the top-to-bottom order in a diagram. That is, an event occurs after everything above it in a diagram, but before anything below it.

Sequence

A bracket encloses a level of decomposition in a diagram. It reveals what something "consists of" at the next level of detail.

Bracket

13 - 78

Warnier / ORR Diagram – Example 1Warnier / ORR Diagram – Example 1

"Welcoming a guest to your home (from 1 to many times) consists of greeting the guest and taking the guest's coat at the same time, thenshowing the guest in. Greeting a guest consists of saying "Good morning" if it's morning, or saying "Good afternoon" if it's afternoon, orsaying "Good evening" if it's evening. Taking the guest's coat consists ofhelping the guest remove their coat, then hanging the coat up.


40




13 - 79


13 - 80



41




13 - 81


13 - 82

SDLCSDLC

Systems Development Life Cycle (SDLC)Provides overall framework for managing system development process

Two main approaches to SDLCTraditional Approach: structured systems development and information engineeringObject-Oriented Approach: object technologies requires different approach to analysis, design, and programming

All projects use some variation of SDLC


42




13 - 83

SDLCSDLC

Systems Development ProjectPlanned undertaking with fixed beginning & endProduces desired result or product Can be a large job of thousands of hours of effort ora small one month project

Successful Development Project:Provides a detailed plan to followOrganized, methodical sequence of tasks and activitiesProduces reliable, robust, and efficient system

13 - 84

SDLCSDLC


43




13 - 85

SDLC PhasesSDLC Phases

13 - 86


1. Project Planning: initiate, ensure feasibility, plan schedule, obtain approval for project

2. Analysis: understand business needs and processing requirements

3. Design: define solution system based on requirements and analysis decisions

4. Implementation: construction, testing, user training, and installation of new system

5. Support: keep system running and improve


44




13 - 87


1. Planning PhaseDefine business problem and scope

Produce detailed project schedule

Confirm project feasibility

Economic, organizational, technical, resource, and schedule

Staff the project (resource management)

Launch project official announcement

13 - 88


2. Analysis PhaseGather information to learn problem domain

Define system requirements

Build prototypes for discovery of requirements

Prioritize requirements

Generate and evaluate alternatives

Review recommendations with management


45




13 - 89


3. Design PhaseDesign the application architecture

Design the user interfaces

Design the system interfaces

Design and integrate the database

Prototype for design details

Design and integrate system controls

Design and integrate the network

13 - 90


4. Implementation PhaseConstruct software componentsVerify and test Convert dataTrain users and document the systemInstall the system


46




13 - 91


5.Support and Maintenance PhaseMaintain system

Small patches, repairs, and updatesEnhance system

Small upgrades or enhancements to expand system capabilitiesLarger enhancements may require separate development project

Support usersHelp desk and/or support team

13 - 92

SDLC Phases SummarySDLC Phases Summary


47




13 - 93

SDLC Phases SummarySDLC Phases Summary

13 - 94

Scheduling Project PhasesScheduling Project Phases

Waterfall Approach – each phase falls into next phase

Freeze planning specifications before analysisFreeze analysis specifications before designOnce go over the waterfall for each phase, do not go back

Overlapping (or concurrent) phasesWaterfall is not realistic, we are not perfectOverlaps can be more efficient than waterfall


48




13 - 95

Water Fall approach to the SDLCWater Fall approach to the SDLC

13 - 96

Overlapping of System Development ActivitiesOverlapping of System Development Activities


49




13 - 97

Two Approaches to System DevelopmentTwo Approaches to System Development

Traditional Approach and Object Oriented Approach

Traditional ApproachAlso called structured system developmentStructured analysis and design technique (SADT)

Structured ProgrammingImproves computer program qualityAllows other programmers to easily read and modify codeEach program module has one beginning and one endingThree programming constructs (sequence, decision, repetition)

13 - 98

Three Structured Programming ConstructsThree Structured Programming Constructs


50




13 - 99

Object-Oriented ApproachObject-Oriented Approach

Views information system as collection of interacting objects that work together to accomplish tasks

Objects - things in computer system that can respond to messagesNo processes, programs, data entities, or files are defined – just objects

Object-Oriented Analysis (OOA)Defines types of objects that do work of systemShows how objects interact with users to complete tasks

13 - 100

Object-Oriented ApproachObject-Oriented Approach

Object-Oriented Design (OOD)Defines object types needed to communicate with people and devices in systemShows how objects interact to complete tasksRefines each type of object for implementation with specific language of environment

Object-Oriented Programming (OOP)Writing statements in programming language to define what each type of object does

Benefits of OOA include naturalness and reuse