Faculty Contact Information:
Phone: 49 (0) 6202 / 5 77 82 14
Snail-Mail:
UMUC - Unit 29216, APO AE 09102
Home Address:
Werderstr. 8
68723 Oftersheim
|
|
Consultation:
In classroom, half an hour before the start of class and during the lunch break. Other times by appointment.
As this is a "technologically enhanced" class, we will communicate via WebTycho between the face-to-face sessions.
Face-to-face meetings are scheduled, from 0900-1600, at Kapaun on these Saturdays:
30 Oct, 4 Dec, 29 Jan, 12 Mar.
|
|
Required Texts and Readings:
|
There is no text for this course.
|
|
Supplementary Readings:
The standard for papers in the graduate program is the APA style. All participants in this course and all graduate INSS, MGMT, PUAD, and ECON courses should have a copy of the style guide:
American Psychological Association. (2001). Publication Manual of the American Psychological Association, 5th Edition. Washington DC: Author.
All graduate students should be prepared to utilize the UMUC online library at http://www.umuc.edu/library/. The library contains a large number of full text academic journals that are free of charge and immediately available. The library homepage also contains a number of links related to improving students' research and writing skills.
|
|
Recommended Journals:
Publications of the various professional societies (such as ACM -- the Association for Computing Machinery, the IEEE Computing Society, and the various management professional societies) are strongly recommended. In addition, there are many trade journals (such as eWEEK) that MIS professionals should become familiar with, many of these being published both weekly and on-line.
|
|
Course Description:
|
3 semester hours credit. Prerequisites: INSS 540, INSS 550, INSS 620, and advancement to candidacy in the M.S. program. Provides the student with practical experience in analyzing, designing, implementing, and evaluating an information system in educational, industrial, governmental, or military environments. The student completes a systems development project in which all of the systems development cycles can be experienced. Students can be placed in practicum sites independently or in a team to acquire practical experience. This course is graded Pass (P) or Fail (F) and is normally conducted over two terms.
|
|
Course Goals:
|
1. Critical Thinking: Students should improve their ability to analyze information and develop appropriate summarizing and reporting techniques.
2. Writing Skills: Students should improve writing skills through development of the Project Proposal and project documentation.
3. Oral Presentation Skills: Students should improve their presentation skills through oral presentations and structured walkthroughs of the project in process.
4. Computer Skills: Students are expected to improve their computer skills implementing a systems analysis and design project. In addition, the conduct of the course will make extensive use of the webboard.
|
|
Course Objectives:
|
1. Directly apply the SDLC (systems development life cycle) methodology
2. Participate proactively in a structured walk-through of code
3. Evaluate critically (on a managerial level) a systems analysis, design, and implementation proposal
4. Identify, describe and model procedures for information systems projects
5. Demonstrate data reporting and analysis techniques
6. Demonstrate technical writing skills
7. Demonstrate oral reporting skills appropriate for a managerial environment
|
|
Grading Information:
A grade of Pass (P) will be achieved with a minimum of 80%
The grade F(a) is used to designate academic failure. F(n) is used to designate failure for non-completion. Grades of Incomplete or Withdrawal are governed by UMUC-Europe policies. For further details, please refer to the UMUC-Europe Graduate Catalog, available in your local Education Center or online at http://www.ed.umuc.edu/general_info/publications/catalogs.
|
|
Course Requirements:
The course is divided into four grading periods (see Course Schedule), each of which includes a face-to-face class meeting.
Each of the four periods contributes 25% of the total course grade, and is based on evaluation by the instructor of
(a) 15% quality, content, and timeliness of written deliverables and in-class presentation (see Course Schedule), and
(b) 10% submissions and participation via WebTycho during the grading period.
|
|
Description of Course Requirements:
Each participant in the course should have a formal presentation of the project proposal perpared for presentation at the first class.
Since the goal of the project is completion of the project, the bulk of the formal online meeting times will be devoted to achieving this goal. This will be accomplished via formal status reports on the projects, beginning with the Project Proposal which each student is expected to present during the first weeek (see Course Schedule).
The group will evaluate the strength of each proposal and will recommend appropriate modifications (evaluating the strength of the proposal as well as recommending modifications to the scope.)
If the project is related to the student's job, the proposal must include explanation of how the proposed project is above-and-beyond the normal work assignment -- it is not acceptable to receive academic credit for INSS 680 for doing something you're paid to do anyway!
Making major enhancements to a project begun in a previous course can be an acceptable project for this course. Students wishing to do so must clearly demonstrate in the initial project proposal what work has been accomplished in the previous course, and what is proposed to be done for INSS 680 credit. Submission of a previous course's project without substantial additional work is not acceptable.
The Project Proposal Form should have been drafted before the first class. This will be the basis for the presentation. A notebook with Power Point as well as a projection device will be available for the presentation. The proposal and presentation must include a proposed timeline (which is expected to be modified throughout the course) for the phases of the project.
Note that while group projects are possible, they are not encouraged, and group projects should not involve more than two participants. If it is a team project, the proposal and timeline should demonstrate clearly who is responsible for what, and that each student will be doing as much work throughout the course as he/she would have doing a project alone.
This not a lecture type of course. The instructor's responsibility will be to guide the student toward successful completion of the project. Students have responsibility to provide constructive feedback regarding the projects of others.
Attendance
Students are expected to be present, and ready to give PowerPoint presentations as noted in the Course Schedule, for the four scheduled face-to-face meetings. If you cannot be present, please notify the instructor as soon as possible (preferably in advance), and post your presentation and other deliverables to WebTycho before the day of the class meetings, so that you may receive maximum feedback from the rest of the class.
If there is a week when you cannot participate via WebTycho, please notify the instructor when and why you cannot.
Project Proposal for Information Systems Practicum -- INSS 680
Project Proposals are due to the instructor in draft form no later than the first class meeting. You are also expected to prepare a presentation of your proposal to be given during the first class session. Project Proposals are due in finalized form during the first week of the class via posting to WebTycho, incorporating feedback given by the class as appropriate.
The project proposal form is available at:
http://faculty.ed.umuc.edu/~sdean/680Proposal.doc
The form is designed so that student, faculty, and organizations can present a Project Proposal that meets the academic integrity of Bowie State University and UMUC - Europe.
Specifically, the proposal must meet the following guidelines:
This course provides the student with practical experience in analyzing, designing, implementing and evaluating an information system in industrial, government, military, or other organizational environments. The student is assigned a systems development project in which all of the systems development cycles can be experienced. The proposal is to be written with sufficient explanation and detail that the project could be assigned to another student, although it is unlikely that will be the case.
The following guidelines must be used when completing the Project Proposal: Consider the length of the course - two seven week terms. Ensure that the project scope does not exceed this very real constraint.
The course description states that the student must "experience" the system-development cycles. This does not require that the student "do" all the steps in the cycle. For example, a student or team could read/study previously created analysis and design documents, "do" the implementation and also prepare an evaluation plan to be completed by other students or teams. Similarly, a student or team could "do" the analysis, "do" the design and develop frameworks for implementation and evaluation phases to be completed by other students or teams.
Please note that an INSS 680 Project is not just a "let's do one
paper" or "let's develop a database" project. It is expected that the student or team will do several tasks or phases in the systems development cycle. While installing a LAN is a neat thing to "do", it does not in and of itself come close to meeting the letter or the spirit of the requirements for INSS 680. One or more of the deliverables for a project may be (a) database(s), but that should occur as a result of the analysis and design, not as a starting goal.
The proposal requires a definitive presentation of the tangible results expected from the project. These tangible results are hereinafter referred to as "deliverables".
a. For example, the document(s) that will be created and the scope and detail that the documents must meet are deliverables, or an operational database with ten (10) input screens and six (6) standard reports are deliverables.
b. The deliverables must be presented in concrete terms that can be evaluated by a disinterested party.
c. The following are presented as examples and as the beginning of a list of possible deliverables that a project may require. Remember a successful project will normally consist of several deliverables of this kind.
i. A LAN User Manual.
ii. Analysis Documents that could include interviews, periodical research and other tasks associated with the analysis phase.
iii. A detailed Design Document
iv. A Programmer's/System Administrator's Maintenance Manual for an implemented database system.
v. A collection of web pages.
vi. Documented installation of a LAN with two (2) file servers, three (3) printers, and fifteen (15) fully functional workstations.
vii. Documented installation of a relational database system.
viii. The creation of a new functional module for an existing database.
ix. The analysis, design, implementation, and evaluation of a reliable Client-Server file transfer system.
Any project that "does" an implementation (a deliverable) must also include the development of an evaluation document (a deliverable) that may be used to evaluate the implemented system.
Organizations that wish to sponsor a student or a team in the INSS 680 Practicum should be prepared to meet some or all of the following requirements:
a. Allow adequate access to software, systems, documentation, and other resources to allow students or teams to complete the project during the term.
b. Sign a Release of Liability with the University of Maryland, Overseas Division.
c. Provide a specific Point of Contact (POC) for the development and implementation of the project. Additionally, the organization will perform a role in ensuring that the project remains on schedule. This will possibly include meeting with students during the first class so that organizations and students or teams can be matched up.
d. Organizations wishing to formally present their projects to students at the first class meeting to "drum up support/interest" are most welcome to do so. This is not a requirement, but an invitation, if you wish to sell your project. This must be arranged with the instructor in advance of the first class meeting.
|
|
Course Schedule:
Projected Course Schedule:
Pre-class 1
review the SDLC in the INSS 540 text, and explore potential projects;
complete a Project Proposal Form;
prepare a PowerPoint presentation of your project proposal, including timeline (which will be revised along the way!)
for completion of the phases of the SDLC.
Class 1 - meet in person Saturday, 30 October
Introduction to course, lecturer, and other class members;
The Planning/Survey Phase;
present your project proposal to the class, and give and receive
feedback regarding proposed projects.
via WebTycho week of 1 Nov:
Post the proposal and the PowerPoint presentation in WebTycho, to receive feedback from classmates;
Provide feedback to others via WebTycho.
Class 2 - via WebTycho week of 8 Nov
Analysis/Study Phase; Walkthroughs Review; User Definition Review
Post progress report, and any questions that you'd like to have
answered by others.
Review and comment on peers' Proposals; develop a walkthrough report
for use by other students in analyzing your work; review the
discussion on walkthroughs in INSS 540 text.
Class 3 - via WebTycho week of 15 Nov
Analysis/Study Phase and/or Definition Phase; Review of Budgeting and Scheduling;
Submit for review: 1) User requirements, 2) A detailed analysis of the users, including their tasks, experience level, and other demographics, 3) A rough budget and schedule estimate; Comment
on peers' walkthrough report form; may want to review the discussion on walkthroughs in INSS 540 text.
End of first grading period.
Class 4 - via WebTycho week of 22 Nov
Design Phase;
Post progress report, and any questions that you'd like to have
answered by others.
Comment on peers' project plans (1-3 above); Begin design work.
Class 5 - via WebTycho week of 29 Nov AND
meet in person Saturday, 4 Dec
Design Phase;
Submit to WebTycho and give PowerPoint presentation in class of
preliminary design for walkthrough and develop a preliminary evaluation plan;
Be an active participant in the walkthroughs.
Class 6 - via WebTycho week of 6 Dec
Design Phase;
Submit final design for walkthrough; Be an active participant in the
walkthroughs.
Class 7 - via WebTycho week of 13 Dec
Construction Phase;
Continue activities listed above and begin constructing the proposed project;
Post progress report, and any questions that you'd like to have answered by others.
End of second grading period.
Break 18 Dec – 16 Jan
Class 8 - via WebTycho week of 17 Jan
Construction Phase;
Provide either a status report or submit materials for walkthrough;
Be an active participant in the walkthroughs; continue work.
Class 9 - via WebTycho week of 24 Jan and meet in person Sat, 29 Jan
Construction Phase;
Post to WebTycho and give PowerPoint presentation of a status report and materials for walkthrough;
Be an active participant in the walkthroughs; continue work
Class 10 - via WebTycho week of 31 Jan
Construction Phase;
Provide either a status report or submit materials for walkthrough; Be an active participant in the walkthroughs; continue work.
Class 11 - via WebTycho week of 7 Feb
Construction Phase;
First Draft of the Deliverables Due, including Implementation Plan.
End of third grading period.
Class 12 -- via WebTycho week of 14 Feb
Delivery Phase;
Be an active participant in the walkthroughs on the deliverables; post progress report; continue work.
Class 13 - via WebTycho week of 21 Feb
Delivery Phase;
Support Plan and Final Evaluation Plan Due.
Class 14 - via WebTycho 28 Feb-13 Mar AND meet in person Saturday, 12 Mar
Evaluation Phase;
Final Project Due, including report on Lessons Learned and Actual vs. Budgeted schedule and resources.
Give in class and post to WebTycho your final PowerPoint presentation of the project. Demonstrate prototype, if applicable.
Final version of deliverables must be posted to Web no later than midnight, CET, Sunday, 13 Mar.
End of fourth grading period.
|
|
Academic Policies:
The University has a license agreement with Turnitin.com, a service that helps prevent plagiarism from internet resources. I may be using this service in this class by either requiring students to submit their papers electronically to Turnitin.com or by submitting questionable text on behalf of a student. If you or I submit part or all of your paper, it will be stored by Turnitin.com in their database throughout the term of the University's contract with Turnitin.com. If you object to this temporary storage of your paper, you must let me know no later than two weeks after the start of this class. Please Note: If you object to the storage of your paper on Turnitin.com, I may utilize other services to check your work for plagiarism
The official university policy on Plagiarism and Academic Dishonesty can be found at http://www.umuc.edu/policy/aa15025.shtml. Section I.C. states: "Faculty may determine if the resubmission of course work from previous classes (whether or not taken at UMUC), partially or in its entirety, is acceptable when assigning a grade on that piece of course work. Faculty must provide this information in their written syllabi. If the resubmission of course work is deemed to be unacceptable, a charge may not be brought under this Policy and will be handled as indicated in the written syllabi."
Please refer to Description of Course Requirements for specific information on how resubmissions will be treated in this course and to the UMUC-Europe Graduate Catalog for information on the following:
Academic Integrity
Course Load
Exception to Policy
Grade Appeal Process
Make-up Examinations
Nondiscrimination
Students with Disabilities
Hard copies of the catalog are available at your local Education Center.
|
|
Faculty Bio:
|
Dr. Dean earned the BA in Mathematics from Vanderbilt University, and the MS and PhD in Computer Science from the University of Alabama in Birmingham. She has worked at various times as a programmer, programmer/analyst, systems analyst, and project manager in the areas of medical information systems, small business support, and life insurance. Since 1975, she has been involved in teaching and curriculum development in computing and mathematics, most recently at Samford University in Birmingham, AL. She has served on the Board of Directors and as President of the Consortium for Computing Sciences in Colleges. She serves on the Regional Board of the CCSC Southeastern Conference. Her areas of interest include curriculum development, database management systems, programming languages, security, and operating systems.
|
|