Instructor: Warren Beatty
Office: Building 76, Room 115
Telephone:474-2353
Office hours: Weekly, Monday through Thursday, 11:00 AM until 1:30 PM
Other hours by appointment, plus availability 24 hours by e-mail: wbeatty@uwf.edu
Text: Essentials of Systems Analysis and Design, by Valacich, George, and Hoffer, Prentice-Hall, ISBN 0-13-018373-3. Other selected readings provided by the instructor. We will make extensive use of the resources available via the Internet throughout the semester.
There will be a version of the text available in the bookstore that has the CASE software tool, Visible Analyst (ver 7.1), included as a package. Those of you with your own computer might wish to consider buying the package deal. It will also be available on the computers in the MIS computer lab (only). You will probably want to wait until we get into the formal system development before considering this text.
Prerequisite Courses: ISM 3011, E-Business System Fundamentals, and ISM 3235, Business Development Environments. It is mandatory that you have a good foundation in E-Business concepts and in Visual Basic system design and program development.
COURSE OBJECTIVES:
The primary objective is to introduce students to the concepts and tools that support and define the Information Systems Design and Development process. Specific objectives include:
This courses teaches the fundamentals of designing information systems. The course combines theory taught by class room lecture with the application of the theory through projects. The prerequisites for this course are courses Management Info Systems (ISM 3011 or the equivalent), and ISM 3235 Business Development Environments. With any less background, a student will be overwhelmed by the terminology and technology and would not be a productive group member. In other words, I assume that you have seen a computer and know what to do with it. Don't even ask if you haven't had these prerequisite courses.
GRADING METHOD: Course grades are based on three elements of the course: exam grades, group participation in case development and presentation, and homework assignments. Most of the homework assignments are group projects. Yes, that's correct: another class with groups. Your homework grade will be heavily influenced by your group members. Therefore, we will take the first class meeting to perform class member introductions. Following the introductions, we will divide into groups and start on the first group project assignment. You should plan your semester schedule to allow PLENTY of time for group work.
Why, you ask, do we have to work in groups? Groups never work, and someone always shirks his/her duties. Well, in the "real world" information systems are designed by groups of people. That's the way it is. You will learn to be a much more effective and efficient IS designer if you can learn how to work within groups. Better to learn how to manage group members here than to have to learn how in the middle of your first new system design on the job!
Your final grade will be composed of the following percentages:
Course Grading Scale
EXAMS: There will be two (2) exams; either in-class and closed book, or possibly take-home, or possibly a combination of both. Questions on the exams will be fill-in-the-blank with a "word bank," multiple choice, short answer essay, or problem/project. The second exam will be comprehensive in nature, but will emphasize the material since the first exam. The second exam is weighted more than the first exam. If you make less than a 70 average on the two exams, you are NOT eligible for the 25% group grade.
The first exam is scheduled for 29 May, and the second exam is scheduled for 3 July.
GROUPS: Each student in the class will be a member of a design group. The group members will collectively work on each of the group assignments, and each student in the group will receive the same grade as the other members in the group. Each group will design its own peer evaluation form and write its own group charter specifying the rules of operation for that group.
Peer evaluations for the group will occur twice during the semester: once about the middle of the term and once at the end of the term. For more details on the peer evaluation, charter, or other details concerning group operation see the section on "Group Organization".
GROUP SYSTEM DEVELOPMENT PROJECT: Each design group will complete a series of cumulative group projects. These projects are designed around the material in the class textbook. The group projects will include performing a DETAILED systems analysis, design, and development of a working solution for the assigned systems project. The series of activities will follow the activities covered in the course materials. I will assign the "subject" of the system.
At the end of the term, each group will perform a formal project presentation which will include an in class demonstration of their system. This is to be a formal presentation presented as if it were to a real user group, complete with all appropriate formal visual aids, handouts, etc. All members of the group participate equally and receive one grade. This presentation and successful demonstration will count as 10% of the groups' graded projects. It is the responsibility of the group to coordinate any technology requirements to support the presentation process.
The group's final product that is submitted to me for evaluation will consist of:
GROUP RESEARCH PROJECT: Each group will research, develop, and write a research project. This project will investigate some aspect of systems analysis and design chosen by the group. Each group should select a topic, discuss the topic with me (either in person or via e-mail), and then develop the project. Only one team per topic. First team to contact me with topic selection gets to do that topic. The project will be developed using Microsoft Word and submitted to me via e-mail - no printed version will be accepted.
The Group Grade will consists of the following parts: 25% group research paper; 50% group systems project; 25% group systems project demonstration/presentation.
Tentative Class Schedule
The first seven weeks will be conducted via the Internet
First Exam on 29 May at 1:30 PM in SAIL Computer Lab, builing 79
The first exam will be on 29 May via the Internet. The second exam will be on 3 July in the classroom. The first exam will be conducted in the SAIL Computer Lab, building 79, at 1:30 PM CDT. This link will take you to more information about the First Exam, including a Word document exam example that you can download for practice.
| Week | Date | Chapters | Topics Introduced | Events, Instructions |
|---|---|---|---|---|
| 1 | 6, 8 May | 1 | Introduction to Systems Analysis and Design, Chapter 1: The Systems Development Environment, Chapter 2: Managing the Information Systems Project | Send your e-mail address if different from "students.uwf.edu" address |
| 2 | 13, 15 May | 3, 4 | Chapter 3: Systems Planning and Selection, Chapter 4: Determining System Requirements | Be certain that you can download the exam answer sheet - see exam information above |
| 3 | 20, 22 May | 5, 6 | Chapter 5: Structuring System Requirements: Process Modeling, Chapter 6: Structuring System Requirements: Conceptual Data Modeling | Exam review using Prometheus Chat Room begins at 1:30 PM CDT. |
| 4 | 27, 29 May | 1 - 6 | First Exam at 1:30 PM CDT on 29 May in SAIL Computer Lab, Building 79 | download answer sheet document BEFORE exam starts |
| 5 | 3, 5 June | 7 | Chapter 7: Selecting the Best Alternative Design Strategy | Begin informal group formation (maximum of five members per group) |
| 6 | 10, 12 June | 8 | Chapter 8: Designing the Human Interface | If groups formed, select group leaders, e-mail group names and members |
| 7 | 17, 19 June | 9 | Chapter 9: Designing Databases | None |
| First Class Meeting on Monday, 24 June, 1:30 PM CDT, Building 74, room 107 | ||||
| 8 | 24, 26 June | 10 | Chapter 10: Systems Implementation and Operation | Formal group formation (if necessary), introduce system development project |
| 9 | 1, 3 July | 7 - 10 | Second Exam at 1:30 PM CDT on 3 July in classroom | Exam held in regular classroom |
| 10 | 8, 10 July | all | Group Project System Development | Group Charter and Evaluation Form submitted NLT 10 July |
| 11 | 15, 17 July | all | Group Project System Development | First Peer Evaluations Due 17 July |
| 12 | 22, 24 July | all | Group Project System Development | Group Research Project Due 24 July |
| 13 | 29,31 July | all | Group Project System Presentations | Second Peer Evaluations Due 29 or 31 July, All Group members must participate in presentation |
The first milestone for each group is to select a group name and develop a group contract to guide group operations. Each group will design, develop, and produce a group contract that is a formal, graded document created by the entire group. The contract should state the rules of operation for the group, including the standards for participation (attendance, cooperation, timeliness, professionalism, etc.). Another item in the contract is two (2) mutually agreeable weekly meeting times of at least 1 ½ hours each. You will find it helpful if one of these group meeting periods is on a day other than class meeting days. Setting group meetings only on class days prevents you from having time to think about assignments before starting to work on them. Job schedules, other class projects, extra-curricular activities, etc. are not valid excuses for missing group meetings or not completing group assignments on time. Students are expected to keep this time free for group meetings. Even though we study the functions of and work with technology, it cannot be used to totally replace face-to-face meetings. Each group is expected to regularly meet together as a group.
Each group should email me their group name, group roster, and group Charter before class on Wednesday, 10 July at the latest. This means it should be edited, neatly printed, and SIGNED by each group member BEFORE class starts. The group contract will be the basis for operating the group during the semester. I estimate that an adequate group contract would be a minimum of two typed pages in length, PLUS the group peer evaluation form.
Each group will need a group leader who will coordinate activities and through whom I can communicate with the group. The contract will include each member's day and evening phone numbers so that group members can maintain contact with each other, and so I can contact the group if necessary. It is mandatory that each team member get a student e-mail account for access to campus e-mail. Put the e-mail address on the contract so that I may contact you. Group members should check their e-mail account often during the week for messages. The projects for this class require that the students FREQUENTLY use special computer software reserved for this class. It is not likely that anyone will have access to this software elsewhere and the entire class will be sharing this scarce and limited resource. Therefore, group members need to be considerate of other groups in adhering to usage schedules and flexible as to hours of usage. NOTE: Not everyone will be able to complete their project the night before it is due. Some of you will have to use forward scheduling and properly budget your time on the computer system.
The contract will also include a group peer evaluation form. This is the form the group will use to evaluate team member participation. (NOTE: the evaluation forms for the groups will be different depending upon group priorities.) At a minimum the group peer evaluation form will include the following items: attendance, preparation, cooperation/collegiality, attitude, level of participation, quantity and quality of work, initiative, demonstrated knowledge of course material, and overall contribution. The peer evaluation form will provide: (1) a total of the rating for the evaluee (out of a possible 100%); (2) and the names of both persons. As many other traits may be evaluated as the group chooses. Think of the personal traits necessary for a successful working relationship when you depend on that person's performance for your own success. Be innovative and creative. The library is a good source for additional references on this subject.
Each group will rate its members performance twice during the semester. One evaluation will be about mid-term and one at the end of the semester. Expected, normal performance will be a grade of 85. Any grade above 85 or below 60 must be documented with the details of the specific instances which warrant the evaluation given. Only EXCEPTIONAL performance should rate a grade above this. Performance lower than 60 percent will result in NEGATIVE peer evaluation points for the participant. (See scale). Your ability to participate and contribute in all aspects of the group's work is extremely important to your success in this course. Overall peer evaluation points will account for up to 10 percent of each student's final grade.
Each student should keep a journal of activities in order to refresh their memory and to document individual performance. I may ask for these journals periodically during the semester to check on group activities and participation.
Peer evaluation 0 20 40 60 80 85 100 Percent +--------------------------------------------------+ -10 0 5 8 9 10 Points Peer Evaluation Point Conversion ScaleThe group contract will demand considerable concessions and compromises in order to arrive at an agreeable consensus. The entire typed and signed group contract is due at the beginning of the class meeting on 10 July. By signing the contract each group member agrees to be bound to the rules set forth in the contract for the duration of the term.
Another detail of the group contract is the circumstances, procedures, and justification for "firing" a member from the group. In the unlikely event that a group finds it necessary to "fire" a group member, that group member will NO LONGER BE ELIGIBLE FOR ANY FURTHER PORTION OF THE GROUP'S GRADE. A student that is fired from a group must fulfill all the requirements for the project(s), but individually (or in a group with other "fired" team members). The same requirements apply to any student who quits a group. Anyone who is fired from a team, or who quits a team forfeits ALL peer evaluation points.
Each group assignment, beginning with the contract, will have a typed cover sheet. This cover sheet will include the name of the group, the name of the assignment, the due date of the assignment, the names of the group members participating in the assignment, and the percentage each of these group members contributed to the assignment.
Sample scales for peer evaluation forms. You are NOT required to use any part of this....in fact you probably shouldn't use it other than for ideas.
I. Attendance at group meetings +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 never usually always there there there II. Preparation for group meetings +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 never usually always worked ahead worked ahead worked ahead III. Cooperation with others in the group +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 rude, obnoxious cooperative very uncooperative cooperative IV. Participation in group discussions and work assignments. +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 didn't usually had always had contribute contributions significant contributions V. Quality of work +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 always had to some rework, always good be redone usually acceptable work, exemplary VI. Quantity of work +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 never did did his/her did most of any work fair share work on project VII. Initiative +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 never made often made led group, had suggestions suggestions great ideas VIII. Group cohesiveness +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 extremely pleasant, very cooperative, dysfunctional cooperative group leader IX. Demonstrated knowledge of course content and subject matter. +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 never learned usually knew always knew any course info what to do what to do X. Overall contribution to the group's efforts +--------------------------------------------------------------------+ 0 10 20 30 40 50 60 70 80 85 90 100 would have been did what carried the easier without was expected group on his/her him/her shoulders
One final note about the course schedule: I have tried to "front end load" the schedule with respect to covering the text material and taking exams. I did this so you can get from the text a basic understanding of the System Analysis and Design process. You will USE this process to guide your group project efforts. I want you to have as much time as possible to work on your projects as possible after learning about the process.
Course Policies: