
Computer Information Systems
INSS 540 - Information Mgmt Analysis and Design
IFSM 436 - Structured Systems Analysis and Design
| Location | London, England |
| Term 4 | Weekends: March 24, 25; April 7, 8; April 28,29; May 12,13 2001 |
| Time | Approximate daily schedule: 09:00-10:00 class, 10:00-10:30 break, 10:30-12:00 class, 12:00-13:00 lunch, 13:00-14:00 class, 14:00-14:30 break, 14:30-16:00 class. |
| Lecturer | Fred Swartz, Email: fred@leepoint.net, Phone: 07799 187-201 Homepage: www.leepoint.net/fred |
| Office Hours | TBA |
| Prerequisites | For INSS 540: INSS 510, 520, 530 or permission of instructor
For IFSM 436: IFSM 202 and CMIS 140, 150, or equivalent. |
| Credit | 3 semester hours credit |
Course Description
It is the job of systems analysis to plan how to design, develop, and implement information systems used by businesses. This requires a tool kit of techniques and procedures as well as communications skills to interact with users, programmers, managers, and executives.This course looks at each phase of information systems development - what it is and how to go about doing it. The result of the analysis is a model of the business and software systems solution. Object-oriented modeling will be emphasized, although the fundamentals of the structured approach will also be covered. Software development life cycle methodologies will be examined, with emphasis on iterative approaches. Analysis and design coursework will be required. There will be a group project, and graduate students will write an additional paper.
Text
Systems Analysis and Design in a Changing World by John W Satzinger, Robert D Burd, published by Course Technology, 2000Supplementary Reading (Required)
- Rapid Development: Taming Wild Software Schedules, by Steve McConnell, Microsoft Press, 1996.
- This is an excellent overview of software development approaches and best practices. There is quite a bit of "hard data" about what works (and what doesn't). Covers important topics that are missing from the text.
Course Objective
To provide general knowledge and understanding of all phases of information systems development. Students will be able to study an information system, define user requirements for a new system, propose and evaluate alternative solutions, develop a design for a new system, and understand system project management issues.Evaluation
Grades are based on the following weighting. Note that graduate students have a paper to write.| INSS 540 | IFSM 436 | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
For group work, the same grade will be awarded to each member of the group. Credit will be given for both content and written presentation.
Class Policies
Students are expected to read all assigned materials before each weekend class.Tentative Course Schedule
| Weekend 1 - March 24, 25 | ||
| Pre-Reading | Text: Ch 1, Ch 2 (skip pages 36-37),
Ch 3 (skip SDLC Variations, pp 75-80), Ch 4, Ch 5
Rapid Dev: none | |
| Saturday | am | Course orientation, introductions, Systems analysis - Big Picture |
| pm | Requirements, Modeling | |
| Sunday | am | Review, Quiz |
| pm | Modeling, Events, ERDs, Classes | |
| Weekend 2 - April 7, 8 | ||
| Due | Group project proposals. | |
| Pre-Reading | Text: Ch 6 DFD (skip 198-207),
Ch 7 OOAD
Rapid Dev: Ch 1-4, Ch 24 (JAD) | |
| Saturday | Requirements Analysis (JAD, Use Case, DFD), Object-Oriented Analysis and Design (OOAD) | |
| Sunday | am | Development strategies, mistakes, and fundamentals |
| pm | Midterm | |
| Weekend 3 - April 28, 29 | ||
| Due | Individual paper outlines. Group project use cases. | |
| Pre-Reading | Text: Ch 9 OOAD (skip 305-325, 341-343)
Ch 10 DB (skip pp 372-384)
Rapid Dev:Ch 6 Core Issues, Ch 7 Lifecycle Planning | |
| Saturday | am | Object-oriented concepts and UML |
| pm | Databases | |
| Sunday | am | Development Issues |
| pm | Software Development Lifecycle (SDLC) | |
| Weekend 4 - May 12, 13 | ||
| Due | Group Projects | |
| Pre-Reading | Text: (none)
Rapid Dev:Ch 11 Motivation, Ch 18 Daily Build and Smoke Test, Ch 20 Evolutionary Delivery, Ch 21 Evolutionary Prototyping, Ch 39 (Timebox Development), Ch 42 (User-Interface Prototyping) | |
| Saturday | Development Approaches | |
| Sunday | am | Review |
| pm | Final Exam | |