(IJCSIS) International Journal of Computer Science and Information Security,Vol. 9, No. 5, May 2011
Enhancement of stakeholders participations inWater fall Process Model
(Step towards reducing the defects in software product)
Mehar Ullah Fasee Ullah Muhammad Saeed Shehzad
email@example.com firstname.lastname@example.org email@example.com
Department of Computer ScienceCity University of Science & Information Technology (CUSIT)Peshawar, Pakistan
— In complete software development life cycle, defectscan be originated from any source such as from stakeholders, endusers, or in understanding the scope of project or product. Inwater fall process model, all activities are performing in sequenceand though it has its own drawbacks, which causes of differentdefects but one perspective of defects is the involvement of developer stakeholders in development process. The coordinationproblem between developer stakeholders of successive activitiescauses many problems such as improving defect ratios, managingthe work within deadline time, productivity, reliability andquality of software. Coordination and communication problemamong stakeholders is due to lack of communication power of stakeholders and proper way to understand his/her work tostakeholder of successive activity. To overcome this problem, wehave proposed a strategy which can be implemented by projectmanager of team or with mutual coordination of team members.
Key Words:Defects , stakeholders, Defects ratio, Coordination,Communication
Software development process comprises on set of activities which can be shaped or named according to definemethodologies and umbrella of these activities is considered as process model. Now-a-day, stakeholders are using number of process model and their demand can be seen with respect todifferent aspect such as delivery time for products, qualitylevel, maintainability, availability, complexity or agility.Among these process model, water fall is an old andtraditional model which can be followed by many developersto develop the customized software and where instant changein system are not acceptable. Water fall process model is alsorepresented as classic software life cycle  where softwareevolution proceeds in sequence of activities. Besides itsadvantages, water fall process model causes some problemsdue to its sequential approach, making the development process length and unable to accept the uncertain requirementsof a system . Similarly, in waterfall process model planningis done during the early stages, so it causes many design flaws before the development process. But its planning and intensivedocumentation helps to maintain the product quality. For considering the full waterfall process model, developers canuse the set of activities such as system requirement, softwarerequirement, architectural design, detail design, coding, testingand maintenance [3, 4].In each stage of waterfall process model, documents arecreated to describe the objectives and requirements of that phase and at the end of each phase a review of project is heldfor continuation on next phase [5, 6, 7]. But if developer stakeholder of current stage is unable to communicateeffectively with developer stakeholder of next phase thennumber of factors arise which can impact the achieving of functional or non functional requirements, delay in delivery of product and its defect rate. Similarly, external influence of software development causes the risk factor which can leadfurther to cost, duration and quality of projects .In 1960, some software crises come in front of audienceduring development phase. Later on in 1993, an IEEE standarddefines several dimensions of defects that should be collected. There are number of interrelated factors indocumentation, process management, development andactivities sequences which cause defects but most probablycommunication gap between stakeholders of successive phaseis considered as important source [10, 11].To overcome this problem, we have proposed a strategy to fillthe communication gap between stakeholders of twoconnective phases and reduce the defect rate.II.
In water fall model, development of software is done byfollowing a set of activities in sequence and each activity is performed by one or more than one stakeholders. The