In this course, we will learn about software engineering by creating a significant piece of softwarea large, multi-faceted software system. This will be a team project in which the class will be formed into sub-teams that tackle specific parts of the design, and integrate their pieces into a whole.
We will learn how to design software by reading case studies of large software design projects, considering theory of well-designed software, and reflecting on the design process as our own projects are underway.
From a technical perspective, we will:
- Discuss requirements elicitation, agile design, the role of documentation, design patterns, test-driven development, the second-system effect, and the role of community / peer-pressure in sotware design.
- Work with source code control
A Bit More...
To generalize, there are two types of software engineering classes one in which everyone builds the same thing, and one in which everyone builds something different. The former is good because it lets instructors focus in on specific and particular theoretical material. Instructors know exactly what problems you will be encountering as you write code, because they have created the design challenges expressly to expose certain ideas! A great example of this type of class is MIT's course 6.170, Laboratory in Software Engineering.
On the other hand you have courses that are more representative of life in the unstructured real-world, where every project is indeed different. As described by Diane Pozefsky in her Software Engineering Laboratory at UNC, this course is a faculty-coached team project. Student teams in this type of class might each have a different client and be working with wholly different software technologies.
Here, we will take a middle ground. Primarily, we will have project implementation as the heart of the class. But we will all be working a joint project, and will share code and technologies.
We will use one required book. It is ordered and available now at the UML North Bookstore. Please buy it there to make sure you have it right away:
There will be other readings, including essays published on the web and material photocopied from out-of-print books. The latter will be handed out in class. The current reading assignment is always here.
This is a project-driven course with a reading component. Discussion, writings, and other reflections on the readings will illuminate your design process as you are engaged in your own software development.
The first third of the course will involve traditional weekly assignments.
This will be followed by two (approx. 5 week each) software development cycles.
We will standardize on Ubuntu Linux as the development operating system, and Emacs as the text editor. We will have coding standards that will be easier to keep uniform if everyone uses Emacs.
Command line tools will be used for source code management and build.
During the first third of the course, work will be done individually.
During the second two-thirds (the software development cycles), work will be done in teams of two to three persons.
Teams will rotate between the first development cycle and the second.
Discussion Group / E-Mail List
We will use Google Groups for class conversation and announcements. Please join this group. I'd advise setting it to send email to you directly.
|Subscribe to 91412-f11|
|Browse Archives at groups.google.com|
The group address is firstname.lastname@example.org. You have to be a member to send to the list.
The following plan will be used in determining course grades:
|First third of course|
|15%||Classroom and online participation|