MBA 781S Structured Systems Analysis
Spring 2005
(Date revised: April 5, 2005)
|
Dr. Robert (Bob) Grenier |
|
|
Phone: |
(309) 762-7075 |
|
Email: |
Dr.Grenier@mchsi.com |
|
Home Page: |
http://dr.grenier.home.mchsi.com |
|
Office Hours: |
by appointment |
|
Class Meets: |
Tuesdays 6: |
Guide to the syllabus
This syllabus is subject to change! The current version is available on my web site at the following URL: http://dr.grenier.home.mchsi.com/syl781-2005.html
Prerequisites:
Course Objectives:
This course introduces the student to information systems analysis and design It is intended to prepare the student for analyzing the information needs and processes of a business. We will examine a variety of concepts and methodologies of Information Systems Analysis and Design. The Systems Development Life Cycle (SDLC) as well as the Object-Oriented Development Life Cycle (ODLC) will form the conceptual basis for development. Additionally, the student will be introduced to the properties of objects and classes, the Unified Modeling Language (UML), and visual modeling.
Upon the successful completion of this course, a student should:
· Demonstrate an understanding of the Systems Development Life Cycle (SDLC).
· Be able to apply systems analysis concepts, methods, and techniques to the analysis of real-world business problems.
Text:
|
|
Systems
Analysis & Design Methods (sixth edition) McGraw Hill – Irwin, 2004 0-07-247417-3 |
There are numerous resources including online magazines devoted to computer technology and related issues. An extensive set of hypertext links is available on my web site at the following URL http://dr.grenier.home.mchsi.com/resources.htm.
Software:
We will be using the following software:
Software of your choice to draw data models (Use Case Diagrams, etc.). If you do not have access to such software, I would suggest downloading Smart Draw from the Internet http://www.smartdraw.com
Internet email will be used extensively for communication and collaboration. Be sure to check your email regularly each week. Students may submit questions and suggestions via email. I will email answers and responses individually or to the class as appropriate. I will also accept assignments as email attachments of Word, Excel, or PowerPoint files. If you do not have an ISP (Internet Service Provider), the University provides all students with accounts.
The Web will be used to access the current course syllabus, other pertinent materials, and for research. The author maintains a web site for the text.
Learning Methods:
I believe nothing is more valuable than time! Although everybody has the same amount, nobody seems to have enough. Therefore, we must use it wisely and well. You have made a decision to attend this class to learn about Systems Analysis. I respect your decision and I will strive diligently to help you achieve this goal and not waste a moment of your time, but I need your cooperation. Help me by doing your part. Be on time to class and be ready to learn as much as you can in these few hours.
We will be using a blend of theory, class discussions, case studies, and in-class exercises. Class time will be spent in lecture and discussing system development concepts. Despite my intentions to provide a clear understanding of these issues in class, real learning will take place when you work through the required and optional assignments. Even though most assignments allow for group work, make sure that you understand how to do all aspects of each assignment. Avoid splitting up work in a way that gives you no opportunity to master the concepts. Since you can be examined on all material, you may not do well unless you follow this advice.
Participation in class discussion is of paramount importance! Be prepared by completing the assigned readings and exercises. I offer you the following suggestions for attaining the maximum benefit from the readings. Each chapter in the text begins with Objectives, an Introduction and concludes with a Summary and a list of Key Terms. Read the learning objectives, introduction, and summary first, and then read the chapter. This practice will make the chapter more understandable on the first reading. When you are done with the chapter, review the key terms list. If any item is not fully understood, look it up in the glossary at the end of the text.
Grading:
|
Assignment |
Weight |
|
Class/group participation |
10% |
|
Exercises/quizzes |
10% |
|
Midterm exam |
40% |
|
Final exam |
40% |
Administrative Considerations:
Assignments turned in, or received by email, after the beginning of class on the day in which they are due are subject to a 10% penalty. Since assignments can be submitted by email, absence from class is not a good reason for late assignments. Assignments will not be accepted if they are more than one week late. Exams must be taken when scheduled unless other arrangements are made beforehand.
Group vs. Independent
Work:
Exercises are to be done individually unless specified otherwise. Although giving and receiving some help from other students is OK, avoid go so far as to essentially do someone's assignment for them. Unless you actually do most of the work yourself, you will run into difficulty on exams.
Exercises:
|
Meeting |
Topic |
Deliverables |
|
|
1 |
Introduction |
|
|
|
2 |
|
|
2, 3 |
|
3 |
Information Systems Development |
|
3, 4 |
|
|
NO CLASS |
|
|
|
4 |
Systems Analysis |
|
5, 6 |
|
5 |
Use Case Modeling |
|
7 |
|
6 |
Data Modeling & Analysis |
|
|
|
3/8 |
NO CLASS |
|
|
|
7 |
Midterm
Examination |
|
|
|
8 |
Process Modeling |
|
9, 10 |
|
9 |
Object-Oriented Analysis and Design using the UML |
|
11, 14 |
|
10 |
Output Design and Prototyping |
|
15, 16, 17 |
|
4/12 |
NO CLASS |
|
|
|
11 |
Systems Construction and Implementation |
|
19, 20 |
|
12 |
FINAL |
|
|
Booch, G. (1994). Object-oriented analysis and design with applications. (Second ed.). Santa Clara, CA: Addison Wesley Longman, Inc.
Brown, D. (1997). An introduction to object-oriented analysis: Objects in plain English. (First ed.). New York, NY: John Wiley & Sons, Inc.
Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., & Stal, M. (1996). Pattern-oriented software architecture: A system of patterns. (Vol. 1996). New York: John Wiley & Sons.
Coad, P., & Yourdon, E. (1991). Object-oriented analysis. (Second ed.). Englewood Cliffs, NJ: Yourdon Press.
Coplien, J. O., & Schmidt, D. C. (Eds.). (1995). Pattern languages of program design. Reading, MA: Addison-Wesley Publishing Company.
Eriksson, H. & Penker, M. (1998). UML toolkit. New York: John Wiley
& Sons.
(Note: this
book includes a CDROM with trial versions of Rational Rose 4.0 and Java source
code for models in the case study).
Fowler, M. (1997). Analysis patterns: Reusable object models. Reading, MA: Addison Wesley Longman, Inc.
Fowler, M., & Scott, K. (1997). UML distilled: Applying the standard object modeling language. Reading, MA: Addison Wesley Longman, Inc.
Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1998 (Book 1995)). Design patterns CD: Elements of reusable object-oriented software: Addison Wesley Longman, Inc.
Jacobson, I., Christerson, M., Jonsson, P., & Overgaard, G. (1992). Object-oriented software engineering: A use case driven approach. Workingham, England: ACM Press, Addison-Wesley Publishing Company.
Larman, C. (1997). Applying UML and patterns : An introduction to object-oriented analysis and design: Prentice Hall Press.
Muller, P.-A. (1997). Instant UML. (Vol. 343). Paris, France: Wrox Press Ltd.
Quatrani, T. (1998). Visual modeling with Rational Rose and UML. Reading, MA: Addison Wesley Longman, Inc.
Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., & Lorensen, W. (1991). Object-oriented modeling and design. Englewood Cliffs, NJ: P T R Prentice Hall.
Schneider, G., & Winters, J. P. (1998). Applying use cases: A practical guide. Reading, MA: Addison Wesley Longman, Inc.
Shlaer, S., & Mellor, S. J. (1992). Object lifecycles: Modeling the world in states. Englewood Cliffs, NJ: P T R Prentice Hall.
Umar, A. (1997). Object-oriented client/server internet environments. Upper Saddle River, NJ: Prentice Hall Press.
Whitten, J. L., & Bentley, L. D. (1997). Systems analysis and design methods. (Fourth ed.). Boston, MA: Irwin McGraw Hill.
Wirfs-Brock, R., Wilkerson, B., & Wiener, L. (1990). Designing object-oriented software. Englewood Cliffs, NJ: P T R Prentice Hall.