Sun, 27 Jul 2008 08:13:06 BST CiteULike: germoglio's library [321 articles] http://www.citeulike.org/user/germoglio CiteULike.org en-gb Copyright © 2004-2008 citeulike.org http://www.citeulike.org/user/germoglio/article/382774 <i>(28 June 2004)</i><br /><br /><p>Sams has assembled a team of experts in web services to provide you with a detailed reference guide on XML, SOAP, USDL and UDDI. <i>Building Web Services with Java</i> is in its second edition and it includes the newest standards for managing security, transactions, reliability and interoperability in web service applications. Go beyond the explanations of standards and find out how and why these tools were designed as they are and focus on practical examples of each concept. Download your source code from the publisher's website and work with a running example of a full enterprise solution. Learn from the best in <i>Building Web Services with Java</i>.</p> Building Web Services with SOAP, XML, and UDDI assumes proficiency with Java and with distributed computing tools. Throughout the book, examples will be presented using Java and the Apache SOAP platform, although a set of sidebars will address .NET development, which Microsoft developers will use to deploy Web services. The book uses progressive disclosure to present an increasingly complex project as it moves through its development cycle. The final section of the book presents linking the completed project with other systems built in J2EE and .NET. Building Web Services with Java : Making Sense of XML, SOAP, WSDL, and UDDI (2nd Edition) (Developer's Library) Steve Graham Doug Davis Simeon Simeonov Glen Daniels Peter Brittenham Yuichi Nakamura Paul Fremantle Dieter Koenig Claudia Zentner (28 June 2004) 2005-11-07T14:58:12-00:00 2004 Sams java webservices http://www.citeulike.org/user/germoglio/article/3009493 <i>Software Engineering, 2002. ICSE 2002. Proceedings of the 24rd International Conference on (2002), pp. 681-682.</i><br /><br />Many software organizations are in the transition from project-centric to architecture-centric engineering of software. This tutorial addresses this development by providing an overview and in-depth treatment of the issues surrounding the architecture-centric engineering of software. Topics include software architecture design in the presence of existing components and infrastructure (top-down versus bottom-up), architecture evaluation and assessment, software artefact variability management, software product lines and the role of the software architect. These topics are, in addition to the technical perspective, discussed from process and organizational viewpoints. The topics are extensively illustrated by examples and experiences from many industrial cases. The tutorial presents our experiences, reflections and research results concerning architecture-centric software engineering. Architecture-centric software engineering J Bosch Software Engineering, 2002. ICSE 2002. Proceedings of the 24rd International Conference on (2002), pp. 681-682. 2008-07-16T18:52:01-00:00 2002 Software Engineering, 2002. ICSE 2002. Proceedings of the 24rd International Conference on 681 682 architecture software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/3009462 <i>Software Engineering, 1999. Proceedings of the 1999 International Conference on (1999), pp. 690-691.</i> Modeling and analyzing software architectures RT Monroe Software Engineering, 1999. Proceedings of the 1999 International Conference on (1999), pp. 690-691. 2008-07-16T18:28:30-00:00 1999 Software Engineering, 1999. Proceedings of the 1999 International Conference on 690 691 analysis architecture models software-architecture http://www.citeulike.org/user/germoglio/article/3009454 <i>Software Engineering, 2002. ICSE 2002. Proceedings of the 24rd International Conference on (2002), pp. 693-694.</i><br /><br />The presence of a solid architectural vision is a key discriminator in the success or failure of a software project. This paper examines what software architecture is and what it is not. It discusses and illustrates how to describe architecture through a set of design viewpoints and views and how to express these views in the UML, in the spirit of the new IEEE Standard 1471:2000: Recommended practice for architectural description. The paper shows of how architectures drive the development process and how to capture architectural design patterns using the UML. It is illustrated by several widely applicable architectural patterns in different domain. Tutorial: describing software architecture with UML P Kruchten B Selic W Kozaczynski Software Engineering, 2002. ICSE 2002. Proceedings of the 24rd International Conference on (2002), pp. 693-694. 2008-07-16T18:22:43-00:00 2002 Software Engineering, 2002. ICSE 2002. Proceedings of the 24rd International Conference on 693 694 architecture description software-architecture uml http://www.citeulike.org/user/germoglio/article/3009452 <i>Software Engineering - Companion, 2007. ICSE 2007 Companion. 29th International Conference on (2007), pp. 170-171.</i><br /><br />Capturing the technical knowledge, contextual information, and rationale surrounding the design decisions underpinning system architectures can greatly improve the software development process. If not managed, this critical knowledge is implicitly embedded in the architecture, becoming tacit knowledge which erodes as personnel on the project change. Moreover, the unavailability of architecture knowledge precludes organizations from growing their architectural capabilities. In this tutorial, we highlight the benefits and challenges in managing software architecture knowledge. We discuss various approaches to characterize architecture knowledge based on the requirements of a particular domain. We describe various concepts and approaches to manage the architecture knowledge from both management and technical perspectives. We also demonstrate the utility of captured knowledge to support software architecture activities with a case study covering the use of architecture knowledge management techniques and tools in an industrial project. Architecture Knowledge Management: Challenges, Approaches, and Tools Muhammad Babar Ian Gorton doi:10.1109/ICSECOMPANION.2007.20 Software Engineering - Companion, 2007. ICSE 2007 Companion. 29th International Conference on (2007), pp. 170-171. 2008-07-16T18:21:36-00:00 2007 Software Engineering - Companion, 2007. ICSE 2007 Companion. 29th International Conference on 170 171 architecture decisions knowledge software-architecture http://www.citeulike.org/user/germoglio/article/3009004 <i>Software Engineering, 2004. ICSE 2004. Proceedings. 26th International Conference on (2004), pp. 533-542.</i><br /><br />Based on interviews with a number of architects and managers from a wide range of organizations, we characterize how architecture is perceived in practice. We identify three groups of organizations that differ with respect to their level of architectural thinking and the alignment of business and IT on architectural issues. Analysis of the interviews further indicates that these three groups differ in the architecture aspects and critical success factors they emphasize. Our results provide a starting point for assessing architecture maturity and alignment within organizations, and can be used to help harmonize different architectural tunes played within organizations. Polyphony in architecture B van der Raadt J Soetendal M Perdeck H van Vliet Software Engineering, 2004. ICSE 2004. Proceedings. 26th International Conference on (2004), pp. 533-542. 2008-07-16T17:20:38-00:00 2004 Software Engineering, 2004. ICSE 2004. Proceedings. 26th International Conference on 533 542 architect architecture process software-engineering http://www.citeulike.org/user/germoglio/article/3008494 <i>Curriculum Inquiry, Vol. 18, No. 4. (1988), pp. 401-423.</i> Using Textbooks and Teachers' Guides: A Dilemma for Beginning Teachers and Teacher Educators Deborah Ball Sharon Nemser doi:10.2307/1179386 Curriculum Inquiry, Vol. 18, No. 4. (1988), pp. 401-423. 2008-07-16T13:19:03-00:00 1988 Curriculum Inquiry 18 4 401 423 Blackwell Publishing on behalf of the Ontario Institute for Studies in Education/University of Toronto education textbook http://www.citeulike.org/user/germoglio/article/3008492 <i>ELT J, Vol. 48, No. 4. (1 October 1994), pp. 315-328.</i><br /><br />Why does there appear to be apathy and even hostility to the ELT textbook in the literature? Why does it survive and prosper apparently in contradiction to the development of ideas in applied linguistics? In this paper, we first consider the role of the textbook in terms of its normal day-to-day use in teaching and learning English, and then consider its role in the process of change. We refer to data from a study carried out in the Philippines into the introduction of an ESP textbook. In the light of our analysis, we challenge some of the assumptions that underlie the anti-textbook view. We argue that the textbook has a vital and positive part to play in the everyday job of teaching and learning English, and that the importance of the textbook becomes even greater in periods of change. Finally, we consider the implications of a more informed and positive view of the role of the textbook, emphasizing, in particular, the need to see textbook creation and teacher education as complementary and mutually beneficial aspects of professional development.1 10.1093/elt/48.4.315 The textbook as agent of change Tom Hutchinson Eunice Torres doi:10.1093/elt/48.4.315 ELT J, Vol. 48, No. 4. (1 October 1994), pp. 315-328. 2008-07-16T13:17:54-00:00 1994 ELT J 48 4 315 328 education textbook http://www.citeulike.org/user/germoglio/article/3008485 <i>Journal of Geography in Higher Education, Vol. 17, No. 2. (1993), pp. 123-129.</i><br /><br />This paper outlines some of the advantages and disadvantages of using one textbook in the teaching of an introductory course in economic geography. It is argued that, if careful thought is given to how a course text can be used, the advantages can outweigh the disadvantages. Basing a course around a suitable textbook can be a beneficial way of teaching an introductory course, particularly if this is complemented by other teaching strategies. With this method of teaching, students have to take a greater responsibility for their own learning and this can provide them with a transition to independent enquiry. Teaching a course around a textbook Mick Healey Brian Ilbery doi:10.1080/03098269308709214 Journal of Geography in Higher Education, Vol. 17, No. 2. (1993), pp. 123-129. 2008-07-16T13:15:45-00:00 1993 Journal of Geography in Higher Education 17 2 123 129 Routledge education geography textbook http://www.citeulike.org/user/germoglio/article/3008077 <i>Advanced Learning Technologies, 2000. IWALT 2000. Proceedings. International Workshop on (2000), pp. 8-11.</i><br /><br />Over the years the author has had the opportunity to evaluate hundreds of instructional products. An amazing number of these are surprisingly ineffective and some do not teach at all. Like a book, too much instruction is judged by its cover; the glitz, glitter, or game-like interaction that too often is irrelevant to the effectiveness of the instruction. This workshop looks beneath the production quality of the instructional product to the instructional strategies involved, those aspects of the instruction that are hard to observe on the surface, but that determine whether or not the product will really teach. In this presentation you will learn to rate an instructional product on those characteristics that effect its ability to teach rather than those attributes that contribute only to its market appeal. The presentation introduces and illustrates a rating system to determine the instructional effectiveness, efficiency, and appeal of an instructional product. It describes and illustrates what is required for five star instruction Does your instruction rate 5 stars? MD Merill doi:10.1109/IWALT.2000.890552 Advanced Learning Technologies, 2000. IWALT 2000. Proceedings. International Workshop on (2000), pp. 8-11. 2008-07-16T11:15:15-00:00 2000 Advanced Learning Technologies, 2000. IWALT 2000. Proceedings. International Workshop on 8 11 education http://www.citeulike.org/user/germoglio/article/3000381 <i>metrics, Vol. 0 (2005)</i> Metrics of Software Architecture Changes Based on Structural Distance Taiga Nakamura Victor Basili doi:10.1109/METRICS.2005.35 metrics, Vol. 0 (2005) 2008-07-14T23:40:15-00:00 2005 metrics 0 IEEE Computer Society architecture evolution metrics software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/2976696 <i>Software, IEEE, Vol. 25, No. 4. (2008), pp. 14-15.</i><br /><br />Without refactoring, complex software-intensive systems become increasingly irregular and thus increasingly chaotic over time. We can understand complex software systems only when they're nearly decomposable and hierarchic. One measure the author uses is lines of source code: the greater the SLOC, the more inertia to change the system will have, the more people it will take to keep it fed, the more stakeholders who will be crawling all over it. The author describes the more complex measures he uses; these are tuned to Philippe Kruchten's 4+1 view model of architecture. He also counts the number of identifiable design patterns at work. These metrics can generally be gathered automatically via clever mining of configuration management and testing data. Measuring Architectural Complexity Grady Booch doi:10.1109/MS.2008.91 Software, IEEE, Vol. 25, No. 4. (2008), pp. 14-15. 2008-07-09T13:50:07-00:00 2008 Software, IEEE 25 4 14 15 architecture complexity software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/2976681 <i>Software Maintenance and Reengineering, 2008. CSMR 2008. 12th European Conference on (2008), pp. 274-278.</i><br /><br />We study the impact of design patterns on quality attributes in the context of software maintenance and evolution. We show that, contrary to popular beliefs, design patterns in practice impact negatively several quality attributes, thus providing concrete evidence against common lore. We then study design patterns and object-oriented best practices by formulating a second hypothesis on the impact of these principles on quality. We show that results for some design patterns cannot be explained and conclude on the need for further studies. Thus, we bring further evidence that design patterns should be used with caution during development because they may actually impede maintenance and evolution. Do Design Patterns Impact Software Quality Positively? F Khomh YG Gueheneuc doi:10.1109/CSMR.2008.4493325 Software Maintenance and Reengineering, 2008. CSMR 2008. 12th European Conference on (2008), pp. 274-278. 2008-07-09T13:42:31-00:00 2008 Software Maintenance and Reengineering, 2008. CSMR 2008. 12th European Conference on 274 278 design design-patterns software software-engineering http://www.citeulike.org/user/germoglio/article/2973118 <i>(01 July 2008)</i><br /><br />Algorithms are at the heart of every nontrivial computer application, and algorithmics is a modern and active area of computer science. Every computer scientist and every professional programmer should know about the basic algorithmic toolbox: structures that allow efficient organization and retrieval of data, frequently used algorithms, and basic techniques for modeling, understanding and solving algorithmic problems. This book is a concise introduction addressed to students and professionals familiar with programming and basic mathematical language. Individual chapters cover arrays and linked lists, hash tables and associative arrays, sorting and selection, priority queues, sorted sequences, graph representation, graph traversal, shortest paths, minimum spanning trees, and optimization. The algorithms are presented in a modern way, with explicitly formulated invariants, and comment on recent trends such as algorithm engineering, memory hierarchies, algorithm libraries and certifying algorithms. The authors use pictures, words and high-level pseudocode to explain the algorithms, and then they present more detail on efficient implementations using real programming languages like C++ and Java. The authors have extensive experience teaching these subjects to undergraduates and graduates, and they offer a clear presentation, with examples, pictures, informal explanations, exercises, and some linkage to the real world. Most chapters have the same basic structure: a motivation for the problem, comments on the most important applications, and then simple solutions presented as informally as possible and as formally as necessary. For the more advanced issues, this approach leads to a more mathematical treatment, including some theorems and proofs. Finally, each chapter concludes with a section on further findings, providing views on the state of research, generalizations and advanced solutions. Algorithms and Data Structures: The Basic Toolbox Kurt Mehlhorn Peter Sanders (01 July 2008) 2008-07-08T18:16:24-00:00 2008 Springer algorithms data-structures programming http://www.citeulike.org/user/germoglio/article/940956 <i>Information and Software Technology, Vol. 49, No. 1. (January 2007), pp. 12-31.</i><br /><br />In 2000, we published an extensive study of existing software architecture description languages (ADLs), which has served as a useful reference to software architecture researchers and practitioners. Since then, circumstances have changed. The Unified Modeling Language (UML) has gained popularity and wide adoption, and many of the ADLs we studied have been pushed into obscurity. We argue that this progression can be attributed to early ADLs' nearly exclusive focus on technological aspects of architecture, ignoring application domain and business contexts within which software systems and development organizations exist. These three concerns - technology, domain, and business - constitute three "lampposts" needed to appropriately "illuminate" software architecture and architectural description. Moving architectural description from under the technology lamppost Nenad Medvidovic Eric Dashofy Richard Taylor doi:10.1016/j.infsof.2006.08.006 Information and Software Technology, Vol. 49, No. 1. (January 2007), pp. 12-31. 2006-11-12T23:20:53-00:00 2007 Information and Software Technology 49 1 12 31 architecture description software software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/200871 <i>(01 September 2002)</i> The Design of Everyday Things Donald Norman (01 September 2002) 2005-05-15T19:31:16-00:00 2002 Basic Books design http://www.citeulike.org/user/germoglio/article/261736 <i>(15 March 2000)</i><br /><br />We live in a dynamic economic and commerical world, surrounded by objects of remarkable complexity and power. In many industries, changes in products and technologies have brought with them new kinds of firms and forms of organization. We are discovering news ways of structuring work, of bringing buyers and sellers together, and of creating and using market information. Although our fast-moving economy often seems to be outside of our influence or control, human beings create the things that create the market forces. Devices, software programs, production processes, contracts, firms, and markets are all the fruit of purposeful action: they are designed.<br /> <br /> Using the computer industry as an example, Carliss Y. Baldwin and Kim B. Clark develop a powerful theory of design and industrial evolution. They argue that the industry has experienced previously unimaginable levels of innovation and growth because it embraced the concept of <i>modularity</i>, building complex products from smaller subsystems that can be designed independently yet function together as a whole. Modularity freed designers to experiment with different approaches, as long as they obeyed the established <i>design rules</i>. Drawing upon the literatures of industrial organization, real options, and computer architecture, the authors provide insight into the forces of change that drive today's economy. Design Rules, Vol. 1: The Power of Modularity Carliss Baldwin Kim Clark (15 March 2000) 2005-07-21T16:21:36-00:00 2000 The MIT Press design guidelines models http://www.citeulike.org/user/germoglio/article/2972522 <i>Institute for Software Research, University of California, Irvine, Technical Report UCI-ISR-06-15, October (2006)</i> Examining Software Design from a General Design Perspective A Baker A van der Hoek Institute for Software Research, University of California, Irvine, Technical Report UCI-ISR-06-15, October (2006) 2008-07-08T12:49:16-00:00 2006 Institute for Software Research, University of California, Irvine, Technical Report UCI-ISR-06-15, October design software-design http://www.citeulike.org/user/germoglio/article/175025 <i>(24 April 1998)</i> Art of Computer Programming, Volume 3: Sorting and Searching (2nd Edition) Donald Knuth (24 April 1998) 2005-04-30T15:57:56-00:00 1998 Addison-Wesley Professional programming sorting http://www.citeulike.org/user/germoglio/article/2931911 <i>Commun. ACM, Vol. 28, No. 6. (June 1985), pp. 590-603.</i> On time and space decomposition of complex structures PJ Courtois doi:10.1145/3812.3814 Commun. ACM, Vol. 28, No. 6. (June 1985), pp. 590-603. 2008-06-26T18:26:47-00:00 1985 Commun. ACM 0001-0782 28 6 590 603 ACM complexity design http://www.citeulike.org/user/germoglio/article/2931443 <i>(29 January 2008)</i> Envisioning the Many Levels of Architectural Enlightenment Mike Rosen (29 January 2008) 2008-06-26T16:56:20-00:00 2008 architect architecture education software-engineering http://www.citeulike.org/user/germoglio/article/1376130 <i>(30 April 2007)</i><br /><br />In this eagerly awaited second edition, Grady Booch draws upon the rich and varied results of those projects and offers improved methods for object development and a new, unified notation. With numerous examples implemented in C++, Booch illustrates essential concepts, explains the method, and shows successful applications in a variety of fields. Booch also gives pragmatic advice on a host of issues, including classification, implementation strategies, and cost-effective project management. A two-time winner of <B>Software Development's</B> coveted <B>Jolt Cola Product Excellence Award!</B> <p><b>Object-Oriented Design with Applications</b> has long been the essential reference to object-oriented technology, which, in turn, has evolved to join the mainstream of industrial-strength software development. In this third edition--the first revision in 13 years--readers can learn to apply object-oriented methods using new paradigms such as Java, the Unified Modeling Language (UML) 2.0, and .NET.</p><p>The authors draw upon their rich and varied experience to offer improved methods for object development and numerous examples that tackle the complex problems faced by software engineers, including systems architecture, data acquisition, cryptoanalysis, control systems, and Web development. They illustrate essential concepts, explain the method, and show successful applications in a variety of fields. You'll also find pragmatic advice on a host of issues, including classification, implementation strategies, and cost-effective project management.</p><p>New to this new edition are</p><ul><li>An introduction to the new UML 2.0, from the notation's most fundamental and advanced elements with an emphasis on key changes</li><li>New domains and contexts</li><li>A greatly enhanced focus on modeling--as eagerly requested by readers--with five chapters that each delve into one phase of the overall development lifecycle.</li><li>Fresh approaches to reasoning about complex systems</li><li>An examination of the conceptual foundation of the widely misunderstood fundamental elements of the object model, such as abstraction, encapsulation, modularity, and hierarchy</li><li>How to allocate the resources of a team of developers and mange the risks associated with developing complex software systems</li><li>An appendix on object-oriented programming languages</li></ul><p>This is the seminal text for anyone who wishes to use object-oriented technology to manage the complexity inherent in many kinds of systems.</p> Object-Oriented Analysis and Design with Applications (3rd Edition) Grady Booch Robert Maksimchuk Michael Engel Bobbi Young Jim Conallen Kelli Houston (30 April 2007) 2007-06-10T14:44:15-00:00 2007 Addison-Wesley Professional analysis book design object-oriented-programming http://www.citeulike.org/user/germoglio/article/1341545 <i>IEEE Std 610.12-1990 (1990)</i><br /><br />Describes the IEEE Std 610.12-1990, IEEE standard glossary of software engineering terminology, which identifies terms currently in use in the field of software engineering. Standard definitions for those terms are established IEEE standard glossary of software engineering terminology IEEE Std 610.12-1990 (1990) 2007-05-29T17:55:47-00:00 1990 IEEE Std 610.12-1990 glossary software software-engineering http://www.citeulike.org/user/germoglio/article/2908078 <i>IEEE Software, Vol. 25, No. 4. (2008), pp. 16-17.</i> What Is a Requirements Engineer? Barbara Paech doi:http://doi.ieeecomputersociety.org/10.1109/MS.2008.106 IEEE Software, Vol. 25, No. 4. (2008), pp. 16-17. 2008-06-19T16:39:12-00:00 2008 IEEE Software 25 4 16 17 IEEE Computer Society requirements software software-engineering http://www.citeulike.org/user/germoglio/article/2884069 <i>(December 2007)</i> Apoio para o Ensino de Projeto de Arquitetura de Software Guilherme Germoglio (December 2007) 2008-06-12T01:25:42-00:00 2007 architecture education proposal software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/2878408 <i>(1991)</i> IEEE Standard Computer Dictionary: Compilation of IEEE Standard Computer Glossaries Anne Geraci (1991) 2008-06-10T01:16:26-00:00 1991 Institute of Electrical and Electronics Engineers Inc., The computer-science definition http://www.citeulike.org/user/germoglio/article/2530329 <i>(1978)</i> Characteristics of Software Quality (TRW series of software technology) Barry Boehm John Brown Hans Kaspar Myron Lipow Gordon Macleod Michael Merritt (1978) 2008-03-14T00:58:48-00:00 1978 Elsevier architecture requirements software software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/2878404 <i>No. CMU/SEI-95-TR-021 ESC-TR-95-021. (December 1995)</i> Quality Attributes Mario Barbacci Mark Klein Thomas Longstaff Charles Weinstock No. CMU/SEI-95-TR-021 ESC-TR-95-021. (December 1995) 2008-06-10T01:10:14-00:00 1995 CMU/SEI-95-TR-021 ESC-TR-95-021 requirements software software-engineering http://www.citeulike.org/user/germoglio/article/2869314 <i>SIGSOFT Softw. Eng. Notes, Vol. 20, No. 2. (April 1995), pp. 42-47.</i> SMART requirements Mike Mannion Barry Keepence doi:10.1145/224155.224157 SIGSOFT Softw. Eng. Notes, Vol. 20, No. 2. (April 1995), pp. 42-47. 2008-06-06T12:26:56-00:00 1995 SIGSOFT Softw. Eng. Notes 0163-5948 20 2 42 47 ACM guidelines requirements software software-engineering http://www.citeulike.org/user/germoglio/article/453462 <i>(26 February 2003)</i><br /><br />"Requirements" are essential for creating successful software because they let users and developers agree on what features will be delivered in new systems. Karl Wiegers's <I>Software Requirements</I> shows you how to define and get more out of software requirements with dozens of "best practices" and tips that make this book a valuable resource for both software project managers and developers.<p> The book's commonsense approach provides exemplary project management skills tailored to gathering (and refining, implementing, and eventually tracking) software requirements. While the book often cites recent software engineering studies, the focus always returns to practical management techniques. A case study for a chemical tracking application frames the book, and most chapters begin with anecdotes that demonstrate situations in which users and developers misunderstand each other about a software project's ultimate goals. (If you've ever worked in the field, these stories will probably sound all too familiar.)<p> This book offers hope, though, for improving your software design process, with dozens of tips on getting better design input from your customers and then using these requirements to generate a variety of design documents. There are numerous templates and sample documents too--a big help for the busy software manager.<p> Several standout sections cover negotiating difficult steps in the process, particularly how to manage shifting requirements as projects move forward and keep the various users and stakeholders content throughout the software process. Late in the book, the author surveys today's software management tools and shows how to pick the right ones for your organization.<p> Anchored by the author's considerable experience and software engineering expertise, this jargon-free and practical guide to software requirements can definitely give you the edge in managing software projects more efficiently. <I>--Richard Dragan</I><p> <B>Topics covered</B>: software requirements specifications (SRS); business and user requirements; risk management; the requirements process; sample documents and templates; requirements development: elicitation, analysis, specification, and verification; rights and responsibilities for software customers; best practices; project management tips; process assessment and improvement; types of users; product champions; use cases and other diagrams; tips for prototyping; managing requirements change; change centered boards (CCBs); evaluating and using requirements tools; requirements traceability matrix; impact analysis. Learn proven, real-world techniques for managing the software requirements engineering process. This award-winning book has been expanded with new topics, including use cases, up-to-date tools, more field examples, and a new troubleshooting guide. Software Requirements, Second Edition Karl Wiegers (26 February 2003) 2005-12-30T18:13:31-00:00 2003 Microsoft Press requirements software software-engineering http://www.citeulike.org/user/germoglio/article/2869259 <i>(August 2001)</i> Defining Non-Functional Requirements Ruth Malan Dana Bredemeyer (August 2001) 2008-06-06T11:41:40-00:00 2001 architecture requirements software-architecture http://www.citeulike.org/user/germoglio/article/2865301 <i>(18 May 2003)</i> Lean Software Development: An Agile Toolkit (The Agile Software Development Series) Mary Poppendieck Tom Poppendieck (18 May 2003) 2008-06-05T12:24:10-00:00 2003 Addison-Wesley Professional agile software software-engineering http://www.citeulike.org/user/germoglio/article/1562081 <i>(20 April 2005)</i><br /><br /><P>The field of software architecture continues to grow in acceptance and</P><P>importance. However, this burgeoning discipline has thus far lacked an</P><P>authoritative treatment that helps its practitioners gain valuable perspective and</P><P>a thorough understanding of the disparate viewpoints that project stakeholders</P><P>bring to the project. In this new book written by two practicing software</P><P>architects, the field of software architecture now has an invaluable resource for</P><P>designing and implementing successful software architectures.</P><P>Colleagues, business management, and ultimately customers appreciate the</P><P>benefit of solid software systems architecture, and this new book helps the</P><P>architect deliver it. This software architecture handbook will be referred to time</P><P>and again. It is a single source of proven practices and valuable advice that will</P><P>help the software architect shepherd a project through its entire lifecycle.</P> Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives Nick Rozanski Eóin Woods (20 April 2005) 2007-08-15T07:33:13-00:00 2005 Addison-Wesley Professional architect documentation software-architecture software-engineering view viewpoint http://www.citeulike.org/user/germoglio/article/2853135 <i>ACM Trans. Archit. Code Optim., Vol. 5, No. 1. (May 2008), pp. 1-32.</i> Design of the Java HotSpot\texttrademark client compiler for Java 6 Thomas Kotzmann Christian Wimmer Hanspeter Mössenböck Thomas Rodriguez Kenneth Russell David Cox doi:10.1145/1369396.1370017 ACM Trans. Archit. Code Optim., Vol. 5, No. 1. (May 2008), pp. 1-32. 2008-05-31T13:09:52-00:00 2008 ACM Trans. Archit. Code Optim. 1544-3566 5 1 1 32 ACM compiler design java optimization http://www.citeulike.org/user/germoglio/article/2842519 <i>(01 March 2006)</i><br /><br />A Software Architecture Primer presents a fresh, pragmatic approach to the study of software architecture. Written by two practitioners with extensive industry and academic experience, it contains a series of chapters that introduce and develop an understanding of software architecture, by means of careful explanation and elaboration of a range of key concepts. Chapters on architectural analysis and design, on fundamental views of complex software systems, and on architectural styles and quality attributes, combine to ensure that the reader or student will master the art of "architectural thinking." This book will be of value to anyone involved in software systems analysis, design, or development. A complete set of course materials is available from the publisher's website, to support the use of this book as an undergraduate or post-graduate textbook. A Software Architecture Primer John Reekie Rohan Mcadam (01 March 2006) 2008-05-28T18:56:48-00:00 2006 Angophora Press book software-architecture software-engineering http://www.citeulike.org/user/germoglio/article/2429871 <i>Software, IEEE, Vol. 25, No. 2. (2008), pp. 92-94.</i><br /><br />Google's position as a leading Web-based applications platform and its embrace of rigorous incremental testing might be the vanguard of a new definition of what software testing encompasses. "Googling" Test Practices? Web Giant's Culture Encourages Process Improvement Greg Goth doi:10.1109/MS.2008.28 Software, IEEE, Vol. 25, No. 2. (2008), pp. 92-94. 2008-02-26T14:39:25-00:00 2008 Software, IEEE 25 2 92 94 process software-engineering testing http://www.citeulike.org/user/germoglio/article/2837450 <i>Computer, Vol. 41, No. 4. (2008), pp. 93-95.</i><br /><br />DSPLs produce software capable of adapting to changes in user needs and resource constraints. Dynamic Software Product Lines Svein Hallsteinsen Mike Hinchey Sooyong Park Klaus Schmid doi:10.1109/MC.2008.123 Computer, Vol. 41, No. 4. (2008), pp. 93-95. 2008-05-27T13:07:55-00:00 2008 Computer 41 4 93 95 product-lines software http://www.citeulike.org/user/germoglio/article/2837443 <i>Software, IEEE, Vol. 25, No. 2. (2008), pp. 96-96.</i><br /><br />English's ambiguities and variations make it difficult to support as a universal language. On the Impurity of the English Language Robert Glass doi:10.1109/MS.2008.41 Software, IEEE, Vol. 25, No. 2. (2008), pp. 96-96. 2008-05-27T13:02:22-00:00 2008 Software, IEEE 25 2 96 96 english http://www.citeulike.org/user/germoglio/article/2818061 <i>(2 March 2006)</i> On Design Grady Booch (2 March 2006) 2008-05-21T02:25:09-00:00 2006 design http://www.citeulike.org/user/germoglio/article/2732143 <i>(11 March 2008)</i><br /><br /><P>Software has become omnipresent and vital in our information-based society, so all software producers should assume responsibility for its reliability. While "reliable" originally assumed implementations that were effective and mainly error-free, additional issues like adaptability and maintainability have gained equal importance recently. For example, the 2004 ACM/IEEE Software Engineering Curriculum Guidelines list software evolution as one of ten key areas of software engineering education.</P> <P></P> <P>Mens and Demeyer, both international authorities in the field of software evolution, together with the invited contributors, focus on novel trends in software evolution research and its relations with other emerging disciplines such as model-driven software engineering, service-oriented software development, and aspect-oriented software development. They do not restrict themselves to the evolution of source code but also address the evolution of other, equally important software artifacts such as databases and database schemas, design models, software architectures, and process management. The contributing authors provide broad overviews of related work, and they also contribute to a comprehensive glossary, a list of acronyms, and a list of books, journals, websites, standards and conferences that together represent the community’s body of knowledge.</P> <P></P> <P>Combining all these features, this book is the indispensable source for researchers and professionals looking for an introduction and comprehensive overview of the state of the art. In addition, it is an ideal basis for an advanced course on software evolution.</P> Software Evolution (11 March 2008) 2008-04-29T07:07:36-00:00 2008 Springer architecture evolution software software-architecture software-evolution http://www.citeulike.org/user/germoglio/article/2717396 <i>(1977), pp. 206-214.</i> Social processes and proofs of theorems and programs Richard Demillo Richard Lipton Alan Perlis doi:10.1145/512950.512970 (1977), pp. 206-214. 2008-04-25T11:09:05-00:00 1977 206 214 ACM formal-methods proofs software http://www.citeulike.org/user/germoglio/article/2713100 <i>Software Engineering, IEEE Transactions on, Vol. SE-11, No. 11. (1985), pp. 1351-1360.</i><br /><br />A designer's expertise rests on the knowledge and skills which develop with experience in a domain. As a result, when a designer is designing an object in an unfamiliar domain he will not have the same knowledge and skills available to him as when he is designing an object in a familiar domain. In this paper we look at the software designer's underlying constellation of knowledge and skills, and at the way in which this constellation is dependent upon experience in a domain. What skills drop out, what skills, or interactions of skills come forward as experience with the domain changes? To answer the above question, we studied expert designers in experimentally created design contexts with which they were differentially familiar. In this paper we describe the knowledge and skills we found were central to each of the above contexts and discuss the functional utility of each. In addition to discussing the knowledge and skills we observed in expert designers, we will also compare novice and expert behavior. The Role of Domain Experience in Software Design B Adelson E Soloway Software Engineering, IEEE Transactions on, Vol. SE-11, No. 11. (1985), pp. 1351-1360. 2008-04-24T13:54:35-00:00 1985 Software Engineering, IEEE Transactions on SE-11 11 1351 1360 design domain-knowledge software http://www.citeulike.org/user/germoglio/article/2702739 <i>Telematica Institut Version, Vol. 1 (2002)</i> State of the Art in Architecture Frameworks and Tools F Arbab M Bonsangue JG Scholten ME Iacob H Jonkers M Lankhorst E Proper A Stam Telematica Institut Version, Vol. 1 (2002) 2008-04-22T18:55:24-00:00 2002 Telematica Institut Version 1 architecture software-architecture http://www.citeulike.org/user/germoglio/article/2702733 <i>(6 February 2004)</i> Guide to the (Evolving) Enterprise Architecture Body of Knowledge Donald Arries Fatma Dandashi Dello Paul Garvey Paula Hagan Diane Mularz Ann Reedy Beverly Woodward Charles Yokley (6 February 2004) 2008-04-22T18:50:46-00:00 2004 architecture body-of-knowledge enterprise http://www.citeulike.org/user/germoglio/article/2675982 <i>(24 August 1999)</i><br /><br />This is the braille version of the timeless reference book. According to the St. Louis Dispatch, this "excellent book, which should go off to college with every freshman, is recognized as the best book of its kind we have." It should be the ". . . daily companion of anyone who writes for a living and, for that matter, anyone who writes at all" (Greensboro Daily New). "No book in shorter space, with fewer words, will help any writer more than this persistent little volume" (The Boston Globe). Two volumes in braille. Composition teachers throughout the English-speaking world have been pushing this book on their students since it was first published in 1957. Co-author White later revised it, and it remains the most compact and lucid handbook we have for matters of basic principles of composition, grammar, word usage and misusage, and writing style. The Elements of Style William Strunk EB White Roger Angell (24 August 1999) 2008-04-16T03:33:43-00:00 1999 Allyn & Bacon book english writing http://www.citeulike.org/user/germoglio/article/2675980 <i>(28 March 2000)</i><br /><br /><div>Time magazine called Mortimer J. Adler a "philosopher for everyman." In this guide to considering the big questions, Adler addresses the topics all men and women ponder in the course of life, such as "What is love?", "How do we decide the right thing to do?", and, "What does it mean to be good?" Drawing on his extensive knowledge of Western literature, history, and philosophy, the author considers what is meant by democracy, law, emotion, language, truth, and other abstract concepts in light of more than two millennia of Western civilization and discourse. Adler's essays offer a remarkable and contemplative distillation of the Great Ideas of Western Thought.<br></div> How to Think About the Great Ideas: From the Great Books of Western Civilization Mortimer Adler (28 March 2000) 2008-04-16T03:31:52-00:00 2000 Open Court book ideas philosophy http://www.citeulike.org/user/germoglio/article/2675954 <i>(2002)</i> A Mathematician's Lament Paul Lockhart (2002) 2008-04-16T03:16:22-00:00 2002 education math http://www.citeulike.org/user/germoglio/article/2458579 <i>Queue, Vol. 3, No. 2. (March 2005), pp. 64-ff.</i> Comments are more important than code Jef Raskin doi:10.1145/1053331.1053354 Queue, Vol. 3, No. 2. (March 2005), pp. 64-ff. 2008-03-02T21:52:34-00:00 2005 Queue 1542-7730 3 2 64 ff ACM code communication documentation implementation http://www.citeulike.org/user/germoglio/article/1730948 <i>(26 October 2007)</i><br /><br /><P style="MARGIN: 0px">Great code doesn't just function: It clearly and consistently communicates your intentions, allowing other programmers to understand your code, rely on it, and modify it with confidence. But great code doesn't just happen. It is the outcome of hundreds of small but critical decisions programmers make every single day. Now, legendary software innovator Kent Beck--known worldwide for creating Extreme Programming and pioneering software patterns and test-driven development--focuses on these critical decisions, unearthing powerful “implementation patterns” for writing programs that are simpler, clearer, better organized, and more cost-effective. </P> <P style="MARGIN: 0px"> </P> <P style="MARGIN: 0px">Beck identifies 77 new patterns for handling everyday programming tasks and writing more readable code. These new patterns address many areas of development, including class, state, behavior, method, collections, frameworks, and more. You’ll find better solutions for handling everything from naming variables to checking exceptions. He uses diagrams, stories, examples, and essays to present each pattern in the most illuminating way possible. </P> <P style="MARGIN: 0px"> </P> <P style="MARGIN: 0px">The book covers</P> <UL> <LI> <DIV style="MARGIN: 0px">The value of communicating through code, and the philosophy behind patterns</DIV> <LI> <DIV style="MARGIN: 0px">How and when to create classes, and how classes encode logic</DIV> <LI> <DIV style="MARGIN: 0px">Best practices for storing and retrieving state</DIV> <LI> <DIV style="MARGIN: 0px">Behavior: Patterns for representing logic, including alternative paths</DIV> <LI> <DIV style="MARGIN: 0px">Writing, naming, and decomposing methods</DIV> <LI> <DIV style="MARGIN: 0px">Choosing and using collections</DIV> <LI> <DIV style="MARGIN: 0px">Implementation pattern variations for use in building frameworks</DIV></LI></UL> <P style="MARGIN: 0px"><B><I>Implementation Patterns</I></B> will help programmers at all experience levels, especially those who have benefited from software patterns or agile methods. It will also be an indispensable resource for development teams seeking to work together more efficiently and build more maintainable software. No other software engineering book will touch your day-to-day work more often, and no other book will prove more useful.</P> Implementation Patterns Kent Beck (26 October 2007) 2007-10-05T13:34:05-00:00 2007 Addison-Wesley Professional communication decisions design implementation patterns http://www.citeulike.org/user/germoglio/article/2458469 <i>Software, IEEE, Vol. 25, No. 2. (2008), pp. 20-21.</i><br /><br />Code clutter and unnecessary complexity can obscure design. How can designers better present their design decisions in their code? Connecting Design with Code Rebecca Wirfs-Brock doi:10.1109/MS.2008.33 Software, IEEE, Vol. 25, No. 2. (2008), pp. 20-21. 2008-03-02T21:28:57-00:00 2008 Software, IEEE 25 2 20 21 code design development documentation software-engineering traceability