|
DevOps
DevOps is a set of practices that combines software development (''Dev'') and IT operations (''Ops''). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary to agile software development; several DevOps aspects came from the ''agile'' way of working. Definition Other than it being a cross-functional combination (and a portmanteau) of the terms and concepts for "development" and "operations", academics and practitioners have not developed a universal definition for the term "DevOps". Most often, DevOps is characterized by key principles: shared ownership, workflow automation, and rapid feedback. From an academic perspective, Len Bass, Ingo Weber, and Liming Zhu—three computer science researchers from the CSIRO and the Software Engineering Institute—suggested defining DevOps as "a set of practices intended to reduce the time between committing a change to a system and the change being placed i ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Continuous Delivery
Continuous delivery (CD) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, following a pipeline through a "production-like environment", without doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery. Continuous delivery contrasts with continuous deployment Continuous deployment (CD) is a software engineering approach in which software functionalities are delivered frequently and through automated deployments. Continuous deployment contrasts with continuous delivery (also abbreviated CD), a similar ... (also abbreviated CD), a similar approach in which software is also produced in short cycles bu ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Nicole Forsgren
Nicole Forsgren Velasquez is an American technology executive, entrepreneur, and author. In 2020 she was named vice-president of Research & Strategy at Microsoft's GitHub and more recently Partner at Microsoft Research. She is coauthor of '' Accelerate: The Science of Lean Software and DevOps'' which won the Shingo Research and Professional Publication Award in 2019. Life and career Forsgren was CEO and co-founder of DevOps Research and Assessment LLC (DORA) with Jez Humble and Gene Kim. DORA is known for the annual ''State of DevOps'' report, and their ''DevOps Scorecard''. In 2018 DORA was purchased by Google Google LLC () is an American multinational technology company focusing on search engine technology, online advertising, cloud computing, computer software, quantum computing, e-commerce, artificial intelligence, and consumer electronics. .... References External links * 1978 births Living people American bloggers GitHub people 21st-century Ame ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Len Bass
Leonard Joel (Len) Bass (born c.1943) is an American software engineer, Emeritus professor and former researcher at the Software Engineering Institute (SEI), particularly known for his contributions on software architecture in practice. Biography Bass received his Ph.D. degree in Computer Science from Purdue University in 1970 under the supervision of Paul Ruel Young with the thesis, entitled "Hierarchies based on computational complexity and irregularities of class determining measured sets." Bass was appointed Professor of Computer Science at the University of Rhode Island in 1970. In 1986, he moved to the Software Engineering Institute at Carnegie Mellon University, where he started as head of the user-interface software group, and later focused on the analysis of software architectures. Since 2011, he has been Senior Principal Researcher at NICTA (National ICT Australia). Len Bass was awarded the ''Software Development Magazines Jolt Productivity Award twice in 1999 and 20 ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Quality
In the context of software engineering, software quality refers to two related but distinct notions: * Software functional quality reflects how well it complies with or conforms to a given design, based on functional requirements or specifications. That attribute can also be described as the fitness for purpose of a piece of software or how it compares to competitors in the marketplace as a worthwhile product. It is the degree to which the correct software was produced. * Software structural quality refers to how it meets non-functional requirements that support the delivery of the functional requirements, such as robustness or maintainability. It has a lot more to do with the degree to which the software works as needed. Many aspects of structural quality can be evaluated only statically through the analysis of the software inner structure, its source code (see Software metrics), at the unit level, system level (sometimes referred to as end-to-end testing), which is in effect ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Engineering Institute
The Software Engineering Institute (SEI) is an American research and development center headquartered in Pittsburgh, Pennsylvania. Its activities cover cybersecurity, software assurance, software engineering and acquisition, and component capabilities critical to the United States Department of Defense. Authority The Carnegie Mellon Software Engineering Institute is a federally funded research and development center headquartered on the campus of Carnegie Mellon University in Pittsburgh, Pennsylvania, United States. The SEI also has offices in Washington, DC; Arlington County, Virginia; and Los Angeles, California. The SEI operates with major funding from the U.S. Department of Defense. The SEI also works with industry and academia through research collaborations. On November 14, 1984, the U.S. Department of Defense elected Carnegie Mellon University as the host site of the Software Engineering Institute. The institute was founded with an initial allocation of $6 million, with ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
ITIL
The Information Technology Infrastructure Library (ITIL) is a set of detailed practices for IT activities such as IT service management (ITSM) and IT asset management (ITAM) that focus on aligning IT services with the needs of business. ITIL describes processes, procedures, tasks, and checklists which are neither organization-specific nor technology-specific, but can be applied by an organization toward strategy, delivering value, and maintaining a minimum level of competency. It allows the organization to establish a baseline from which it can plan, implement, and measure. It is used to demonstrate compliance and to measure improvement. There is no formal independent third party compliance assessment available for ITIL compliance in an organization. Certification in ITIL is only available to individuals. Since 2013, ITIL has been owned by AXELOS, a joint venture between Capita and the UK Cabinet Office. History Responding to growing dependence on IT, the UK Government's Ce ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Software Development
Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other software components. Software development involves writing and maintaining the source code, but in a broader sense, it includes all processes from the conception of the desired software through to the final manifestation of the software, typically in a planned and structured process. Software development also includes research, new development, prototyping, modification, reuse, re-engineering, maintenance, or any other activities that result in software products. Methodologies One system development methodology is not necessarily suitable for use by all projects. Each of the available methodologies are best suited to specific kinds of projects, based on various technical, organizational, project, and team considerations. Software development activities Identification of need The sou ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
PDCA
PDCA (plan–do–check–act or plan–do–check–adjust) is an iterative design and management method used in business for the control and continual improvement of processes and products. It is also known as the Shewhart cycle, or the control circle/cycle. Another version of this PDCA cycle is OPDCA. The added "O" stands for ''observation'' or as some versions say: "Observe the current condition." This emphasis on observation and current condition has currency with the literature on lean manufacturing and the Toyota Production System. The PDCA cycle, with Ishikawa's changes, can be traced back to S. Mizuno of the Tokyo Institute of Technology in 1959. PDCA is often confused with PDSA (Plan-Do-Study-Act). Dr. W. Edwards Deming emphasized the PDSA Cycle, not the PDCA Cycle, with a third step emphasis on Study (S), not Check (C). Dr. Deming found that the focus on Check is more about the implementation of a change, with success or failure. His focus was on predicting the results ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
The Toyota Way
The Toyota Way is a set of principles defining the organizational culture of Toyota Motor Corporation. The company formalized the Toyota Way in 2001, after decades of academic research into the Toyota Production System and its implications for lean manufacturing as a methodology that could be adopted by other organizations. The two pillars of the Toyota Way are respect for people and continuous improvement. The philosophy was popularized by Jeffrey K. Liker in his 2004 book, ''The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer.'' Subsequent research has explored the extent to which the Toyota Way can be applied in other contexts. Background The principles were first collated into a single document in the company's pamphlet "The Toyota Way 2001", to help codify the company's organizational culture. The philosophy was subsequently analyzed in the 2004 book ''The Toyota Way'' by industrial engineering researcher Jeffrey Liker, and has received attention ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Agile Software Development
In software development, agile (sometimes written Agile) practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/ end user(s), adaptive planning, evolutionary development, early delivery, continual improvement, and flexible responses to changes in requirements, capacity, and understanding of the problems to be solved. Popularized in the 2001 ''Manifesto for Agile Software Development'', these values and principles were derived from and underpin a broad range of software development frameworks, including Scrum and Kanban. While there is much anecdotal evidence that adopting agile practices and values improves the effectiveness of software professionals, teams and organizations, the empirical evidence is mixed and hard to find. History Iterative and incremental software development methods can be traced back as early as 1957, Gerald M. Weinberg, as quoted in " ... [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
Extreme Programming
Extreme programming (XP) is a software development methodology intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,"Human Centred Technology Workshop 2006 ", 2006, PDFHuman Centred Technology Workshop 2006 /ref> it advocates frequent Software release life cycle, releases in short development cycles, intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. Other elements of extreme programming include: programming Pair programming, in pairs or doing extensive code review, unit testing of all code, You aren't gonna need it, not programming features until they are actually needed, a flat management structure, code simplicity and clarity, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers. [...More Info...] [...Related Items...] OR: [Wikipedia] [Google] [Baidu] |
