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 development process”

Software development process

Mehdi Sagheb‐Tehrani, Arbi Ghazarian · ACM SIGSOFT Software Engineering Notes · 2002

A successful project demands a correct and thorough requirements specification. This paper proposes techniques and strategies for handling business rules and requirements. The guidelines we provide are based on our own experiences with the development of large-scale enterprise applications as well as research we have done on best practices for requirements management proposed by other authors. The techniques are based on recursively classifying software requirements into logical coherent classes of requirements so that they improve developers' conception of the requirements and streamline the navigation to the next steps in the process. The techniques proposed in this paper, provide a mechanism for keeping track of requirements and help the development team to test the software in a more efficient way.

Cited by 11

Software development process

Mohamed E. Fayad · Communications of the ACM · 1997

article Free Access Share on Software development process: a necessary evil Author: Mohamed E. Fayad University of Nevada University of NevadaView Profile Authors Info & Claims Communications of the ACMVolume 40Issue 9Sept. 1997 pp 101–103https://doi.org/10.1145/260750.260783Published:01 September 1997Publication History 6citation1,223DownloadsMetricsTotal Citations6Total Downloads1,223Last 12 Months15Last 6 weeks1 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 Alerts New Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

Cited by 10Open access

Software Test Process Development

Jussi Kasurinen · LUTPub (LUT University) · 2011

In this thesis, the components important for testing work and organisational test process are identified and analysed. This work focuses on the testing activities in reallife software organisations, identifying the important test process components, observing testing work in practice, and analysing how the organisational test process could be developed. 
\n
\nSoftware professionals from 14 different software organisations were interviewed to collect data on organisational test process and testing‐related factors. Moreover, additional data on organisational aspects was collected with a survey conducted on 31 organisations. This data was further analysed with the Grounded Theory method to identify the important test process components, and to observe how real‐life test organisations develop their testing activities. 
\n
\nThe results indicate that the test management at the project level is an important factor; the organisations do have sufficient test resources available, but they are not necessarily applied efficiently. In addition, organisations in general are reactive; they develop their process mainly to correct problems, not to enhance their efficiency or output quality. The results of this study allows organisations to have a better understanding of the test processes, and develop towards better practices and a culture of preventing problems, not reacting to them.

Cited by 10Open access

The Software Development Process

Waller, Jerico · The Mathematics Enthusiast · 2024

The topic of my research is the process of software development. This project is meant to provide a more comprehensive understanding of modern methods of software consultation, development, testing, and deployment. It will also build “soft” skills, like communication and project management. To reach this goal, I am working together with a team of three other students and the local branch of a business consulting and I.T. company to create a piece of software from the ground up. The process starts with gathering information about the users that the application is intended for. After these requirements have been defined, we create various prototypes, working upwards in complexity, and continue to solicit feedback from the clients to ensure they are satisfied with the proposed functionality and design. Then, we begin implementing these features using a phased approach, whereby each phase is populated with various tasks that are typically divided between the team members. Throughout this process, we are also testing the software in multiple ways to verify correctness. At the end of the project, the goal is to have a high-quality, useful piece of software that meets the specifications of the clients and is delivered on time. Understanding this software development process is crucial for software engineers. A disorganized team could lead to quality issues, missed deadlines, or even security concerns. Leaving any part of this process incomplete could create issues down the line: not gathering feedback can cause design inconsistencies and missed expectations, a lack of testing could create a buggy and hard-to-use product, etc. This is especially important when creating software that deals with sensitive information, like government or banking applications. Modern methods of software development lead to useful, safe, and innovative tools that a wide variety of people can use, but only if they are utilized properly.

Cited by 0

Software Development: The Process

Vinay Trivedi · Apress eBooks · 2019

In 2011, having spent the previous three years advising entrepreneurs on organizing resources and designing processes, Eric Ries laid out his methodology in the book The Lean Startup, the release of which sparked the Lean Startup movement. Its philosophy, which articulates a continuous and feedback-driven approach to product development, informs this chapter.

Cited by 0

Software Process Paradigms and Crowdsourced Software Development

Nitasha Hasteer, Abhay Bansal, B. K. Murthy · Advances in IT personnel and project management · 2016

Production of quality software requires selecting the right development strategy. The process and development strategies for creating software have evolved over the years to cope with the changing paradigms. Cloud computing models have made provisioning of the computing capabilities and access to configurable pooled resources as convenient as having access to the common utilities. With the recent advancements in the use of social media and advent of software development through crowdsourcing, the need to comprehend and analyze the traditional process models of software development, with regard to the changed paradigm have become ever more necessary. The changes in the way software are being created and the continuous evolution in the processes of development and deployment has created a need to understand the development process models. This chapter provides an insight on the transition from the conventional process models of software development to the software development methodology being used to develop software through crowdsourcing.

Cited by 1

AKnowledge-Based Software Process Library for Process-Driven Software Development

Peiwei Mi Y, Ming-june Lee Y, Walt Scacchi Z · 2008

Process-driven software development represents a new technique for software pro-duction, in which a conceptual knowledge representation. called a software process, is used to represent and guide development activities. Management and reuse of software processes therefore becomes a requirement for process-driven software development. In this paper, we presentaknowledge-based process library (SPLib) that supports the or-ganization, 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 sup-port browsing, searching composition and abstraction. These operations reason about the content ofsoftware processes as well as maintain proper interdependency relation-ships among the software processes. To demonstrate the use of SPLib in process-driven software development, we provide a usage scenario where SPLib facilitates the access and reuse of software processes in real applications.

Cited by 0

Management of Software Development Process

Cai Yong-qiang · 2008

Focusing on software engineering management, some ideas of software development process management were presented. Some keys of software development process management for controlling criterion software development process were discussed.

Cited by 0

Optimizing the Software Development Process

Mates, Vojtěch · Brno University of Technology Digital Library (Brno University of Technology) · 2012

Práce se zaměřuje na modelování a optimalizaci podnikových procesů. Vybraná skupina procesů se zaměřuje na oblast tvorby software. Pomocí analýzy jsou odhalena problematické místa procesů. Optimalizace procesů je primárně zaměřena na redukci celkového času vykonání procesu a z toho vyplývajících nákladů.

Cited by 0

Formalizing the software development process

Pons, Claudia, Giandini, Roxana Silvia, Baum, Gabriel Alfredo · El Servicio de Difusión de la Creación Intelectual (National University of La Plata) · 2001

Object-oriented software development process, such as the Unified Process [Jacobson 99], Catalysis [D´Souza 98] and Fusion [Coleman 94] among others, is a set of activities needed to transform user’s requirements into a software system. A software development process typically consists of a set of software development artifacts together with a graph of tasks and activities. Software artifacts are the products resulting from software development, for example, a use case model, a class model or source code. Tasks are small behavioral units that usually results in a software artifact. Examples of tasks are construction of a use case model, construction of a class model and writing code. Activities (or workflows) are units that are larger than a task. Activities generally include several tasks and software artifacts. Examples of activities are requirements, analysis, design and implementation. Modern software development processes are iterative and incremental, they repeat over a series of iterations making up the life cycle of a system. Each iteration takes place over time and it consists of one pass through the requirements, analysis, design, implementation and test activities, building a number of different artifacts. All these artifacts are not independent. They are related to each other, they are semantically overlapping and together represent the system as a whole. Elements in one artifact have trace dependencies to other artifacts. For instance, a use case (in the use-case model) can be traced to a collaboration (in the design model) representing its realization.

Cited by 0

Usability-Oriented Software Development Process

Carvajal García, Laura Elena · Tesis Doctorals en Xarxa (Consorci de Serveis Universitaris de Catalunya) · 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 0Open access