Peiwei Mi, M.-J. Lee, Walt Scacchi · 2003
The authors present a knowledge-based process library (SPLib) that supports the organization, access, and reuse of software processes. SPLib consists of a knowledge base of software process representations. It also provides a set of process operations that support browsing, searching, composition, and abstraction. These operations reason about the content of software processes as well as maintain proper interdependency relationships among the software processes. To demonstrate the use of SPLib in process-driven software development, a usage scenario is provided where SPLib facilitates the access and reuse of software processes.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>
Cited by 7
Nikolai M. Sergienko · 2018
Information technologies is rapidly getting involved in our lives with each next year. Today there are almost no person who has never ever used a browser to search for some websites and information they present. In order to make this process comfortable and seamless, web development companies have to adapt to every customer need. This is not an easy procedure, since software development considers many activities and communication of different people with various mind-set for specific responsibilities. Thus, it is QA engineers who have duties to make sure that website is totally functional and looks good on every device and screen resolution.The aim of this paper is to firstly make sure that every reader would understand the basic terms and activities, which are handled in software development. Then, show insights of how software development works with attention to testing processes in the particular company. Finally, analyse company’s maturity of test processes and propose improvements for each non-functioning part. The overall results have showed strengths and weaknesses of test organisation within the company and willingness of authorities to optimise the processes accordingly.
Cited by 0
Abdullah, Mohd Syazwan, al-Tarawneh, Mejhem Yousef, Mat Ali, Abdul Bashah · Universiti Utara Malaysia Institutional Repository (Universiti Utara Malaysia) · 2012
Most of small software development firms use ad-hoc manner in developing their software products where it is difficult for them to achieve the requirements of the traditional software process improvement (SPI) models and standards, as these traditional models and standards were developed for large firms. As such, these firms are suffering from the lack of suitable software development methods that will enable them to follow the SPI models. This can be addressed by having a suitable software development process improvement framework to enable them in delivering high quality software products that fulfil the customer's expectation faster and cheaper. This paper presents the software development process improvement framework which was developed based on the Capability Maturity Model Integration Version 1.2 for Development (CMMI-DEV1.2) as a software improvement model and eXtreme Programming (XP) as a software development method.It discusses the development processes of this framework by highlighting the steps and stages involved.
Cited by 1Open access
Zeynep Konuralp · OpenMETU (Middle East Technical University) · 2007
A software process improvement study is presented. The literature on software development processes and their improvement is reviewed. The current peer review process at Software Engineering Directorate of the X Company, Ankara, Türkiye (XCOM) is studied and the static software development metrics based on a recent proposal have been evaluated. The static software metrics based improvement suggestions and the author’s improvement suggestions discussed with the senior staff are compared. An improved peer review process is proposed. The static software development metrics have been evaluated on the improved process to see the impacts of the improvements. The improved process has been already implemented at XCOM and preliminary results have been obtained.
Cited by 1Open access
Arif Ali Khan, Jacky Keung, Shahid Hussain et al. · ACM SIGAPP Applied Computing Review · 2017
Presently, most of the software development organizations are adopting the phenomena of Global Software Development (GSD), mainly because of the significant return on investment it produces. However, GSD is a complex phenomenon and there are many challenges associated with it, especially that related to Software Process Improvement (SPI). The aim of this work is to identify humans' related success factors and barriers that could impact the SPI process in GSD organizations and proposed a theoretical framework of the factors in relation to SPI implementation. We have adopted the Systematic Literature Review (SLR) method in order to investigate the success factors and barriers. Using the SLR approach, total ten success factors and eight barriers were identified. The paper also reported the Critical Success Factors (CSFs) and Critical Barriers (CBs) for SPI implementation following the criteria of the factors having a frequency ≥ 50% as critical. Our results reveal that five out of ten factors are critical for SPI program. Moreover, total three barriers were ranked as the most critical barriers. Based on the analysis of the identified factors, we have presented a theoretical framework that has highlighted an association between the identified factors and the implementation of the SPI program in GSD environment.
Cited by 35
Ross Smith · 2002
During 1992-94 the Cellular Infrastructure Group (CIG) organization of Motorola implemented a set of common software development process specifications using the IEEE Std 1074 as a process architecture guideline and the SEI Capability Maturity Model (CMM) for process requirements. In late 1993 the Software Quality Assurance group implemented a process assurance program of auditing against these process specifications for process compliance and process improvement. The IEEE Std 1028 was chosen as the basic standard for development of the audit program. In June 1996, the Cellular Infrastructure Group became ISO 9001 certified. This paper discusses challenges and lessons learned from working with these three major quality system and software development process standards from a process assurance perspective.
Cited by 7
Juho Leinonen · 2016
Cited by 3
University of Oulu Repository (University of Oulu) · 2016
Cited by 0Open access
Caldeira, Joao · Data Archiving and Networked Services (DANS) · 2020
Dataset for article IDE-based Software Development Process Analytics
Cited by 0Open access
Neil Walkinshaw · Undergraduate topics in computer science · 2017
Cited by 0
Pero Pasković · FER Repository · 2025
Cilj ovog rada je prijedlog modela procesa razvoja aplikacija za pristupačni turizam. U radu su se prvo istražila i ispitale dobre inicijative i postojeća rješenja u domeni pristupačnog turizma. Na temelju njih se došlo do zahtjeva na pristupačnu aplikaciju. Zatim je razvijen prototip pristupačne aplikacije za pristupačni prikaz kulturno-povijesnih znamenitosti. Aplikacija sadrži nekoliko opcija pristupačnosti koje su sve detaljno opisane u radu te je provedeno korisničko testiranje s odabranim korisnicima. Na temelju vlastitog iskustva u razvoju prototipa aplikacije te na temelju vanjskih izvora koji su citirani u radu oblikovan je model procesa razvoja aplikacije za pristupačni turizam i opisane su njegove faze. Ovaj model može poslužiti kao vodič budućim projektima u domeni pristupačnog turizma.
Cited by 0Open access
Mohamed E. Fayad
A process defines specifically who does what, when, and how. The Webster dictionary defines it as a "particular method of doing something, generally involving a number of steps or operations." A process implements one part of a method, such as, an object modeling technique, in sufficient detail such that the results are repeatable by any number of similarly trained individuals following steps of the process. However, processes are generally locally documented implementations of methods. Processes tell which tools will be used to implement a method. Process generally define what needs to be done, but they are only one part of what a method defines. They may define a set of high-level or low-level activities that need to be performed during the software development effort. They are usually partially ordered by time. Software processes may define a set of reviews or they may define how a review is to be conducted. Any complete set of processes will list deliverables resulting from each process. Processes put object-oriented techniques to work. Where a method or a technique defines the theory behind an approach, a process addresses the practicalities of using the method in a given development environment. A technique explains the ideas applied while a process lays out the concrete actions that take place. A technique can only predict results while a process might define the metrics to be used to verify the result.
Cited by 0
Karen Sandhof · LA Referencia (Red Federada de Repositorios Institucionales de Publicaciones Científicas) · 2004
Os modelos para melhoria da qualidade de software são fundamentados na tríade processo-pessoas-tecnologia. Este trabalho busca a relação entre dois destes pilares da qualidade de software: o processo de desenvolvimento e o ser humano. Este trabalho avalia como os modelos de qualidade de software consideram o ser humano e caracteriza a inserção de defeitos no software por seus desenvolvedores como erros humanos cometidos no processo de desenvolvimento. Fatores humanos condicionantes do desempenho são identificados e, através de pesquisa de campo cujo objetivo é explorar a realidade do processo de desenvolvimento de software, analisam-se os fatores humanos que podem afetar a qualidade de software, principalmente no que diz respeito às características de funcionalidade e confiabilidade.
Cited by 0
Sergey Gusev · Applied Mathematics and Control Sciences · 2019
The purpose of this work is to provide decision support for the management of software development information systems. The novelty of the results is determined by the fact that the developed models and algorithms for managing the process of developing information systems software provide an increase in the quality of management decisions by ensuring the accounting of uncertainty in the estimates of experts at the initial stage of the project, automated calculation of the volume of changes as a proportion of requirements implemented in the previous stages/iterations and affected by the implementation of new requirements, based on the calculated relationships between the elements of the project and the automated calculation of estimates of the complexity and timing of software development based on fuzzy inference systems, dynamically adjusted as retrospective data are accumulated.
Cited by 0Open access
Robert Slagter · 2004
Cited by 0
Colin Kirsopp · 2001
This paper argues that software measurement and the software development process are mutually dependent. Firstly, a high-level view of the relationship between measurement and the development process is taken. This view shows where the various activities within software measurement are positioned within the context of the high-level project stages. The topic of process modelling is introduced, and is used to develop a lower-level view of measurement integration with process. This shows that process models for measurement integration should be sufficiently fine-grained to show when measurements should be collected, how they should be collected, who should collect then, and how the results will be used (the usual lifecycle models are too coarse-grain to achieve this). It is also shown that measurement can be most easily integrated within an automated environment, as measurement collection should itself be automated. The initial work on the...
Cited by 0
Zeba-Shahzeab Z.I.Shaheen Sajjade · Zenodo (CERN European Organization for Nuclear Research) · 2020
<em>Software development is that the process of observing, requiring, designing, programming, documenting, testing and bug fixing involved in creating and preserving applications, maintaining frameworks or other software components. Software Development Life Cycle (SDLC) consists of an in depth plan which needs the way to develop, maintain and replace specific software. Several software development models followed by various organizations are referred to as Waterfall Model, V-Shaped Model, and Incremental Model. However Agile is adopted to be a winning choice for software development across all industries. The features like possibility of modifications as per requirements at any stage of software development and importance given to the business values delivered instead of confirmation to project plan makes Agile unique from traditional software development models. Industries are changing their software development choice as agile methodology. It shows how the Agile is becoming an attractive choice for software development altogether industries across the world.</em>
Cited by 0Open access
Binoy Kurikaparambil Revi · Journal of Artificial Intelligence Machine Learning and Data Science · 2023
Cited by 0Open access
Włodzimierz Wysocki · Procedia Computer Science · 2023
Managing software development processes remains a severe challenge despite the support of tools. To remedy this situation, we propose better use of data collected in management support systems, a light approach to planning inspired by agile approaches, and the premise that continuous changes are inevitable. This approach lies at the heart of the described solution. The article presents a simplified software development process model that classifies project work in task types and roles of project team members, uses statistics to generate tasks, and then aggregates the results in iterative (month or sprint) and incremental approaches. The simplicity of macrosimulation allows for implementation in a spreadsheet. Despite its simplicity, the model allows for analysis of the completed project work, planning further courses, selecting employees for the project team, identifying bottlenecks, and performing quick what-if simulations. The macro model concept explains its structure, operation, and components details. Three experiments demonstrate its replicative and predictive capability, using data from real-world IT industry software projects.
Cited by 3Open access
Schellekens, JHM Jorrit · TU/e Research Portal (Eindhoven University of Technology) · 2000
Cited by 0