Building Superior Embedded Systems
Continuous delivery (CD), sometimes called continuous deployment, is a software development practice where changes to a code base are automatically built, tested, and deployed for release.
In software development, a Change Control Board (CCB) or Software Change Control Board (SCCB) is a committee that consists of Subject Matter Experts (SME) and Technical Chiefs, who will make decisions regarding whether or not proposed changes to a software project should be implemented.
“Extreme programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements.”
A software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases, then the software is improved so that the tests pass.
Refers to a common time-wasting phenomenon for embedded developers, where software development is gated on hardware, long build times, or a long flashing cycle.
“Software Process Improvement (SPI) methodology is defined as a sequence of tasks, tools, and techniques to plan and implement improvement activities to achieve specific goals such as increasing development speed, achieving higher product quality or reducing costs.”
A development model originally designed to objectively assess the ability of a government contractors’s process for implementing a software project.
“A software development process characterized by a systematic effort to control changes made to a code base. The primary goal is to ensure that no unnecessary changes are made.”
A method for improving software design reviews proposed by D.L. Parnas.
A methodology to create software architectures that takes into account the quality attributes of the software.