Link to
approximate location of current lecture
IFSC 7310 Information Systems Analysis
SPRING 2009, M
Object-oriented systems analysis and related
topics in the Unified Process software life cycle, including requirements and
business modeling disciplines. Related topics in non-object-oriented
systems analysis. Three lecture hours per week (three credit hours).
Textbooks and references:
Required: Applying UML and Patterns, second or third edition, by
Craig Larman, copyright 2002 (2nd), 2005 (3rd),
Prentice-Hall. The 2nd edition is just as good as the 3rd,
and more economical if you buy it used from amazon.com, half.ebay.com,
alibris.com, etc.
2nd
Edition says “SECOND EDITION” on the cover, and has an ISBN (above bar code on
back cover) of 0130925691. It is available as of 2008 for prices of about $5 on
up at half.ebay.com and $10-$15 on up at amazon.com. To find it reliably on
most book sites, use the ISBN as the search term.
3rd
Edition says “THIRD EDITION” on the cover, and has an ISBN of 0131489062. It is
available for around $40-$45 on up at half.ebay.com and amazon.com. To find it
reliably on most book sites, use the ISBN as the search term.
Do
*not* get the 1st Edition. Its ISBN is 0137488807 and it does not
say anything on the cover about what edition it is. It is available for under a
dollar (+ shipping) so if you paid that much you probably got the wrong book.
Potentially
helpful: portions of the course will be based on the following book by Stephen
Schach. It is available in several editions and even versions of the same
edition of varying title, any of which will be helpful. Many are
available at very reasonable prices on half.ebay.com, amazon.com, and other
vendors, and are perfectly adequate for this course. Some of the less expensive
ones are:
Sofware
Engineering, second edition, 1993, ISBN 0-256-12998-3;
Classical
and Object-Oriented Software Engineering, third edition, 1996, ISBN
0-256-18298-1
Software
Engineering with Java, third edition (Java version), 1997, ISBN 0-256-24167-8
Classical
and Object-Oriented Software Engineering with UML and Java, fourth edition,
1999, ISBN 0-07-230226-7
Object-Oriented
and Classical Software Engineering, fifth edition, 2001, ISBN 0072395591; sixth
edition, 2004, ISBN 0072865512; seventh edition, 2006, ISBN 0073191264.
Full
UML (Universal Modeling Language) description is available at http://www.omg.org/technology/documents/formal/uml.htm.
Required: A book that can answer your questions on the Java
programming language. You can get lots of them used at low prices on-line, or
buy one at any bookstore. Here are some links to further Java info:
a. Web sites: http://java.sun.com/ (Sun is the creator of
Java and maintains a very extensive Web site)
The Sun Microsystems documentation start page is at: http://java.sun.com/docs/.
See http://java.sun.com/javase/6
See http://java.ittoolbox.com/groups/groups.asp?v=JAVA-L
for a discussion group.
Coordinator and instructor:
Daniel Berleant
Course Objectives:
Topics Covered:
|
Part 1 of
course: Java introduction and/or review |
|
|
1/12/09 Monday |
· Introduction to the course – this syllabus · Achieving your childhood dreams (really) (see version with captions but may upload too slowly; faster youtube version here; see also the transcript) (dvd: ser. #2 of another course) ·
As time allows: work on HW 1 in class · HOMEWORK #1: "Hello World" due by next class |
|
1/26/09 Monday |
· Java
basics; Strings; Example strings program · HOMEWORK
#2: the problem of accountability in team
projects |
|
2/2/09 Monday |
· Event
handling and GUI introduction; sample program · GUI constructs and example program (AWT-based); sample program Supplement: GUI constructs and example program (swing-based);
some extra notes on GUI
constructs |
|
Part 2 of course: The
Unified Process (UP) |
|
|
2/9/09 Monday |
· An
overview of OO analysis and design;
survey (ser. #7) ·
HOMEWORK #3: Due in one week. From previous semester: Team building exercise (ser. # 8) |
|
2/16/09 Monday |
· An
overview of the Unified Process
(ser. # 9) · Case
study, inception, and requirements
(ser. # 10) |
|
2/23/09 Monday |
· Use
case modeling I (ser. #11) · HOMEWORK #4 (due M 3/9/09): Please
hand in a fully dressed use case (one copy per team) for the "use case
diagram editing" functionality of the UML editor system. See the
textbook and its example, e.g. on pp. 50-54 (2nd ed.), pp. 67-72
(3rd ed.). See also this template.
|
|
3/2/09 Monday |
·
Use
cases II: granularity, EBPs ·
Supplement/As
time permits: Use
case modeling 3 |
|
3/9/09 Monday |
·
Understanding plagiarism: http://www.indiana.edu/~tedfrick/plagiarism/index2.html,
http://www.nyu.edu/classes/op/writing/CourseBuilder/plagiarism/delfattore_frame.htm,
http://www.lib.umich.edu/acadintegrity/instructors/preventing/plagiarism.htm,
http://www.indiana.edu/~istd/test.html,
extreme quoting is ok. · HOMEWORK #5 (ser. #12) |
|
3/16/09 Monday |
· From
inception to elaboration (up to
but not including SSDs) · Domain
models - introduction · HOMEWORK #6, due next time: answer all questions (designated by a question mark)
in the “From
inception to elaboration” slide set up to “Elaboration Questions II” &
hand in. Extra credit (10 pts.): obtain and hand in your certificate
from http://www.indiana.edu/~istd/test.html · Historical note: an old homework
|
|
3/23/09 Monday |
· Spring break, no class |
|
3/30/09 Monday |
· HOMEWORK #7, due next time |
|
Part 3 of course: non-UP
analysis methods (based on Schach book) |
|
|
4/6/09 Monday |
· Read An
initial note on specifications (ser.
#15) · Read The
problem of good specifications and hand in exercises and answers to
questions therein, if you missed lecture due to equipment failure (ser. #15) · Read Specifications
techniques and hand in exercises and answers to questions therein, if
you missed lecture due to equipment failure (ser. #15) · HOMEWORK #8, due by Tuesday 4/14/09 |
|
4/13/09 Monday |
· Historical
note: HOMEWORK - build a data flow diagram of your use case diagram
editor system, due in one week. Show the result of each leveling step. You
may look up data flow diagrams on the Web for further info; ser. #15 |
|
4/20/09 Monday |
· Project planning: SPMPs; how number of people affects
things (ser. #20) · HOMEWORK #9 (due by Tues. 4/28/09) |
|
|
We are currently here in the syllabus. The information
quality of the items below is limited, but provided for general information anyway. |
|
4/27/09 Monday |
·
PERT
diagrams, Gantt Charts, & etc. (ser. #21) · Some research on PERT · Research on mutation analysis (15
min. and 40
min. versions) · HOMEWORK #10,
due next Monday (5/4/09), by 4:00 p.m. (2 hrs. before class) so that I have time to
compile the powerpoint file. · Historical note: HOMEWORK Due Wednesday 5/2/07. Sketch a PERT diagram for
the project shown as a Gantt Chart handed out in class. Make a Project Table.
What information, if any, in the Gantt Chart is missing in the PERT diagram?
The Project Table? Sketch a Gantt Chart diagram for the project shown as a
PERT diagram handed out in class. Make a Project Table. What information, if
any, in the PERT diagram is missing in the Gantt Chart? The Project Table?
Sketch a Gantt Chart diagram for the project shown as a Project Table handed
out in class. Make a PERT Diagram. What information, if any, in the Project
Table is missing in the Gantt Chart? The Project Table? |
|
5/4/09 Monday |
· Student presentations on SA and IQ · Information systems “horror
stories,” such as the Therac,
Mars
orbiter, Y2K bug and Conficker worm cases; POS problems; personal anecdotes, the myth
of invulnerability (we’ve muddled thru before so we will again), and the AI singularity. Also Ariane 5 and Patriot
Missile failures; a long list of software failures;
wikipedia article
on software disasters, and the "Stars"
system case |
|
5/11/09 Monday 6-8 p.m. |
· Scheduled final period. Required only for students with missing assignments. |
======================================
The information quality of the items
below is limited. Provided for
general information only.
======================================
Supplementary
and historical topics:
5/7/07,
M: Final. We will meet at the usual
time, but there will not be a “big test.” There will be an in-class exercise
worth 25 pts.
4/11/07,
W: Reviews, including walkthroughs
and inspections; A
SPMP inspection form; A
DFD inspection form; a
design inspection form; a code
inspection form, ser. #10b
2/5/07, M: Exercise
The mathematics behind
efficient project development by dealing with errors early.
SPMP
exercise (due next time), Assignment #N due next time at class time:
bring hard copy of the SPMP to class for your own use during class; do your
own DFD for your project and bring to class one copy for each team
member, including yourself. These items will be used for the session on
software engineering inspections, next time. (No need to do this old hw -Specifications
Exercise.) Assignment #11 - final
SPMP
Supplementary
topics II: design (outside scope of course but relevant nonetheless)
Design
Patterns; the
cohesion and coupling patterns
* More on domain
sub/superclasses and the domain model
HOMEWORK
#11: due by class time on Thursday
11/3/05
exercise
Realizing init
and UI; visibility
HOMEWORK
#12: small assignment due next time
Design
Class Diagrams; old HOMEWORK
HOMEWORK #13: 2nd implementation
Some GoF
design patterns; Strategy
pattern in more detail
exercise
Logical
architecture; GoF Facade
Pattern
Historical note from last
year: HOMEWORK
#14: (Small, but due in two days; this will give a week left to study patterns)
Review
of key points Possible Design
patterns test
Supplementary
topics III:
More on associations;
statecharts; More
architecture; review; Observer
Pattern; domain
sub/superclasses
Homeworks:
· Homework
assignments will mostly be worth 100 pts. HWs will often be done in teams of
3-4. Not all members of a team will necessarily get the same score.
Project component:
Exams and quizzes:
· Exams (worth 100 pts.) and
quizzes (worth substantially less than 100 pts.) will be occasional but
studying for tests will not be a major focus of the course.
Assignments,
Exams, Grading…:
· Latest
available grades
· Minimum grade on any quiz or assignment will be
50%.
· Grades on team assignments may be adjusted to
reflect individual contributions.
· Originality
will be worth 50% of each assignment, so be sure not to copy (or modify a copy)
of anyone else’s, and also be sure not to accidentally have your work look like
it might have been copied or modified from a copy of anyone else’s assignment.
I’m quite sure you can do this.
· Cheating
(that includes copying or modifying copies of others’ work) is subject to
university policies. I hope not to have to find out what they are.
· Letter grades
in the course will be assigned as follows (note that the registrar does not
permit +’s and –’s, so they will not appear on your transcript):
A (95-100%)
A- (90-95%)
B+ (86.67-90%)
B (83.33-86.67%)
B- (80-83.33%)
C+ (76.67-80%)
C (73.33-76.67%)
C- (70-73.33%)
D+ (66.67-70%
D (63.33-66.67%)
D- (60-63.33%)
F (50-60%)
If your grade is ambiguous
(e.g. exactly 90%) you will get the higher one.
Lateness policy: 10% reduction in the grade on any assignment handed in up to 1 week late. 30% reduction in grade on any assignment handed in more than 1 week late.
Special accommodations: If
you are not feeling well, see me about HWs, tests, quizzes, etc., that are
affected.
Disability Support
Services: It is the policy of UALR to
accommodate students with disabilities, pursuant to federal law and state law.
Any student with a disability who needs accommodation, for example in
arrangements for seating, examinations, note-taking should inform the
instructor at the beginning of the course. It is also the policy and practice
of UALR to make web-based information accessible to students with disabilities.
If you, as a student with a disability, have difficulty accessing any part of
the online course materials for this class, please notify the instructor
immediately. The chair of the department offering this course is also available
to assist with accommodations. Students with disabilities are encouraged to
contact Disability Support Services, telephone 501-569-3143 (v/tty), and on the
Web at http://www.ualr.edu/dssdept/.