_______________________________________________________________________________________________
“Reliability Test of Questionnaire for SME’s”
1Kothapalli Venkata Rao, 2Balakrishna R
1 Computer Science & Engineering, JAIN University, Bengaluru & Associate Professor in Department of Computer Science and Engineering, Kammavari Sangham Institute of Technology, Bengaluru
2RajaRajeswari College of Engineering, Bengaluru Research Scholar, Computer Science & Engineering, JAIN University, Bengaluru
Email: [email protected], [email protected]
ABSTRACT : As the product improvement circle grows advance into progression, each person, even somewhat associated with data innovation, comprehends what quality confirmation (QA) is. The circumstance was a little extraordinary couple of years prior when just a modest bunch associations were finishing QA forms. Cases where tech-engineers were asking 'For what reason do we require a quality confirmation group?' were normal. Indeed, even today, certain QA positions appear thought little of contrasted with those having a place with creating specialists. Individuals who surmise that the response to the inquiry above is simply 'trying programming' most likely neglect to assess the primary objective and obligation of value affirmation. How about we observe QA instruments' essential significance for tech organizations
INTRODUCTION
Numerous product architects would realize that it is close to outlandish coding something that is 100 for each penny culminate. You can never be too certain if an application would run easily until the point that you hit the refresh catch and the code to check whether it does what it should do. Subsequently, testing is an essential piece of building and enhancing crafted by items nowadays. A worldwide famous tech business visionary, pioneer, and financial specialist, Marc Andreessen, announced in 2011 that Software Is Eating The World, however following a couple of years, in 2016, he refreshed his investigation to assert "Programming Is Programming The World". It is gravely essential, in this specific situation, that your independent company has an exhaustive testing approach and that you plan to computerize it however much as could be expected to get the best outcomes. Computerized programming testing has now turned into a basic piece of all effective programming and improvement ventures. Previously, robotization was viewed as a moderate extravagance for new companies, notwithstanding, as more programming testing devices fly up, its cost has extensively diminished winding up to a lesser extent a boundary for littler associations.
In a nation like Ireland, QA testing is expanding sought after as an ever increasing number of organizations are investigating filling positions here. Be that as it may, one of the difficulties is that there are insufficient individuals to apply for these positions. A QA Software Placements selection representative, Laura Boland, clarifies: "We have some awesome competitors here in
Ireland, yet insufficient for every one of the parts we are attempting to fill. Some remote organizations opening their IT HQ's here in Ireland far exceed the measure of accessible IT laborers." Why programming organizations should utilize one In the event that the product you created is surrey and hard to utilize in light of the fact that you didn't set aside the opportunity to test it, there is a decent shot your organization could lose clients post-dispatch. Skipping QA can even outcome in less efficacies, particularly if your application was worked to enhance inner procedures.
1. Item dispatch
Having programming quality issues will force you to improve on the item in the event that anything. The refixes and backtracking is the most burdening stage. It has a tendency to wind up pricier relying upon how late in the process the mistake rises: do you remember it toward the begin, amid the plan stage or do you just look it up some other time on?
For your organization and the clients' purpose, it should best be the underlying stage when you're setting the fundamental necessities. Since with each after stage, the cost of repairing a product mistake rises quick; it ought to be managed in the beginning periods. Most of the item can be re-assembled utilizing the right determinations. Surely, there will be some additional work included, however it is superior to anything distinguishing the issue after the item has been sent out to the market. That is the point at which the client gripes; orders are returned/rejected, and your image notoriety takes an emotional plunge.
2. It's not just about discovering bugs
Quality confirmation isn't just about doing the 'negative test.' It additionally needs to ensure an item/programming plays out its assumed obligation.
This is as fundamental as finding issues while taking a gander at the innovation through the purchaser's eyes.
Would you be able to get to the territory without wandering through the knocks, hopping through excessively numerous circles? Does the last upshot look pleasant or is it a lot for the eyes to deal with?
3. Client details
Deliberately recording each progression in the assembling and quality process is a fundamental piece of programming improvement. The QA group reports the machined parts against the client specs and adds the data to the organization's database. Generally, the guaranteed documentation is electronically joined to the item all through the procedure; with the ERP framework giving specialists all the traceability alternatives required from crude material receipts to completed item shipment.
Programming organizations like btechsolutions records work process, courses of events, and testing check at the same time.
4. Dodge the disappointment costs
You can spare your organization the cost related with terrible item quality by investing the essential exertion in advance to track client programming improvement.
Able techniques for quality affirmation and robotization are exceedingly vital parts of the condition.
Without a doubt, these trials cost additional speculation of assets: see how programming quality is scaled and estimated, get the correct instruments to do it, work with QA specialists who hear what they're saying.
Take after the things specified above, and rest aussred you will have the capacity to spare stacks of cash at last;
guaranteeing that you don't need to spend a substantial bit returning and reconstructing a defective programming item after improvement.
Making an amazing tech program is costly, yet it is less exorbitant than making a low-quality one.
5. Lessening dangers
The program headway dangers can be both programmed and concentrated; that is, threats that the online space or programming won't execute obviously to or will be unreasonably ensnared, rolling out it difficult to improvement, use or keep up, while the fear that the undertaking will misuse the time or cost are programmed dangers.
The chief goal of QA devices is to reduce the likelihood of these threats. Coding standards, for instance, are made to ensure the movement of significant worth code.
On the off chance that there ought to emerge an event of no set models, the code twists up clearly open to insurability risk, and inescapable patch up by the QA group. Regardless, if set principles are created however there is no express system for ensuring that all codes meet the standard, there is an edgy threat of the base not fulfilling the necessities.
The quality assertion process is fundamental for an item progression cycle to decrease the dangers, developing quality in both the last fabricated thing and work process. To have no QA gadgets suggests extended danger for an association and the landing of inadmissible codes.
RESEARCH METHODOLOGY
Geographic Location : Bengaluru
Accepted Sample Size for the Survey : 317
Rejected Sample : 57
Type of Company : Software
Category : Small & Medium Level Enterprises
Investment : Less Than 10 Crores
Tool Used : IBM SPSS Data Collection & Analysis A) Selection of organisation
70 Software SME’s are selected on the basis of top Convenient Sampling
B) Sampling population
As many as 317 samples were included as part of data for the study. These samples were collected from Top , middle management executives & also at supervisory level
C) Data collection
An exhaustive questionnaire was prepared and data was collected with regard to Software Processes D) Stages of Data collection
Figure 1: Stages of Data Collection followed by Author
RESULTS OF QUESTIONNAIRE
Cronbach's alpha will by and large increment as the inter correlations among test things increment, and is hence known as an interior consistency gauge of dependability of test scores. Since inter correlations among test things are amplified when all things measure a similar build, Cronbach's alpha is broadly accepted to in a roundabout way show how much an arrangement of things measures a solitary unidimensional inactive develop. It is anything but difficult to appear, in any case, that tests with a similar test length and fluctuation, however extraordinary hidden factorial structures can bring about similar estimations of Cronbach's alpha. In reality, a few specialists have demonstrated that alpha can go up against very high esteems notwithstanding when the arrangement of things measures a few inconsequential inactive builds. Subsequently, alpha is most properly utilized when the things measure diverse substantive territories inside a solitary develop. At the point when the arrangement of things measures in excess of one build, coefficient is more fitting. Alpha regards any covariance among things as obvious score fluctuation, regardless of whether things covary for deceptive reasons. For instance, alpha can be misleadingly swelled by making scales which comprise of shallow changes to the wording inside an arrangement of things or by breaking down speeded tests. A normally acknowledged administer for depicting inside consistency utilizing Cronbach's alpha is as per the following, however a
_______________________________________________________________________________________________
more prominent number of things in the test can misleadingly swell the estimation of alpha and an example with a restricted range can empty it, so this lead ought to be utilized with alert.
Case Processing Summary
N %
Cases Valid 316 100.0
Excluded a 0 .0 Total 316 100.0 Reliability Statistics
Cronbach's Alpha N of Items
.808 56
It can be Observed that for 56 Questions responded by Respondents the Value of 0.808 is achieved , which means our questionnaire is Good and acceptable
SAMPLE QUESTIONNAIRE
Welcome to my PhD Questionnaire survey
Dear Participant,
I invite you to participate in a research study entitled
“Implementation & Design Model for Robust Software in Small Scale Firms” by actively participating in the survey. I am currently enrolled in the PhD Program at JAIN UNIVERSITY, Bengaluru
The study aims to achieve robust software development in a typical software development process of a software organization, and identify obstacles in applying a lean software development framework to remove such waste.
Lean software development is in conflict with many traditional values of manufacturing organizations.
Although lean may be prevalent in other parts of the organization, this does not necessarily include the IT function. IT still has a hard time comprehending the benefits of concepts such as flow, waste and value. This study might also reveal challenges in adopting lean and non value added activities. A robust model will be developed which helps small industries to easily adopt Lean and improve its efficiency and robustness.
Your participation in this research project is completely voluntary. Your responses will remain confidential and anonymous. Data from this research will be reported only as a collective combined total. If you agree to participate in this project, Please answer the questions at your best. It should take approximately 15-20 minutes to complete.
If you have any questions about this project, feel free to email me your queries
Thank you for participating in the survey. Your feedback is important.
Mr.Venkata Rao Research Scholar Under Guidance of Dr. R. Balakrishna
1. Are requirements collected and specified?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
2. As the requirements change, are the necessaryadjustments to software plans, work products, and activities made?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
3. Does the project follow a written organizationalpolicy for managing the system requirements allocated to software?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
4. Are measurements used to determine the status of the activities performed for managing the allocated requirements
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
5. Are estimates (e.g., size, cost, and schedule)documented for use in planning and tracking the software project?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
6. Do the software plans document the activities tobe performed and the commitments made for the software project?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
7. Do all affected groups and individuals agree to their commitments related to the software project?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
8. Does the project follow a written organizational policy for planning a software project?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree 9. Are adequate resources provided for planningthe software project ?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
10. Are measurements used to determine the status of the activities for planning the software project ?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
11. Does the project manager review the activities for planning the software project on both a periodic and event-driven basis?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
12. Are the project’s actual results (e.g., schedule, size, and cost) compared with estimates in the software plans?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
13. Is corrective action taken when actual results deviate significantly from the project’s software plans?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
14. Are changes in the software commitments agreed to by all affected groups and individuals?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
15. Does the project follow a written organizational policy for both tracking and controlling its software development activities?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
16. Is someone on the project assigned specific responsibilities for tracking software work products and activities ?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
17. Are measurements used to determine the status of the activities for software tracking and oversight
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
18. Are the activities for software project tracking and oversight reviewed with senior management on a periodic basis
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
19. Are software configuration management activities planned for the project?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
20. Has the project identified, controlled, and made available the software work products through the use of configuration management?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
21. Does the project follow a documented procedure to control changes to configuration items/units?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
22. Does the project follow a written organizational policy for implementing software configuration management activities?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
23. Are measurements used to determine the status of activities for software configuration management ?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
24. Are training activities planned?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
_______________________________________________________________________________________________
25. Is training provided for developing the skills and knowledge needed to perform software managerial and technical roles?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
26. Do members of the software engineering group and other software-related groups receive the training necessary to perform their roles?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
27. Does your organization follow a writtenorganizational policy to meet its training needs?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
28. Are adequate resources provided to implement the organization’s training program?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
29. Are measurements used to determine the quality of the training program?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
30. Are training program activities reviewed with senior management on a periodic basis?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
31. Are the software work products produced according to the project’s defined software process?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
32. Is consistency maintained across software work products?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
33. Does the project follow a written organizational policy for performing the software engineering activities
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
34. Are adequate resources provided for performing the software engineering tasks ?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
35. Are measurements used to determine the functionality and quality of the software products?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
36. Are the activities and work products for engineering software subjected to SQA reviews and audits ?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
37. Are peer reviews planned?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
38. Are actions associated with defects that are identified during peer reviews tracked until they are resolved?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
39. Does the project follow a written organizational policy for performing peer reviews?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
40. Do participants of peer reviews receive the training required to perform their roles?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
41. Are measurements used to determine the status of peer review activities?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
42. Are peer review activities and work products subjected to SQA review and audit?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
43. Are the activities for managing software quality planned for the project?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
44. Does the project use measurable and prioritized goals for managing the quality of its software products?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
45. Are measurements of quality compared to goals for software product quality to determine if the quality goals are satisfied?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
46. Does the project follow a written organizational policy for managing software quality?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
47. Do members of the software engineering group and other software-related groups receive required training in software quality management?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
48. Are measurements used to determine the status of the activities for managing software quality (e.g., the cost of poor quality)?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
49. Are the activities performed for software quality management reviewed with senior management on a periodic basis?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
50. Does the organization follow a plan formanaging technology changes?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
51. Are new technologies evaluated to determine their effect on quality and productivity?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
52. Does the organization follow a documented procedure for incorporating new technologies into the organization's standard software process?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
53. Does senior management sponsor the organization’s activities for managing technology change
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
54. Do process data exist to assist in the selection of new technology?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
55. Are measurements used to determine the status of the organization’s activities for managing technology change
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
56. Are the organization’s activities for managing technology change reviewed with senior management on a periodic basis?
Strongly Agree
Agree
Neither Agree nor Disagree
Disagree
Strongly Disagree
Thank you for filling the Questionnaire!
CONCLUSION
Numerous creating specialists think QA is the last advance of an assembling procedure, or even after the dispatch take it as a way to discover and settle bugs. As a product organization, become more acquainted with your item and client prerequisites to start with, building quality confirmation around the correct needs of the shopper base. QA devices guarantee a dependable, all around worked last item by social occasion prerequisites through item conveyance.
References
1. Hou Xiaoliang. Software project risk management based on CMMI Study [J].Beijing University of Posts and Telecommunications, 2012 (05).
2. Han Shaohua. Software project quality management practice analysis based on CMMI system [J]. Enterprise technology development, 2015, 4.
3. Fei Li, He Yumin, Wu Chaoying. Research on project quality management of software company based on CMMI[J]. Journal of Beihang University (SOCIAL SCIENCE EDITION), 2012, 10.
_______________________________________________________________________________________________
4. Li Feifei, Zhu Chao. Research on the quality management of enterprise software project based on CMMI [J].Shopping mall modernization, 2014, 10.
5. Ahire, S.L., & Golhar, D.Y. (2001). Quality management in large versus small firms. Journal of Small Business Management, 27, 1–13.
6. Ahire, L.S., Golhar, D.Y., & Waller, M.A.
(1996). Development and validation of TQM implementation constructs. Decision Sciences, 27, 23–56.
7. Ahire, S.L., Landeros, R., & Golhar, D.Y.
(1995). Total quality management: A literature review and an agenda for future research.
Production and Operations Management, 4(3), 277–306. Ahmed, P.K. (1998). Culture and climate for innovation. European Journal of Innovation Management, 1(1), 30–43.
8. Anderson, J.C., & Gerbing, D.W. (1988).
Structural equation modeling in practice: A review and recommended two-step approach.
Psychological Bulletin, 103, 411–423.
9. Anderson, J.C., Rungtusanatham, M., &
Schroeder, R.G. (1994). A theory of quality management underlying the Deming management method. Academy of Management Review, 19(3), 472–509.
10. Atuahene-Gima, K. (1996). Market orientation and innovation. Journal of Business Research, 35(2), 93–103.
11. Badri, M.A., Davis, D., & Davis, D. (1995). A study of measuring the critical factors of quality management. International Journal of Quality &
Reliability Management, 2(2), 36–53.
12. Baldwin, J.R., & Johnson, J. (1996). Business strategies in more and less-innovative firms in Canada. Research Policy, 25(5), 785–804.