Link to approximate location of current lecture


YOU'RE HERE! Welcome to the Syllabus and Home Page for. . .

IFSC 7310 Information Systems Analysis
SPRING 2010, M 6:00 p.m. – 8:40 p.m. in ETAS 354

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: J. Arlow and I. Neustadt, UML 2 and The Unified Process: Practical Object-Oriented Analysis and Design, Addison-Wesley, 2005. ISBN-13 9780321321275, ISBN-10 0321321278.

Useful and recommended but not required (some lectures were originally developed using this book): 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,,, 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 and $10-$15 on up at 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 and 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,, 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

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: (Sun is the creator of Java and maintains a very extensive Web site)

The Sun Microsystems documentation start page is at:

See for descriptions of all classes.

See for a discussion group.

b)      Many useful books are described, and many available on-line, at See for example The Java Tutorial, Fourth Edition: A Short Course on the Basics by Sharon Zakhour, Scott Hommel, Jacob Royal, Isaac Rabinovitch, Thomas Risser, and Mark Hoeber; Prentice Hall PTR, 2006); ISBN: 0321334205.  Third edition, ISBN: 0201703939, is also good and much lower in price. 2nd edition is good too (still!).

c)      A free textbook on-line is at this site.

d)      Various other Java course Web sites with on-line lectures exist, for example,


Coordinator and instructor: Daniel Berleant

  1. Email:
  2. Office phone: (501) 569-3488
  3. Mail: Information Science, ETAS Bldg. Rm. 259D, University of Arkansas at Little Rock, 2801 S. University Ave., Little Rock, AR 72204
  4. Office location: ETAS Bldg. Rm. 259D.

Course Objectives:

  1. Ability to write a program in Java. Helps to better understand the software analysis and design process.
  2. Familiarity with the Unified Process software life-cycle model.
  3. Familiarity with the iterative development lifecycle, emphasizing object-oriented analysis aspects.
  4. Familiarity with non-UML, non-UP sofware project development concepts that are widely used in practice.


Topics Covered

bolded – updated for current semester

unbolded – from last semester, not yet updated for this semester


Part 1 of course: Java introduction and/or review



·   Introduction to the course – this syllabus

·   “Achieving your childhood dreams (really)” (see version with captions but may upload too slowly (start with part 1, not part 0); 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 (updates at ser. # 0)



·   Martin Luther King Day (Holiday)



·   Java introduction (ser. #1)

·   Java basics slides and version with program all on one page (ser. #2, 2a);

·   Strings notes; example strings program (in pdf-ized powerpoint) and (.java file format)

·   HOMEWORK #2: the problem of accountability in team projects



·   Event handling and GUI introduction; the sample program

·   GUI constructs and example program (AWT-based); sample program

·   (Old supplemental notes from previous semesters: GUI constructs and example program (swing-based); extra notes on GUI constructs)


Part 2 of course: The Unified Process (UP)



·   Snow Day



·   Research on mutation analysis (15 min. and 40 min. versions)

·   A review of OO analysis and design; survey (ser. #7)

·   HOMEWORK #3: Due in one week.

From previous semester: Team building exercise (ser. # 8); Larman HW



·   A review of the Unified Process; Schach’s temperate fruit system example (ser. # 9)

·   Case study, inception, and requirements (ser. # 10)




·  From inception to elaboration

·   Use case modeling I (ser. #11)

·   Historical note: old homework: answer all questions (designated by a question mark) in the “From inception to elaboration” slide set up to “Elaboration Questions II” & hand in. An older homework.



·   More on Use case modeling I (ser. #11)

·  Use cases II: granularity, EBPs, style

·  Modeling procedure (preview)

·  HOMEWORK #5 (due M 3/15/10): Please hand in a “fully dressed” use case for the some functionality of the system you worked on in HW4. See e.g. this template. Also include an example use case diagram. 5 pts. extra credit if you include brief and casual use cases.



·  Modeling procedure

·  Other requirements

·  HOMEWORK #6 (ser. #12)

·  Understanding plagiarism:,,,, extreme quoting is ok.

·  Supplemental: Use case modeling 3



·   Spring break, no class



·  Analysis (domain) models - introduction

·   More on domain models

·   Homework #7 , due WEDNESDAY (not Monday) April 7, 2010



Part 3 of course: non-UP analysis methods (based on Schach book)



·   Waterfall, Unified Process, Spiral Models, and Project Failure (ser. # 22 & see spiral-background…htm and spiral-Jones….pdf)

·   Project planning: decomposability



·   SPMPs; how number of people affects things (ser. #20)

·   Read An initial note on specifications (ser. #15)

·   The problem of good specifications (ser. #15)

·   Extra credit (10 pts.): obtain and hand in your certificate from

·   HOMEWORK #8 (due by Monday 4/19/10) (shorten? Too long?)



·   Specifications techniques (historical note: don’t do this old HOMEWORK ,  ser. =#15)

·   Data Flow Diagrams

·   Homework #9 (due by Tuesday 4/27/10):  (ser. =#15)

1.      Build three (3) data flow diagrams of the same system you worked with for HW#8. Start with the top level (context) diagram, then level it, then level that. For further info, there is lots about DFDs in the course notes and on the Web.

2.      Research on the Web to answer the question that came up in class, of just how relevant the DFD approach is in this day and age.

·   We are currently here in the syllabus. The information quality of the items below is limited, but provided for general information. REMINDER: bolded information is firm; unbolded information is tentative only.



·   PERT diagrams, Gantt Charts, & etc. (ser. #21)

·   Some research on PERT

·   Workflow diagrams

·   Three classic software project failures (see also 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

·   HOMEWORK, due next Monday (5/3/09), by 4:00 p.m. (2 hrs. before class) so that I have time to compile the powerpoint file: send me a couple of power points and prepare a 5-minute presentation on whether or not information systems analysis is relevant to information quality, information quality is relevant to information systems analysis, information systems analysis is relevant to your degree or your work, and/or anything else of this nature. 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?



·   Student presentations (offline) on SA and IQ

Makeup Day (if scheduled)

·   No makeup day. Build another snowman instead!



6-8 p.m.

·   Scheduled final period. Required only for students with missing assignments. Ser. #23



The information quality of the lecture topics next is limited. Provided for general information only.


Supplementary and historical topics:

W: Reviews, including walkthroughs and inspections; A SPMP inspection form; A DFD inspection form; a design inspection form; a code inspection form, ser. #10b

M: Exercise on inheritance, solution, inheritance notes

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

* Architectural analysis 

* More on domain sub/superclasses and the domain model

Use-Case Realizations

            HOMEWORK #11: due by class time on Thursday 11/3/05


Realizing init and UI; visibility
#12: small assignment due next time

Design Class Diagrams; old HOMEWORK

More GRASP Patterns

HOMEWORK #13: 2nd implementation

Some GoF design patterns; Strategy pattern in more detail

GoF Composite Pattern 


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


·       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:   The HWs will often be part of a coherent project. 

Exams and quizzes:

·     Exams (worth 100 pts.) and quizzes (worth substantially less than 100 pts.) are a possibility 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