Modeling Software Characteristics and Their Correlations in A Specific Domain by Comparing Existing Similar Systems

Authors:
Akira Osada;Daigo Ozawa;Haruhiko Kaiya;Kenji Kaijiri
Affiliations:
Graduate School of Science and Technology, Shinshu University, Japan;Graduate School of Science and Technology, Shinshu University, Japan;Graduate School of Science and Technology, Shinshu University, Japan;Graduate School of Science and Technology, Shinshu University, Japan
Venue:
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
Year:
2005

Citing 7
Cited 2

Specification matching of software components

ACM Transactions on Software Engineering and Methodology (TOSEM)
Applying use cases (2nd ed.): a practical guide

Applying use cases (2nd ed.): a practical guide
Developing Groupware for Requirements Negotiation: Lessons Learned

IEEE Software
Conducting Requirements Evolution by Replacing Components in the Current System

APSEC '99 Proceedings of the Sixth Asia Pacific Software Engineering Conference
Design and Development Assessment

IWSSD '00 Proceedings of the 10th International Workshop on Software Specification and Design
QFD for Customer-Focused Requirements Engineering

RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems

RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International

The role of domain knowledge representation in requirements elicitation

SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Extracting conceptual graphs from Japanese documents for software requirements modeling

APCCM '09 Proceedings of the Sixth Asia-Pacific Conference on Conceptual Modeling - Volume 96

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software in a specific domain has several characteristics and each characteristic should be fixed when the software requirements are specified. In addition, these characteristics sometimes correlate with each other. However, we sometimes forget to specify several characteristics and/or to take their correlations into account during requirements elicitation. In this paper, we propose a meta-model for representing such characteristics and their correlations, and also propose a method to build a model for a specific domain by using documents about existing software systems. By using our model for a domain, a requirements specifi- cation for a system in the domain could be complete and unambiguous because requirements analysts can check the characteristics that should be decided. The specification could be also correct and consistent because the analysts can know side effects of a requirement change by using correlation among the characteristics. We have applied our methods to a case study for confirming the usefulness of such model and the methods.