Al-Rawas, Amer, and Easterbrook, Steve. Communication
Problems in Requirements Engineering a Field Study / by Amer Al-Rawas and Steve
Easterbrook. Eds. Easterbrook, S. M. and Administration United States.
National Aeronautics and Space. Washington, DC : Springfield, Va.: Washington,
DC : National Aeronautics and Space Administration ; Springfield, Va. :
National Technical Information Service, distributor, 1996. Print. In this
article, the authors attempt to identify the problems that occur when gathering
the requirements for a Software Engineering Project. Directed toward other
engineers who might find use with this information, this article emphasizes
communication between the developers and the end users. There is no bias or
slant in the article, and the evidence does support the main points, but there
is no discussion on the topic of communicating the requirements between a small
group of individuals.
Cherry, Sébastien, and Pierre N. Robillard.
"Communication problems in global software development: Spotlight on a new
field of investigation." (2004): 48-52. The main point of this article is
to point out the inefficiencies of groups that communicate over distance. Aimed
at other software engineers who may find the information useful, this article
goes over means of communication that are not face-to-face. There is no bias or
slant in the source, and the evidence supports the main points, but the article
focuses only on long-distance communication.
Communication Effectiveness v. Richness of
Communication. Digital image. Agile Modeling. N.p., n.d. Web. 12 Mar. 2014. This image is not directed
toward any particular audience, and only serves as a visual for the
effectiveness for different types of communication. No assumptions or major
omissions were made. There would be nothing to gain from altering this image,
so bias can be assumed to be negligible.
Edwards, H. Keith, Robert R. Puckett, and Art
Jolly. "Analyzing Communication Patterns in Software Engineering
Projects." Software Engineering
Research and Practice. 2006. Edwards,
Puckett, and Jolly analyze the communication methods used by Software Engineers
in order to see what is good and what is bad, aiming at other researchers with
the same questions. The author makes no assumptions, getting all their
information from other sources, without emphasizing any single aspect of
communication. There is no bias or omissions.
Hainey, Thomas, et al. "Evaluation of a Game to Teach
Requirements Collection and Analysis in Software Engineering at Tertiary
Education Level." Computers & Education 56.1
(2011): 21-35. Print. Hainey seeks to come up with a way to better prepare
software engineers for real-life software engineering positions by developing a
game-based learning application to teach requirements collection. Directed
toward other researchers who may be interested in this approach, Hainey
emphasizes the use of games over conventional methods in order to teach
Software Engineers how to gather requirements for their projects, without
assuming much, getting information from several other sources. There is no bias
or notable omissions in this article.
Knorzer, Oliver, and Powree. Richard's Guide to Software Development. Digital image.Sandra and Woo. N.p.,
19 Nov. 2012. Web. 12 Mar. 2014. This is an image that depicts the software
development process as a cat, and in each frame, a different version of the cat
is displayed. The author is trying to help visualize the things that go into
software development for common people. It emphasizes the work that goes into a
project, as well as the results of that work, but doesn’t focus on
communication alone. Is there bias? Probably. It is a webcomic, designed to be
more funny than true.
Liu, C., Sandell, K., and Welch, L. “Teaching Communication
Skills in Software Engineering Courses,” Proceedings of the 2005 American
Society for Engineering Education Conference and Exposition, Session 2461.
2005. The main point of this article was to find the best way to teach
communication skills to students in computer science and software engineering.
This article is geared toward professors who should be teaching these
communication skills.
Maiocchi, Marco. "Software Engineering." Future
Generation Computer Systems 7.1 (1991): 23-29. Print. Maiocchi seeks
to provide other researchers with an overview of what software engineers
contribute to software production. The author does not emphasize over any
single software engineering role, and doesn’t make any assumptions as all
required information is found and cited in external sources. There is no bias,
or notable omissions.
McChesney, Ian R., and Séamus Gallagher. "Communication and
Co- Ordination Practices in Software Engineering Projects." Information
and Software Technology 46.7 (2004): 473-89. Print.
Poyhonen, P. J. "Structuring Routine
Interactions in Software Engineering." Managing Complexity in Software Engineering. By Richard Mitchell. Hitchin: Peregrinus on
Behalf of the Institution of Electrical Engineers, 1990. 167-79. Print.
Ruff, S., and M. Carter. "Communication Learning Outcomes
from Software Engineering Professionals: A Basis for Teaching Communication in
the Engineering Curriculum." 2009. 1-6. Print.
"Software
Engineering-Coordination and Communication Issues - Best Online Tutorials |
Source Codes | Programming Languages." 1000 Source Codes. 1000
Source Codes, n.d. Web. 07 Apr. 2014. This article is about the types of
communication that software Engineers use, but not really how they use them. This
article is focused on a more general audience and can be related to by pretty
much everybody. It focuses more on the types of communication, and less on how
those communications are actually used.
