Communications of the ACM
Refine your search:
Contingency Plans for CS Students in Large Classes
Some of our students will get sick before the end of the term. We need a plan.
From BLOG@CACM
Getting a Program Right (1)
Why it is good to have a systematic approach to software verification.
From BLOG@CACM
There is More Than One Way to Become a Good Programmer
A recent Communications of the ACM article casts aspersions on the innovative concept of code academy, a fast-developing approach to teaching programming. The analysis...
From BLOG@CACM
Are My Requirements Complete?
Knowing the notion of sufficient completeness and the theory of abstract data types helps practitioners produce better requirements.
From BLOG@CACM
The Shortest Possible Schedule Theorem: Yes, You Can Throw Money at Software Deadlines
As close as we have to a universal law of software engineering management.
From BLOG@CACM
Soundness and Completeness: With Precision
The two key properties of program analysis are dual of each other.
From BLOG@CACM
The Formal Picnic Approach to Requirements
A mathematical excursion will improve your requirements.
From BLOG@CACM
Ten Traits of Exceptional Innovators
I have had the privilege of meeting, and in some cases closely interacting with, pioneer scientists, technologists, and entrepreneurs, including Nobel, Fields,...
From BLOG@CACM
Discussing Empirical Answers to Questions of Software Engineering
Focusing on what helps software developers.
From BLOG@CACM