The Unified Modeling Language user guide
The Unified Modeling Language user guide
Communications of the ACM - Ontology: different ways of representing the same concept
Proceedings of the 24th International Conference on Software Engineering
What Are Ontologies, and Why Do We Need Them?
IEEE Intelligent Systems
Semantic blogging and decentralized knowledge management
Communications of the ACM - The Blogosphere
Hermeneutics, information and representation
European Journal of Information Systems - Special issue: "Interpretive" approaches to information systems and computing
Integrated Requirements Engineering: A Tutorial
IEEE Software
An empirical study of industrial requirements engineering process assessment and improvement
ACM Transactions on Software Engineering and Methodology (TOSEM)
Reasoning about inconsistencies in natural language requirements
ACM Transactions on Software Engineering and Methodology (TOSEM)
Ontology Based Requirements Analysis: Lightweight Semantic Processing Approach
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
Instant consistency checking for the UML
Proceedings of the 28th international conference on Software engineering
Managing requirements conflicts in software product lines: A goal and scenario based approach
Data & Knowledge Engineering
Ensuring Consistency in Relational Repository of UML Models
ICIT '07 Proceedings of the 10th International Conference on Information Technology
The Role of User Participation in Information Systems Development: Implications from a Meta-Analysis
Journal of Management Information Systems
Quantifying knowledge base inconsistency via fixpoint semantics
Transactions on computational science II
| Hi-index | 0.00 |
Requirements conflicts analysis is one of most crucial activities in successful software engineering projects. Activity diagrams are a useful standard for modeling process behaviors of systems. This paper utilizes ontological approach to analyze conflicts in the requirement specifications of activity diagrams. The proposed conflicts analysis method includes a modeling process and a set of conflicts detection rules. Several scenarios of electronic commerce are also provided for demonstrating the validity of the proposed rules. The benefits of the proposed method are threefold: (1) The method provides systematic steps for modeling requirements and ontologies. (2) This method also offers a set of questions for facilitating requirements elicitation about activity diagrams. (3) The proposed rules can systematically assist in requirements conflicts detection.