[Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

ZERO DEFECT SOFTWARE DEVELOPMENT AND EXPORTING - A

ROADMAP TO SUCCESS

1. Mr. S.Thowseaf (Ph.D. Research Scholar), 2. Dr. M. Ayisha Millath (Research Supervisor),

Alagappa Institute of management, Alagappa University, Karaikudi - 630003

Ct Email ID- thowseaf786@gmail.com, Ct Mobile. No- +91 7358167123

Ct Email ID- ayishamillath05@gmail.com, Ct Mobile. No- +919842144984

ABSTRACT

The software industry is increasingly becoming a dependent factor for effective

functioning of other industries around the globe. The software companies, recognition and
business greatly depends on its successful software compilation according to the requirement of
the customer. In-order to achieve recognition, get continuous business, software companies are
more keen in removing the defects in the software after they are created. Focusing on fixing the
software defect is better option, but eliminating and producing zero defect software in first place
is the best option. Several organizational strategies were adopted towards defect management
and most of the work to produce defect free software happens during the preproduction phase
and software development process. On closer analysis Zero defect therapy is hypothetical, but
expecting Zero defect and making Zero defect as a goal will ultimately lead to defect free
software for very few clients or very less defective software saving nearly 50-80% software
project money for most of the clients. This paper is made to bring awareness on conceptual term
coined in this paper as zero defect therapy to software industry. Review on various case studies
is made to formulate this conceptual paper. information have been enclosed to have insight into
risk and mitigation plan. The inference drawn from the various case studies is that awareness,
personnel involved in project, resources and capacity planning helps in managing the defect
effectively.

Keywords : Zero defect therapy concept, Defect Management Process, Control

activities in production floor.

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

INTRODUCTION

On calculating the age of software industry, it is till now infancy, on other hand
connecting in terms of growth, it was more than exponential which attracted the world market
and still now influencing every part of the industry and individual life through its significance.
The term software quality is viewed from various angles with customer as the centre focus, In-
fact software quality is an intangible concept, whose usefulness can only be felt when it meets
most of the client or consumer expectation (Kan, 2003). Getting the exact requirement of the
consumer and treating defect as something very serious during the initial and during the course is
the only way to prevent defect, this can be achieved by zero defect therapy. Defect is common,
though many defects are fixed before releasing, most of the defect are still analyzed detailed
soon the software is released, thereby company are forced to spend further amount for fixing the
problem. Zero defect therapy is a concept of fundamental change in the thinking; it doesn't mean
zero defect in software, it doesn't mean complete software that doesn't require any change now
and never, these are practically impossible. Zero defect therapy means expecting zero defect,
which means zero defect is the goal of the organization and every individual there in the
organization. Zero defect therapy practice on other end will lay a strong foundation in building a
software that meets consumer or client needs also value perception (Humphrey, 1995)
(Weinberg, 1997). Zero defect therapy is a scientific methodological approach consisting
Planning on project, customer validation, review, process implementation and data collection. It
involves implementing proper design, processing compliances and setting limited tolerance
(Nandyal, 2001). Achieving zero defect software might be hypothetical but still most it part can
be achieved i.e. 99.999% whose context model was referred in an article posted by (Greenland,
2010). Insight, it is discovered that Zero defect therapy reduces overall project cost, saves time,
reduces rework, increases goodwill and business of the company (Jain, 2003).The study was
centered on making zero defect delivery of software, hence paper is scrutinized as following;
past case studies illustrating importance of Zero defect therapy, Apart case studies, the paper
have been divided into 4 sections; 1st section is formulated for senior managers, 2nd part for the
project managers, 3rd part for the developers and reviewers and the final section discloses how
software export have to be carried out in-order to ripe fullest benefit with specific references to
India.

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

COST OF DEFECT IN SOFTWARE

Defect-less software are the most needed in al segment of the industry, this because small
issues when not taken care may lead to serious consequences, hence taking care of every defect
seriously is the best way to tackle software defect and its related problems (Linger, 1993). A
review on few of the problems and its serious consequences are discussed below. The US Air
force computer upgrade program for NORAD was initiated during 1968 and its operation have
been started during 1980, due to poor management in program delays and incompatible system
configuration the missile warning was reported by NORAD, similarly Soviet reported US missile
attack during 1983, luckily the officer in charge understood it was false alarm, this was reported
that, negligence of US in NORAD could have started the world war III (STATES, 1981).
Therac-25 medical radiation therapy machine made by Atomic energy of Canada Limited
(AECL) had caused cancer to several patients due to lethal overdose of radiation also have killed
four people, which have arise due to software defect (Leveson, 1987). It was on 1994 in
Scotland, where 29 passenger were killed due to the crash of Chinook helicopter, it was initially
pilot who was blamed, on closer investigation it was later found due to the system failure caused
by the software defect (David Harrison, 1994). Patriot missile software error had made the
tracking system off by 0.34, ended up killing one during 1991 Gulf war (Arnold, 2000).
ARIANE 5 rocket have consumed 370 million $ without any return, the problem with the
software which in-turn resulted from the reuse of code from its predecessor rocket i.e. ARIANE
4 that turned the rocket from its path and self destruct (LIONS, 1996). Software defect resulting
delayed response from the transponder of the Iran Air Flight 655 have USS Vincennes shoot
down the flight which, resulted in tragedy causing 290 innocent civilians death during 1988
(Ghasemi, 2004). AT&T reaches out public for apologize caused by the software bug which
caused system breakdown and malfunction of 114 switching centers leading to 65 million calls
drop out, the company goodwill was setback and it took time to regain the company goodwill
and loss claim (Tumulty, 1990). Careful testing for defect in software field would result in
saving cost, lives, time and increases safety (Sagan, 1993). A knowledge can be syntactically
made correct but if the semantic structure itself wrong, no human technology can correct it
(Kopec, 1992). There is misconception that the software is correct when it meets the requirement
but the semantic error that is leading to major defect of the software build (Leveson N. G., 1992)

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

WHAT IS ZERO DEFECT THERAPY: A MESSAGE TO SENIOR MANAGER

Zero defect software code is an repetitive process in unit level, module level, integration
level, system level, deployment level and user level. It undoubted fact that Zero defect therapy
reduces cost overall project, improves the productivity and accelerates the market value of the
product. Zero defect therapy initial stage involves designing methodological approach, design
review using significant amount of data, making logic design clean and clear before coding,
adopting specification during the phase of implementation and conducting adequate testing,
which are vital source for software complexity. As zero defect therapy is an concept were goal s
an zero defect; prevention, predictability, and zero tolerance for defects must be an habit, this is
because zero defect therapy is commitment and continuous process, it a mindset applies to every
people, products and processes. Identifying key process area and deciding right action plan
towards it should be best strategic choice for zero defect implementation, when these are
implemented in work process, induction, work automation, standards and skill up-gradation
process the yielded result will be better than best (Kashif Adeel, 2005). On above mentioned
points when compiled with continuous improvement procedure with constant review and
industry standard benchmarking will lay down strong platform for the company. Habit as
discussed before for zero defect therapy should implement an attitude with every individual that
" I cannot create defects and no one can find any defect in any code I created" this could be
challenge for organization to impart such an habit and attitude through culture, but if made has
value and in-return bring only success and competitiveness to the company (Vasudevan, 2005).
Training employees to identify defects in relation to syntactical, logical, technological will yield
better output but, training to increase quality, reduce time and costs through reusability,
optimization and cross modularity will have substantial effect. Improvement program, cost Vs.
benefit analysis, verification system to check will be best tool for Zero defect therapy.
Unrealistic goals will lead to unrealistic achievements though unimaginable innovative thought,
this the concept behind zero defect therapy.

ZERO DEFECT MANAGEMENT: A MESSAGE TO PROJECT MANAGER

Inducing Zero defect therapy during induction is considered best practice also
maintaining score card, promoting kaizen and spot excellence will act as the motivational factor.

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

Rigorous reviews, code inspection, setting standards, unit test and validation molds employees
and organization towards betterment. Every process have to be clearly defined with achievable
target time, well planned methodology, necessary tools and technology at design level and
analysis level. Automation of process is the best way to increase the productivity and reduce loss
due to human ambiguity, automation certainly makes return on investment and makes work
efficient and easy. Stringent practices and habit of uncompromising through periodic assessment
on skill set, standards, training through idea forum, technology forum and increasing shared
accountability on the project undertaken will be impactful during execution phase (Carver,
2000). Review and inspection process key to zero defect; Pre-review, review during process,
post-review will ultimately help in knowledge sharing and improved document on software and
reduce most of the defect. It is better to select reviewer who is specialist or people from the same
team or people interested in product or people from other organization. It is always better to plan
and decide reviewer at the beginning of the project instead of selecting based on the availability
of the reviewer, t is advisable to conduct review not more than 3 hours also testing team presence
will make the review session effective. Inspection on other hand is formal evaluation through
which software requirement and code are examined other than author detecting faults, standards
deviation and other problems (Ciolkowski, 2002). Like review; pre-inspection, inspection during
process, post-inspection and follow-up is only shortcut to zero defect therapy.

ZERO DEFECT DELIVERY: A ADVICE TO DEVELOPER AND REVIEWERS

Primary steps for developing zero defect software is to know the requirement clearly;
having a clear picture on guidelines, requirement, optional, and mandatory will make things
comfortable. being with client and knowing the requirement, creating a proposal and circulating
the same with methodology going to be adopted to the team members are the important
component of guidelines (Geoff, 2003). The guidelines should also encloses; team composition,
hardware-software topology, training needs, project risk, mitigation plans and mechanism of
communication with other stakeholders. During the requirement phase verify content with
proposal with check-list and make sure 90-95% of the items are covered for smooth functioning.
Set rules for every individual project, make three section namely; input, tools and output. The
input component should consists of business requirement, standards, reference documents,
checklist, benchmark, prototype, sample application and business rules. The tools vary according

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

to the project having every necessary tools such as requisite pro, change control tool, project
management tool and component wizard is advisable. The output component should contain the
requirement specification, specimen prototype, simulation routine and status report on proposed
flow. Client acceptance at every phase have to be recorded and documented. Project planning
and management plays a crucial role ensure signed contract, process database, project asset,
standards and required specification of database is available as the input. Tools such as Project
schedule and tracking tools, estimation tools, project risk identification and tracking tool
document control tools are readily available (Suma. V, 2014). The output components of project
planning should wrap project plan, quality plan, configuration plan, project schedule, risk and
mitigation plan. design phase is important segment in software development it is here the
permission on screen are finalized, thereby the developer and reviewer have to design n such a
way that the design meets the requirement, ease of use, has non-compromising standards,
maintainability and extendibility. Proper tools such as HTML, Delphi, Visual basic, XML and
other such similar tools. Major objective of design such as proper screen navigation, processing
steps, transaction mapping should be well designed and built. Post to design phase prototyping
and simulation of designed application will give overall picture, on how well the software built
and these have to be once again acknowledged from clientele side. On closer insight on design,
when it meets the requirement, project coding with detailed plan, milestone, review and audits
have to be carried out (Shashi Kumar, 2014). The final phase of the project involves testing
project, testing integration and testing system rigorously for shipment to client.

A SUGGESTION FOR HASSLE FREE SOFTWARE EXPORT

Over 75% of the SEI CMM level 5 certified companies are concentrated in India.
Computer software services accounts nearly 4.33% in India's GDP. Currently India is exporting
its software to nearly 145 countries out which USA holds the highest amount of 55% of share,
the next place is occupied by UK whose share value is 21.44 similarly Canada, Netherland,
Germany, Australia, Finland, Mauritius, Singapore and Japan are the top destination of India.
India export during 2013-2014 was reported Rs. 2839270 crore also registering 18% growth
every year (www.escindia.in, 2015). It is not registering software company will ripe beneficial, if
the company is involved in exporting it is essential that the company is registered member of
Electronics And Computer Software Export Promotion Council of India, EXIM (Export Import

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

Bank of India) financial assistance, ECGC (Export Credit Guarantee Corporation Of India)
importer information, Tax department for duty draw back and making use of special economic
zones provided by the government of India will act as an additional support; reducing production
cost and increasing the availability of recourses.

CONCLUSION

Most efficient management term six sigma, Kaizen, 5S model has a defect of 0.001%
defect, Zero defect therapy is about following any practice including above mentioned models, to
achieve best of what an organization could do to achieve zero defect whatever they make. Zero
defect therapy is hypothetical, but implementing it as an organizational practice and zero defect
achievement as destination will provide betterment throughout life of the company without
undergoing nominal business lifecycle. Awareness on defect management technique and
implementing of best suited model is the initial and primary factor for zero defect achievement.
Capacity planning, training personnel involved in project and inducing zero defect therapy at
personnel level and organizational level will create an effective organizational culture and
efficient production operations.

REFERENCES

1. Arnold, D. N. (2000, 8 23). https://www.ima.umn.edu/~arnold/disasters/patriot.html.

Retrieved 12 20, 2015, from https://www.ima.umn.edu:
https://www.ima.umn.edu/~arnold/disasters/patriot.html

2. Carver, G. S. (2000). A systematic Literature Review to Identify and Classify Software

Requirement Errors. Technical Report MSU-071207 .

3. Ciolkowski, M. L. (2002). Software Inspections, Reviews and Walkthroughs. International

Conference on Software Engineering, ICSE, Orlando, Florida, USA, , pp. 641-642.

4. David Harrison, A. F. (1994). How the Royal Air Force blamed two dead pilots and covered
up problems with the. RAF JUSTICE.

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

5. Geoff, D. R. (2003). Software Control Quality - Prevention Verses Cure? ISSN: 0963-9314 ,
pp. 197- 21.

6. Ghasemi, S. (2004). Shooting Down Iran Air Flight 655 [IR655]. Iran: Iran Chamber
Society.

7. Greenland, J. (2010, 8 17). Achieving Zero Defect Software Development.

8. Humphrey, W. (1995). A Discipline for Software Engineering. Addison-Wesley Professional

publisher .

9. Jain, A. (2003). How to achieve zero defect software. Chennai: Polaris.

10. Kan, S. H. (2003). Metrics and Models in Software Quality Engineering. Addison-Wesley
publisher, Edition 2, Boston, MA, USA .

11. Kashif Adeel, S. A. (2005). Defect Prevention Techniques and its Usage in Requirements
Gathering-Industry Practices. International Conference on Engineering Sciences and
Technology , 1-5.

12. Kopec, D. &. (1992). Mismatch between machine representations and human concepts:
dangers and remedies. . Report to the EEC under subprogram.

13. Leveson, N. G. (1992). "An Investigation of the Therac-25 Accidents". . Department of

Information and Computer Science, University of California, Irvine .

14. Leveson, N. (1987). Medical Device: Therac 25*. University of washington .

15. Linger, R. C. (1993). Clean room Software Engineering for Zero- Defect Software. IEEE , 1-
13.

16. LIONS, P. J. (1996). ARIANE 5 : Flight 501 Failure. Paris: Report by the Inquiry Board.

17. Nandyal, R. S. (2001). A Near Zero-Defect Approach to software development. Hyderabad:

The Synergy Approach.

18. Sagan, S. D. (1993). The limits to safety. Princeton University press .

ISSN - 2454-6593
 [Indian Journal of Research in Commerce, Management, Engineering and applied Science] January 1, 2016

19. Shashi Kumar, T. G. (2014). SLI, a new Metric to Determine the Success of a Software
Project. International Conference on Electronics and Communication System .

20. STATES, C. G.-R. (1981). NORADs Missile Warning System: What Went Wrong? .
UNITED STATES.

21. Suma. V, T. R. (2014). Impact of Test Effort in Software Development Life Cycle for
Effective Defect Management. International Journal of Productivity and Quality
Management , Vol. 13, No 3.

22. Tumulty, K. (1990). AT&T reaches out to public and apologize for breakdown. Times Staff
Writer.

23. Vasudevan, S. (2005). Defect Prevention Techniques and Practices. Fifth Annual
International Software Testing Conference .

24. Weinberg, G. M. (1997). Quality Software Management: Systems Thinking. Dorset House
publisher .

25. www.escindia.in. (2015). http://www.escindia.in/export-scenario/indias-overall-

exports.html#. Retrieved 12 21, 2015, from http://www.escindia.in:
http://www.escindia.in/export-scenario/indias-overall-exports.html#

ISSN - 2454-6593