You are on page 1of 6

Global Journal of Advanced Engineering Technologies, Vol3, Issue3-2014 ISSN: 2277-6370

CUSTOMER SATISFACTION IN SOFTWARE


INDUSTRY 1
Fatima Abogila Mohamed Matog, 2 Dr. Deva Raj Baduu
1
Research scholar, SamHigginbottom Institute of Agriculture and Technology and sciences, Allahabad, India.
2
Associate Professor &Head, Dept. of Marketing Sam higginbottom Institute of Agriculture and Technology and Sciences
Allahabad, India

Abstract: - Customer satisfaction in software industry is and add to the basic entities of business like marketing,
the predominant topic to be discussed. There are several sales, service after sales.
products to market. Software products are with
international standards and should be served for national II. BACKGROUND
and international clients. To market the software products
in the country the distinct qualities should be rendered to Customer satisfaction is regarded as the most
the products and the products should be sold to the predominant for any business. Customer satisfaction leads
customers. The software products should be developed to to set up the standards needed for growth of the business.
meet the expectations of the customers and mixed with the The competition in software industry is very high and
international quality standards. Customer is the king for filled with neck to neck competition. Predicting customer
every business, who controls the business, wields life and satisfaction in the field of software is key point. This has to
death power over the product of the manufacturer. Key be addressed and find the possible innovative solutions to
words: Marketing, Customer Satisfaction, Software achieve the customer satisfaction in the field of software
Products, Software service after sales. The customer products. To attain Customer-oriented business philosophy
satisfaction is depended on many factors of the product the company has to follow customer-focus, customer
development. In this paper the customer satisfaction levels centrism, relationship marketing and other necessary
and the objectives are discussed in detail. The thesis customer centric fundamental concepts. The important
consists of introduction to the customer satisfaction business improvement factor has to be defined along with
definitions, objectives, limitations and need of the study. the quality parameters of international standards of
The thesis has been developed by taking the products of software industry.
DennisCodd a business automation company. The products
analysis and the feedback on the products from the III. RESEARCH HYPOTHESIS
customers have been taken into consideration.
Customer Satisfaction can be measurable with
Keywords: - Customer Satisfaction, Software products, scientific research methods. Especially to measure the
Quality parameters, requirement analysis. satisfaction of the customer related to software industry has
to be identified and declared in this paper. The research
I. INTRODUCTION Hypothesis of this paper is to find the most suitable
customer satisfaction factors for the customers who have
Customer satisfaction is playing a vital role in purchased the software.
promoting the product and experience the profit in the Research Hypothesis one is to understand the key
business. In judging the customer satisfaction factors are relationship factors to improve the customer satisfaction to
that businesses should consider: Increasing loyalty and maximize profits.
customer retention by just 5% can increase profits by 75%. Research Hypothesis two is to find the quality
Most dissatisfied customers will reveal the problem for 9 parameters of software industry which gives ultimate
other people. Only 4% of dissatisfied customers actually quality and utility to the customers.
complain to the company. Satisfied customers, on the other The final Hypothesis of the paper is combining the
hand, tell 5 to 6 other people about their positive customers requirements with quality parameters to
experience. Managing dissatisfaction, then, is a critical achieve highest customer satisfaction in software industry.
consideration in planning a customer satisfaction. The
present investigation is to find the ways to get the customer IV. RESEARCH METHODOLOGY
satisfaction in software industry. This has to be achieved
with the combination of key customer requirements as well The research methodology to develop the thesis on
as the remarkable quality parameters specified by the customer satisfaction in software industry, various books
international quality standards. There is a substantial body on customer satisfaction, Research articles and previous
of empirical literature that establishes the benefits of research works done by predominant authors have been
customer satisfaction for firms. This should be different collected. The Secondary data has been developed from the
company financial statements, facts and figures collection

339
Global Journal of Advanced Engineering Technologies, Vol3, Issue3-2014 ISSN: 2277-6370

from the customer surveys with direct interaction. The TABLE 1


numbers of products are limited and the customers for the
products are in hundreds. To do the survey on the products Goal Area/Factor Metrics:
satisfaction one hundred customers have been taken into
Consideration. The sampling has been done only on one 20% increase Customer Satisfaction
hundred customers. The feedback has been analyzed and in satisfying Satisfaction: (score) with
kept in the results chapter. The research methodology is customer project, product,
rich with quantitative research, qualitative research and needs meet need; process, people
experimental research methods have been used to develop
the thesis. Qualitative research methods have given the No. of prototype
confidence in
data for concept building; quantitative research methods releases -
product;
have been used to get the data related to the customers planned, actual
feedback through the questioners and web feedback. The
experimental research method has helped to get the confidence in
process/people Number of the
answers from the customers with a great tactics in
original
experimental model. Customer satisfaction measurement
Product satisfied/unsatisf
methods have been investigated and applied in this thesis
ied requirements
implementation and practically experimented on the Effectiveness:
customers. The results have been depicted in this project
thesis. The results evaluation and finding the facts related Number of
product
to the project aim and objectives have been fulfilled with requirements
quality
the help of action research methods. changed
claimed;
Research methodology is predominantly good in
this research work to reveal the innovative concepts of demonstration Number of
customer satisfaction in relation with the software industry. requirements
of quality
The research methodology has been applied on the quality priority changes
parameters of software industry. The research
methodology has revealed the customer satisfaction No of evolutions
parameters, customer behavior and customer centric of requirements
objectives. The research methodology focused on the No change in Project Time spent in
customer surveys also. Customer feedback and surveys are costs of efficiency: customer
key points and milestones for getting accurate. While requirements interactions
investigating the facts about the customer satisfaction, activity process
three methods are predominant. These are customer definition; Number of
characteristics, Time availability, and cost. These three customer
make the organization to identify the customer satisfaction interactions
factors. These facts have revealed from thousands of process cost;
surveys. The methods for surveys are through comment
cards, telephone surveys, mail based survey, focus groups, people impact Time spent
group interviews and finally contact between customer and demonstrating
employees. models/prototyp
es
V. RESULTS AND INTERPRETATIONS 15% decrease Project Number of
in problems efficiency: requirements
due to poor not satisfied
requirements requirement
Analysis of data is a process of inspecting,
understanding defects; Effort spent
cleaning, transforming, and modeling data with the goal of
discovering useful information, suggesting conclusions, satisfying
and supporting decision making. Data analysis has multiple people incorrect
facets and approaches, encompassing diverse techniques interaction; requirements
under a variety of names, in different business, science,
and social science domains. process cost
impact

340
Global Journal of Advanced Engineering Technologies, Vol3, Issue3-2014 ISSN: 2277-6370

TABLE 2 Experiment 3 There was good buy-in by the


Experiment Main Results: development team
Applying and There were high levels of user
Experiment 1 Successive levels of measuring involvement
tailoring are involved - the impact of There was a high level of user
Defining, they are difficult to clearly the new satisfaction with the final
tailoring and define customer- product
introducing the The DSDM based oriented The users sometimes resented
customer- customer oriented DennisCodd the demands on their time
oriented process. framework is loosely' process: The team emphasis on
defined and requires development of product means
further refinement and CMM documentation/testing suffers
instantiation to be Assessment unless control exercised; this
employable Tool Project may be a problem for longer
The new DSDM based term customer satisfaction
process does not fit easily Any organization and culture
with existing Quality changes are non-trivial
Systems It was difficult to control and
Detailed DSDM based plan prototyping
processes cannot be fully It was difficult to monitor project
prescribed due to the progress with traditional
highly iterative processes management techniques
involved that is The development team was not
dependent on actual used to empowerment and they
product development tended to perceive a lack of
progress direction and management
Detailed project planning
cannot be achieved: plans Experiment 4 It is difficult to compare results with
need to stay at a high traditional methods due to non-
level or they will lag equivalence with stages in water fall
behind the actual Comparing the
and variants.
new customer-
development Customer surveys provided evidence
oriented
of improved satisfaction
DennisCodd
Experiment 2 The DENNISCODD process was found
The pragmatic use of principles process with
to be more efficient than traditional
leads to a fit for purpose the existing
methods in terms of required
Applying and product traditional
functionality achieved for developer
High level user requirements are development
measuring effort
difficult to resolve and manage process.
the impact of If the development had followed the
the new contractually existing traditional process, that may
customer- The use of prototyping have led to the development of an
oriented techniques are very effective altogether different tool, not taking
process: The contract requirements would into account real business need
Requirement The longer term customer
not have been met if traditional
Tool Project satisfaction advantages are more
processes used difficult to assess
The DENNISCODD process developed
products may be more difficult to
maintain and evolve

341
Global Journal of Advanced Engineering
ngineering Technologies, Vol3, Issue3-2014
Issue3 ISSN: 2277-6370

TABLE 3 has given best results from the customers of a software


company.
YEAR 2007- 2008- 2009- 2010- 2011- 2011- 2013-
2008 2009 2010 2011 2012 2013 2014
a) Excellent b) Good c) Average d)
d should be improved.
SALES 14 16 19 23 45 69 105
Feedback Excellent Good Average Should
be
improved

200 No of 50 30 15 5
SALES
customers

0
SALES

No of customers
Excellent

Both behavioral marketing and multichannel marketing


have positive business impact. Mature behavioral Good
marketers in B2B companies reported 42 percent of their
sales pipelines as marketing sourced, while their B2C Average
counterparts reported 47 percent. Both of these
th are
significantly higher than average 35 percent and 41
percent, respectively. 3) Does the company service after sales to your product
Question: 1) What are the products and how many maintenance? Please rate the service.
numbers of customers have been taken into account for
making the customer satisfaction survey? a) Excellent b) good c) Average d) Should be improved

TABLE 4 Feedback Excellent Good Average Should


be
Name of improved
College Hospital Used Car Super
the
Automation Management Showroom Market
Product No of 48 29 16 7
No of customers
20 25 25 30
Customers

Customer Satisfaction factors


No of customers

48
29
16
7

2) Does the project give you full pledged satisfaction in


serving your needs? Please rate our product. The results
have to be chosen from the following options. The survey

342
Global Journal of Advanced Engineering
ngineering Technologies, Vol3, Issue3-2014
Issue3 ISSN: 2277-6370

3) Do you feel satisfied with the products of DennisCodd? REFERENCES

A. Excellent B. Good C) Average D) Need to be 1. Pressman, Scott (2005), Software Engineering: A


improved. Practitioner's Approach (Sixth, International ed.),
Feed Back Excellent Good Average Need McGraw-Hill
Hill Education Pressman, p. 388
Improvement 2. TECHNICAL REPORT [2010]Improving
Customers 64 27 5 4 processes for providing better services published
by
CMMI for Services, Version 1.3
3. "How to Deliver Resilient, Secure,
S Efficient, and
Easily Changed IT Systems in Line with CISQ
Customers with 4.
Recommendations". Retrieved 2013-10-18.
2013
"ISO 25000:2005" (PDF). Retrieved 2013-10-18.
2013
satisfaction levels 5. J. Bohnet, J. Dllner, "Monitoring Code Quality
and Development Activity by Software Maps".
Customers Proceedings of the IEEE ACM ICSE Workshop on
Managing Technical Debt, pp. 9-16,
9 2011.
64 6. Improving Quality Through Better Requirements
(Slideshow), Dr. Ralph R. Young, 24/01/2004,
27 Northrop Grumman Information Technology
5 4 7. a b International Organization for
Standardization,, "ISO/IEC 9001: Quality
management systems -- Requirements," 1999.
8. International Organization for Standardization,
"ISO/IEC 24765: Systems and software
engineering Vocabulary," 2010.
9. W. A. Shewhart, Economic control of quality of
manufactured product. Van Nostrand, 1931.
10. a b c B. Kitchenham and S. Pfleeger, "Software
VI. CONCLUSION quality: the elusive target", Software, IEEE, vol.
13, no. 1, pp. 1221,
21, 1996.
The
he frequent measurement of customer satisfaction is 11. D. A. Garvin, Managing Quality - the strategic
essential for defining the objectives of the business and competitive edge. New York, NY: Free Press
improvement. Customer Satisfaction in software industry [u.a.], 1988.
is directly proportionate to growth of the business as well 12. S. H. Kan, "Metrics and Models in Software
as improves the brand image in the industry. Customer Quality Engineering", 2nd ed. Boston, MA, USA:
satisfaction can be achieved in software industry with the Addison-Wesley
Wesley Longman Publishing Co., Inc.,
combination of fulfilling the needs of the customers and 2002.
embedding the ultimate quality parameters of International 13. W. E. Deming, "Out of the crisis: quality,
Standards. The customer satisfaction ccan be known with productivity and competitive position".
the help of surveys and feedback of customers. Cambridge University Press, 1988.
19
Incorporating the quality parameters with the customer 14. A. V. Feigenbaum, "Total Quality Control",
oriented software development which fulfills the needs and McGraw-Hill,
requirements. The customer satisfaction should be 15. Albrecht, A. J. (1979), Measuring application
incorporated in software industry
ustry before sales, during sales development productivity. In Proceedings of the
and after sales service. The feedback is mandatory to judge Joint SHARE/GUIDE IBM Applications
the heights of customer satisfaction of the business entity. Development Symposium., IBM
16. Ben-Menachem,
Menachem, M.; Marliss, G. S. (1997), (1997)
Software Quality, Producing Practical and
Consistent Software, Thomson Computer Press
17. Boehm, B.; Brown, J.R.; Kaspar, H.; MacLeod,
G.J.; Merritt, M.J. (1978), Characteristics of
Software Quality, North-Holland.
North
18. Chidamber, S.; Kemerer, C. (1994), A Metrics
Suite for Object Oriented Design. IEEE
Transactions on Software Engineering, 20 (6), pp.
476493

343
Global Journal of Advanced Engineering Technologies, Vol3, Issue3-2014 ISSN: 2277-6370

19. Ebert, Christof; Dumke, Reiner, Software 39. Pressman, R. S., "Software Engineering - A
Measurement: Establish - Extract - Evaluate - Practitioners Approach", McGraw Hill, 1997.
Execute, Kindle Edition, p. 91 40. MacDonald, J., "Understanding Business Process
20. Garmus, D.; Herron, D. (2001), Function Point Re-engineering", Hodder & Stoughton, 1995.
Analysis, Addison Wesley 41. Bell, S., Wood-Harper, T., "Rapid Information
21. Halstead, M.E. (1977), Elements of Software Systems Development - System Development in an
Science, Elsevier North-Holland Imperfect World", Second Ed., McGraw-Hill,
22. Hamill, M.; Goseva-Popstojanova, K. (2009), 1998.
Common faults in software fault and failure data. 42. Martin J., "Rapid Application Development", New
IEEE Transactions of Software Engineering, 35 York: Macmillian, 1991.
(4), pp. 484496. 43. Elliott, J. J., "System Understanding Reference
23. Jackson, D.J. (2009), A direct path to dependable Model", DERA Report, 1999.
software. Communications of the ACM, 52 (4). 44. Raynor-Smith, P. M., "DENNISCODD Process",
24. Martin, R. (2001), Managing vulnerabilities in DERA Report, 1998.
networked systems, IEEE Computer. 45. DSDM Consortium , "DSDM Manual", 1996.
25. McCabe, T. (December 1976), A complexity 46. Stapleton J., "Dynamic Systems Development
measure. IEEE Transactions on Software Method", Addison-Wesley, 1997.
Engineering 47. Raynor-Smith, P. M., Elliott J. J., DENNISCODD
26. McConnell, Steve (1993), Code Complete (First Final Report, Version 1.0, May 1999.
ed.), Microsoft Press 48. ESSI VASIE website: http:// www .cordis.lu/
27. Nygard, M.T. (2007), Release It! Design and esprit/src/stessi.htm
Deploy Production Ready Software, The 49. Bob E. Hayes, Measuring Customer Satisfaction:
Pragmatic Programmers. Survey Design, Use, and Statistical Analysis
28. Park, R.E. (1992), Software Size Measurement: A Methods, 2nd Edition, ASQ Quality Press,
Framework for Counting Source Statements. Milwaukee, Wisconsin, 1998.
(CMU/SEI-92-TR-020)., Software Engineering 50. Terry G. Vavra, Improving Your Measurement of
Institute, Carnegie Mellon University Customer Satisfaction: A Guide to Creating,
29. Pressman, Scott (2005), Software Engineering: A Conducting, Analyzing, and Reporting Customer
Practitioner's Approach (Sixth, International ed.), Satisfaction Measurement, ASQ Quality Press,
McGraw-Hill Education Spinellis, D. (2006), Milwaukee, Wisconsin, 1997.
Code Quality, Addison Wesley 51. Donald C. Gause & Gerald M. Weinberg,
30. John ElliottAchieving Customer Satisfaction Exploring Requirements: Quality Before Design,
through Requirements Understanding BY John Dorset House Publishing, New York, New York,
Elliott FROM System and Software Engineering 1989.
Centre, Defence Evaluation and Research 52. Robert Grady,(2002)Practical Software Metrics
Agency, Malvern, UK for Project Management and Process
31. Article published by Written By Scott Smith, Ph.D. Improvement, PTR Prentice Hall, Englewood
in http:// www.qualtrics.com /blog/customer- Cliffs, New Jersey, 2002.
expectations/ 53. Norman Fenton, Robin Whitty & Yoshinori Iizuka,
32. Garrity, E.J., Saunders, G.L., "Information Software Quality Assurance and Measurement: A
Systems Success Measurement", IDEA Group, Worldwide Perspective, International Thomson
1998. Computer Press, London, England, 1995.
33. Fenton, N. E., Pfleeger S. L., "Software Metrics", 54. Steve Jobs(2013) 5 Easy Ways To Gain Customer
2nd Ed, Thomson Computer Press, 1997. Feedback On Your Product
34. Gillies, A., "Software Quality - Theory and 55. Aileron, Contributor (2012)The 10 Keys of
Management", Chapman and Hall, 1992. Excellent Customer Service
35. Linda Westfall ISO 9126, "Software Product 56. Lina Saikkonen (2012) Customer Satisfaction in
Evaluation", 2012. IT service Industry
36. Van Ekris, J., "Towards business oriented 57. Murali Chemuturi (2013)How to Measure
questionnaires for the specification of software Customer Satisfaction.
product quality", ESCOM-ENCRESS 1998
Proceedings, May 1998, pp230-238.
37. Somerville, I., "Software Engineering", Addison
Welsey, 1996.
38. McConnell, S., "Rapid Development", Microsoft
Press, 1996.

344