References
A. Abran, J. W. Moore (2004). Guide to the Software Engineering Body of Knowledge. Washington, DC: IEEE Computer Society.
J. -R. Abrial (1996). The B-Book: Assigning Programs to Meanings. Cambridge: Cambridge University Press.
ACM/IEEE Joint Task Force (2004). “Software Engineering 2004: Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering.” ACM Computing Curricula Series, pp. 1–128.
C. Alexander (1996). “The Origins of Pattern Theory: the Future of the Theory, and the Generation of a Living World.” Software, IEEE, 16(5), 71–82.
K. Beck (1996). Smalltalk Best Practice Patterns. Englewood Cliffs, NJ: Prentice Hall.
A. E. Bell (2004). “Death by UML Fever: Self-Diagnosis and Early Treatment Are Crucial in the Fight Against UML Fever.” Queue, 2(1), 72–80.
A. E. Bell (2005). “UML Fever: Diagnosis and Recovery.” Queue, 3(2), 48–56.
G. Booch (1993). Object-Oriented Analysis and Design with Applications, 2nd ed. Reading, MA: Addison-Wesley Professional.
E. Börger, R. Stärk (2003). Abstract State Machines: A Method for High-Level System Design and Analysis. Berlin: Springer.
F. P. Brooks II. (1987). “No Silver Bullet: Essence and Accidents of Software Engineering.” IEEE Computer, 20(4), 10–19.
N. G. Carr (2004). Does IT Matter? Information Technology and the Corrosion of Competitive Advantage. Boston: Harvard Business School Press.
J. O. Coplien (1991). Advanced C++ Programming Styles and Idioms. Reading, MA: Addison-Wesley Professional.
J. O. Coplien, ...
Get Codecharts: Roadmaps and blueprints for object-oriented programs now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
