|
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Project Manager
|
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 |
Gimourginas, James George |
| Boamah, Isaac Brentuo | ||
| Ahn, Sunjoo April | ||
|
Coding |
Kim, Janet Bokyung | |
| Somaram, Johnson K | ||
| Adewuyi, Babatunde Adebola | ||
Team 2: TerpWord Word Processor with Graph/image display capability |
Testing |
Lam, Dorothy Chi Ying |
| Bedrossian, Adam Jerry | ||
| Patel, Chintan Pankaj | ||
| Singh, Jawahar | ||
|
Coding |
Berch, Joshua Hershel | |
| Chen, Wenchao | ||
| Collins, Joel David | ||
|
Team 3: TerpSpreadsheet Spreadsheet program |
Testing |
Glinkowski, Magdalena |
| Fu, Tony | ||
| Palliparambil, Ashy Antony | ||
|
Coding |
Hill, Michael David | |
| Hsu, Daniel Jen-Dee | ||
| Ivanov, Alexei Borisovich | ||
| Johnson, Johny Kurichiel | ||
|
Team 4: TerpPaint Paint Program |
Testing |
Bento, Ana Leticia Ferreir |
| Kim, Eli Hyunjin | ||
| Laszlo, Istvan | ||
|
Coding |
Lawless, James Albert | |
| Luo, Ming | ||
| Ma, Kin-Pong | ||
| Min, Michael Young-Chan | ||
Team 5: TerpPresent Object-based drawing and Presentation Tool |
Testing |
Sivaramakrishnan, Harihara |
| Mohapatra, Pramit | ||
| Mowry, Jonathan Tyler | ||
| Nguyen, Kim T | ||
|
Coding |
Nguyen, Vinh Xuan | |
| Pourahmadi, Narimaan | ||
| Rauf, Basit | ||
|
Team 6: TerpManager An Explorer |
Testing |
Snider, David Richard |
| Shafrir, Michael | ||
| Winemiller, Mark Ryan | ||
|
Coding |
Wong, Lok-Yun | |
| Yan, Lei | ||
| Zimmerman, Noah Herzenberg |
I will give you an initial set of requirements for a desired software product.
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 | Testing | Summary: GUITAR Tests & Update bug-reports for Version
2.0
Deliverables
Successful/unsuccessful log files (automatically generated by GUITAR). 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. 22 | ||||||||||
| 2 | Coding | Summary: JavaDoc Files Creation, Unit Test Cases & Update bug-reports for
Version 2.0
Deliverables
|
Feb. 22 | ||||||||||
| 3 | Testing & Coding | Summary: Requirement Analysis Document
Deliverables
|
Mar. 7 | ||||||||||
| 4 | Testing | Summary: Design Document
Deliverables
|
Apr. 4 | ||||||||||
| 5 | Coding | Summary: Complete Working Software Code
(Version 3.0)
Deliverables
|
Apr. 4 | ||||||||||
| 6 | Testing | Summary: GUITAR Tests & Update bug-reports for
Version 3.0
Deliverables
Successful/unsuccessful log files (automatically generated by GUITAR). 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. 18 | ||||||||||
| 7 | Coding | Summary: JavaDoc Files Creation, Unit Test Cases & Update bug-reports for
Version 3.0
Deliverables
|
Apr. 18 | ||||||||||
| 8 | Testing | Summary: User Manuals (User Guide) and update Web-site for Version 3.0 | May 09 | ||||||||||
| 9 | Coding | Summary: Debugged Final Deliverable (one-click installable) Code for Version 3.0 | May 09 |
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 be accepted with a 10% penalty per day. 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.
|