COMP 320/420, Fall, 2015—Schedule

The details of this schedule may be adjusted during the course to reflect the backgrounds and interests of the students. Please recheck often.

Date Topic(s)
NOTE: The links below to presentation slides will be activated a day or two before the class session.
Reading
Web articles may contain links to other interesting items.
Asgn.
given
Asgn.
due
Aug. 24 Course introduction
Role of the systems analyst
Historical survey of systems analysis methodologies
-What Ever Happened?
-"Analysis & Design" Harmful
1 -
Aug. 31 Specifying system outputs
Components of a structured system specification
Overview of diagramming tools
Specifying scope and context of a proposed new application
Examples of context diagrams using G&S symbols and using DeMarco symbols
Robertson:
- Foreword by DeMarco
- Chapters. 1.1 & 2.1
Specifying Output Requirements
2 -
Sept. 7 Labor Day holiday - --
Sept. 14 Data item taxonomy
Abstract data types
Defining data items
Maintaining a data dictionary
-Defining Data Items
-Implicit Data Dictionaries
-Too many string data items
3 1
Sept. 21 Tying it all together with multi-level dataflow diagrams
Specifying the system diagram
Robertson: Chapter 2.2 & 1.2
Dataflow diagramming
4 2
Sept. 28 Specifying system inputs
Specifying processes, algorithms, and decision rules
Specifying system inputs
Robertson: chapter 2.12
Specifying processes
Decision tables
- 3
Oct. 5 Mid-term break - --
Oct. 12 I-P-O diagrams
Gathering information from the users
Specifying constraints
Specifying constraints
Results Are the Primary Concern
5 -
Oct. 19 Data modeling and entity-relationship diagrams
Compiling the complete system specification
Assignment #3: sample solution
Robertson: Ch. 1.18 6 4
Oct. 26 Mid-term examination (~75 minutes)
Launching the class project— (From this point on lectures and class discussions will be limited each week to about an hour. The rest of each class session will be available for the project teams to meet and work, with assistance as needed from the instructor.)
- Project -
Oct. 30 Drop deadline: Last chance to withdraw without academic penalty.
(Graded mid-terms will be available.)
- --
Nov. 2 UML overview and recommendations Mid-term suggested answers
Robertson:
  ch. 2.5, pp. 156-171
  ch. 2.6, pp. 180-187
- 5
Nov. 9 "Agile" methods and "emergent specifications" Requirements Are not Discrete
Robertson: Ch. 2.7
The Untrainables
7 6
Nov. 16 Use-Case documentation
User stories
Extreme programming flaw
Agile methods & component re-use
- -
Nov. 23 Shortcuts for purchasing packaged application products
Modeling sequence: physical and logical
Shortcuts for purchasing packaged application software
The Irrational Unified Process
- 7*
Nov. 30 The analyst's role in preparing the user organizations for the new system.
The analyst's role during final acceptance testing, installation, and start-up.
Project team presentations (optional)
Robertson: ch. 2.15 - Project**
Dec. 7 Final Examination
- - -

* Due to the bad weather November 21, Assignment #7 can be turned in any time before November 28.

** If the extra week would improve the quality of your team project, you may turn it in later in the final week of the course. However, if I receive it later than December 2, then you won't get to see the returned graded project before the final examination. In any case, in order to post the course grades on time I'll accept no work after December 7.

Last updated November 23, 2015