Communication and Organization: An Empirical Study of Discussion in Inspection Meetings
IEEE Transactions on Software Engineering
Shallow Knowledge as an Aid to Deep Understanding in Early Phase Requirements Engineering
IEEE Transactions on Software Engineering
Systems and Computers in Japan
A Proposal of Indexing Conference Movies with Thinking States
C5 '07 Proceedings of the Fifth International Conference on Creating, Connecting and Collaborating through Computing
The role of domain knowledge representation in requirements elicitation
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
On the Need for Mixed Media in Distributed Requirements Negotiations
IEEE Transactions on Software Engineering
Empirical studies of agile software development: A systematic review
Information and Software Technology
Hi-index | 0.00 |
Requirement analysis of software is an important phase on software development. In practice, stakeholders discuss software requirements with system engineers on meetings. Quality of meetings influences quality of software requirements. Low quality of meetings will lead low quality software. However, measurement of meeting quality is difficult, because meetings for software requirements mainly perform oral discussions among stakeholders and system engineers. Therefore, we propose a new metrics of meeting quality for software requirements are discussed. A feature of the metrics is to measure only when and who speaks. Because the metrics does not depend on analysis of conversations' contents by natural language techniques, the metrics can be easily adapted to various software domains. As a result of adapting practical software development projects, we extracted doubtful discussions in meetings. After that, we confirmed that the metrics can predict doubtful specifications that may lead specification faults in future.