Software architects in practice

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Software architects in practice: handling requirements

Full text

Html (1 KB), Pdf

Pdf (155 KB)

Source

IBM Centre for Advanced Studies Conference archive
Proceedings of the 2006 conference of the Center for Advanced Studies on Collaborative research table of contents

Toronto, Ontario, Canada

SESSION: J table of contents

Article No. 25

Year of Publication: 2006

Authors

Vidya Lakshminarayanan	The University of Texas at Austin, TX
WenQian Liu	University of Toronto, Canada
Charles L Chen	The University of Texas at Austin, TX
Steve Easterbrook	University of Toronto, Canada
Dewayne E Perry	The University of Texas at Austin, TX

Sponsors

: IBM Toronto Lab
: CAS

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 6, Downloads (12 Months): 59, Citation Count: 0

Additional Information:

abstract references index terms collaborative colleagues

Tools and Actions:	Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1188966.1189000 What is a DOI?

ABSTRACT

Software architecture can be a critical factor in software development. Understanding what software architects do in practice is necessary to the enterprise of providing techniques, methods, process, tools and technologies to support the development and use of software architecture. In this paper, we present the results of how architects handle requirements in practice. We then summarize the key lessons learned from the study.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Daniel M. Berry , Rick Kazman , Roel Wieringa, Second international workshop on from SofTware Requirements to Architectures (STRAW'03), Proceedings of the 25th International Conference on Software Engineering, May 03-10, 2003, Portland, Oregon
	2	M. Brandozzi and D. E. Perry, "From Goal-Oriented Requirements to Architectural Prescriptions: The Preskiptor Process", in {3}.
	3	Jaelson Castro , Jeff Kramer, From software requirements to architectures, Proceedings of the 23rd International Conference on Software Engineering, p.764-765, May 12-19, 2001, Toronto, Ontario, Canada
	4	David Garlan, Software architecture: a roadmap, Proceedings of the Conference on The Future of Software Engineering, p.91-101, June 04-11, 2000, Limerick, Ireland [doi>10.1145/336512.336537]
	5	D. Jani, D. Vanderveken and D. E. Perry. "Deriving Architectural Specifications from KAOS Specifications: A Research Case Study". European Workshop on Software Architecture 2005, Pisa Italy.
	6	WenQian Liu , Charles L. Chen , Vidya Lakshminarayanan , Dewayne E. Perry, A design for evidence - based soft research, Proceedings of the 2005 workshop on Realising evidence-based software engineering, p.1-7, May 17-17, 2005, St. Louis, Missouri
	7	Bashar Nuseibeh , Steve Easterbrook, Requirements engineering: a roadmap, Proceedings of the Conference on The Future of Software Engineering, p.35-46, June 04-11, 2000, Limerick, Ireland [doi>10.1145/336512.336523]
	8	D. E. Perry. NSF Grant CCR-0306613 Project Web Site "Transforming Requirement Specifications into Architectural Prescriptions", http://www.ece.utexas.edu/~perry/work/projects/nsf-r2a/ {29 October 2005}
	9	A. van Lamsweerde, "From System Goals to Software Architecture", In M. Bernardo and P. Inverardi, editors, Formal Methods for Software Architectures, 2003.
	10	D. Vanderveken, A. van Lamsweerde, D. E. Perry, and C. Ponsard, "Deriving Architectural Descriptions from Goal-Oriented Requirements Models", September 2005
	11	R. K. Yin, "Case Study Research: Design and Methods", 3/e. Thousand Oaks, CA: Sage Publications, 2002.