Process Evaluation Based on Meeting Quality of Requirement Analysis Phase in Software Development Projects
- 1 Faculty of Information Science and Technology, Osaka Institute of Technology, Osaka, Japan
- 2 Faculty of Management Information, Hannan University, Osaka, Japan
Abstract
We propose a metric for meeting quality in software development. Meeting is important in order to share knowledge and experience among developers and stakeholders. Most frequent and important meetings are in software requirement analysis phase. System engineers and stakeholders discuss software requirements. However, meeting quality is various. Sometimes, stakeholders feel vague decision and suspicious discussion. It is difficult to measure quantitatively the vagueness and suspicion because the vagueness and suspicion are based on human feeling. Therefore, to measure the vagueness and suspicion, our proposed metric is useful. A feature of the metric is to measure only when and who speaks in meetings, not depending on what was said. Hence, the metric does not require software domain knowledge and development experience. The metric consists of system engineers’ speaking time and the number of stakeholders’ speaking within one question by a system engineer. The metric is applied to a practical project. As a result, we automatically extract vague discussion and suspicious discussion in quantitative analysis using the metric. The number of extracted doubtful topic is 37 in all 69 topics. After that, we confirmed that the metric can predict doubtful topics that cause software faults in precision 59.5%, recall 84.5%. In addition, we found that a repeatable topic may cause software faults in requirement meetings.
- Thayer, R. and Dorfman, M. (2000) Software Requirements Engineering. Wiley IEEE Press/Books & eBooks.
- Carver, J.C., Nagappan, N. and Page, A. (2008) The Impact of Educational Background on the E?ectiveness of Requirements Inspections: An Empirical Study. IEEE Transactions on Software Engineering, 34, 800-812. http://dx.doi.org/10.1109/TSE.2008.49
- Kamatar, J. and Hayes, W. (2000) An Experience Report on the Personal Software Process. IEEE Software, 17, 85-89. http://dx.doi.org/10.1109/52.895173
- Dyba, T. and Dingsoyr, T. (2008) Empirical Studies of Agile Software Development: A Systematic Review. Information and Software Technology, 50, 833-859. http://dx.doi.org/10.1016/j.infsof.2008.01.006
- Stellman, A. and Greene, J. (2005) Applied Software Project Management. O’Reilly Media.
- Sawyer, P., Rayson, P. and Cosh, K. (2005) Shallow Knowledge as an Aid to Deep Understanding in Early Phase Requirements Engineering. IEEE Transactions on Software Engineering, 31, 969-981. http://dx.doi.org/10.1109/TSE.2005.129
- Osada, A., Ozawa, D., Kaiya, H. and Kaijiri, K. (2007) The Role of Domain Knowledge Representation in Requirements Elicitation. Proceeding of the 29th International Conference on Software Engineering (ICSE2007), 84-92.
- Doi, K., Horai, H., Watanabe, I., Katayama, Y. and Sonobe (2003) User-Oriented Requirements Capturing Method in Analyzing Requirements Capturing Meeting Requirements Engineering. Transactions of Information Processing Society of Japan, 44, 48-58.
- Dutoit, A.H. and Bruegge, B. (1998) Communication Metrics for Software Development. IEEE Transactions on Software Engineering, 24, 615-628. http://dx.doi.org/10.1109/32.707697
- d’Astous, P. and Robillard, P.N. (2002) Empirical Study of Exchange Patterns during Software Peer Review Meetings. Information and Software Technology, 44, 639-648. http://dx.doi.org/10.1016/S0950-5849(02)00081-2
- Seaman, C.B. and Basili, V.R. (1998) Communication and Organization: An Empirical Study of Discussion in Inspection Meetings, Software Engineering. IEEE Transactions on Software Engineering, 24, 559-572. http://dx.doi.org/10.1109/32.708569
- Damian, D., Lanubile, F. and Mallardo, T. (2008) On the Need for Mixed Media in Distributed Requirements Negotiations. IEEE Transactions on Software Engineering, 34, 116-132. http://dx.doi.org/10.1109/TSE.2007.70758