261446 Information Systems Week 7 Securing Information Systems.
ICS321 Management Information Systems
description
Transcript of ICS321 Management Information Systems
![Page 1: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/1.jpg)
ICS321 MANAGEMENT INFORMATION SYSTEMS
Dr. Ken Cosh
![Page 2: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/2.jpg)
REVIEW Business Applications
Ebusiness Systems Cross Functional Ebusiness Systems CRM SCM KMS DSS Business Intelligence
![Page 3: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/3.jpg)
NEXT MODULE “Building Information Systems”
Redesigning an organisation with IS Systems as planned organisational change
The Systems Development Lifecycle Business’ impact on Systems Development
Requirements Engineering Implementing valuable systems Managing Change Outsourcing Solutions
![Page 4: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/4.jpg)
BUILDING INFORMATION SYSTEMSTHE CHALLENGES
Major Risks and uncertainties in systems development. Already mentioned some of the enterprise wide
project failures Systems requirements are complex and volatile Time and costs are difficult to predict Managing Organisational change
Deciding where the best impact could be had Which system project to choose How far to go with the system changes
![Page 5: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/5.jpg)
ORGANISATIONAL CHANGE THROUGH SYSTEMS DEVELOPMENT 4 structured organisational change levels
available; Automation
Replacing repetitive tasks by faster, more reliable systems
Rationalisation of procedures Streamlining of standard operating procedures, removing
bottlenecks for example. Business Process Re-engineering (BPR)
Radical redesign of business processes, redesigning the way the business performs procedures, combining steps for example.
Paradigm Shift Radical reconceptualisation of the nature of the business
and the nature of the organisation.
![Page 6: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/6.jpg)
THE SPECTRUM OF ORGANISATIONAL CHANGE
Automation
Rationalisation
Reengineering
Paradigm Shifts
High
High
Low
Low
RISK
REWARD
![Page 7: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/7.jpg)
SYSTEMS ENGINEERING An engineering discipline that
investigates the cost effective development of systems.
Concerned with all practical aspects of system production from system specification to system maintenance, including design, development and implementation.
![Page 8: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/8.jpg)
S.E. LIFECYCLE
![Page 9: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/9.jpg)
S.E. LIFECYCLE II
![Page 10: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/10.jpg)
REQUIREMENTS ENGINEERING
“Requirements are the things that you should discover before starting to build your product.
Discovering the requirements during construction, or worse, when your client starts using your
product, is so expensive and so inefficient... …A requirement is something that the product must do
or a quality that the product must have.”
[Robertson & Robertson 1999]
![Page 11: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/11.jpg)
The Importance of R.E.
• The later in the development cycle an error is detected the more expensive it is to repair.
Stage Relative cost of repair
Requirements 0.1 – 0.2
Design 0.5
Coding 1
Unit Test 2
Acceptance Test 5
Maintenance 20
Davies 1993
![Page 12: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/12.jpg)
Requirements Elicitation
• Sources:– Goals– Domain Knowledge– System Stakeholders– Operational Environment– Organisational Environment
• Techniques:– Interviews– Scenarios– Prototypes– Facilitated Meetings– Observation
![Page 13: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/13.jpg)
ELICITATION DIFFICULTIES Communication Issues
Management lack appreciation of IS concepts (people oriented)
IS lack appreciation of Business functions (technology oriented)
User disagreements / conflicts
Result - elicit requirements from many stakeholders (viewpoints) using many different techniques.
![Page 14: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/14.jpg)
ELICITING REQUIREMENTS Interviewing difficulties
Firstly, one individual person is unlikely to know everything about what a system should do.
Secondly, the individual may not be able to articulate all the requirements coherently.
Finally, the individual may not actually know what they do
![Page 15: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/15.jpg)
FACILITATED MEETINGS Brainstorming Project Scoping Conflict discussion
However, arguments and people not really understanding what they do.
![Page 16: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/16.jpg)
OBSERVATION Ethnography
Watching users in action to understand what they do.
But problem of creating meaningful reports. Business processes often too subtle & complex to describe easily.
![Page 17: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/17.jpg)
SCENARIOS Discussion of what should occur in
different situations and under different conditions.
Conceptual modeling
But, can you cover all eventualities?
![Page 18: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/18.jpg)
PROTOTYPES Present basic overview of potential
solution Paper Mockup Beta test version
Potential to get carried away with how it looks.
Design Orientated.
![Page 19: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/19.jpg)
COMBINATION OF TECHNIQUES
A Good Requirements Specification
Interviewing Facilitated Meetings
Scenarios
Prototypes
ObservationAnalysis of existing systems
Analysis of available systems
![Page 20: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/20.jpg)
REQUIREMENTS ANALYSIS Detecting & Resolving Conflicts
between Requirements Discovering the bounds of a system
and how it interacts in it’s environment Elaborate System Requirements to
Software Requirements
![Page 21: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/21.jpg)
REQUIREMENTS ANALYSIS Classification
Functional vs Non-functional Priority Scope Stability / Volatility
Conceptual Modeling Negotiation
![Page 22: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/22.jpg)
FEASIBILITY ANALYSIS Technical Analysis
Is it possible? Economic Analysis
Costs vs Benefits Is it worth doing?
![Page 23: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/23.jpg)
Economic Evaluation
• What’s it going to cost me?– Acquisition / Development Costs
• Hardware, Software, Project Team salaries, Consultant fees.
– Implementation Costs• Conversion, Training, Staff salaries, Design &
Printing costs– Operating Costs
• Ongoing Staff salaries, Training, Outside services, Forms, Maintenance, Upgrades/
![Page 24: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/24.jpg)
Apparent / Hidden Costs
Computer CostsOverheadsSoftwarePersonnel
Improper use of management timeConversion CostsSecurity / PrivacyDocumentation CostsTraining & RecruitmentOperations OverloadCommunication ProblemsLabour Division
![Page 25: ICS321 Management Information Systems](https://reader036.fdocuments.net/reader036/viewer/2022062520/56815f30550346895dcdfe87/html5/thumbnails/25.jpg)
Benefits
• Direct Savings– Staff reductions, Space,
• Cost Avoidance– Current system inflation (maintenance etc.),
Additional Staff, • Intangible Benefits
– Productivity Improvement, Better Information & Decisions, Accuracy, More Timeliness, Reliability, Flexibility