Construction of the Curriculum System of Software Engineering Based on the Agile Development Method

Under the background of“new engineering”construction,software engineering teaching pays more attention to cultivating students’engineering practice and innovation ability.In view of the inconsistency between development and demand design,team division of labor,difficult measurement of individual contribution,single assessment method,and other problems in traditional practice teaching,this paper proposes that under the guidance of agile development methods,software engineering courses should adopt Scrum framework to organize course project practice,use agile collaboration platform to implement individual work,follow up experiment progress,and ensure effective project advancement.The statistical data of curriculum“diversity”assessment show that there is an obvious improvement effect on students’software engineering ability and quality.

Research and Design of Consistent Project Cases for the Software Engineering Course Group

In order to enhance the abilities of practical innovation and solving complex engineering problems of students in the engineering context,we design a course cluster teaching model based on a unified enterprise-level project case.The program divides the knowledge points required by the project into the corresponding courses,and divides their realization into the practical teaching cases,so as to realize the design of teaching practice cases embodied in the unified project framework.This model allows students to practice projects based on the unified project background while learning knowledge from different courses.It not only allows students to learn abstract,fragmented,and difficult-to-understand knowledge systems thoroughly,but also integrates the knowledge into the practice of the enterprise-level project development,helping students experience the value of knowledge in complex engineering projects and thus improving their ability to solve complex engineering problems while learning theoretical knowledge.

Integrating Project Management, Software Development, and Knowledge Management Models: A Case Study in a Public ICT Services Organization

In project-based organizations knowledge is a critical resource used to develop and deliver products and services with a high level of quality. Therefore, a systematic and sustainable process is necessary to coordinate knowledge management, project management and product lifecycle. This scenario predominates in companies focused on the creation and maintenance of information systems. This article presents an exploratory study based on a framework that integrates cognitive, managerial, and operational processes in a public Brazilian organization that provides services in the area of information and communications technology, focusing on the construction and maintenance of information systems. Those processes are operationalized by three management models considering knowledge, project, and software development processes. Our proposal aims to understand the relationships between those three management models and their influence on the software development process in the organization under study. Our premise is based on the principle that cognitive management, project management, and software development management must be integrated to fulfill the demands of product development and service provision. The research data was composed of registers of working hours spent on software development and maintenance projects involving 244 people allocated to 5064 projects in the period from 2007 to 2013. The study resulted in the identification of the relationships among the three management models adopted by the organization, with emphasis on knowledge management activities, which were not directly identified, making it difficult to account for and measure them. We established a set of activities connected to each one of the knowledge management model phases. Since those activities were not visible before, our approach contributed to build a systematic process to register and relate activities linked to the dimensions of cognitive processes, project management, and software construction.

A Knowledge Management Framework in Software Requirements Engineering Based on the SECI Model

Software requirements engineering deals with: elicitation, specification, and validation of software requirements. Furthermore there is a need to facilitate collaboration amongst stakeholders and analysts. Fewer efforts were deployed to support them in performing their job on a day to day basis. To solve this problem we use knowledge management for software requirements engineering. This paper proposes a knowledge management framework, based on the SECI model of knowledge creation, aimed at exploiting tacit and explicit knowledge related to software requirements within a given software project. The core part of the proposed framework is a set of four sub systems “Socializer”;“Externalizer”;“Combiner”;and “Internalizer”, attached to a couple of domain ontologies and a set of knowledge assets. Indeed we aim to facilitate a semantic based interpretation of knowledge assets related to software requirements by restricting their interpretation through the application domain and software requirements ontologies. We anticipate that this framework would be very helpful for stakeholders as well as analysts to exchange and manage their knowledge within a given software project. We show in the case study, through a virtual payroll project using the two-step approach: domain level requirements plus design level requirements, how the key elicitation SRE techniques are used during the first phase of domain requirements elicitation through the four subsystems of our framework.

HV Process Model of Software Development

Software Development Life Cycle (SDLC) is one of the major ingredients for the development of efficient software systems within a time frame and low-cost involvement. From the literature, it is evident that there are various kinds of process models that are used by the software industries for the development of small, medium and long-term software projects, but many of them do not cover risk management. It is quite obvious that the improper selection of the software development process model leads to failure of the software products as it is time bound activity. In the present work, a new software development process model is proposed which covers the risks at any stage of the development of the software product. The model is named a Hemant-Vipin (HV) process model and may be helpful for the software industries for development of the efficient software products and timely delivery at the end of the client. The efficiency of the HV process model is observed by considering various kinds of factors like requirement clarity, user feedback, change agility, predictability, risk identification, practical implementation, customer satisfaction, incremental development, use of ready-made components, quick design, resource organization and many more and found through a case study that the presented approach covers many of parameters in comparison of the existing process models. .

Crowdsourced Requirements Engineering Challenges and Solutions:A Software Industry Perspective

Software crowdsourcing(SW CS)is an evolving software development paradigm,in which crowds of people are asked to solve various problems through an open call(with the encouragement of prizes for the top solutions).Because of its dynamic nature,SW CS has been progressively accepted and adopted in the software industry.However,issues pertinent to the understanding of requirements among crowds of people and requirements engineers are yet to be clarified and explained.If the requirements are not clear to the development team,it has a significant effect on the quality of the software product.This study aims to identify the potential challenges faced by requirements engineers when conducting the SW–CS based requirements engineering(RE)process.Moreover,solutions to overcome these challenges are also identified.Qualitative data analysis is performed on the interview data collected from software industry professionals.Consequently,20 SW–CS based RE challenges and their subsequent proposed solutions are devised,which are further grouped under seven categories.This study is beneficial for academicians,researchers and practitioners by providing detailed SW–CS based RE challenges and subsequent solutions that could eventually guide them to understand and effectively implement RE in SW CS.

Optimizing Bidders Selection of Multi-Round Procurement Problem in Software Project Management Using Parallel Max-Min Ant System Algorithm

This paper presents a Game-theoretic optimization via Parallel Min-Max Ant System(PMMAS)algorithm is used in practice to determine the Nash equilibrium value to resolve the confusion in choosing appropriate bidders of multi-round procurement problem in software project management.To this end,we introduce an approach that proposes:(i)A Game-theoretic model of multiround procurement problem(ii)A Nash equilibrium strategy corresponds to multi-round strategy bid(iii)An application of PSO for the determination of global Nash equilibrium.The balance point in Nash Equilibrium can help to maintain a sustainable structure not only in terms of project management but also in terms of future cooperation.As an alternative of procuring entities subjectively,a methodology to support decision making has been studied using Nash equilibrium to create a balance point on benefit in procurement where buyers and suppliers need multiple rounds of bidding.Our goal focus on the balance point in Nash Equilibrium to optimizing bidder selection in multi-round procurement which is the most beneficial for both investors and selected tenderers.Our PMMAS algorithm is implemented based on MPI(message passing interface)to find the approximate optimal solution for the question of how to choose bidders and ensure a path for a win-win relationship of all participants in the procurement process.We also evaluate the speedup ratio and parallel efficiency between our algorithm and other proposed algorithms.As the experiment results,the high feasibility and effectiveness of the PMMAS algorithm are verified.

Development and Experience of“Software Project Practice”Course for the Master of Software Engineering

Practice is an important phase in the teaching of software engineering.How to improve students' practical ability is a common problem for many software colleges.The course of Software Project Practice is proposed to enhance students' practical skills.In this course,the students participate in the whole process of software development practice and take the exercise of entrepreneurial project development in their learning stage.

The Design and Improvement of a Software Project Management System Based on CMMI

The paper researched and analyzed the characteristics, deficiencies and reasons of a management system of a software enterprise project to design a software project management system based on CMMI 1.2, thus helping the enterprise to improve development and management efficiency of software project and reduce the risks and costs on project devel- opment. It studied CMMI model version 1.3 which is recently released by SEI, analyzed its characteristics and told the difference between version 1.2 and version 1.3. In addition, an improvement proposal and a solution of the software project management system were given from multiple perspectives.

A Comprehensive Software Project Management Framework

Project management is vital for software project success. Project Management Body of Knowledge (PMBOK), CMMI for Development (CMMI-DEV), and other software project management models and practices established to assist software organizations, each of these models offers diverse focal points. Combined effective software project management practices remain a challenge to software organizations. In striving to raise the likelihood of software project success, this paper introduces a framework for software project management effectiveness which integrated a set of software project management practices based on the PMBOK guide processes, CMMI-DEV processes, and management areas that influence a software project. The proposed framework called 4PTRB which includes people, process, product, project, technology, risk, and business management areas. The 4PTRB software project management framework provides a whole comprehensive view to help software project managers to improve their project management effectiveness. The framework is validated by conducting a web-based survey of software professional practitioners around the world. A statistical analysis of twenty software projects has been conducted as a case study thereafter, spanning small to large development projects. The consistency of the case study and survey results shows the power of the 4PTRB framework as an inclusive software project management framework.

An Improved Framework for Requirement Change Management in Global Software Development

In this research, an improved framework for requirement change management in global software development (RCM_GSD) has been presented. The objective is to manage the change in requirement specifically in global software development in an appropriate manner. The proposed frame-work RCM_GSD follows the required processes of RCM and reduces the concerns of GSD. Systematic Literature Review (SLR) was conducted for exploration of relevant research. During literature study, it is analyzed that the existing techniques of change management were not suitable for global software development (GSD). The change in requirements becomes more complicated in distributed environment due to the lack of communication and collaboration among globally dispersed stakeholders. The proposed model is compared with other models proposed in recent literature and analysis is made between them;feedback was obtained from the domain experts as well. The feedback and comparison results show that the proposed model provides an appropriate solution for requirement change management in GSD.

Process Evaluation Based on Meeting Quality of Requirement Analysis Phase in Software Development Projects

We propose a metric for meeting quality in software development. Meeting is important in order to share knowledge and experience among developers and stakeholders. Most frequent and important meetings are in software requirement analysis phase. System engineers and stakeholders discuss software requirements. However, meeting quality is various. Sometimes, stakeholders feel vague decision and suspicious discussion. It is difficult to measure quantitatively the vagueness and suspicion because the vagueness and suspicion are based on human feeling. Therefore, to measure the vagueness and suspicion, our proposed metric is useful. A feature of the metric is to measure only when and who speaks in meetings, not depending on what was said. Hence, the metric does not require software domain knowledge and development experience. The metric consists of system engineers’ speaking time and the number of stakeholders’ speaking within one question by a system engineer. The metric is applied to a practical project. As a result, we automatically extract vague discussion and suspicious discussion in quantitative analysis using the metric. The number of extracted doubtful topic is 37 in all 69 topics. After that, we confirmed that the metric can predict doubtful topics that cause software faults in precision 59.5%, recall 84.5%. In addition, we found that a repeatable topic may cause software faults in requirement meetings.

Ontologies for Software Project Management: A Review

Software Project Management is a knowledge intensive process that can benefit substantially from ontology development and ontology engineering. Ontology development could facilitate or improve substantially the software development process through the improvement of knowledge management, the increase of software and artefacts reusability, and the establishment of internal consistency within project management processes of various phases of software life cycle. A large number of ontologies have been developed attempting to address various software engineering aspects, such as requirements engineering, components reuse, domain modelling, etc. In this paper, we present a systematic literature review focusing on software project management ontologies. The literature review, among other, has identified lack of standardization in terminology and concepts, lack of systematic domain modelling and use of ontologies mainly in prototype ontology systems that address rather limited aspects of software project management processes.

Study on strengthen the application of software engineering management

With the development of science and technology change quickly, the technology of the computer field is becoming more and more perfect and progress, and the development of computer software is also more extensive. It provides a simple, scientific and technological solution for many fields. The high development of information bring digitized concept to every sections. So, Software development, operation, testing and other steps will be affect by those fields. Therefore, the development of the software industry needs to improve the management efficiency, and improve the efficiency of product development in the whole process.

The Analysis and Proposed Modifications to ISO/IEC 25030—Software Engineering—Software Quality Requirements and Evaluation—Quality Requirements

The quality of the software product is a crucial factor that contributes to its success. Therefore, it is important to specify the right software quality requirements that will establish the basis for desired quality of the final system/software product. There are several known methodologies/ processes that support the specification of the system/software functional requirements starting from the user needs to finally obtain the system requirements that the developers can implement through their development process. System/software quality requirements are interdependent with functional requirements, which means that the system/software quality requirements are meant to be specified in parallel with the latter. The ISO/IEC 25000 [1] SQuaRE series of standards include the standard ISO/IEC 25030—Software engineering—Software Quality Requirements and Evaluation—Quality requirements [2], which has as main goal to help specify software quality requirements. As to date, this standard does not offer clear and concise steps that a software quality engineer could follow in order to specify them. This article presents modifications recommended for ISO/IEC 25030 standard, with, among the others, a new requirements definition process that allows for specifying the system/software quality requirements taking into account the existing published system and software quality model ISO/IEC 25010 [3] as well as all the stake- holders of the project.

A Defect Detection Method for the Primary Stage of Software Development

In the early stage of software development,a software requirements specification(SRS)is essential,and whether the requirements are clear and explicit is the key.However,due to various reasons,there may be a large number of misunderstandings.To generate high-quality software requirements specifications,numerous researchers have developed a variety of ways to improve the quality of SRS.In this paper,we propose a questions extraction method based on SRS elements decomposition,which evaluates the quality of SRS in the form of numerical indicators.The proposed method not only evaluates the quality of SRSs but also helps in the detection of defects,especially the description problem and omission defects in SRSs.To verify the effectiveness of the proposed method,we conducted a controlled experiment to compare the ability of checklist-based review(CBR)and the proposed method in the SRS review.The CBR is a classicmethod of reviewing SRS defects.After a lot of practice and improvement for a long time,CBR has excellent review ability in improving the quality of software requirements specifications.The experimental results with 40 graduate studentsmajoring in software engineering confirmed the effectiveness and advantages of the proposed method.However,the shortcomings and deficiencies of the proposed method are also observed through the experiment.Furthermore,the proposed method has been tried out by engineers with practical work experience in software development industry and received good feedback.

The Reform Scheme of Practice-Courses Cooperation Training Pattern of Software Engineering Major of Overseas Chinese Universities

How to improve the employment of software engineering graduates, especially, how to effectively enhance the employment competitiveness of relevant overseas students in the context of "One Belt and One Road" is one of the core tasks of overseas Chinese universities. This paper proposes a reform plan for the practical training mode of school-enterprise cooperative project in the software engineering of overseas Chinese universities. The reform plan combines education concepts with practical research and development. It subdivides students and according to the characteristics of different types of students, and is carried out on campus, outside campus(in the province), and abroad(original area), which makes senior undergraduates fully understand the needs of enterprises, constantly improve their professional practice ability, and improve their competitiveness. Thus, the professional innovation and entrepreneurship ability of students is enhanced, and it also reduces the cost of employee entry.

Software Project’s Complexity Measurement: A Case Study

Project management is a well understood management method, widely adopted today, in order to give predictable results to complex problems. However, quite often projects fail to satisfy their initial objectives. This is why studying the factors that affect the complexity of projects is quite important. In this paper, we will present the complexity factors that are related to project time, cost and quality management and then we will apply them to a number of selected projects, in order to compare the acquired results. The projects have been chosen in a way that results can be easily compared.

A Novel Method for Assessing and Optimizing Software Project Process Based Risk Control

A new approach for assessing and optimizing software project process based on software risk control presented, which evaluates and optimizes software project process from the view of controlling the software project risks. A model for optimizing software risk control is given, a discrete optimization algorithm based on dynamic programruing is proposed and an example of using above method to solve a problem is also included in this paper. By improving the old passive post-project control into an active effective preaction, this new method can greatly promote the possibility of success of software projects.