CPSC 606 Software Engineering Project

Summer 2004

Test Your Knowledge

Overview

To construct an interactive web site for the students who want to know where they stand in terms of Software Engineering Knowledge by testing the following areas with different levels (basic, intermediate, advanced):

* Software development process (UPEDU, Waterfall, Spiral, etc.)
* UML designs/diagrams (use case, sequence, class diagrams, etc.)
* Quality of products
* Maturity of software processes (e.g., CMM)
* Security
* etc.

Your system should be developed as designed. The system will be documented using UML diagrams and implemented in your preferred object-oriented language. The designed classes (or components) should be implemented and used. Scripts cannot be used in replacement of "classes".

Assumptions/Constraints

* Should contain at least the followings: 3 different areas (fields), 20 topics (questions) per area, and 2 different levels
* Should be able to add new topics easily
* Should compare performance based on other university students values
* Should show the results using graphics (e.g., MS Excel type)
* Sholud implement what you specify in your UML diagrams
* Sholud choose the object-oriented programming language of your preference
* Should be innovative and creative
* Should try to demonstrate your project management and teamwork skills
* You may have the freedom to fill in the details of the project using your own knowledge and skills

Milestones

Deliverables (Subject to Change)

Assignments are due class time, unless specified otherwise.

Team Web site	July 9 (Friday)
Expanded Use Cases and Use Case diagram(s). * See Chapter 4 and Chapter 16 of Valtech's slides. * For the expanded Use Cases, follow the format in Chapter 4 pages 29-30. * Use Rational Rose tool to create your Use Case diagrams. * Post your *.mdl file in your Team Web site. Everything created in this project should be accessible from your Team Web site. * Submit hardcopy of deliverables.	July 15 (Thursday)
Project Plan	July 16 (Friday)
System Sequence Diagrams * See Chapter 8 of Valtech's slides * Derive System Sequence diagrams from your use cases * Use Rational Rose tool to create your System Sequence diagrams * Post your new *.mdl file on your Team Web site. * Submit hardcopy of deliverables.	July 19 (Monday)
Collaboration Diagrams using GRASP patterns	July 21 (Wednesday)
Class Diagrams * See Chapter 13 of Valtech's slides * Use Rational Rose tool to create your Class diagrams. * Post your *.mdl file in your Team Web site. * Submit hardcopy of deliverables.	July 24 (Saturday), extended
Project Report	August 9 (Monday), in class
Peer Evaluations	August 9 (Monday), in class
Developer's Manual (including code documentation (e.g. using javadoc))	August 9 (Monday), in class
User's Manual	August 9 (Monday), in class
CD containing all your project-related artifacts (codes, deliverables, presentations, manuals, etc.)	August 9 (Monday), in class