There is no text for this course.

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.

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.

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.

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.

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

A grade of Pass (P) will be achieved with a minimum of 80%

The grade F 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/.

The course is divided into four grading periods (see Course Schedule). Each of the four periods contributes 20% of the total course grade, and is based on evaluation by the instructor of (a) 12 % quality of content and timely posting of assigned deliverables and reports (see Course Schedule), and (b) 8 % participation during the grading period. The remaining 20% of the course grade comes from (a) 15% quality of content and timely posting of the final report and other deliverables specified in the Course Schedule, and (b) 5% participation in the evaluation of the final postings by the other students.

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.

Note that while group projects are possible, they are not encouraged, and group projects should not involve more than two participants. For a team project to be approved, the proposal must clearly demonstrate which student will be doing which work, and that each student will do as much work as would have been required had the student done a "solo" project.

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.

Participation
Students are expected to be present at least twice a week via WebTycho, and to post progress reports and deliverables according to the Course Schedule. It is extremely valuable to receive the feedback of fellow students, so each student is expected to participate actively. Part of your grade comes from the quality (not quantity!) of your feedback to other students. Please try to provide explanations and references for your suggestions where possible.
There will be defined spaces for posting of your reports, deliverables, and feedback, and your grade will come from what you post there. Much more information regarding this will be given within the WebTycho classroom for this course.

If there is a week when you cannot participate, please notify the instructor via email of when and why you cannot.

Project Proposal for Information Systems Practicum -- INSS 680

Project proposals are due the first week of the course. You are encouraged to communicate with the instructor via email prior to the start of the course regarding the project and its scope.

Prior to the time when you have access to the WebTycho classroom, the project proposal form is available at:
http://faculty.ed.umuc.edu/~sdean/680Proposal.doc

The form is designed so that student, faculty, and organization 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, or military environments. The student is to propose a systems development project in which all of the systems development cycles can be experienced.

The project proposal is to be written so that it provides enough information that another student could be assigned to do the project. Provide sufficient detail for the instructor and your fellow classmates to realistically evaluate what is to be done, and whether or not it is feasible with the given resources (including the length of the course).

The following guidelines must be used when completing the Project Proposal:
Consider the length of the course. 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 evaluate 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" 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.

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: A User Manual for the system; Analysis Documents that could include interviews, periodical research and other tasks associated with the analysis phase; A detailed Design Document; A Programmer's/System Administrator's Maintenance Manual for an implemented database system. Review an INSS 540 textbook for further examples of deliverables associated with development of systems.

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.

Projected Course Schedule: Note the not everyone is expected to be precisely at the designated phase of the SDLC as targeted here in any given week. Depending on the nature of the projects, different ones will be in different phases at any given time. What IS expected is that throughout the course each week you will clearly demonstrate that significant progress has been made on your project, and you will communicate constructively regarding the projects of your fellow students. You are required to submit at least a progress report in each week of the course. Pre-class 1 WebTycho, Connectivity, and preparation for the Practicum; Connect to WebTycho, send an e-mail to the instructor, review the SDLC in an INSS540 text, and explore potential projects Class 1 - week of 29 Aug Introduction to course, lecturer, and other class members; The Planning/Survey Phase; Submit a brief biography to Introductions; review the SDLC in INSS 540 text, paying particular attention to the deliverables and tasks by Phase complete a Project Proposal Form and timeline; obtain instructor's approval for your project; Class 2 - week of 5 Sept Analysis/Study Phase; Walkthroughs Review; User Definition Review; Review and comment on peers' Proposals; review the discussion on walkthroughs in INSS 540 text develop a walkthrough report for use by other students in analyzing your work; Class 3 - week of 12 Sept 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 forms. End of first grading period. Class 4 - week of 19 Sept Design Phase; Comment on peers' project plans; Work on design Class 5 - week of 26 Sept Design Phase; Submit preliminary design for walkthrough and develop a preliminary evaluation plan; Be an active participant in the walkthroughs Class 6 - week of 3 Oct Design Phase; Submit final design for walkthrough; Be an active participant in the walkthroughs. End of second grading period. Class 7 - week of 10 Oct Construction Phase; Continue activities listed above and begin constructing the proposed project Break: 15-23 Oct, 2005 Class 8 - week of 24 Oct Construction Phase; Provide either a status report or submit draft deliverables for review; Be an active participant in reviewing the work of classmates Class 9 - week of 31 Oct Construction Phase; Provide either a status report or submit draft deliverables for review; Be an active participant in reviewing the work of classmates End of third grading period. Class 10 - week of 7 Nov Construction Phase; Provide either a status report or submit draft deliverables for review; Be an active participant in reviewing the work of classmates Class 11 - week of 14 Nov Construction Phase; First Draft of the Deliverables Due, including Implementation Plan. Class 12 - week of 21 Nov Delivery Phase; Provide either a status report or submit draft deliverables for review; Be an active participant in reviewing the work of classmates End of fourth grading period. Class 13 - week of 28 Nov Delivery Phase; Provide either a status report or submit draft deliverables for review; Be an active participant in reviewing the work of classmates Class 14 - week of 5 Dec Evaluation Phase; Final Project Due, including report on Lessons Learned and Actual vs. Budgeted schedule and resources Class 15 - Week of 12 Dec Provide constructive feedback to other students regarding Final Project deliverables. Celebrate your accomplishments, and share the lessons learned!

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
Code of Civility

Hard copies of the catalog are available at your local Education Center.