Sage Journals: Discover world-class research

Abstract

The software development process is a collaboration between developers, users experience experts, clients and other stakeholders. Several teams of Computer Science students developed citizen-science Android applications, working with scientists, the application clients and domain experts. We studied the applications’ development and determined the progress and performance of the teams by interviewing team members, studying their emails records, and documents shared by the scientists. The results from usability tests were used to measure the performance of the teams in terms of software correctness and usability. Our results showed that communication between clients and developers during the software development process is more complex than verbal. The quality of the documents shared by the clients is important.

Get full access to this article

View all access options for this article.

References

Alexander

Robertson

(2004). Understanding project sociology by modeling stakeholders. Software, IEEE, 21(1), 23-27.

Alexander

I. F.

(2005). A taxonomy of stakeholders: human roles in system development. International Journal of Technology and Human Interaction (IJTHI), 1(1), 23-59.

Bertram

Voida

Greenberg

Walker

(2010). Communication, collaboration, and bugs: the social nature of issue tracking in small, collocated teams. In Proceedings of the 2010 ACM conference on Computer supported cooperative work (pp. 291-300). ACM.

Chatzoglou

P. D.

Macaulay

L. A.

(1996). Requirements capture and analysis: A survey of current practice. Requirements Engineering, 1(2), 75-87.

Damian

(2007). Stakeholders in global requirements engineering: Lessons learned from practice. Software, IEEE, 24(2), 21-27.

Freeman

R. B.

Medoff

J. L.

(1984). What do unions do. Indus. & Lab. Rel. Rev., 38, 244.

Freeman

McVea

(2001). A stakeholder approach to strategic management.

Grimble

Chan

M. K.

(1995, May). Stakeholder analysis for natural resource management in developing countries. In Natural resources forum (Vol. 19, No. 2, pp. 113-124). Blackwell Publishing Ltd.

Hanneman

R. A.

Riddle

(2005). Introduction to social network methods.

10.

Hein

A. M.

Tziolas

A. C.

Osborne

(2011). Project Icarus: Stakeholder Scenarios for an Interstellar Exploration Program. Journal of the British Interplanetary Society, 64, 224-233.

11.

Keil

Carmel

(1995). Customer-developer links in software development. Communications of the ACM, 38(5), 33-44.

12.

Martin

(1984). An information systems manifesto (pp. 8-1). Englewood Cliffs, NJ: Prentice-Hall.

13.

Mayer

Pastel

Wallace

Oppliger

Donovan

Environmental cybercitizens: Engaging citizen scientists in global environmental change through crowdsensing and visualization. http://www.nsf.gov/awardsearch/showAward?AWD_ID=1135523&HistoricalAwards=false

14.

Moe

N. B.

Dingsøyr

Dybå

(2010). A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology, 52(5), 480-491.

15.

Pastel

Brown

Woller-Carter

Kumar

(2012, September). Teaching Human Factors to Graduate and Undergraduate Computer Science Students. In Proceedings of the Human Factors and Ergonomics Society Annual Meeting (Vol. 56, No. 1, pp. 595-599). SAGE Publications.

16.

Pouloudi

(1999). Aspects of the stakeholder concept and their implications for information systems development. In System Sciences, 1999. HICSS-32. Proceedings of the 32nd Annual Hawaii International Conference on (pp. 17 pp). IEEE.

17.

Roberts

N. C.

Bradley

R. T.

(1991). Stakeholder collaboration and innovation: A study of public policy initiation at the state level. The Journal of applied behavioral science, 27(2), 209-227.

18.

Saeki

(1995, December). Communication, collaboration and cooperation in software development-how should we support group work in software development?. In Software Engineering Conference, 1995. Proceedings., 1995 Asia Pacific (pp. 12-20). IEEE.

19.

Sommerville

Sawyer

(1997): Requirements Engineering - A Good Practice Guide, John Wiley & Sons, England.

20.

Thanasankit

Corbitt

(2000). Cultural context and its impact on requirements elicitation in Thailand. The Electronic Journal of Information Systems in Developing Countries, 1.

Communication is More than Verbal

Abstract

Get full access to this article

References