Software engineering education: A study on conducting collaborative senior project development

Project and teamwork training is recognized as an important aspect in software engineering (SE) education. Senior projects, which often feature industrial involvement, serve the function of a ‘capstone course’ in SE curricula, by offering comprehensive training in collaborative software development. Given the characteristics of student team projects and the social aspects of software development, instructional issues in such a course must include: how to encourage teamwork, how to formalize and streamline stakeholder participation, and how to monitor students’ work, as well as sustain their desired collaborative effort throughout the development. In this paper, we present an exploratory study which highlights a particular case and introduces the meetings-flow approach. In order to investigate how this approach could contribute to the project's results, we examined its quantitative benefits in relation to the development of the project. We also conducted focus group interviews to discuss the humanistic findings and educational effects pertaining to this approach.     

Change the face of software engineering education: A field report from Taiwan

Context: In Taiwan, the supply of software engineers provided by universities has suffered from both a quantity problem and a quality problem. An effort to change the software engineering education is in need.Objective: The Software Engineering Consortium (SEC) of Taiwan sets its objective to increase the number of college graduates that are better prepared for filling software development and maintenance jobs.Method: Four dysfunctions: avoidance of process, inattention to modeling, lack of awareness to software quality, and chasm between application domains and software engineering, of the current situation are identified. The effort to correct the dysfunctions involves design of a module-oriented software engineering curriculum, and organization of people, resource, and activities.Results: In the academic years from 2003 to 2008, both the number of software engineering courses offered and the enrollment size increased significantly by a space of some 250 courses and 5000 enrollments, respectively.Conclusion: The SEC effort to establishing software engineering modules has been received with enthusiasm by faculty members and students of the participating institutes. Inspired by the important foundational work such as SWEBOK and SE2004, we believe that the adopted strategy of identifying dysfunctions and then designing remedies to address these dysfunctions contributed significantly to the success of the SEC effort.     

Empirical research methodologies and studies in Requirements Engineering: How far did we come?

Since the inception of the RE conference series (1992), both researchers and practitioners in the RE community have acknowledged the significance of empirical evaluation as an instrument to gain knowledge about various aspects of RE phenomena and the validity of our research results. A significant number of empirical studies have been conducted in the search for knowledge about RE problems as well as evidence of successful and less successful application of proposed solutions. This editorial presents the progress empirical RE research has made since 1992. Based on a search in the Scopus digital library, we report from an analysis of peer-reviewed systematic literature reviews and mapping studies to showcase major areas of RE research that use methods from the Empirical Software Engineering paradigm. We summarize prior empirical research in RE and introduce the contributors to this special issue on empirical research methodologies and studies in RE.     

Mechatronics engineering education and dissemination program

For evolution of Mechanical System Technology, a simplified mechanism with sophisticated electronics control are replacing the traditional pure mechanical system. The new technology which combines the mechanical system with electronics control is being referred to as Mechatronics Technology and explosively growing in all over the industrialized countries. The paper describes, the concept and essential technology components of the mechatronics technology and the methodology and implementation of the Mechatronics Engineering Education.     

Software engineering: An example of misuse

Managers of programmers and designers are sometimes wont to adopt the new and shiny. This paper describes a situation in which managers at several levels grasped for the ‘new and shiny’ in the form of software engineering. This approach was not without its hidden dangers, especially when established guidelines were ignored or violated. The results of an experience with a large software project are reported. This project dealt with a sophisticated inventory control system. The effects on the project of ignorance and the violation of rules are described. Several measures of the final product are reported. Observations of the authors conclude the paper.     

Software cost estimation: Present and future

The state-of-the-art in software cost estimation is reviewed. The estimated cost of a software system varies widely with the model used. Some variation in cost estimation is attributable to the anomolies in the cost data base used in developing the model. The other variations, it is claimed are due to the presence or absence of certain ‘qualities’ in the final product. These qualities are measures of ‘goodness’ in design, development, and test-integration phases of software. To consider quality as a driver of software cost, we have suggested an association between cost and quality and have proposed a way to use quality metrics to estimate software cost.     

Socio-technical systems: From design methods to systems engineering

It is widely acknowledged that adopting a socio-technical approach to system development leads to systems that are more acceptable to end users and deliver better value to stakeholders. Despite this, such approaches are not widely practised. We analyse the reasons for this, highlighting some of the problems with the better known socio-technical design methods. Based on this analysis we propose a new pragmatic framework for socio-technical systems engineering (STSE) which builds on the (largely independent) research of groups investigating work design, information systems, computer-supported cooperative work, and cognitive systems engineering. STSE bridges the traditional gap between organisational change and system development using two main types of activity: sensitisation and awareness; and constructive engagement. From the framework, we identify an initial set of interdisciplinary research problems that address how to apply socio-technical approaches in a cost-effective way, and how to facilitate the integration of STSE with existing systems and software engineering approaches.     

Software engineering article types: An analysis of the literature

The software engineering (SE) community has recently recognized that the field lacks well-established research paradigms and clear guidance on how to write good research reports. With no comprehensive guide to the different article types in the field, article writing and reviewing heavily depends on the expertise and the understanding of the individual SE actors.In this work, we classify and describe the article types published in SE with an emphasis on what is required for publication in journals and conference proceedings. Theoretically, we consider article types as genres, because we assume that each type of article has a specific function and a particular communicative purpose within the community, which the members of the community can recognize. We draw on written sources available, i.e. the instructions to authors/reviewers of major SE journals, the calls for papers of major SE conferences, and previous research published on the topic.Despite the fragmentation and limitations of the sources studied, we are able to propose a classification of different SE article types. Such classification helps in guiding the reader through the SE literature, and in making the researcher reflect on directions for improvements.     

Software product line scoping and requirements engineering in a small and medium-sized enterprise: An industrial case study

Software product line (SPL) engineering has been applied in several domains, especially in large-scale software development. Given the benefits experienced and reported, SPL engineering has increasingly garnered interest from small to medium-sized companies. It is possible to find a wide range of studies reporting on the challenges of running a SPL project in large companies. However, very little reports exist that consider the situation for small to medium-sized enterprises and these studies try develop universal truths for SPL without lessons learned from empirical evidence need to be contextualized. This study is a step towards bridging this gap in contextual evidence by characterizing the weaknesses discovered in the scoping (SC) and requirements (RE) disciplines of SPL. Moreover, in this study we conducted a case study in a small to medium sized enterprises (SMEs) to justify the use of agile methods when introducing the SPL SC and RE disciplines through the characterization of their bottlenecks. The results of the characterization indicated that ineffective communication and collaboration, long iteration cycles, and the absence of adaptability and flexibility can increase the effort and reduce motivation during project development. These issues can be mitigated by agile methods.     

Software engineering as a scientific and engineering discipline

A new interpretation of software engineering from scientific, engineering, and practical standpoints is proposed. Software engineering is defined as a successor of programming and computer science, namely, its management theory. Features and attributes of software engineering as an original discipline are founded. The structure, content, and concepts of this discipline and its basic elements are presented. __________ Translated from Kibernetika i Sistemnyi Analiz, No. 3, pp. 19–28, May–June 2008.     

Evaluation of a game to teach requirements collection and analysis in software engineering at tertiary education level

A highly important part of software engineering education is requirements collection and analysis which is one of the initial stages of the Database Application Lifecycle and arguably the most important stage of the Software Development Lifecycle. No other conceptual work is as difficult to rectify at a later stage or as damaging to the overall system if performed incorrectly. As software engineering is a field with a reputation for producing graduates who are inappropriately prepared for applying their skills in real life software engineering scenarios, it suggests that traditional educational techniques such as role-play, live-through case studies and paper-based case studies are insufficient preparation and that other approaches are required. To attempt to combat this problem we have developed a games-based learning application to teach requirements collection and analysis at tertiary education level as games-based learning is seen as a highly motivating, engaging form of media and is a rapidly expanding field. This paper will describe the evaluation of the requirements collection and analysis game particularly from a pedagogical perspective. The game will be compared to traditional methods of software engineering education using a pre-test/post-test, control group/experimental group design to assess if the game can act as a suitable supplement to traditional techniques and assess if it can potentially overcome shortcomings. The game will be evaluated in five separate experiments at tertiary education level.     

Software engineering projects may fail before they are started: Post-mortem analysis of five cancelled projects

Context

Software project cancellations are often caused by mistakes made during the project, and such cancellations make a strong economic impact. We analyzed five cancelled software engineering projects. One case was an internal product development project of a company that sells products to its customers. The other four cases were different software engineering projects, and outcomes of these projects were planned to be delivered to external customers.

Objective

This study reports a post-mortem analysis of five software engineering projects with the aim of providing more knowledge about the reasons for cancellation decisions and the causes behind those reasons.

Methods

The research method is case study. A method for a document-based post-mortem analysis was developed and post-mortem analysis was performed. All project documentation was available for analysis.

Results

The reasons for the cancellation decisions were well-known ones. In four cases of five, the outcome of the project was to be delivered to an external customer, but in these cases the causes of the cancellation reasons were not found from the normal project documentation. In these cases the cause of the cancellation originated in a phase before the start of the project and therefore the project was doomed before it was started.

Conclusion

It is reasonable to suggest that a remarkable portion of project cancellations are due to mistakes made before the project is started in the case of contract-based software engineering projects.     

Software and systems engineering process capability in the South Australian defence industry

It is well recognised that that there is a correlation between process maturity in large organisations and project success. In response to this, a number of process models and standards have been developed for the large-project environment. The Australian defence industry, unlike many overseas countries, relies to a much greater extent on small and medium-sized enterprises to supply equipment and services. Hence, the question has arisen about the scalability of overseas concepts to the Australian defence industry situation. To address this question, a research project has been undertaken to identify the current baseline of process capability for the South Australian defence software and systems engineering industry. This paper presents findings from the research project, including a general characterisation of the industry process capability and a discussion of the common perceived strengths and challenges of organisations within the industry. The project’s objectives, research design and findings are then compared and contrasted with similar research activities conducted in different parts of the world. Finally, the paper draws conclusions based on the body of work presented and suggests areas for future research and development to address industry needs.     

A practitioner’s guide to light weight software process assessment and improvement planning

Software process improvement (SPI) is challenging, particularly for small and medium sized enterprises. Most existing SPI frameworks are either too expensive to deploy, or do not take an organizations’ specific needs into consideration. There is a need for light weight SPI frameworks that enable practitioners to base improvement efforts on the issues that are the most critical for the specific organization.

This paper presents a step-by-step guide to process assessment and improvement planning using improvement framework utilizing light weight assessment and improvement planning (iFLAP), aimed at practitioners undertaking SPI initiatives. In addition to the guide itself the industrial application of iFLAP is shown through two industrial cases. iFLAP is a packaged improvement framework, containing both assessment and improvement planning capabilities, explicitly developed to be light weight in nature. Assessment is performed by eliciting improvements issues based on the organization’s experience and knowledge. The findings are validated through triangulation utilizing multiple data sources. iFLAP actively involves practitioners in prioritizing improvement issues and identifying dependencies between them in order to package improvements, and thus establish a, for the organization, realistic improvement plan. The two cases of iFLAP application in industry are presented together with lessons learned in order to exemplify actual use of the framework as well as challenges encountered.     

Planning and design of industrial engineering education quality

A Quality Function Deployment (QFD) approach to improve industrial engineering (IE) education quality at the Middle East Technical University (METU) is presented. Major stakeholders of IE education are identified as students, faculty members and future employers of the students. Requirements of these groups from an IE graduate are determined by surveys and interviews with them. These requirements are prioritized. Main education requirements are identified to meet the stakeholders' requirements. Finally, the results and plans for future studies are given.     

关于提高软件工程专业学生工程能力的探索与思考

针对我国计算机软件相关专业“产销不对路”的教育现状,围绕工程教育的集成性和实践性,对软件工程专业实践教学进行了研究,提出了工程化实践教学的总体思路,并对四类实践课程进行工程化改造,通过校企合作推出工程项目实训,为构建工程化实践教学新体系做出了有益尝试。     

Potential and limitations of the ISBSG dataset in enhancing software engineering research: A mapping review

ContextThe International Software Benchmarking Standards Group (ISBSG) maintains a software development repository with over 6000 software projects. This dataset makes it possible to estimate a project’s size, effort, duration, and cost.ObjectiveThe aim of this study was to determine how and to what extent, ISBSG has been used by researchers from 2000, when the first papers were published, until June of 2012.MethodA systematic mapping review was used as the research method, which was applied to over 129 papers obtained after the filtering process.ResultsThe papers were published in 19 journals and 40 conferences. Thirty-five percent of the papers published between years 2000 and 2011 have received at least one citation in journals and only five papers have received six or more citations. Effort variable is the focus of 70.5% of the papers, 22.5% center their research in a variable different from effort and 7% do not consider any target variable. Additionally, in as many as 70.5% of papers, effort estimation is the research topic, followed by dataset properties (36.4%). The more frequent methods are Regression (61.2%), Machine Learning (35.7%), and Estimation by Analogy (22.5%). ISBSG is used as the only support in 55% of the papers while the remaining papers use complementary datasets. The ISBSG release 10 is used most frequently with 32 references. Finally, some benefits and drawbacks of the usage of ISBSG have been highlighted.ConclusionThis work presents a snapshot of the existing usage of ISBSG in software development research. ISBSG offers a wealth of information regarding practices from a wide range of organizations, applications, and development types, which constitutes its main potential. However, a data preparation process is required before any analysis. Lastly, the potential of ISBSG to develop new research is also outlined.     

The use of Nassi-Shneiderman charts and supporting tools in software engineering education

In 1973 Nassi and Shneiderman proposed a new form of flowchart which was advocated as being better suited to the practices of structured programming. It is argued that Nassi-Shneiderman charts (N-S charts) provide a convenient common framework for the communication and practice of other widely accepted ideas concerning software development. They can for example be used to promote top-down design, structured implementation, thorough testing and graphical documentation. This paper relates experiences using N-S charts in a University educational environment and describes some tools which have been developed to support use of the charts.     

RoboCup: Today and tomorrow—What we have learned

RoboCup is an increasingly successful attempt to promote the full integration of AI and robotics research. The most prominent feature of RoboCup is that it provides the researchers with the opportunity to demonstrate their research results as a form of competition in a dynamically changing hostile environment, defined as the international standard game definition, which the gamut of intelligent robotics research issues are naturally involved. This article describes what we have learned from the past RoboCup activities, mainly the first and the second RoboCups, and overviews the future perspectives of RoboCup in the next century. First, the issue on what and why RoboCup is addressed, and a wide range of research issues are explained. Next, the current leagues are introduced and the research achievements are reviewed from a viewpoint of system architecture. Some of these achievements are included in this special issue. Finally, prospects for future activities are discussed.