Syllabus Entrance
Printer Friendly
Email Syllabus

IS 315 Computer Systems Analysis and Design I
Kellenberger, Fred J.


Mission Statement: The mission of Park University, an entrepreneurial institution of learning, is to provide access to academic excellence, which will prepare learners to think critically, communicate effectively and engage in lifelong learning while serving a global community.

Vision Statement: Park University will be a renowned international leader in providing innovative educational opportunities for learners within the global society.

Course

IS 315 Computer Systems Analysis and Design I

Semester

F1T 2006 DLA

Faculty

Kellenberger, Fred J.

Title

Adjunct Faculty

Degrees/Certificates

B.A., M.S

Daytime Phone

760-717-8022 (cell)

E-Mail

fred.kellenberger@park.edu

fkellenb@yahoo.com

Class Days

TBA

Class Time

TBA

Prerequisites

Suggested prerequisite: IS205.

Credit Hours

3


Textbook:

Kendall & Kendall, Systems Analysis & Design, 6th Edition,

Bundled with: Visible Analyst Workbench 7.5 CD.

Prentice Hall

Textbooks can be purchased through the MBS bookstore

Textbooks can be purchased through the Parkville Bookstore

Additional Resources:

McAfee Memorial Library - Online information, links, electronic databases and the Online catalog. Contact the library for further assistance via email or at 800-270-4347.
Career Counseling - The Career Development Center (CDC) provides services for all stages of career development.  The mission of the CDC is to provide the career planning tools to ensure a lifetime of career success.
Park Helpdesk - If you have forgotten your OPEN ID or Password, or need assistance with your PirateMail account, please email helpdesk@park.edu or call 800-927-3024
Resources for Current Students - A great place to look for all kinds of information http://www.park.edu/Current/.
Advising - Park University would like to assist you in achieving your educational goals. Please contact your Campus Center for advising or enrollment adjustment information.
Online Classroom Technical Support - For technical assistance with the Online classroom, email helpdesk@parkonline.org or call the helpdesk at 866-301-PARK (7275). To see the technical requirements for Online courses, please visit the http://parkonline.org website, and click on the "Technical Requirements" link, and click on "BROWSER Test" to see if your system is ready.
FAQ's for Online Students - You might find the answer to your questions here.


Course Description:
This course presents various philosophies, terminology, and techniques used in the analysis and implementation of the system development life cycle. The student will investigate such areas as project proposals, logical systems, flow diagrams, data modeling, dictionaries, and documentation. The student will learn how to use a CASE tool. PREREQUISITE: IS 205. 3:0:3

Learning Outcomes:
  Core Learning Outcomes

  1. Identify stakeholders and describe their roles and individual needs in system development.
  2. Explain the Information Systems professional's role and the user's role in system development in order to achieve user acceptance and a solution that fits both the user's needs and satisfies the business objective.
  3. Evaluate strengths/weaknesses and applicable roles of several strategies/methodologies for design of information systems including Model Driven, RAD, Agile, OO development, and Prototyping.
  4. Evaluate problem/opportunity/directive, cause/effect and business requirements for a given problem scenario.
  5. Illustrate and explain project management life cycle, approaches to scheduling, measuring of project progress and relationship to the system development life cycle.
  6. Identify the responsibilities of the Project Manager and discuss why they are important to the success of the project.
  7. Practice systems analysis traditional tasks: Problem analysis, Requirements analysis. Decision analysis
  8. Build process and data models for analysis within the system development life cycle.
  9. Differentiate between logical and physical models.
  10. Communicate both orally and in writing as an individual and as a member of a team.


Core Assessment:

All Park University courses must include a core assessment that measures the relevant Departmental Learning Outcomes.  The purpose of this assessment is to determine if expectations have been met concerning mastery of learning outcomes across all instructional modalities. The core assessment for this course is a project which counts for 20% of the grade. The course project will be an information system plan for a system chosen by the student. Emphasis will be on developing the basic components of a system using system analysis tools and methodology. The system may be stand alone or integrated with other systems in the organization. Each week portions of the project will be developed including a system description, needs analysis, feasibility analysis, data analysis, process analysis, and financial analysis. Computer aided software engineering (CASE) tools will be used where needed in support of the weekly assignments. The final project document is due at the end of the course with all assignments integrated into one document.

Link to Class Rubric

Class Assessment:
Week 1: Systems Analysis Fundamentals Overview & Introductions: Review the syllabus, course policies, and assignment schedule. Write a paragraph about yourself and submit it to the classroom. Lecture: Read the lecture on "Using a CASE Tool". Reading Assignment: Systems Analysis & Design Chapters 1, 2 Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 23 or 44 that has not been previously answered. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Homework Problem: Choose one problem from Systems Analysis & Design on page 25 or 45 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Groupwork: Join a group and introduce yourself in the group study area. With your group, review possibilities for a groupwork project. During the course the group will be developing a groupwork Project Document for a system development activity with which you are familiar. You should choose a simple activity from your personal life or one at work. The activity should have a definite beginning, a definite completion point, milestones to be achieved, and resources to be applied. The activity must involve more than one person. Send your groupwork project description to the instructor by e-mail for approval. Individual Project: Choose an information system for an individual project. During the course your project will be developing an Information Systems Plan for an existing or hypothetical system. Each week you will develop parts of that plan. Weekly assignments include a system description, needs analysis, feasibility analysis, data analysis, process analysis, and financial analysis. The final assignment will be to consolidate all previous assignments into one document. Once you have chosen a system, submit your choice to the instructor by e-mail for approval, and then post it to the virtual classroom. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 22 or 44 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 2: Managing Systems Analysis & Design Activities Lecture: Read the lecture on "The System Development Life Cycle As A Project". Reading Assignment: Systems Analysis & Design Chapter 3. Search the Internet for project management information. Include the following websites in the reading: -  Project Management Resources & Exploration: http://web.mit.edu/ist/about/resources/projectmgmt/index.html -  ACM Portal: http://portal.acm.org/citation.cfm?doid=332051.332066 Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 81 that has not been previously answered. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Homework Problem: Choose one problem from Systems Analysis & Design on page 82 that has not been previously answered. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Should all problems be answered, submit information on websites found in the reading assignment. Groupwork: Write a statement of work for your groupwork Project Document. The statement of work should be in general terms and include a written narrative giving the activity a name, objectives to be achieved by the activity, when the activity begins and ends, major milestones during the activity with associated results or deliverables, how each deliverable will be measured to determine success or failure of the associated milestone, and written reports that will be generated during the activity. Save the statement of work for consolidation in the final document to be submitted during week eight. Individual Project: Write and submit a detailed description of the information system chosen for the Information Systems Plan. Include the system name, type of system, key system benefits, along with interrelations and interdependencies with other systems. If there is an existing system to be replaced or upgraded, provide a description of the replacement or upgrade and the associated supporting technology. Submit the information system description along with a document outline for the Information Systems Plan to the virtual classroom for grading and peer review. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 81 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 3: Requirements Analysis Lecture: Read the lecture on "Technology Connectors". Reading Assignment: Systems Analysis & Design Chapters 4, 5 Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 113 or 144 that has not been answered yet. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Homework Problem: Choose one problem from Systems Analysis & Design on page 114 or 145 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Groupwork: Write a work breakdown structure statement for your groupwork Project Document. The work breakdown structure should define the hierarchy of activity tasks and associated work packages and include a structure showing tasks with associated subtasks. Save the work breakdown structure statement for consolidation in the final document to be submitted during week eight. Individual Project: Conduct and document a 'needs analysis' for the Information Systems Plan. Include a description of the system organizational environment, stakeholders, users, levels of management served, and the organizational culture for the system. Also include how the analyst will interface with the organization and the role of the analyst in system development. Provide details on activities, methodologies, and techniques to be used in the analysis and design of the system along with planned use of CASE tools. Include the justification for CASE tool use. Post the project material to the virtual classroom for grading and peer review. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 113 or 144 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 4: Systems Analysis Methods Lecture: Read the lecture on "System Requirement Viewpoints" Reading Assignment: Systems Analysis & Design Chapter 6, 7 Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 180 or 226 that has not been answered yet. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Homework Problem: Choose one problem from Systems Analysis & Design on page 181 or 226 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Groupwork: Write an organizational structure for your groupwork Project Document. Present the structure for the activity. Show the functional responsibilities of individuals conducting the activity and reporting relationships between individuals. Submit the organizational structure for consolidation in the final document to be submitted during week eight. Individual Project: Conduct and document a feasibility analysis for the Information Systems Plan. Include operational, technical, and economic feasibility. Provide system objectives, organizational objectives, and how system and organizational objectives are aligned. Also include necessary technology resources to support the system with associated approaches and feasibility of procuring these resources. Provide an overview of the costs for the resources and activities and the associated economic feasibility of these. Make recommendations on the feasibility of the project. Post the project material to the virtual classroom for peer review and grading. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 180 or 225 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 5: Data Analysis Lecture: Read the lecture on "Estimating Software Costs". Reading Assignment: Systems Analysis & Design Chapter 8. Search the internet for websites on data analysis. Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 268 that has not been answered yet. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Should all questions be answered, submit information on websites found in the reading assignment. Homework Problem: Choose one problem from Systems Analysis & Design on page 268 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Should all problems be answered, submit information on websites found in the reading assignment. Groupwork: Develop a schedule for your groupwork Project Document. Include the tasks, subtasks, and activities shown on the work breakdown structure as they relate to milestones shown in the statement of work. Identify the time required to complete the tasks, subtasks, and activities. Show the sequence of tasks, subtasks, and activities and how they relate to each other including dependencies and precedence relationships. Identify the critical path for the schedule. Save the schedule for consolidation in the final document to be submitted during week eight. Individual Project: Document and submit a ‘data analysis’ giving an overview of the system data. Show how various data relates to the system organizational environment, users, levels of management served, and the organizational culture for the system. Provide a narrative for overall data flow, elements, structure, and data stores. Illustrate the narrative with a context level diagram of the system showing entity relationships. Post the project material to the virtual classroom for peer review and grading. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 268 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 6: Process Analysis Lecture: Read the lecture on "System Analysis Flow Diagram Methods" Reading Assignment: Systems Analysis & Design Chapter 9. Search the internet for websites on process analysis. Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 309 that has not been answered yet. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Should all questions be answered, submit information on websites found in the reading assignment. Homework Problem: Choose one problem from Systems Analysis & Design on page 310 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Should all problems be answered, submit information on websites found in the reading assignment. Groupwork: Define resources and resource loading for your groupwork Project Document. Show resources required by each task, subtask, or activity and how resources will be allocated. Provide a time-cost model for expenditure of funds. Save the resource statement for consolidation in the final document to be submitted during week eight. Individual Project: Conduct and develop a ‘process analysis’ for the Information Systems Plan. Provide a narrative of system processes with associated data and data flow. Decompose the context level diagram of the system submitted in an earlier assignment into a data flow diagram showing processes, associated data, and data stores. Post the project material to the virtual classroom for peer review and grading. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 309 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 7: Financial Analysis Lecture: Read the lecture on Structured Analysis Concepts Reading Assignment: Systems Analysis & Design Chapter 10. Search the internet for websites on financial analysis. Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 350 that has not been answered yet. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Homework Problem: Choose one problem from Systems Analysis & Design on page 351 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Should all problems be answered, submit information on websites found in the reading assignment. Groupwork: Write a control statement for your groupwork Project Document. Indicate how and when the activity results (deliverables) will be measured, timing and content of graphic and written reports, and action to be taken for deviations in the planned schedule and resource loading. Save the control statement for consolidation in the final document to be submitted during week eight. Individual Project: Provide a financial analysis for the Information System Plan. Include an estimate of time and resources (e.g. facilities, technology, vendor and employee expenses, etc.) with associated cost. Also, include a break-even analysis, cash flow analysis, and present value analysis. Provide a narrative on methods to be used for control of project activities and costs. Illustrate the material with charts and graphs. Post the project material to the virtual classroom for peer for peer review and grading. Quiz: Submit a weekly quiz on learning objectives to the instructor for grading and feedback. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 350 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom. Week 8: Object Oriented Analysis Lecture: Read the lecture on Object Oriented and Structured Analysis Comparison Reading Assignment: Systems Analysis & Design Chapter 18. Search the internet for websites on object oriented analysis. Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 700 that has not been answered yet. Develop a 'one paragraph' answer to the question and submit it to the classroom. Respond to at least one weekly discussion question answer (other than your own) in the classroom. Homework Problem: Choose one problem from Systems Analysis & Design on page 701 that has not been answered yet. Develop a 'one paragraph' solution for the problem including examples and submit it to the classroom. Respond to at least one weekly problem solution (other than your own) in the classroom. Should all problems be answered, submit information on websites found in the reading assignment. Groupwork: Consolidate material from previous assignments into one groupwork Project Document. Include the names of participants, course, date, document title, statement of work, work breakdown structure, schedule, organizational structure, resource allocation, and control information. Include a table of contents that indicates the location of the previous assignments in the document. Submit the completed groupwork Project Document to the classroom for peer review and grading. Individual Project: Consolidate the previous weekly project assignments into an Information Systems Plan document. Include a title page with student, course and system name. Also include the system description along with needs, feasibility, data, process, and financial analysis material. Provide a table of contents that indicates the location of the previous assignments in the document. Formalize the document and submit it to the classroom for peer review. Final Examination: Take the final exam supplied by the instructor to your proctor. Student Opinion Survey: Complete the Student Opinion Survey form at the Park College Distance Education web page. Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. Confirm that the final exam has been taken with a proctor and the Student Opinion Survey form has been completed. The paragraph may include topics that are key points, particularly useful items, or any other information that will be beneficial to the class. Incorporate at least one key term from Systems Analysis & Design on page 699 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Grading:
General Grading Policy: Grades will be given by accumulation of points during the eight weeks of the course. Points are accumulated by completing and submitting assignments as follows: IS315 - Assignment Point Schedule Assignment Due Date Points per Week Total Points In Course Submitting an answer to a discussion question - and responding to a submitted discussion question (other than your own) By end of the week (weeks 1-8) 1 8 Submitting answers to a homework problem - and responding to a submitted homework problem (other than your own) By end of the week (weeks 1-8) 2 16 Submitting a project assignment Project Final Document By end of the week (weeks 2-7) By end of the week (week 8) 2 8 12 8 Submitting answers to a quiz By end of the week (weeks 1-7) 2 14 Submitting a lessons learned assignment By end of the week (weeks 1-8) 1 8 Submitting a groupwork assignment By end of the week (week 8) 8 8 Completing a proctored final exam By end of the week (week 8) 26 26 Total 100 Students will be able to track their points throughout the course through use of the classroom grade book. Points for discussion, homework, project, quiz, lessons learned, and groupwork will be shown each week. Submission of Late Work: Each week's work must be completed by the end of that week (Midnight MST on Sunday). Assignments received after this time will receive a 50% reduction in points. Assignments received more than a week late will not receive any credit. Proctored Final Examination: A final proctored examination will be taken in a proctored testing environment during the 8th week at one of the Park University sites around the country or at an approved alternative location.  For proctored examinations, photo identification is required at the time of the test.  Guidelines for selecting an acceptable proctor can be found on the Park University Website. Other Information on proctored exams: It will be the responsibility of the student to arrange for a proctor, by the 6th week of the term, who is accepted and approved by the course instructor.   Approval of proctors is the discretion of the Online instructor.   A proctor request form will be made available to you during the first week of class so that you can send your requested proctor to your instructor for approval.   Failure to take a final proctored exam will result in an automatic "F" grade for the course. Course Grading Scale IS316 - Points To Grade Schedule Grade Points Percent A 90 points or higher 90 to 100% B 80 to 89 points 80 to 89 % C 70 to 79 points 70 to 79 % D 60 to 69 points 60 to 69 % F 59 or fewer points 59 or less %

Late Submission of Course Materials:
Each week's work must be completed by the end of that week (Midnight MST on Sunday). Assignments received after this time will receive a 50% reduction in points. Assignments received more than a week late will not receive any credit.

Classroom Rules of Conduct:
General E-mail: When sending e-mail other than assignments, you must identify yourself fully by name and class in the subject line of all e-mail sent to me and/or other members of our class. Response Policy: I will check my e-mail frequently and respond to course-related questions within 24-48 hours (unless I notify you previously that I will be unavailable). File Attachments: When files are sent attached to an email, the files should be in Microsoft Word RTF file formats. Weekly Submitted Material: Each week's work must be completed and submitted to the online classroom by the end of that week (Midnight MST on Sunday). Assignments received after this time will receive a 50% reduction in your score. Assignments received more than a week late will not receive any credit. Online Communication: All your Online communications need to be composed with fairness, honesty and tact. Spelling and grammar are very important in an Online course. What you put into an Online course reflects on your level of professionalism. Use of American Standard English with correct grammar, punctuation, sentence structure, and spelling is expected for all material submitted to the online class classroom. Here are a couple of references that discuss writing online: http://goto.intwg.com/ and netiquette , http://www.albion.com/netiquette/corerules.html. Other Course Policies: Students are responsible for clicking on the link below and thoroughly reading each Online course policy.  If you have questions about any of these policies, please contact your instructor for clarification.

Course Topic/Dates/Assignments:
For those in this course, the next weeks will be filled with material of critical importance in analysis and design of information systems. The course introduces various philosophies, terminology, and techniques used for the system development life cycle. Topics will include fundamentals of system analysis, information requirement analysis, and the analysis process. The project for this course gives practical experience in system analysis and design by developing a project plan for analysis and design of a system including a system description, needs analysis, system feasibility, activity planning and control, scheduling, analysis tools, along with data and process analysis. The Visible Analyst 7.5 CASE tools will be used for project work. You will participate in online discussions, homework preparation, peer response of other's materials, summarizing 'lessons learned', and development of an individual project during the course. These will reinforce and expand readings in the text, Systems Analysis and Design. Each week we will focus on a different segment of the material using the reading, discussion, homework, and a 'lessons learned' paragraph to optimize the learning experience

Academic Honesty:
Academic integrity is the foundation of the academic community. Because each student has the primary responsibility for being academically honest, students are advised to read and understand all sections of this policy relating to standards of conduct and academic life.   Park University 2006-2007 Undergraduate Catalog Page 87-89

Plagiarism:
Plagiarism involves the use of quotations without quotation marks, the use of quotations without indication of the source, the use of another's idea without acknowledging the source, the submission of a paper, laboratory report, project, or class assignment (any portion of such) prepared by another person, or incorrect paraphrasing. Park University 2006-2007 Undergraduate Catalog Page 87

Attendance Policy:
Instructors are required to maintain attendance records and to report absences via the online attendance reporting system.

  1. The instructor may excuse absences for valid reasons, but missed work must be made up within the semester/term of enrollment.
  2. Work missed through unexcused absences must also be made up within the semester/term of enrollment, but unexcused absences may carry further penalties.
  3. In the event of two consecutive weeks of unexcused absences in a semester/term of enrollment, the student will be administratively withdrawn, resulting in a grade of "W".
  4. A "Contract for Incomplete" will not be issued to a student who has unexcused or excessive absences recorded for a course.
  5. Students receiving Military Tuition Assistance or Veterans Administration educational benefits must not exceed three unexcused absences in the semester/term of enrollment. Excessive absences will be reported to the appropriate agency and may result in a monetary penalty to the student.
  6. Report of a "F" grade (attendance or academic) resulting from excessive absence for those students who are receiving financial assistance from agencies not mentioned in item 5 above will be reported to the appropriate agency.
ONLINE NOTE: An attendance report of "P" (present) will be recorded for students who have logged in to the Online classroom at least once during each week of the term. Recording of attendance is not equivalent to participation. Participation grades will be assigned by each instructor according to the criteria in the Grading Policy section of the syllabus.

Park University 2006-2007 Undergraduate Catalog Page 89-90

Disability Guidelines:
Park University is committed to meeting the needs of all students that meet the criteria for special assistance. These guidelines are designed to supply directions to students concerning the information necessary to accomplish this goal. It is Park University's policy to comply fully with federal and state law, including Section 504 of the Rehabilitation Act of 1973 and the Americans with Disabilities Act of 1990, regarding students with disabilities. In the case of any inconsistency between these guidelines and federal and/or state law, the provisions of the law will apply. Additional information concerning Park University's policies and procedures related to disability can be found on the Park University web page: http://www.park.edu/disability .

Additional Information:

INSTRUCTOR INFORMATION:


Fred Kellenberger
Fred.Kellenberger@pirate.park.edu
Phone: Information Systems Plan



Fred Kellenberger has an AA in Mathematics, BS in Mathematics, MS in Computer Science, and MS in Management. Mr. Kellenberger has worked as a programmer, systems analyst, and MIS manager. He has taught a variety of computer science and information technology courses. His area of expertise is database, programming, and web design. Mr. Kellenberger likes to travel, hike and read.His telephone number is (760)717-8022 and his e-mail address is fred.kellenberger@park.edu.




Rubric

CompetencyExceeds Expectation (3)Meets Expectation (2)Does Not Meet Expectation (1)No Evidence (0)
Synthesis                                                                                                                                                                                                                                                  
Outcomes
8                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
The artifact demonstrates student ability to synthesize various components of an information system into a cohesive statement describing system characteristics using a computer aided software engineering (CASE) tool. Synthesis is performed with 0 rework and  0 errors to show consistency and design compatibility between: (1) needs analysis (2) data analysis (3) process analysis. The artifact demonstrates student ability to synthesize various components of an information system into a cohesive statement describing system characteristics using a computer aided software engineering (CASE) tool. Synthesis is performed with 1 rework and 0 errors to show consistency and design compatibility between: (1) needs analysis (2) data analysis (3) process analysis. The artifact demonstrates student ability to synthesize various components of an information system into a cohesive statement describing system characteristics using a computer aided software engineering (CASE) tool. Synthesis is performed with more than 1 rework and 1 or more errors to show consistency and design compatibility between: (1) needs analysis (2) data analysis (3) process analysis. The artifact demonstrates student ability to synthesize various components of an information system into a cohesive statement describing system characteristics using a computer aided software engineering (CASE) tool. Synthesis is not performed to show consistency and design compatibility between: (1) needs analysis (2) data analysis (3) process analysis. 
Analysis                                                                                                                                                                                                                                                   
Outcomes
1,2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  
The artifact demonstrates student ability to conduct and document a system needs analysis using a prescribed methodology and a computer aided software engineering (CASE) tool. The needs analysis will be documented with 0 rework and 0 errors and include (1) system requirements (2) role of the analyst in system development and (3) methodology and tools to be used. The artifact demonstrates student ability to conduct and document a system needs analysis using a prescribed methodology and a computer aided software engineering (CASE) tool. The needs analysis will be documented with 1 rework and 0 errors and include (1) system requirements (2) role of the analyst in system development and (3) methodology and tools to be used. The artifact demonstrates student ability to conduct and document a system needs analysis using a prescribed methodology and a computer aided software engineering (CASE) tool. The needs analysis will be documented with more than one rework and 1 or more errors and include (1) system requirements (2) role of the analyst in system development and (3) methodology and tools to be used. The artifact demonstrates student ability to conduct and document a system needs analysis using a prescribed methodology and a computer aided software engineering (CASE) tool. The needs analysis  is not documented to include all categories: (1) system requirements (2) role of the analyst in system development and (3) methodology and tools to be used. 
Evaluation                                                                                                                                                                                                                                                 
Outcomes
3                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
The artifact demonstrates student ability to evaluate analysis of system features as they relate to system architectural design alternatives. System features are shown with 0 rework and 0 errors describing: (1) system interfaces (2) processes the system must perform (3) process definition with input and output and (4) data stores. The artifact demonstrates student ability to evaluate analysis of system features as they relate to system architectural design alternatives. System features are shown with 0 rework and 0 errors describing: (1) system interfaces (2) processes the system must perform (3) process definition with input and output and (4) data stores. The artifact demonstrates student ability to evaluate analysis of system features as they relate to system architectural design alternatives. System features are shown with moThe artifact demonstrates student ability to evaluate analysis of system features as they relate to system architectural design alternatives. System features are shown with 1 rework and 0 errors describing: (1) system interfaces (2) processes the system must perform (3) process definition with input and output and (4) data stores.re than 1 rework and 1 or more errors describing: (1) system interfaces (2) processes the system must perform (3) process definition with input and output and (4) data stores. The artifact demonstrates student ability to evaluate analysis of system features as they relate to system architectural design alternatives. System features are shown with moThe artifact demonstrates student ability to evaluate analysis of system features as they relate to system architectural design alternatives. System features are shown with 1 rework and 0 errors describing: (1) system interfaces (2) processes the system must perform (3) process definition with input and output and (4) data stores.re than 1 rework and 1 or more errors describing: (1) system interfaces (2) processes the system must perform (3) process definition with input and output and (4) data stores. 
Terminology                                                                                                                                                                                                                                                
Outcomes
4                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
The artifact demonstrates student ability to analyze and document feasibility of a system with 0 rework and 0 errors in terms of: (1) operational, (2) technical, and (3) economic feasibility. The artifact demonstrates student ability to analyze and document feasibility of a system with 1 rework and 0 errors in terms of: (1) operational, (2) technical, and (3) economic feasibility. The artifact demonstrates student ability to analyze and document feasibility of a system with more than 1 rework and 1 or more errors in terms of: (1) operational, (2) technical, and (3) economic feasibility. The artifact demonstrates student ability to analyze and document feasibility of a system. Feasibility is not described for all categories: (1) operational, (2) technical, and (3) economic. 
Concepts                                                                                                                                                                                                                                                   
Outcomes
5,6                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  
The artifact demonstrates student ability to perform and document a financial analysis for a system. Results are documented with 0 rework and  0 errors for: (1) break even analysis (2) cash flow analysis (3) and present value analysis. The artifact demonstrates student ability to perform and document a financial analysis for a system. Results are documented with 1 rework and  0 errors for: (1) break even analysis (2) cash flow analysis (3) and present value analysis. The artifact demonstrates student ability to perform and document a financial analysis for a system. Results are documented with more than 1 rework and   or more errors for: (1) break even analysis (2) cash flow analysis (3) and present value analysis. The artifact demonstrates student ability to perform and document a financial analysis for a system. Results are not documented for all categories: (1) break even analysis (2) cash flow analysis (3) and present value analysis. 
Application                                                                                                                                                                                                                                                
Outcomes
9                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
The artifact demonstrates student ability to perform a process analysis and document the results. Results are demonstrated with 0 rework and 0 errors in (1) process flow narrative (2) context diagrams and (3) data flow diagram decomposition. The artifact demonstrates student ability to perform a process analysis and document the results. Results are demonstrated with 1 rework and 0 errors in (1) process flow narrative (2) context diagrams and (3) data flow diagram decomposition. The artifact demonstrates student ability to perfThe artifact demonstrates student ability to perform a process analysis and document the results. Results are demonstrated with 1 rework and 0 errors in (1) process flow narrative (2) context diagrams and (3) data flow diagram decomposition.orm a process analysis and document the results. Results are demonstrated with more than 1 rework and 1 or more errors in (1) process flow narrative (2) context diagrams and (3) data flow diagram decomposition The artifact demonstrates student ability to perform a process analysis and document the results. Results  are not demonstrated in all categories: (1) process flow narrative (2) context diagrams and (3) data flow diagram decomposition. 
Whole Artifact                                                                                                                                                                                                                                             
Outcomes
10                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   
The artifact as a whole demonstrates the ability to effectively communicate a system analysis and design to system stakeholders. Systems analysis and design is communicated  with 0 rework and 0 errors through: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. The artifact as a whole demonstrates the ability to effectively communicate a system analysis and design to system stakeholders. Systems analysis and design is communicated  with 1 rework and 0 errors through: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. The artifact as a whole demonstrates the ability to effectively communicate a system analysis and design to system stakeholders. Systems analysis and design is communicated  with more than 1 rework and 1 or more errors through: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis The artifact as a whole demonstrates the ability to effectively communicate a system analysis and design to system stakeholders. Systems analysis and design is not communicated in all categories: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. 
Component                                                                                                                                                                                                                                                  
Outcomes
7                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
Various components of the artifact demonstrate the ability to effectively analyze and document a system from different perspectives. The system is analyzed and documented with 0 rework and 0 errors using: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. Various components of the artifact demonstrate the ability to effectively analyze and document a system from different perspectives. The system is analyzed and documented with 1 rework and 0 errors using: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. Various components of the artifact demonstrate the ability to effectively analyze and document a system from different perspectives. The system is analyzed and documented with more than 1 rework and 1 or more errors using: (1) needs, (2) feasibility, (3) data, (4) process, and Various components of the artifact demonstrate the ability to effectively analyze and document a system from different perspectives. The system is analyzed and documented with more than 1 rework and 1 or more errors using: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. Various components of the artifact demonstrate the ability to effectively analyze and document a system from different perspectives. The system is not analyzed and documented in all categories: (1) needs, (2) feasibility, (3) data, (4) process, and (5) financial analysis. 

Copyright:

This material is protected by copyright and can not be reused without author permission.

Last Updated:1/9/2007 2:22:42 PM