Software Engineering

Spring 2002; CMSC 435; Section 0301

Course Information
Class Schedule
Course Readings
Atif M. Memon's Page
Send Atif an e-mail
Send the TA an e-mail



    I will partition the class into teams of approximately eight students. Each team will consist of a testing and verification group (group 1) of four students and a coding group (group 2) of four students. The following chart summarizes the duties of these groups:

    The project manager will be a member of one group.

Team Group type STUDENT NAME
Team 1: Calculator with Filing capability Testing Andryuk, Jason Paul
Baqai, Haroon Rasheed
Beninghove, Jeff Mark
Brunetto, Michael Thomas
Coding Chan, Chi-Chung
Cheung, Chun Pan
Choi, Ha Wing
Dean, Justin Wendell
Team 2: NotePad with Graph/image display capability Testing Donohue, Paul Stanley
Emminizer, Daniel Matthew
Gilhool, Matthew James
Gnatiko, Komi Agbemon
Coding Goldgeier, Michael Brian
Gomes, William J
Hashemi, Navead A
Hillery, Nathan
Team 3: Spreadsheet program Testing Hughes, Adam R
King, Jason Matthew
Klancer, John C
Ko, Kenneth
Coding Kolawole, Olufolajimi Abay
Kuklov, Danila S
Kwong, Kayee
Lam, Chi-Ming
Team 4: Paint Testing Lang, Jeffrey A
Liu, Mark Pan-Chi
Liu, Wai Fai
Liu, Yang
Coding Locke, Thomas Gregory
Modaressi, Mark Bijan
Mudd, Gregory Scott
Mundy, Marshall Wilson
Team 5: Object-based drawing Testing Nixon, James Vincent
Park, Anthony Daesung
Pearlman, Jason Richard
Pillalamarri, Anupama
Rajan, Sahil
Coding Rastogi, Anshuman
Ray, Justin Alan
Relunia, John Paul Asuncio
Shafi, Omer Muhammad
Team 6: Integrator Testing Shah, Jigar Nikunj
Smith, Andrew Benton
Soe, Pyi
Sun, Wei
Swift, Brian Lee
Coding Thoundayil, Jerry A
Torres, Manuel Luis
Ulanow, Jason Adam
Wolkoff, Ian Scott


Project Requirements

    I will give you an initial set of requirements for a desired software product, the class project. 

What you need to do

    Starting from the project requirements, you will develop a complete set of requirements, design a system that meets these requirements, and finally create and test a software system that implements your design. At each step in this process you will produce corresponding documentation. All documents must be submitted in electronic format and must be written in English. You must also submit an evaluation of yourself and each of your team-mates at each of these stages.

Project Schedule




Due Date

1 1 & 2 Requirement Analysis Document Feb. 15
2 1 & 2 Design Document Mar. 7
3 1 Test Plan Including Executable Specifications (Preconditions/postconditions), Scenarios, event-flow graphs, integration tree, & Test Cases. The specifications for the test cases are:
The structure of each test case is [initial GUI state, event sequence, final GUI state]
length is the total number of events in the test case
You will use 3 ways to generate test cases
event-flow graph/integration tree
You will submit total 100 test cases (note that no test case should be a prefix or copy of another). Generate:
30 test cases using the planner
lengths 1-10, 3 test cases of each length
30 test cases manually
lengths 21-50, one test case of each length
40 test cases using the event-flow graph/integration tree
lengths 21-60, one test case of each length
Apr. 8
4 2 Complete Working Software Code Apr. 8
5 1 & 2 Error and Coverage Reports Apr. 21
6 1 & 2 User Manuals May. 7
7 1 & 2 Debugged Final Deliverable (one-click installable) Code & Test Cases May. 7

Computing Resources

    The university computer labs should provide all necessary support for the project. Other resources normally available to you (e.g., home computers) can be employed, however you do this is "at your own risk." No alterations to conditions of the assignment will be made to accommodate peculiarities of your other computing resources.

Project Presentation

    All teams will present their project in class. Details of the presentation are available here. An evaluation sheet will need to be filled by every student.

"The dog ate my homework"

    Late deliverables will not be accepted. Start your projects early - last-minute computer malfunctions will not be accepted as reason for delaying an assignment's due date.


Back to Top

Copyright: Dept. of Computer Science, University of Maryland.
For problems or questions regarding this web, contact Atif M. Memon.
Last updated: April 18, 2002.