Lightweight methodology
Encyclopedia
A lightweight methodology is a software development methodology
which has only a few rules and practices or ones which are easy to follow. In contrast, a complex methodology with many rules is considered a "heavyweight methodology".
Some examples of lightweight methodologies are:
Most of these lightweight processes emphasize the need to deal with change in requirements and change in environment or technology by being flexible and adaptive.
Software development methodology
A software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system.- History :...
which has only a few rules and practices or ones which are easy to follow. In contrast, a complex methodology with many rules is considered a "heavyweight methodology".
Some examples of lightweight methodologies are:
- Adaptive Software DevelopmentAdaptive Software DevelopmentAdaptive Software Development is a software development process that grew out of rapid application development work by Jim Highsmith and Sam Bayer...
by Jim HighsmithJim HighsmithJames A. Highsmith III is an American software engineer and author of books in the field of software development methodology. He is the creator of Adaptive Software Development, described in his 1999 book "Adaptive Software Development", and winner of the 2000 Jolt Award, and the Stevens Award in...
described in his 1999 book "Adaptive Software Development" - Crystal ClearCrystal Clear (software development)Crystal Clear is a member of the Crystal family of methodologies as described by Alistair Cockburn and is considered an example of an agile or lightweight methodology....
family of methodologies with Alistair CockburnAlistair CockburnAlistair Cockburn is one of the initiators of the agile movement in software development, helping write theManifesto for Agile Software Development in 2001 and the agile PM Declaration of Interdependence in 2005...
, - Extreme ProgrammingExtreme ProgrammingExtreme programming is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements...
(XP) promoted by people such as Kent BeckKent BeckKent Beck is an American software engineer and the creator of the Extreme Programming and Test Driven Development software development methodologies. Beck was one of the 17 original signatories of the Agile Manifesto in 2001....
and Martin FowlerMartin Fowler-Online presentations:* at RailsConf 2006* at JAOO 2006* at QCon London 2007 * at QCon London 2008 * at ThoughtWorks Quarterly Technology Briefing, October 2008... - Feature Driven DevelopmentFeature Driven DevelopmentFeature-driven development is an iterative and incremental software development process. It is one of a number of Agile methods for developing software and forms part of the Agile Alliance. FDD blends a number of industry-recognized best practices into a cohesive whole. These practices are all...
(FDD) developed (1999) by Jeff De LucaJeff De LucaJeff De Luca is a global information technology strategist and an author in the field of software development methodology. He is considered the primary architect of Feature Driven Development circa 1999 [^JDLBIO], a lightweight methodology for developing computer software with reduced management...
and Peter CoadPeter CoadPeter Coad is a software entrepreneur and author of books on programming. He is notable for his role in defining what have come to be known as the UML colors, a color-coded notation chiefly useful for simplifying one's understanding of a design or model.-Education:Coad received a Bachelor of...
. - ICONIXICONIXICONIX is a software development methodology which predates both the Rational Unified Process , Extreme Programming and Agile software development. Like RUP, the ICONIX process is UML Use Case driven but more lightweight than RUP. Unlike the XP and Agile approaches, ICONIX provides sufficient...
Process, developed by Doug Rosenberg: An UML Use Case driven approach to providing just enough documentation and structure to the process to allow flexibility, yet produce software which meets user and business requirements.
Most of these lightweight processes emphasize the need to deal with change in requirements and change in environment or technology by being flexible and adaptive.