Methods and Approaches

of Information Systems
Development
 What is Information System

Source: GeeksforGeeks website

Most Common Problems of Systems
Development and Maintenance?
1. Inadequate Functionality (Technical
Shortfalls)
2. Inconsistency with the existing systems
3. Cost and Time Over-Run
4. Rapid obsolescence of Technology
5. Failure to obtain Assumed Benefits
6. Non-availability of skilled professional
 5 Root Causes of System
Development Problems
1. Incomplete understanding of Requirements
2. Wrong selection of Methods and
approaches of Systems Development and
Management
3. Inherent Characteristics of Software
Systems
4. Inexperience and over ambitious Software
Project execution team
5. Non-availability of right Project Leader
 Complexity

Software entities are more

complex than any other human
construct because no two parts
are alike.
 Conformity

• The developed software must do, what it is suppose

to do.
• The system must conform (do the accepted thing)
with the systems to which it interfaces.
• Confirmation is necessary because the systems are
developed and designed by different people.
 Changeability

The software entity is constantly

under the pressures of change to
cope, deliver and conform with the
changing paradigms of application
domain, business and technology.
 Invisibility

• Software is invisible and un-visualizable.

• Software has no ready geometric representation in the

way land has maps etc.

• Notations and Symbols are used to draw scenarios and

roadmaps to represent the flow of control, the flow of

data, pattern of dependencies, time sequence, name-

space relationships.
 Complicated Vs. Complex

Complicated Complex
1. A System is Complicated, 1. A System is complex, if its
relationships can not be
if each of its individual explained fully by merely
components or analyzing its components
constituents can be because they are Dynamic
and Changing.
Described/ Separated
2. A Bio-Chemical Reaction
(Even if there is huge
3. Complexity Generate
numbers of them). Novel Features , often
2. A Mixer called Emergent
Properties
E.g. Manufacturing an Aircraft. E.g. The Brain is a complex
system
Major Issues in IS Development
Functionality
Cost Compatibility
M
A Capacity Security T
N E
E C
G H
E
Availability Fault Tolerance
N
R I
I C
A A
L
Performance Throughput
L

Technology Churn Resilience

1. The biggest challenge is not cost or performance, but

the complexity. - Sun Microsystems
2. We have to develop expertise to mange the complexity
2 Types of Models of Software/
Systems Development

1. Life Cycle Oriented Model

 The Waterfall Model
 The Incremental Model
 The Spiral Model

2. Management Oriented Model

 The V-Model
 The SEI’s Process Maturity Model
Waterfall Model
Advantage of waterfall model
• Requirement are well defined and
documentation. 
• The project is very short.
• All the state are Clearly defined.
• very easy to arrange tasks.
 Disadvantage of waterfall
model
• It doesn’t allow much reflection or revision.
• It is use only one process like if we are in the testing
stage, it is very difficult to go back and change
something that was not well-documented or thought
upon in the concept stage
• This is not working software is produced until late
during the life cycle.
• This is high amounts of risk and uncertainty.
 Why Prototyping?
1. Process of building experimental systems to
demonstrate, evaluate approach; refine
users’ needs
2. PROTOTYPE: Preliminary working version of
selected aspects of proposed Information
System for Demonstration, Evaluation
Purposes
3. An iterative process.
4. It provides users an opportunity to examine
the utilities and difficulties of proposed
system (s).
 Prototyping
Start
Stop
Requirements
Gathering
and Refinement
Quick
Engineer
Design
Product

Refining Building
Prototype Prototype
Customer
Evaluation of
Prototype
 Incremental model
Incremental Model is a process of software development where requirements
divided into multiple standalone modules of the software development cycle.
 Advantage of Incremental
Model
• Errors are easy to be recognized.
• Easier to test and debug
• More flexible.
• Simple to manage risk because it handled
during its iteration.
• The Client gets important functionality
early.
 Disadvantage of Incremental
Model

• Need for good planning

• Total Cost is high.
• Well defined module interfaces are
needed.
Spiral Model
 Spiral Model Parts of Each
Stage
Objective setting: Each cycle in the spiral starts with the identification of
purpose for that cycle, the various alternatives that are possible for achieving
the targets, and the constraints that exists.

Risk Assessment and reduction: The next phase in the cycle is to calculate
these various alternatives based on the goals and constraints. The focus of
evaluation in this stage is located on the risk perception for the project.

Development and validation: The next phase is to develop strategies that

resolve uncertainties and risks. This process may include activities such as
benchmarking, simulation, and prototyping.

Planning: Finally, the next step is planned. The project is reviewed, and a
choice made whether to continue with a further period of the spiral. If it is
determined to keep, plans are drawn up for the next step of the project.
 Make versus Buy
• Alternatives
 packages are less expensive, immediately
available, supported
 custom software is more individualized
 semi-custom means buying a package but
then tailoring it to your needs
• Clear trend towards packages or
• Get it done (outsource)
 Product

V-Model
Project
Initiation Phase Out

(Contractual Model) Operation

Requirement and
Specification Maintenance

Accepted
Specification Software

Acceptance
Structural
Design Test

Integrated
Design Software

Detailed Integration
Design & Test

Module Debugged
Design Module

Code and Unit Test

3 Levels of Standardization of V- model

Configuration Management
Quality Assurance

Software Development

Project Management

Procedure

Methods

Tool Requirements
How V-Model Facilitate Tailoring

Selection recommendations
V-Model or deletion conditions

Contractual Tailoring
at project initialization

Selection of required Collection of all other important

activities and products regulations for the project

Technical Tailoring Project Manual

conducted during the project

Following of the project specific implementing conditions.

Decide what activities and products have to be carried out/produced

Project Plan
 Roles in the V-Model
SWD Project Manager
Assistant Project Manager
System Analyst
System Designer
Project Assistant PM
DP Analyst
DP Designer QA Manager
SW Analyst QA Contact
SW Designer Quality Assessor QA
Programmer QA Assistant

Support Consultant
Applications Consultant CM Manager
Configuration Administrator
HW Consultant CM
Representative for Data
Technical Author
Protection and Security
SEI’s(Software Engineering Institute)
Process Maturity Model
 Process Maturity Model
Level Characteristic Key Problem Area Result

Optimizing Improvement fed Automation Productivity

back into process & Quality

Managed (Quantitative) Changing Technology

Managed Process Problem analysis Quantitative
Quality Plan
Defined (Qualitative) Process Process Measurement
Defined & Problem analysis Quantitative
Institutionalized Quality Plan
Repeatable (Intuitive) Training, Technical Practices,
Process dependent on Reviews, Testing, Process
Individuals Focus Standards, Process
Groups

Initial Ad hoc/ Chaotic Project Management

Configuration Management,
Software Quality Assurance
Risk
 Utility of Maturity Model
1. Allows systems development managers to
assess the levels of maturity of the
competing S/W organizations.
2. Enable mangers to decide whom to award
the contract of systems development.
3. Enable to take calculated risks between
the costs vis-à-vis the chance of failures.
Tasks of Analysis to Design
Information
Functional Model
Model
Other
Requirements
Behavioral
Model Design Data
Archite Design
ctural
Design
Procedural
Design
Interface Code
Design Program
Module

Test

Integrated
Verified
System
PS: Build Specifications Based on these Models
 Technical & Management
Aspects of Design
Management
Aspects
Preliminary Design
Detail Design

Data Design

Architectural Design
Technical
Aspects
Procedural Design

Interface Design
 Major Stake Holders of ISDP

1 2 3

CUSTOMER DEVELOPER USER

Requirements System Design & Implementation
Analysis Development Process

ISDP = Information System Development Process

 Focuses of Stake Holders
CUSTOMER DEVELOPER USER
Requirements System Design & Implementation
Analysis Development Process

Experience &
Statements Specifications
Expectations
Methods Approach Implementation
Tools Methods Strategy
Methods & Tools
Existing Practices Existing Practices
Exposures & Initiatives
Specifications Tools Training & Rewards

VALIDATION & MEASUREMENTS

VERIFICATION
VERIFICATION & CONTROL
Tasks of Project Management

Dimensions of project management

 Key Tasks of Software Project
Management
Contracts
Contracts  Project Purpose and Scope Control
Control
 Project Goals and Objectives Requirements
Requirements
 Organization and Responsibilities
Schedule
Schedule Development
 Management & Technical Control Development
Methodologies
Methodologies
 Work Definition and Work Flow
Budgets
Budgets  Development Environment
Staffing
Staffing
 Development Methodology
Plans
Plans
 Configuration Management
Customer
Requirements  Verification And Validation
 Quality Assurance Provisions Resumes

Contract
Contract Company
Company Systems
Systems Interface
Interface Performance
Performance
Implementation
Implementation
Plan
Requirements
Requirements Requirements Requirements
Requirements Requirements Requirements
Requirements
Plan
 Assignment - III
Situation:
Assume that you have recently joined A2Z Supply Chain Ltd. In Bangalore
as Systems Manager. Mr. Kumar, GM of the A2Z, feels that A2Z’s MIS
systems are outdated. Mr. Kumar asked you to replace the old systems
with an ultra modern Management Information Systems.
Questions:
1. What methods and approaches of system development you would
like to follow and why?
2. How would you ensure the delivery of the proposed systems
within the given budget and time?
3. What would be your key tasks?
4. How would you monitor the progress?
5. What would be your focus?
QUESTIONS