I need ppt slides around 13 about the give journal
MITS5501 Software Quality, Change Management and Testing Assignment 1 Paper presentation and participation MITS5501 Assignment 1 Copyright © 2015-2019 VIT, All Rights Reserved. 2 NOTE: This Document is used in conjunction with Assessment 1 [Paper presentation & participation] and Assessment 2 [Research Report] in the Teaching and Assessment Plan document [MITS5502_Teaching and Assessment Plan.doc] Objective(s) This assessment item relates to the unit learning outcomes as in the unit descriptor. This assessment is designed to improve student presentation skills and to give students experience in researching a topics relevant to the Unit of Study subject matter. INSTRUCTIONS For this assignment you are required to do a 10-12 minutes presentation on an academic paper on Software Quality, Software Change Management or Software Testing. The paper you select must be directly relevant to these 3 topics. The paper can be from any academic conference or other relevant Journal or online sources such as Google Scholar, Academic department repositories etc... All students must select a different paper; thus the paper must be approved by your lecturer or tutor before proceeding. In case two students are wanting to present on the same paper, the first who emails the lecturer or tutor with their choice will be allocated that paper. A grade of 10% of the Units mark will be awarded for your presentation and your participation in other student presentations. Prepare a PowerPoint slide presentation for your presentation. Note: This is an individual assessment, students need to select their own individual paper for assignment 2 (see assignment 2 specifications). The presentations recorded video should be submitted in Moodle drop box, no submissions are considered via email or any other way/medium. What to Submit. After your presentation video, if your presentation slides are not visible in the video you are required submit the presentation slides in Moodle drop box. MITS5501 Assignment 1 Copyright © 2015-2019 VIT, All Rights Reserved. 3 Appendix- I - Marking Guide: Criteria (the criteria may be used to help guide in marking only for consistency across campuses and cohorts) Tick appropriate columns and insert marks for each criterion. Total marks are scaled to 10% i.e. weightage of the assignment 1 in the unit Marks F F to D D to C C to B B A Topic The topic chosen was relevant to the Unit and material being studied Purpose The speaker clearly identified the intent and major points of the paper Overview The speaker provided a good overview of the paper being discussed Discussion The Speaker gave a well-structured presentation and discussion Summary The speaker clearly summarizes and discusses the content of the article(s) Conclusion Identifies and discusses the article’s conclusions Overall Oral Presentation Presenter addressed the audience, was clear and confident and explained key concepts in the slides and within time Other Material Uses material from other Authors Overall Visual Presentation Visual Material was well organized, clear, use of images / charts easy to understand and of appropriate length Total Marks (out of 90) [Individual marks awarded may apply deductions e.g. Upto 25% deduction applies if participation in other peers/groups presentation is less than 70% and upto 30% deduction applies based on student’s individual contribution in the presentation. The deductions are applied by the lecturer based on their assessment of participation or asking one or two questions during the presentations.]. Comments [Along with marks awarded, additional verbal or written comments (in questions/discussions during presentation) may also be provided lecturers/tutors/peer-students]. MITS5501 Assignment 1 Copyright © 2015-2019 VIT, All Rights Reserved. 4 Greening Software Requirements Change Management Strategy Based on Nash Equilibrium Research Article Greening Software Requirements Change Management Strategy Based on Nash Equilibrium Zhixiang Tong,1 Xiaohong Su,1 Longzhu Cen,2 and TiantianWang1 1School of Computer Science and Technology, Harbin Institute of Technology, Harbin 150001, China 2School of Science, Harbin Institute of Technology, Harbin 150001, China Correspondence should be addressed to Xiaohong Su; sxh@hit.edu.cn Received 13 July 2017; Revised 4 September 2017; Accepted 19 September 2017; Published 10 December 2017 Academic Editor: Zhi Liu Copyright © 2017 Zhixiang Tong et al. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited. Recently, green computing has becomemore andmore important in software engineering (SE), which can be achieved by effectively recycling the software system and utilizing the computing resources. However, the requirement change may lead to unnecessary labor and time cost.Moreover, it may also result in the waste of hardware and computing resources once unreasonable requirements are realized. Thus, to perform green computing in SE, it is necessary to propose effective strategies to manage the requirement change. For this decision-making problem, game theoretical methods can be feasible solutions. In this paper, we propose a novel requirement change management approach based on game theory. Specifically, we model the problem as a game between the stakeholders and the developer and devise the payoff matrix between different strategies of the players. We then propose a Nash equilibrium-based game theoretical algorithm to manage requirement change. The evaluation results show that, compared to the exhaustive algorithm, our method not only can achieve almost the same optimal results but also can significantly reduce the computational time complexity.Thus, ourmethod is feasible for a lot of requirement changes and can facilitate the green computing targets from the perspective of software engineering. 1. Introduction Software is the fundamental part of the computing system. Greenness in the software is an emerging quality attribute that needs to be taken into account in each phase of the software development process involving requirement engineering (RE), the system implementation, testing, and maintenance. To support efficient computing paradigms, it is necessary to design effective software requirements management methods. Requirement engineering is one of the most important phases of the software development process and is able to reduce software errors at its early stage. “Variability” is an important feature in the software requirements, and a lot of software system development issues arise from requirement changes. Existing researches indicate that before the software products are formally put into use over 50% of the software requirements will be changed [1]. Requirement change results from adding, deleting, or updating requirements will lead to a series of serious problems in techniques, quality, management, and so forth, whichmay cause software failure.Thus, how to respond to requirement changes is essential for the survival of the software products. When the software requirement changes, if the project proceeds without judgments or evaluation on the changes, it may disrupt the control and management. In the software developing process, it is necessary to formulate feasible solutions to evaluate the impacts of the requirement change from various aspects such as cost, developing period, quality, and user satisfaction, aiming to provide evidence on making a proper decision. These solutions are essential to ensure the overall success of the software development project. In the past decades, a number of models have been proposed to describe and analyze the requirement change management [1–9]. On one hand, some studies focus on for- mal descriptions of requirement changes, such as Kobayashi and Maekawa [1] who came up with an NBM (Need-Based requirement change Management) model, which describes system requirements in 4W (Where, Who, Why, and What). Hindawi Wireless Communications and Mobile Computing Volume 2017, Article ID 4020162, 10 pages https://doi.org/10.1155/2017/4020162 https://doi.org/10.1155/2017/4020162 2 Wireless Communications and Mobile Computing This model monitors and processes requirement changes during the entire software development cycle by the way of validation and verification. Ramzan and Ikram describe the software requirement change management process as a processmodel, which consists of activities, roles, and artifacts [2]. Ahmad et al. present a model to minimize the impact of requirement change through classifying the requirements into three different categories: fixed, less likely to change, and most likely to change [9]. On the other hand, some studies have proposed specific methods and procedures for the management of changes. Bhatti et al. propose a change management approach that includes six basic phases [3]. According to this approach, Change Control Board (CCB) evaluates the effects of requirement changes in various aspects of the system; then CCB, QA (Quality Assurance) team, the requirement change proposer, and project group members should reach a collective agreement on whether to accept or reject this change. The Spiral of Change model is a change management method that includes change propos- ing, decision-making, and technology implementation, and whether to implement the change is determined by the change owner [4]. Recently, Tomyim and Pohthong propose a requirement change management model especially for object-oriented software engineering using unified modeling language [10]. Oertel and Rettberg present a change man- agement approach that measures the effects of a change by integrating the verification and validation activities and the propagation of changes [11]. However, most of the existing models lack the impact analysis and decision-making process for requirement changes. The impact analysis means deter- mining the impact of requirement changes on the software developing processes, such as the impact on the cost or benefit for the developer and the satisfaction for the stakeholders, which will help to provide decision-making on implementing a change scientifically, reasonably, and accurately. In addition, most of the previous methodologies depend a lot on the human role which relies on the interest and experience of the decision-makers, and they also lack detailed descriptions of the decision methods. These problems will affect the reproducibility of the results of a change. Some researchers emphasize that using the agent-oriented process to improve software productivity may be a novel model in require- ment change management (RCM) [12–14]. Bendakir et al. develop an agent-oriented approach based on the definition of the process covering all the necessary activities for an effective RCM process [15]. The adaptability, perception, and cooperation features of the model allow managing the change requirements in a controlled manner. In summary, the requirement change impact measurement, the change management automation, and the adjustment strategy for the systemafter accepting the changes are still crucial problems in RCM [16–18]. Although a set of requirement change