ESOF 422: Software Engineering II

Spring 2014

Welcome to Software Engineering II

Software Engineering is not computer programming, but rather the practice of producing high quality software. Programming is but a part of this process and is extensively covered in the seminal years of your Computer Science degree.  This course focuses on the design and architectural specifications of software --early in the lifecycle, as well as the testing techniques that generally occur after the implementation phase --late in the lifecycle. In the first part of this course we will focus on advanced software modeling and specification techniques. We will discuss model-driven engineering through model driven software development and its support tools such as UML, USE and OCL. In the second part of the course we will focus on learning software testing techniques.



IMPORTANT:

This is a rigorous course that requires significant maturity and much of the work is intended for students that can work independently. Students are expected to be very familiar with all Object Oriented concepts as well as an excellent command of UML.

Meeting Times

• Tuesday, Thursday 9:25 - 10:40 in TCE 102.

Textbook

• Introduction to Software Testing, by Paul Ammann and Jeff Offutt: Required
• The Object Constraint Language Second Edition, by Warmer and Kleppe: Highly Recommended (Reference)
  

Grading

• Quizes and Homework : 50%
• Mid Term : 25%
  
• Final : 25%

Grading Policy

• If you come to class, read the assigned material, participate and contribute in class, and complete your homework you should do fine in the course.
• 50% of the grade comes from exams (a midterm and a final). To pass the course, you must average at least 50% on the exams. The midterm and final exams must be taken during their stated times and no make up exams will be given. Plan accordingly.
• 50% of the grade comes from your assigned homework.
  
• All homework will be done in pairs. You may choose a partner to work with during the semester. If you have not found a partner, you will be assigned one by your professor.
  

Instructor

• Dr. Izurieta EPS 356. 994-3720. Office hours are either when my door is open or Tuesday, Thursday and Friday's from 2-3pm.
• Email : clemente.izurieta(AT)cs.montana.edu

Policy

• You are responsible for any announcements made in class.
• No late submissions are allowed unless an emergency occurs. No exceptions.
  
• Unless otherwise stated, all work must be done with your team mate.
  
• Academic DISHONESTY will be dealt with severely. This should never be a problem, however instances of cheating do occur. There are web sites in the Internet that provide answers to high bidders. I do monitor these sites. If you do not know how to solve a problem, come see me!
• You are expected to attend class.

Course Outcomes

• Articulate what formal methods are.
• Be able to read and write formal specifications written in UML and OCL.
  
• Write and analyze specification constraints using OCL.
• Write SOIL to extend UML diagrams.
  
• Understand various software testing techniques.
• Form informed opinions about model-driven techniques and testing.
• Use a constraint solving tool --USE.
  
• Basics of fault tolerance (if time allows).

Software and Additional Reference Material

The following is a list of the software and relevant downloads that we will use throughout this course:

• USE: A tool for analyzing OCL constraints
• Papyrus: An Eclipse based UML tool
• Any tool your are comfortable using for UML modeling: ArgoUML, PlantUML, Visio, Rational, Altova, etc.