A Requirement Elicitation Method in Collaborative Software Development Community

  • Masatoshi Shimakage
  • Atsuo Hazeyama
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3009)


We developed a collaborative software development community-ware whose goal is to provide practical tasks for the students in software engineering education in a university and to provide software for education purpose. We performed a pilot experimentation for the community-ware. The results show that software requesters made software change requests for not only functional aspects but also user interface. This paper proposes a user interface oriented requirement elicitation process. The process is that software requesters present functional requests and user interface design which met the requests. Then based on the requests and the user interface, developers and software requesters decide priority for each requirement in a collaborative manner.


Functional Requirement Release Planning Requirement Engineer Requirement Elicitation Change Request 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Bruegge, B., Dutoit, A.H., Kobylinski, R., Teubner, G.: Transatlantic Project Courses in a University Environment. In: Proceedings of the Seventh Asia Pacific Software Engineering Conference, pp. 30–37. IEEE CS Press, Los Alamitos (2000)CrossRefGoogle Scholar
  2. 2.
    Curtis, B., Krasner, H., Iscoe, N.: A Field Study of the Software Design Process for Large Systems. Communications of the ACM 31(11), 1268–1287 (1988)CrossRefGoogle Scholar
  3. 3.
    Davis, A.M.: A Strategy for Comparing Alternative Software Development Life Cycle Models. IEEE Transactions on Software Engineering 14(10), 1453–1461 (1988)CrossRefGoogle Scholar
  4. 4.
    Deifel, B.: A Process Model for Requirements Engineering of COTS. In: Proceedings of the DEXA, pp. 316–320. IEEE CS Press, Los Alamitos (1999)Google Scholar
  5. 5.
    Proceedings of the International Workshop on Global Software Development (2003),
  6. 6.
    Karlsson, J., Ryan, K.: A Cost-Value Approach for Prioritizing Requirements. IEEE Software 14(5), 67–74 (1997)CrossRefGoogle Scholar
  7. 7.
    Komiya, S., Kato, J., Nagata, M., Ohnishi, A., Saeki, M., Yamamoto, S., Horai, H.: A Realization Method of the System to Navigate Requirements Elicitation Work Driven by Interviews. IPSJ SIGNotes SE121-13, 99-106 (1998) (in Japanese)Google Scholar
  8. 8.
    Lang, M., Duggan, J.: A Tool to Support Collaborative Software Requirements Management. Requirements Engineering (6), 161–172 (2001)Google Scholar
  9. 9.
    Raymond, E.: The Cathedral and Bazaar,
  10. 10.
    Regnell, B., Beremark, P., Eklundh, O.: A Market-driven Requirements Engineering Process - Results from an Industrial Process Improvement Programme. In: Proceedings of Conference on European Industrial Requirements Engineering, CEIRE 1998 (1998)Google Scholar
  11. 11.
    Saaty, T.L.: The Analytic Hierarchy Process. In: Procededings of the International Symposium of the Analytic Hierarchy Process (1999)Google Scholar
  12. 12.
    Shimakage, M., Hazeyama, A., Ishide, T.: Collaborative Software Development Communityware and Its Prelimenary Applicatiuon. In: Proceedings of the First International Conference on Knowledge Economy and Development of Science and Technology (2003)Google Scholar
  13. 13.

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Masatoshi Shimakage
    • 1
  • Atsuo Hazeyama
    • 1
  1. 1.Graduate School of Mathematics and InformaticsTokyo Gakugei UniversityTokyoJapan

Personalised recommendations