Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Energy conservation --- Green technology --- Software engineering --- Environmental aspects

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

The GREENS workshop provides a forum for practitioners and academics to share knowledge, ideas, practices, and current results related to green and sustainable software engineering. The goal of green software engineering is to apply green principles to the design and operation of softwareintensive systems. Green and self-greening software systems have tremendous potential to decrease energy consumption. Moreover, enterprise software can and should be re-thought to address sustainability issues using innovative business models, processes, and incentives. Monitoring and measuring the greenness of software is critical towards the notion of sustainable and green software. Demonstrating improvement is paramount for users to achieve and affect change. Thus, the theme of GREENS 2015 is Towards a Green Software Body of Knowledge. GREENS 2015 is interested in contributions from industry, government, and academia on all topics related to greener software engineering. Topics range from bringing sustainability and energy efficiency into all software lifecycle stages, to green measures and estimations, practices, notations, and tools to both greening the software engineering process, and greening the resulting ICT systems. To ensure high quality papers and presentations, all submissions were reviewed by at least three program committee members whose identity was not revealed to any of the authors. The reviewers did not review papers for which they had a conflict of interest. The organizers were excluded by the reviewer selection process when in direct or indirect conflict of interest.

Green technology

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

A software architecture manifests the major early design decisions, which determine the system’s development, deployment and evolution. Thus, making better architectural decisions is one of the large challenges in software engineering. Software architecture knowledge management is about capturing practical experience and translating it into generalized architectural knowledge, and using this knowledge in the communication with stakeholders during all phases of the software lifecycle. This book presents a concise description of knowledge management in the software architecture discipline. It explains the importance of sound knowledge management practices for improving software architecture processes and products, and makes clear the role of knowledge management in software architecture and software development processes. It presents many approaches that are in use in software companies today, approaches that have been used in other domains, and approaches under development in academia. After an initial introduction by the editors, the contributions are grouped in three parts on "Architecture Knowledge Management", "Strategies and Approaches for Managing Architectural Knowledge", and "Tools and Techniques for Managing Architectural Knowledge". The presentation aims at information technology and software engineering professionals, in particular software architects and software architecture researchers. For the industrial audience, the book gives a broad and concise understanding of the importance of knowledge management for improving software architecture process and building capabilities in designing and evaluating better architectures for their mission- and business-critical systems. For researchers, the book will help to understand the applications of various knowledge management approaches in an industrial setting and to identify research challenges and opportunities.

Computer architecture. --- Computer software -- Development. --- Electronic books. -- local. --- Knowledge management -- Data processing. --- Software engineering. --- Software architecture --- Knowledge management --- Application software --- Computer Science --- Engineering & Applied Sciences --- Development --- Information Technology --- Software Engineering --- Computer software --- Development. --- Data processing. --- Management of knowledge assets --- Architecture, Computer --- Development of computer software --- Software development --- Computer software engineering --- Computer science. --- Management information systems. --- Computer Science. --- Software Engineering/Programming and Operating Systems. --- Software Engineering. --- Management of Computing and Information Systems. --- Engineering --- Management --- Information technology --- Intellectual capital --- Organizational learning --- Information Systems. --- Informatics --- Science --- Computer-based information systems --- EIS (Information systems) --- Executive information systems --- MIS (Information systems) --- Sociotechnical systems --- Information resources management --- Communication systems

Choose an application

• Reference Manager
• EndNote
• RefWorks (Direct export to RefWorks)

Why have a book about the relation between requirements and software architecture? Understanding the relation between requirements and architecture is important because the requirements, be they explicit or implicit, represent the function, whereas the architecture determines the form. While changes to a set of requirements may impact on the realization of the architecture, choices made for an architectural solution may impact on requirements, e.g., in terms of revising functional or non-functional requirements that cannot actually be met. Although research in both requirements engineering and software architecture is quite active, it is in their combination that understanding is most needed and actively sought. Presenting the current state of the art is the purpose of this book. The editors have divided the contributions into four parts: Part 1 Theoretical Underpinnings and Reviews  addresses the issue of requirements change management in architectural design through traceability and reasoning. Part 2 Tools and Techniques  presents approaches, tools, and techniques for bridging the gap between software requirements and architecture. Part 3 Experiences from Industrial Projects  then reports on case studies from industry, while part 4 on Emerging Issues  details advanced topics such as synthesizing architecture from requirements or the role of middleware in architecting for non-functional requirements. The final chapter is a conclusions chapter identifying key contributions and outstanding areas for future research and improvement of practice. The book is targeted at academic and industrial researchers in requirements engineering or software architecture. Graduate students specializing in these areas as well as advanced professionals in software development will also benefit from the results and experiences presented in this volume.

Computer. Automation --- software engineering --- informatica management