Re-engineering legacy Cobol programs
Communications of the ACM
A Quality Software Process for Rapid Application Development
Software Quality Control
Proceedings of the Second XP Universe and First Agile Universe Conference on Extreme Programming and Agile Methods - XP/Agile Universe 2002
Is Internet-Speed Software Development Different?
IEEE Software
Designing electronic reference documentation for software component libraries
Journal of Systems and Software
Credibility On-Line: Quality Metrics for Evaluation
OCSC '09 Proceedings of the 3d International Conference on Online Communities and Social Computing: Held as Part of HCI International 2009
Proceedings of the 2011 International Conference on Software and Systems Process
| Hi-index | 0.02 |
Because the product of software engineering is not physical, physical laws do not form a suitable foundation. Instead, software engineering has had to evolve its principles based solely on observations of thousands of projects. The following are probably the 15 most important principles: (1) make quality number one priority; (2) high-quality software is possible; (3) give products to customers early; (4) determine the problem before writing requirements; (5) evaluate design alternatives; (6) use an appropriate process model; (7) use different languages for different phases; (8) minimize intellectual distance; (9) put technique before tools; (10) get it right before you make it faster; (11) inspect code; (12) good management is more important than good technology; (13) people are the key to success; (14) follow hype with care; and (15) take responsibility. An additional 15 software engineering principles are also listed.