This is at least the ninth time the course has been taught.
There are significant improvements between the 2nd and 3rd editions
so you should not buy older editions. The book store has copies. You can
buy or rent it there.
- Applying UML and Patterns: An Introduction to Object-Oriented Analysis and
Design and the Unified Process, 3/E
- Craig Larman
- ISBN: 0-13-148906-2
- Publisher: Prentice Hall PTR
- Copyright: 2003
We will not have time to cover chapters 21, 22, 28, 29, 30, and 33
through to 40.
There is a lot of wisdom in them
but there won't be any assessment
made of the content. So you can do the minimum on the following topics:
There will be no tests of your knowledge of the history in the book -- but
knowing the history will help you recall the best practices.
- -- Tools and Management
- -- Persistence -> data base classes
- -- UML Components
- -- UML Activity Diagrams (CS557)
- -- UML State Machines -> Comp Sci Theory
- -- Documenting architectural decisions
- -- User Interfaces -- frameworks, design, etc.
- -- Physical Architecture -- Artifacts and deployment (CS557)
- -- Deployment Diagrams (CS557)
- -- Some advanced Patterns (TBA)
I will be stressing
(In this class I use the number of asterisks to indicate how important a topic
is in the assessment. )
- *** Use cases and scenarios
- ** UML Relations between use cases.
- *** Quality/Non-functional requirements
- *** Class diagrams: domain and design models
- **** Interaction diagrams
- *** GRASP
- *** Logical Architecture -- especially layered architecture and Model-View-Controller -- (MVC)
- ** GoF -- Gang of Four Patterns
The mission of the course is to give you skills and attitudes you can
use to produce modern object oriented software using a light and agile
process that gives programs to your stakeholders and clients that they
value highly: now and in the future.
A detailed list of objectives can be found
[ objectives.html ]
on the course web site.
(N): Reading. ( 2 points >< 19)
- Start with the web site. It lists the assigned reading
for each class and
tells you how important the different topics are.
- Read the assigned pieces of text and take notes.
- Follow the links to the review questions. Answer as many as you have time for.
- Write down your name, one(1) question and your answer on a piece of paper
and hand it in at the start of class for grading.
(P): Turn up on time and be ready to work and participate in
the classroom activities. In the first class I will give a lecture.
Normally I minimize the lecture in favor of activities.
You will be working on projects,
exercises, etc. (2 points).
(W): In 9 classes a previously assigned piece of work
[ projects.html ]
will be presented
and collected. This will be a series of iterations
in a software project. Each starts at the end of the class before the
Each piece of work is worth 10 points maximum. Bring
whatever you have got at the time to class.
Late work scores nothing. Bad or incomplete work can score
Make a presentation (4 points) in class.
I may even ask you to demonstrate how a set of objects carry out
some task. Then submit
documentation(6 points) to me.
These artifacts can be hard copy or on the Web.
You can do the deliverables by hand
or using CASE tools as you wish.... but it should be readable
and spelled correctly. You can even submit photos of diagrams sketched on a
(Q): In 9 classes there will be a Quiz worth 15 points (maximum) on the
topics covered in the course up to that time -- but mainly on the most
(Bonus): You can earn 5 points each time you attend a CSE seminar
[ ../seminar/ ]
and within 24 hours email me a short message that reports on the seminar.
There will be a comprehensive final that will cover all the assigned readings,
all the work done in class, all the review questions, and your team project.
[ mock.html ]
is the format and topics in the previous final.
I will be following my generic grading scheme
[ ../syllabus.html#Grading ]
with these rules:
An up to date schedule is maintained at
[ schedule.html ]
on the web site. This tells you what assignments
are due when. This includes all the assigned reading/study
listed by the date due.
[ http://cse.csusb.edu/dick/cs375/ ]
the course web site. It has
up-to-date and reference information. Try the [Search______ ]
on all these pages.
The pages also have a [Contact] button at the top to send me Email.
My phone number, office, and calendar are here
[ http://cse.csusb.edu/dick/ ]
and in my generic syllabus. Come and see me!
- No more than 300 points can be earned for course work
(prior to the final) even counting bonus points.
- Bonus points can not effect the score on the final.
. . . . . . . . . ( end of section CSE375 Requirements Analysis and Design Syllabus) <<Contents | End>>