* SIGSOFT: Software Engineering

This model became the foundation from which Carnegie Mellon created the Software Engineering Institute ( SEI ).

Active development of the model by the US Department of Defense Software Engineering Institute ( SEI ) began in 1986 when Humphrey joined the Software Engineering Institute located at Carnegie Mellon University in Pittsburgh, Pennsylvania after retiring from IBM.

Organizations were originally assessed using a process maturity questionnaire and a Software Capability Evaluation method devised by Humphrey and his colleagues at the Software Engineering Institute

* CSIRAC The Computation Laboratory at the University of Melbourne's Dept of Computer Science and Software Engineering

* RAISE, Rigorous Approach to Industrial Software Engineering, was developed as part of the European ESPRIT II LaCoS project in the 1990s, led by Dines Bjørner.

* Domain-Specific Languages for Software Engineering ( Compares 4GLs to DSLs )

In addition to The Mythical Man-Month, Brooks is also known for the paper No Silver Bullet — Essence and Accident in Software Engineering.

The Software Engineering Institute at Carnegie Mellon University, in a publication titled " Governing for Enterprise Security ( GES )", defines characteristics of effective security governance.

In 2008, Id Software was honored at the 59th Annual Technology & Engineering Emmy Awards for the pioneering work Quake represented in user modifiable games.

In 2009 OMG, together with the Software Engineering Institute at Carnegie Mellon, launched the Consortium of IT Software Quality ( CISQ ).

The Software Process Engineering Metamodel ( SPEM ) is an OMG-standard for Meta-Process Modeling.

* Capability Maturity Model from the Software Engineering Institute.

* Team Software Process ( TSP ) from the Software Engineering Institute.

* Mens, Tom and Tourwé, Tom ( 2004 ) A Survey of Software Refactoring, IEEE Transactions on Software Engineering, February 2004 ( vol.

The term software engineering first appeared in the 1968 NATO Software Engineering Conference, and was meant to provoke thought regarding the perceived " software crisis " at the time.

The IEEE's Guide to the Software Engineering Body of Knowledge-2004 Version, or SWEBOK, defines the field and describes the knowledge the IEEE expects a practicing software engineer to have.

The IEEE also promulgates a " Software Engineering Code of Ethics ".

This approach is consistent with other management standards such as ISO 9000 and the Software Engineering Institute's CMMI.

Watts Humphrey's Capability Maturity Model ( CMM ) was published in 1988 and as a book in 1989, in Managing the Software Process.

The best-known example of SEI work in management practices is the SEI ’ s Capability Maturity Model ( CMM ) for Software ( now Capability Maturity Model Integration ( CMMI )).

The program resulted in the development of the Capability Maturity Model, published in 1989 in Humphrey's " Managing the Software Process " and inspired the later development of the Personal Software Process ( PSP ) and the Team Software Process ( TSP ).

Leadership, Teamwork, and Trust: Building a Competitive Software Capability.

In 1988, the Software Engineering Institute suggested that SPC could be applied to non-manufacturing processes, such as software engineering processes, in the Capability Maturity Model ( CMM ).

ISO / IEC 15504 Information technology — Process assessment, also known as SPICE ( Software Process Improvement and Capability Determination ), is a set of technical standards documents for the computer software development process and related business management functions.

SPICE initially stood for " Software Process Improvement and Capability Evaluation ", but in consideration of French concerns over the meaning of " evaluation ", SPICE has now been redefined as " Software Process Improvement and Capability Determination ".

The PSP was created by Watts Humphrey to apply the underlying principles of the Software Engineering Institute ’ s ( SEI ) Capability Maturity Model ( CMM ) to the software development practices of a single developer.

* SPICE ( Software Process Improvement and Capability Determination ), see ( ISO 15504 ), a process-assessment framework

The Software Engineering Institute has its own process assessment and improvement methods, called CMMi ( Capability Maturity Model — integrated ) and IDEAL respectively.

To fulfill these needs, Microsoft represents the metamodel of MSF 4. 0 in two prescriptive methodology templates that provide specific process guidance, named Microsoft Solutions Framework for Agile Software Development ( MSF4ASD ) and Microsoft Solutions Framework for Capability Maturity Model Integration Process Improvement ( MSF4CMMI ).

Capability Maturity Model was created at the Software Engineering Institute of Carnegie Mellon University, and is a process improvement approach that provides organizations with the essential elements of continuous process improvement resulting in a reduced SDLC, improved ability to meet the cost and schedule targets, building products of high quality.

* High Maturity Program, a concept in Software development maturity.

* Software Architectural Model

* Software Architectural Model

* Philippe Kruchten: Architectural Blueprints-the 4 + 1 View Model of Software Architecture.

CA-Datacom and Software AG's ADABAS are competing databases for z / OS, and there are certain niche products as well ( Model 204, SUPRA SQL, NOMAD, etc.

The spiral model was defined by Barry Boehm in his 1986 article " A Spiral Model of Software Development and Enhancement ".

Software systems based on IDLs include Sun's ONC RPC, The Open Group's Distributed Computing Environment, IBM's System Object Model, the Object Management Group's CORBA ( which implements OMG IDL, an IDL based on DCE / RPC ), Mozilla's XPCOM, Facebook's Thrift and WSDL for Web services.

Software and data is on the Earth Gravitational Model 2008 ( EGM2008 )-WGS 84 Version page.

A new disc version released by Superior Software in 1986 was enhanced to take advantage of the BBC Micro Model B's successors including the BBC Micro Model B +, Master 128 computers, the optional 6502 Second Processor or sideways RAM, if they were fitted.

His contributions to the field, according to Boehm ( 1997 ) himself, include " the Constructive Cost Model ( COCOMO ), the Spiral Model of the software process, the Theory W ( win-win ) approach to software management and requirements determination and two advanced software engineering environments: the TRW Software Productivity System and Quantum Leap Environment ".

Barry Boehm's 1981 book Software Engineering Economics documents his Constructive Cost Model ( COCOMO ).

It was only in 1998, after the development of the ICM that Barry Boehm along with A Winsor Brown started to focus on reconciling it with the WinWin Spiral Model and its incarnation in MBASE and the follow-on Lean MBASE, and working towards an Incremental Commitment Model for Software ( ICMS ) by adapting the existing WinWin Spiral Model support tools.

The abstract model was first published as an IETF Request for Comments, < nowiki > RFC 2778 </ nowiki > " A Model for Presence and Instant Messaging " in February 2000, which was authored by Mark Day of SightPath ( formerly of Lotus Software where helped develop IBM Lotus Sametime, now Chief Scientist at Riverbed Technology ), Jonathan Rosenberg of dynamicsoft ( now the Chief Technology Strategist for Skype ) and Hiroyasu Sugano of Fujitsu Laboratories LtdLtd.

* Raccoon ( 1995 ) The Chaos Model and the Chaos Life Cycle, in ACM Software Engineering Notes, Volume 20, Number 1, Pages 55 to 66, January 1995, ACM Press.

Under the name Big Five Software, Bill Hogue programmed commercial computer games in the late 1970s for Radio Shack's TRS-80 Model I home computer.