.: SWE699/IT8212 Assignments

There will be a total of three assignments, as detailed below. There will be no exams for this course.

Assignment 1 (20%): Evaluation of a Model-Driven Development Tool (iLogix Rhapsody)

The objective in this assignment is to gain experience with iLogix's Rhapsody tool. A small problem statement will be assigned. Students must develop a state machine model in the tool and then use the tool's code generation capabilities to generate a working implementation. This assignment will be done individually.

Handout date: Sep 7. Due date: Sep 28.

Assignment 1 Description
Designing a Home Alarm Using the UML

Assignment 2 (30%): Presentation of a Model-Driven Development Tool.

Students will work in pairs and will each evaluate and present a tool from a list provided by the instructor. Choice of tool for each group will be made in discussion with the instructor. The deliverable is a report providing a summary of the tool's capabilities and a critical evaluation of the tool in terms of its support for model-driven development. The results will also be communicated to the rest of the class as a presentation towards the end of the semester.

Handout date: Sep 7.
Tool selection due date: Sep 21
Due date: Nov 9.

Assignment 2 Description

Assignment 3 (50%): Identification and Solution of a small research problem in model-driven software development.

In collaboration with the instructor, students will work in pairs to identify a small research problem, produce a sh0rt literature survey related to the problem, write a research report documenting a proposed solution to the problem, and present the problem and its solution to the class. Consultation time with the instructor will be provided both in class and during office hours. The research problem will be small in scope and will be chosen from a list of topics provided by the instructor. (Students may also propose their own topics).

Handout date: Sep 7.
Problem Selection due date: Oct 12
Literature Survey due date: Nov 16
Final report due date: Dec 14

Assignment 3 Description

Note: the list of topics given in the assignment description is incomplete. I'll add more suggested topics below as I think of them:

• Define a transformation for mapping an OO analysis model to an OO task architecture (e.g., using COMET task structuring guidelines)
• Application of the composition filter approach to modeling
• Experimental evaluation of aspect-oriented programming

Note to students: these 3 assignments run concurrently. It is the responsibility of the student to schedule his/her time so that each assignment is given sufficient time and focus.

Tool Presentations

Each pair of students must present their assignment 2 report. These presentations will last for 15 minutes with an additional 10 minutes for questions/discussion. The presentation may be given by one person or by both. Scheduling is as follows (in the order given):

Nov 16: donley, jayaraman, rufai, street, liles, anwar

Nov 30: vardhan, jadhwani, massie, icore, church, lahjouji

Research Presentations

Each pair of students must present their assignment 3 report. These presentations will last for 15 minutes with an additional 10 minutes for questions/discussion. The presentation may be given by one person or by both. Scheduling is as follows (in the order given):

Dec 7 : donley, jayaraman, icore, glass, liles, anwar

Dec 14 : vardhan, jadhwani, massie, rufai, church, street