Outline of software engineering explained
The following outline is provided as an overview of and topical guide to software engineering:
Software engineering - application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; that is the application of engineering to software.[1]
The ACM Computing Classification system is a poly-hierarchical ontology that organizes the topics of the field and can be used in semantic web applications and as a de facto standard classification system for the field. The major section "Software and its Engineering" provides an outline and ontology for software engineering.
Software applications
Software engineers build software (applications, operating systems, system software) that people use.
Applications influence software engineering by pressuring developers to solve problems in new ways. For example, consumer software emphasizes low cost, medical software emphasizes high quality, and Internet commerce software emphasizes rapid development.
- Business software
- Analytics
- Airline reservations
- Banking
- Commerce
- Compilers
- Communication
- Computer graphics
- Cryptography
- Databases, support almost every field
- Embedded systems Both software engineers and traditional engineers write software control systems for embedded products.
- Engineering All traditional engineering branches use software extensively. Engineers use spreadsheets, more than they ever used calculators. Engineers use custom software tools to design, analyze, and simulate their own projects, like bridges and power lines. These projects resemble software in many respects, because the work exists as electronic documents and goes through analysis, design, implementation, and testing phases. Software tools for engineers use the tenets of computer science; as well as the tenets of calculus, physics, and chemistry.
- File
- Finance
- Games
- Information systems, support almost every field
- LIS Management of laboratory data
- MIS Management of financial and personnel data
- Logistics
- Manufacturing
- Music
- Network Management
- Networks and Internet
- Office suites
- Operating systems
- Robotics
- Signal processing, encoding and interpreting signals
- Simulation, supports almost every field.
- Sciences
- Traffic Control
- Training
- Visualization, supports almost every field
- Voting
- World Wide Web
Software engineering topics
Programming paradigm, based on a programming language technology
Databases
Graphical user interfaces
Programming tools
Libraries
Design languages
Patterns, document many common programming and project management techniques
Processes and methodologies
- Agile
- Heavyweight
- Process Models
- Metamodels
Platforms
A platform combines computer hardware and an operating system. As platforms grow more powerful and less costly, applications and tools grow more widely available.
Other Practices
Other tools
Computer science topics
Skilled software engineers know a lot of computer science including what is possible and impossible, and what is easy and hard for software.
Mathematics topics
Discrete mathematics is a key foundation of software engineering.
Other
Life cycle phases
- 2.0
- Software development lifecycle
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
- 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
- Support info for computer support groups.
- Marketing and sales materials
- White papers, explain the technologies used in the applications
Business roles
Management topics
Business topics
Software engineering profession
History of software engineering
History of software engineering
Pioneers
Many people made important contributions to SE technologies, practices, or applications.
Fortran, first optimizing compiler, BNF
Experience factory.
Stack principle, popularized the term Software Engineering
Refactoring, extreme programming, pair programming, test-driven development.
World Wide Web
SE economics, COCOMO, Spiral model.
Object-oriented design, UML.
Managed System 360 and OS 360. Wrote The Mythical Man-Month and No Silver Bullet.
Structured design, coupling, cohesion
Wrote Notes on Structured Programming, A Discipline of Programming and Go To Statement Considered Harmful, algorithms, formal methods, pedagogy.
Software inspection.
Software metrics, Software inspection, Evolutionary Delivery ("Evo").
Wrote the Operators Manual for the ENIAC, the first electronic digital computer, and trained some of the first human computers
FORTRAN, wrote the first parser
Coined the term "software engineering", developed Universal Systems Language
Regression testing, fault localization
The first compiler (Mark 1), COBOL, Nanoseconds.
Capability Maturity Model, Personal Software Process, fellow of the Software Engineering Institute.
Ada
Jackson Structured Programming, Jackson System Development
Berkeley Unix, vi, Java.
Smalltalk
C and Unix.
Wrote The Art of Computer Programming, TeX, algorithms, literate programming
System safety
Design by Contract, Eiffel programming language.
RISKS Digest, ACM Sigsoft.
Module design, social responsibility, professionalism.
Developed the original Macintosh GUI, authored The Humane Interface
C and Unix.
Waterfall model.
Software architecture.
Founder of the Free Software Foundation
Linux kernel, free software / open source development.
Reuse, ACM Software Engineering Notes.
Wrote The Psychology of Computer Programming.
Software testing
Formal specifications.
Structured programming, wrote The Decline and Fall of the American Programmer.
See also
Notable publications
- About Face: The Essentials of User Interface Design by Alan Cooper, about user interface design.
- The Capability Maturity Model by Watts Humphrey. Written for the Software Engineering Institute, emphasizing management and process. (See Managing the Software Process)
- 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.
- Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides.
- "Internet, Innovation and Open Source:Actors in the Network" — First Monday article by Ilkka Tuomi (2000) source
- The Mythical Man-Month by Fred Brooks, about project management.
- Object-oriented Analysis and Design by Grady Booch.
- Peopleware by Tom DeMarco and Tim Lister.
- The pragmatic engineer versus the scientific designer by E. W. Dijkstra https://www.cs.utexas.edu/users/EWD/transcriptions/EWD06xx/EWD690.html
- Principles of Software Engineering Management by Tom Gilb about evolutionary processes.
- The Psychology of Computer Programming by Gerald Weinberg. Written as an independent consultant, partly about his years at IBM.
- Refactoring: Improving the Design of Existing Code by Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts.
- The Pragmatic Programmer: from journeyman to master by Andrew Hunt, and David Thomas.
- Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR 19759
Related fields
See also
External links
- Professional organizations
- Professionalism
- Education
- Standards:
- Government organizations:
- Agile:
- Other organizations:
- Demographics
- Surveys:
- Other:
Notes and References
- Book: Pierre . Bourque . Robert . Dupuis . Guide to the Software Engineering Body of Knowledge - 2004 Version . . 2004 . 1 . 0-7695-2330-7 .
