Information Systems Department
SYLLABUS
|
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 Course 10 in the IS Model Curriculum. The course also dovetails with the Five Learning Goals & Outcomes of Education at UW-Eau Claire in the following manner:
|
GOAL |
CLASS ACTIVITY/PRODUCT |
|
|
1. |
Knowledge
of Human Culture |
a.
Essay on How to Get, Keep, and Quit IS Jobs in Your Career b.
Essay on the Nature and Value of Artificial Intelligence |
|
2. |
Creative
and Critical Thinking |
c.
Essay on How to Improve the IS Field d.
Project Management and Design Documents, Project Products e.
Essay on How General Systems Theory Informs the Scientific Method |
|
3. |
Effective
Communication |
f.
Presentations g.
Essay on How to Communicate IS Topics to an Intelligent but
Uninformed Audience h.
Project Management and Design Documents, Project Products |
|
4. |
Individual
and Social Responsibility |
i.
Essay Reporting Interview with UWEC Non-Business Faculty on IS Ethics
j.
Essay on IT and Making, Marketing, and Getting Art (of any type) k.
Essay on IS Security Issues |
|
5. |
Respect
for Diversity among People |
l.
Essay reporting E-Mail Thread or Chat with a non-U.S. IT College
Student Living Outside the USA m.
Essay on Lessons Learned from IS History n.
Essay on How to Improve Diversity of IS Majors at UW-Eau Claire |
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 current IS research, and
practicing 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 informed opinions on the current state of selected aspects of IS research or practice.
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 Topic Presentation |
|
10% |
Presentation-Related Web Page and Quiz Items |
|
10% |
Presentation-Related Quizzes |
|
35% |
Information System 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 topic 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
· 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
one essay from the list of activities to address the five goals of education at
UW – Eau Claire near the top of this syllabus. 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; 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 45-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 10-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. Critique the rehearsal of another team’s presentation outside class using the presentation grading sheet.
7. Rehearse the presentation using a draft of your visual aids and web page for the team that agrees to critique you.
8. In the presentation, dress, behave, accept input, and answer questions professionally.
9. Receive the evaluations of the instructor and the other class members.
10. As needed, meet with the instructor to resolve issues from the evaluations.
11. 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 Topic Presentation: Each team will give an oral presentation to the rest
of the class on the current state of a topic of their choice in the IS field
(see the list of possible topics for a few ideas). The
45-minute presentation will include the development of slides, test questions
(see below), and a web site (see below). Students will also take the quiz
associated with each presentation except their own. Note that, generally
speaking, vendor-specific presentations (e.g., presenting one software
application) are inappropriate for this presentation; software demonstrations
from multiple, competing vendors are, however, allowed.
Quiz Items: Each student in the
group will write at least five multiple-choice test items on the presentation
topic (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, punctuality,
mechanics, and format.
Web Page: Team members will work together to create a web page that complements their IS topic presentation and e-mail the URL to the instructor for linking to the syllabus. 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; and
· The quiz developed by the presentation team (also due one week after the presentation).
The web page will be graded by the
instructor per the criteria listed above.
Information System for Client: Throughout the semester, each
presentation 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
attend two interim planning meetings with the instructor during the development
of the system. The systems are graded using the IS Project
Evaluation Checklist. 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
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 TEAM PRESENTATIONS
1. Calculating the value of information or information systems
2. Quantum Computing or other non Von Neumann computing architectures
3. Messaging in Business—mechanisms, costs, benefits of chat, Instant Messaging, E-Mail, video-conferencing, etc.
4. Mainframe and supercomputing platforms, costs, uses, sources, etc.
5. Current and future computer programming languages; their use, benefits, problems, directions, etc.
6. Strategic Planning for Information Systems: Planning systems, design, implementation; advantages and disadvantages
7. Computer Hardware—concepts/terms, trouble-shooting, assembly/disassembly, care/maintenance/security
8. Communications—VOIP, POTS, wireless, wired communications; Internet and Web technologies, mobile
9. Service Providers and Outsourcing of Information Services—providers; users; how it affects IT staffing
10. Applications—Middleware and component software; enabling technologies for mobile Internet access
11. Web services—what they are, how they impact companies, who the vendors are, how they are used
12. Artificial Intelligence: its nature, applications, and issues
13. Investment Strategies related to technology stocks. Opportunities – what are they? Should you buy into them?
14. Peer-to-peer file sharing software and attendant social/legal issues
15. ERP and CRM - related vendors such as Banner, PeopleSoft, Oracle, Nortel, Vantive, SAP, etc.
16. Open-source systems: Pros & cons; future; capabilities; directions
17. Alternatives to Windows operating systems—products, pros/cons, market share, vendors, users, etc.
18. Role of IS in human resource management, accounting, finance, research/development, production, marketing, logistics/transportation, etc.
19. Professional development, professional certifications, and professional organizations in the IS field
20. E-business terms, concepts, and strategies
21. Acquiring software applications: how to decide whether to build, buy, or borrow
22. Non-PC personal computing: PDA’s, wearables, smart watches, RFID tags, etc.
23. Security, Piracy, or IT Ethics
24. The Legal Environment of IS
25. Performance Reviews for IS Personnel
26. Managing the IS function—organizational structure, job duties, strategic planning, leadership, CTO, CIO, etc.
27. Equity in IT employment practices—age, gender, disability, etc.
28. Interactive computer-based television, graphics, environments, etc.
29. Digital Convergence
30. Data management and storage technologies
31. Gazillions of other topics as approved by the instructor
|
IS
460 Team Assignments |
||
|
Team |
Client |
Members |
|
1 |
Eau Claire County |
Andrew Duckert, Josh Hebard, Sarah
Lembke |
|
2 |
Eau Claire County |
Travis Eichner, Peter Forcey, Matt
Hammock, Nick Kelly |
|
3 |
Healthcare Administration |
Becca Brandt, Kuang-Jer Cheng,
Lance Overson |
|
4 |
Western Dairyland |
Rob Frey, Chuo Lee, Derek Steffen |
|
5 |
Wisconsin Bio-energy Forum |
John Block, Sarah Drews, Cory
Germain |
|
6 |
Bolton Refuge House |
Josh Krebs, Jordan Sova, Peter
Storm |
|
7 |
L. E. Phillips Senior Center |
Matt Grube, Travis Krause, Dustin
Lakowske, Cliff Zevenbergen |
|
8 |
Gilman Care Center |
Dan Bindl, Jason Flackey, Patrick
McLaren |
|
9 |
Lost Pets |
Kevin Anderson, Chris Johnson,
Tammy Karlen |
|
SCHEDULE
FOR IS 460 |
||||
|
Day |
Date |
Topic |
Assignment |
Team |
|
T |
9/2 |
Course Introduction, Form Project Teams, Choose
Clients |
All |
|
|
R |
9/4 |
(Essay e) |
(All) |
|
|
T |
9/9 |
(Essay a, g) |
(All) |
|
|
R |
9/11 |
(Essay c) Write four sentences Initial Client Meeting Report |
(All) All Team 1 |
|
|
T |
9/16 |
(Essay l) Write one paragraph Study Example DFD Initial Client Meeting Report Initial Client Meeting Report |
(All) All All Team 2 Team 3 |
|
|
R |
9/18 |
Substantiate an assertion Design Walkthrough Planning Initial Client Meeting Report |
All Team 1 Team 4 |
|
|
T |
9/23 |
Example
Design Walkthrough Presentation Design Walkthrough Planning Design Walkthrough Planning Initial Client Meeting Report |
Team 2 Team 3 Team 5 |
|
|
R |
9/25 |
Attend Career Fair Design Walkthrough Approval Design Walkthrough Planning Initial Client Meeting Report |
All Team 1 Team 4 Team 6 |
|
|
T |
9/30 |
(Essay i, j, k) Design Walkthrough Approval Design Walkthrough Approval Design Walkthrough Planning Initial Client Meeting Report |
(All) Team 2 Team 3 Team 5 Team 7 |
|
|
R |
10/2* |
Guest Speaker: Charlie Anderson of Genesis10 |
Project Preparation Design Walkthrough Rehearsal |
All Team 1 |
|
T |
10/7 |
Team 1 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Design Walkthrough Approval Design Walkthrough Planning Initial Client Meeting Report |
Team 1 Team 2 Team 4 Team 6 Team 8 |
|
R |
10/9 |
Team 2 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Design Walkthrough Approval Design Walkthrough Planning Initial Client Meeting Report |
Team 2 Team 3 Team 5 Team 7 Team 9 |
|
T |
10/14 |
Team 3 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Design Walkthrough Approval Design Walkthrough Planning |
Team 3 Team 4 Team 6 Team 8 |
|
R |
10/16 |
Team 4 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Design Walkthrough Approval Design Walkthrough Planning |
Team 4 Team 5 Team 7 Team 9 |
|
T |
10/21 |
Team 5 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Design Walkthrough Approval Topic Initial Approval |
Team 5 Team 6 Team 8 Team 1 |
|
R |
10/23 |
Team 6 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Design Walkthrough Approval Topic Initial Approval |
Team 6 Team 7 Team 9 Team 2 |
|
T |
10/28 |
Team 7 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Topic Presentation Review Topic Initial Approval |
Team 7 Team 8 Team 1 Team 3 |
|
R |
10/30 |
Team 8 Client |
Design Walkthrough Presentation Design Walkthrough Rehearsal Topic Presentation Review Topic Initial Approval |
Team 8 Team 9 Team 2 Team 4 |
|
T |
11/4 |
Team 9 Client Libby Christiansen & Ellen Burgermeister Usability at Northwestern Mutual |
Design Walkthrough Presentation Topic Presentation Rehearsal Topic Presentation Review Topic Initial Approval |
Team 9 Team 1 Team 3 Team 5 |
|
R |
11/6 |
Team 1 Topic |
Topic Presentation Topic Presentation Rehearsal Topic Presentation Review Topic Initial Approval |
Team 1 Team 2 Team 4 Team 6 |
|
T |
11/11 |
Team 2 Topic |
Topic Presentation Topic Presentation Rehearsal Topic Presentation Review |
Team 2 Team 3 Team 5 |
|
R |
11/13 |
Team 3 Topic |
Topic Presentation Topic Presentation Rehearsal Topic Presentation Review Topic Initial Approval Topic Website & Quiz Online |
Team 3 Team 4 Team 6 Team 7 Team 1 |
|
T |
11/18 |
Team 4 Topic |
Topic Presentation Topic Presentation Rehearsal Topic Initial Approval Topic Website & Quiz Online |
Team 4 Team 5 Team 8 Team 2 |
|
R |
11/20 |
Team 5 Topic |
Topic Presentation Topic Presentation Rehearsal Topic Presentation Review Topic Initial Approval Topic Website & Quiz Online |
Team 5 Team 6 Team 7 Team 9 Team 3 |
|
T |
11/25 |
Team 6 Topic |
Topic Presentation Topic Presentation Review Topic Website & Quiz Online |
Team 6 Team 8 Team 4 |
|
R |
11/27* |
Thanksgiving |
Be grateful Topic Presentation Rehearsal Topic Website & Quiz Online |
All Team 7 Team 5 |
|
T |
12/2 |
Team 7 Topic |
Topic Presentation Topic Presentation Rehearsal Topic Presentation Review Topic Website & Quiz Online |
Team 7 Team 8 Team 9 Team 6 |
|
R |
12/4 |
Team 8 Topic |
Topic Presentation Topic Presentation Rehearsal |
Team 8 Team 9 |
|
T |
12/9 |
Team 9 Topic |
Topic Presentation Topic Website & Quiz Online |
Team 9 Team 7 |
|
R |
12/11 |
Final Project Presentations, Exit
Survey |
Topic Website & Quiz Online Topic Website & Quiz Online |
Team 8 Team 9 |
|
M |
12/15 |
3:00-6:00 p.m. Exit Exam |
Quizzes, essay due |
|
EVALUATION CHECKLIST FOR IS 460 TOPIC PRESENTATIONS
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) |
|
|
|
|
III. PRESENTATION |
(20
pts) |
|
|
|
|
IV. MEDIA |
(20
pts) |
|
|
|
|
V. SUBTOTALS |
|
|
|
|
|
|
(100pts) |
|
|
[___] |
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 |
|
|
|
|
[___] |
||
EVALUATION CHECKLIST FOR IS 460 ESSAYS
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:
__________________________________________________
_____________________________________________________________
_____________________________________________________________