MAKE THE QUALITY OF SOFTWARE PRODUCT IN THE VIEW OF POOR PRACTICES BY USING SOFTWARE QUALITY MANAGEM

Journal for Research | Volume 03| Issue 01 | March 2017 ISSN: 2395-7549

Make the Quality of Software Product in the View of Poor Practices by using Software Quality Management Panthangi Venkateswara Rao Assistant Professor Department of Computer Science & Engineering B.V.R.I.T, Narsapur, Medak Dist, Telangana-502313, India

Dr. Katta Subba Rao Professor Department of Computer Science & Engineering B.V.R.I.T, Narsapur, Medak Dist, Telangana-502313, India

Abstract In the Software Engineering, One of the most important factors to impact national and international business is quality of software and its assurance. Integral part of software development cycle is SQA, evaluation of software Quality product when compared to other industrial projects and it is very highly difficult. For developing, performance, speed, maintaining the quality, cost and efficiency of the software, SQA activities, principles and its methods are implemented in the early stages of the software engineering development phases. Where in this paper there is little visibility of lack of software Quality product in the view of poor practices. Hence we proposed a new system with best practices in software quality management to make the best quality product. This System works on Gain Better Visibility into Supplier Quality with Technology.

Keywords: Software Engineering, Software quality Assurance (SQA), Software quality Product, Software Quality Management _______________________________________________________________________________________________________ I.

INTRODUCTION TO SOFTWARE QUALITY MANAGEMENT

Software Quality is a complex collaborative process. Each organization has their own preferred software development process to get their respective standards for the product developed. Where each uniquely selected process models help to guide, support and advice software developers prescribing what activities they have to follow for gaining a qualitative product. As software engineering is critically dependent on unique abilities of creative people involved in those process. To obtain coherence in the organization focusing on the process is important, reworking allows peop0le to learn more about the process considered and brings process to life. Where reworking allows people to learn, innovate and deal with contingences, they are thus an essential part of software development for developing a product.

II. POOR ACQUISITION PRACTICES (EXISTING SYSTEM) In the View of Poor acquisition Practices, there is a little visibility to see the lack of software product Quality.

Where in this system visibility plays a major role. Visibility is a process which shows the abilities to measure progress or status against goals. In software engineering visibility principle is mainly in the form of process visibility and mainly in form of scheduling visibility which shows the ability to judge the state of development against scheduling. To gain qualitative goals qualitative process visibility is also applied. Visibility indeed is also known as observability which has ability to extract required information from a software art craft. Visibility of progress largely determines the architectural design and build plan of the system. What is visibility within the supply chain? Most basic definition is tractability of products from manufacturer to final destination. Where they could be components or parts used to make a final product. In a wide way visibility is increase of available data which analyzes to make recommendations and determine strategies which improve and strengthen supply chain.

There are particularly different levels of visibility whereas risks in supply chain continue to be occurring and customer demand which continues to be less understanding of disruptions, most of the companies are recognizing importance of developing and managing the supply chain.

III. BEST PRACTICES IN THE SOFTWARE QUALITY MANAGEMENT (PROPOSED SYSTEM) Gain Better Visibility into Supplier Quality with Technology.

By stream lining and automating workflows technology makes quality management process simpler and more efficient which helps for a work flow such as supplier performance monitoring and quality risk assessments. Easy to access remote supplier locations (even without network connectivity) by using advanced tools such as offline and mobile auditing applications.

Decision-making can be done using interactive reports, dashboards and analytics can add further value by helping you harness supplier quality information from enterprise, slicing and dicing data from various angles and pull out timely and intelligent

All rights reserved by www.journal4research.org

86

Make the Quality of Software Product in the View of Poor Practices by using Software Quality Management (J4R/ Volume 03 / Issue 01 / 018)

insights. Where we can drill down to analyze the data in detail by shifting multiple spreadsheets and word documents by which we get a qualitative and require information we needed in a common view.

One of the biggest challenges companies face is lack of efficient and timely visibility of supplier quality in global supply chain. Integration of supplier data in centralized system with help of technology is done by mapping each supplier to be associated products/ingredients, risks, policies, controls and issues. Which in return helps to get a comprehensive, cohesive view of supplier quality which in turn enhances traceability and accountability for issues raised.

Fig. 1: Visibility between Supplier and Consumer

From the above figure1 visibility depends on transportation and warehousing to reach consumer, if there is any mismatch to visibility complains to supplier.

IV. CONCLUSION This paper has little visibility of lack of software product quality,it means poor acquisition practices. To develop more visibility of lack of software product quality, we proposed best practices in the Software Quality Management which mean Gain Better Visibility into Supplier Quality with Technology. The best visibility concept is “Visibility between Supplier and Consumer”,i.e. shown in the above figure..This Supplier consumer method is one of the Visibility process method.

REFERENCES [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

A. Graesser and S. Franklin, “Is it an agent, or just a Program?” Taxonomy for Autonomous Agents”. In Proceedings of the Third International Workshop on Agents Theories, Architecture, and Languages, Springer-Verlag, 1996.

Chen, F, Nunamaker, J. F., Romano, N. C. & Briggs, R. O. (2003). Collaborative project management architecture”. Proceedings of the 36th Hawaii International Conference on System Sciences. Big Island, Hawaii.

D’Inverno, M. & Luck, M. (2001). “Understanding Agent Systems”. Berlin: Springer-Verlag.

Leonard Foner, "What's an Agent Anyway?", Agents Memo 93-01, Agents Group MIT Media Lab, 1993.

Michael Wooldridge and Nick Jennings, Dept. of Computer science, Manchester Metropolitan University,IEEE Review Jean Paul Paquin, Jean Couillard, and Dominique J. Ferrand, Assessing and Controlling the Quality of a Project End Product: The Earned Quality Method, IEEE TRANSACTIONS ON ENGINEERINGMANAGEMENT, VOL. 47, NO. 1, FEBRUARY 2000 White Papers Borland the open ALM Company, Software Quality Management, White paper April 2006 Books Staffordshire University, Software Quality: Definitions and Strategic Issues School of Computing Report, Ronan Fitzpatrick, April 1996. Websites www.dti.gov.uk/quality/q Barker, J. (1992),Future Edge: Discovering the Paradigms of Success William Morrow and Company Inc., New York, NY Budlong, F. and Peterson, J. (1996), “Software metrics, capability evaluation methodology and implementation”, Cros-Talk January, pp. 15-19 McManus, J. (2000), “Quality meets process improvement”, Management Services Journal Nos. 5, pp.

Paulk, M. (1993), Capability Maturity Model, Version 1.1 Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA TickIT(1992),AGuidetoSoftwareQualityManagementSystemConstructionandCertificationusingEN29001(ISO 9001)Issue 2.0, 28 February, UK Department of Trade andsIndustry, London.

Rangarajan,K.,Swaminathan,N.,Hedge,V.andJacob,J.(2001),“Productqualityframework:avehicleforfocusing on product quality goals”, Software Engineering NotesVol. 26 No. 4,pp. 77-82 Sanders,J.andCurran,E.(1994),SoftwareQuality:AFrameworkforSuccessinSoftwareDevelopmentandSupport, Addison-Wesley, Reading, MA. Budlong, F. and Peterson, J. (1996), “Software metrics, capability evaluation methodology and implementation”, Cross-Talk January, pp. 15-19 K.Subba Rao, P.Babual Saheb, Dr.L.S.S Reddy Published a Internal Journal on “Reuse of Software in Distributed System Components “International Journal of Scientific Engineering and Technology (IJSETR).

K.Subba Rao, Dr. L.S.S Reddy published a International journal on “Measurement model of software Quality in users Perception “International Journal of Research in Engineering and Technology (IJRET).

Norman f. Schneidewind, Knowledge Requirements for Software quality measurement

All rights reserved by www.journal4research.org

87