Programming Languages and the Software Production Process

2004 ◽  
pp. 321-349
Author(s):  
Ernest Mnkandla

This chapter aims to reveal agile techniques that have been applied to software development and have resulted in meaningful improvements in software productivity. Available literature generally state some claims on the gains associated with the use of particular agile methodologies in software development. What lacks however, is a comprehensive analysis of how the application of agile techniques as a family will lead to improvement in software productivity. This chapter therefore provides such details. Software productivity techniques provide ways of measuring three things in order to determine the productivity of software; software products, software production processes and structures, and software production setting. Agile methodologies improve software productivity by focusing on the software production process and structures. The fundamental concern of this chapter is to show that agile methodologies measure the production process activities in a different but effective way from the more traditional approaches. For example, time-to-market is reduced by use of an iterative incremental development approach.


2005 ◽  
Vol 3 (1) ◽  
pp. 15-22 ◽  
Author(s):  
P. Maller ◽  
C. Ochoa ◽  
J. Silva

2018 ◽  
Vol 227 ◽  
pp. 02013
Author(s):  
Ming Zhao ◽  
Rui Wang ◽  
Yongming Xu ◽  
Xiaochun Xu

This article introduces the use of PCI software production day draw satellite is projective like production process, analyzes the key technologies in the production, summarizes the Suggestions to improve the quality of results, strengthen quality control method is proposed, for the day draw satellite orthogonal projection as mass production work has carried on the beneficial exploration.


Author(s):  
Sergi Valverde

Software is based on universal principles but not its development. Relating software to hardware is never automatic or easy. Attempts to optimize software production and drastically reduce their costs (like in hardware) have been very restricted. Instead, highly-skilled and experienced individuals are ultimately responsible for project success. The long and convoluted path towards useful and reliable software is often plagued by idiosyncratic accidents and emergent complexity. It was expected that software standardisation would remove these sources of unwanted diversity by aiming to controllable development processes, universal programming languages, and toolkits of reusable software components. However, limited adoption of development standards suggests that we still do not understand why software is so difficult to produce. Software standardisation has been limited by our poor understanding of humans’ role at the origin of technological diversity.


Sign in / Sign up

Export Citation Format

Share Document