Di24709711

Miss. Shaikh Tahesin Yasin , Prof. Sayyad Razak Nizam, Dr A.P. Dhande,Dr. A.R. Dani /
International Journal of Engineering Research and Applications (IJERA)
ISSN: 2248-9622 www.ijera.com
Vol. 2, Issue 4, June-July 2012, pp.709-711
Comparative Study of CBA and User in Waterfall Model for Cost
Effective Software

Miss. Shaikh Tahesin Yasin*, Prof. Sayyad Razak Nizam**,
Dr A.P. Dhande***,Dr. A.R. Dani****
*( Student of Ph.D., Singhania University, Pacheri Bari,
Dist. Jhunjhunu( Rajasthan), India
**( Student of Ph.D., Singhania University, Pacheri Bari,
Dist. Jhunjhunu( Rajasthan), India
***(VIT College of Engineering,Pune(Maharashtra) ,India
****International Institute of Informational Technology,Pune(Maharashtra),India

Abstract
The main aim of CBA and user is to show Decision-makers can be provided with a consistent
how the cost of software can be reduced so that the basis for assessing proposals and can be better
software can be developed in more quicker and informed about the implications of using economic
easy way.CBA helps us to determine the precost of resources. CBA can also be used to test the
the software and user helps us to find out how the effectiveness of a proposal after it has been
cost can be reducd by placing the user in different implemented..
models of the software.The CBA role is important
as it guides the development industry The waterfall model is a popular version of
How to find the estimate cost of the project and the systems development life cycle model for software
should they take up the project in desire cost which engineering. Often considered the classic approach to
is decided.Therefore the major role of CBA is to the systems development life cycle, the waterfall
decide ,should the project be taken in hand or model describes a development method that is linear
not.The user role in waterfall model plays a vital and sequential. Waterfall development has distinct
role in reducing the cost of project in different goals for each phase of development. Imagine a
perspective.The user helps to find the cost of the waterfall on the cliff of a steep mountain. Once the
project from time point of view.It reduces the water has flowed over the edge of the cliff and has
analysis cost which in turn reduces the time cost begun its journey down the side of the mountain, it
and more quick and easy way to collect the cannot turn back. It is the same with waterfall
data.During the designing phase the user development. Once a phase of development is
participates in the designing which again reduces completed, the development proceeds to the next
the time cost.In testing phase the user helps the phase and there is no turning back.
tester to suggest the look and feel view of the input
and output screen.The implementation phase has a Structured Analysis :
huge cost of training which can be reduced so that It is the representation of the system in terms
the user participation is necessary in different of data and the processes that act upon the data. The
phases of waterfall model. system development is organized into phases, with
deliverables and milestones to measure progress. The
Introduction: Systems Development Life Cycle (SDLC) waterfall
Cost Benefit Analysis (CBA) is an economic model typically consists of five phases. Iteration is
assessment tool. By quantifying all costs and benefits possible among phases. Although structured analysis
in monetary terms, and discounting, it is possible to evolved many years ago, it remains a popular systems
determine the net benefits (or costs) of a proposal in development method. Structured analysis is based on
today’s dollars. These net benefits/costs can then be an overall plan, similar to a blueprint for constructing
used to quantitatively rank alternative proposals: a building, so it is called a predictive approach.
between a given proposal and the status quo, Five step process:
orbetween competing proposals.

709 | P a g e

Systems Planning: -This is probably the most approval. Management and user involvement is critical
important step since it is the start of the project and to avoid any misunderstanding about what the new
will include every detail. The systems planning phase system will do, how it will do it, and what it will cost.
usually begins with a formal request to the IT Systems Implementation:- The objective of
department, called systems request, which describes this phase is to deliver a completely functioning and
problems or desired changes in an information system documented information system. During this stage, the
or a business process. The purpose of this phase is to new system is constructed. If the system was
perform a preliminary investigation to evaluate an IT purchased as a package, systems analysts configure the
related business opportunity or problem. The software and perform any necessary modifications. At
preliminary examination is a critical step because the the conclusion of this phase, the system is ready to
outcome will affect the entire development process. A use. Final preparations include converting data to the
key part of the preliminary investigation is a feasibility new system's files, training users, and performing the
study that reviews anticipated costs and benefits and actual transition to the new system. This phase also
recommends a course of action based on operational, includes an assessment, called a systems evaluation, to
technical, economic, and time factors. determine whether the system operates properly and if
Systems Analysis:-The purpose of this phase costs and benefits are within expectations.
is to build a logical model of the new system. The first Systems Support and Security:- During this
step requirements modeling, where you investigate phase the IT staff maintains , enhances, and protects
business processes and document what the new system the system. Maintenance changes correct errors and
must do to satisfy users. Requirements modeling adapt to changes in the environment, such as tax rates.
continues the investigation that began during the Enhancements provide new features and benefits. The
systems planning phase. The deliverable for the objective during this phase is to maximize return on
systems analysis phase is the system requirements the IT investment. A well-designed system must be
document. The system requirements document secure, reliable, maintainable, and scalable. A scalable
describes management and user requirements, costs design can expand to meet new business requirements
and benefits, and outlines alternative development and volumes. Information systems development is
strategies. always a work in progress. Business processes change
Systems Design:- The purpose of this phase rapidly, and most information systems need to be
is to create a physical model that will satisfy all updated significantly or replaced after several years.
documented requirements for the system. At this stage,
you design the user interface and identify necessary Evaluation Technique:-
outputs, inputs, processes, internal and external The cost of the project can be reduced by the
controls, computer based and manual features to participation of user in different phases of the model.
guarantee that the system will be reliable, accurate, The below table shown indicates the involvement of
maintainable, and secure. The deliverable for this user in different phases of proposed technique.
phase is the system design specification, which
presented to management and users for review and
Participati
on
Participation of the User in the phases System Coding User not NIL
Participati
Phases Existing Proposed on
technique Technique System testing User not User
Participati participatio
on n
(Participati
Implementation&Evalu User not User
on of user)
ation Participati participatio
Preliminary User is As per the
on n
investigation Participati current role
Maintenance User not User
on
Participati participatio
Requirement Analysis User not NIL on n
Participati
on
System design User not NIL

710 | P a g e

Conclusion: Demand Forecasts in Public Works
The cost of developing the website or any Projects? The Case of Transportation."
software can found easily with the waterfall Journal of the American Planning
model.The waterfall model helps to find the cost Association, vol. 71, no. 2, Spring 2005, pp.
which will be encoured by the project in various 131–146. [16]
phases.The cost per phase is sum up first and then 6. Bent Flyvbjerg, Nils Bruzelius, and Werner
calculated with real coast and finally the difference is Rothengatter, Megaprojects and Risk: An
calculated which shows the total cost needed for Anatomy of Ambition (Cambridge
developing the software.It also helps to find out the University Press, 2003). [17]
area where the cost can be reduced (extra cost) which 7. Software Requirements 2 by Karl Wiegers
helps the team to develop a cost effective 8. The Passionate Programmer: Creating a
software.When the area is defined by the CBA for Remarkable Career in Software
cost effectivness than the management can take Development (Pragmatic Life) by Chad
necessary action to reduced the cost Fowle
9. Benefit/Cost Analysis: Introduction.
References: Mankato State University. undated. [18]
1. Ascott, Elizabeth. 2006. Benefit Cost 10. Campbell, Harry and Brown, Richard (2003)
Analysis of Wonderworld Drive Overpass in Benefit-Cost Analysis: Financial and
San Marcos, Texas. Applied Research Economic Appraisal Using Spreadsheets.
Project. [14], Texas State University Cambridge University Press [19]
2. Bent Flyvbjerg, Mette K. Skamris Holm, 11. Exploring Requirements: Quality Before
and Søren L. Buhl, "Underestimating Costs Design by Donald A.
in Public Works Projects: Error or Lie?" 12. The Deadline: A Novel About Project
Journal of the American Planning Management by Tom DeMarco
Association, vol. 68, no. 3, Summer 2002, 13. Chakravarty, Sukhamoy (1987). "cost-
pp. 279–295. [15] benefit analysis," The New Palgrave: A
3. Software Requirements 2 by Karl Wiegers Dictionary of Economics, v. 1, pp. 687–90.
4. The Passionate Programmer: Creating a 14. Dupuit, Jules. "On the Measurement of the
Remarkable Career in Software Utility of Public Works" in Readings in
Development (Pragmatic Life) by Chad Welfare Economics, ed. Kenneth J. Arrow
Fowle and Tibor Scitovsky (1969)
5. Bent Flyvbjerg, Mette K. Skamris Holm, 15. Valentina Plekhanova, Intelligent Agent
and Søren L. Buhl, "How (In)accurate Are Software Engineering

711 | P a g e

Di24709711

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Di24709711 (20)

Di24709711