Software Engineering

Spring 2003; CMSC 435; Section 0201

Home
Course Information
Class Schedule
Course Readings
Project
TerpOffice
Bug Database
Quizzes
Discussions
Atif M. Memon's Page
Send Atif an e-mail
Send the TA an email

Project

Teams

    I will partition the class into teams of approximately six students. Each team will consist of a testing and verification group (group 1) of three/four students and a coding group (group 2) of three/four students. The following bullets summarize the duties of these groups:

Project Manager
Testing and Verification Group (Group 1)
GUITAR Tests for Version 1.0
Update bug-reports for Version 1.0
VORD Documents
Scenario Creation for Version 2.0 with customer
Preconditions/postconditions
GUITAR Tests for Version 2.0
Update bug-reports for Version 2.0
User Manual Creation and Update website for Version 2.0
Coding Group (Group 2)
JavaDoc Files Creation for Version 1.0
JUnit Test Cases for Version 1.0
Update bug-reports for Version 1.0
VORD Documents
Implementation for Version 2.0
JavaDoc Files Creation for Version 2.0
JUnit Test Cases for Version 2.0
Final Installable (one file) Software Creation for Version 2.0

    The project manager (marked in red below) will be a member of one group.

Team

Group type

STUDENT NAME

Team 1: TerpCalc

Calculator with Filing capability

Testing

Aluthgedara, Nilani

Bhuta, Brian S

Jeng, Mary

Coding

Chang, Deborah Dinhwei

Chen, Chun Yang

Conti-Vock, Christian Crai

Team 2: TerpPad

NotePad with Graph/image

display capability

Testing

Del Mundo, Anton Paolo Cab

Dill, Richard

Divock, Jason Lance

Coding

Gebremichael, Martha Semer

Ghosh, Anita

Gloster, Nekoro Kofi

Team 3: TerpSpreadsheet 

Spreadsheet program

Testing

Hannon, Patrick Michael

Husain, Nora Fatima

John, Johny

Kalelkar, Amar Arun

Coding

Koo, Ricky S

Lam, Alvin

Lay, Serey

Team 4: TerpPaint

Paint Program

Testing

Lee, Devmann

Li, Yunpeng

Liu, Eric Lingchao

Nguyen, Mai Julie

Coding

Nguyen, Tu Duc

Ouh, Won Sun

Parsee, Shirin

Team 5: TerpDraw

 Object-based drawing

Testing

Patel, Amit Rajnikant

Purohit, Rooshi Rajendraba

Reichert, Joshua Thomas

Song, Chao

Coding

Tang, David A

Tung, William

Wallner, Joseph Lee

Team 6: TerpManager

Integrator

Testing

Wang, Danny Yu-Chun

Wang, Peggy Te-Hsing

Webster, Michael Andrew

Coding

White, James Patrick

Kwon, Soohee

Zhang, Grace Xinmei

 

Project Requirements

    I will give you an initial set of requirements for a desired software product. 

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

#

Group

Phase

Due Date

1 Testing Summary: GUITAR Tests & Update bug-reports for Version 1.0

Deliverables

  1. GUITAR Test cases

    Structural 2000 test cases (length 1 or more) + Coverage report (Method - 100% & Statement - 95%)

    Manual 900 test cases (length 20 or more)  + Coverage report (Method - 100% & Statement - 95%)

    Random 1000 test cases (length 30 or more)  + Coverage report

  2. Successful/unsuccessful log files (automatically generated by GUITAR).

  3. Printout of your Bug reports from Bugzilla (Bug reports should have description of Bug and the test case attachment that was used to detect it)

Feb. 24
2 Coding Summary: JavaDoc Files Creation, Unit Test Cases & Update bug-reports for Version 1.0

Deliverables

  1. Source code with JavaDoc comments (each relevant field should be filled)
  2. JavaDoc HTML output
  3. JUnit Test cases & their JavaDoc (Test Cases should have 95% Statement Coverage and 100% Method Coverage; Submit Coverage Reports)
  4. Printout of your Bug reports from Bugzilla (Bug reports should have description of Bug and the test case attachment that was used to detect it)
Feb. 24
3 Testing & Coding Summary: Requirement Analysis Document

Deliverables

  1. VORD templates 
  2. Viewpoint hierarchy
Mar. 10
4 Testing Summary: Design Document

Deliverables

  1. Get scenarios from customer via interviews
  2. 100 Executable PDDL Scenarios (Preconditions/postconditions). The structure of each scenario is [initial GUI state, event sequence, final GUI state]. 
25 sequences should be of length 1 or more. 
25 sequences should be of length 10 or more. 
25 sequences should be of length 20 or more. 
15 sequences should be of length 25 or more. 
10 sequences should be of length 30 or more. 
Apr. 7
5 Coding Summary: Complete Working Software Code (Version 2.0)

Deliverables

  1. Source Code
  2. Executables
Apr. 7
6 Testing Summary: GUITAR Tests & Update bug-reports for Version 2.0

Deliverables

  1. GUITAR Test cases

    Structural 2000 test cases (length 1 or more) + Coverage report (Method - 100% & Statement - 95%)

    Manual 900 test cases (length 20 or more)  + Coverage report (Method - 100% & Statement - 95%)

    PDDL Scenarios replayed using manual capture tool 

    Random 1000 test cases (length 30 or more)  + Coverage report

  2. Successful/unsuccessful log files (automatically generated by GUITAR).

  3. Printout of your Bug reports from Bugzilla (Bug reports should have description of Bug and the test case attachment that was used to detect it)

Apr. 21
7 Coding Summary: JavaDoc Files Creation, Unit Test Cases & Update bug-reports for Version 2.0

Deliverables

  1. Source code with JavaDoc comments (each relevant field should be filled)
  2. JavaDoc HTML output
  3. JUnit Test cases & their JavaDoc (Test Cases should have 95% Statement Coverage and 100% Method Coverage; Submit Coverage Reports)
  4. Printout of your Bug reports from Bugzilla (Bug reports should have description of Bug and the test case attachment that was used to detect it)
Apr. 21
8 Testing Summary: User Manuals (User Guide) and update Web-site for Version 2.0 May 09
9 Coding Summary: Debugged Final Deliverable (one-click installable) Code for Version 2.0 May 09

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: February 18, 2003.