You are on page 1of 15

Proc and Cons of Sequential

and Parallel
Sequential Parallel
• Pros • Pros
– Customer Driven
– Upfront planning provide reference
– Chaotic in nature
at any stage for project status. – Iterative confidence buildup
– Resources known and managed – Change agility
– Developer decision for design
– Control through Chain of command
– Ensured Quality and
– Managed risks – Business value game
– Formal Nature – Collaborative Customer Relation
– Iterative development and deployment
– Lesser no of experts in Team
– Testing is also iterative so can’t be squeezed
– Only pre agreed deployment. – Automated test suit is not time expensive
– End Date estimation – Value of product becomes evident during
development a and closure of project does not
• Other points change on result in desperation for any party

circumstances • Other points change on


– Minor Refactoring only circumstances
– Autocratic in nature
– Illusion of estimated approach – Good for small Teams
– Bureaucratic in nature – Code that is sufficient rather than speculative
Proc and Cons of Sequential
and Parallel
Sequential Parallel
• Cons • Cons
– Competitive customer relation – Trust based contracts
– More Resources
– Project may linger forever
• Human, Financial, Special, others

– Exhaustive for Team.
Nothing to show up till last stages
except huge bill. – Only experts constitute a team
– Exhaustive efforts on planning rather – Customer may get annoyed with
then product. constant involvement
– Long term planning yields larger
– Test Team is engaged from start
slippages.

to end
Easily converts to a roadblock and
raises desperation. – Complexity increases incase of
– Change is undesirable distributed teams
– Testing might gets squeezed due to – Loosing Site of big picture
slippages – Testing of expectations
– Only Quality could become variable in
large products
– No fallback in case of contingency (In
case of accident)
Initiation
Sequential Parallel
• Team Formulation.
• Technical.
• Core Team Formation
• Support.
• List Modules
• Project Lead Identification.
• Organization. • List Support People
• Module identification.
• Project Plan. • Plan Requirements
• Define Operational Process. • Define Operational
• Decide Formats and standards.
• SCM System Process
– Plan,
– Design and • SCM System
– Implement – Plan,
• Prepare for next phase.
– Design and
– Implement
Requirements
Sequential Parallel
• Analyze Requirements. • Analyze initial
• Remove any ambiguities.
requirements.
• Complete details.
• Gather general
• Prepare RDD.
• Get it approved from all parties.
understanding.
• Incorporate suggestions. • Prepare Backlog
• Finalize RDD.
• Future iteration
• Baseline. (functional or containing requirements
requirements baseline)
to be completed.
• Understanding is
developed to take on
Requirements.
System Analysis
Sequential Parallel
• Suggest solutions for • Each member works on
requirements in RDD.
• Technical solutions. task at hand and
• Financial solutions. analyze problem for a
• Finalize Working
requirements. solution.
• Performance. • Analyze what to re-
• Reliability.
• Quality. factor or create.
• Prototype (if required) •Requirements review is conducted on the
• Evolution or Throwaway. start of each Iteration.
•Testable Task specification against
• Tools used. requirements.
• Demonstrate for feed back. •Prioritize tasks.
•Estimate tasks.
• Prepare SAD. •Allocate tasks.
• Usability plan for of the shelf •Create test scenarios. (may even write
components. test before development)
Design HighLevel

Sequential Parallel
• Establish design • Each member works on task
at hand and design a
objectives. solution.
• Prepare HLD • High level design is
discussed in Requirements
• Prepare system review each time.
component list. • Design how to re-factor or
• UI design. create a skeleton.
• Interfaces and modules up
•Requirements review is conducted on the
to routine level. start of each Iteration.
•Testable Task specification against
• Reports. requirements.
• Navigation details. •Prioritize tasks.
•Estimate tasks.
• Help and error messages. •Allocate tasks.
•Create test scenarios. (may even write
• Prepare STP and STS. test before development)
Design LowLevel

Sequential Parallel
• Finalize on what libraries • Designing is repeated in
or routines are to be each iteration.
used. • Low level design is
• Prepare LLD. developer’s
• Finalize Low level details. responsibility.
• Prepare UTS and UTP.
• Design unit tests.
• Refine and update
previously prepared and •Requirements review is conducted on the
start of each Iteration.
controlled documents. •Testable Task specification against
requirements.
• Baseline (allocated or •Prioritize tasks.
design baseline) •Estimate tasks.
•Allocate tasks.
•Create test scenarios. (may even write
test before development)
Development and Unit test
Sequential Parallel
• Code program. • Each member works on
• Conduct unit testing. task at hand and
implements a solution.
• Implement help and • Re-factor or create a
error messages. new implementation.
• Update design • Code unit test before or
documents if required. after Implementation.
• Fix errors.
•Requirements review is conducted on the
• Update defect log. start of each Iteration.
•Testable Task specification against
• Initiate corrective action. requirements.
•Prioritize tasks.
• Record unit test results •Estimate tasks.
•Allocate tasks.
and other data •Create test scenarios. (may even write
generated in process. test before development)
Integrated test.
Sequential Parallel
• STS and STP are used to • Implemented solution is
conduct Integrated tests finalized only if integrated
solution implements some
• alpha testing feature fulfilling (partial or
– Limited users test integrated complete) requirement.
system • Integrated testing is done
• beta testing on the go for each new
– Full fledge testing feature implemented.
• Test results recording
•Requirements review is conducted on the
• Diagnose and fix recorded start of each Iteration.
bugs •Testable Task specification against
requirements.
• Update defect logs •Prioritize tasks.
•Estimate tasks.
• Initiate corrective action •Allocate tasks.
•Create test scenarios. (may even write
• Perform regression testing test before development)
• Baseline. (product baseline)
Acceptance test.
Sequential Parallel
• User acceptance. • Demonstrate product
• Conducted by delta to the customers
– Client or and team.
– Authorized entity.
• Get Acceptance of
• Development team helps.
– Make work products available.
product delta.
– Record Errors and fix them. • Get project clearance.
• Update defect logs. •Acceptance review is conducted at the end
• Initiate corrective action. of each Iteration.
•Test features against requirements
• Perform regression testing. involving all involved parties.
•Get clearance from stakeholders.
• Record results and highlight •Get go ahead for release.
disagreements. •Get go ahead for project.
•Process review is also conducted between
Acceptance and Requirements Review.
Implement
Sequential Parallel
• Development team • System deployment is
supervises the planed.
installation. • Core team (member)
• Maintenance team provides assistance in
takes over. – deployment.
– Enhancements. – Maintenance.
– Technical support.
– Bugs recording and
fixing.
Wind up
Sequential Parallel
• Project ending • Proceed as planned
appraisals. during deployment.
• Release resources • Free all resources
excluding related to except related to
support. support.
• Return client property.
• Ensure complete
documentation is
retained in proper NOTE: This phase is a
format. part of deployment
plan and not executed
separately.
Maintenance
Sequential Parallel
• True benefits of SCM • Maintenance may or
could be picked in this may not be provided
phase. by development team
– All the support so this is also done in
documentation is the same way as
available in this phase iterations during
for maintenance.
development is done.
– Easy bug fixing during
this phase. These Iterations may be
planned by the core
team during execution
of other projects as
well.
Retirement
Sequential Parallel
• SCM resources are • Reasons may be
released. Unavailability of Core
• Maintenance team team (members).
disbands. • Same as sequential
• Reasons may be process’s same phase.
ineffectiveness of
– Cost.
– Resources.
• Requirements of
resources for some
other projects.
Project Phases Outputs
Project Phase Documents in Controlled Documents SCM Documents
preparation

Initiation RDD Project Plan, Standards and SCM Plan Meeting


guide Lines Minutes ,
Policies,
Requirement RDD CR and
Rules and
Analysis and PRs for
Regulations.
Specification controlled
Organization
Document
System Analysis HLD SAD, Usability plan structures,
s, CR and
Standard
High Level Design LLD, user HLD, STP, STS PR Status
Forms and
documents Reports
manuals,
Low Level Design user documentsLLD, UTS, UTP Process and
procedures ,
Version
Coding and Unit user documentsUnit tested Programs, Test
Reports,
testing Data
CI Status
System Testing user documentsTest Data Tested Programs Reports

Acceptance Testing Test Results Reports,


Accepted and Rejected
feature lists, user SCM
Reposito
documents ry
Implementation FAQs