Information Systems Quality

Chapter-8
PRM-41
 SDLC- The Limitations
Traditional SDLC methodology for current IT
Projects are not always appropriate:
Many systems projects fail to meet objectives
– Difficulty in estimating costs
– Each project is often so unique that previous
experience may not provide the necessary skills
– Objectives may be too broad or too narrow
– Opportunity may not be appropriately leveraged.
– There may not be enough time to comply each step
of the SDLC
PRM-41, MIS; Chapter-8
 GAPS in IS Planning
End-Users
-Not much of idea on technology/tools
-Improper /less Communication
-Over occupied with immediate needs First Order Effect:
-Takes people/technology as granted
Poor use of IS
Consequence:- Patch work, Feels let- down

IT- Centre Developer / Vendor

-Limited knowledge on -Sells concepts
business -Sells technology
-Project mode strategies -Lacks empathy
for IT infrastructure set -Lacks knowledge on
up organization
-Engrossed in Technical Evaluation and Gap
Issues Analyses
Consequence:- Mismatch in
requirement and offered
Consequence: Doing wrong product
things efficiently

•Second Order Effect: Far reaching effects on

key performances
•Third Order Effect: Increase in TCO
PRM-41, MIS; Chapter-8
 Why Quality Systems?
• Bridge the gap between acquirers and service
providers
• Service providers include
– Infrastructure providers (H/w, OS, Databases, Networks,
Middleware, groupware…)
– Application software ( like Tally, ERP etc..)
• The challenge is to
– Ascertain quality of services
– Know if any certifying agency is there?

PRM-41, MIS; Chapter-8

 Expectations from Quality Systems

• Are the supplies of product/ services quality

certified?
• Is the development process certified?
– SDLC supported Models
– Quality Models

PRM-41, MIS; Chapter-8

 Possible Outcomes
• Address issues related to mismatch in
requirement of user and delivery of supplier
• Enforce standard methods adopted by Service
Providers which can be tested and verified
• Educate User on vendors/ service providers
and their capabilities

PRM-41, MIS; Chapter-8

 Quality Models
End-Users
-Not much idea on technology/tools
-Improper /less Communication
Software Engineering Models, User
-Over occupied with immediate needs
-Takes people/technology as granted
Centered Designs; for managing
User
Consequence:- Patch work, FeelsParticipation,
let- down in specification
mapping, Testing, Acquisition of
IT- Centre Products../ Services… Developer / Vendor
-Limited knowledge on -Sells concepts
business -Sells technology
-Project mode strategies -Lacks empathy
for IT infrastructure set -Lacks knowledge on
up organization
-Engrossed in Technical Evaluation and Gap
Issues Analyses

SDLC Driven Software Engineering Consequence:- Mismatch in

requirement and offered product
Models: Consequence: Doing wrong
things efficiently Quality Systems Models:
CHAOS; Linear Sequential; ISO; IEEE;BOOTSTRAP; TRILLIUM…etc
RAD…etc for managing quality in for quality of Products../ Services…
Acquisition of Products../ Services… CMM Certification for People and
Processes; Integration
PRM-41, MIS; Chapter-8