Syllabus Entrance
Printer Friendly
Email Syllabus

IS 316 Computer Systems Analysis and Design II
Burns, James D.


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 316 Computer Systems Analysis and Design II

Semester

U1T 2006 DLA

Faculty

Burns, James D.

Title

Senior Instructor

Degrees/Certificates

MS Systems Engineering Naval PostGraduate School
BS University of South Carolina

Office Location

Online

Office Hours

Asynchronous

Daytime Phone

410 294 7725

Other Phone

410 569 6658

E-Mail

james.burns@pirate.park.edu

calif1610@comcast.net

Semester Dates

5 June 2006 - 30 July 2006

Class Days

TBA

Class Time

TBA

Credit Hours

3


Textbook:
Systems Analysis & Design, (6th Edition, Prentice Hall, 2004, Bundled with: Visible Analyst Workbench 7.5 CD)

Author: Kendall & Kendall
ISBN: 0131188798

Textbooks can be purchased though the MBS bookstore

Textbooks can be purchased though the Parkville Bookstore


Course Description:
Continuation of IS315. The student will continue to study the concepts and  methods used in a system development life cycle.  In addition, the student  will gain practical experience by working on various projects.  The student  will use a CASE tool for his/her project work. Prerequisite: IS315. 3:0:3

Learning Outcomes:
  Core Learning Outcomes

  1. Distinguish logical versus physical models and translate logical process and data models into physical design models using design/ CASE software.
  2. Evaluate and make architectural design decisions given a problem scenario: Client Server, Centralized versus Decentralized, Database and distribution of data, User and system interface alternatives (inputs/outputs)
  3. Explain design principles for Input/Output with regard to human interaction and user acceptability.
  4. Explain advantages and disadvantages of data storage options (i.e. Relational Database, Object Database, Conventional Files and Data Warehouse)
  5. Practice key concepts of analysis and design as well as advance techniques such as JAD, Prototyping, USE CASES and/or other OOA/OOD techniques.
  6. Evaluate strengths/weaknesses and applicable roles of several strategies/methodologies for design of information systems including Model Driven, RAD, Agile, OO development, and Prototyping.
  7. Apply Quality Assurance steps that can be taken in all phases of development to ensure a quality product and user acceptance.
  8. 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 final exam which counts for 20% of the grade. Questions on the final exam will be developed to test at least eight of the ten course core objectives.

Link to Class Rubric

Class Assessment:
Final examination, weekly quizzes, group and individual project, weekly assignments (discussion question, homework, lessons learned)

Grading:
Grades will be assigned by accumulation of points during the eight weeks of the course.  Grades are calculated based on the value of each assignment. For example, if you receive a 93% score for the Week 2 Discussion Question, you will see the number 15.81 posted in the eCollege grade area for that assignment. This number is the 93% multiplied by the value for that specific assignment (in this case, the Week 2 Discussion Question is worth a possible 17 points). Points are accumulated by completing and submitting assignments as follows:

IS316 - Assignment Point Schedule

Assignment (Each Week)
Due Date
Total Points In Course

Submitting an answer to a discussion question - and providing peer review for a submitted discussion question (other than your own)
By end of the week
(Weeks 1-8) 140
Submitting answers to a homework problem - and providing peer review for a submitted homework problem (other than your own)
By end of the week
(weeks 1-8)
160
Submitting a project assignment and providing peer review for at least one of your colleagues
By end of the week
(Weeks 1-8)
200
Submitting answers to a quiz
By end of the week
(Weeks 1-7)
100
Submitting a lessons learned assignment (no peer review is required for this)
By end of the week
(Weeks 1-8)
100
Submitting a groupwork assignment (to be sent to me from the Group Leader only)
By end of the week
(Weeks 1- 8)
100
Completing a proctored final exam (single final exam--not a weekly assignment. By end of week 8 200

Total  1000

Late Submission of Course Materials:
Submission of Late Work:

Each week's work must be completed by the end of that week (Midnight, Mountain time on Sunday) to receive full credit. Assignments received after this time will receive a 20% reduction in points unless there was an genuine emergency that prevented your timely posting.  

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.  

For example, your subject line would read as follows (without the quotes): "IS316: Albert Johnson, Week 1 project draft"

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 Office-compatible formats (Word .DOC, Excel .XLS, PowerPoint .PPT) or .RTF (Rich Text Format) file formats. You may also send attachments in Adobe .PDF (Portable Document File) format.
Weekly Submitted Material: Each week's work must be completed and submitted to the online classroom by the end of that week (Midnight, Mountain time on Sunday). Assignments received after this time will receive a 20% reduction in your score unless a genuine emergency prevented you from posting in a timely fashion. You must contact me individually before any waiver of lateness penalties will be considered.

Assignment Posting Deadline: Our term posting deadline for this term will be Wednesday, March 1, 2006 at midnight (Mountain time). All assignments (EXCEPT the final exam) must be posted on the eCollege threads for credit to be awarded. Any assignments posted after the above deadline will not be added to the grade book. Please consult the "Checklist" (in the Course Home section) to verify posting dates for full credit and also this term deadline.

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.

Course Topic/Dates/Assignments:
Week 1: Systems Analysis & Design Review

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, 7, 8. Search the internet for information on CASE software.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 23, 226, or 268 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. Should all questions be answered, submit information on found in the reading assignment Internet search.

Homework Problem: Choose one problem from Systems Analysis & Design on page 226 or 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 found in the reading assignment Internet search.

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 System Risk Analysis for a system with which you are familiar. The document will include a detailed system description along with risk analysis on system concepts, feasibility (technical, environmental, and financial), system and data security, development methodology, user acceptance, and system implementation. You should choose a simple system from your personal life or one at work. The system can be real or hypothetical. 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 a System Proposal for an existing or hypothetical information system. Each week you will develop parts of that plan. Weekly assignments include a table of contents, executive summary, process functions, use of CASE tools, data flow diagrams, data description, sample input/output screens, testing, maintenance, and auditing requirements. The final individual project assignment will be to consolidate all previous assignments into one MSWord document. Care should be taken that the chosen system will provide the necessary information for all weekly assignments. 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, 225 or 268 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 2: Preparing For Course Projects

Lecture: Read the lecture on "Data Flow Diagram Relationships".

Reading Assignment: Systems Analysis & Design Chapters 9, 10. Search the internet for information on structured decision making.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 309 or 350 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. Should all questions be answered, submit information on found in the reading assignment Internet search.

Homework Problem: Choose one problem from Systems Analysis & Design on page 310 or 351 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 found in the reading assignment Internet search.

Groupwork: Write a detailed description of the system chosen for the groupwork System Risk Analysis. Include the system name, type of system, key system benefits, along with interrelations and interdependencies with other internal or external 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. Also, include a description of the system organizational environment, stakeholders, users, levels of management served, and the organizational culture for the system. Save the detailed system description 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 System Proposal. Include the system name, type of system, key system benefits, along with interrelations and interdependencies with other internal or external 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. Also, include a description of the system organizational environment, stakeholders, users, levels of management served, and the organizational culture for the system. Submit the information system description along with a Table of Contents for the System Proposal document 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 309 or 350 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 3: Designing Effective Input and Output

Lecture: Read the lecture on "System Alignment with Organizational Needs".

Reading Assignment: Systems Analysis & Design Chapters 11, 12. Search the internet for information on website design.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 389 or 428 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 found in the reading assignment Internet search.

Homework Problem: Choose one problem from Systems Analysis & Design on page 391 or 429 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 risk analysis on system concepts for the System Risk Analysis. List potential system concept risks or threats that will prohibit system success. With each risk or thread provide the relative importance to the overall system success (low, high, ciritcal), measures to mitigate the risk, and the time frame needed for risk mitigation. Include in your analysis system boundaries, system interfaces external to the organization, system interfaces internal to the organization, how the system relates to the organizational mission, organizational decisions the system must support, information processing the system will perform , as well as any other items that are key to system success. Save the risk analysis on system concepts for consolidation in the final System Risk Analysis to be submitted during week eight.

Individual Project: Define and document the functional description for the individual project information system along with plans for use of a CASE tool in development of the proposed system. Provide a narrative describing functions the system will perform. Include a definition of system boundaries, system interfaces external to the organization, system interfaces internal to the organization, how the system relates to the organizational mission, organizational decisions the system must support, and information processing the system will perform in terms of information input to the process, process definition, and information output from the process. Submit 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 389 or 428 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 4: Designing Databases

Lecture: Read the lecture on "Structured Analysis Techniques"

Reading Assignment: Systems Analysis & Design Chapter 13. Search the internet for information on data warehouses.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 484 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 found in the reading assignment Internet search.

Homework Problem: Choose one problem from Systems Analysis & Design on page 485 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 an analysis on technical, financial, and environment risk for the System Risk Analysis. List potential technical, environmental, or financial feasibility risks or threats that will prohibit system success. With each risk or thread provide the relative importance to the overall system success (low, high, ciritcal), measures to mitigate the risk, and the time frame needed for risk mitigation.
Include an analysis of system objectives, organizational objectives, how system and organizational objectives are aligned with user needs and organizational objectives, necessary technology resources to support the system with associated approaches and feasibility of procuring these resources, along with costs for the resources and activities and the associated economic feasibility of these. Include a break-even analysis, cash flow analysis, and present value analysis.  Save the analysis on technical, financial, and environment risk for consolidation in the final document to be submitted during week eight.

Individual Project: Define and document the data for the individual project information system. Develop a data dictionary showing all data for functions described in the functional description. Show data as it is related to system boundaries, system interfaces external to the organization, system interfaces internal to the organization, organizational mission, various users in the organization, and decisions the system must support. Submit 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 483 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 5: Designing User Interfaces

Lecture: Read the lecture on "Designing System Interfaces".

Reading Assignment: Systems Analysis & Design Chapter 14, 15. Search the internet for ecommerce system design.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 530 or 570 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 found in the reading assignment Internet search.

Homework Problem: Choose one problem from Systems Analysis & Design on page 530 or 571 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 risk analysis for system and data security for the System Risk Analysis. List potential system and data security risks or threats that will prohibit system success. With each risk or thread provide the relative importance to the overall system success (low, high, ciritcal), measures to mitigate the risk, and the time frame needed for risk mitigation. Include an analysis of all system functions, reliability, boundaries, interfaces external to the organization, interfaces internal to the organization, along with data backup, accuracy, timeliness, reliability, and redundancy. Save the system and data security analysis for consolidation in the final document to be submitted during week eight.

Individual Project:  Develop and submit a context level data flow diagram and the next level data flow diagram (diagram zero). Develop the data flow diagrams to show graphically information documented in the functional description, including system boundaries, system interfaces external to the organization, system interfaces internal to the organization, and information processing the system will perform in terms of input to the process, process definition, and output from the process. Also, develop the datat flow diagrams to show graphically data included in the data dictionary. Submit 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 529 or 570 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 6: Quality Assurance & Software Engineering

Lecture: Read the lecture on "System Testing Concepts"
Reading Assignment: Systems Analysis & Design Chapter 16. Search the internet for software engineering information.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 610 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 611 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 risk analysis on the development methodology for the System Risk Analysis. List potential development methodology risks or threats that will prohibit system success. With each risk or thread provide the relative importance to the overall system success (low, high, ciritcal), measures to mitigate the risk, and the time frame needed for risk mitigation. Analyze how the analyst will interface with the organization and the role of the analyst in system development. Include an analysis of activities, methodologies, support software, and techniques to be used in the analysis along with any planned use of CASE tools. Save the development methodology risk analysis for consolidation in the final document to be submitted during week eight.

Individual Project: Define and document system input, output forms, and interfaces for the individual project information system. Include sample screens, input, and output data forms, and interfaces with internal or external systems. Include the key system screens, input and output forms, and interfaces that illustrate interfaces external to the organization, system interfaces internal to the organization, relation of the system to organizational mission, and support of organizational decisions. Provide information with each key screen on the interfaces illustrated. Submit 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 610 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 7: System Implementation

Lecture: Read the lecture on "Steps To System Implementation"

Reading Assignment: Systems Analysis & Design Chapter 17. Search the internet for information on system conversion, system security, or distributed system implementation.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 650 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 found in the reading assignment Internet search.

Homework Problem: Choose one problem from Systems Analysis & Design on page 651 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 risk analysis on user acceptance of the system and system implementation for the System Risk Analysis. List potential user acceptance or system implementation risks or threats that will prohibit system success. With each risk or thread provide the relative importance to the overall system success (low, high, ciritcal), measures to mitigate the risk, and the time frame needed for risk mitigation. Include an analysis on testing, maintenance, and audting to be performed on the system, including system features for testing, maintenance, and auditing such as data validation, and editing and conversion of data from systems internal or external to the organization. Also, include testing, maintenance, and auditing to be performed during and after system development. Analyze the criteria, standards, and tracking of test, maintenance, and audit activities. Save the user acceptance and system implementation risk analysis for consolidation in the final document to be submitted during week eight.

Individual Project: Define and submit the testing, maintenance, and audting to be performed on the system. Include system features for testing, maintenance, and auditing such as data validation, and editing and conversion of data from systems internal or external to the organization. Also, include testing, maintenance, and auditing to be performed during and after system development. Describe the criteria, standards, and tracking of test, maintenance, and audit activities. Submit 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 649 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the classroom.

Week 8:  Object Oriented Analysis & Design

Lecture: Read the lecture on Object Oriented and Structured Analysis Comparison

Reading Assignment: Systems Analysis & Design Chapter 18. Search the internet for information 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. Should all questions be answered, submit information found in the reading assignment Internet search.

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 System Risk Analysis using MSWord. Assure that  the material included in the consolidated document is the latest version and has been updated in relation to  reviews from individuals, peers, or the instructor. Include in the document the names of participants, course, date, document title, detailed system description along with risk analysis on system concepts, feasibility (technical, environmental, and financial), system and data security, development methodology, user acceptance, and system implementation. Also, 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 System Proposal document. Include a title page with student, course and system name. Also include a table of contents, executive summary, process functions, use of CASE tools, data flow diagrams, data description, sample input/output screens, testing, maintenance, and auditing requirements. Formalize the project material to be  with consistent format and content in one MSWord document. Submit the project material to the virtual classroom for peer review and grading.

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.

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 2005-2006 Undergraduate Catalog Page 85-87

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 2005-2006 Undergraduate Catalog Page 85-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 "WH".
  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 2005-2006 Undergraduate Catalog Page 89

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 .



Rubric

CompetencyExceeds Expectation (3)Meets Expectation (2)Does Not Meet Expectation (1)No Evidence (0)
Synthesis                                                                                                                                              
Outcomes
2,7                                                
The artifact demonstrates the student ability to creatively apply prior knowledge and skills to produce an original narrative. Synthesis is demonstrated by correctly answering 2 out of 2 questions regarding: (a) managing changes to system requirements (b) comparison of a system analysis and design methodology to an information system. The artifact demonstrates the student ability to creatively apply prior knowledge and skills to produce an original narrative. Synthesis is demonstrated by correctly answering 1 out of 2 questions regarding: (a) managing changes to system requirements (b) comparison of a system analysis and design methodology to an information system. The artifact demonstrates the student ability to creatively apply prior knowledge and skills to produce an original narrative. Synthesis is demonstrated by correctly answering 0 out of 2 questions regarding: (a) managing changes to system requirements (b) comparison of a system analysis and design methodology to an information system. The artifact demonstrates the student ability to creatively apply prior knowledge and skills to produce an original narrative. Synthesis is not demonstrated by answering any regarding: (a) managing changes to system requirements (b) comparison of a system analysis and design methodology to an information system. 
Analysis                                                                                                                                               
Outcomes
1,2                                                
The artifact demonstrates the student ability to differentiate information in an organizational structure. Analysis is demonstrated by correctly answering 2 out of 2 questions regarding: (a) methods of showing results of analyzing requirement dependencies (b) example showing results of analyzing requirements dependencies The artifact demonstrates the student ability to differentiate information in an organizational structure. Analysis is demonstrated by correctly answering 1 out of 2 questions regarding: (a) methods of showing results of analyzing requirement dependencies (b) example showing results of analyzing requirements dependencies The artifact demonstrates the student ability to differentiate information in an organizational structure. Analysis is demonstrated by correctly answering 0 out of 2 questions regarding: (a) methods of showing results of analyzing requirement dependencies (b) example showing results of analyzing requirements dependencies The artifact demonstrates the student ability to differentiate information in an organizational structure. Analysis is not demonstrated by not answering any  questions regarding: (a) methods of showing results of analyzing requirement dependencies (b) example showing results of analyzing requirements dependencies 
Evaluation                                                                                                                                             
Outcomes
2,3                                                
The artifact demonstrates the student ability to judge relative value of information based on prior knowledge. Evaluation is demonstrated by correctly answering 2 out of 2 questions regarding: (a) reasons for involving individuals with various view points in system analysis and design (b) benefits of using a system analysis and design methodology in system maintenance The artifact demonstrates the student ability to judge relative value of information based on prior knowledge. Evaluation is demonstrated by correctly answering 1 out of 2 questions regarding: (a) reasons for involving individuals with various view points in system analysis and design (b) benefits of using a system analysis and design methodology in system maintenance The artifact demonstrates the student ability to judge relative value of information based on prior knowledge. Evaluation is demonstrated by correctly answering 0 out of 2 questions regarding: (a) reasons for involving individuals with various view points in system analysis and design (b) benefits of using a system analysis and design methodology in system maintenance The artifact demonstrates the student ability to judge relative value of information based on prior knowledge. Evaluation is not demonstrated by correctly answering questions regarding: (a) reasons for involving individuals with various view points in system analysis and design (b) benefits of using a system analysis and design methodology in system maintenance 
Terminology                                                                                                                                            
Outcomes
1,5                                                
The artifact demonstrates the student ability to proficiently use terminology related to specific course area. Use of terminology is demonstrated by correctly answering 2 out of 2 questions regarding (a) automation of systems analysis and design processes (b) characteristics of a systems analysis methodology. The artifact demonstrates the student ability to proficiently use terminology related to specific course area. Use of terminology is demonstrated by correctly answering 1 out of 2 questions regarding (a) automation of systems analysis and design processes (b) characteristics of a systems analysis methodology. The artifact demonstrates the student ability to proficiently use terminology related to specific course area. Use of terminology is demonstrated by correctly answering 0 out of 2 questions regarding (a) automation of systems analysis and design processes (b) characteristics of a systems analysis methodology. The artifact demonstrates the student ability to proficiently use terminology related to specific course area. Use of terminology is not demonstrated by answering any questions regarding (a) automation of systems analysis and design processes (b) characteristics of a systems analysis methodology. 
Concepts                                                                                                                                               
Outcomes
4,7                                                
The artifact demonstrates student ability to recognize and articulate concepts relevant to core course topics. Recognition and articulation is demonstrated by correctly answering 2 out of 2 questions regarding: (a) failures in implementing a system    (b) common issues with data security The artifact demonstrates student ability to recognize and articulate concepts relevant to core course topics. Recognition and articulation is demonstrated by correctly answering 1 out of 2 questions regarding: (a) failures in implementing a system    (b) common issues with data security The artifact demonstrates student ability to recognize and articulate concepts relevant to core course topics. Recognition and articulation is demonstrated by correctly answering 0 out of 2 questions regarding: (a) failures in implementing a system    (b) common issues with data security The artifact demonstrates student ability to recognize and articulate concepts relevant to core course topics. Recognition and articulation is not demonstrated by correctly answering any questions regarding: (a) failures in implementing a system    (b) common issues with data security 
Application                                                                                                                                            
Outcomes
9                                                  
The artifact demonstrates student ability to use principles as they relate to core course topics. Application is demonstrated by correctly answering 2 out of 2 questions regarding: (a) use of multiple models in system analysis and design (b) system design to support maintenance. The artifact demonstrates student ability to use principles as they relate to core course topics. Application is demonstrated by correctly answering 1 out of 2 questions regarding: (a) use of multiple models in system analysis and design (b) system design to support maintenance The artifact demonstrates student ability to use principles as they relate to core course topics. Application is demonstrated by correctly answering 0 out of 2 questions regarding: (a) use of multiple models in system analysis and design (b) system design to support maintenance The artifact demonstrates student ability to use principles as they relate to core course topics. Application is not demonstrated by answering  questions regarding: (a) use of multiple models in system analysis and design (b) system design to support maintenance 
Whole Artifact                                                                                                                                         
Outcomes
6                                                  
The artifact demonstrates student ability to use accepted methods and standards in performing system analysis and design activities. Ability is demonstrated by correctly answering 2 out of 2 questions regarding: (a) computer aided software engineering (CASE) tool functions (b) key activities in system analysis and design The artifact demonstrates student ability to use accepted methods and standards in performing system analysis and design activities. Ability is demonstrated by correctly answering 1 out of 2 questions regarding: (a) computer aided software engineering (CASE) tool functions (b) key activities in system analysis and design The artifact demonstrates student ability to use accepted methods and standards in performing system analysis and design activities. Ability is demonstrated by correctly answering 0 out of 2 questions regarding: (a) computer aided software engineering (CASE) tool functions (b) key activities in system analysis and design The artifact demonstrates student ability to use accepted methods and standards in performing system analysis and design activities. Ability is not demonstrated by answering any questions regarding: (a) computer aided software engineering (CASE) tool functions (b) key activities in system analysis and design 
Component                                                                                                                                              
Outcomes
6,7                                                
The artifact demonstrates student ability to use accepted methods and standards in performing specific system analysis and design activities. Ability is demonstrated by correctly answering 2 out of 2 questions regarding: (a) system analysis activities supported by computer aided software engineering (CASE) tools (b) testing activities in phases of the system development life cycle The artifact demonstrates student ability to use accepted methods and standards in performing specific system analysis and design activities. Ability is demonstrated by correctly answering 1 out of 2 questions regarding: (a) system analysis activities supported by computer aided software engineering (CASE) tools (b) testing activities in phases of the system development life cycle The artifact demonstrates student ability to use accepted methods and standards in performing specific system analysis and design activities. Ability is demonstrated by correctly answering 0 out of 2 questions regarding: (a) system analysis activities supported by computer aided software engineering (CASE) tools (b) testing activities in phases of the system development life cycle The artifact demonstrates student ability to use accepted methods and standards in performing specific system analysis and design activities. Ability is not demonstrated answering any questions regarding: (a) system analysis activities supported by computer aided software engineering (CASE) tools (b) testing activities in phases of the system development life cycle 

Copyright:

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

Last Updated:5/20/2006 7:06:15 PM