Cyber security at software development time

2011 ◽  
Author(s):  
Mark Bradley ◽  
Ansgar Fehnker ◽  
Ralf Huuck
Keyword(s):  
Software Development ◽  
Cyber Security ◽  
Development Time

Effort, Time, and Staffing in Continually Evolving Open-Source Projects

2015 ◽  
pp. 1722-1743
Author(s):  
Liguo Yu
Keyword(s):  
Software Development ◽  
Open Source ◽  
Power Law ◽  
Development Time ◽  
Development Effort ◽  
Linux Kernel ◽  
Software Projects ◽  
Management And Development ◽  
Software Development Effort ◽  
Closed Source

Scheduling and staffing are important management activities in software projects. In closed-source software development, the relationships among development effort, time, and staffing have been well established and validated: the development effort determines the development time and the best number of developers that should be allocated to the project. However, there has been no similar research reported in open-source projects. In this chapter, the authors study the development effort, development time, and staffing in an open-source project, the Linux kernel project. Specifically, they investigate the power law relations among development effort, development time, and the number of active developers in the Linux kernel project. The authors find the power law relations differ from one branch to another branch in the Linux kernel project, which suggests different kinds of management and development styles might exist in different branches of the Linux kernel project. The empirical knowledge of software development effort obtained in this study could help project management and cost control in both open-source communities and closed-source industries.

Pervasive fun

First Monday ◽  
2007 ◽  
Author(s):  
Benno Luthiger ◽  
Carola Jungwirth
Keyword(s):  
Software Development ◽  
Open Source ◽  
Development Time ◽  
Software Developers ◽  
Commercial Software ◽  
Software Companies ◽  
Good Proxy

The goal of the study on Fun and Software Development (FASD) is to precisely assess the importance that fun has as motivation for software developers to engage in open source projects. A survey carried out both under open source developers and programmers working in Swiss software companies yielded that the fun motive accounts for about 27 percent to 33 percent of open source developers’ motivation. Fun is a pervasive feature of software development, not only for open source programmers but in the area of commercial software development too: Open source developers that are paid for their work are observed to be very motivated and prepared for future effort, especially if they enjoy their development time. Furthermore, the fun that programmers experience functions as a good proxy for their productivity. Therefore, employers that want to enhance the programmers’ productivity can safely invest in an environment of fun for developers in their company.

Towards Measuring the Change Impact in ATL Model Transformations

2016 ◽  
Vol 26 (02) ◽  
pp. 153-181 ◽  
Author(s):  
Andreza Vieira ◽  
Franklin Ramalho
Keyword(s):  
Software Development ◽  
Static Analysis ◽  
Development Time ◽  
Development Process ◽  
Model Transformations ◽  
Software Development Process ◽  
Model Driven ◽  
Change Impact ◽  
The Impact

The Model-Driven Development (MDD) approach shifts the focus on code to models in the software development process. In MDD, model transformations are elements that play an important role. MDD-based projects evolve along their lifecycle in a way that changes in their transformations are frequent. Before applying changes it is important to measure their impacts within the transformation. However, currently no technique helps practitioners in this direction. We propose an approach to measure the change impact in ATL model transformations. Based on static analysis, it detects the elements impacted by a change and calculates the change impact value through three metrics we defined. By using our approach, practitioners can (i) save effort and development time since the elements impacted with the change are automatically detected and (ii) better schedule and prioritize changes according to the impact value. To empirically evaluate our approach we conducted a case study.

Tools and Techniques for Model Based Testing

2010 ◽  
pp. 226-249
Author(s):  
Swapan Bhattacharya ◽  
Ananya Kanjilal ◽  
Sabnam Sengupta
Keyword(s):  
Software Development ◽  
Development Time ◽  
Domain Model ◽  
Test Case Generation ◽  
Test Case ◽  
Model Based ◽  
Testing Tools ◽  
Research Activities ◽  
Model Based Testing ◽  
Tools And Techniques

Software testing has gained immense importance in the present competitive world of developing software more quickly, more efficiently and more accurately. Testing activity is carried out throughout the lifecycle of software development and not only towards the end of development. Time and effort required to correct errors, detected later is much more compared to those, which are detected earlier. This has direct impact on costs and has led to a splurge of research activities in this domain. Model-based testing has recently gained attention with the popularization of modeling itself. It refers to testing and test case generation based on a model that describes the behavior of the system. The OMG initiative MDA has revolutionized the way models would be used for software development. There are a number of modeling techniques in use today- some have formal syntax like Z, VDM while some are semi-formal like UML. We have made a comprehensive summary of a considerable number of research works on Model Based testing. First, the issues, challenges and problems of model based testing have been discussed. Then the different methods developed for testing or test case generation based on the models are summarized. Finally a list of model based testing tools used for testing has been collectively presented.

Effort, Time, and Staffing in Continually Evolving Open-Source Projects

2013 ◽  
pp. 86-108
Author(s):  
Liguo Yu
Keyword(s):  
Software Development ◽  
Open Source ◽  
Power Law ◽  
Development Time ◽  
Development Effort ◽  
Linux Kernel ◽  
Software Projects ◽  
Management And Development ◽  
Software Development Effort ◽  
Closed Source

Scheduling and staffing are important management activities in software projects. In closed-source software development, the relationships among development effort, time, and staffing have been well established and validated: the development effort determines the development time and the best number of developers that should be allocated to the project. However, there has been no similar research reported in open-source projects. In this chapter, the authors study the development effort, development time, and staffing in an open-source project, the Linux kernel project. Specifically, they investigate the power law relations among development effort, development time, and the number of active developers in the Linux kernel project. The authors find the power law relations differ from one branch to another branch in the Linux kernel project, which suggests different kinds of management and development styles might exist in different branches of the Linux kernel project. The empirical knowledge of software development effort obtained in this study could help project management and cost control in both open-source communities and closed-source industries.

scholarly journals Architecture Centric Software Development using Program Line Code

2019 ◽  
Vol 8 (4) ◽  
pp. 5826-5830
Keyword(s):  
Software Development ◽  
Development Time ◽  
Product Lines ◽  
High Quality ◽  
Time To Market ◽  
Software Applications ◽  
Time Period ◽  
Software Program ◽  
Development Approach ◽  
Program Line

SoftwareArchitecture Centric Development Approach is regular and price outstanding in software program development technique in the software applications product lines. Traditionally used techniques in software improvement are very costly and unreliable in time period of high quality attribute and time to market products. If we are working in the same area then architecture centric development is very useful. In this technique we will reusable existing developed applications aspects for growing new software program alternatively of developing these software from scratch that are very time consuming and unreliable. To reduce the development time period we will reuse elements of from every stage of improvement to minimize the development time and provide better quality. Already developed, established and friendly components will be reused for development of new software. In this paper we will analysis Architecture Centric Software Development using Program Line Code. Which focus on which center of attention on high-quality attributes of software

Object Oriented Testing in Software Development

2011 ◽  
pp. 43-57
Author(s):  
Samuel K.A. Agyemang
Keyword(s):  
Software Development ◽  
Development Time ◽  
Development Process ◽  
Object Oriented ◽  
Final Analysis ◽  
Software Development Process ◽  
Object Oriented Technology ◽  
Development Processes ◽  
Software Object ◽  
The Cost

Object oriented technology is still growing and has not yet matured. Many articles have been written on object oriented software development processes, particularly in the area of testing. Most of the publications seem to agree with the fact that object oriented testing is a challenging aspect of the software development process. The main reason for this view seems to revolve around the fact that the objects and the code are inseparable and also, the idea of inheritance. Despite these views, the publications all seem to agree on one aspect, that object oriented when successfully tested leaves a better-maintained product compared to the traditional non-object oriented software. Object oriented software makes better maintainable software; it also has an added advantage over traditional software development because in the final analysis, it will cost less by shortening the development time as well as cutting down the cost of maintenance.

Sign in / Sign up

Export Citation Format

Share Document