Abstract
Post-development change requests are user requirements for information systems changes after development. Conflicts might occur as contradictive or inconsistent relationships between requests and existing system design. Detecting conflicts in post-developmenet change requests is an important task during requests management processes. To address this topic, this article proposes an ontology-based blog for automatically discovering conflicts in the extended use-case models of requests from users. This study proposed an information system maintenance process. The proposed approach applies ontologies to represent domain knowledge. A set of rules are used to detect conflicts. This study developed a prototype and invited two companies to evaluate it. Usage feedback opinions about ontology-based blog from two companies indicated the usefulness. The ontology-based blog is a relatively new approach which bridge requirements blogs with a formal and machine interpretable representational model. The automatic conflicts detection capability of the ontology-based blog can reduce the labor cost in requirements analysis phase.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Abran, A., & Nguyenkim, H. (1993). Measurement of the maintenance process from a demand-based perspective. Journal of Software Maintenance Research and Practice, 5(2), 63–90.
April, A., Hayes, J. H., Abran, A., & Dumke, R. (2005). Software maintenance maturity model (SMmm): the software maintenance process model. Journal of Software Maintenance and Evolution, 17(3), 197–223.
Booch, G., Rumbaugh, J., & Jacobson, I. (1998). The unified modeling language user guide. Upper Saddle River: Addison-Wesley.
Chandrasekaran, B., Josephson, J. R., & Benjamins, V. R. (1999). What are ontologies, and why do we need then? IEEE Intelligent Systems, 14(1), 20–26.
Conallen, J. (1999). Building web applications with UML. Upper Saddle River: Addison-Wesley.
Dobing, B., & Parsons, J. (2000). Understanding the role of use cases in UML: A review and research agenda. Journal of Database Management, 11(4), 28–36.
Eden, A. H. (2002). A theory of object-oriented design. Information Systems Frontiers, 4(4), 379–391.
Fatolahi, A., & Shams, F. (2006). An investigation into applying UML to the Zachman framework. Information Systems Frontiers, 8(12), 133–143.
Gervasi, V., & Zowghi, D. (2005). Reasoning about inconsistencies in Natural language requirements. ACM Transactions on Software Engineering and Methodology, 14(3), 277–330.
Gruninger, M., & Lee, J. (2002). Ontology: Applications and design. Communications of the ACM, 45(2), 39–65.
Hausmann, J. H., Heckel, R., & Taentzer, G. (2002). Detection of conflicting functional requirements in a use case-driven approach. In: Proceedings of the 24th international conference on software engineering (pp. 105–115). Long Beach CA: IEEE Computer Society.
Jiao, J., & Chen, C. (2006). Customer requirement management in product developmenet: A review of research issues. Concurrent Engineering: Research and applications, 14(3), 173–185.
Kaiya, H., & Saeki, M. (2005). Ontology based requirements analysis: lightweight semantic processing approach. In: Proceedings of the Fifth International Conference on Quality Software (pp. 223–230). Long Beach CA: IEEE Computer Society.
Kaiya, H., & Saeki, M. (2006). Using domain ontology as domain knowledge for requirements elicitation. In: Proceedings of 14th IEEE International Requirements Engineering Conference (pp. 189–198). Long Beach CA: IEEE Computer Society.
Kang, D., & Chiang, R. (2006). A systematic approach in managing post-deployment system changes. Communications of the ACM, 49(6), 91–95.
Kajko-Mattsson, M. (2002). Problem management maturity within corrective maintenance. Journal of Software Maintenance and Evolution, 14(3), 197–227.
Kajko-Mattsson, M., & Bosu, M. (2006). Eliciting an enhancive maintenance model in three organisations in Ghana. In: Proceedings of 5th IEEE/ACIS International Conference on Computer and Information Science and 1 st IEEE/ACIS International Workshop on Component-Based Software Engineering, Software Architecture and Reuse (pp. 244–251). Long Beach CA: IEEE Computer Society.
Lee, J., & Xue, N. (1999). Analyzing user requirements by use cases: A goal-driven approach. IEEE Software, 16(4), 92–101.
Madallli, D. P., & Suman, A. (2008). UML for the conceptual web. Online Information Review, 32(4), 511–515.
Paulo, J., Almeida, A., Iacob, M. E., & van Eck, P. (2007). Requirements traceability in model-driven development: Applying model and transformation conformance. Information Systems Frontiers, 9(4), 327–342.
Robinson, W. N., & Pawlowski, S. D. (1999). Managing requirements inconsistency with development goal monitor. IEEE Transactions on Software Engineering, 25(6), 816–835.
Robinson, W. N., Pawlowski, S. D., & Volkov, V. (2003). Requirements interaction management. ACM Computing Surveys, 35(2), 132–190.
Sommerville, I. (2005). Integrated requirements engineering: A tutorial. IEEE Software, 22(1), 16–23.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Liu, CL., Yang, HL. Applying ontology-based blog to detect information system post-development change requests conflicts. Inf Syst Front 14, 1019–1032 (2012). https://doi.org/10.1007/s10796-011-9314-0
Published:
Issue Date:
DOI: https://doi.org/10.1007/s10796-011-9314-0