Page 1
Page 1
Transactions on Aspect-Oriented Software Development IV : Focus : Early Aspects and Aspects of Software Evolution
This volume, the fourth in the Transactions on Aspect-Oriented Software Development series, presents 5 revised papers together with 2 guest editors' introductions. The papers, which focus on mapping of early aspects across the software lifecycle, and aspects and software evolution, have passed through a careful peer reviewing process, carried out by the journal's Editorial Board and expert referees.
Software Quality — ECSQ 2002 ; Quality Connection - 7th European Conference on Software Quality, Helsinki, Finland, June 9-13, 2002. Proceedings
We have selected two themes for this conference . Our ?rst theme, “production of attractive and reliable software at Internet speed” sums up the dilemma many software organisations face. In order to be competitive, software should contain advanced features and run reliably – yet it should be developed quickly and cost e?ectively for the right market window. Finding the right balance between these objectives is a critical question that will determine business success in the years to come. Our second theme, “production of software with a dynamic partnership n- work” highlights the current trend of using partnerships and subcontractors as integral players in the software development process. Partnerships sometimes need to be created quickly to respond to a market opportunity, yet the costs and speed of cooperation must be competitive.
Software Process and Product Measurement ; International Conferences IWSM 2008, Metrikon 2008, and Mensura 2008 Munich, Germany, November 18-19, 2008. Proceedings
Includes : estimation models, measurement methodology, effort estimation, measurement programs, new approaches, prozessbewertung, size measurement, education, measurement in software lifecycle, and product measurement.
Rationale-Based Software Engineering
Many decisions are required throughout the software development process. These decisions, and to some extent the decision-making process itself, can best be documented as the rationale for the system, which will reveal not only what was done during development but the reasons behind the choices made and alternatives considered and rejected. This information becomes increasingly critical as software development becomes more distributed and encompasses the corporate knowledge both used and refined during the development process. The capture of rationale helps to ensure that decisions are well thought out and justified and the use of rationale can help avoid the mistakes of the past during both the development of the current system and when software products (architecture and design, as well as code) are reused in future systems.
Product-Focused Software Process Improvement ; 7th International Conference, PROFES 2006, Amsterdam, The Netherlands, June 12-14, 2006, Proceedings
Brought together researchers and industrial practitioners for reporting new research results and exchanging experiences and findings in the area of process and product improvement. The focus of the conference was on understanding, evaluating, controlling, and improving the relationship between process improvement activities (such as the deployment of innovative defect detection processes) and their effects on products (such as improved product reliability and safety). Consequently, major topics of the conference included the evaluation of existing software process improvement (SPI) approaches in different contexts, the presentation of new or modified SPI approaches, and the relation between SPI and new development techniques or emerging application domains. The need for SPI is being widely recognized.
Product Focused Software Process Improvement ; 6th International Conference, PROFES 2005, Oulu, Finland, June 13-18, 2005, Proceedings
Addresses both the solutions found in practice and the relevant research results from academia. This is reflected in the 42 full papers, which are – as in the years before – a well-balanced mix of academic papers as well as industrial experience reports. The business of developing new applications like mobile and Internet services or enhancing the functionality of a variety of products using embedded software is rapidly growing, maturing and meeting the harsh business realities.The accepted papers focusing on wireless and the Internet are grouped into a special “mobile and wireless” session. We wish to thank VTT Electronics, the University of Oulu including Infotech, and Fraunhofer IESE for supporting the conference. We are also grateful to the authors for high-quality papers, the Program Committee for their hard work in reviewing the papers, the Organizing Committee for making the event possible, and all the numerous supporters who helped in organizing this conference.
Early Aspects: Current Challenges and Future Directions ; 10th International Workshop, Vancouver, Canada, March 13, 2007, Revised Selected Papers
Traditionally, aspect-oriented software development (AOSD) has focused on the implementation phase of the software lifecycle: aspects are identified and captured mainly in code. Therefore, most current AOSD approaches place the burden for aspect identification and management on the programmer working at low levels of abstraction. However, aspects are often present well before the implementation phase, such as in domain models, requirements and software architecture. Identification and capture of these early aspects ensure that aspects related to the problem domain (as opposed to merely the implementation) will be appropriately captured, reasoned about and available. This offers improved opportunities for early recognition and negotiation of trade-offs and allows forward and backward aspect traceability. This makes requirements, architecture, and implementation more seamless, and allows a more systematic application of aspects.
DevOps Tools for Java Developers : Best Practices from Source Code to Production Containers
Explore software lifecycle best practices Use DevSecOps methodologies to facilitate software development and delivery Understand the business value of DevSecOps best practices Manage and secure software dependencies Develop and deploy applications using containers and cloud native technologies Manage and administrate source control repositories and development processes Use automation to set up and administer build pipelines Identify common deployment patterns and antipatterns Maintain and monitor software after deployment
DevOps for Digital Leaders : Reignite Business with a Modern DevOps-Enabled Software Factory
In DevOps for Digital Leaders, deep collective experience on both sides of the dev–ops divide informs the global thought leadership and penetrating insights of the authors, all three of whom are cross-portfolio DevOps leaders at CA Technologies. Aruna Ravichandran, Kieran Taylor, and Peter Waterhouse analyze the organizational benefits, costs, freedoms, and constraints of DevOps. They chart the coordinated strategy of organizational change, metrics, lean thinking, and investment that an enterprise must undertake to realize the full potential of DevOps and reach the sweet spot where accelerating code deployments drive increasing customer satisfaction, revenue, and profitability.
