Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “software engineering process”

Software engineering process improvement

Sezer, Bülent · OpenMETU (Middle East Technical University) · 2019

This thesis presents a software engineering process improvement study. The literature on software process improvement is reviewed. Then the current design verification process at one of the Software Engineering Departments of the X Company, Ankara, Türkiye (SED) is analyzed. Static software development process metrics have been calculated for the SED based on a recently proposed approach. Some improvement suggestions have been made based on the metric values calculated according to the proposals of that study. Besides, the author's improvement suggestions have been discussed with the senior staff at the department and then final version of the improvements has been gathered. Then, a discussion has been made comparing these two approaches. Finally, a new software design verification process model has been proposed. Some of the suggestions have already been applied and preliminary results have been obtained.

Cited by 0Open access

Software Engineering Program: Software Process Improvement Guidebook

V Basili, F Mcgarry · NASA Technical Reports Server (NASA)

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Cited by 0Open access

Tools for software process engineering

Robert A. Brownlie, Philip Brown, Kathleen Culver-Lozo et al. · Bell Labs Technical Journal · 2002

Lucent Technologies serves a large variety of telecommunications markets and customer needs. Success in such a rapidly changing environment requires that we quickly and effectively identify market needs and marshal our resources to address them. Clearly, a company that better coordinates and focuses its resources to serve customer needs will enjoy a competitive advantage. Because software development processes provide an important mechanism to coordinate project teams and ensure the customer-perceived value of the delivered product, we must be able to develop, deploy, and evolve those processes rapidly in step with the changing environment. Our experiences with software process engineering initiatives for Lucent projects have shown that such rapid process iteration is possible if an organization has a solid process engineering infrastructure. To provide such an infrastructure, the Software Technology Center has developed a set of process engineering tools to support the rapid development, deployment, and improvement of software processes. The platform is based on a centralized database organized around a relational model of key process concepts. Process engineers create instances of this database and automatically generate different views of their process. The process views are deployed to the members of the project through the Internet and the World Wide Web.

Cited by 1

Software Engineering Process Group Guide

Priscilla Fowler, Stan Rifkin · 1990

Abstract : Improving the process of software systems development and maintenance is the most reliable way to improve product quality. This document offers guidance on how to establish a software engineering process group (SEPG) and related software engineering process improvement functions. The process group works with line organizations to improve process quality by helping to assess current status, plan and implement improvements, and transfer technology to facilitate improvement in practice.

Cited by 72

Software Engineering Process Case Study

Gary J. Nut T · 2015

Recently a faction of software engineering re-searchers has focused their attention on studying the process by which software is produced, stimulating interest in models to specify, design, and implement software. A significant part of the practicing soft-ware industry must produce software that conforms to a documentation standard (military standard 2167A) for software products; it is intended to ensure that delivered software meets the documentation require-ments. This paper is a case study of how a government software contractor might use models to define a pro-cess for designing and implementing a software prod-uct that complies with the documentation require-ments. The intent of the paper is to apply business process modeling technology to the software ngineer-ing domain, thus exploring strengths and weaknesses of our evolving models of group collaboration. The case study illustrates an alternative way to design, an-alyze, and track software processes. It also attempts to illustrate how the model might "break down " as the basis of an enactment model if it were to be used to coordinate the work of a large number of software developers.

Cited by 0

Software and Systems Engineering Process

Improvement At Oerlikon, Claude Y. Laporte, Nicola R. Papiccio et al. · 2007

In order to reduce cycle time, increase customer satisfaction and lower costs, Oerlikon Aerospace has initiated, three years ago, a project to define and implement software and systems engineering processes. The initiative started by performing a formal assessment of current software engineering practices. An action plan was developed and multi-functional working groups were tasked to define and facilitate the implementation of software processes. A second initiative was started a year ago with the objective of defining and implementing a systems engineering process and, integrating to the systems engineering process the software engineering process already in use.

Cited by 0

Software Re-engineering Process Model

Avishek Kumar · International Journal of Science and Research (IJSR) · 2021

Software Re-engineering process is the examination and alteration of a system to reconstitute it in a new form. The principle of Re-Engineering when applied to the software development process is called software re-engineering. It affects positively at software cost, quality, service to the customer and speed of delivery. In Software Re-engineering, we are improving the software to make it more efficient and effective. Software re-engineering is an economical process for software development and quality enhancement of the product. The process enables us to identify the useless consumption of deployed resources and the constraints that are restricting the development process so that the development process can be made easier and cost-effective and maintainable.

Cited by 0Open access

SPEM: Software Process Engineering Metamodel

Víctor Hugo Menéndez Domínguez, María Enriqueta Castellanos Bolaños · Revista Latinoamericana de Ingenieria de Software · 2015

Todas las organizaciones involucradas en el desarrollo de software necesitan establecer, gestionar y soportar el trabajo de desarrollo. El término “proceso de desarrollo de software” tiende a unificar todas las actividades y prácticas que cubren esas necesidades. Modelar el proceso de software es una forma para mejorar el desarrollo y la calidad de las aplicaciones resultantes. De entre todos los lenguajes existentes para el modelado de procesos, aquellos basados en productos de trabajo son los más adecuados. Uno de tales lenguajes es SPEM (Software Process Engineering Metamodel). SPEM fue creado por OMG (Object Management Group) como un estándar de alto nivel, que está basado en MOF (MetaObject Facility) y es un metamodelo UML (Uniform Model Language). Constituye un tipo de ontología de procesos de desarrollo de software. En este artículo se ofrece una descripción, en términos generales, del estándar SPEM. También se destacan los cambios que ha experimentado entre la versión 1.1 y la versión 2.0, presentando tanto las ventajas como las desventajas encontradas entre ambas versiones.

Cited by 14Open access

A Software Process Model Applicable to Software Engineering and Knowledge Engineering

Silvia Acuña, Marta Lopez Fernandez, Natália Juristo et al. · Zenodo (CERN European Organization for Nuclear Research) · 1999

Software engineering (SE) and knowledge engineering (KE) develop software systems using different construction process models. Because of the growing complexity of the problems to be solved by computers, the conventional systems (CS) and knowledge-based systems (KBS) software process is at present passing through a period of integration. In this paper, we propose a software process model applicable to both CS and KBS. The model designed is declarative, that is, it indicates what is done to build a software system. Its goal is to provide software and knowledge engineers with a techno-conceptual tool to develop systems comprising both traditional and knowledge-based software.

Cited by 0Open access

A Software Process Model Applicable to Software Engineering and Knowledge Engineering

Silvia Acuña, Marta Lopez Fernandez, Natália Juristo et al. · Zenodo (CERN European Organization for Nuclear Research) · 1999

Software engineering (SE) and knowledge engineering (KE) develop software systems using different construction process models. Because of the growing complexity of the problems to be solved by computers, the conventional systems (CS) and knowledge-based systems (KBS) software process is at present passing through a period of integration. In this paper, we propose a software process model applicable to both CS and KBS. The model designed is declarative, that is, it indicates what is done to build a software system. Its goal is to provide software and knowledge engineers with a techno-conceptual tool to develop systems comprising both traditional and knowledge-based software.

Cited by 0Open access

Effective Requirement Engineering Process Model in Software Engineering

Isonkobong Udousoro · Software Engineering · 2020

Requirement Engineering is regarded as one of the major stages in software development and management. The aim of requirement engineering is to analyse, investigate, document and check the services and also the constraints of the software system that is being developed. The world of requirement management has increasingly developed over the years and has become the cornerstone for any software development to be successful, therefore it is vital for every organization to consider and pay more attention to the requirement engineering if they intend to build a quality software product that will satisfy the users. Different viewpoints, objectives, roles and responsibilities are all incorporated into requirements engineering which makes it a difficult and complex process in software engineering. Many researchers have come up with different optimized approaches to the requirement engineering. This paper reviewed relevant literature from Elsevier, Emerald, IEEE, ProQuest and Google Scholar databases. Requirement engineering processes are further outlined and explained which include requirement elicitation and development, validation and verification etc. In conclusion, the paper recommends effective requirements engineering process to adopt depending on the industry’s goal.

Cited by 7Open access

Supporting the software process in a process-centred software engineering environment

Hans‐Ulrich Kobialka · Publikationsdatenbank der Fraunhofer-Gesellschaft (Fraunhofer-Gesellschaft) · 2004

In software projects there exist tools, working schemes, and collaboration. Turning such an environment into a Process-centred Software Engineering Environment (PSEE), involves: 1) Augmenting the process with an additional flow of information and a dedicated user interface. 2) Supporting wanted process steps. 3) Disabling unwanted process steps. There is no need for completeness. It is not practical to claim that all activities in software projects have to be completely defined and supported by a PSEE. Instead, process support has to be introduced incrementally. This paper illustrates how this can be achieved.

Cited by 0Open access