Evaluation of Risk Attributes Driven by Periodically Changing System Functionality
Modeling of the distributed systems allows us to
represent the whole its functionality. The working system instance
rarely fulfils the whole functionality represented by model; usually
some parts of this functionality should be accessible periodically.
The reporting system based on the Data Warehouse concept seams to
be an intuitive example of the system that some of its functionality is
required only from time to time. Analyzing an enterprise risk
associated with the periodical change of the system functionality, we
should consider not only the inaccessibility of the components
(object) but also their functions (methods), and the impact of such a
situation on the system functionality from the business point of view.
In the paper we suggest that the risk attributes should be estimated
from risk attributes specified at the requirements level (Use Case in
the UML model) on the base of the information about the structure of
the model (presented at other levels of the UML model). We argue
that it is desirable to consider the influence of periodical changes in
requirements on the enterprise risk estimation. Finally, the
proposition of such a solution basing on the UML system model is
presented.
[1] R. Allen, R. Douence and D. Garlan, "Specifying and Analyzing
Dynamic Software Architectures", Lecture Notes in Computer Science,
vol. 1382, pp. 21-36, 1998.
[2] J.C. Alberts and J.D. Audrey, "Mission Assurance Analysis Protocol
(MAAP): Assessing Risk in Complex Environments", Technical Report
CMU/SEI-2005-TN-032, 2005.
[3] R. Bahsoon and W. Emmerich "Evaluating Software Architectures:
Development, Stability, and Evolution", Proceedings of ACS/IEEE Int.
Conf. on Computer Systems and Applications, Tunis, Tunisia, July, 2003
[4] D. Dymek and L. Kotulski, "On Hierarchical Composition of the Risk
Management Evaluation in the Computer Information Systems",
accepted for 25-th IASTED Multi-international Conference on Applied
Informatics, Software Engineering, February 13-15, Insbruck, 2007.
[5] R. Kazman, L. Bass, G. Abowd, and M. Webb, "SAAM: A Method for
Analyzing the Properties of Software Architecture", International
Conference on Software Engineering, pages 81-90, 1994.
[6] R. Kazman, M. Klein and P. Clements, "ATAM, Method for
Architecture Evaluation", Technical Report CMU/SEI-2000-TR-004,
2000.
[7] M. Klain and R. Kazman, "Atribute-Based Architectural Styles",
Technical Report CMU/SEI-99-TR-022, 1999.
[8] L. Kotulski, ÔÇ×Model wspomagania generacji oprogramowania w
środowisku rozproszonym za pomoc─à gramatyk grafowych - DSc
degree", Wydawnictwo Uniwersytetu Jagiellońskiego, Krak├│w, ISBN
83-233-1391-1, 2000.
[9] L. Kotulski, "Nested Software Structure Maintained by aedNLC graph
grammar"- Proceedings of the 24th IASTED International Multi-
Conference Software Engineering, February 14-16, pp 335-339,
Innsbruck, Austria, 2006.
[10] OMG-Unified Modeling Language, v2.0. www.rational.com
[1] R. Allen, R. Douence and D. Garlan, "Specifying and Analyzing
Dynamic Software Architectures", Lecture Notes in Computer Science,
vol. 1382, pp. 21-36, 1998.
[2] J.C. Alberts and J.D. Audrey, "Mission Assurance Analysis Protocol
(MAAP): Assessing Risk in Complex Environments", Technical Report
CMU/SEI-2005-TN-032, 2005.
[3] R. Bahsoon and W. Emmerich "Evaluating Software Architectures:
Development, Stability, and Evolution", Proceedings of ACS/IEEE Int.
Conf. on Computer Systems and Applications, Tunis, Tunisia, July, 2003
[4] D. Dymek and L. Kotulski, "On Hierarchical Composition of the Risk
Management Evaluation in the Computer Information Systems",
accepted for 25-th IASTED Multi-international Conference on Applied
Informatics, Software Engineering, February 13-15, Insbruck, 2007.
[5] R. Kazman, L. Bass, G. Abowd, and M. Webb, "SAAM: A Method for
Analyzing the Properties of Software Architecture", International
Conference on Software Engineering, pages 81-90, 1994.
[6] R. Kazman, M. Klein and P. Clements, "ATAM, Method for
Architecture Evaluation", Technical Report CMU/SEI-2000-TR-004,
2000.
[7] M. Klain and R. Kazman, "Atribute-Based Architectural Styles",
Technical Report CMU/SEI-99-TR-022, 1999.
[8] L. Kotulski, ÔÇ×Model wspomagania generacji oprogramowania w
środowisku rozproszonym za pomoc─à gramatyk grafowych - DSc
degree", Wydawnictwo Uniwersytetu Jagiellońskiego, Krak├│w, ISBN
83-233-1391-1, 2000.
[9] L. Kotulski, "Nested Software Structure Maintained by aedNLC graph
grammar"- Proceedings of the 24th IASTED International Multi-
Conference Software Engineering, February 14-16, pp 335-339,
Innsbruck, Austria, 2006.
[10] OMG-Unified Modeling Language, v2.0. www.rational.com
@article{"International Journal of Information, Control and Computer Sciences:62424", author = "Dariusz Dymek and Leszek Kotulski", title = "Evaluation of Risk Attributes Driven by Periodically Changing System Functionality", abstract = "Modeling of the distributed systems allows us to
represent the whole its functionality. The working system instance
rarely fulfils the whole functionality represented by model; usually
some parts of this functionality should be accessible periodically.
The reporting system based on the Data Warehouse concept seams to
be an intuitive example of the system that some of its functionality is
required only from time to time. Analyzing an enterprise risk
associated with the periodical change of the system functionality, we
should consider not only the inaccessibility of the components
(object) but also their functions (methods), and the impact of such a
situation on the system functionality from the business point of view.
In the paper we suggest that the risk attributes should be estimated
from risk attributes specified at the requirements level (Use Case in
the UML model) on the base of the information about the structure of
the model (presented at other levels of the UML model). We argue
that it is desirable to consider the influence of periodical changes in
requirements on the enterprise risk estimation. Finally, the
proposition of such a solution basing on the UML system model is
presented.", keywords = "Risk assessing, software maintenance, UML, graph
grammars.", volume = "2", number = "11", pages = "3947-6", }