No Silver Bullet – Essence and Accident in Software EngineeringNo Silver Bullet – Essence and Accident in Software Engineering Mike Ballou“There is no single development, in either technology or management technique, which by itself promises even one order-of- in simplicity.”Abstract “All software construction involves essential tasks, the fashioning of the complex conceptual structures that compose the abstract software entity, and accidental tasks, the onto machine languages within space and speed constraints.”Abstract “Most of the big gains in software productivity have come from removing artificial barriers that have made the accidental tasks inordinately0 码力 | 35 页 | 1.43 MB | 5 月前3
MITRE Defense Agile Acquisition Guide - Mar 2014technologies and operations, including the challenges associated with information assurance. Agile development practices can help the DoD to transform IT acquisition by delivering capabilities faster and responding succeed in an increasingly complex environment. Agile has emerged as the leading industry software development methodology, and has seen growing adoption across the DoD and other federal agencies. Agile the program characteristics. Agile development can achieve these objectives through: Focusing on small, frequent capability releases Valuing working software over comprehensive documentation0 码力 | 74 页 | 3.57 MB | 5 月前3
Trends Artificial Intelligence
AI Will Likely Do in Ten Years, per ChatGPT Source: ChatGPT (5/15/25) AI = Circa 2035?36 AI Development Trending = Unprecedented37 Machine-Learning Model* Trending = In 2015... Industry Surpassed Academia Models by Sector – 2003-2024, per Stanford HAI Annual New Notable Machine-Learning Models AI Development Trending = Unprecedented38 AI Developer Growth (NVIDIA Ecosystem as Proxy) = +6x to 6MM Developers to reach 2 million.’ Source: NVIDIA blog posts, press releases, & company overviews +6x AI Development Trending = Unprecedented Global Developers in NVIDIA Ecosystem (MM) – 2005-2025, Per NVIDIA390 码力 | 340 页 | 12.14 MB | 4 月前3
The DevOps HandbookMyth—DevOps is Just “Infrastructure as Code” or Automation: g. Myth—DevOps is Only for Open Source Software: 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: a. THE CORE, CHRONIC CONFLICT and poor quality 3. Consider when we have an annual schedule for software releases, where an entire year’s worth of code that Development has worked on is released to production deployment. Like in manufacturing STREAM 1. In the book Implementing Lean Software Development: From Concept to Cash, Mary and Tom Poppendieck describe waste and hardship in the software development stream as anything that causes delay0 码力 | 8 页 | 22.57 KB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilityand when we realize that the costs and risks of custom development have been radically reduced, the economics often now favor custom development. Governance and Oversight: Governance has traditionally uncertainty by planning and analysis. Agile teams tend to drive out uncertainty by developing working software in small increments and then adjusting. Waterfall plans are made at the moment of greatest uncertainty—the Cross-functional and team-based: It used to be natural for ops specialists to do ops, developers to do development, and testers to do testing. Now, crossover skills are increasingly important. On a delivery team0 码力 | 7 页 | 387.48 KB | 5 月前3
DoD CIO Enterprise DevSecOps Reference Design - SummaryDevSecOps – Defined by DoD CIO DevSecOps is an organizational software engineering culture and practice that aims at unifying software development (Dev), security (Sec) and operations (Ops). The main characteristic characteristic of DevSecOps is to automate, monitor, and apply security at all phases of the software lifecycle: plan, develop, build, test, release, deliver, deploy, operate, and monitor. In DevSecOps, built simultaneously. Key Measures Mean-time to production: the average time it takes from when new software features are required until they are running in production. Average lead-time: how long it takes0 码力 | 8 页 | 3.38 MB | 5 月前3
A Seat at the Table - IT Leadership in the Age of AgilityBrining Lean Principles to Software Development: Kanban is David Anderson’s approach to bringing Lean principles into software development while driving fear out of the transformation with desired outcomes as requirements is Gojko Adzic’s Impact Mapping: Making a Big Impact with Software Products and Projects. The age of IT organizations hiding behind requirements—“just tell me what lies, I believe, in our distinction between the development of a system and its operation and maintenance. Dividing our IT spending into development and maintenance buckets leads to some ineffective 0 码力 | 4 页 | 379.23 KB | 5 月前3
OpenAI - AI in the Enterpriseresponsive customer experiences. 3 AI in the EnterpriseBut leveraging AI isn’t the same as building software or deploying cloud apps. The most successful companies are often those who treat it as a new paradigm value faster and with greater buy-in from users and stakeholders. Our approach: iterative development OpenAI is organized around three teams. Our Research Team advances the foundations of AI, developing process are best-placed to improve it with AI. 06 Unblock your developers Automating the software development lifecycle can multiply AI dividends. 07 Set bold automation goals Most processes involve0 码力 | 25 页 | 9.48 MB | 5 月前3
The DevOps Handbookcritical areas. ii. Michael Nygard, author of Release It! Design and Deploy Production-Ready Software, “If you do not design your failure modes, then you will get whatever unpredictable—and usually ii. Public knowledge versus private knowledge from emails b. AUTOMATE STANDARDIZED PROCESSES IN SOFTWARE FOR RE-USE i. Don’t store standards and processes in Word or non-actionable documents; leads to NFRs. Codify these into the tests and pipeline f. BUILD REUSABLE OPERATIONS USER STORIES INTO DEVELOPMENT i. Goal – make recurring work as repeatable and deterministic as possible; standardize and automate0 码力 | 9 页 | 25.13 KB | 5 月前3
The DevOps Handbookproduction instances v. Keep developers’ environments most current e. MODIFY OUR DEFINITION OF DEVELOPMENT “DONE” TO INCLUDE RUNNNING IN PRODUCTION-LIKE ENVIRONMENTS i. In general, the longer the interval consistent and repeatable wayiii. Building a deployment pipeline 1. Commit stage – build & package software, runs automated unit tests, and code quality (static analysis, coverage, style, etc.) 2. Package frequently as possible i. WRITE OUR AUTOMATED TESTS BEFORE WE WRITE THE CODE (“TEST DRIVEN DEVELOPMENT”) i. TDD – Kent Beck as part of Extreme Programming 1. Ensure the tests fail – “Write a test0 码力 | 8 页 | 23.08 KB | 5 月前3
共 44 条
- 1
- 2
- 3
- 4
- 5













