A capstone course at the University of Maryland
Software engineering deals with the quality issues that arise during construction of applications involving computers and systems. How do we precisely determine all that an intended program is supposed to do? And how do we proceed in situations where we can't know everything about a proposed system in advance? How do we know a proposed system will actually solve a given problem? How do we communicate our needs among developers, and how do we keep them working together productively? As the system is constructed, how do we confirm that it does what we really wanted it to do? Among all the ways one might solve a problem, which designs and implementations will bring the lowest costs, least risk and greatest long-term value? 435 will address these questions and many more.
Because this is a 'capstone' course, we are interested in ensuring that not only do students have knowledge of software engineering topics, but also that you have given us an evidence-based way to confirm whether you possess skills and exhibit professional patterns of thought which are appropriate to our discipline. We require substantial pre-reqs to enter the class in anticipation that we will integrate your prior preparation with our content, then we will help you learn better how to apply it. Our target goals are thus substantial, and our strategy for reaching them involves solving a challenging problem in collaboration with other students on your team.
Copyright © 2015-2017, James M. Purtilo