classes ::: Engineering, Computer Science, subject,
children :::
branches ::: Software Engineering

bookmarks: Instances - Definitions - Quotes - Chapters - Wordnet - Webgen


object:Software Engineering
parent subject class:Engineering
parent subject class:Computer Science
class:subject

see also :::

questions, comments, suggestions/feedback, take-down requests, contribute, etc
contact me @ integralyogin@gmail.com or
join the integral discord server (chatrooms)
if the page you visited was empty, it may be noted and I will try to fill it out. cheers



now begins generated list of local instances, definitions, quotes, instances in chapters, wordnet info if available and instances among weblinks


OBJECT INSTANCES [0] - TOPICS - AUTHORS - BOOKS - CHAPTERS - CLASSES - SEE ALSO - SIMILAR TITLES

TOPICS
SEE ALSO


AUTH

BOOKS

IN CHAPTERS TITLE

IN CHAPTERS CLASSNAME

IN CHAPTERS TEXT

PRIMARY CLASS

subject
SIMILAR TITLES
Software Engineering

DEFINITIONS


TERMS STARTING WITH

Software Engineering Environment (SEE) A set of management and technical tools to support software development, usually integrated in a coherent framework; equivalent to an {IPSE}. (1994-11-03)

Software Engineering Environment ::: (SEE) A set of management and technical tools to support software development, usually integrated in a coherent framework; equivalent to an IPSE. (1994-11-03)

software engineering "programming" (SE) A systematic approach to the analysis, design, implementation and maintenance of {software}. It often involves the use of {CASE} tools. There are various models of the {software life-cycle}, and many {methodologies} for the different phases. (1994-11-03)

software engineering ::: (programming) (SE) A systematic approach to the analysis, design, implementation and maintenance of software. It often involves the use of CASE tools. There are various models of the software life-cycle, and many methodologies for the different phases. (1994-11-03)

software engineering ::: The application of engineering to the development of software in a systematic method.[285][286][287]


TERMS ANYWHERE

Acknowledgements ::: (introduction) Many thanks to the hundreds of , mirror site maintainers and the maintainers of the following resources from which some entries originate:Mike Sendall's STING Software engineering glossary , 1993-10-13,Bill Kinnersley's v2.2, 1994-01-15,Mark Hopkins' catalogue of Free Compilers and Interpreters v6.4, 1994-02-28,The on-line hacker Jargon File v3.0.0, 1993-07-27,Internet Users' Glossary (RFC 1392, FYI 18), Jan 1993.John Cross's computer glossary, 1994-11-01.John Bayko's Great Microprocessors of the Past and Present, v4.0.0, 1994-08-18.Electronic Commerce Dictionary. (1997-08-01)

Acknowledgements "introduction" Many thanks to the thousands of {contributors (contributors.html)} and especially to the Guest Editors, mirror site maintainers and the maintainers of the following resources from which some entries originate: Mike Sendall's STING Software engineering glossary "sendall@dxpt01.cern.ch", 1993-10-13, Bill Kinnersley's {Language List (http://people.ku.edu/~nkinners/LangList/Extras/langlist.htm)} v2.2, 1994-01-15, Mark Hopkins' catalogue of Free Compilers and Interpreters v6.4, 1994-02-28, The on-line hacker {Jargon File} v3.0.0, 1993-07-27, Internet Users' Glossary (RFC 1392, FYI 18), Jan 1993. John Cross's computer glossary, 1994-11-01. John Bayko's Great Microprocessors of the Past and Present, v4.0.0, 1994-08-18. {Electronic Commerce Dictionary}. (2014-09-11)

Ada "language" (After {Ada Lovelace}) A {Pascal}-descended language, designed by Jean Ichbiah's team at {CII Honeywell} in 1979, made mandatory for Department of Defense software projects by the Pentagon. The original language was standardised as "Ada 83", the latest is "{Ada 95}". Ada is a large, complex, {block-structured} language aimed primarily at {embedded} applications. It has facilities for {real-time} response, {concurrency}, hardware access and reliable run-time error handling. In support of large-scale {software engineering}, it emphasises {strong typing}, {data abstraction} and {encapsulation}. The type system uses {name equivalence} and includes both {subtypes} and {derived types}. Both fixed and {floating-point} numerical types are supported. {Control flow} is fully bracketed: if-then-elsif-end if, case-is-when-end case, loop-exit-end loop, goto. Subprogram parameters are in, out, or inout. Variables imported from other packages may be hidden or directly visible. Operators may be {overloaded} and so may {enumeration} literals. There are user-defined {exceptions} and {exception handlers}. An Ada program consists of a set of packages encapsulating data objects and their related operations. A package has a separately compilable body and interface. Ada permits {generic packages} and subroutines, possibly parametrised. Ada support {single inheritance}, using "tagged types" which are types that can be extended via {inheritance}. Ada programming places a heavy emphasis on {multitasking}. Tasks are synchronised by the {rendezvous}, in which a task waits for one of its subroutines to be executed by another. The conditional entry makes it possible for a task to test whether an entry is ready. The selective wait waits for either of two entries or waits for a limited time. Ada is often criticised, especially for its size and complexity, and this is attributed to its having been designed by committee. In fact, both Ada 83 and Ada 95 were designed by small design teams to be internally consistent and tightly integrated. By contrast, two possible competitors, {Fortran 90} and {C++} have both become products designed by large and disparate volunteer committees. See also {Ada/Ed}, {Toy/Ada}. {Home of the Brave Ada Programmers (http://lglwww.epfl.ch/Ada/)}. {Ada FAQs (http://lglwww.epfl.ch/Ada/FAQ/)} (hypertext), {text only (ftp://lglftp.epfl.ch/pub/Ada/FAQ)}. {(http://wuarchive.wustl.edu/languages/ada/)}, {(ftp://ajpo.sei.cmu.edu/)}, {(ftp://stars.rosslyn.unisys.com/pub/ACE_8.0)}. E-mail: "adainfo@ajpo.sei.cmu.edu". {Usenet} newsgroup: {news:comp.lang.ada}. {An Ada grammar (ftp://primost.cs.wisc.edu/)} including a lex scanner and yacc parser is available. E-mail: "masticol@dumas.rutgers.edu". {Another yacc grammar and parser for Ada by Herman Fischer (ftp://wsmr-simtel20.army.mil/PD2:"ADA.EXTERNAL-TOOLS"GRAM2.SRC)}. An {LR parser} and {pretty-printer} for {Ada} from NASA is available from the {Ada Software Repository}. {Adamakegen} generates {makefiles} for {Ada} programs. ["Reference Manual for the Ada Programming Language", ANSI/MIL STD 1815A, US DoD (Jan 1983)]. Earlier draft versions appeared in July 1980 and July 1982. ISO 1987. [{Jargon File}] (2000-08-12)

ADDD "tool" A Depository of Development Documents. A {public domain} Software Engineering Environment from {GMD} developed as part of the {STONE} project. (1995-02-03)

ADDD ::: (tool) A Depository of Development Documents.A public domain Software Engineering Environment from GMD developed as part of the STONE project. (1995-02-03)

application lifecycle management "programming" (ALM) A combination of {software engineering}, {requirements management}, {architecture}, {coding}, {testing}, {tracking} and {release management}. (2009-06-10)

ASSET {Asset Source for Software Engineering Technology}

Asset Source for Software Engineering Technology "project" (ASSET) A programme to promote software {reuse} by the US {DoD}. See also {ASSET Reuse Library}. (1996-08-19)

Asset Source for Software Engineering Technology ::: (project) (ASSET) A programme to promote software reuse by the US DoD.See also ASSET Reuse Library. (1996-08-19)

AverStar "company" The US software engineering company that developed {Hal}, under their former name, "Intermetrics". Other products include {CS-4}, {Red}, {Mwave Developers Toolkit} ({multimedia} for {IBM PC}), {cross-compilers} for {C} and {C++}; {Ada '83}, {Ada 95}, and {SAMeDL}. AverStar also supply {client/server} systems; custom software applications and {turnkey} systems; independent verification and validation; {CAE} integration technology; languages and compilers: {Ada}, {C}, {C++}, {HDLs} ({MHDL}), {Modula}, {SPL/1}. Address: Intermetrics, Inc., 733 Concord Avenue, Cambridge, MA 02138, USA. Telephone: +1 (617) 661 1840. Fax: +1 (617) 868 2843. Address: 7918 Jones Branch Drive, McLean, Va 22102, USA. Telephone: +1 (703) 827-2606. Fax: +1 (703) 827-5560. Also Houston, TX, Huntington Beach, CA, Warminster, PA, and others. {AverStar Home (http://averstar.com/)}. (2003-02-17)

AverStar ::: (company) The US software engineering company that developed Hal, under their former name, Intermetrics. Other products include CS-4, Red, Mwave validation; CAE integration technology; languages and compilers: Ada, C, C++, HDLs (MHDL), Modula, SPL/1.Address: Intermetrics, Inc., 733 Concord Avenue, Cambridge, MA 02138, USA. Telephone: +1 (617) 661 1840. Fax: +1 (617) 868 2843.Address: 7918 Jones Branch Drive, McLean, Va 22102, USA. Telephone: +1 (703) 827-2606. Fax: +1 (703) 827-5560.Also Houston, TX, Huntington Beach, CA, Warminster, PA, and others. .(2003-02-17)

Berard Object and Class Specifier "tool, object-oriented, modeling" (BOCS) An {object-oriented} {CASE} tool released by US company, {Berard Software Engineering} on 1993-07-05. BOCS helps users document and model a system and its underlying objects. It includes libraries to manage {requirements}, object and {class} specifications and graphical models. [Computerworld, 1993-07-05, p63]. (2015-06-17)

BOCS ::: Berard Object and Class Specifier, an Object-oriented CASE tool from Berard Software Engineering.

Software Engineering Environment (SEE) A set of management and technical tools to support software development, usually integrated in a coherent framework; equivalent to an {IPSE}. (1994-11-03)

Software Engineering Environment ::: (SEE) A set of management and technical tools to support software development, usually integrated in a coherent framework; equivalent to an IPSE. (1994-11-03)

CADRE "company" The US {software engineering} vendor which merged with {Bachman Information Systems} to form {Cayenne Software} in July 1996. (1998-02-08)

CADRE ::: (company) The US software engineering vendor which merged with Bachman Information Systems to form Cayenne Software in July 1996. (1998-02-08)

Capabilities Maturity Model ::: (software) (CMM) The Software Engineering Institute's model of software engineering that specifies five levels of maturity of the processes of a expanded to cover other areas including Human Resources and Software Acquitition.The levels - focii - and key process areas are:Level 1 Initial - Heroes - None.Level 2 Repeatable - Project Management - Software Project Planning, Software Project Tracking and Oversight, Software Subcontract Management, Software Quality Assurance, Software Configuration Management, Requirements Management.Level 3 Defined - Engineering Process - Organisation Process Focus, Organisation Process Definition, Peer Reviews, Training Program, Inter-group Coordination, Software Product Engineering, Integrated Software Management.Level 4 Managed - Product and Process Quality - Software Quality Management, Quantitative Process Management.Level 5 Optimising - Continuous Improvement - Process Change Management, Technology Change Management, Defect Prevention.[Reference?](2001-04-28)

Capability Maturity Model "software" (CMM) The {Software Engineering Institute}'s model of {software engineering} that specifies five levels of maturity of the processes of a software organisation. CMM offers a framework for evolutionary process improvement. Originally applied to software development (SE-CMM), it has been expanded to cover other areas including Human Resources and Software Acquitition. The levels - focii - and key process areas are: Level 1 Initial - Heroes - None. Level 2 Repeatable - Project Management - Software Project Planning, Software Project Tracking and Oversight, Software Subcontract Management, Software Quality Assurance, Software Configuration Management, Requirements Management. Level 3 Defined - Engineering Process - Organisation Process Focus, Organisation Process Definition, Peer Reviews, Training Program, Inter-group Coordination, Software Product Engineering, Integrated Software Management. Level 4 Managed - Product and Process Quality - Software Quality Management, Quantitative Process Management. Level 5 Optimising - Continuous Improvement - Process Change Management, Technology Change Management, Defect Prevention. {(http://www.sei.cmu.edu/cmm/cmm.html)}. (2001-04-28)

CASE ::: 1. Computer Aided Software Engineering.2. Common Application Service Element.

CASE 1. {Computer Aided Software Engineering}. 2. {Common Application Service Element}.

CA-Telon ::: (application) A Computer Aided Software Engineering (CASE) tool for designing, generating and maintaining COBOL and PL/I application programs. Telon was developed by Pansophic Systems who were bought by Computer Associates in 1991, whereupon it was renamed CA-Telon.It supports high-level, non-prodedural design and prototyping, combined with automatic code generation. There are mainframe and PC versions. The generated COBOL applications can execute in AIX, HP-UX, VSE, OS/400 for the AS/400, PC-DOS, or OS/2.(2000-01-19)

CA-Telon "application" A {Computer Aided Software Engineering} (CASE) tool for designing, generating and maintaining {COBOL} and {PL/I} {application programs}. Telon was developed by {Pansophic} Systems who were bought by {Computer Associates} in 1991, whereupon it was renamed CA-Telon. It supports high-level, non-{prodedural} design and prototyping, combined with automatic {code generation}. There are {mainframe} and {PC} versions. The generated COBOL applications can execute in {AIX}, {HP-UX}, {VSE}, {OS/400} for the {AS/400}, {PC-DOS}, or {OS/2}. (2000-01-19)

CDL ::: 1. Computer Definition [Design?] Language. A hardware description language. Computer Organisation and Microprogramming, Yaohan Chu, P-H 1970.2. Command Definition Language. Portion of ICES used to implement commands. Sammet 1969, p.618-620.3. Compiler Description Language. C.H.A. Koster, 1969. Intended for implementation of the rules of an affix grammar by recursive procedures. A C.H.A. Koster, LNCS 47, Springer 1977, pp.341-351. Using the CDL Compiler Compiler, C.H.A. Koster, 1974. Versions: CDL2, CDLM used at Manchester.4. Common Design Language. Common Design Language, IBM, Software Engineering Inst, Sept 1983.5. Control Definition Language. Ideas which contributed to Smalltalk.[Control Structures for Programming Languges, David A. Fisher, PhD Thesis, CMU 1970].

CDL 1. Computer Definition [Design?] Language. A hardware description language. "Computer Organisation and Microprogramming", Yaohan Chu, P-H 1970. 2. Command Definition Language. Portion of ICES used to implement commands. Sammet 1969, p.618-620. 3. Compiler Description Language. C.H.A. Koster, 1969. Intended for implementation of the rules of an affix grammar by recursive procedures. A procedure may be a set of tree-structured alternatives, each alternative is executed until one successfully exits. Used in a portable COBOL-74 compiler from MPB, mprolog system from SzKI, and the Mephisto chess computer. "CDL: A Compiler Implementation Language", in Methods of Algorithmic Language Implementation, C.H.A. Koster, LNCS 47, Springer 1977, pp.341-351. "Using the CDL Compiler Compiler", C.H.A. Koster, 1974. Versions: CDL2, CDLM used at Manchester. 4. Common Design Language. "Common Design Language", IBM, Software Engineering Inst, Sept 1983. 5. Control Definition Language. Ideas which contributed to Smalltalk. ["Control Structures for Programming Languges", David A. Fisher, PhD Thesis, CMU 1970].

CGI 1. "web" {Common Gateway Interface}. 2. "graphics" {computer-generated imagery}. 3. "company" A French {software engineering} vendor in the US. 4. "company" {Computer Generation Incorporated}.

CGI ::: 1. (World-Wide Web) Common Gateway Interface.2. (graphics) computer-generated imagery.3. (company) A French software engineering vendor in the US.4. (company) Computer Generation Incorporated.

Computer Aided Software Engineering ::: (programming) (CASE, or assisted) A technique for using computers to help with one or more phases of the software life-cycle, including the Adopting the CASE approach to building and maintaining systems involves software tools and training for the developers who will use them. (1996-05-10)

Computer Aided Software Engineering "programming" (CASE, or "- assisted -") A technique for using computers to help with one or more phases of the {software life-cycle}, including the systematic analysis, design, implementation and maintenance of software. Adopting the CASE approach to building and maintaining systems involves software tools and training for the developers who will use them. (1996-05-10)

Computer-Assisted Software Engineering {Computer-Aided Software Engineering}

Constructive Cost Model "programming" (COCOMO) A method for estimating the cost of a {software} package, proposed by Dr Barry Boehm. The Basic COCOMO Model estimates the effort required to develop software in three modes of development ({Organic Mode}, {Semidetached Mode}, or {Embedded Mode}) using only {DSIs} as an input. The Basic model is good for quick estimates. The Intermediate Model extends the Basic Model with an {Effort Adjustment Factor} (EAF) and different coefficients for the effort equation. The user supplies settings for cost drivers that determine the effort and duration of the software projects. It also allows DSI values and cost drivers to be chosen for individual components instead of for the system as a whole. The Detailed COCOMO Model uses effort multipliers for each phase of the project and provides a three-level product hierarchy and has some other capabilities such as a procedure for adjusting the phase distribution of the development schedule. ["Software Engineering Economics", B. Boehm, Prentice-Hall, 1981]. (1996-05-29)

Constructive Cost Model ::: (programming) (COCOMO) A method for evaluating the cost of a software package proposed by Dr Barry Boehm. There are a number of different types:The Basic COCOMO Model estimates the effort required to develop software in three modes of development (Organic Mode, Semidetached Mode, or Embedded Mode) using only DSIs as an input. The Basic model is good for quick, early, and rough order of magnitude estimates.The Intermediate COCOMO Model an extension of the Basic COCOMO model. The Intermediate model uses an Effort Adjustment Factor (EAF) and slightly different components. DSI values and cost drivers can be chosen for individual components instead of for the system as a whole.The Detailed COCOMO Model differs from the Intermediate COCOMO model in that it uses effort multipliers for each phase of the project. These phase dependent product hierarchy and has some other capabilities such as a procedure for adjusting the phase distribution of the development schedule.[Software Engineering Economics, B. Boehm, Prentice-Hall, 1981]. (1996-05-29)

Contextually Communicating Sequential Processes ::: (CCSP) A notation based on CSP.[Contextually Communicating Sequential Processes - A Software Engineering Approach, M. Hull et al, Software Prac & Exp 16(9):845-864 (Sept 1986)]. (1994-11-01)

Contextually Communicating Sequential Processes "language" (CCSP) A notation based on {CSP}. ["Contextually Communicating Sequential Processes - A Software Engineering Approach", M. Hull et al, Software Prac & Exp 16(9):845-864, Sept 1986]. (1994-11-01)

coupling "programming, hardware" The degree to which components depend on one another. There are two types of coupling, "tight" and "loose". Loose coupling is desirable for good {software engineering} but tight coupling may be necessary for maximum performance. Coupling is increased when the data exchanged between components becomes larger or more complex. (1996-08-01)

Darwin 1. "operating system" An {operating system} based on the {FreeBSD} version of {Unix}, running on top of a {microkernel} ({Mach} 3.0 with darwin 1.02) that offers advanced networking, services such as the {Apache} {web server}, and support for both {Macintosh} and Unix {file systems}. Darwin was originally released in March 1999. It currently runs on {PowerPC} based Macintosh computers, and, in October 2000, was being ported to {Intel} processor-based computers and compatible systems by the Darwin community. 2. "programming, tool" A general purpose structuring tool of use in building complex {distributed systems} from diverse components and diverse component interaction mechanisms. Darwin is being developed by the Distributed Software Engineering Section of the Department of Computing at {Imperial College}. It is in essence a {declarative} binding language which can be used to define hierarchic compositions of interconnected components. Distribution is dealt with orthogonally to system structuring. The language allows the specification of both static structures and dynamic structures which evolve during execution. The central abstractions managed by Darwin are components and services. Bindings are formed by manipulating references to services. The {operational semantics} of Darwin is described in terms of the {Pi-calculus}, {Milner}'s calculus of mobile processes. The correspondence between the treatment of names in the Pi-calculus and the management of service references in Darwin leads to an elegant and concise Pi-calculus model of Darwin's {operational semantics}. The model has proved useful in arguing the correctness of Darwin implementations and in designing extensions to Darwin and reasoning about their behaviour. {Distributed Software Engineering Section (http://www-dse.doc.ic.ac.uk/)}. {Darwin publications (http://scorch.doc.ic.ac.uk/dse-papers/darwin/)}. E-mail: Jeff Magee "jnm@doc.ic.ac.uk", Naranker Dulay "nd@doc.ic.ac.uk". 3. {Core War}. (2003-08-08)

Department of Defense "body" (DoD) The US military body responsible for sponsoring many software engineering standards. (1996-05-29)

Department of Defense ::: (body) (DoD) The US military body responsible for sponsoring many software engineering standards. (1996-05-29)

Domain Software Engineering Environment "programming" (DSEE) A proprietary {CASE} framework and {configuration management} system from {Apollo}. (1996-05-29)

Domain Software Engineering Environment ::: (programming) (DSEE) A proprietary CASE framework and configuration management system from Apollo. (1996-05-29)

DSEE {Domain Software Engineering Environment}

EAST ::: A Eureka project developing a software engineering platform. (1994-12-07)

EAST A {Eureka} project developing a {software engineering} {platform}. (1994-12-07)

Edward Yourdon ::: (person) A software engineering consultant, widely known as the developer of the Yourdon method of structured systems analysis and design, as well as software technology trends and products in the United States and several other countries around the world.Ed Yourdon received a B.S. in Applied Mathematics from MIT, and has done graduate work at MIT and at the Polytechnic Institute of New York. He has been in Buenos Aires, Argentina and has received numerous honors and awards from other universities and professional societies around the world.He has worked in the computer industry for 30 years, including positions with DEC and General Electric. Earlier in his career, he worked on over 25 different mainframe computers, and was involved in a number of pioneering computer projects involving time-sharing and virtual memory.In 1974, he founded the consulting firm, Yourdon, Inc.. He is currently immersed in research in new developments in software engineering, such as object-oriented software development and system dynamics modelling.Ed Yourdon is the author of over 200 technical articles; he has also written 19 computer books, including a novel on computer crime and a book for the general Portugese, Dutch, French, German, and other languages, and his articles have appeared in virtually all of the major computer journals.He is a regular keynote speaker at major computer conferences around the world, and serves as the conference Chairman for Digital Consulting's SOFTWARE WORLD software industry opportunities in the former Soviet Union, and a member of the expert advisory panel on CASE acquisition for the U.S. Department of Defense.Mr. Yourdon was born on a small planet at the edge of one of the distant red-shifted galaxies. He now lives in the Center of the Universe (New York City) with his wife, three children, and nine Macintosh computers, all of which are linked together through an Appletalk network. (1995-04-16)

Edward Yourdon "person" A {software engineering} consultant, widely known as the developer of the "{Yourdon method}" of structured systems analysis and design, as well as the co-developer of the Coad/Yourdon method of {object-oriented analysis} and design. He is also the editor of three software journals - American Programmer, Guerrilla Programmer, and Application Development Strategies - that analyse software technology trends and products in the United States and several other countries around the world. Ed Yourdon received a B.S. in Applied Mathematics from {MIT}, and has done graduate work at MIT and at the Polytechnic Institute of New York. He has been appointed an Honorary Professor of {Information Technology} at Universidad CAECE in Buenos Aires, Argentina and has received numerous honors and awards from other universities and professional societies around the world. He has worked in the computer industry for 30 years, including positions with {DEC} and {General Electric}. Earlier in his career, he worked on over 25 different {mainframe} computers, and was involved in a number of pioneering computer projects involving {time-sharing} and {virtual memory}. In 1974, he founded the consulting firm, {Yourdon, Inc.}. He is currently immersed in research in new developments in software engineering, such as object-oriented software development and {system dynamics} modelling. Ed Yourdon is the author of over 200 technical articles; he has also written 19 computer books, including a novel on {computer crime} and a book for the general public entitled Nations At Risk. His most recent books are Object-Oriented Systems Development (1994), Decline and Fall of the American Programmer (1992), Object-Oriented Design (1991), and Object-Oriented Analysis (1990). Several of his books have been translated into Japanese, Russian, Chinese, Spanish, Portugese, Dutch, French, German, and other languages, and his articles have appeared in virtually all of the major computer journals. He is a regular keynote speaker at major computer conferences around the world, and serves as the conference Chairman for Digital Consulting's SOFTWARE WORLD conference. He was an advisor to Technology Transfer's research project on software industry opportunities in the former Soviet Union, and a member of the expert advisory panel on CASE acquisition for the U.S. Department of Defense. Mr. Yourdon was born on a small planet at the edge of one of the distant red-shifted galaxies. He now lives in the Center of the Universe (New York City) with his wife, three children, and nine Macintosh computers, all of which are linked together through an Appletalk network. (1995-04-16)

Eiffel "language" An {object-oriented} language produced by {Bertrand Meyer} in 1985. Eiffel has {classes} with {multiple inheritance} and {repeated inheritance}, {deferred class}es (like {Smalltalk}'s {abstract class}), and {clusters} of classes. Objects can have both {static types} and {dynamic types}. The dynamic type must be a descendant of the static (declared) type. {Dynamic binding} resolves {multiple inheritance} clashes. It has flattened forms of classes, in which all of the inherited features are added at the same level and {generic class}es parametrised by type. Other features are {persistent objects}, {garbage collection}, {exception} handling, {foreign language interface}. Classes may be equipped with {assertions} (routine preconditions and postconditions, class {invariants}) implementing the theory of "{Design by Contract}" and helping produce more reliable software. Eiffel is compiled to {C}. It comes with libraries containing several hundred classes: data structures and {algorithms} (EiffelBase), graphics and user interfaces (EiffelVision) and language analysis (EiffelLex, EiffelParse). The first release of Eiffel was release 1.4, introduced at the first {OOPSLA} in October 1986. The language proper was first described in a University of California, Santa Barbara report dated September 1985. Eiffel is available, with different libraries, from several sources including {Interactive Software Engineering}, USA (ISE Eiffel version 3.3); Sig Computer GmbH, Germany (Eiffel/S); and {Tower, Inc.}, Austin (Tower Eiffel). The language definition is administered by an open organisation, the Nonprofit International Consortium for Eiffel (NICE). There is a standard kernel library. An {Eiffel source checker} and compiler {front-end} is available. See also {Sather}, {Distributed Eiffel}, {Lace}, {shelf}. E-mail: "queries@eiffel.com". ["Eiffel: The Language", Bertrand Meyer, P-H 1992]. (1998-11-15)

Eiffel ::: (language) An object-oriented language produced by Bertrand Meyer in 1985. Eiffel has classes with multiple inheritance and repeated inheritance, inherited features are added at the same level and generic classes parametrised by type.Other features are persistent objects, garbage collection, exception handling, foreign language interface. Classes may be equipped with assertions (routine preconditions and postconditions, class invariants) implementing the theory of Design by Contract and helping produce more reliable software.Eiffel is compiled to C. It comes with libraries containing several hundred classes: data structures and algorithms (EiffelBase), graphics and user interfaces (EiffelVision) and language analysis (EiffelLex, EiffelParse).The first release of Eiffel was release 1.4, introduced at the first OOPSLA in October 1986. The language proper was first described in a University of California, Santa Barbara report dated September 1985.Eiffel is available, with different libraries, from several sources including Interactive Software Engineering, USA (ISE Eiffel version 3.3); Sig Computer GmbH, Germany (Eiffel/S); and Tower, Inc., Austin (Tower Eiffel).The language definition is administered by an open organisation, the Nonprofit International Consortium for Eiffel (NICE). There is a standard kernel library.An Eiffel source checker and compiler front-end is available.Latest version: 4.2, as of 1998-10-28.Latest version: ISE Eiffel version 3.3.See also Sather, Distributed Eiffel, Lace, shelf.E-mail: .[Eiffel: The Language, Bertrand Meyer, P-H 1992]. (1998-11-15)

Enterprise Resource Planning "application, business" (ERP) Any {software} system designed to support and automate the business processes of medium and large businesses. This may include manufacturing, distribution, personnel, project management, payroll, and financials. ERP systems are accounting-oriented information systems for identifying and planning the {enterprise}-wide resources needed to take, make, distribute, and account for customer orders. ERP systems were originally extensions of {MRP II} systems, but have since widened their scope. An ERP system also differs from the typical MRP II system in technical requirements such as {relational database}, use of {object oriented programming} language, {computer aided software engineering} tools in development, {client/server} {architecture}, and {open system} {portability}. {JBOPS} are the major producers of ERP software. {"ERP Systems - Using IT to gain a competitive advantage", Shankarnarayanan S. (http://expressindia.com/newads/bsl/advant.htm)}. (1999-07-27)

Enterprise Resource Planning ::: (application, business) (ERP) Any software system designed to support and automate the business processes of medium and large businesses. This may include manufacturing, distribution, personnel, project management, payroll, and financials.ERP systems are accounting-oriented information systems for identifying and planning the enterprise-wide resources needed to take, make, distribute, and of object oriented programming language, computer aided software engineering tools in development, client/server architecture, and open system portability.JBOPS are the major producers of ERP software. ERP Systems - Using IT to gain a competitive advantage, Shankarnarayanan S. . (1999-07-27)

ESML ::: Extended Systems Modelling Language: a real-time software engineering methodology based on RTSA.

Extended Systems Modelling Language "language" (ESML) A {real-time} software engineering methodology based on {RTSA}. (2009-05-11)

frame language ::: A technology used for knowledge representation in artificial intelligence. Frames are stored as ontologies of sets and subsets of the frame concepts. They are similar to class hierarchies in object-oriented languages although their fundamental design goals are different. Frames are focused on explicit and intuitive representation of knowledge whereas objects focus on encapsulation and information hiding. Frames originated in AI research and objects primarily in software engineering. However, in practice the techniques and capabilities of frame and object-oriented languages overlap significantly.

GEI ::: A German software engineering company.

GEI A German software engineering company.

GRAS ::: A public domain graph-oriented database system for software engineering applications from RWTH Aachen.

GRAS A {public domain} {graph-oriented database} system for {software engineering} applications from {RWTH Aachen}.

GRASPIN ::: An Esprit project to develop a personal software engineering environment to support the construction and verification of distributed and non-sequential software systems.

GRASPIN An Esprit project to develop a personal software engineering environment to support the construction and verification of distributed and non-sequential software systems.

ICONIX Software Engineering, Inc. ::: (company) Makers of ICONIX PowerTools, software development tools, and the first CD-ROM training course in object-oriented methods. ICONIX started operating in 1984. .Address: 2800 28th Street, Suite 320, Santa Monica, CA 90405, USA. Telephone: +1 (310) 458 0092 (1995-04-30)

ICONIX Software Engineering, Inc. "company" Makers of {ICONIX PowerTools}, software development tools, and the first {CD-ROM} training course in {object-oriented} methods. ICONIX started operating in 1984. {(http://biap.com/iconix/)}. Address: 2800 28th Street, Suite 320, Santa Monica, CA 90405, USA. Telephone: +1 (310) 458 0092 (1995-04-30)

Imperial Software Technology "company" A {software engineering} company which emerged from {Imperial College} in about 1982. It enjoys a world-wide reputation for technical excellence as a software product and technology provider in the Open Systems market. Its flagship product is {X-Designer}, the award-winning {graphical user interface builder}. It also has considerable expertise in the {Z} language and {Formal Methods}. {(http://ist.co.uk/)}. (1995-11-23)

Imperial Software Technology ::: (company) A software engineering company which emerged from Imperial College in about 1982. It enjoys a world-wide reputation for technical interface builder. It also has considerable expertise in the Z language and Formal Methods. . (1995-11-23)

Information Systems Factory (ISF) An equivalent to an {SEE}. [{Simultaneous Engineering Environment} or {Software Engineering Environment}?] (2000-12-30)

Information Systems Factory ::: (ISF) An equivalent to an SEE.[Simultaneous Engineering Environment or Software Engineering Environment?](2000-12-30)

Integrated Project Support Environment "software" (IPSE) A set of management and technical tools to support software development, usually integrated in a coherent framework, equivalent to a {Software Engineering Environment}. (1999-04-26)

Integrated Project Support Environment ::: (software) (IPSE) A set of management and technical tools to support software development, usually integrated in a coherent framework, equivalent to a Software Engineering Environment. (1999-04-26)

Interactive Software Engineering ::: (company) (ISE) The company set up by Bertrand Meyer, now its president, to develop and distribute Eiffel, the language which he created. ISE also organises the TOOLS conference (Technology of Object-Oriented Languages and Systems). .E-mail: Telephone: +1 (805) 685 1006.Address: Santa Barbara, Goleta CA, USA. (1995-12-28)

Interactive Software Engineering "company" (ISE) The company set up by {Bertrand Meyer}, now its president, to develop and distribute {Eiffel}, the language which he created. ISE also organises the {TOOLS} conference (Technology of Object-Oriented Languages and Systems). {(http://eiffel.com/)}. E-mail: info@eiffel.com. Telephone: +1 (805) 685 1006. Address: Santa Barbara, Goleta CA, USA. (1995-12-28)

Interactive Development Environments "company" (IDE) A US {software engineering} company. (1996-03-04)

Interactive Development Environments ::: (company) (IDE) A US software engineering company. (1996-03-04)

ISEE ::: Integrated Software Engineering Environment - equivalent to SEE.

ISEE Integrated {Software Engineering Environment} - equivalent to {SEE}.

ISE {Interactive Software Engineering}

magic bullet "jargon" (Or "silver bullet" from vampire legends) A term widely used in software engineering for a supposed quick, simple cure for some problem. E.g. "There's no silver bullet for this problem". (1999-01-13)

magic bullet ::: (jargon) (Or silver bullet from vampire legends) A term widely used in software engineering for a supposed quick, simple cure for some problem. E.g. There's no silver bullet for this problem. (1999-01-13)

maintenance "programming" The modification of a software product, after delivery, to correct faults, to improve performance or other attributes, or to adapt the product to a changed environment. Maintenance is an important part of the {software life-cycle}. It is expensive in manpower and resources, and one of the aims of {software engineering} is to reduce its cost. (1996-12-27)

maintenance ::: (programming) The modification of a software product, after delivery, to correct faults, to improve performance or other attributes, or to adapt the product to a changed environment.Maintenance is an important part of the software life-cycle. It is expensive in manpower and resources, and one of the aims of software engineering is to reduce its cost. (1996-12-27)

Margaret Hamilton "person" (born 1936-08-17) A {computer scientist}, {systems engineer} and business owner, credited with coining the term {software engineering}. Margaret Hamilton published over 130 papers, proceedings and reports about the 60 projects and six major programs in which she has been involved. In 1965 she became Director of Software Programming at MIT's {Charles Stark Draper Laboratory} and Director of the Software Engineering Division of the {MIT Instrumentation Laboratory}, which developed on-board {flight software} for the Apollo space program. At {NASA}, Hamilton pioneered the Apollo on-board guidance software that navigated to and landed on the Moon and formed the basis for software used in later missions. At the time, programming was a hands-on, engineering descipline; computer science and software engineering barely existed. Hamilton produced innovations in {system design} and software development, enterprise and {process modelling}, development paradigms, {formal systems modelling languages}, system-oriented objects for systems modelling and development, {automated life-cycle environments}, {software reliability}, {software reuse}, {domain analysis}, correctness by built-in language properties, open architecture techniques for robust systems, full {life-cycle automation}, {quality assurance}, {seamless integration}, {error detection and recovery}, {man-machine interface} systems, {operating systems}, {end-to-end testing} and {life-cycle management}. She developed concepts of {asynchronous software}, {priority scheduling} and {Human-in-the-loop} decision capability, which became the foundation for modern, ultra-reliable software design. The Apollo 11 moon landing would have aborted when spurious data threatened to overload the computer, but thanks to the innovative asynchronous, priority based scheduling, it eliminated the unnecessary processing and completed the landing successfully. In 1986, she founded {Hamilton Technologies, Inc.}, developed around the {Universal Systems Language} and her systems and software design {paradigm} of {Development Before the Fact} (DBTF). (2015-03-08)

MERISE ::: Methode d'Etude et de Realisation Informatique pour les Systemes d'Enteprise.A software engineering method popular in France; many IPSEs are based on it. (1995-01-24)

MERISE Methode d'Etude et de Realisation Informatique pour les Systemes d'Enteprise. A software engineering method popular in France; many {IPSEs} are based on it. (1995-01-24)

MSG.84 "language" A language for the {functional specification} and module design phases of the {software life cycle}, first presented in Berzins and Gray's 1985 paper. Not unlike {PDL}. ["Analysis and design in MSG.84: formalizing functional specifications", Valdis Berzins, Michael Gray, Volume 11 Issue 8, IEEE Transactions on Software Engineering, Aug 1985]. (2003-05-15)

MSG.84 ::: (language) A language for the functional specification and module design phases of the software life cycle, first presented in Berzins and Gray's 1985 paper. Not unlike PDL.[Analysis and design in MSG.84: formalizing functional specifications, Valdis Berzins, Michael Gray, Volume 11 Issue 8, IEEE Transactions on Software Engineering, Aug 1985].(2003-05-15)

Neptune ::: A hypertext system for computer assisted software engineering, developed at Tektronix.

Neptune A hypertext system for computer assisted software engineering, developed at Tektronix.

Pansophic ::: A US Software Engineering company.

Pansophic A US Software Engineering company.

RAISE {Rigorous Approach to Industrial Software Engineering}

RAISE Specification Language "language" (RSL) (RAISE = Rigorous Approach to Industrial Software Engineering). A wide-spectrum specification and design language developed by {ESPRIT} Project 315 at {CRI} A/S, Denmark. Systems may be modular, {concurrent} and {nondeterministic}. Specifications may be {applicative} or {imperative}, explicit or implicit, abstract or concrete. ["The RAISE Specification Language", RAISE Language Group, P-H 1992, ISBN 0-13-752833-7]. (2007-10-02)

RSL ::: RAISE Specification Language. (RAISE = Rigorous Approach to Industrial Software Engineering). A wide-spectrum specification and design language developed by nondeterministic. Specifications may be applicative or imperative, explicit or implicit, abstract or concrete.[The RAISE Specification Language, RAISE Language Group, P-H 1992, ISBN 0-13-752833-7].

SE ::: 1. (software) software engineering.2. IBM Systems Engineer. (1998-07-08)

SE 1. "software" {software engineering}. 2. {IBM Systems Engineer}. (1998-07-08)

SEE ::: 1. Simultaneous Engineering Environment.2. Software Engineering Environment. (1999-04-26)

SEE 1. {Simultaneous Engineering Environment}. 2. {Software Engineering Environment}. (1999-04-26)

SEI ::: Software Engineering Institute.(Carnegie Mellon University).

SEI Software Engineering Institute. (Carnegie Mellon University).

Softlab "company" A {software engineering} company strong in the UK and Germany. [Details?]

Softlab ::: (company) A software engineering company strong in the UK and Germany.[Details?]

software ::: A collection of data or computer instructions that tell the computer how to work. This is in contrast to physical hardware, from which the system is built and actually performs the work. In computer science and software engineering, computer software is all information processed by computer systems, programs and data. Computer software includes computer programs, libraries and related non-executable data, such as online documentation or digital media.

Software AG "company" A German {software engineering} company that started with the {ADABAS} {database}. {Natural} is their {4GL} development environment, {EntireX} is their {DCOM} for {Unix} and {IBM}. {BOLERO}, is an {object-oriented} development environment and {application server} specially made for Electronic Business applications. {(http://softwareag.com/)}. Mailing-list: "sag-l@uafsysb.uark.edu". (1999-03-06)

Software AG ::: (company) A German software engineering company that started with the ADABAS database. Natural is their 4GL development environment, EntireX is their DCOM for Unix and IBM. BOLERO, is an object-oriented development environment and application server specially made for Electronic Business applications. .Mailing-list: . (1999-03-06)

software engineering "programming" (SE) A systematic approach to the analysis, design, implementation and maintenance of {software}. It often involves the use of {CASE} tools. There are various models of the {software life-cycle}, and many {methodologies} for the different phases. (1994-11-03)

software engineering ::: (programming) (SE) A systematic approach to the analysis, design, implementation and maintenance of software. It often involves the use of CASE tools. There are various models of the software life-cycle, and many methodologies for the different phases. (1994-11-03)

software engineering ::: The application of engineering to the development of software in a systematic method.[285][286][287]

Software Productivity Centre "body" (SPC) A non-profit organisation based in Vancouver, BC, Canada with the mandate to assist software developers to improve their {software engineering} process. (1998-10-13)

Software Productivity Centre ::: (body) (SPC) A non-profit organisation based in Vancouver, BC, Canada with the mandate to assist software developers to improve their software engineering process. (1998-10-13)

spiral model "programming" A {software life-cycle} model which supposes incremental development, using the {waterfall model} for each step, with the aim of managing risk. In the spiral model, developers define and implement features in order of decreasing priority. [Barry Boehm, "A Spiral Model of Software Development and Enhancement", ACM SIGSOFT Software Engineering Notes, August 1986]. [Barry Boehm "A Spiral Model of Software Development and Enhancement" IEEE Computer, vol.21,

spiral model ::: (programming) A software life-cycle model which supposes incremental development, using the waterfall model for each step, with the aim of managing risk. In the spiral model, developers define and implement features in order of decreasing priority.[Barry Boehm, A Spiral Model of Software Development and Enhancement, ACM SIGSOFT Software Engineering Notes, August 1986].[Barry Boehm A Spiral Model of Software Development and Enhancement IEEE Computer, vol.21,

SSADM ::: A software engineering method and toolset required by some UK government agencies.

SSADM A software engineering method and toolset required by some UK government agencies.

structured analysis ::: One of a number of requirements analysis methods used in software engineering.

structured analysis One of a number of requirements analysis methods used in software engineering.

structured design "programming" (SD) One of a number of systematic {top-down design} techniques used in {software engineering}, usually after {structured analysis}. (1995-04-28)

structured design ::: (programming) (SD) One of a number of systematic top-down design techniques used in software engineering, usually after structured analysis. (1995-04-28)

Technology of Object-Oriented Languages and Systems "event" (TOOLS) One of the oldest {object-oriented} conferences, with 18 published proceedings volumes. TOOLS is organised by {Interactive Software Engineering}. (1995-12-29)

Technology of Object-Oriented Languages and Systems ::: (event) (TOOLS) One of the oldest object-oriented conferences, with 18 published proceedings volumes. TOOLS is organised by Interactive Software Engineering. (1995-12-29)

The Mythical Man-Month "publication" Fred Brooks's excellent 1975 book on {software engineering}. See also {Brooks's Law}. ["The Mythical Man-Month: Essays on Software Engineering", Fred Brooks, Addison-Wesley, 1975, ISBN 0-201-00650-2]. (1996-06-20)

The Mythical Man-Month ::: (publication) Fred Brooks's excellent 1975 book on software engineering.See also Brooks's Law.[The Mythical Man-Month: Essays on Software Engineering, Fred Brooks, Addison-Wesley, 1975, ISBN 0-201-00650-2]. (1996-06-20)

Tool Builder Kit "tool" (TBK) A product from {IPSYS} which allows users to develop {CASE} tools appropriate to any {software engineering} {methodology}. (1996-05-08)

Tool Builder Kit ::: (tool) (TBK) A product from IPSYS which allows users to develop CASE tools appropriate to any software engineering methodology. (1996-05-08)

Tree Transformation Language ::: (functional language, rule-based language) (TXL) A hybrid functional language and rule-based language developed by J.R. Cordy rapidly prototyping new languages and language processors. It uses structural transformation based on term rewriting.TXL has been particularly successful in software engineering tasks such as design recovery, refactoring, and reengineering. Most recently it has been applied to artificial intelligence tasks such as recognition of hand-written mathematics, and to transformation of structured documents in XML.TXL takes as input an arbitrary context-free grammar in extended BNF-like notation, and a set of show-by-example transformation rules to be applied to inputs parsed using the grammar. TXL supports the notion of agile parsing, the ability to tailor the grammar to each particular task using grammar overrides.Current version: FreeTXL 10.3, as of 2003-10-26. .[TXL: A Rapid Prototyping System for Programming Language Dialects, J.R. Cordy, C.D.; Halpern and D. Promislow, Computer Languages, Vol. 16, No. 1, January 1991, pp 97-107][Source Transformation in Software Engineering using the TXL Transformation System, J.R. Cordy, T.R. Dean, A.J. Malton and K.A. Schneider, Journal of Information and Software Technology, Vol. 44, No. 13, October 2002, pp 827-837][Recognizing Mathematical Expressions Using Tree Transformation, R. Zanibbi, D. Blostein and J.R. Cordy, IEEE Transactions on Pattern Analysis & Machine Intelligence, Vol. 24, No. 11, November 2002, pp 1455-1467][Agile Parsing in TXL, T.R. Dean, J.R. Cordy, A.J. Malton and K.A. Schneider, Journal of Automated Software Engineering, Vol. 10, No. 4, October 2003, pp 311-336](2003-11-04)

Tree Transformation Language "functional programming" (TXL) A hybrid {functional language} and {rule-based language} developed by J.R. Cordy "cordy@cs.queensu.ca" et al of {Queen's University}, Canada in 1988. TXL is suitable for performing {source to source analysis} and transformation and for {rapid prototyping} of new languages and language processors. It uses {structural transformation} based on {term rewriting}. TXL has been particularly successful in {software engineering} tasks such as {design recovery}, {refactoring}, and {reengineering}. Most recently it has been applied to {artificial intelligence} tasks such as recognition of hand-written mathematics, and to transformation of {structured documents} in {XML}. TXL takes as input an arbitrary {context-free grammar} in {extended BNF}-like notation, and a set of {show-by-example} transformation rules to be applied to inputs {parsed} using the grammar. TXL supports the notion of {agile parsing}, the ability to tailor the grammar to each particular task using "grammar overrides". {TXL Home (http://txl.ca/)}. ["TXL: A Rapid Prototyping System for Programming Language Dialects", J.R. Cordy, C.D.; Halpern and D. Promislow, Computer Languages, Vol. 16, No. 1, January 1991, pp 97-107] ["Source Transformation in Software Engineering using the TXL Transformation System", J.R. Cordy, T.R. Dean, A.J. Malton and K.A. Schneider, Journal of Information and Software Technology, Vol. 44, No. 13, October 2002, pp 827-837] ["Recognizing Mathematical Expressions Using Tree Transformation", R. Zanibbi, D. Blostein and J.R. Cordy, IEEE Transactions on Pattern Analysis & Machine Intelligence, Vol. 24, No. 11, November 2002, pp 1455-1467] ["Agile Parsing in TXL", T.R. Dean, J.R. Cordy, A.J. Malton and K.A. Schneider, Journal of Automated Software Engineering, Vol. 10, No. 4, October 2003, pp 311-336] (2003-11-04)

Verilog SA "company" A French {real-time software engineering} company. (1999-04-16)

Verilog SA ::: (company) A French real-time software engineering company. (1999-04-16)

ViewPoints ::: (programming) A framework for distributed and concurrent software engineering which provides an alternative approach to traditional centralised software development environments.Decentralised process models are used to drive consistency checking and conflict resolution. The process models use pattern matching on local development Communication between such process models facilitates the decentralised management of explicitly defined consistency constraints.[Ulf Leonhardt] (1995-03-27)

ViewPoints "programming" A framework for distributed and {concurrent} software engineering which provides an alternative approach to traditional centralised software development environments. Decentralised process models are used to drive consistency checking and conflict resolution. The process models use pattern matching on local development histories to determine the particular state of the development process, and employ rules to trigger situation-dependent assistance to the user. Communication between such process models facilitates the decentralised management of explicitly defined consistency constraints. [Ulf Leonhardt] (1995-03-27)

Virtual Software Factory "programming, tool" (VSF) A product from {Systematica} which allows users to develop {CASE} tools appropriate to any software engineering methodology. (1997-06-09)

Virtual Software Factory ::: (programming, tool) (VSF) A product from Systematica which allows users to develop CASE tools appropriate to any software engineering methodology. (1997-06-09)

Westmount "company" A Dutch software engineering vendor of {RTEE} and other products. (1998-04-27)

Westmount ::: (company) A Dutch software engineering vendor of RTEE and other products. (1998-04-27)

Yourdon, Inc. ::: (company) The company founded in 1974 by Edward Yourdon to provide educational, publishing, and consulting services in state-of-the-art software computer books on a wide range of software engineering topics; many of these classics are used as standard university computer science textbooks. (1995-04-16)

Yourdon, Inc. "company" The company founded in 1974 by {Edward Yourdon} to provide educational, publishing, and consulting services in state-of-the-art software engineering technology. Over the next 12 years, the company grew to a staff of over 150 people, with offices throughout North America and Europe. As CEO of the company, Yourdon oversaw an operation that trained over 250,000 people around the world; the company was sold in 1986 and eventually became part of {CGI}, the French software company that is now part of {IBM}. The publishing division, Yourdon Press (now part of Prentice Hall), has produced over 150 technical computer books on a wide range of software engineering topics; many of these "classics" are used as standard university computer science textbooks. (1995-04-16)

Yourdon methodology "programming" The {software engineering} {methodology} developed by {Edward Yourdon} and colleagues in the 1970s and 1980s. "Yourdon methodology" is a generic term for all of the following methodologies: {Yourdon/Demarco}, {Yourdon/Constantine}, {Coad/Yourdon}. (1995-04-07)

Yourdon methodology ::: (programming) The software engineering methodology developed by Edward Yourdon and colleagues in the 1970s and 1980s. Yourdon methodology is a generic term for all of the following methodologies: Yourdon/Demarco, Yourdon/Constantine, Coad/Yourdon. (1995-04-07)



QUOTES [0 / 0 - 30 / 30]


KEYS (10k)


NEW FULL DB (2.4M)

   4 Frederick P Brooks Jr
   2 Steve McConnell
   2 Friedrich L Bauer
   2 Edsger Dijkstra
   2 David J Anderson
   2 Betsy Beyer
   2 Anonymous

*** WISDOM TROVE ***

*** NEWFULLDB 2.4M ***

1:Software engineering economics. ~ Barry Boehm,
2:Code reuse is the Holy Grail of Software Engineering. ~ Douglas Crockford,
3:Software engineering is not about right and wrong but only better and worse ~ Ellen Ullman,
4:The purpose of software engineering is to control complexity, not to create it. ~ Jon L Bentley,
5:Never in the annals of software engineering was so much owed by so many to so few lines of code ~ Martin Fowler,
6:Software Engineering might be science; but that's not what I do. I'm a hacker, not an engineer. ~ Jamie Zawinski,
7:Software Engineering is that part of Computer Science which is too difficult for the Computer Scientist. ~ Friedrich L Bauer,
8:[Dea07] J. Dean, “Software Engineering Advice from Building Large-Scale Distributed Systems”, Stanford CS297 class lecture, Spring 2007. ~ Betsy Beyer,
9:Software engineering is the establishment and use of sound engineering principles to obtain economically software that is reliable and works on real machines efficiently. ~ Friedrich L Bauer,
10:Software engineering has this in common with having children: the labor before the birth is painful and difficult, but the labor after the birth is where you actually spend most of your effort. Yet ~ Betsy Beyer,
11:The gap between the best software engineering practice and the average practice is very wide—perhaps wider than in any other engineering discipline. A tool that disseminates good practice would be important. — Fred Brooks ~ Steve McConnell,
12:Building on our successful partnership, we can now bring together the best of Microsoft's software engineering with the best of Nokia's product engineering, award-winning design, and global sales, marketing and manufacturing. ~ Stephen Elop,
13:To make an embarrassing admission, I like video games. That's what got me into software engineering when I was a kid. I wanted to make money so I could buy a better computer to play better video games. Nothing like saving the world. ~ Elon Musk,
14:Software engineering is the part of computer science which is too difficult for the computer scientist. ~ Friedrich Bauer, "Software Engineering." Information Processing: Proceedings of the IFIP Congress 1971, Ljubljana, Yugoslavia, August 23-28, 1971.,
15:software engineering is very much governed by human behavior through the people developing software. Thus, we cannot expect to find any formal rules or laws in software engineering except perhaps when focusing on specific technical aspects. ~ Anonymous,
16:By claiming that they can contribute to software engineering, the soft scientists make themselves even more ridiculous. (Not less dangerous, alas!) In spite of its name, software engineering requires (cruelly) hard science for its support. ~ Edsger W Dijkstra,
17:However, a real implementation may still have to include code to handle the case where something happens that was assumed to be impossible, even if that handling boils down to printf("Sucks to be you") and exit(666) — i.e., letting a human operator clean up the mess [93]. (This is arguably the difference between computer science and software engineering.) ~ Martin Kleppmann,
18:The required techniques of effective reasoning are pretty formal, but as long as programming is done by people that don't master them, the software crisis will remain with us and will be considered an incurable disease. And you know what incurable diseases do: they invite the quacks and charlatans in, who in this case take the form of Software Engineering gurus. ~ Edsger Dijkstra,
19:… what society overwhelmingly asks for is snake oil. Of course, the snake oil has the most impressive names — otherwise you would be selling nothing — like “Structured Analysis and Design”, “Software Engineering”, “Maturity Models”, “Management Information Systems”, “Integrated Project Support Environments” “Object Orientation” and “Business Process Re-engineering”. ~ Edsger Dijkstra,
20:The first step toward the management of disease was replacement of demon theories and humours theories by the germ theory. That very step, the beginning of hope, in itself dashed all hopes of magical solutions. It told workers that progress would be made stepwise, at great effort, and that a persistent, unremitting care would have to be paid to a discipline of cleanliness. So it is with software engineering today. ~ Fred Brooks,
21:In general, software engineering teams and IT departments seemed to be at the mercy of other groups who would negotiate, cajole, intimidate, and overrule even the most defensible and objectively derived plans. Even plans based on thorough analysis and backed by years of historical data were vulnerable. Most teams, which had neither a thorough analysis method nor any historical data, were powerless at the hands of others who would push them to commit to unknown (and often completely unreasonable) deliverables. ~ David J Anderson,
22:We will actively manage this technical debt by ensuring that we invest at least 20% of all Development and Operations cycles on refactoring, investing in automation work and architecture and non-functional requirements (NFRs, sometimes referred to as the “ilities”), such as maintainability, manageability, scalability, reliability, testability, deployability, and security. Figure 11: Invest 20% of cycles on those that create positive, user-invisible value (Source: “Machine Learning and Technical Debt with D. Sculley,” Software Engineering Daily podcast, November 17, 2015, ~ Gene Kim,
23:NASA's Software Engineering Laboratory studied ten projects that pursued reuse aggressively (McGarry, Waligora, and McDermott 1989). In both the object-oriented and the functionally oriented approaches, the initial projects weren't able to take much of their code from previous projects because previous projects hadn't established a sufficient code base. Subsequently, the projects that used functional design were able to take about 35 percent of their code from previous projects. Projects that used an object-oriented approach were able to take more than 70 percent of their code from previous projects. If you can avoid writing 70 percent of your code by planning ahead, do it! ~ Steve McConnell,
24:Today I am more convinced than ever. Conceptual integrity is central to product quality. Having a system architect is the most important single step toward conceptual integrity. These principles are by no means limited to software systems, but to the design of any complex construct, whether a computer, an airplane, a Strategic Defense Initiative, a Global Positioning System. After teaching a software engineering laboratory more than 20 times, I came to insist that student teams as small as four people choose a manager and a separate architect. Defining distinct roles in such small teams may be a little extreme, but I have observed it to work well and to contribute to design success even for small teams. ~ Frederick P Brooks Jr,
25:Improve performance through process improvements introduced with minimal resistance. Deliver with high quality. Deliver a predictable lead time by controlling the quantity of work-in-progress. Give team members a better life through an improved work/life balance. Provide slack in the system by balancing demand against throughput. Provide a simple prioritization mechanism that delays commitment and keeps options open. Provide a transparent scheme for seeing improvement opportunities, thereby enabling change to a more collaborative culture that encourages continuous improvement. Strive for a process that enables predictable results, business agility, good governance, and the development of what the Software Engineering Institute calls a high-maturity organization. ~ David J Anderson,
26:As an author writing about software engineering, I am committed to providing the best grounding for any factual claims I make or support. To that end I will: only cite papers that I have in fact personally read refrain from indirect quotation (or other ‘telephone game’ variants) make it clear whenever I’m citing opinion or indirect quotation, as opposed to original research cite page and section numbers when available, and always when citing books whenever possible, cite papers freely available online in full text versions refrain from citing obscure or non peer-reviewed sources check that the data I’m citing actually supports the claim look for contradictory evidence as well as supporting, to avoid confirmation bias only make prudent claims, and present all plausible threats to validity. ~ Anonymous,
27:Even at a cost of $100,000, a purchased piece of software is costing only about as much as one programmer-year. And delivery is immediate! Immediate at least for products that really exist, products whose developer can refer the prospect to a happy user. Moreover, such products tend to be much better documented and somewhat better maintained than homegrown software. The development of the mass market is, I believe, the most profound long-run trend in software engineering. The cost of software has always been development cost, not replication cost. Sharing that cost among even a few users radically cuts the per-user cost. Another way of looking at it is that the use of n copies of a software system effectively multiplies the productivity of its developers by n. That is an enhancement of the productivity of the discipline and of the nation. ~ Frederick P Brooks Jr,
28:Hiro and Y.T. have eaten a lot of junk food together in different joints all
over L.A. -- doughnuts, burritos, pizza, sushi, you name it -- and all Y.T. ever
talks about is her mother and the terrible job that she has with the Feds. The
regimentation. The lie-detector tests. The fact that for all the work she
does, she really has no idea what it is that the government is really working
on.
It's always been a mystery to Hiro, too, but then, that's how the government is.
It was invented to do stuff that private enterprise doesn't bother with, which
means that there's probably no reason for it; you never know what they're doing
or why. Hackers have traditionally looked upon the government's coding
sweatshops with horror and just tried to forget that all of that shit ever
existed.
But they have thousands of programmers. The programmers work twelve hours a day
out of some twisted sense of personal loyalty. Their software-engineering
techniques, while cruel and ugly, are very sophisticated. They must have been
up to something. ~ Neal Stephenson,
29:This really does attack essence. Because the build-on-package phenomenon does not today affect the average MIS programmer, it is not yet very visible to the software engineering discipline. Nevertheless, it will grow rapidly, because it does attack the essence of fashioning conceptual constructs. The shrink-wrapped package provides a big module of function, with an elaborate but proper interface, and its internal conceptual structure does not have to be designed at all. High-function software products such as Excel or 4th Dimension are big modules indeed, but they serve as known, documented, tested modules with which to build customized systems. Next-level application builders get richness of function, a shorter development time, a tested component, better documentation, and radically lower cost. The difficulty, of course, is that the shrink-wrapped software package is designed as a stand-alone entity whose functions and interfaces metaprogrammers cannot change. Moreover, and more seriously, shrink-wrapped package builders seemingly have little incentive to make their products suitable as modules in a larger system. I ~ Frederick P Brooks Jr,
30:If, as I believe, the conceptual structures we construct today are too complicated to be accurately specified in advance, and too complex to be built faultlessly, then we must take a radically different approach. Let us turn to nature and study complexity in living things, instead of just the dead works of man. Here we find constructs whose complexities thrill us with awe. The brain alone is intricate beyond mapping, powerful beyond imitation, rich in diversity, self-protecting, and self-renewing. The secret is that it is grown, not built. So it must be with our software systems. Some years ago Harlan Mills proposed that any software system should be grown by incremental development.[11] That is, the system should first be made to run, even though it does nothing useful except call the proper set of dummy subprograms. Then, bit by bit it is fleshed out, with the subprograms in turn being developed into actions or calls to empty stubs in the level below. I have seen the most dramatic results since I began urging this technique on the project builders in my software engineering laboratory class. Nothing in the past decade has so radically changed my own practice, or its effectiveness. The approach necessitates top-down design, for it is a top-down growing of the software. It allows easy backtracking. It lends itself to early prototypes. Each added function and new provision for more complex data or circumstances grows organically out of what is already there. The morale effects are startling. Enthusiasm jumps when there is a running system, even a simple one. Efforts redouble when the first picture from a new graphics software system appears on the screen, even if it is only a rectangle. One always has, at every stage in the process, a working system. I find that teams can grow much more complex entities in four months than they can build. ~ Frederick P Brooks Jr,

IN CHAPTERS [0/0]









WORDNET














IN WEBGEN [10000/107]

Wikipedia - Abstraction (software engineering)
Wikipedia - Bachelor of Software Engineering
Wikipedia - Birgit Penzenstadler -- German software engineering professor
Wikipedia - Category:Software engineering folklore
Wikipedia - Category:Software engineering papers
Wikipedia - Category:Software engineering researchers
Wikipedia - Category:Software engineering
Wikipedia - Cleanroom software engineering
Wikipedia - CMU Software Engineering Institute
Wikipedia - Component-based software engineering
Wikipedia - Computer-Aided Software Engineering
Wikipedia - Computer-aided software engineering
Wikipedia - Critical mass (software engineering) -- Software engineering term; stage in the life cycle when the source code grows too complicated to effectively manage without a complete rewrite
Wikipedia - Domain (software engineering) -- target subject of a computer program
Wikipedia - Draft:Daniel Mendez -- Spanish German software engineering professor
Wikipedia - Edward Yourdon -- American software engineer and pioneer in the software engineering methodology
Wikipedia - Experimental software engineering
Wikipedia - Forensic software engineering
Wikipedia - Fork (software engineering)
Wikipedia - Frame technology (software engineering)
Wikipedia - Freeze (software engineering)
Wikipedia - Fundamental theorem of software engineering -- A general principle for managing complexity through abstraction
Wikipedia - Graphical user interface testing -- Term in software engineering
Wikipedia - History of software engineering
Wikipedia - IEEE Transactions on Software Engineering
Wikipedia - Index of software engineering articles -- Wikipedia index
Wikipedia - Infosys -- Indian multinational consulting, IT services, software engineering and outsourcing company
Wikipedia - Innovations in Systems and Software Engineering
Wikipedia - International Conference on Software Engineering
Wikipedia - List of software engineering conferences
Wikipedia - List of software engineering topics
Wikipedia - Methodology (software engineering)
Wikipedia - NATO Software Engineering Conferences
Wikipedia - Object-oriented software engineering
Wikipedia - Outline of software engineering
Wikipedia - Rands -- blogger, software engineering manager, and webcomic author
Wikipedia - Rigorous Approach to Industrial Software Engineering
Wikipedia - SaleCycle -- Behavioral marketing company, does software engineering
Wikipedia - Search-based software engineering
Wikipedia - Site reliability engineering -- Discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems
Wikipedia - Software Engineering 2004 -- Software engineering curriculum
Wikipedia - Software Engineering Body of Knowledge
Wikipedia - Software Engineering Institute
Wikipedia - Software Engineering Journal
Wikipedia - Software engineering methodologies
Wikipedia - Software engineering methodology
Wikipedia - Software engineering process
Wikipedia - Software engineering professionalism
Wikipedia - Software Engineering Programme
Wikipedia - Software Engineering
Wikipedia - Software engineering -- Branch of computing science
Wikipedia - Software engineer -- Practitioner of software engineering
Wikipedia - Software quality assurance -- Means of monitoring the software engineering process
Wikipedia - Template talk:Software engineering
Wikipedia - Ubiquitous computing -- Concept in software engineering and computer science
Wikipedia - Watts Humphrey -- American pioneer in software engineering
Wikipedia - White box (software engineering) -- System whose internals can be viewed but not altered
https://www.goodreads.com/book/show/10232146-generative-and-transformational-techniques-in-software-engineering-iii
https://www.goodreads.com/book/show/142789.Agile_Management_for_Software_Engineering
https://www.goodreads.com/book/show/17127733-generative-and-transformational-techniques-in-software-engineering-iv
https://www.goodreads.com/book/show/191913.Creating_a_Software_Engineering_Culture
https://www.goodreads.com/book/show/20865725-generative-and-transformational-techniques-in-software-engineering
https://en.wikiquote.org/wiki/Software_engineering
https://academia.fandom.com/wiki/Journal_of_Computer_Science_and_Software_Engineering
https://cities.fandom.com/wiki/Pittsburgh:Software_Engineering_Institute
https://engineering.fandom.com/wiki/Software_engineering
https://engineering.fandom.com/wiki/Software_engineering_topics
ACM Transactions on Software Engineering and Methodology
Agent-oriented software engineering
Australian Software Engineering Conference
Bachelor of Software Engineering
Bisection (software engineering)
Brownout (software engineering)
Cleanroom software engineering
Component-based software engineering
Computer-aided software engineering
Conference on Software Engineering Education and Training
Cost estimation in software engineering
Critical mass (software engineering)
E-Informatica Software Engineering Journal
Empirical Software Engineering Journal
European Master on Software Engineering
Experimental software engineering
Frame technology (software engineering)
Freeze (software engineering)
History of software engineering
IEEE Transactions on Software Engineering
Index of software engineering articles
Innovations in Systems and Software Engineering
International Conference on Software Engineering and Formal Methods
International Journal of Software Engineering and Knowledge Engineering
Lero (software engineering)
Outline of software engineering
Rigorous Approach to Industrial Software Engineering
Search-based software engineering
Service-oriented software engineering
Social software engineering
Software engineering
Software Engineering 2004
Software Engineering Body of Knowledge
Software engineering demographics
Software Engineering for Adaptive and Self-Managing Systems
Software Engineering Institute
Software Engineering Notes
Software Engineering Process Group
Software engineering professionalism
White box (software engineering)



convenience portal:
recent: Section Maps - index table - favorites
Savitri -- Savitri extended toc
Savitri Section Map -- 1 2 3 4 5 6 7 8 9 10 11 12
authors -- Crowley - Peterson - Borges - Wilber - Teresa - Aurobindo - Ramakrishna - Maharshi - Mother
places -- Garden - Inf. Art Gallery - Inf. Building - Inf. Library - Labyrinth - Library - School - Temple - Tower - Tower of MEM
powers -- Aspiration - Beauty - Concentration - Effort - Faith - Force - Grace - inspiration - Presence - Purity - Sincerity - surrender
difficulties -- cowardice - depres. - distract. - distress - dryness - evil - fear - forget - habits - impulse - incapacity - irritation - lost - mistakes - obscur. - problem - resist - sadness - self-deception - shame - sin - suffering
practices -- Lucid Dreaming - meditation - project - programming - Prayer - read Savitri - study
subjects -- CS - Cybernetics - Game Dev - Integral Theory - Integral Yoga - Kabbalah - Language - Philosophy - Poetry - Zen
6.01 books -- KC - ABA - Null - Savitri - SA O TAOC - SICP - The Gospel of SRK - TIC - The Library of Babel - TLD - TSOY - TTYODAS - TSZ - WOTM II
8 unsorted / add here -- Always - Everyday - Verbs


change css options:
change font "color":
change "background-color":
change "font-family":
change "padding":
change "table font size":
last updated: 2022-05-07 07:54:47
101709 site hits