Roy H. Campbell, Hal Render, R. N. Sum et al. · 1988
Much of the software development process is repetitive, tedious to perform, but possible to automate. Our SAGA Project research includes building models of software development tasks that accurately reflect the processes involved and have direct and efficient implementations. In this paper we assume the desirability of a software engineering environment that supports the entire life-cycle; automation should greatly enhance the quality and efficiency of software production and maintenance. To study the problems involved, SAGA has constructed ENCOMPASS, a prototype environment which supports software development. ENCOMPASS has provided valuable insights and experience; however, during its development and use many limitations have surfaced. In this paper we emphasize the configuration and project management aspects of our work. We discuss the current capabilities and limitations of ENCOMPASS, as well as describing the new systems being constructed to overcome its limitations and extend its life-cycle coverage.
Cited by 12
Rubén González Crespo, S. J. Bolaños Castro, Victor Hugo Medina Garc�a · International Journal of Interactive Multimedia and Artificial Intelligence · 2011
This article presents a set of patterns that can be found to perform best practices in software processes that are directly related to the problem of implementing the activities of the process, the roles involved, the knowledge generated and the inputs and outputs belonging to the process. In this work, a definition of the architecture is encouraged by using different recurrent configurations that strengthen the process and yield efficient results for the development of a software project. The patterns presented constitute a catalog, which serves as a vocabulary for communication among project participants [1], [2], and also can be implemented through software tools, thus facilitating patterns implementation [3]. Additionally, a tool that can be obtained under GPL (General Public license) is provided for this purpose.
Cited by 15Open access
June S. Hopkins, Jean M. Jernow · 1990
The Software Engineering Process Group (SEPG) at the Data Systems Division of Litton Systems, Inc., was given the task of documenting the software development process used within the division. This paper describes how the SEPG at Litton accomplished this task. It discusses the sources we used for guidance and describes the resulting documentation for defining the software development process and the methods and tools that support the process.
Cited by 6Open access
Laura Elena Carvajal García · 2012
Usability is the capability of the software product to be understood, learned, used and attractive to the user, when used under specified conditions. Many studies demonstrate the benefits of usability, yet to this day software products continue to exhibit consistently low levels of this quality attribute. Furthermore, poor usability in software systems contributes largely to software failing in actual use. One of the main disciplines involved in usability is that of Human-Computer Interaction (HCI). Over the past two decades the HCI community has proposed specific features that should be present in applications to improve their usability, yet incorporating them into software continues to be far from trivial for software developers. These difficulties are due to multiple factors, including the high level of abstraction at which these HCI recommendations are made and how far removed they are from actual software implementation. In order to bridge this gap, the Software Engineering community has long proposed software design solutions to help developers include usability features into software, however, the problem remains an open research question. This doctoral thesis addresses the problem of helping software developers include specific usability features into their applications by providing them with a structured and tangible guidance in the form of a process, which we have termed the Usability-Oriented Software Development Process. This process is supported by a set of Software Usability Guidelines that help developers to incorporate a set of eleven usability features with high impact on software design. After developing the Usability-oriented Software Development Process and the Software Usability Guidelines, they have been validated across multiple academic projects and proven to help software developers to include such usability features into their software applications. In doing so, their use significantly reduced development time and improved the quality of the resulting designs of these projects. Furthermore, in this work we propose a software tool to automate the application of the proposed process. In sum, this work contributes to the integration of the Software Engineering and HCI disciplines providing a framework that helps software developers to create usable applications in an efficient way.
Cited by 5Open access
J. Lubelczyk, A. Parra · 2000
Cited by 1
Helwerda, Leon · Zenodo (CERN European Organization for Nuclear Research) · 2024
Version as used during the GROS research project.
Cited by 0Open access
Pietilä, Miika · Theseus (Ammattikorkeakoulujen) · 2023
Customer was developing software for a non-regulated general laboratory devices and research use only devices. The future plan was however to develop software for In Vitro Diagnostic Devices (IVD) which are more regulated, and more requirements needs to be fulfilled in order to sell the devices in US and EU marketing areas. The main problem to be researched in the thesis was to investigate what process changes needs to be done to make the current software development process to be compliant for software developed for IVD devices. In addition to this the goal of the thesis was also to list what kind of documentation needs to be produced so that the documentation complies with all the IVD documentation requirements. The scope of the thesis was delimited to software development process related to lowest risk category IVD devices, research use only devices and general-purpose laboratory devices. Software validation and usability studies were also left out of scope but can be analysed and introduced to the process in later stages. \n \nThe methods used in the thesis was selected to be action research. The action research method allowed to analyse the background and source material in the planning stage, execute a current state analysis for the gathered material in the acting stage and finalize the process prototype in stakeholder workshops in developing stage. Finally, the final process prototype was built to the application lifecycle management (ALM) system and shared with the stakeholder and wider product development group in the reflecting stage. \n \nThe results of the thesis show that similarly structured process can be used to develop software for non-regulated and regulated software products. New process structures need to be put in place and also new documentation generated by that process needs to be implemented and preferably have document templates in place to easily fulfil the requirements. Using regulated process structure, documentation templates and hierarchy for non-regulated software also ensures that good common practices are used in both environments and are then cohesive between projects.
Cited by 0Open access
Arash Khodabandeh Paolo, Paolo Palazzi · 2007
The production of software is a labour intensive activity. Given the scale of software projects related to current and future HEP experiments, it is worth trying to improve the knowledge of the PEOPLE involved, the organization of the software development PROCESS and the TECHNOLOGY used in the various aspects of this activity. The goal is better systems at lower cost and happier users of the software. This document can be accessed through WWW at: URL = http://www.cern.ch/PTGroup/Papers/Sopron94/ The authors can be reached at: [khoda@ptsun00.cern.ch] and [palazzi@ptsun00.cern.ch] People Process Technology Published in the proceedings of the 1994 CERN School of Computing, Sopron, Hungary, and as CERN ECP Report 95/5. 2/25 1 Introduction Software is expensive. Building it and maintaining it are labour intensive activities, but delays in delivery can be very costly and any undetected problems may cause loss of performance and frustrate users. This also applies to High Energy Physics, ...
Cited by 0
Tesis Doctorals en Xarxa (Consorci de Serveis Universitaris de Catalunya)
Cited by 0
Aristides Dasso, Ana Funes · IGI Global eBooks · 2009
Nowadays, software engineering (SE) is considered more frequently an engineering discipline. Several definitions have been proposed by different authors, and many of them agree in affirming that SE is the application of principles and systematic practices for the development of software. That is—as it was established by the IEEE (1990)—SE is the application of engineering to the software. As a general rule all engineering applications use mathematics or mathematical tools as a basis for their development. However, software engineering is an exception to this rule. Not all the techniques and software development methods have a formal basis. Formal methods1 (FM) rely on mathematical foundations. FM are a collection of methodologies and related tools, geared to the production of software employing a mathematical basis. There are a number of different formal methods each having its own methodology and tools, specially a specification language. As it is expressed in Wikipedia (2006) and Foldoc (2006), we can say that FM are “mathematically based techniques for the specification, development and verification of software and hardware systems.” FM are based on the production of formal specifications— for which they have a formal language to express it. Sometimes there is also a method to use the language in the software development process. The aims of FM can vary according to the different methodologies, but they all shared a common goal: the production of software with the utmost quality mainly based on the production of software that is error free. To achieve this, the different FM have developed not only a theory, but also different tools to support the formal process. FM can cover all the steps of the life cycle of a software system development from requirement specification to deployment and maintenance. However, not all FM have that capacity, and not always it is convenient to apply them. It is necessary to make an evaluation between pros and cons before applying FM in the software development process.
Cited by 1
A Peter, H. Feller, Watts S. Humphrey et al. · 1992
AD-A258 465'l! I~ili1 I l I " l ' ~ II•i'It~lllllllll lu l 'l
Cited by 0
Wilson P. Paula Filho · 2002
Software engineering education must provide the students with knowledge and practice of software development processes. These must be used in course projects, to confront the students with realistic software engineering issues. A requirements set for educational software development processes is proposed here. It includes requirements about process architecture, team orientation, project life cycle, standards and practicesl student support and instructor support. Some published real-life processes were evaluated against these requirements, and a new process was designed to meet them. 1.
Cited by 0
Juan Carlos Augusto · 2014
The Software Engineering community has produced plenty of recipes on how to build software systems. Through the decades we have seen a shift from the more structured and organized to the most flexible approaches, lately with emphasis on speed. Although these methods in principle apply to all software, in being generic they may not address specific needs of some areas where systems have special features and demands. We argue in this paper that Intelligent Environments is one such area to be considered and in need of a tailored software development process. We introduce a new software development process and explain how is to be applied in systems of the Intelligent Environments field.
Cited by 12
Sandro Javier Bolaños Castro, Rubén Gonzalez Crespo, Victor Hugo Medina Garcia · SHILAP Revista de lepidopterología · 2011
"Times New Roman","serif";mso-fareast-font-family:"Times New Roman";mso-ansi-language:EN-US;mso-fareast-language:EN-US;mso-bidi-language:AR-SA">This article presents a set of patterns that can be found to perform best practices in software processes that are directly related to the problem of implementing the activities of the process, the roles involved, the knowledge generated and the inputs and outputs belonging to the process. In this work, a definition of the architecture is encouraged by using different recurrent configurations that strengthen the process and yield efficient results for the development of a software project. The patterns presented constitute a catalog, which serves as a vocabulary for communication among project participants [1], [2], and also can be implemented through software tools, thus facilitating patterns implementation [3]. Additionally, a tool that can be obtained under GPL (General Public license) is provided for this purpose
Cited by 0Open access
Bolaños Castro, Sandro Javier, González Crespo, Rubén, Medina García, Víctor Hugo · Dialnet (Universidad de la Rioja) · 2011
This article presents a set of patterns that can be found\nto perform best practices in software processes that are directly\nrelated to the problem of implementing the activities of the\nprocess, the roles involved, the knowledge generated and the\ninputs and outputs belonging to the process. In this work, a\ndefinition of the architecture is encouraged by using different\nrecurrent configurations that strengthen the process and yield\nefficient results for the development of a software project. The\npatterns presented constitute a catalog, which serves as a\nvocabulary for communication among project participants [1],\n[2], and also can be implemented through software tools, thus\nfacilitating patterns implementation [3]. Additionally, a tool that\ncan be obtained under GPL (General Public license) is provided\nfor this purpose.
Cited by 0
Vyron Damasiotis, Panos Fitsilis, James O’Kane · International Journal of Information Technology Project Management · 2018
Modern software systems are growing increasingly complex, requiring increased complexity of software and software development process (SDP). Most software complexity measurement approaches focus on software features such as code size, code defects, number of control paths, etc. However, software complexity measurement should not only focus on code features but on features that cover several aspects of SDP in order to have a more complete approach to software complexity. To implement this approach, an extensive literature review for identifying factors that contribute to the complexity of SDP was performed and seventeen complexity factors were identified. As there were indications that the identified factors were not independent from each other but there were interrelations between them, statistical methods for identifying the underlined relations and refining them were applied, resulting to the final set of measures used in the proposed model. Finally, the proposed model has been tested in five software projects and the results were evaluated.
Cited by 7
Helwerda, Leon · Zenodo (CERN European Organization for Nuclear Research) · 2024
Version as used during the GROS research project.
Cited by 0Open access
Renata M. S. Santos, Toacy Oliveira, Fernando Brito e Abreu · 2015
Process tailoring aims to customize a software process to better suit the specific needs of an organization when executing a software project or due to a social context in which the process is inserted. Tailoring happens, in general, through variations in the process elements, such as activities, artifacts, and control flows. This paper aims to introduce a technique that uses process mining to uncover elements from the software process that are candidates for tailoring. The proposed approach analyzes the execution logs from several process instances that share a common standard process. As a result, execution traces that differ from the standard process flow are identified and assessed to uncover their variable elements. The proposed technique was evaluated with data extracted from a real software development scenario when a large system was under development for a set of Brazilian Federal Institutes of Education, Science and Technology.
Cited by 9
Suparna Kurdi · 1997
Cited by 0Open access
EA Anibere, F.A. Egbokhare · Information Technologist (The) · 2007
Cited by 1