fully SDLC Policy

1. Traditional SDLC

2. Manifesto for Agile Software
Development
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.

4. Agile Activities

5. SDLC with AGILE

6. Requirements Analysis
ICONIX Process
Gather information about the
legacy system you're re-
engineering
Identify real-world
domain objects
Database tables
Screens
Do some rapid prototyping
of the proposed new
system
Draw the domain model
Identify use cases, and put them
on use case diagrams
Organize the use cases logically into groups.
Capture this information in a package diagram
Milestone 1: Requirements Review
Allocate Functional requirements to the use
cases and domain objects
Write the first-draft use
cases
Put the domain
Objects on here
Gather information about the
legacy system you're re-
engineering
Do it in two hours at max
AnalysisEfforts

7. Perform robustness analysis
For Each use case …
Disambiguate the first-draft use case text
Identify a first cut of objects that
accomplish each scenario
Update your domain model as you
discover new objects and attributes
Finish updating the analysis-level class
diagram
Milestone 1: Requirements Review
Milestone 2: Preliminary Design Review
DesigningEfforts

8. Milestone 2: Preliminary Design Review
Split the domain model into as
many class diagrams as needed
Allocate behavior by drawing
sequence diagrams <<automagic>>
Generate a skeleton sequence
diagram from boundary and
entity objects on the robustness
diagram
<<automagic>>
Update class diagrams with new
attributes and operations
<<automagic>>
Generate unit test stubs for all
controllers on the robustness
diagram
Draw message arrows between
objects
For each use case……
One sequence diagram
per use case
Allocate operations to
classes
Clean up the static model
Review design to ensure it
satisfies all the requirements
Milestone 3: Critical Design Review
DesigningEfforts

9. Milestone 4:Delivery
Generate the domain classes
Synchronize the design with the code in
preparation for the next release or
iteration
Milestone 3: Critical Design Review
Also generate whatever
code you can get your IDE
or code generator to
create for you
Code and testing
For each controller on the robustness diagram …
Implement unit
tests
Write the source
code
Run the Tests
no
Test
passed?
yes
Perform system and
user-acceptance testing
Code Review and Model
Update
Generate your unit
test stubs from the
robustness diagram
controllers
ImplementationEfforts

10. • http://www.agilemanifesto.org/iso/ar/principles.html
• http://mind42.com/mindmap/b2e3a8bc-30b5-42ec-
a366-0ec97be6eef3?rel=gallery
• http://www.scrumguides.org/docs/scrumguide/v1/scru
m-guide-us.pdf
• http://www.agilemodeling.com/
• http://www.iconixsw.com/
Links to read