The followingoutlineis 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 ofsoftware;that is the application ofengineeringtosoftware.[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
editSoftwareengineers buildsoftware(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
- Data miningclosely related todatabase
- Decision support systems
- Airlinereservations
- Banking
- Automated teller machines
- Chequeprocessing
- Credit cards
- Commerce
- Trade
- Auctions(e.g. eBay)
- Reverse auctions(procurement)
- Bar code scanners
- Compilers
- Communication
- Instant messengers
- VOIP
- Calendars— scheduling and coordinating
- Contact managers
- Computer graphics
- Animation
- Special effectsfor video and film
- Editing
- Post-processing
- Cryptography
- Databases,support almost every field
- Embedded systemsBoth software engineers and traditional engineers write software control systems for embedded products.
- Automotive software
- Avionics software
- Heating ventilating and air conditioning (HVAC) software
- Medical device software
- Telephony
- Telemetry
- EngineeringAll traditional engineering branches use software extensively. Engineers use spreadsheets, more than they ever used calculators. Engineers use custom softwaretoolsto design, analyze, and simulate their own projects, like bridges and power lines. These projects resemble software in many respects, because the work exists aselectronic documentsand 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
- Logistics
- Manufacturing
- Music
- Network Management
- NetworksandInternet
- Office suites
- Operating systems
- Robotics
- Signal processing,encoding and interpreting signals
- Image processing,encoding and interpreting visual information
- Speech processing
- Text recognition
- Handwriting recognition
- Simulation,supports almost every field.
- Engineering,A softwaresimulationcan be cheaper to build and more flexible to change than a physicalengineering model.
- Sciences
- Sciences
- Traffic Control
- Training
- Drill
- Simulation
- Testing
- Visualization,supports almost every field
- Voting
- World Wide Web
Software engineering topics
editProgramming paradigm, based on a programming language technology
edit- Object-oriented programming
- Aspect-oriented programming
- Functional decomposition
- Structured programming
- Rule-based programming
Databases
editGraphical user interfaces
edit- GTK+GIMP Toolkit
- wxWidgets
- Ultimate++
- Qt toolkit
- FLTK
Programming tools
edit- Configuration managementand source code management
- CVS
- Subversion
- Git
- Mercurial
- RCS
- GNU Arch
- LibreSource Synchronizer
- Team Foundation Server
- Visual Studio Team Services
- Build tools
- Make
- Rake
- Cabal
- Ant
- CADES
- Nant
- Maven
- Final Builder
- Gradle
- Team Foundation Server
- Visual Studio Team Services
- Visual Build Pro
- Editors
- Parsercreation tools
- Static code analysis tools
Libraries
editDesign languages
editPatterns, document many common programming and project management techniques
editProcesses and methodologies
edit- Agile
- Heavyweight
- Cleanroom
- ISO/IEC 12207— software life cycle processes
- ISO 9000andISO 9001
- Process Models
- Metamodels
Platforms
editA platform combines computer hardware and an operating system. As platforms grow more powerful and less costly, applications and tools grow more widely available.
- BREW
- Craysupercomputers
- DECminicomputers
- IBMmainframes
- LinuxPCs
- Classic Mac OSandmacOSPCs
- Microsoft.NET
- PalmPDAs
- Sun MicrosystemsSolaris
- WindowsPCs (Wintel)
- Symbian OS
Other Practices
edit- Communication
- Method engineering
- Pair programming
- Performance Engineering
- Programming productivity
- Refactoring
- Software inspections/Code reviews
- Software reuse
- Systems integration
- Teamwork
Other tools
editComputer science topics
editSkilled software engineers know a lot ofcomputer scienceincluding what is possible and impossible, and what is easy and hard for software.
- Algorithms,well-defined methods for solving specific problems.
- Compiler theory
- Data structures,well-defined methods for storing and retrieving data.
- Computability,some problems cannot be solved at all
- Complexity,some problems are solvable in principle, yet unsolvable in practice
- Formal methods
- Adaptive Systems
Mathematics topics
editDiscrete mathematicsis a key foundation ofsoftwareengineering.
- Numberrepresentation
- Set (computer science)
- Bags
- Graphs
- Logic
- Induction
- Combinatorics
Other
Life cycle phases
edit- Developmentlife cycle phase
- Requirements gathering / analysis
- Software architecture
- Computer programming
- Testing,detectsbugs
- Quality assurance,ensures compliance with process.
- ProductLife cycle phase andProject lifecycle
- Releasedevelopment stage,near the end of a release cycle
- Software development lifecycle
Deliverables
editDeliverables 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 andMaintenancepolicy, what should be backed-up, checked, configured,...
- Installers
- Migration
- Upgrade from previous installations
- Upgrade from competitor's installations
- Trainingmaterials, for each role
- Supportinfo for computer support groups.
- Marketingandsalesmaterials
- White papers,explain the technologies used in the applications
Business roles
edit- Operations
- Development
- Business
- Consulting— customization and installation of applications
- Sales
- Marketing
- Legal— contracts, intellectual property rights
- PrivacyandPrivacy engineering
- Support— helping customers use applications
- Personnel— hiring and training qualified personnel
- Finance— funding new development
- Academe
Management topics
edit- 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
- Process management
Business topics
edit- Quality programs
Software engineering profession
editHistory of software engineering
editHistory of software engineering
Pioneers
editMany people made important contributions to SE technologies, practices, or applications.
- John Backus:Fortran,first optimizing compiler,BNF
- Victor Basili:Experience factory.
- F.L. Bauer:Stackprinciple, popularized the termSoftware 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-orienteddesign,UML.
- Fred Brooks:ManagedSystem 360andOS 360.WroteThe Mythical Man-MonthandNo Silver Bullet.
- Larry Constantine:Structured design,coupling,cohesion
- Edsger Dijkstra:WroteNotes on Structured Programming,A Discipline of ProgrammingandGo 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 theENIAC,the first electronic digital computer, and trained some of the firsthuman computers
- Lois Haibt:FORTRAN,wrote the firstparser
- Margaret Hamilton:Coined the term "software engineering", developedUniversal 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 theSoftware Engineering Institute.
- Jean Ichbiah:Ada
- Michael A. Jackson:Jackson Structured Programming,Jackson System Development
- Bill Joy:BerkeleyUnix,vi,Java.
- Alan Kay:Smalltalk
- Brian Kernighan:C and Unix.
- Donald Knuth:WroteThe 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 originalMacintoshGUI,authoredThe Humane Interface
- Dennis Ritchie:CandUnix.
- Winston W. Royce:Waterfall model.
- Mary Shaw:Softwarearchitecture.
- Richard Stallman:Founder of theFree Software Foundation
- Linus Torvalds:Linuxkernel,free software/open sourcedevelopment.
- Will Tracz:Reuse, ACM Software Engineering Notes.
- Gerald Weinberg:WroteThe Psychology of Computer Programming.
- Elaine Weyuker:Software testing
- Jeannette Wing:Formal specifications.
- Ed Yourdon:Structured programming,wroteThe Decline and Fall of the American Programmer.
See also
Notable publications
edit- About Face: The Essentials of User Interface DesignbyAlan Cooper,about user interface design.ISBN0-7645-2641-3
- The Capability Maturity ModelbyWatts Humphrey.Written for theSoftware Engineering Institute,emphasizing management and process. (SeeManaging the Software ProcessISBN0-201-18095-2)
- The Cathedral and the BazaarbyEric Raymondabout open source development.
- The Decline and Fall of the American ProgrammerbyEd Yourdonpredicts the end of software development in the U.S.ISBN0-13-191958-X
- Design PatternsbyErich Gamma,Richard Helm,Ralph Johnson,andJohn Vlissides.ISBN0-201-63361-2
- Extreme Programming ExplainedbyKent BeckISBN0-321-27865-8
- "Go To Statement Considered Harmful"byEdsger Dijkstra.
- "Internet, Innovation and Open Source:Actors in the Network" —First Mondayarticle byIlkka Tuomi(2000)source
- The Mythical Man-MonthbyFred Brooks,about project management.ISBN0-201-83595-9
- Object-oriented Analysis and DesignbyGrady Booch.ISBN0-8053-5340-2
- PeoplewarebyTom DeMarcoand Tim Lister.ISBN0-932633-43-9
- The pragmatic engineer versus the scientific designerbyE. W. Dijkstra[1]
- Principles of Software Engineering ManagementbyTom Gilbabout evolutionary processes.ISBN0-201-19246-2
- The Psychology of Computer ProgrammingbyGerald Weinberg.Written as an independent consultant, partly about his years at IBM.ISBN0-932633-42-0
- Refactoring: Improving the Design of Existing CodebyMartin Fowler,Kent Beck,John Brant,William Opdyke,and Don Roberts.ISBN0-201-48567-2
- The Pragmatic Programmer: from journeyman to masterbyAndrew Hunt,andDavid Thomas.ISBN0-201-61622-X
- Software Engineering Body of Knowledge(SWEBOK)ISO/IEC TR 19759
Related fields
edit- Computer science
- Information engineering
- Information technology
- Traditional engineering
- Software engineering
- ArtsandSciences
- Application software
- Programming
- Systems Engineering
See also
edit- Index of software engineering articles
- Search-based software engineering
- SWEBOKSoftware engineering body of knowledge
- CCSEComputing curriculum for software engineering
- Computer terms etymology,the origins of computer terms
- Complexityor scaling
- Second system syndrome
- optimization
- Source code escrow
- Feature interaction problem
- Certification (software engineering)
- Engineering disasters#Failure due to software
- Outline of software development
- List of software development philosophies
References
edit- ^Bourque, Pierre; Dupuis, Robert, eds. (2004).Guide to the Software Engineering Body of Knowledge - 2004 Version.IEEE Computer Society.p. 1.ISBN0-7695-2330-7.
External links
edit- Professional organizations
- Professionalism
- Education
- Standards
- Government organizations
- Agile
- Other organizations
- Demographics
- Surveys
- Other