Instructor: Dr. Sergiu Dascalu
Room
SEM-236
Tel:
(775) 784-4613
E-mail:
dascalus@cs.unr.edu
Office hours: MW,
Course
outline: This capstone course represents a
coronation of the students’ academic work, involving the use of a significant
part of their computer science expertise acquired while in school. A
continuation of CS 425 Software Engineering, the course emphasizes team
collaboration and application of modern engineering approaches to software construction.
The development by each team of an original, industry-strength software product
is envisaged. The instructor will present lectures on the Unified Modeling
Language (UML) and its application to object-oriented analysis and design and
the teams will report on their progress by giving presentations and submitting
deliverables related to the project. In summary, the teams will present their
work at the following stages: topic proposal (the concept), software specification (the requirements), design (the
model), and implemented software (the
final product). At the beginning of
the semester the
teams will set up web sites for their projects, web sites that will be then
updated regularly to reflect the progress of the projects. At the end of the
semester there will be a public Senior Projects Workshop with project
presentations, demos, and posters.
Pre-requisites: CS
425 Software Engineering or instructor’s consent.
Texts: · The
required textbook for CS426 is Jim
Arlow's and Ila Neustadt's "UML and the Unified Process: Practical
Object-Oriented Analysis and Design," Addison Wesley, 2002, ISBN:
0201770601.
· A
recommended book for deciding on various
human-computer interface aspects of the projects (but not required for the test)
is Donald Norman’s “The Design of Everyday Things,” Basic Books, 2002, ISBN: 0465067107.
· For
each individual project an additional
book (“project domain book”) will
be consulted, together with at least four
reference articles (journal papers, conference papers, or web publications).
This extra reading will be assigned shortly after the project topics will be defined
by the teams. The project domain book and the articles will provide support for
broadly focused, multi-disciplinary and cross-cultural projects and will be
used as references in presentations and project deliverables.
Initial www pointers:
· The Object Management Group: www.omg.com
· IBM / Rational Software: www.rational.com
Several other addresses of websites
that contain useful project-related resources will be indicated later by the
instructor.
Grading scheme (subject
to minor modifications):
· Project Deliverables: 56%
- Concept (P-I) [ 4%]
- Specification (P-II) [11%]
- Design (P-III) [13%]
- Implementation, Integration, and
Testing (P-IV) [28%]
· Project Presentations and Publications 19%
- Presentations (specs, design,
workshop) (PRES-I, II, III) [ 9%]
- Project website (PWEB) [ 6%]
- Poster (POST) [
4%]
· Midterm examination (TEST)
16%
· Class participation (scheduled classes &
workshop, WS) 9%
Late
submissions:
Late submissions of assigned work
will be penalized with a deduction of 10% of the grade per late day, to a maximum
of two late days for each submission. No material will be accepted after two
days past the deadline. For example, a project deliverable that is worth 90/100
points will receive 90*0.9 = 81/100 points if it is one day late. The same
deliverable will receive 90*0.8 = 72/100 points if it is two late days and it
will not be accepted if it is more than two days late. Note that late days are
not divisible in subunits. Late days are not allowed for presentations, poster,
and test.
On
plagiarism and cheating:
Plagiarism and cheating will not be
tolerated. It will be dealt with according to the policies of the
Legal
notices on the world-wide web:
When accessing www
resources such as downloadable software, technical reports, papers, on-line
tutorials, etc., do not forget to read their accompanying legal notices and
comply with their provisions.
Tentative Schedule CS 426 Senior
Projects Spring 2004
|
Week |
Period |
Contents |
|
1 |
Jan 20 – Jan 23 |
Course
goals, outline and organization, project topics, workplan. |
|
2 |
Jan 26 – Jan 30 |
Lectures
on UML and UP: Requirements
Workflow, Analysis. Definition
of project topics. Project teams set (Jan 28) |
|
3 |
Feb 02 – Feb 06 |
Lectures on
UML and UP: Analysis. Draw for presentations’ order. Project concept deliverable due (P-I, Feb 05) |
|
4 |
Feb 09 – Feb 13 |
Lecture on
UML and UP: Analysis & Invited Lecture Project website set up
(PWEB, Feb 12) |
|
5 |
Feb 16 – Feb 20 |
Lectures based
on “The Design of Everyday Things”. Guidelines
for peer evaluation. |
|
6 |
Feb 23 – Feb 27 |
Lectures on UML and UP: Design Project specification deliverable due (P-II,
Feb 26) |
|
7 |
Mar 01 - Mar 05 |
Project specification
presentations (PRES-I, Mar 01
& Mar 03) |
|
8 |
Mar 08 – Mar 12 |
Project specification
presentations (PRES-I, Mar 08
& Mar 10) |
|
9 |
Mar 13 – Mar 21 |
Spring break, no classes |
|
10 |
Mar 22 – Mar 26 |
Invited lecture & Lecture on UML and UP: Implementation Project design deliverable due (P-III, Mar 25) |
|
11 |
Mar 29 – Apr 02 |
Recap for midterm exam
& Midterm
exam (TEST, Mar 31) |
|
12 |
Apr 05 – Apr 09 |
Project design presentations (PRES-II, Apr 05
& Apr 07) |
|
13 |
Apr 12 – Apr 16 |
Project design
presentations (PRES-II, Apr 12 & Apr 14) |
|
14 |
Apr 19 – Apr 23 |
Invited lectures (experts from industry,
business and research) Posters due (POST, Apr 19) |
|
15 |
Apr 26 – Apr 30 |
Project implementation, integration, and
testing deliverable & Internal project demos (P-IV, Apr 26
& Apr 27) |
|
|
Apr 30 |
Workshop presentations,
demos, and posters (WS, PRES-III) |