7.3 KiB
| title | chunk | source | category | tags | date_saved | instance |
|---|---|---|---|---|---|---|
| Outline of software engineering | 2/3 | https://en.wikipedia.org/wiki/Outline_of_software_engineering | reference | science, encyclopedia | 2026-05-05T08:04:27.296851+00:00 | kb-cron |
=== Life cycle phases === Development life cycle phase Requirements gathering / analysis Software architecture Computer programming Testing, detects bugs Black box testing White box testing Quality assurance, ensures compliance with process. Product Life cycle phase and Project lifecycle Inception First development Major release Minor release Bug fix release Maintenance Obsolescence Release development stage, near the end of a release cycle Alpha Beta Gold master 1.0; 2.0 Software development lifecycle Waterfall model — Structured programming and Stepwise refinement SSADM Spiral model — Iterative development V-model Agile software development DSDM Chaos model — Chaos strategy
=== Deliverables === Deliverables must be developed for many SE projects. Software engineers rarely make all of these deliverables themselves. They usually cooperate with the writers, trainers, installers, marketers, technical support people, and others who make many of these deliverables.
Application software — the software Database — schemas and data. Documentation, online and/or print, FAQ, Readme, release notes, Help, for each role User Administrator Manager Buyer Administration and Maintenance policy, what should be backed-up, checked, configured, ... Installers Migration Upgrade from previous installations Upgrade from competitor's installations Training materials, for each role User Administrator Manager Buyer Support info for computer support groups. Marketing and sales materials White papers, explain the technologies used in the applications
=== Business roles === Operations Users Administrators Managers Buyers Development Analysts Programmers Testers Managers Business Consulting — customization and installation of applications Sales Marketing Legal — contracts, intellectual property rights Privacy and Privacy engineering Support — helping customers use applications Personnel — hiring and training qualified personnel Finance — funding new development Academia Educators Researchers
=== Management topics === Leadership Coaching Communication Listening Motivation Vision, SEs are good at this Example, everyone follows a good example best Human resource management Hiring, getting people into an organization Training Evaluation Project management Goal setting Customer interaction (Rethink) Estimation Risk management Change management Process management Software development processes Metrics
=== Business topics === Quality programs Malcolm Baldrige National Quality Award Six Sigma Total Quality Management (TQM)
== Software engineering profession == Software engineering demographics Software engineering economics CCSE History of software engineering Software engineering professionalism Ethics Licensing Legal Intellectual property Consumer protection
== History of software engineering == History of software engineering
=== Pioneers === Many people made important contributions to SE technologies, practices, or applications.
John Backus: Fortran, first optimizing compiler, BNF Victor Basili: Experience factory. F.L. Bauer: Stack principle, popularized the term Software Engineering Kent Beck: Refactoring, extreme programming, pair programming, test-driven development. Tim Berners-Lee: World Wide Web Barry Boehm: SE economics, COCOMO, Spiral model. Grady Booch: Object-oriented design, UML. Fred Brooks: Managed System 360 and OS 360. Wrote The Mythical Man-Month and No Silver Bullet. Larry Constantine: Structured design, coupling, cohesion Edsger Dijkstra: Wrote Notes on Structured Programming, A Discipline of Programming and Go To Statement Considered Harmful, algorithms, formal methods, pedagogy. Michael Fagan: Software inspection. Tom Gilb: Software metrics, Software inspection, Evolutionary Delivery ("Evo"). Adele Goldstine: Wrote the Operators Manual for the ENIAC, the first electronic digital computer, and trained some of the first human computers Lois Haibt: FORTRAN, wrote the first parser Margaret Hamilton: Coined the term "software engineering", developed Universal Systems Language Mary Jean Harrold: Regression testing, fault localization Grace Hopper: The first compiler (Mark 1), COBOL, Nanoseconds. Watts Humphrey: Capability Maturity Model, Personal Software Process, fellow of the Software Engineering Institute. Jean Ichbiah: Ada Michael A. Jackson: Jackson Structured Programming, Jackson System Development Bill Joy: Berkeley Unix, vi, Java. Alan Kay: Smalltalk Brian Kernighan: C and Unix. Donald Knuth: Wrote The Art of Computer Programming, TeX, algorithms, literate programming Nancy Leveson: System safety Bertrand Meyer: Design by Contract, Eiffel programming language. Peter G. Neumann: RISKS Digest, ACM Sigsoft. David Parnas: Module design, social responsibility, professionalism. Jef Raskin: Developed the original Macintosh GUI, authored The Humane Interface Dennis Ritchie: C and Unix. Winston W. Royce: Waterfall model. Mary Shaw: Software architecture. Richard Stallman: Founder of the Free Software Foundation Linus Torvalds: Linux kernel, free software / open source development. Will Tracz: Reuse, ACM Software Engineering Notes. Gerald Weinberg: Wrote The Psychology of Computer Programming. Elaine Weyuker: Software testing Jeannette Wing: Formal specifications. Ed Yourdon: Structured programming, wrote The Decline and Fall of the American Programmer. See also
List of programmers List of computer scientists
== Notable publications == About Face: The Essentials of User Interface Design by Alan Cooper, about user interface design. ISBN 0-7645-2641-3 The Capability Maturity Model by Watts Humphrey. Written for the Software Engineering Institute, emphasizing management and process. (See Managing the Software Process ISBN 0-201-18095-2) The Cathedral and the Bazaar by Eric Raymond about open source development. The Decline and Fall of the American Programmer by Ed Yourdon predicts the end of software development in the U.S. ISBN 0-13-191958-X Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides. ISBN 0-201-63361-2 Extreme Programming Explained by Kent Beck ISBN 0-321-27865-8 "Go To Statement Considered Harmful" by Edsger Dijkstra. "Internet, Innovation and Open Source:Actors in the Network" — First Monday article by Ilkka Tuomi (2000) source Archived 2013-04-10 at the Wayback Machine The Mythical Man-Month by Fred Brooks, about project management. ISBN 0-201-83595-9 Object-oriented Analysis and Design by Grady Booch. ISBN 0-8053-5340-2 Peopleware by Tom DeMarco and Tim Lister. ISBN 0-932633-43-9 The pragmatic engineer versus the scientific designer by E. W. Dijkstra [1] Principles of Software Engineering Management by Tom Gilb about evolutionary processes. ISBN 0-201-19246-2 The Psychology of Computer Programming by Gerald Weinberg. Written as an independent consultant, partly about his years at IBM. ISBN 0-932633-42-0 Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts. ISBN 0-201-48567-2 The Pragmatic Programmer: from journeyman to master by Andrew Hunt, and David Thomas. ISBN 0-201-61622-X Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR 19759