.Szalva, V. (n.d.). An Introduction to Agile Software Development. Retrieved from danube.

com:
http://www.danube.com/docs/Intro_to_Agile.pdf

(1) FDD FEATURE DRIVEN DEVELOPMENT

Feature driven development is a ceaseless and progressive software development process that
consists of basic activities such as gathering user requirements, design and documentation,
development, testing and deployment, in this approach; assuming that each task assigned or stage
is accomplished and 100% complete before the stepping to the next stage. By adopting this
methodology the most frequently occurring problem are almost resolved whereas there is a
chance that errors might not be recovered easily.
It was introduced in 1977 by Jeff De Luca and Peter Coad. FDD is an agile highly adaptive
software development process that is and is known to be a highly and short iterative. Also, this
software emphasizes on maintaining quality at each single step, making sure that it delivers
frequent and tangible working results at all steps. The most promising advantage of using this
methodology is that it does not fail to offer accurate and meaningful results. The status of using
information with the minimum of overhead and disruption for the developers is commendable.
Moreover, it is liked by clients, managers and developers.
Considering the main purposes of FDD in agile mainly to enable clear and transparent
communication channels, reduce complexity and enhance quality. These are some of the features
of FDD which makes it highly and short iterative, focusing more on quality at all steps,
frequently delivering, tangible working results at all steps, it also provides accurate and
meaningful and status information and last but not least it is liked by all the clients, managers
and developers.
In conclusion FDD is a process for helping terms that leads to increase in production of frequent,
tangible working results and it is prepared to work with team where developers’ experience
varies, it offers tackling the progress and reporting capabilities of the stages. This process also
comforts managers and makes it more attractive for big companies.
Flora1, H. K. (n.d.). A Systematic Study on Agile Software. Retrieved from
http://www.ijcsit.com/docs/Volume%205/vol5issue03/ijcsit20140503214.pdf

(2) ASD (ADAPTIVE SOFTWARE DEVELOPMENT)

ASD is known to act in order to bring change without fighting against it. Considering that we all
live in a turbulent environment, people should adopt practices that help to accept and respond to
change in a positive manner. The behavior of the adaptive software development is found to
carry away by a firm belief that ensures adaptation in a continuous manner by adopting a
different philosophy and a different norm in ASD. The firm plan of using this software is to
create or design a life cycle that is easily replaced by the most dynamic speculate life cycle.
Moreover, this life cycle adapted by a team is done to dedicate the team work to continuous
learning and be open to change, perform the task of re-evaluation, stepping into an uncertain
future and involving developers, management and customer’s in intense collaboration.
The second important component of ASD that is based on a concept is collaboration. The
complex applications are not built; they evolve and change with the time. Large volume of
information is collected in order to work with complex applications, analyzing is conducted and
is duly applied to a problem when it comes across, much larger volume than any individual can
handle by himself or herself, although it brings a big room for improvement.
The life cycle in Adaptive software development mostly focuses on outcome, not on work, and
the results are based on features of application. These features are known to be customer’s
functionality that is to be worked upon while the iteration process takes place.
ASD is also open to any kind of changes or adapts easily without taking the change as a trouble.
The process of adaption takes place by observing the ability to bring changes as a competitive
advantage.
As the name suggest, this software mainly ensures that better ways are adopted in order to
develop software by creating transparency among individuals and their interactions which takes
place over processes and tools, enabling flexibility in the working of software over
comprehensive documentation, creating customer collaboration over contract negotiation, and
responding to change over and walking a plan by helping others do it.

Flora1, H. K. (n.d.). A Systematic Study on Agile Software. Retrieved from

http://www.ijcsit.com/docs/Volume%205/vol5issue03/ijcsit20140503214.pdf

(3) LEAN SOFTWARE DEVELOPMENT

The Lean soft ware development (LSD) is known to be create a process by translating process in
to lean manufacturing and working on a principle that leads to the software development,
management of project, creating foundation for a team, also building domain and adapting from
the Toyota production system within the Agile community.
The Lean software development is thoroughly summarized in to seven principles. These are
eliminating waste; amplify learning, making quick decisions and delivering as fast as possible,
strengthening the team, maintaining quality in and combining all in one. Also, the principles are
similar when it comes to do with lean manufacturing and mainly for lean product development
Before adapting to LSSD, it is important that LSSD has to be well understood by all members of
a project before using it and working on it in real practical situation. Also, it is recommended to
think big and act small, lose easily, and learn quickly. All of the above mentioned conditions are
used to the display the importance of using LSSD. Also, it is important to consider the field and
the sustainability of implementing lean principles along the whole software development
process.
The principles of Lean are more in providing a big help to all those organizations that aspire to
shift from old development techniques and adapt to modernize software. The approach is taken
in a way that’s makes them to depend on the internet companies. In this way, they learn to
optimize software development over the entire value stream. Only because of this reason the
large companies have legacy systems. Now, they have become aware about it. They struggle
with hard by moving from where they are to the world by thriving internet companies. The rapid
growth of large, reliable secure software systems can be linked to the fact that software engineers
routinely contribute to and build upon the work of their world wide colleagues through open
source projects.
As a result, it is found that as long as the software community continues to leverage its
knowledge by sharing and expanding culture, the company will continue to grow rapidly because
solutions to seemingly intractable problems eventually emerge when many minds are focused on
the problem.

Steindl, D. C. (n.d.). Lean Software Development. Retrieved from

http://cf.agilealliance.org/articles/system/article/file/1422/file.pdf

(4) SSM (SOFT SYSTEM METHODOLOGY)

The Soft System Methodology is a progressive way of treating the organizational process
modeling. This software came in to being after the successful research conducted at Lancaster
University by Peter Checkland in the late 60’s. This application mainly focused to adapt to
systems of engineering that helps in solving general management/business problems. Moreover,
an attempt is made in order to create an application for the hard systems that are utilized to create
a fixation of business problems. On doing so, it was discovered that this approach frequently got
stuck at the first step of problem definition only. In the past, this software was seen as a tool for
modeling, but currently after coming to a time, this application is found to be seen an increasing
way as a learning and meaning development tool. Though it develops models, these models are
not supposed to represent the real world. On the contrary, by using systems rules and principles
of SSM, it helps to construct a structure while you are thinking about the real world. Despite the
fact that these models are neither descriptive nor normative, they only carry elements of both.
The most interesting feature of SSM is that it mainly creates constrains in the user’s thinking.
This is done in order to expand the horizon of your thinking, by blowing away the idea that
system thinking is always expansive. The soft system methodology also encourages the user to
find out some messy problematic situations that arise due to human activity. However, without
lowering the complexity of the mess, this model is capable to create a modeled that is
mathematically (hard systems) flexible. This Soft system strives to act as a learning tool that
learns from the different perceptions that exist in the minds of the different people involved in a
situation.
As a result, it is seen that this approach of applying SSM to various problems in a construction
project management. Moreover, it is used to sort out those knowledge management problems
that are highly challenging and complicated to understand and difficult to act upon. Also, it is
comprised of five case studies that help in dealing the situations when people are badly stuck.
They learn to incorporate human, keeping in mind the organizational and technical aspects. The
SSM encourages group learning and is ideally considered as a group decision making approach.
The problems are strengthened by the active participation of different participants and stake
holders. Also, on adopting this methodology, the users are encouraged to create joint ownership
of the problem solving process. Ultimately, SSM is recommended where an organization is
seeking to achieve changes in work places culture and transforming into a learning organization.

WHAT IS SSM?

Soft Systems Methodology (SSM) is an analytical approach for tackling complex messy
problems. Complex messy problems are those whose definition changes according to the
different perspectives of the observer (i.e. almost any area involving people). Using SSM brings
structure, coherence and an explicit defensible audit trail to the analysis.

SSM contends that all organisations are complex, that they are inhabited by people and this also
makes them messy and unique. SSM is about thinking about complexity and messes and it
provides a language for making that thinking explicit.

WHY IS SSM “SOFT”?

Contrary to traditional engineering approaches known as “Hard”, the "Soft" in the title SSM
refers to the type of problems that it is used to address not to the rigour of the approach. The
practice of SSM seeks to apply the sort of rigorous thinking of the ‘traditional’ engineering
paradigm to less predictable "Human Activity Systems."

HOW IS SSM USEFUL?

SSM is a powerful tool for unearthing implicit assumptions and competing purposes that can de-
rail an organisation’s endeavours if not understood and addressed. As a method of analysis it is:

 Strategic (top-down and forward looking)

  Explicit and defensible
 Rigorous and auditable
 Flexible enough to apply to all types and size of organisational problems
 Consensus building
 Outcome focused

WHERE CAN SSM BE APPLIED?

SSM has been used successfully to tackle problems in almost every area of human endeavour;
from prisons to the theatre, from defence and Intelligence to banking, from health to publishing,
from education to meteorology. It has been applied successfully in Commercial, Government and
Academic organisations to tackle issues in the areas of:

 Strategy and Change,

 HR and Training Development,
 Programme and Benefits Management,
 Capability Acquisition,
 Requirements Engineering,
 Concept Development (CONOPS and CONEMP),
 Enterprise Architecture Development and Strategic & Operational Process Improvement

Burge, S. (n.d.). An Overview of the Soft Systems Methodology. Retrieved from

http://www.burgehugheswalsh.co.uk/Uploaded/1/Documents/Soft-Systems-Methodology.pdf

(5) ICONIX
Iconix is a software development methodology which utilizes and combines the Rational Unified
Process (RUP), Extreme programming (XP) and agile software development.
The Iconix process is mainly about establishing an understanding and creating documents
relating the user’ behavior requirements and this is done by rooting out ambiguity in these
requirements and then utilizing them to drive a good clean 00 design. The principle distinction
of ICONIX lies in its use of Robustness analysis and design. The Robustness analysis is used to
reduce the ambiguity in use case descriptions. The software also ensures that they are written by
a combining the domain model. This process also makes the use cases much easier in order to
design test. Also, it is called as the ICONIX ‘’hidden weapon’’.
More importantly the process of ICONIX is described as the core logical analysis and design
modeling process. However, this process is highly used without performing the tailoring task on
projects that is done by following the different project management.
This process is known to adopt that most effective tie together in a combination by conducting
the analysis and design in phases. In other words, the Iconix process is versatile in a way and is
easily comparable to XP. Once this system is applied to a project, the chances of success are
enhanced.
This process comes in to play when software projects fail for all sorts Iconix process might just
not work out.
Iconix process is a use case-driven analysis and design methodology and it emphasizes on how
to achieve reliable from use cases to code. It is divided up into four milestones. These are as
follows:
 Requirement review
 Preliminary design review
 Detailed design review
 Deployment, at each stage the work for the previous milestone is reviewed and updated.

Morteza Poyan rad, H. M. (n.d.). Improving Web Engineering and Agile ICONIX Process.
Retrieved from http://www.idosi.org/mejsr/mejsr8(1)11/47.pdf