Hakan Erdogmus

Oryal Tanir

This book contains both relevant real-world research, as well as reviews of different areas of interest in the software engineering literature, such as clone identification. The contents of the various sections will provide a better understanding of known problems and detailed treatment of advanced topics. Consequently, the book consolidates the work and findings from leading researchers in the software research community in key areas such as maintainability, architectural recovery, code analysis, software migration, and tool support.

Comprehension, Evaluation, and Evolution

Advances in Software Engineering

Lowell Lindstrom

Carmen Zannier

It was 1999 when Extreme Programming Explained was ?rst published, making this year’s event arguably the ?fth anniversary of the birth of the XP/Agile movement in software development. Our fourth conference re?ected the evolution and the learning that have occurred in these exciting ?ve years as agile practices have become part of the mainstream in software development. These pages are the proceedingsof XP Agile Universe 2004, held in beautiful Calgary, gateway to the Canadian Rockies, in Alberta, Canada. Evidentintheconferenceis thefactthatourlearningis still inits earlystages. While at times overlooked,adaptation has beena core principleof agile software development since the earliest literature on the subject. The conference and these proceedings re- force that principle. Although some organizations are able to practice agile methods in the near-pure form, most are not, re?ecting just how radically innovativethese methods areto thisday. Anyinnovationmustcoexistwithan existingenvironmentandagileso- ware development is no different. There are numerous challenges confronting IT and software development organizations today, with many solutions pitched by a cadre of advocates. Be it CMM, offshoring, outsourcing, security, or one of many other current topics in the industry, teams using or transitioning to Extreme Programming and other agile practices must integrate with the rest of the organization in order to succeed. The papers here offer some of the latest experiences that teams are having in those efforts. XP Agile Universe 2004consisted of workshops,tutorials, papers, panels, the Open Space session, the Educators’ Symposium, keynotes, educational games and industry presentations.

4th Conference on Extreme Programming and Agile Methods, Calgary, Canada, August 15-18, 2004, Proceedings

Extreme Programming and Agile Methods - XP/Agile Universe 2004

This book constitutes the refereed proceedings of the 4th Conference on Extreme Programming and Agile Methods, XP/Agile Universe 2004, held in Calgary, Canada in August 2004. The 18 revised full papers presented together with summaries of workshops, panels, and tutorials were carefully reviewed and selected from 45 submissions. The papers are organized in topical sections on testing and integration, managing requirements and usability, pair programming, foundations of agility, process adaptation, and educational issues.

ICCBSS 2003 (2003 : Ottawa, Ont.)

This book constitutes the refereed proceedings of the Second International Conference on COTS-Based Software Systems, ICCBSS 2003, held in Ottawa, Canada in February 2003. The 24 revised full papers presented were carefully reviewed and selected from numerous submissions. The papers address all current issues on commcerial-off-the-shelf-systems, from the point of view of research and development as well as from the practitioner's application point of view.

Second International Conference, ICCBSS 2003 Ottawa, Canada, February 10-13, 2003

COTS-Based Software Systems

Tao Weng

Paul Grünbacher

Barry Boehm

Stefan Biffl

Aybuke Aurum

Ross Jeffery When, as a result of pressure from the CEO, the Chief Information Officer poses the question “Just what is this information system worth to the organization?” the IT staff members are typically at a loss. “That’s a difficult question,” they might say; or “well it really depends” is another answer. Clearly, neither of these is very satisfactory and yet both are correct. The IT community has struggled with qu- tions concerning the value of an organization’s investment in software and ha- ware ever since it became a significant item in organizational budgets. And like all questions concerning value, the first step is the precise determination of the object being assessed and the second step is the identification of the entity to which the value is beneficial. In software engineering both of these can be difficult. The p- cise determination of the object can be complex. If it is an entire information s- tem in an organizational context that is the object of interest, then boundary defi- tion becomes an issue. Is the hardware and middleware to be included? Can the application exist without any other applications? If however the object of interest is, say, a software engineering activity such as testing within a particular project, then the boundary definition becomes a little easier. But the measure of benefit may become a little harder.

Hakan Erdogmus

About

Books

Join the club