IS305 Analysis & Design
Fall 2007
Meetings
Mondays 4:00-6:50 PM; ACB 205
Instructor
Name: Terry Ryan; Office: ACB 220; Office Hours: Mondays 3:00-3:50 PM;
Phone: (909) 607-9591; Office Fax: (909) 621-8564; E-Mail: terry.ryan@cgu.edu
Course Overview
In this
course, you will learn about object-oriented analysis and design. In addition, you will acquire some hands-on
skills through an analysis and design project.
This course prepares you for other courses in the IS curriculum, as well
as investigation of advanced topics.
To get
the most out of this course, you should know how to program in an
object-oriented language. If you do not,
you should read the optional assignments for the first 3 weeks of the course,
which cover the essentials of Java programming.
COURSE
OBJECTIVES
“This
course provides an understanding and application of system analysis and design
processes. Students evaluate and choose
appropriate system development methodologies and design a system. Students learn the importance of effective
communication and integration with users and user systems. The course emphasizes interpersonal skill
development with clients, users, team members, and others associated with
development, operation, and maintenance of systems.”[1]
Course Requirements and Grading
|
Class Participation |
150 |
|
Exercises |
150 |
|
Tests |
200 |
|
Project |
500 |
|
|
1000 |
Required TextBOOK:
McLaughlin, B.D., Pollice, G., and West, D. Head First Object-Oriented Analysis & Design, O’Reilly, 2007.
ISBN 0-596-00867-8
(Shown in schedule below as A&D.)
OPTIONAL TEXTBOOK:
Sierra, K., and Bates, B. Head First Java, 2nd Edition, O’Reilly, 2005.
ISBN 0-596-00920-8
(Shown in schedule below as Java.)
REQUIRED READINGS:
1) “Who killed the virtual case file?” http://www.spectrum.ieee.org/sep05/1455
2) “Classic mistakes enumerated” http://stevemcconnell.com/rdmistak.htm
3) “Where now for development methodologies?” Avison, D.E., and Fitzgerald, G., Communications of the ACM, 46(1), January 2003, pp. 78-82
Participation
You should read the assignments before class. Participate in class. Show up on time. Be respectful of your classmates and instructor.
EXERCISES
You must complete exercises as assigned by the instructor. These are due at the beginning of class on the date specified in the assignment. Some assignments involve preparation of written deliverables; some require in-class presentation. Specifics will be explained by the instructor when the assignment is made.
tests
Tests will consist of questions and problems. Questions may require essay answers. Problems may require the production of diagrams or similar output; proper use of modeling techniques will be expected. Tests may be split into closed book and open-book sections at the instructor’s discretion.
Project
You must
be part of a team of students who complete an analysis and design project. The project must be done using the techniques
covered in the texts, readings, and lectures.
The goal of the project is to provide analysis and design deliverables,
along with a demo of the proposed system.
Any application may be chosen, although the instructor must approve the
choice.
Deliverables for the project are due on the days specified in the schedule. All deliverables should be word-processed or CASE-tool-processed and stapled, with an appropriate cover sheet, which should include a title, the date, and the names of team members.
1. Teams must propose a project by submitting a 1-page explanation of it on the day noted in the schedule as ‘Proposal presentation’. Additionally, teams must explain to the class what they intend to do as a project. This should be brief (approx. 3 minutes) and need not be detailed. If there is a client for the project, agreement must be reached with the client about what will be done. Teams must convey clearly to their clients whether the project will involve implementation. Such implementation may be necessary to convince the client to participate, but it is beyond the requirements of the course. If you promise the client you will build a working solution, it is essential that you follow through. Failure to do so would be damaging to CGU’s reputation.
2. Teams must submit the results of their planning efforts in written form and as a short presentation (approx. 30 minutes) on the day noted in the schedule as ‘Planning presentation’. This must include a feasibility analysis, including reasonable initial estimates for schedule, staffing, and budget. It should also explain other project management factors, including how the project would be evaluated, the standards to be followed, and the risks to be handled.
3. Teams must submit the results of their analysis efforts in written form and as a short presentation (approx. 30 minutes) on the day noted in the schedule as ‘Analysis presentation’. These must include detailed requirements for the system, as well as any models needed. If one were following the RUP approach, these would include functional, structural, and behavioral models, depicted in proper UML.
4. Teams must present the results of their design efforts (and submit deliverables in written form) on the day noted in the schedule as ‘Design presentation & demo’. If one were following the RUP approach, these would include: factored models, system architecture design, infrastructure design, interface design, data storage design, program design, test plan, implementation plan, change management plan, and training plan.
5. As part of their design presentation (approx. 30 minutes), teams must present a demo of their system. This should be some kind of working model of the system. At a minimum, this should be something like an html prototype to illustrate the functionality of the system that could be built. More sophisticated demos, up to and including working systems are encouraged and will earn ‘extra credit’. Teams should provide the instructor with a digital copy of the demo, perhaps burned to a CD, along with instructions for how to install and run it, including any required software.
Every team should be ready to present on the scheduled days. All team members should contribute equally. Presentations should explain clearly what was done and why, justifying project decisions in terms that would be understandable to clients. Grades on the project will reflect each team’s success in applying the concepts and techniques introduced in the class.
TEAM ASSIGNMENT RULES
Students should form their own teams. Each team must have 2 or 3 members. No individual submissions are allowed. Once teams are formed, their membership may not be changed. Each team member will receive the score assigned to the team. It is expected that team members will share the work involved equally and will work to resolve any issues related to unequal participation. The instructor reserves the right to remove non-participative team members from teams and assign them grades indicative of non-participation.
PLAGIARISM WARNING
Plagiarism will not be tolerated. The minimum penalty for plagiarism is a zero
for the assignment; more severe penalties can include failure in the course and
expulsion from the program. To avoid
plagiarism, do not take credit for the work of others. Obtain permission from the holders of rights
to any intellectual property you use, including text, code, images, etc. Provide a full reference for each work
used. See http://www.cgu.edu/pages/903.asp
for additional information.
|
SCHEDULE |
|
|
|
Sep 10 |
Req. Reading 1 |
Introduction to Course |
|
Sep 17 |
Req. Reading 2 |
Exercise 1 |
|
Sep 24 |
Req. Reading 3 |
Exercise 2 |
|
Oct 1 |
A&D 1 |
Exercise 3 |
|
Oct 8 |
A&D 2 |
Proposal presentation |
|
Oct 15 |
A&D 3 |
Exercise 4 |
|
Oct 22 |
Midterm Exam |
Exam |
|
Oct 29 |
A&D 4 |
Planning presentation |
|
Nov 5 |
A&D 5 |
Review of exam |
|
Nov 12 |
A&D 6 |
Exercise 5 |
|
Nov 19 |
A&D 7 |
Analysis presentation |
|
Nov 26 |
A&D 8 |
Exercise 6 |
|
Dec 3 |
A&D 9 |
Design presentation & demo |
|
Dec 17 |
Final Exam |
Exam |