Software
Engineering
Spring 2002; CMSC 435; Section 0301
|
         
|
| 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 |
I will give you an initial set of requirements for a desired software product, the class project.
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.
| # |
Group |
Phase |
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:
|
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 |
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.
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.
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.
|
Copyright: Dept. of Computer Science, University of Maryland.
|
