Faculty Contact Information:
Instructor can be contacted by e-mail:
yhinz@faculty.ed.umuc.edu
|
|
Consultation:
In classroom during our four meetings
Via e-mail and WebTycho (CET)
|
|
Required Texts and Readings:
|
Leedy, P. and Ormrod, J. (2005). Practical Research: Planning and Design, 8th edition. Upper Saddle River, NJ, Prentice-Hall, Inc.
|
|
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.ed.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. (Formerly INSS 680.) Prerequisites: INSS 540 or INSS 640, INSS 550 or INSS 650, INSS 620 or INSS 720, 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 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. 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.
|
|
Description of Course Requirements:
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 880 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 880 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 880
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/880Proposal.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 880 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 880.
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 880 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.
|
|
Course Schedule:
Saturday (5 April 2008)
Introduction to course, instructor, and other class members
Submit a brief biography to Introductions
The Planning/Survey Phase
Review the SDLC in INSS 540 text, paying particular attention to the deliverables, phase completeness, and timeline
Obtain instructor's approval for your project
Analysis/Study Phase
Walkthroughs Review
User Definition Review
Review and comment on peers' Proposals
Review the discussion on walkthroughs in INSS 640 text
Develop a walkthrough report for use by other students in analyzing your work
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
End of first grading period
Sunday (6 April 2008)
Design Phase
Submit preliminary design for walkthrough and develop a preliminary evaluation plan
Submit final design for walkthrough
End of second grading period
Saturday (17 May 2008)
Construction Phase
First draft of the deliverables due, including Implementation Plan
End of third grading period
Sunday (18 May 2008)
Delivery Phase
Provide either a status report or submit draft deliverables for review
Evaluation Phase
Final Project Due, including report on Lessons Learned and Actual vs. Budgeted schedule and resources
Provide constructive feedback to other students regarding Final Project deliverables
Celebrate your accomplishments, and share the lessons learned
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.
Students with disabilities should contact the appropriate support office at UMUC-Europe.
Jan Keller, Director of Student Services
UMUC-Europe, Heidelberg
Phone: +49-6221-378299
Email: edstudent_svc@ed.umuc.edu
Mailing Address: Unit 29216, APO AE 09102 OR Im Bosseldorn 30, D-69126 Heidelberg, Germany
Please refer 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
Code of Civility
Hard copies of the catalog are available at your local Education Center.
|
|
Faculty Bio:
Spending a significant part of his life in Poland, Yurek Hinz had been a professional musician for over 25 years both, in Europe and the U.S. Earning his first Master of Music degree in 1989 from the Chopin Conservatory of Music, Warsaw, Poland, in 1990, he was granted a full scholarship to study communication at Regent University, Virginia Beach, VA, were he received a Master of Arts degree in Radio Production and Directing two years later.
Yurek Hinz also graduated with the Master of Science degree in Management Information Systems from Bowie State University, Bowie, MD in 2002.
Currently he holds the following professional certifications: Information Systems Analyst Certificate, MCP, MCSA, MCSE, MCSA 2003: Security, MCSE 2003: Security, CompTIA Network+ and CompTIA Security+.
Mr. Hinz is an IT Specialist for the Information Assurance Program Management’s (IAPM) PKI Team in Schwetzingen, Germany. In 2006, he was accepted to the Northcentral Univeristy's PhD program in Management Information Systems and hopes to complete his dissertation by 2009.
|
|