You are on page 1of 6

MDX BIS4225.

10

Operations and Mantenance


After a system has been:
designed,
BIS4225.10 developed, and
tested,
Systems Maintenance it moves into the Operations
and Maintenance phase.

1 2

Operations and Mantenance Software Maintenance


This starts when the initiator Definition (IEEE 1219): The
provisionally accepts the modification of a software
system. product after delivery
Once a system is up and to correct faults,
running, it needs to be to improve performance, or
provided with the best to adapt the product to a modified
possible service. environment.

3 4

Software Maintenance Software Maintenance


Definition: The totality of Large systems are never
activities required to provide complete and they continue
cost-effective support to a to evolve.
software system. Maintenance is a form of
Pre-Delivery Stage (determination continuing development
of supportability, logistics) within the constraints of the
Post-Delivery Stage (software existing software system.
modification, training, help desk)
5 6

1
MDX BIS4225.10

Software Maintenance Software Maintenance


It is not only about fixing

Cost of Correcting Design Errors


bugs (80% of maintenance
effort is for non-corrective
actions).
Maintenance account for over
60% of effort expended by a
development organization.
Initiation Development Implementation Operations &
Maintenance
7 A (1999, 424) 8

Software Maintenance Need for Maintenance


Software Maintainers: Correct Errors Changes in
Correct Design system, files, or
Look at the product
Flaws databases
development code.
Interface with Improve design
Look at the current situation. new or Cater to different
Look forward to anticipate changed hardware,
problems and functional systems software,
changes. Enhancements networks, etc.
9 10

Areas of Focus Categories


Maintaining control over: Corrective Maintenance
systems data-to-day functions to correct discovered faults (top
system modification maintenance priority)
Perfecting: Perfective Maintenance
existing acceptable functions to improve performance or
system performance from maintainability (not changing
degrading to unacceptable levels. functionality)
11 12

2
MDX BIS4225.10

Categories Prioritization
Adaptive Maintenance Urgency
to maintain usability in a Criticality
changed or changing A problem is critical if the
environment
software, or an essential part
Preventive Maintenance of it, is unavailable
to enable software to best serve
the needs of end users
13 14

Maintenance Activities Maintenance Activities


Unique Activities Supporting Activities
Need thorough knowledge of Configuration Management
codes structure and content. (controlled changes through
Need to conduct impact analysis on approved Software Configuration
likely and actual outcomes of their Management process).
work. Quality (by reducing complexity
Need to analyze Software Problem and conducting software
Reports (SPRs). inspections).
15 16

Maintenance Activities Maintenance Activities


Maintenance Planning Maintenance Planning
Activities Activities
May last for several years. Scope of software maintenance.
Proper maintenance planning Tailoring of the post-delivery process.
should begin with the decision to People who will provide maintenance.
develop a new system! Estimation of life cycle costs.

17 18

3
MDX BIS4225.10

Maintenance Activities Maintenance Process


Standards Maintenance Process Models
IEEE 1219 Standard for Software Provides operations.
Maintenance Provides detailed inputs/outputs to
ISO/IEC 12207 Standard for Life- these operations.
Cycle Processes Specified in:
ISO/IEC 14764 Standard for IEEE 1219
Software Maintenance ISO/IEC 14764
19 20

Maintenance Process Maintenance Process


Maintenance Process Models Maintenance Process Activities:
Process Implementation
Modification
Request Classification & Problem and Modification Analysis
Analyze
Identification
Modification Implementation
Delivery Design Maintenance Review and Acceptance
Migration
Acceptance Test Implementation Software Retirement
System Test

21 22

Organization Aspects Organization Aspects


Software Maintainers: Software Maintainers:
Software developers are not An organization must be in
always used to maintaining the place to meet usersneeds
system once it is operational. when they use the software.
Software maintainers can be Respond to problem reports.
from a separate team. This can Provide user support.
be outsourced.
23 24

4
MDX BIS4225.10

Management Aspects Management Aspects


Documentation: Modified Software Releases:
SPR: Software Problem Report Major Releases (new solutions,
SCR: Software Change Request correction of outstanding faults,
(prepared for approval by Review perfecting existing software)
Board before making changes) Minor Releases (small extensions)
SMR: Software Modification Emergency Releases (urgent
Report (prepared after making patches)
changes)
25 26

Problems Problems
Technical Problems Management Problems
Limited Understanding (especially for Alignment with Organizational Issues
systems with bad documentation). (ROI is never clear, problem to get
Testing (time and cost). resources for maintenance).
Impact Analysis (requires special skills). Staffing (for unglamourous work).
Maintainability (usually not incorporated Process Issues (especially activities that
in the development process). are not found in software development,
for example, help desk support).

27 28

Problems Problems
Maintenance Cost Maintenance Cost Estimates
Costs are high due to Parametric Models: COCOMO
maintenance problems. (Constructive Cost Model).
Maintenance consumes a major Experience: sound judgement,
share of a products life cycle reasoning, work breakdown
costs. structure, guesses, use of
empirical/historical data.
29 30

5
MDX BIS4225.10

Measurements Measurements
General Software Specific Metrics
Engineering Metrics IEEE 982.1 Software Maturity Index (SMI)

GQM: Goal-Question-Metric MT (Fc + Fa +F d)


SMI =
MT
Identify organizational goals
MT = No of modules
Defining questions related to goals Fc = No of modules that have been changed
Selecting measures that answer the Fa = No of modules that have been added
questions. Fd = No of modules from the preceding release that
were deleted in the current release.
31 32

You might also like