Editing History of software engineering (section)

== 2000 to 2015: Lightweight methodologies ==
With the expanding demand for software in many smaller organizations, the need for inexpensive software solutions led to the growth of simpler, faster methodologies that developed running software, from requirements to deployment, quicker & easier.  The use of rapid-prototyping evolved to entire ''lightweight methodologies'', such as [[Extreme Programming]] (XP), which attempted to simplify many areas of software engineering, including requirements gathering and reliability testing for the growing, vast number of small software systems.  Very large software systems still used heavily documented methodologies, with many volumes in the documentation set; however, smaller systems had a simpler, faster alternative approach to managing the development and maintenance of software calculations and algorithms, information storage/retrieval and display.{{citation needed|date=February 2016}}

=== Current trends in software engineering ===
Software engineering is a young discipline, and is still developing. The directions in which software engineering is developing include:{{citation needed|date=February 2016}}

==== Aspects ====
[[Aspect-oriented programming|Aspects]] help software engineers deal with [[quality attributes]] by providing tools to add or remove [[boilerplate code]] from many areas in the [[source code]]. Aspects describe how all objects or functions should behave in particular circumstances. For example, [[aspect (computer science)|aspects]] can add [[debugging]], [[data logging|logging]], or [[lock (computer science)|locking]] control into all objects of particular types. Researchers are currently working to understand how to use aspects to design general-purpose code. Related concepts include [[generative programming]] and [[Template (programming)|templates]].

==== Experimental ====
[[Experimental software engineering]] is a branch of software engineering interested in devising [[experiment]]s on software, in collecting data from the experiments, and in devising laws and theories from this data.

==== Software product lines ====
[[product family engineering|Software product lines, aka product family engineering]], is a systematic way to produce ''families'' of software systems, instead of creating a succession of completely individual products. This method emphasizes extensive, systematic, formal [[code reuse]], to try to industrialize the software development process.

The Future of Software Engineering conference (FOSE), held at ICSE 2000, documented the state of the art of SE in 2000 and listed many problems to be solved over the next decade. The FOSE tracks at the  ICSE 2000 <ref>{{cite web|url=http://www.ul.ie/%7Eicse2000/|title=ICSE2000: Call for Participation|work=ul.ie}}</ref> and the ICSE 2007<ref>{{cite web|url=http://web4.cs.ucl.ac.uk/icse07/|title=ICSE 2007: Home|work=ucl.ac.uk}}</ref> conferences also help identify the state of the art in software engineering.{{citation needed|date=February 2016}}

=== Software engineering today ===
The profession is trying to define its boundary and content. The Software Engineering Body of Knowledge [[SWEBOK]] has been tabled as an ISO standard during 2006 (ISO/IEC TR 19759).{{citation needed|date=February 2016}}

In 2006, ''Money Magazine'' and ''Salary.com'' rated software engineering as the best job in America in terms of growth, pay, stress levels, flexibility in hours and working environment, creativity, and how easy it is to enter and advance in the field.<ref>{{cite web
 | last = Kalwarski
 | first = Tara |author2=Daphne Mosher |author3=Janet Paskin |author4=Donna Rosato |author4-link=Donna Rosato | year = 2006
 | url = https://money.cnn.com/magazines/moneymag/bestjobs/2006/
 | title = Best Jobs in America
 | work = MONEY Magazine
 | publisher = CNN
 | access-date = 2006-04-20
}}, "MONEY Magazine and Salary.com researched hundreds of jobs, considering their growth, pay, stress-levels and other factors. These careers ranked highest. 1. Software Engineer..."</ref>