Software Engineering Principles and Practices
Reference documents in Software Engineering Principles and Practices.
Documents in Software Engineering Principles and Practices
Page 1 of 3-
The scope of reliability engineering is extremely wide, encompassing many areas of engineering technology. Reliability engineering helps ensure the success of space missions, maintain the national security, deliver a steady supply of electric power, provide reliable transportation, and so on.
-
Performance Testing Guidance for Web Applications provides an end-to-end approach for implementing performance testing. Whether you are new to performance testing or looking for ways to improve your current performance-testing approach, you will gain insights that you can tailor to your specific scenarios.
-
This book reviews important technologies for software development with a particular focus on Web applications. In reviewing these technologies the author puts emphasis on underlying principles and basic concepts, rather than meticulousness and completeness.
-
This volume provides an overview of the acceptance process and how acceptance testing and other key practices fit into the process. It is subdivided into three main parts:
-
The Definitive Guide to Building Code Quality presents a comprehensive review of modern techniques used to transform raw source code into finished product. In addition to exploring current tools and methods, the guide reviews common techniques and best practices for debugging, testing, and preparing code for commercial release. Throughout, the emphasis is on completeness of coverage in test cases, complete exercise and optimization of code, and use of appropriate procedures and workflows to ensure that changes to code bases are properly recognized, tested, and integrated.
-
This book is about how individuals can take the lead in realigning our development efforts to that promise. In doing so, we shall in turn take our lead from the practice of Architecture, when Architects formed themselves into organisations determined to combat the problem of buildings falling on people's heads.
-
This book provides valuable insights for the core business on how software development impacts profitability. It helps the core business understand how to communicate with software developers and reward the right behaviors.
-
In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra - offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as:
-
This book is a collection of those 68 additional essays from 97 Things Every Programmer Should Know site.
-
This book is a collection of articles written by developers and researches from all around the globe. Mostly they present methodologies for separate Systems Engineering processes; others consider issues of adjacent knowledge areas and sub-areas that significantly contribute to systems development, operation, and maintenance.
-
Unit testing can be a valuable part of any development cycle, but it can easily cause more problems than it prevents if used incorrectly. With Unit Testing Succinctly by Marc Clifton, you'll learn what you need to know to leverage unit testing and minimize the number of bugs introduced in development. The book clearly defines what does and does not constitute units and tests, different approaches to implementing unit tests, and even the far-reaching effects that unit testing can have on the architecture of your application.
-
Software architecture is the discipline concerned with model-based description and analysis of software systems with a view to satisfying the (often contradictory) concerns of stakeholders. The software architecture of a system is a high-level description of its components and their interactions.
-
The Software Product Line (SPL) is an emerging methodology for developing software products. Currently, there are two hot issues in the SPL: modelling and the analysis of the SPL. Variability modelling techniques have been developed to assist engineers in dealing with the complications of variability management. The principal goal of modelling variability techniques is to configure a successful software product by managing variability in domain-engineering. In other words, a good method for modelling variability is a prerequisite for a successful SPL. On the other hand, analysis of the SPL aids the extraction of useful information from the SPL and provides a control and planning strategy mechanism for engineers or experts. In addition, the analysis of the SPL provides a clear view for users. Moreover, it ensures the accuracy of the SPL. This book presents new techniques for modelling and new methods for SPL analysis.
-
This free book is about strategies for automating your build and deployment processes, implementing a continuous integration system, and how to continuously test your mobile applications.
-
An illustrated collection of (sometimes violent) fables concerning the Art and Philosophy of software development, written in the spirit of Zen koans. (For three days and nights the Java master did not emerge from his cubicle. On the fourth day the monks of the temple sent a novice to inquire after him.)