Analysis of crosscutting across software development phases based on traceability

2006 ◽  
Author(s):  
Klaas van den Berg ◽  
José María Conejero ◽  
Juan Hernández
Keyword(s):  
Software Development ◽  
Development Phases

An Early Multi-Criteria Risk Assessment Model

2019 ◽  
Vol 21 (2) ◽  
pp. 51-64
Author(s):  
Priyanka Chandani ◽  
Chetna Gupta
Keyword(s):  
Risk Assessment ◽  
Software Development ◽  
Cumulative Risk ◽  
Requirement Engineering ◽  
Assessment Model ◽  
Risk Assessment Model ◽  
Software Projects ◽  
Development Life Cycle ◽  
Weighted Score ◽  
Development Phases

Accurate time and budget is an essential estimate for planning software projects correctly. Quite often, the software projects fall into unrealistic estimates and the core reason generally owes to problems with the requirement analysis. For investigating such problems, risk has to identified and assessed at the requirement engineering phase only so that defects do not seep down to other software development phases. This article proposes a multi-criteria risk assessment model to compute risk at a requirement level by computing cumulative risk score based on a weighted score assigned to each criterion. The result of comparison with other approaches and experimentation shows that using this model it is possible to predict the risk at the early phase of software development life cycle with high accuracy.

THE DEVELOPMENT OF AN OBJECT-ORIENTED SYSTEM WHICH INTEGRATES SIMULATION AND RECONSTRUCTION WITHIN A COMMON FRAMEWORK

1995 ◽  
Vol 06 (04) ◽  
pp. 481-488
Author(s):  
PAUL FUCHS
Keyword(s):  
Software Development ◽  
Object Oriented ◽  
Real Data ◽  
Design Strategy ◽  
Interface Problems ◽  
Software Components ◽  
Overall Design ◽  
Common Framework ◽  
Development Phases ◽  
Oriented System

A common problem for small experiments is that the design of the data acquisition, the simulation of the experiment and the reconstruction and analysis of real data is broken up into several disjoint development phases. Software development is necessary in all phases, yet continuity and an overall design strategy is lacking. This leads to duplication of software components and interface problems from one phase to the next and prohibits the generation of code which is reusable over the lifetime of many experiments. We address this problem within an object-oriented paradigm.

scholarly journals The Study of Resource Allocation among Software Development Phases: An Economics-Based Approach

2011 ◽  
Vol 2011 ◽  
pp. 1-21 ◽  
Author(s):  
Peleg Yiftachel ◽  
Irit Hadar ◽  
Dan Peled ◽  
Eitan Farchi ◽  
Dan Goldwasser
Keyword(s):  
Resource Allocation ◽  
Software Development ◽  
Empirical Studies ◽  
Profit Maximization ◽  
Maximization Problem ◽  
Software Production ◽  
Software Product ◽  
Development Processes ◽  
Development Phases ◽  
Novel Concept

This paper presents an economics-based approach for studying the problem of resource allocation among software development phases. Our approach is structured along two parallel axes: theoretical and empirical. We developed a general economic model for analyzing the allocation problem as a constrained profit maximization problem. The model, based on a novel concept of software production function, considers the effects of different allocations of development resources on output measures of the resulting software product. An empirical environment for evaluating and refining the model is presented, and a first exploratory study for characterizing the model's components and developers' resource allocation decisions is described. The findings illustrate how the model can be applied and validate its underlying assumptions and usability. Future quantitative empirical studies can refine and substantiate various aspects of the proposed model and ultimately improve the productivity of software development processes.

Q-IBADAH MOBILE APPLICATION: A USABILITY PILOT TESTING

2015 ◽  
Vol 77 (29) ◽  
Author(s):  
Aeni Zuhana Saidin ◽  
Khairun Salwa Mohamed ◽  
Zayana Husnayat Adzmi ◽  
Nurul Wadhihah Azhar
Keyword(s):  
Software Development ◽  
Learning Style ◽  
Mobile Application ◽  
Mobile App ◽  
Religious Knowledge ◽  
Pilot Testing ◽  
Testing Phase ◽  
Development Cycle ◽  
Development Phases ◽  
App Design

Q-Ibadah is a mobile application that aims to nurture KAFA students on their Islamic and religious knowledge.  The lack of accessibility of digital and online KAFA subject resources have become the motivation in the development of this mobile app.  Design and development of this application have followed the software development phases by iterating its design based on the results gathered during the usability pilot-testing phase.  As a result, few alterations were suggested for the next development cycle. This research is aimed to provide more contemporary learning style for this important religious lesson for children in Malaysia.

scholarly journals Knowledge reuse in software projects: Retrieving software development Q&A posts based on project task similarity

PLoS ONE ◽  
2020 ◽  
Vol 15 (12) ◽  
pp. e0243852
Author(s):  
Glaucia Melo ◽  
Toacy Oliveira ◽  
Paulo Alencar ◽  
Donald Cowan
Keyword(s):  
Software Development ◽  
Programming Languages ◽  
Knowledge Reuse ◽  
Software Projects ◽  
Explicit Integration ◽  
Stack Overflow ◽  
Task Similarity ◽  
Development Phases ◽  
Amount Of Knowledge ◽  
Agile Software

Software developers need to cope with a massive amount of knowledge throughout the typical life cycle of modern projects. This knowledge includes expertise related to the software development phases (e.g., programming, testing) using a wide variety of methods and tools, including development methodologies (e.g., waterfall, agile), software tools (e.g., Eclipse), programming languages (e.g., Java, SQL), and deployment strategies (e.g., Docker, Jenkins). However, there is no explicit integration of these various types of knowledge with software development projects so that developers can avoid having to search over and over for similar and recurrent solutions to tasks and reuse this knowledge. Specifically, Q&A sites such as Stack Overflow are used by developers to share software development knowledge through posts published in several categories, but there is no link between these posts and the tasks developers perform. In this paper, we present an approach that (i) allows developers to associate project tasks with Stack Overflow posts, and (ii) recommends which Stack Overflow posts might be reused based on task similarity. We analyze an industry dataset, which contains project tasks associated with Stack Overflow posts, looking for the similarity of project tasks that reuse a Stack Overflow post. The approach indicates that when a software developer is performing a task, and this task is similar to another task that has been associated with a post, the same post can be recommended to the developer and possibly reused. We believe that this approach can significantly advance the state of the art of software knowledge reuse by supporting novel knowledge-project associations.

Sign in / Sign up

Export Citation Format

Share Document