Syllabus for SSE 550
Object-Oriented Design I
Fall Semester 2013 (13F)
Early version, changes are possible.
Instructor: Dr. Paul E. MacNeil
Office: Suite
223a, School of Engineering
Phone: 478-301-2185
Email: macneil_pe@mercer.edu
Back to Top
Textbooks and Supplies:
Texts
(including web sites):
(Read the Important Note
(below the list of texts) before you buy! Three books are
listed as
"required",
but only one is required; which text is required depends on
your choice
of
language.)
- Head First Java (2nd ed.) ,
by Kathy Sierra and Bert
Bates, O'Reilly Media, Inc. ISBN 0596009208 (2005) (Required for
the
Java option only!)
Download the Java errata.
- Head First C# (2nd ed.) , by
Andrew Stellman and Jennifer
Greene, O'Reilly Media, Inc. ISBN 1449380344 (2010) (Required
for
the C# option only!)
Download the C# errata.
- C++ Primer Plus (6th ed.),
by Stephen Prata,
Addison Wesley ISBN 978-0-321-77640-2 (2011) (Required for the C++
option
only!)
To download the C++ errata click on the "Updates" tab.
Back to Top
Software
(including web sites):
- A software development environment for your language of choice (C++, C#, Java) (Required, but your choice.)
- TBD - more information will be forthcoming
- An Internet ftp client of your choice. Core FTP LE is
free and works well http://www.coreftp.com/
. (Required, but your choice)
Back to Top
Back to Top
This is a
beginning course in object-oriented development. It may be
taken
in one of several object-oriented languages, e.g., C#, Java, or
C++.
This
Online Learning course begins on August 20, 2013.
Back to Top
Breadth and
Depth in Defining, Analyzing, and Solving Complex
Problems:
- After
successfully completing this course, you should be able to
demonstrate a basic capability to apply Object-Oriented
Programming (OOP) design techniques to solve
complex problems.
- After
successfully completing this course, you should be able to
demonstrate a basic ability to communicate regarding the
application of
OOP design techniques to a technical audience.
Back to Top
SSE
graduate standing or permission of the SSE graduate
chair.
Back to Top
- The Online Learning
asynchronous "meetings" take place in
Cyberspace; i.e., on the Internet.
Back to Top
Item
|
Percent of Term Grade
|
Project 1 |
20
|
Project 2 |
30
|
Project 3 |
40
|
Listserv contributions
|
10
|
Credit will be given only for
original work.
Project reports are to be submitted complete, not as incremental
partial submissions.
Listserv Contributions
- The Listserv contribution grade
will be awarded based on the
professor's professional judgement regarding your
contributions to the
course.
- Course-specific listserv
messages are for technical issues,
technical solutions, and other substantive material relevant
to the
course subject matter. Other course-related items (questions,
procedural issues, etc.) are also welcome.
- There is another listserv that
is not specific to any one course.
Messages on this listserv are for software engineering-related
items
that are applicable to several courses or to no course.
- If you have a question about
any of this, please ask
More information about
grading is contained in the General Project Rubric .
Back to Top
- Purpose of
projects:
- Use the projects to
develop your capabilities, and
- Use the projects to
demonstrate your capabilities.
- Deliverables
for all projects:
- Projects may be
delivered either via the course FTP site;
both of these will be announced.
- Your report, if
delivered via the FTP site should be a
single, standalone document .pdf (preferred), or .doc, or .docx format,
or a single
set of appropriately linked html pages.
- Project reports should focus on the development and/or
maintenance that you actually do. Reports should not focus on
summarizing or explaining the text or other materials.
- Inclusion of screenshots demonstrating your work, and code
you actually wrote for the project, are appropriate. Long code
listings can be placed in appendices if doing so does not
interfere with you presenting your work on that code in the
body of the text.
- Your report should
be organized in such a way as to make the
topics that you want credit for covering easy to find, and
demonstrate
your capabilities clearly and convincingly. Everything you
want
considered for credit, including code and tests (including
test
results), should be included in the report.
- Each project can be
a single, integrated project that tries
to actually do something, or a collection of exercises
that demonstrate
your capabilities but don't accomplish anything else, or
any
combination of these two alternatives that you find
convenient
- You may include
other material outside of the report (on the
FTP site), if you wish, but this material may or may not
be considered
in evaluating your work.
- For each capability
that you demonstrate within a report or
major section of that report, you may present only the
final result of
your work; you need not demonstrate every step in the
development of
that result.
- Some
suggestions for doing a project are contained in the One Way to Do a Project page.
- Project 1 (solo):
- Java Option : Develop and demonstrate
your
capabilities in the topics covered in Chapters 1 through 10
of the
(Java) text.
- C# Option : Develop and demonstrate your
capabilities in the topics covered in Chapters 1 through 7
of the (C#)
text.
- C++ Option : Develop and demonstrate your
capabilities in the topics covered in Chapters 1 through 4
of the (C++)
text.
- TBD.
- Project 2 (solo):
- Java Option : Develop and demonstrate
your
capabilities in the topics covered in Chapters 11 through 14
of the
(Java) text.
- C# Option : Develop and demonstrate your
capabilities in the topics covered in Chapters 8 through 11
of the (C#)
text.
- C++ Option : Develop and demonstrate your
capabilities in the topics covered in Chapters 5 through 7
of the (C++)
text.
- TBD.
- Project 3 (team):
- Java Option : Develop and demonstrate
your
capabilities in the topics covered in Chapters 15 through 18
and
Appendix B of the (Java) text.
- C# Option : Develop and demonstrate your
capabilities in the topics covered in Chapters 12 through
15` of the
(C#) text.
- C++ Option : Develop and demonstrate your
capabilities in the topics covered in Chapters 8 through 11
of the
(C++) text.
- You may form your own teams. Announce your team's
composition
via the course listserv.
- Two person teams are strongly prefered; three person teams
require the prior written (email is okay) approval of the
professor.
- TBD.
- TBD
Back to Top
- Asynchronous
Learning Nets (ALNs)
-
- Self
Study: You study the texts and any other course study
material on your own(team).
- Collaborative
Projects: After your self-study, you
collaborate (via the Internet [email]) with your
partner(s) to produce
a team product. Your collaborative work is substantial,
asynchronous,
and rapid.
- This
course is an online learning course. Please read this Online Learning web page
regarding
online learning in this course and this program.
Back to Top
(team)
- Subscribe to the course email listserv. Your professor can tell you how to
do this.
- Study the assigned material.
- Write and read email messages about ideas, problems and
solutions
to do with the assigned study material.
- Do the assigned work, deliver the assigned deliverables.
- Write and read email messages (to/from the listserv) about
ideas,
problems and solutions to do with the assigned homework.
- Review the deliverables produced by other people.
Back to Top
Changes to this Syllabus:
There will be changes to this syllabus, so check back frequently,
and don't
forget to hit "Reload" or "Refresh".
Start Date
|
End Date
|
Activity/Event
|
August 20, 2013 |
December 6, 2013 |
Course in Progress |
|
NLT August 27, 2013
|
Identify your selected
language for this course in an email message to the _course_
listserv.
|
August 20, 2013 |
September 24, 2013 |
Work on Project 1 |
|
September 24, 2013 |
Project 1 due. |
|
October 22, 2013 |
Project 2 due. |
|
December 6, 2013 |
Project 3 due. |
|
December 6, 2013 |
Course ends. Firm date. |
Notes:
tbd
Back to Top
Contact
Information
- My Name: Dr. Paul E. MacNeil
- My E-mail: macneil_pe@mercer.edu
.
- My Office Phone: 478 301-2185
- US Mail:
- Dr. Paul E. MacNeil
- School of Engineering
- Mercer University
- 1400 Coleman Ave.
- Macon, GA 31207
Back to Top
Important Additional Information:
“Students requiring accommodations or modifications for a disability
should inform the instructor at the close of the first class meeting
or as soon as possible. The instructor will refer you to the ACCESS
and Accommodation Office to document your disability, determine
eligibility for accommodations under the ADAAA/Section 504 and to
request a Faculty Accommodation Form. Disability accommodations or
status will not be indicated on academic transcripts. In order to
receive accommodations in a class, students with sensory, learning,
psychological, physical or medical disabilities must provide their
instructor with a Faculty Accommodation Form to sign. Students must
return the signed form to the ACCESS Coordinator. A new form must be
requested each semester. Students with a history of a disability
perceived as having a disability or with a current disability who does
not wish to use academic accommodations are also strongly encouraged to
register with the ACCESS and Accommodation Office and request a Faculty
Accommodation Form each semester. For further information, please
contact Carole Burrowbridge, Director and ADA/504 Coordinator, at
301-2778 or visit the ACCESS and Accommodation Office website at
http://www.mercer.edu/disabilityservices.
Accreditation: Mercer University is accredited by SACS.