IS7892 -- Current Topics in SAD
- •Alexander, C., The Timeless Way of Building, New York: The Oxford Press, 1979.
- •Brooks, F.P., The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition, Addison-Wesley, 1995.
- •Norman, Donald A., The Design of Everyday Things, New York: Doubleday, 1988.
Articles: see readings.
Prerequisites: Only students officially admitted to the Ph.D. Program in Information Systems are allowed to register for class. In addition, students must have completed IS 5800 and IS 6840.
Course Description: The official description of the class is:
The unofficial and working description of the class is: a seminar in the topics of systems analysis and design. Hence, it has become known as “the technical seminar.”
- Advanced topics of current interest in management information systems.
- Content to be determined each time the course is offered. May be repeated for credit.
Semester Goals: This class addresses a series of questions: Why is there not more IS research directed toward systems analysis and design? Clearly these topics are critical for effective business applications in the 21st Century. However, most of the development and drive comes from industry. Why? If the development and drive come from industry, is this a good thing or a bad thing? What kinds of research agendas might be developed to address these questions? How might we apply the theories addressed in your other seminars to address questions of systems analysis and design?.
Exams: There will be a midterm and a final exam, and both will be take home exams and due on the date stated below.
- Midterm exam: March 4
- Final exam: May 13
Grading Policy: The following proportions will be used for grading.
- Website - 5%
- Class Participation - 10%
- Discussion Leading - 10%
- Paper - 35%
- Midterm - 20%
- Final - 20%
Course Format: Classes will often be student led discussion of research projects. Papers will be assigned to a student who will review the research. All students will be expected to contribute to the discussion by identifying the strengths, weaknesses and extensions of the research. Since this is a class of questions, students will be asked not only to discuss the assigned readings, but to bring to the discussion readings from other classes or outside readings. Students should be aware of
topics to include when reviewing research.
Research Proposals: Each student will create a proposal for research on some topic of systems analysis and design, database or decision support systems. You should think of these proposals as a first step in creating a publishable journal article. As such, the proposals should answer the same questions that area addressed when reviewing research (see above). Select a topic that is interesting to you. Perform a preliminary literature search to ensure that your idea has not already been completed and that you have a fresh approach. You may want to consult with the instructor about topics and the literature.
Submit a preliminary proposal by March 11. Not only should you turn in a paper copy to me on that date, you should also provide either an electronic copy or paper copy to your classmates. On March 18, each person will present his or her proposal to the class for discussion. Please plan for no more than 15 minutes for your presentation. Other students should have read the proposals and be prepared for discussion.
Academic Honesty: According to the University Standard of Conduct, Section 6.0101,
The Board of Curators recognizes that academic honesty is essential for the intellectual life of the University. Faculty members have a special obligation to expect high standards of academic honesty in all student work.
Students have a special obligation to adhere to such standards.
Furthermore, note that the University’s Collected Rules 200.010 B.1 REQUIRE faculty to notify Academic Affairs of suspected cases of dishonesty. It states, “In all cases of academic dishonesty, the instructor shall make an academic judgment about the student’s grade on that work and in that course. The instructor shall report the alleged academic dishonesty to the Primary Administrative Officer.”
For the purposes of this class, cheating will include: plagiarism (using the writings of another without proper citation), copying of another (either current or past student's work), working with another on individually assigned work or exams, unauthorized marking on a graded paper or exam, or in any other way presenting as one's own work that which is not entirely one's own work. It is unacceptable to seek the help of another (whether in the class or not) for help on an exam; this is considered academic dishonesty.
Any student who is caught cheating on any assignment or exam will receive a grade of zero (0) for that assignment or exam. Further, a recommendation will be made to the appropriate university officials that additional disciplinary action be taken.
Tutorials on Plagiarism exist at the following sites:
Rights and Responsibilities of Computer Users
As part of its educational and research missions, the University of Missouri-St. Louis strives to provide quality computing facilities. These include large and small systems, communication networks, and personal computers, as well as associated software, files and data. Although computers affect how individuals communicate and interact with each other, computers do not change underlying societal values and established individual rights with respect to personal privacy and ownership of property. Computing facilities are recognized as community resources. Each computer user, therefore, is expected to act responsibly so as not to violate the rights of others. Access to computing resources is contingent upon prudent and responsible use. Inappropriate use of computing services and facilities will not be tolerated and may result in loss of computing privileges. In addition, disciplinary and/or legal action will be pursued for violation of these codes and statutes through appropriate University procedures.|
See http://www.umsl.edu/technology/policy/acceptable.html for more details.