Algorithms to support systematic software design are needed to enable practitioners to mechanize and coherently manage the engineering of quality software. In practice, design is both an art and a science, and this dichotomy has led some to under-focus on the science and engineering side of software development. In our previous research, we presented a design algorithm for structural design focused on UML use case and requirements class diagrams. In this paper we shift focus to systematic behavioral design algorithms illustrated by UML state and activity diagrams. We present the systematic behavioral design algorithms, their application to a specific case study, as well as contingent results, implications, and lessons learned.
