Software Engineering Project Management Research Articles

Performance Evolution of Software Engineering Development and Project Management: A Critical Evolution Software Engineering Process

Among the many pressing concerns in the realm of computers, software project development is among the highest. System development life cycle is a part of this (SDLC). A key goal of the software development life cycle (SDLC) is to reduce the likelihood of errors while improving the quality of the final result. Without a well-defined set of steps, the software development process is a pretty complicated affair. Method established to standardize and streamline software development. The introduction of the SDLC (Software Development Life Cycle) existence. What we have here is a methodical and organized approach to the process of creating software. Using the SDLC as a guide, entails a wide variety of steps and processes that must be completed before the final programmer is released. Software comes in many forms. Types of software development life cycles, each with their own benefits and drawbacks, are commonly employed in the software development process. Disadvantages Five of these software development life cycle (SDLC) models, including the waterfall model, the v-shaped model, and the prototype model, are presented in this study. Existing models are compared using a spiral and an iterative structure.

Logical framework of information technology: Systematization of software development research

This article aims to present a comprehensive Logical Framework for Information Technology (IT) Research, specifically for developing customized IT applications or software. The methodology of writing this article uses a content analysis with the main source of literature review, Focus Discussion Group, and also based on the experience and knowledge of the authors as lecturers of Software Engineering and Software Project Management. This article shows that although current IT development approaches or methodologies (especially software development methodology) continue to develop, good IT design is carried out through six main stages, namely planning, analysis, design, construction, implementation, and maintenance. The success of IT implementation depends on the good process of all stages of IT design. The involvement of all actors/ stakeholders in IT design is essential to be accommodated at all stages of IT design. Quality also becomes the main goal and controls every process of IT development.

Continuous Integration and Continuous Delivery Platform Development of Software Engineering and Software Project Management in Higher Education

We present a report of development phase of a platform which aims to enhance the efficiency of software project management in higher education. The platform accommodates a strategy known as Continuous Integration and Continuous Delivery (CI/CD). The phase consists of several stages, followed by testing of the system and its deployment. For starters, the CI/CD platform will be deployed for software projects of students in the Faculty of Information Technology, Universitas Kristen Maranatha. The goal of this paper is to show a design of an effective platform for continuous integration and continuous delivery pipeline to accommodate source code compilation, code analysis, code execution, until its deployment, all in a fully automated fashion.

Software Development Life Time Prediction Using Machine Learning Approach and There Comparison

Software Engineering Project Management (SEPM) contributes to being a key factor in determining the success of a software project. One of the major tasks assigned to it is to estimate the time that needs to be put in the process of development of the software. In real life, we use a plethora of different prediction machine learning algorithms in order to calculate the time it takes, but we have to keep in mind the accuracy and performance of this algorithm. To get the comparative study of the different machine learning techniques that is simple linear-regression, multiple-regressions, Artificial neural networks and the Gaussian-algorithm will be put into action in an attempt to correctly calculate the time it takes in software production keeping in mind the parameters. The dataset that we are trending to test is the content of past software development. Eventually the results that we obtained are published.

The Impact of Scope Creep on Project Success: An Empirical Investigation

Advocates of software engineering and software project management stated in the literature that creeping of scope is one of the most common causes for the failure of software projects. Also, advocates believed that it could occur in almost every software project, which leads to compromise in quality, delayed schedules, increase cost and decreased customer satisfaction. However, the lack of empirical evidence demands a comprehensive investigation to identify the factors of scope creep and to propose a conceptual framework to empirically evaluate the impact of scope creep on software project success. To determine the scope creep factors in this study, two exploratory methods, i.e. a Systematic Literature Review (SLR) and interview from experts are performed. Following the analysis of these methods, a conceptual framework is proposed. To empirically evaluate the proposed conceptual framework, data is collected through a survey method. Next, the collected data is analyzed through Partial Least Squares' Structural Equation Modelling (PLS-SEM). From the results, it is evident that the identified factors of scope creep are negatively associated with software project success. The results of empirical evaluation also second the findings of SLR. The outcome of the study may help the practitioners to understand the dynamics of factors, which undermine scope creep in software SMEs and to assist them in the development of effective control and mitigation strategies, therefore, to increase the project success rate.

Software Engineering Design Principles Applied to Instructional Design: What can we Learn from our Sister Discipline?

The failure of many instructional design initiatives is often attributed to poor instructional design. Current instructional design models do not provide much insight into design processes for creating e-learning instructional solutions. Given the similarities between the fields of instructional design and software engineering, instructional designers could employ the ideas and techniques employed in software engineering to improve their design solutions. Software engineering development and project management methodologies can be employed to develop effective e-learning solutions. Furthermore, software engineering design principles used to develop high-quality software can be applied to planning and enhancing instruction. Fundamental software design concepts, such as abstraction, modularity, reusability, compatibility, extensibility, scalability, and maintainability are all important factors that can potentially lead to the development of high quality instructional solutions. This paper explores the possibility to integrate software engineering design principles into instructional design for e-learning solutions, which not only augment the generic instructional design approach with the best practices from the field of software engineering, but also make the development process more productive and efficient. Finally, this paper illustrates how all of the software engineering design principles are interrelated and can be realized in practice to enhance the quality of instruction.

Current Trends in Software Engineering Research

Software engineering is dynamic disciplines that have continuous growth in research in identifying new methods, tools and methodologies that have cause vast improvement in software development and maintenance to be more reliable and efficient. Past research critics on cost reduction, quality and flexibility have endless try to design and develop many ways to improve these sectors are still causing impacts to the software industry [1]. The new trends in software engineering research topics resolves under the research field of Cloud Computing, Big Data, Android Computing, Network Security and Software Engineering Project Management. Nevertheless, there are more other research areas in software engineering that have been intense researched and implemented in the industries.

The Agile approach in industrial and software engineering project management

The paper presents the agile approach in industrial engineering and discusses similar ways of agile development in different disciplines. Societal changes and technological innovation brought significant changes in the market, leading to highly demanding users and frequent changes in product design. Agile is implemented in different disciplines as a response to current changes in the market. Industry 4.0 as part of 'High-Tech Strategy 2020 for Germany' involves agile principles and brings latest technological trends in production process. Agile framework was firstly used in manufacturing but along with that it started to develop as a lightweight framework in software development. Agile is interdisciplinary and brings flexibility to organization. For successful implementation of agile principles, experiences and recommendations from all the industries should be used.

A Systematic Survey of Games Used for Software Engineering Education

Simsoft is a serious game— one that trains or educates— at the centre of a research project designed to see if and how games can contribute to better software engineering management education by helping software engineers and project managers explore some of the dynamic complexities of the field in a safe and inexpensive environment. A necessary precursor for this project was to establish what games already existed in the field and how effective they had been. To this end a systematic review of the literature was conducted using a collection of online science, engineering, education, and business databases looking for games or simulations used for educational or training purposes in software engineering or software project management across any of the SWEBOK knowledge areas. The initial search returned 243 results, which was filtered to 36 papers by applying some simple quality and relevance inclusion/exclusion criteria. These remaining papers were then analysed in more depth to see if and how they promoted education in the field of software engineering management. The results showed that games were mainly used in the SWEBOK knowledge areas of software engineering management and development processes, and most game activity was in Europe and the Americas. The results also showed that most games in the field have learning objectives pitched at the first rung of Bloom’s taxonomy (knowledge), most studies followed a non-experimental design, and many had very small sample sizes. This suggests that more rigorous research is needed into the efficacy of games in teaching software engineering management, but enough evidence exists to say that educators could include serious games in their courses as a useful and interesting supplement to other teaching methods.

Teaching Software Engineering Project Management – A Novel Approach for Software Engineering Programs

In response to real and perceived short-comings in the quality and productivity of software engineering practices and projects, professionally-endorsed graduate and post-graduate curriculum guides have been developed to meet technical developments and evolving industry demands. Each of these curriculum guidelines identifies better software project management skills as critical for all graduating students, but they provide little guidance on how to achieve this. One possible way is to use a serious game — a game designed to teach and educate players about some of the dynamic complexities of the field in a safe and inexpensive environment. This paper presents the results of a qualitative research project that used a simple game of a software project to see if and how games could contribute to better software project management education. Initial results suggest that suitably-designed games are able to teach software engineering and project management concepts at higher-order Bloom taxonomy levels.

Special Issue on Search‐Based Software Maintenance

Search-based software engineering (SBSE) consists of the application of metaheuristic search techniques—such as genetic algorithms, simulated annealing, hill climbing, and tabu search—to software engineering problems. This idea is based on the observation that some software engineering activities can be thought of as optimization problems, and on the fact that techniques providing exact solutions are, very often, unable to adequately scale to large, real-world software engineering problems. Define fitness functions to guide an automated search for solutions, rather than attempting to construct solutions from scratch by hand. SBSE moves the engineer up the abstraction chain, from the tedious and expensive role of detailed solution construction, to the potentially more productive and more cost-effective area of fitness function design. This approach has been repeatedly demonstrated to have successful applications across the software engineering life cycle from requirements and project planning to maintenance and testing. This special issue focuses on applications of search SBSE to the maintenance phase of the life cycle. After software testing 2, software maintenance is the most widely studied application area for SBSE research. Work on SBSE applications to problems in software maintenance can be traced back to the pioneering work of the Mancoridis et al. 3, which led to the development of the Bunch tool for software re-modularization 4. In the past five years there has been a significant increase in SBSE applications to software maintenance and evolution. Search-based techniques have been applied to post-development code improvement problems, such as object-oriented refactoring 5, 6, and imperative language slicing and transformation 7. Other applications are related to software engineering economics and project management problems, such as release planning 8-12, effort, and cost estimation 13-16, and project staffing and planning 17-20. Last, but not the least, SBSE has been applied to deal with service-oriented architectures, for example for services QoS-aware composition 21, service-level agreement negotiation 22, and testing 23. A complete overview of SBSE with a discussion of future research trends can be found in the recent International Conference on Software Engineering (ICSE) ‘Future of Software Engineering’ paper 24. This issue of the Journal of Software Maintenance and Evolution: Research and Practice features three outstanding papers, dealing with different aspects of software maintenance and evolution: release planning and staffing, re-factoring, and component substitution. The paper ‘Optimized Staffing for Product Releases—Focused Search and its Application at Chartwell Technologies’ by Puneet Kapur, An Ngo-The, Günther Ruhe, and Andrew Smith presents an approach for optimizing the staffing for product releases. The problem they solve can be viewed as part of the more general release planning problem, which assigns features to releases such that technical, resource, risk, and budget constraints are met. In particular, the genetic search-based approach the authors propose aims at assigning human resources to software development tasks, taking them from a pool of developers having different levels of skills. The applicability of the proposed approach is demonstrated with an industrial case study. The paper ‘Search-Based Refactoring: an Empirical Study’ by Mark O'Keffe and Mel Ó Cinnéide presents an approach to automatically re-factor, using search-based techniques, object-oriented systems that undergo repeated addition of functionality. Such addition can, very often, deteriorate the quality of the system's underlying design. Their re-factoring is guided by the QMOOD quality model 25, and the paper compares different optimization techniques, such as Genetic Algorithms, Simulated Annealing, and Multiple Ascent Hill-Climbing. The results of experiments carried out on five software systems suggest that the latter technique outperforms the others. The paper ‘Search-based Many-to-one Component Substitution’ by Nicolas Desnos, Marianne Huchard, Guy Tremblay, Christelle Urtado, and Sylvain Vauttier presents a search-based approach that allows the replacement of an obsolete component with a composition of multiple components. When a component becomes obsolete, the approach searches for a minimal assembly of other components, exposing their functionality by means of ports that preserves the behavior of the original component. The proposed approach has been evaluated on a set of randomly generated components. We hope that readers will enjoy this special issue and find the selected papers insightful and inspiring. We would like to thank all the authors who presented papers for this special issue: there were many good quality papers, but unfortunately we could accept only three of them. Last, but not the least, we would like to thank the reviewers who provided timely, detailed and constructive feedbacks to the authors. Without their precious help this special issue would not have been possible.

Guest Editors' Introduction: Software Engineering Project Management 20 Years Later

A little more than 20 years ago, the guest editors assembled several papers on software engineering project management for the January 1984 edition of IEEE Transactions on Software Engineering. Those papers portrayed the state of the practice in SEPM and looked into its future. They decided to revisit SEPM and assemble another set of articles that reflect how SEPM had advanced over the past 20 years and offer a fresh prediction of what lies ahead.

On site: Software engineering project management

On site: Software engineering project management

How to improve the quality of software engineering project management

Every project, including software engineering projects, start with the project plan. A project plan means the prediction of future events with the goal of minimizing the risk during execution of the project. The heart of the problem is to make the project plan as close to reality as possible. Ideally, it should be exactly the same as the post project measured data. In the end we always encounter the problem of "the perfect project plan". Does a perfect project plan exist? If it does not exist, can we be any better than we are now? In the article we will show that we can improve, but the perfect project plan is still somewhere in the future.

Total quality management for bridging the expectations gap in systems development

The expectations gap in systems development is the result of differences between the expectations of end users from computer systems and their actual performance. High expectations of users are caused by vendors' self-serving claims and the glitter of technology, while the low performance of computer systems is the result of inadequacies in systems development. Application of total quality management (TQM) concepts in systems development narrows this expectations gap by meeting users' requirements of functionality and budget constraints. This is achieved by involving users, senior managers and systems developers in systems development. The development process is streamlined with computer-aided software engineering (CASE) tools and project management techniques.

Fuzzy systems and neural networks in software engineering project management

To make reasonable estimates of resources, costs, and schedules, software project managers need to be provided with models that furnish the essential framework for software project planning and control by supplying important “management numbers” concerning the state and parameters of the project that are critical for resource allocation. Understanding that software development is not a “mechanistic” process brings about the realization that parameters that characterize the development of software possess an inherent “fuzziness,” thus providing the rationale for the development of realistic models based on fuzzy set or neural theories.

A spiral approach to Software Engineering Project Management Education

A spiral approach to Software Engineering Project Management Education

A spiral approach to Software Engineering Project Management Education

article A spiral approach to Software Engineering Project Management Education Share on Author: Joseph C. Spicer Wang Institute of Graduate Studies, Tyngsboro, MA Wang Institute of Graduate Studies, Tyngsboro, MAView Profile Authors Info & Claims ACM SIGSOFT Software Engineering NotesVolume 8Issue 3July 1983 pp 30–38https://doi.org/10.1145/1010891.1010895Online:01 July 1983Publication History 4citation718DownloadsMetricsTotal Citations4Total Downloads718Last 12 Months3Last 6 weeks0 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access

Validating Solutions to Major Problems in Software Engineering Project Management

Validating Solutions to Major Problems in Software Engineering Project Management

Major Issues in Software Engineering Project Management

Software engineering project management (SEPM) has been the focus of much recent attention because of the enormous penalties incurred during software development and maintenance resulting from poor management. To date there has been no comprehensive study performed to determine the most significant problems of SEPM, their relative importance, or the research directions necessary to solve them. We conducted a major survey of individuals from all areas of the computer field to determine the general consensus on SEPM problems. Twenty hypothesized problems were submitted to several hundred individuals for their opinions. The 294 respondents validated most of these propositions. None of the propositions was rejected by the respondents as unimportant. A number of research directions were indicated by the respondents which, if followed, the respondents believed would lead to solutions for these problems.