|
COURSE: |
IS 460, Seminar in Information Systems, 3 credits |
|
INSTRUCTOR: |
Dr.
Thomas S. E. Hilton |
|
PREREQUISITE: |
Take as a last-semester senior |
COURSE GOALS: This course is designed to help IS majors in their last semester before graduation extend their understanding of the IS profession by studying aspects of it that are too new to be in textbooks and by integrating the content they have studied in prior courses. It covers all aspects of organizational information systems but emphasizes information systems management and the current state of the art. The course is highly integrative, including system design, system development, computer networks, database management, end-user computing issues, and other current topics. It is designed to correspond to Core Course 7 in the IS 2010 Model Curriculum. The course also dovetails with the Six Learning Goals & Outcomes of Education at UW-Eau Claire in the following manner:
|
GOAL |
CLASS
ACTIVITY/PRODUCT |
|
|
1. |
Knowledge of Human Culture and the Natural World |
Research project |
|
2. |
Creative and Critical Thinking |
Project Management and Design Documents, Project Products |
|
3. |
Effective Communication |
Presentations |
|
4. |
Individual and Social Responsibility |
Client Relations |
|
5. |
Respect for Diversity among People |
Systems Analysis & Design |
|
6. |
Integrative Learning |
Development Project |
OBJECTIVES: The objectives of this course center on learning IS concepts
not covered in other IS courses, refining understanding of vocabulary and
concepts studied in other IS courses, understanding and doing current IS
research, and engaging in professional communication:
1. Refine and extend the post-graduate employment campaign.
2. Integrate understanding of foundational IS concepts via the general systems view.
3. Share research findings on the current state of selected aspects of the IS field.
4. Develop a strategically important information system for a real client.
ACCOMMODATION OF DISABILITIES:
Students with disabilities are encouraged to discuss their needs with the
instructor, preferably during the first week of class. All reasonable
accommodations will be made to see that disabilities do not restrict a
student's opportunity to learn. Help is also available from the Disability Resource Center (Old Library
2136, phone 715/836-4542).
COMFORTABLE LEARNING ENVIRONMENT: UW-Eau Claire, the IS Department, and
your instructor are all committed to maintaining a non-threatening learning
environment for every student. All class members are thus to treat each other
politely—both in word and deed. Offensive humor and unwanted personal
advances are specifically forbidden. If you feel uncomfortable with a personal
interaction related to this class, feel free to see the instructor for help in
solving the problem. The dean of the
WORK REQUIRED FOR THE COURSE:
The class is organized to have maximum participation by the students.
Most course content will be taken from readings and presentations.
Supplementary information will be added by the instructor and class members as
needed. To complete course requirements, students will use e-mail, the
Worldwide Web, the McIntyre Library, etc. They will also develop and deliver
presentations, interact with team members and clients, and engage in system
development and project management.
STUDENT EVALUATION: Students' grades in the course consist of the ten
components listed next, each component contributing the indicated percentage of
the total grade:
|
5% |
Involvement with an I.S. Professional Society |
|
10% |
Class Participation |
|
10% |
Persuasive Essay |
|
20% |
IS Research Presentation |
|
10% |
Research-Related Webpage and Quiz Items |
|
10% |
Webpage-Related Quizzes |
|
35% |
Information System Design Walkthrough |
|
∞ |
Information System for Client |
|
∞ |
Final Exit Survey and Assessment Exam |
|
∞ |
Ethical Conduct |
Involvement with an I.S. Professional Society: It is virtually impossible to succeed in information systems without participating in a professional society. Active membership in a society such as AITP (via the IS-sponsored student chapter for instance) yields at least four benefits: contact with practicing professionals and potential employers, continuing education to stay current in the field, a forum for contributing ideas to the industry, and fun getting to know people like you. Hence, students are to be involved with a regional, national, or international professional society in the information systems field. To fulfill this requirement, students can show evidence of membership and participation (at least four hours during the semester) in such a society, or they can write a two- to three-page report describing an IS society they would join if they could and its potential benefits to their career. Membership in societies not in the information systems field (such as BUS, PBL, SHRM, APICS, BAP, SAS, etc.), while laudable, does not fulfill this requirement. Reports are due by the last regular class period. Late reports are normally not accepted. Reports are graded A/B/C/D/F on punctuality, content, organization, language mechanics, and format.
Class Participation: An important part of this class is practicing the use of appropriate vocabulary to discuss IS concepts and to learn from debate of current IS issues; all students are thus to attend all class sessions (this is University policy), participate vocally and regularly in class, and complete the quizzes associated with IS research presentations. Students should also come to every class prepared to evaluate and respond to each other's presentations. During the last week of regular classes before final exams, students are invited to e-mail the instructor with a self-assessment of their class participation. In their self-assessment they should treat at least these points:
· how often they were absent or tardy
· how attentive they were during class
· how often they volunteered comments in class
· how realistic their evaluations of classmate presentations were
· whether they were polite to and honest with the instructor and their classmates
· how well they participated in out-of-class team meetings
Students should bear in mind that a major objective in this class is to practice communicating professionally regarding IS issues: their e-mail message should thus be well written and their questions and comments well formed.
Persuasive
Essay: In the
course students will polish their understanding of the connections among the
diverse content areas in their education. As part of summing up their college
experience, students will write an essay defining and defending their opinion
on an IS-related controversy of their choice (cleared beforehand with the
instructor). Submissions will be graded on content, organization, language
mechanics, and formatting (for the
grading rubric, click here). Note that this
essay is to be an opportunity to develop and substantiate your own professional
opinion; while citing expert opinion and research is welcome, this is not to be
a research paper where you report only what the experts think. Note also that
you are to write this essay for IS 460; students are not to resubmit an essay
from another class.
General Presentation Guidelines
As described in more detail in succeeding paragraphs,
students will make three team-based presentations in the course: a 30-minute
design walkthrough for the information system they are developing, a 30-minute
in-depth analysis of the state of the art in an IS topic of their choice, and a
5-minute debrief of their completed information system development project. All
presentations are to follow these guidelines:
1. Gain approval of your topic from the instructor before investing lots of effort in it.
2. Develop an outline of the presentation content as a team, and review it with the instructor as a team.
3. Develop all presentation materials (e.g., PowerPoint file, web site, quiz, etc.).
4. Each team member participates equally in the in-class presentation.
5. Use visual aids and a web page.
6. Rehearse
the presentation using a draft of your visual aids and web page in front of
Sean Kaiser. Please contact him directly for an appointment during these hours:
+ Monday: 9-11 am, 12-2, 5-6
+ Tuesday: 9 am-2 pm, after 8:30 pm
+ Wednesday: 9-11 am, 1-2, or after 8 pm
+ Thursday: 1-2, after 5 p.m.
+ Friday: 9-11 a.m., after noon
7. In the presentation, dress, behave, accept input, and answer questions professionally.
8. Receive the evaluations of the instructor and the other class members.
9. As needed, meet with the instructor to resolve issues from the evaluations.
10. Although the instructor has final authority for each presentation's grade, class members will also evaluate the presentation; these evaluations will form the basis of presenters' grades. Evaluations will be graded on content, organization, presentation style, and media use. See the presentation grading sheet at the end of this syllabus.
IS Research Presentation: Each team will give an oral presentation to the
rest of the class on their research project (see the list of possible
topics for a few ideas). Note that presenting on a specific product from a
single vendor is discouraged, but comparing similar products from multiple
vendors is encouraged. The 30-minute presentation will include the development
of slides, quiz items (see below), and a web site (see below). Students will
also take the quiz associated with each presentation except their own.
Quiz Items: Each student in the
group will write at least five multiple-choice test items on the presentation
(e.g., a three-person group would generate at least 15 test items). Test items
should be addressed in the presentation and be written according to the guidelines for
writing high-quality multiple-choice items. For each item, identify the
correct answer and the content source. Once the test items are complete, e-mail
them to your team members for feedback and revision (consider using the
“track changes” feature of Word). Once all members of the team have
reviewed and approved all the items written for their presentation, link them
to the presentation web page (see below). Test items are due one week after the
presentation date. Once the items are posted to the Web, all class members
should study the items for each presentation and e-mail questions regarding
them to all the members of the presentation team that developed them.
Presentation team members should consult with each other and the instructor as
needed to generate a correct response to each question then modify test items,
inform the class members, or take other appropriate action. The test items thus
developed and revised will form the quiz that all students must complete as
homework for the presentation. Test items are graded on content, language
mechanics, and format.
Web Page: Team members will work together to create a simple, attractive web page in SharePoint that complements their IS research presentation. At minimum, the web site home page is to include the following components:
· The presentation title, course name and section number, team members’ names and contact information, and the presentation date;
· A one- or two-paragraph summary of the major ideas treated in the presentation;
· A link (or other access directions) to the sources used by the team in preparing the presentation;
· A link to the presentation aids (e.g., PowerPoint slides, test items, etc.) used in the presentation;
· The quiz developed by the presentation team (also due one week after the presentation); and
The web page will be graded by the
instructor per the criteria listed above.
Information System for Client: Throughout the semester, each team
will complete a full information system development project for a community
client approved by the instructor. This can be structured to fulfill the
Service-Learning graduation requirement if needed. The project must incorporate
all phases of the System Development Life Cycle: feasibility study, system
analysis, design, development, testing, implementation (including user training
and documentation), and maintenance. Team members will make two project-related
presentations to the class during the semester: a) the initial system design
walkthrough and b) a debrief presentation of the completed system; clients are
encouraged to attend these presentations. Team members will participate in two
interim planning meetings with the instructor during the development of the
system. The systems are graded using the IS Project
Evaluation Checklist. All project-related documentation is to be developed
and stored in the
project’s SharePoint site, and completed information systems are
due in final form no later than the last regular class day before final exam
week.
Final Exit Survey and Assessment Exam: Two assessment
activities will comprise the final exam. The first is an exit survey, and the
second is a multiple-choice vocabulary & concept exam covering all aspects
of the IS field. Both the survey and exam will be administered online in class.
The exit survey is internally developed and will take about 15 minutes of the
last regular class period. The exam is provided through the Institute for the
Certification of Computer Professionals (ICCP),
the most broadly recognized independent professional certification authority in
the IS field, and is a three-hour timed exam. Both the survey and exam are for
assessing the IS Department; hence, your performance on the test has no effect
on your course grade. However, to pass this class you are required to complete
the survey and the exam with a good-faith effort. Students who score 50% or
higher on the exam qualify for ICCP certification at the Information Systems
Analyst (ISA) level; students who score 75% or higher can count the exam toward
ICCP certification at the Certified Computer Professional (CCP) level.
Ethical Conduct: To pass this
course, students must behave in accordance with defined norms of professional
ethics. In part, these include submitting assignments and arriving in class on
time; doing your own work on assignments, reports, and tests; attending and
participating in all class sessions; dressing appropriately; behaving
collegially; and obeying the law. For more detail, see the IS Faculty and
Student Ethical Standards.
IS 460
POSSIBLE TOPICS FOR RESEARCH PRESENTATIONS
1. Calculating the value of information or information systems
2. Multi-core, parallel, quantum and other non-Von-Neumann computing architectures
3. Social media in organizations—mechanisms, costs, benefits of chat, instant messaging, email, videoconferencing, Facebook, etc.
4. Accessibility in computing, computing to compensate for disabilities
5. Mainframe and supercomputing platforms, costs, uses, sources, etc.
6. Current and future computer programming languages; their use, benefits, problems, directions, etc.
7. Strategic Planning for Information Systems: Planning systems, design, implementation; advantages and disadvantages
8. Computer Hardware—concepts/terms, trouble-shooting, assembly/disassembly, care/maintenance/security
9. Communications—VOIP, POTS, wireless, wired communications; Internet and Web technologies, softphones, mobile
10. Service Providers and Outsourcing of Information Services—providers; users; how it affects IT staffing
11. Applications—Middleware and component software; enabling technologies for mobile Internet access
12. Web services—what they are, how they impact companies, who the vendors are, how they are used
13. Artificial Intelligence: its nature, applications, and issues
14. Investment Strategies related to technology stocks. Opportunities – what are they? Should you buy into them?
15. Ethical, social, or legal issues of computing
16. ERP and CRM - related vendors such as Banner, PeopleSoft, Oracle, Nortel, Vantive, SAP, etc.
17. Open-source software systems: Pros & cons; future; capabilities; directions
18. Alternatives to Windows operating systems—products, pros/cons, market share, vendors, users, etc.
19. Role of IS in human resource management, accounting, finance, research/development, production, marketing, logistics/transportation, etc.
20. E-business terms, concepts, and strategies
21. Cloud, SOA, and other Web-centric architectures
22. Acquiring software applications: deciding whether to build, buy, or borrow
23. Non-PC personal computing: smart phones, tablets, wearables, implants, RFID tags, etc.
24. Security, piracy, hacking, cyber-warfare
25. What attracts people into the IS field? What causes them to leave? How to tell if someone will succeed in IS?
26. Professional development, professional certifications, and professional organizations in the IS field
27. Performance Reviews for IS Personnel
28. Managing the IS function—organizational structure, job duties, strategic planning, leadership, CTO, CIO, etc.
29. Equity in IT employment practices—age, gender, disability, etc.
30. Costs & benefits of IP TV, online gaming, and other online entertainment
31. Digital Convergence
32. Big Data management and storage technologies
33. Future input and output devices
34. Gazillions of other topics as approved by the instructor
|
IS 460 Team Assignments |
|||
|
Team |
Members |
Development Project |
Research Project |
|
1 |
Tyrrell Wirkus Joel Manteufel Andrew Kuhnmuench |
Epilepsy Foundation of
Western Wisconsin |
Emerging Data |
|
2 |
Brandin Henke Michael Tousley Brian Ely |
Chippewa Valley Free Clinic |
Cloud Computing |
|
3 |
Lauren Philippi Philip Pizza Corey Groshens |
Vecon Inc |
Externally Implemented |
|
4 |
Alex Molter Lucas Johnson Daniel Beihoff |
Eau Claire City Council |
Wearable/Implantable computers and |
|
5 |
See Vue Jakob Broesch Jordan Leonhardt |
UWEC Chinese Culture Club |
Internally Implemented |
|
6 |
Brandon Garrett Joshua Stolberg Matthew Kempfert |
Eau Claire School Library
Friends |
Bitcoin: The (Electronic) |
|
7 |
Travis Wozniak Brian Stangel Matthew Nye |
Quality Cleaners |
Head-Mounted Displays |
|
8 |
Brian Murphy Samantha Winkler Reid Fenton |
Half Moon Education |
Artificial Intelligence: |
|
9 |
Neil Busick Christian Head Julie Sullivan |
UWEC LTS |
Professional Development after College |
|
10 |
Michael Abbott Eric Adank Joseph Burns |
Continental Products |
Responsive Design |
|
11 |
Sarah Munson Nathan Arey Conor Rzeszutek |
Jason Borneman
Photography |
Mobile Operating Systems |
|
12 |
Andrew Faber Brandon Cole Christopher Buell |
Concrete Cutting |
OLEDs are really cool! |
|
13 |
Alan Gustafson Christian Untiedt Matthew Mauer Anthony Wegleitner |
Hickok Businesses |
The Open Source Movement, Packages, |
|
14 |
John Drews Major Sanguansack MaiThao Yang Benjamin Cumming |
McDonald’s Offline POS |
Social Issues of |
SCHEDULE FOR IS 460
|
Day |
Date |
Topic |
Teams
1&8 |
Teams
2&9 |
Teams
3&10 |
Teams
4&11 |
Teams
5&12 |
Teams
6&13 |
Teams
7&14 |
|
W |
01/23 |
Course Introduction |
Form Teams Choose Clients |
Form Teams Choose Clients |
Form Teams Choose Clients |
Form Teams Choose Clients |
Form Teams Choose Clients |
Form Teams Choose Clients |
Form Teams Choose Clients |
|
M |
01/28 |
Choose Clients Research Topics |
Choose Clients Research Topics |
Choose Clients Research Topics |
Choose Clients Research Topics |
Choose Clients Research Topics |
Choose Clients Research Topics |
Choose Clients Research Topics |
|
|
W |
01/30 |
|
|
|
|
|
|
||
|
M |
02/04 |
|
|
|
|
|
|
||
|
W |
02/06 |
Initial Report |
|
|
|
|
|
||
|
M |
02/11 |
Example DFD |
|||||||
|
W |
02/13 |
Example |
|
Example |
|
||||
|
M |
02/18 |
|
Design Planning |
|
Initial Report |
|
|
|
|
|
W |
02/20 |
Design Approval (bring PowerPoint) |
Design Planning |
Initial Report |
|||||
|
M |
02/25 |
|
Design Approval (bring PowerPoint) |
|
Design Planning |
|
Initial Report |
|
|
|
W |
02/27 |
HighJump
Software IS Careers |
Design Rehearsal |
|
Design Approval (bring PowerPoint) |
|
Design Planning |
|
Initial Report |
|
M |
03/04 |
Teams 1&8 |
Design |
Design Rehearsal |
|
Design Approval (bring PowerPoint) |
|
Design Planning |
|
|
W |
03/06 |
Teams 2&9 |
|
Design |
Design Rehearsal |
|
Design Approval |
|
Design Planning |
|
M |
03/11 |
Teams 3&10 |
Research Topic |
|
Design |
Design Rehearsal |
|
Design Approval |
|
|
W |
03/13 |
Teams 4&11 |
|
Research Topic |
|
Design |
Design Rehearsal |
|
Design Approval |
|
M |
03/18* |
Class dismissed for spring break |
|
|
|
|
|
|
|
|
W |
03/20* |
Class dismissed for spring break |
|
|
|
|
|
|
|
|
M |
03/25 |
Teams 5&12 |
Research Planning (bring outline) |
|
Research Topic |
|
Design |
Design Rehearsal |
|
|
W |
03/27 |
Teams 6&13 |
|
Research Planning (bring outline) |
|
Research Topic |
|
Design |
Design Rehearsal |
|
M |
04/01 |
Teams 7&14 |
Research Approval (bring PowerPoint) |
|
Research Planning (bring outline) |
|
Research Topic |
|
Design |
|
W |
04/03 |
Jeff Cookle, Hormel |
|
Research Approval (bring PowerPoint) |
|
Research Planning |
|
Research Topic |
|
|
M |
04/08 |
SharePoint Websites |
Research Rehearsal (outside class with Sean Kaiser) |
|
Research Approval (bring PowerPoint) |
|
Research Planning |
|
Research Topic |
|
W |
04/10 |
Teams 1&8 |
Research Presentation |
Research Rehearsal (outside class with Sean Kaiser) |
|
Research Approval |
|
Research Planning |
|
|
M |
04/15 |
Teams 2&9 |
|
Research Presentation |
Research Rehearsal (outside class with Sean Kaiser) |
|
Research Approval |
|
Research Planning |
|
W |
04/17 |
Teams 3&10 |
Research Website |
|
Research Presentation |
Research Rehearsal |
|
Research Approval |
|
|
M |
04/22 |
Teams 4&11 |
|
Research Website |
|
Research Presentation |
Research Rehearsal |
|
Research Approval |
|
W |
04/24 |
Teams 5&12 |
|
|
Research Website |
|
Research Presentation |
Research Rehearsal |
|
|
M |
04/29 |
Teams 6&13 |
|
|
|
Research Website |
|
Research Presentation |
Research Rehearsal |
|
W |
05/01 |
Teams 7&14 |
|
|
|
|
Research Website |
|
Research Presentation |
|
M |
05/06 |
Project Final Reports |
|
|
|
|
|
Research Website |
|
|
W |
05/08 |
Course Evaluation |
|
|
|
|
|
|
Research Website |
|
M |
05/13 |
Any 3 contiguous hrs 2:00-7:00p |
Quizzes due Essay due |
Quizzes due Essay due |
Quizzes due Essay due |
Quizzes due Essay due |
Quizzes due Essay due |
Quizzes due Essay due |
Quizzes due Essay due |
EVALUATION CHECKLIST FOR IS 460 RESEARCH PRESENTATION
Presenters:
______________________________________________________________
Topic: __________________________________________________________________
Evaluator: _______________________________________________________________
|
|
Absent |
Poor |
Fair |
Good |
|
I. CONTENT E. Verifiability (sources, citations) |
(40
pts) [
0 ] |
[ 3 ] [ 3 ] |
[ 5 ] [ 5 ] |
[ 8 ] [ 8 ] |
|
II. ORGANIZATION |
(20
pts) |
[
1 ] |
|
|
|
III. PRESENTATION |
(20
pts) |
|
|
|
|
IV. MEDIA |
(20
pts) |
|
|
|
|
V. SUBTOTALS |
|
|
|
|
|
|
(100pts) |
|
|
[___]* |
|
*On the assumption that nobody’s perfect, scores of 100 are considered the result of inattention and are not counted. |
||||
Comments: ______________________________________________________________
________________________________________________________________________
________________________________________________________________________
|
IS 460 SEMINAR IN
INFORMATION SYSTEMS EVALUATION CHECKLIST
FOR INFORMATION SYSTEM DEVELOPMENT PROJECT |
|||||||
|
Authors:
_______________________________________________________ |
Evaluator:
____________________ |
||||||
|
I.
FEASIBILITY STUDY |
20 pts |
Absent |
Poor |
Fair |
Good |
||
|
|
A. Project |
|
|
|
|
|
|
|
|
|
1. Environment (organization, client, etc.) |
|
0 |
0 |
1 |
2 |
|
|
|
2. Boundary (scope: what's in; what's out) |
|
0 |
1 |
2 |
4 |
|
|
|
3. Intended Output/Purpose (business benefits,
problems to solve) |
|
0 |
0 |
1 |
2 |
|
|
|
4. Input (primary/secondary users, other
stakeholders) |
|
0 |
0 |
1 |
2 |
|
|
B. Feasibility |
|
|
|
|
|
|
|
|
|
1. Personnel (team members and
expertise/assignments) |
|
0 |
1 |
2 |
3 |
|
|
|
2. Budget (labor, equipment, facilities,
consumables, etc.) |
|
0 |
1 |
2 |
3 |
|
|
|
3. Time (Milestones/deliverables; Gantt, PERT,
CPA, other) |
|
0 |
1 |
2 |
4 |
|
II.
ANALYSIS OF EXISTING BUSINESS SYSTEM |
24 pts |
Absent |
Poor |
Fair |
Good |
||
|
|
A. Output/Information (purpose/product,
unintended) |
|
0 |
1 |
3 |
4 |
|
|
|
B. Processes: Transformation/Control (DFD, OO, or
other) |
|
0 |
1 |
3 |
4 |
|
|
|
C. Processes: Storage (ERD, OO, or other) |
|
0 |
1 |
3 |
4 |
|
|
|
D. Processes: Interface (Mock-ups, samples, OO, or
other) |
|
0 |
1 |
3 |
4 |
|
|
|
E. Input/Data (Main input from users, Maintenance
input) |
|
0 |
1 |
3 |
4 |
|
|
|
F. Boundary & Environment (Hardware, Software,
Wetware) |
|
0 |
1 |
3 |
4 |
|
|
III.
DESIGN OF NEW SYSTEM (evolve from II) |
36 pts |
Absent |
Poor |
Fair |
Good |
||
|
|
A. Output/Information (purpose/product,
unintended) |
|
0 |
1 |
3 |
4 |
|
|
|
B. Logical Processes: Transformation/Control (DFD,
OO, or other) |
|
0 |
1 |
3 |
4 |
|
|
|
C. Logical Processes: Functional Primitives, Pseudocode |
|
0 |
1 |
3 |
5 |
|
|
|
D. Detailed Processes: Data Store (ERD/OD in 3NF,
tree diagram, network diagram) |
|
0 |
1 |
3 |
5 |
|
|
|
E. Physical Processes: Interface (Mock-ups,
samples, OO, or other) |
|
0 |
1 |
3 |
4 |
|
|
|
F. Input/Data (Main input from users, Maintenance
input) |
|
0 |
1 |
3 |
4 |
|
|
|
G. Boundary & Environment |
|
|
|
|
|
|
|
|
|
1. Network (links, leased lines, topologies,
protocols, etc.) |
|
0 |
0 |
1 |
2 |
|
|
|
2. Nodes (clients, servers) |
|
0 |
1 |
2 |
3 |
|
|
|
3. Software (OS, NOS, DB, IDE, Applications, etc.) |
|
0 |
0 |
1 |
2 |
|
|
|
4. Security (Personnel, Physical, Procedural,
Technical) |
|
0 |
1 |
2 |
3 |
|
IV.
COST-BENEFIT ANALYSIS (for depreciation period) |
10 pts |
Absent |
Poor |
Fair |
Good |
||
|
|
A. Reasonably Quantify All Tangible Costs |
|
0 |
0 |
1 |
2 |
|
|
|
B. Reasonably Quantify All Intangible Costs |
|
0 |
0 |
1 |
2 |
|
|
|
C. Reasonably Quantify All Tangible Benefits |
|
0 |
0 |
1 |
2 |
|
|
|
D. Reasonably Quantify All Intangible Benefits |
|
0 |
0 |
1 |
2 |
|
|
|
E. Calculate a justifiable cost-benefit ratio <
1 |
|
0 |
0 |
1 |
2 |
|
|
V.
IMPLEMENTATION |
10 pts |
Absent |
Poor |
Fair |
Good |
||
|
|
A. Coding Plan (inputs, tools, products,
structure, personnel) |
|
0 |
0 |
1 |
2 |
|
|
|
B. Testing Plan (Alpha, Beta) |
|
0 |
0 |
1 |
2 |
|
|
|
C. Deployment Plan (tandem, site-phased,
module-phased, cut-over) |
|
0 |
0 |
1 |
2 |
|
|
|
D. Training Plan (including user materials) |
|
0 |
0 |
1 |
2 |
|
|
|
E. Maintenance/Support Plan (time frame,
resources/cost, personnel) |
|
0 |
0 |
1 |
2 |
|
|
VI.
PROFESSIONALISM |
0 pts |
Absent |
Poor |
Fair |
Good |
||
|
|
A. Design Walkthrough Presentation |
|
∞ |
∞ |
-10 |
-0 |
|
|
|
B. Punctuality (1 day late, on time) |
|
∞ |
∞ |
-10 |
-0 |
|
|
|
C.
Client Letter of Acceptance |
|
∞ |
∞ |
∞ |
-0 |
|
|
|
D.
Ethical Behavior |
|
∞ |
∞ |
∞ |
-0 |
|
|
VII. SUBTOTALS |
100 pts |
|
|
|
|
||
|
|
A. Feasibility Study |
20 pts |
|
|
|
[___] |
|
|
|
B. Analysis of Existing System |
24 pts |
|
|
|
[___] |
|
|
|
C. Design of New System |
36 pts |
|
|
|
[___] |
|
|
|
E.
Cost-Benefit Analysis |
10 pts |
|
|
|
[___] |
|
|
|
F.
Implementation |
10 pts |
|
|
|
[___] |
|
|
|
G.
Professionalism |
∞ |
|
|
|
[___] |
|
|
VIII.
TOTAL/GRADE* |
|
|
|
|
[___] |
||
|
*On
the assumption that nobody’s perfect, scores of 100 are considered the
result of inattention and are not counted. |
|||||||
EVALUATION CHECKLIST FOR IS 460 ESSAY
Author: ____________________________________________________
Assignment: ________________________________________________
|
|
Absent |
Poor |
Fair |
Good |
|
I. CONTENT E.
Verifiability (sources, citations) |
(40 pts) [ 0 ] |
[ 3 ] [ 3 ] |
[ 5 ] [ 5 ] |
[ 8 ] [ 8 ] |
|
II. ORGANIZATION |
(20 pts) |
|
|
|
|
III. LANGUAGE D. Punctuation E.
Spelling |
(25 pts) |
|
|
|
|
IV. FORMAT |
(15 pts) |
|
|
|
|
V. SUBTOTALS |
|
|
|
|
|
|
(100pts) |
|
|
[___] |
Comments: __________________________________________________
_____________________________________________________________
_____________________________________________________________