Question

Select a keyword/term(e.g. quality)or a set of keywords/terms (e.g. quality assessment) related with the software project management class, and included into your textbook.Write a report on your keywords after investigating at least five scientific articles(must be published after 2015) by presenting briefly research purpose, methodology, and results of each paper (literature review). Provide your own comments about the contributions and limitations. Suggest a further research topic. Don’t forget to include references to your answer.

Answer 1

Research paper (keywords- quality, quality assessment ) in software development project

Paper 1

Paper name- Research on Software Quality Assurance Based on Software Quality Standards and Technology Management

Publisher – 2018 IEEE

Research purpose- This paper focuses on the relationship between software quality standards and software quality assurance.According to the software engineering international standard ISO/IEC 25000 series localization process in China, how to ensure the software quality by software standard and technology management is explored. It is pointed out that software quality needs to be guaranteed by software quality standard, software quality assessment and software test process management mechanism.With the development of computer technology, the position of software in production and life is becoming more and more important. More and more tasks are handled by the software system, and the quality of the software system determines the success or failure of this task. Therefore, we must attach great importance to software's high reliability and high quality guarantee. A defective software system will not only cause serious property loss, but also threaten the safety of personnel.

Methodology- Software testing

Result / conclusion -   With the continuous development and progress of the times, the software quality standard has made great contributions to the development and improvement of software engineering, and has created favorable conditions for software quality assurance. The high quality assurance of software needs our scientific researchers to refine and improve the standard of software quality standard continuously. Not only do we need to mine software testing methods, create automated software testing tools, and constantly improve the testing process management mechanism, but also the development of software engineering must conform to the software quality standards that are constantly developing and updating in today's society. Only in such a perfect software engineering mechanism can high quality software be developed.

Paper 2

paper name - The Impact of Software Development Process on Software Quality: A Review

publisher - 2016 8th International Conference on Computational Intelligence and Communication Networks

research purpose- Quality of software products depends upon various phase of software development process. Process of
software development is used to create and achieve quality in software products. Software development process uses four main phases which have its own importance for development. Software quality is a conformance to requirements which is
divided into functional and non-functional requirements. The objective of this paper is to present a review on the impact of
software development process on software quality. In this paper various quality attributes have been considered during
analysis of development process to see the impact on software quality. During analysis we observe that software architecture is more important phase than other phase because it provides abstract representation of overall structure of software.
In this paper we have organized the activities in software development process and analyze the impact of individual phase on various well defined attributes of quality. As we have seen every phase has an individual impact on software quality attributes.

methodology- software testing

result/conclusion - Based on analysis every phase of software development is important for software quality however software design is more important than other phase. Software design is used to capture the set of requirements and create architecture of software which realizes the broad class of requirements.In literature we have seen that every quality attributes are important but maintainability is most important attribute for software product because software maintenance is the
process of refining the software to make sure it continuous to meet business needs. Using maintainability software system or component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment. So
maintainability is important for software development process.The main finding of this analysis is software architecture play an important role to achieve quality in software products.

paper 3

paper name- A Systematic Approach to Software Quality Assurance: The Relationship of Project Activities within Project Life Cycle and System Development Life Cycle

publish- 2018 IEEE Conference on Systems, Process and Control (ICSPC 2018), 14–15 December 2018, Melaka, Malaysia

research purpose - The process of software changes is complex and constantly needed to be monitored, controlled and tracked by a systematic approach or mechanism. For the past decades, organizations invested great amount of effort, money and resources in quality management system (QMS) to ensure software change control management (SCCM) and business
operations are consistent, reliable and meeting customers’ needs. As such, it is important for every project team member
to comply and adhere to change control standards following best practices maximizing business advantages, enhancing
product quality, improving process routines and increases performance earnings. A formalized SCCM without compliance from project team is equivalence to “procedure on paper”. This paper discusses the need of joined effort from both project manager and technical team in view of organizational level achievement in software quality assurance. At the same time, this paper provides a general overview of how software change control is carried out in the context of IT Project Management. A step-by-step project activity within system development life cycle (SDLC) and project life cycle (PLC) is discussed in the paper.

methodology- software testing

result/conclusion- More and more IT organizations are venturing into the trend of SQA to stay competitive and have advantage against their competitors. Software quality is a collective team output as a result of integrated and interlinked of SCCM amongst project activities. It is necessary for all members of an organization to comply to the systemize change control process as specify in the QMS to establish a strategy, define a process and materialize it in the organization.
Fundamentally, IT organizations and IT specialists should view SCCM as a structured knowledgeacquisition/ problem-solving approach assisting company level in honing the missions of SQA. Anyhow, whether it be a technical staff or a non-technical staff, everyone in the organization should work as a team aligning towards company’s common goals that can be sustained over both the short and long term directives. We have not addressed all possible project activities in this paper. More comprehensive views of SCCM activities within PLC and SDLC would be our next target of future research. In conclusion, successful implementation of SCCM as a joint effort from both project manager and technical team has been practically and theoretically justified with literature reviews, industry business reviews and against practical consultancy work by the author. Any Malaysian IT organizations seeking to boost SCCM as part of continuous improvement to business performance should view change control mechanism as a join effort from all project team members in order to maximize business earning in the long run.

paper 4

paper - How Do Defects Hurt Qualities? An Empirical Study on Characterizing A Software Maintainability Ontology in Open Source Software

publish - 2018 IEEE International Conference on Software Quality, Reliability and Security

research purpose- Beyond the functional requirements of a system, software maintainability is essential for project success. While there exists a large knowledge base of software maintainability, this knowledge is rarely used in open source software due to the large number of developers and inefficiency in identifying quality issues. To effectively utilize the current knowledge base in practice requires a deeper understanding of how problems associated with the different qualities arise and change over time. In this paper, we sample over 6000 real bugs found from several Mozilla products to examine how maintainability is expressed with subgroups of repairability and modifiability. Furthermore, we manually study how these qualities evolve as the products mature, what the root causes of the bugs are for each quality and the impact and dependency of each quality. Our results inform which areas should be focused on to ensure maintainability at different stages of the development and maintenance process

methodology- software testing

result/conclusion- This paper studies the characteristics of maintainability in the context of 11 products found in a large open source community from analyzing reported bugs using a maintainability ontology. We mined 61790 and manually study 6372 randomly sampled bugs and categorize them into one of the subgroup SQs found in the ontology. We further study the
trend of how maintainability and its subgroup SQs change as software evolves, how related bugs are introduced in different
classifications, and how thees SQs relate to each other. Overall, our results not only provide a brand new perspective on software development with a good understanding of software maintainability, but also enlighten and contribute to the current techniques of maintainability estimation and prediction. Our findings and their implications include: (1) As software
evolves, products in client software exhibit an overall increasing trend of maintainability while products in server software
show an opposite trend. (2) Higher severity bugs express more maintainability issues compared to lower severity, which validates the importance of software maintainability measurement. (3) The most frequent relationship originates with accessibility issues, which lead to understandability issues.

paper 5

paper - Exploring the Dependency Relationships between Software Qualities

publish - 2019 IEEE 19th International Conference on Software Quality, Reliability and Security Companion (QRS-C)

research purpose- Software-intensive systems are expected to meet a variety of non-functional quality objectives essential for proper system functioning. However, there is still a lack of an effective estimation method for overall quality. Previous work has shown that it is possible to evaluate software systems’ qualities based on issue summaries; however, this requires large amounts of manual effort to employ. There is a need for automated methods which can evaluate software systems as they evolve. Moreover, system qualities do not always change independently of each other. There are various dependencies which need to be taken into consideration when looking to make quality improvements. In this paper we look to explore the dependencies between bugs and the qualities they express. We have a fuzzy classifier that uses issue summaries to identify and summarize the quality of software with respect to maintainability, thus we propose a road map which will use this classifier to explore patterns for these relations and identify potential conflicts and synergies between these means-end qualities.In this paper, we highlight a potential solution and propose a roadmap that uses the tag results provided by the classifier to identify and analyze the relationships among SQ concerns expressed in issue summaries.

methodology- software testing, bug report network

result/conclusion- In this paper, we emphasized the lack of research that has been done to explore the dependency relationships among SQs and presented the benefits of understanding such relationships. Previous work has shown that issues can be mapped to expressed SQ concerns. A fuzzy classifier has been constructed to automatically produce these mappings. Thus, we proposed an idea that utilizes the existing bug dependency relationships with these mapping results to identify potential dependency relationships among expressed SQ concerns. A preliminary analysis on several open source software identified the top dependency relationships between maintainability subgroups SQs. With the proposed roadmap, we plan to conduct further research to examine those relationships in a large empirical study. We believe that such approach can provide a more thorough high level understanding of software qualities.

my understanding and finding

as i am not sure about your question "provide your own comments about the contribution and limitation" but basically what i understand about the quality in software is that , while developing a software a customer always look for the quality product. so it is the duty of the software team to deliver a quality product to the cusomter. what quality is bascially in software language terms is the software which is bug free, software which is providing full functionality to the user, software with a best GUI. mainily a quality focus on the main term is bug. a product should be bug free it should not contain any error or bug when the customer is using the software. software quality can be achived by performing testing after the development phase for finding if there is any bug ,error,defect, fault in the product. testing can be achived by peroforming manual testing( creating test cases of different input fields,components and comparing it with the expected result) or automatic testing (using selenium tool). quality product should meets the requirement of the customer as prescribed by the customer and should be in budget given by the customer. the main and biggest thing in software phase is quality to make a quality product and after delivering it to the customer to maintain a quality product.

further research topic

designing, testing, maintenance, development