This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Improving Software Development through Three Stages
September/October 2006 (vol. 23 no. 5)
pp. 81-87
ASCII Text
x 
 
Tetsuro Motoyama, "Improving Software Development through Three Stages," IEEE Software, vol. 23, no. 5, pp. 81-87, September/October, 2006.
 
 
BibTex
x
 
@article{ 10.1109/MS.2006.129,
author = {Tetsuro Motoyama},
title = {Improving Software Development through Three Stages},
journal ={IEEE Software},
volume = {23},
number = {5},
issn = {0740-7459},
year = {2006},
pages = {81-87},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.129},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Improving Software Development through Three Stages
IS - 5
SN - 0740-7459
SP81
EP87
EPD - 81-87
A1 - Tetsuro Motoyama,
PY - 2006
KW - management
KW - methodologies
KW - software engineering process
VL - 23
JA - IEEE Software
ER -
 
In three stages covering 12 years and 16 projects, a software development group worked on attaining visible schedule control and usable software design documentation. The first stage identified two major problems: unstable code and schedule delays. The group used code inspection to address the immediate issue of code construction. In the second stage, the group formulated and implemented a software development process that addressed the entire software development life cycle. The third stage improved that process. The major factor in process improvement was the group's willingness to identify its mistakes and problems.
Index Terms:
management, methodologies, software engineering process
Citation:
Tetsuro Motoyama, "Improving Software Development through Three Stages," IEEE Software, vol. 23, no. 5, pp. 81-87, Sept.-Oct. 2006, doi:10.1109/MS.2006.129
Usage of this product signifies your acceptance of the Terms of Use.