|
28483 CSC 4175N - 0 - Software Engineering 28484 CSC 177N - 0 - Senior Project
Spring 2005
CSC 4175N Tuesday, Thursday, 4:00 pm - 5:20 pm , Oakdale Campus KSC 102A
CSC 4177N TBA
Herbert J. Bernstein (yaya@dowling.edu)
Assignments
|
|
This web page is http://www.bernstein-plus-sons.com/.dowling/CSC4175S05/CSC4175_Assignments.html
Copyright © 2005 Herbert J. Bernstein and other parties. All rights reserved.
Projects
The best way to develop an understanding of modern software engineering
is by applying the tools of software engineering to a significant software
project. The class will form into a small number of groups (perhaps only 1).
Each group will work as a team to implement a significant software system.
Each group will be given the opportunity to identify a suitable project.
Students are urged to interview Dowling students, faculty and administrators
to find software projects that need to be done. Examples would be new and
useful record-keeping databases for departments or divisions, middle-ware query
systems which would extract new and useful reports from existing systems,
a new and useful scientific API, etc.
Students will be given two weeks to voluntarily form groups and
select projects. At the fifth meeting of the course, the class as a
whole, under the guidance of the instructor, will evaluate all proposed
projects and all proposed groups, and attempt to make a consensus
determination of project assignments. If this process fails to achieve
resolution within one class meeting, each student will be required to
write a detailed report with copies for all members of the class as well
as for the instructor. The report will analyze the outstanding problems
and recommend a course of action, and will be presented at the sixth
meeting of the class. If that does not result in resolution of
outstanding problems, the instructor will intervene as "chief decision
maker" and make the necessary assignments. No further changes in
project or in group assignments will be permitted during the
semester.
Assignments
Return to this page often to find new assignments and clarifications
to old assignments.
EXCEPT FOR ASSIGNMENTS #1, #2, #3 and #4, ALL ASSIGNMENMENTS ON THIS PAGE
ARE TENTATIVE AND SUBJECT TO CHANGE.
- Assignment #1, assigned Tuesday, 1 Feb 2005, due 8 and 10 Feb 2005
- Acquire your text books and a lab notebook with carbons. Read
pages 1-50 of Brooks. Read pages 1-91 of Sommerville. Do all
exercises. Be prepared to discuss readings and exercises.
- Start investigation of possible projects, keeping careful notes
in your lab notebook. Put your name, email address and date on every
page. Be ready to turn in the carbons on 10 Feb 2005.
- Prepare a short bio and skills inventory of yourself to share with
the class. Classify yourself as: leader, follower, or lone wolf.
Classify yourself as: Very organized, somewhat organized, or not
very organized. Classify yourself as: Highly skilled with
technology, somewhat skilled with technology, or not very skilled
with technology. Bring
enough copies for everybody to the meeting on 8 Feb.
- Assignment #2, assigned 8 Feb 2005, due 15 Feb 2005
- Read pages 51-83 of Brooks.
Read pages 92-141 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Put a preliminary design for the agreed project into your notebook.
Be prepared to discuss why this design is feasible. If the class
project is not yet agreed, put a preliminary design for the project
you favor into your notebook instead.
- Assignment #3, assigned 15 Feb 2005, due 22 Feb 2005
- Read pages 88-112 of Brooks.
Read pages 142-215 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- There should now be an agreed preliminary feasible design for the class project.
Bring it back to the people you have talked to about the
project before and discuss it with them. Record your discussions in
your notebook. Prepare a more detailed, updated system design, based
on your discussions. Prepare your best suggestions on project
schedule and task assignments. Be prepared to discuss.
- President's Day: Monday 21 February 2005, College Closed.
- Assignment #4, assigned 22 Feb 2005, due 1 March 2005
- Read pages 115-150 of Brooks.
Read pages 216-265 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Be prepared to report on your project progress.
- Assignment #5, tentatively assigned 1 Mar 2005, due 8 Mar 2005
- Read pages 153-160 of Brooks.
Read pages 266-312 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Be prepared to report on your project progress.
- In collaboration with your classmates, start on a combined
project web page on arcib.dowling.edu in the user account CSC4175S5a/b
Prepare a draft outline of the user manual and for the system manager's manual
for the system you all are creating, and post them to the project
web page as well as your own web pages,
with assigments as to who will be writing which sections,
and firm deadlines for that work. Post other project-related
materials to the project web page and invite your users to
review and comment on it.
- Assignment #6, tentatively assigned 8 Mar 2005, due 15 March 2005
- Read pages 163-175 of Brooks.
Read pages 313-338 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Be prepared to report on your project progress.
- In collaboration with your classmates, do an object-oriented
design (OOD) for your project and update the combined
project web page on arcib.dowling.edu in the user account CSC4175S05.
Try to make use of UML in preparing the the OOD, but don't let problems
with your tools prevent you from getting the OOD posted.
Add a full project timeline to the project web page, with all milestones,
including those that have been met.
Update the draft outline of the user manual and for the system manager's
manual
for the system you all are creating. Be sure not to remove the old
information from the outlines, but indicate both the old and the new and
how they differ. For all milestones, as the class meets them, be sure to
show both the original
planned date and the actual date on which it is met. Post all the new
material to the
project web page (as well as your own web pages if appropriate).
Post other project-related
materials to the project web page and once again invite your users to
review and comment on it.
- Assignment #7, tentatively assigned 15 Mar 2005, due 22 Mar 2005
- Be prepared for an open book, open notes midterm examination on
22 March 2005 and project presentations on 24 March 2005.
This is 20% of your grade. All materials in the readings and exercises to
date in both textbooks, all material discussed in class, and certain
information relating to your project are fair game. This examination is a
major component of the work for this course. See the syllabus on Grading
Policy. Students who miss or fail this examination will be given a formal
midterm warning and will be encouraged to withdraw from the course.
- Part of the midterm examination will be formal individual reports
of project plans and progress. Each report is to be presented orally and
backed by written report which is to be posted to the individual web page
prior to the presentation.
- The class project website and all individual participant web sites
and all submitted carbons as well as the daily quizzes will be evaluated
as part of the midterm grading. Failure to have completed all individual
efforts or failure to have
properly participated in collaborative efforts by 22 March 2005 will
result in a formal midterm warning and a recommendation that the
student(s) involved withdraw from the course. Missing carbons will
not be accepted after 4:00 pm, 22 Mar 2005. Missing
web sites will not be counted towards the midterm evaluation after 4:00
pm, 24 Mar 2005.
- Despite the heavy demands imposed by the midterm requirements
above, the timeline must also show significant progress on the project
itself during the week of 15-22 Mar 2005.
- Good Friday: Friday 25 March 2005, College Closed.
- Assignment #8, assigned 29 March 2005, due 5 April 2005
- Read pages 177-203 of Brooks.
Read pages 339-361 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Be prepared to report on the complete class structure for the
project, and to report subproject statuses.
- Assignment #9, assigned 5 April 2005, due 12 April 2005
- Read pages 207-227 of Brooks.
Read pages 362-387 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Be prepared to report on the complete class structure for the
project, and to report subproject statuses.
- Assignment #10, assigned 12 April 2005, due 19 April 2005
- Read pages 229-289 of Brooks. (Yes, that is a lot of reading,
but much of it is review and material you should now be very familiar
with).
Read pages 388-438 of Sommerville. Do all the exercises. Be
prepared to discuss readings and exercises.
- Be prepared to report on the
project as a whole, and to report subproject statuses.
- Assignment #11, assigned 19 April 2005, due 3 May 2005
- You have now finished Brooks. Write a short 2 page essay
summarizing the most important lesson you draw from reading
this book. Be sure to cite specific material from the book
with which you agree or disagree.
- Each student should prepare a list of 3 questions about
software engineering that you feel need to be reviewed before you take
the final exam.
- Read pages 592-640 of Sommerville. Use what you read there
and your own experience with the course project and with other
projects to prepare a realistic time and cost estimate for what
it would take to create a complete version of your project, starting from
the base of what has been done this semester, or, if you choose, starting
from scratch. Do your
estimate three different ways:
- Assuming you were going to do the project on your own.
- Assuming you were going to do the project with the
same team you are now working with.
- Assuming you were going to do the project with a
hand-picked student team chosen by you. You must name the team
members you would choose and give a brief justification
for your choices. The size of this team is up to you.
In doing your costing, assume that students cost $8.00 per hour.
Assume that institutional administrative overhead is 50% and
covers all institutional costs other than staff.
- Be prepared to report on the
project as a whole, and to report subproject statuses.
- Spring Recess: Saturday 23 April 2005 through
Friday 29 April 2005.
- Final Exam: The finals for this course will be in 2 parts at
the normal class meeting times: a written final exam on Tuesday 10 May 2005,
and final joint project reports on Thursday 12 May 2005.
You must each speak, but the division of labor as to who speaks
about what aspects of the project is up to all of you jointly. The
presentation should be a smooth, well-organized team effort, and should
take no less than 25 minutes and no more than 35 minutes total,
divided among all of you in speaking in whatever order you all jointly
choose. Even if you choose to do the presentation as powerpoint, an html
version of the presentation should be added to the course web page. There
will be a question and project evaluation session after the presentation.
All source code and documentation of the project as being reported
in the presentation should also be added to the course web page.
All major links from the course web page to student web pages
whould be brought forward to copies directly on arcib, so we
can be certain this web page will survive as an independent
entity in the future.
Updated 11 April 2005.
yaya@dowling.edu