Waterfall model Explain about spiral

• Software project tracking SDLC The Waterfall Model was the model? • Customer Satisfaction:
and control : SDLC is the acronym of first Process Model to be Spiral model is one of the Customer can see the
Tracking and Control is the dual Software Development Life introduced. It is also referred most important Software development of the
process of detecting when a project Cycle.It is also called as to as a linear-sequential life Development Life Cycle product at the early phase
is drifting off-plan, and taking Software Development cycle model. It is very simple to models, which provides of the software
corrective action to bring the Process.SDLC is a framework understand and use. In a support for Risk Handling. development and thus,
project back on track. defining tasks performed at waterfall model, each phase In its diagrammatic they habituated with the
• Formal technical reviews : each step in the software must be completed before the representation, it looks like a system by using it before
development process. next phase can begin and there spiral with many loops. The completion of the total
This includes reviewing the A typical Software is no overlapping in the phases. exact number of loops of the product.
techniques that has been used in the Development Life Cycle Characteristics of waterfall spiral is unknown and can Disadvantages
project. consists of the following stages model:- vary from project to project. • Complex: The Spiral
• Software quality assurance : − • It also known as Linear Each loop of the spiral is Model is much more
Stage 1: Planning and sequential model,Classic life called a Phase of the software complex than other SDLC
This is very important to ensure the Requirement cycle model. development process. The models.
quality measurement of each part Analysis/preliminary exact number of phases
• Simplest of all models • Expensive: Spiral Model
to ensure them. investigation needed to develop the is not suitable for small
• Software configuration Requirement analysis is the • Systematic sequential product can be varied by the projects as it is expensive.
management : most important and approach project
fundamental stage in SDLC.. manager depending upon the • Too much dependable
Stage 2: Defining • Real project rarely follows on Risk Analysis: The
In software engineering, software project risks. As the project
configuration management (SCM Requirements/software • A working version is available manager dynamically successful completion of
or S/W CM) is the task of tracking analysis only at the end determines the number of the project is very much
and controlling changes in the Once the requirement analysis phases, so the project dependent on Risk
is done the next step is to • Difficult for customer to state Analysis. Without very
software, part of the larger cross- manager has an important
clearly define and document all requirements highly experienced
disciplinary field of configuration role to develop a product
the product requirements and • Requirement Gathering and expertise, it is going to be
management. using spiral model.
analysis − All possible a failure to develop a
• Document preparation and get them approved from the • Objectives determination
customer or the market requirements of the system to project using this model.
production : and identify alternative
analysts. This is done through be developed are captured in
this phase and documented in a solutions: Requirements are
All the project planning and other an SRS (Software gathered from the customers • Difficulty in time
Requirement Specification) requirement specification management: As the
activities should be hardly copied and the objectives are
document which consists of all document. number of phases is
and the production get started here. identified, elaborated and
• Reusability management : the product requirements to be • System Design − The analyzed at the start of every unknown at the start of
designed and developed during requirement specifications phase. Then alternative the project, so time
This includes the backing up of the project life cycle. from first phase are studied in solutions possible for the estimation is very
each part of the s/w project for the Stage 3: Designing the Product this phase and the system phase are proposed in this difficult.
future work(eg: updation) Architecture/software design design is prepared. This system quadrant. Explain about
• Measurement : SRS is the reference for design helps in specifying
incremental model?
product architects to come out hardware and system • Identify and resolve Risks:
During the second quadrant Incremental Model is a
This will include all the with the best architecture for requirements and helps in
all the possible solutions are process of software
measurement of every aspects of the product to be developed. defining the overall system
evaluated to select the best development where
the software project. Based on the requirements architecture.
possible solution. Then the requirements are broken
• Risk management : Risk specified in SRS, usually more • Implementation − With down into multiple
than one design approach for risks associated with that
management is a series of steps that inputs from the system design, standalone modules of
the product architecture is solution is identified and the
help a software team to understand the system is first developed in software development
proposed and documented in a risks are resolved using the
and manage uncertainty. small programs called units, cycle. Incremental
DDS - Design Document best possible strategy. At the
5. Explain about layered structure which are integrated in the next end of this quadrant, development is done in
Specification.Eg: DFD,ER
of SE? phase. Each unit is developed Prototype is built for the best steps from analysis design,
diagram etc... and tested for its functionality, possible solution. implementation,
Stage 4: Building or
• Tools: This layer contains which is referred to as Unit testing/verification,
Developing the Testing. • Develop next version of the maintenance.Each
automated or semi-automated tools Product/software coding Product: During the third iteration passes through
that offer support for the In this stage of SDLC the • Integration and Testing − All quadrant, the identified the requirements, design,
framework and the method each actual development starts and the units developed in the features are developed and coding and testing phases.
software engineering project will the product is built.. If the implementation phase are verified through testing. At And each subsequent
follow. design is performed in a integrated into a system after the end of the third release of the system adds
• Method: This layer contains the detailed and organized testing of each unit. Post quadrant, the next version of
integration the entire system is function to the previous
methods, the technical knowledge manner, code generation can the software is available. release until all designed
and “how-tos” in order to develop be accomplished without much tested for any faults and
failures. • Review and plan for the functionality has been
software. hassle.
next Phase: In the fourth implemented.
• Process: This layer consists of the Stage 5: Testing the • Deployment of system − Once quadrant, the Customers The system is put into
framework that must be established Product/software testing the functional and non- evaluate the so far developed production when the first
for the effective delivery of This stage is usually a subset of functional testing is done; the version of the software. In increment is delivered.
software. all the stages as in the modern product is deployed in the the end, planning for the next The first increment is
SDLC models, the testing customer environment or
• Quality Focus: This layer is the phase is started. often a core product
activities are mostly involved released into the market.
fundamental layer for software in all the stages of SDLC. Advantages and where the basic
engineering. As stated above it is of • Maintenance − There are disadvantages of spiral requirements are
However, this stage refers to
great importance to test the end some issues which come up in model? addressed, and
the testing only stage of the
product to see if it meets its the client environment. To fix supplementary features
product where product defects Advantages are added in the next
specifications. Efficiency, usability, those issues, patches are
are reported, tracked, fixed • Risk Handling: The
maintenance and reusability are released. Also to enhance the increments. Once the core
and retested, until the product projects with many unknown
some of the requirements that need product some better versions product is analyzed by the
reaches the quality standards risks that occur as the
to be met by new software. are released. Maintenance is client, there is plan
defined in the SRS. development proceeds, in
done to deliver these changes in development for the next
Characteristics of Stage 6: Deployment in the that case, Spiral Model is the
increment.
Market and the customer environment.
incremental model? best development model to
• Analysis:Requirement
Analysis:Requirement and Maintenance/software follow due to the risk analysis
and specification of the
specification of the software are maintanance and risk handling at every
software are collected
collected Once the product is tested and phase.
ready to be deployed it is • Design:Some high-end
Design:Some high-end function are • Good for large projects: It
released formally in the function are designed
designed during this stage is recommended to use the
appropriate market. during this stage
Code:Coding of software is done Spiral Model in large and
during this stage Sometimes product • Code:Coding of software
complex projects.
Test:Once the system is deployed, it deployment happens in stages is done during this stage
as per the business strategy of • Flexibility in Requirements:
goes through the testing phase • Test:Once the system is
that organization. Then based Change requests in the
on the feedback, the product Requirements at later phase deployed, it goes through
may be released as it is or with can be incorporated the testing phase
suggested enhancements in the accurately by using this
targeting market segment. model.
After the product is released in
the market, its maintenance is
done for the existing customer
base.
Evolutionary prototyping What is Agile model in Explain ASD in agile
model? Evolutionary software engineering? model development? What is Scrum
What is lean software
models are iterative type a. satisfy customer Adaptive Software development(LSD)?
models.They allow to Development is cyclical like framework in agile Lean Software Development
develop more complete b. welcome changing
requirements
the Evolutionary model, with model? (LSD) is an agile framework
versions of the software.It is the phase names reflecting Scrum is a lightweight, based on optimizing
software working model of c. deliver working software the unpredictability in the iterative and incremental development time and
limited frequently complex systems. framework for managing resources, eliminating waste,
functionality.Prototype The Agile model was primarily Phases of ASD Life Cycle complex work. and ultimately delivering
methodology is defined as a designed to help a project to • • Speculate Scrum framework activities: only what the product needs.
Software Development adapt to change requests • • Requirements The Lean approach is also
model in which a prototype quickly. So, the main aim of the • • Collaborate
often referred to as the
is built, test, and then Agile model is to facilitate • Learn • • Analysis
Minimum Viable Product
reworked when needed until quick project completion. To • • Design (MVP) strategy, in which a
an acceptable prototype is accomplish this task agility is These three phases reflect
team releases a bare-
achieved.First of all, we will required. Agility is achieved by the dynamic nature of • • Evolution
minimum version of its
develop the most visual fitting the process to the Adaptive Software
Development. The Adaptive • • Delivery product to the market, learns
aspect of the system. You project, removing activities that from users what they like,
present a portion of the Development explicitly
may not be essential for a Important concepts in scrum don’t like and want to be
system to the customer and specific project. Also, anything replaces Determinism with
added, and then iterates
continue to develop that is wastage of time and Emergence. It goes beyond a
mere change in lifecycle to a • Backlog: a prioritized list of based on this feedback.
prototypes based on the effort is avoided. An agile requirements or
feedback received. At some deeper change in 28. What is Agile
process is adaptable and it features.Within each
point, you and the customer should adapt incrementally management style. Adaptive
framework activity work task
modelling and AUP?
agree that the prototype is S/w increments must be Software Development has a
occurs within a process
“good enough” and release delivered in short time periods dynamic Speculate-
pattern called sprint.
Agile modeling (AM) is a
the prototype as the final Agile principles. Collaborate-Learn Lifecycle. methodology for modeling
product.Step 1: The Adaptive Software • Sprint: consists of work and documenting software
Requirements gathering and
analysis
 Development Lifecycle
focuses on results, not tasks,
units required to achieve a
requirement defined in
systems based on best
practices. It is a collection of
• A prototyping model starts What are the different and the results are identified backlog that can be done in a values and principles, that
with requirement analysis. types of Agile as application features. predefined time box(30days) can be applied on an (agile)
In this phase, the ASD life cyle is shown below • Scrum meeting : short software development
requirements of the system development models? Speculate meeting(15 minutes) held project. This methodology is
are defined in detail. During • In Adaptive Software daily by the scrum Team more flexible than traditional
the process, the users of the • Extreme Programming(XP) • Development, the term plan modeling methods, making it
system are interviewed to is replaced by the term • Demos: delivers the a better fit in a fast changing
Adaptive Software increment to the customer
know what is their speculate. While speculating, environment.
Development • Scrum • the team does not abandon Explain FDD in Agile
expectation from the system. Agile Unified Process (AUP)
Dynamic Systems Development planning, but it is a simplified version of the
Step 2: Quick design model?
• The second phase is a Method• Feature Driven acknowledges the reality of Feature Driven Development Rational Unified Process
preliminary design or a Development• Lean Software uncertainty in complex (FDD) is an agile framework (RUP), which is an iterative
quick design. In this stage, a Development• Agile Modelling • problems. Speculate that, as its name suggests, software development process
simple design of the system is Agile Unified Process encourages exploration and organizes software framework.
created. However, it is not a experimentation. Iterations development around making It describes a simple, easy to
complete design. It gives a with short cycles are progress on features. understand approach to
brief idea of the system to Explain about Extreme encouraged. Features in the FDD context, developing business
the user. The quick design programming(XP) in though, are not necessarily application software using
helps in developing the Collaborate product features in the agile techniques and
prototype. Agile model? • Collaborate would require commonly understood sense. concepts.
Step 3: Build a Prototype the ability to work jointly to “complete the login process”
• In this phase, an actual • Planning • Design
produce results, share might be considered a feature
prototype is designed based knowledge or make in the Feature Driven
on the information gathered decisions. Development (FDD)
• Coding • Testing . It is the
from quick design. It is a methodology.
most widely used approach of Learn
small working model of the FDD was designed to follow a
agile development • Team has to enhance their
required system. five-step development
Step 4: Initial user knowledge constantly, using process, built largely around
evaluation• In this stage, the The XP Process includes practices such as − discrete “feature” projects.
proposed system is presented ► XP design follows KIS(Keep • Technical Reviews That project lifecycle looks
to the client for an initial It Simple) principle like this:
• Project Retrospectives
evaluation. It helps to find ► Encourages refactoring • Develop an overall model
out the strength and • Customer Focus Groups
► Pair programming concept • Build a features list
weakness of the working Explain DSDM in
model. Comment and is used in coding • Plan by feature
Agile model?
suggestion are collected from • Applications of Extreme • Design by feature
the customer and provided Programming (XP): Some of • The Dynamic Systems
to the developer. Step 5: Development method • Build by feature
the projects that are suitable to
Refining prototype develop using XP model are (DSDM )is an agile software
• If the user is not happy given below: development methodology. It
with the current prototype, is an iterative, incremental
you need to refine the • Small projects: XP model is approach that is largely
prototype according to the very useful in small projects based on the Rapid
user's feedback and consisting of small teams as Application Development
suggestions.This phase will face to face meeting is easier to (RAD) methodology.
not over until all the achieve.
• Principles
requirements specified by • Projects involving new Focus on the business need
the user are met. Once the technology or Research Deliver on time
user is satisfied with the projects: This type of projects Collaborate
developed prototype, a final face changing of requirements Never compromise quality
system is developed based on rapidly and technical problems. Build incrementally from
the approved final prototype. So XP model is used to firm foundations
Step 6: Implement Product complete this type of projects. Develop iteratively
and Maintain • Once the Communicate continuously
final system is developed and clearly
based on the final prototype, Demonstrate control
it is thoroughly tested and
deployed to production. The
system undergoes routine
maintenance for minimizing
downtime and prevent large-
scale failures.