Extending the McCumber Cube to Model Software System Maintenance Tasks

Extending the McCumber Cube to Model Software System Maintenance Tasks published by Requirements Engineering Lab, School of Information Technology

1. Extending the McCumber
Cube To Model Software
System Maintenance
Tasks
Vorachet Jaroensawas
1
, Vajirasak Vanijja
2
and Chonlameth Arpnikanondt
1
1
Requirements Engineering Lab, School of Information Technology
2
IP Communications Lab, School of Information Technology
King Mongkut’s University of Technology, Bangkok, Thailand Emails: [email protected], {vachee, chonlameth}@sit.kmutt.ac.th

2. Introduction
Welcome
My subject is “Extending The McCumber
Cube To Model Software System
Maintenance Tasks (SSMT)”
Online the structure of THIS presentation
Instruction about questions “Do feel free
to interrupt me if you have any questions”
1. the progress of this year
2. the problem we have encountered and how alleviate them
2.1 the need of maintenance policies study
2.2 the lack of understanding problem
2.3 What maintenance is best for us?
3. The proposed extension
4. Validation of the research (application case study)
5. Conclusion

3. the problem we have encountered
The need of maintenance policies study

the lack of understanding problem
What maintenance is best for us?

4. how alleviate them
A clear guideline for understanding the
general decision structure for SSMT is needed
Model based approach are needed
Security-driven approach is needed
McCumber Cube Price’s extension
McCumber Cube Price’s extension
Maintenance Policies :
FBM,CBM,DOM,TBM/UBM,OBM

5. Maintenance Policies :
FBM,CBM,DOM,TBM/UBM,OBM

6. Extends
Extends
Our extension
Price’s extensionMcCumber Cube

7. The proposed Extension

8. Method Process
Overview

9. Design dataMSI of Interest
This section specifies the functional requirements of mycompany.com in terms of list of requirements and the
selected maintenance significant items on which we are interested to model. The selected issues of assumed
maintenance decision support data are consist of the following: integrity of visitor database, integrity of web
documents, and availability of HTTP service. We assume that these three issues are identified as a high-impacted
incident.
APPLICATION CASE STUDY

10. The selected maintenance policy is CBM. This
predictive maintenance is widely-used for a
system maintainer where parameters of the
computer resources such as the CPU, memory,
and network bandwidth can be measured by a
monitoring software application.
In this example, the countermeasure
proposes the DOM maintenance policy
which will be implemented with database
replication software. The focus of DOM is
to improve the design in order to make
maintenance easier or to even eliminate
it.
This case study assumes that the system
does not provide rigid control of release
process for the homepage maintenance. FBM
is typically handy in case of random
failure behavior or no preventive
maintenance task found on the MSI.
APPLICATION CASE STUDY
Integrity of visitor database
Integrity of web documents
Availability of HTTP service
The selected issues of assumed maintenance decision support data are consist of the following: integrity of visitor database, integrity of web documents, and
availability of HTTP service. We assume that these three issues are identified as a high-impacted incident.

11. Conclusion
Advantages Disadvantages
It seems that a number of organizations
today prefer reducing risks of critical
system maintenance by outsourcing to a
specialized service provider—as oppose
to building their own maintenance team.
In that case, the proposed method could
be of more use to the contracted third
party.
• A clear guideline for understanding the general
decision structure for SSMT
• Model based approach
• Security-driven approach
Recommendations
COntributions
This paper introduced a novel method
for representing maintenance task
modeling. The method was based on
Price’s work and explicitly associated
the general security goal to prescribe
the required maintenance policies and
actions. It effectively allowed the
maintainer to model maintenance
tasks from the security point of view,
as well as to reason how the
maintainer should maintain the critical
items belonging to risk assessment.
The method process overview
shows how the maintenance
concept is composed. The idea of
an optimized maintenance
program suggests that an
adequate mix of maintenance
actions and policies need to be
selected and fine-tuned in order to
satisfy maintenance objectives.
Rausand and Vatn explained the
concept of the reliability-centered
maintenance (RCM) analysis
process and argued that design
data, operational and failure data,
as well as reliability data are
n e e d e d f o r a n e ff e c t i v e
maintenance analysis.