Syllabus Entrance
Printer Friendly
Email Syllabus

IS 315 Computer Sys Analysis & Design I
McGinnis, Jacob


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 Sys Analysis & Design I

Semester

S1J 2009 DN

Faculty

McGinnis, Jacob

Title

Adjunct Faculty

Degrees/Certificates

BS Electricity Electronics
MS Industrial Management

Other Phone

816-665-5068 cell

E-Mail

jacob.mcginnis@park.edu

chipmckcmo@aol.com

Semester Dates

Jan 12 - Mar 8 2009

Class Days

Monday

Class Time

5:30 - 9:50 PM

Prerequisites

Suggest IS 205

Credit Hours

3


Textbook:

Kendall & Kendall Systems Analysis & Design, 7th Edition
 
Prentice Hall
 
ISBN 0-13-224085-8

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/.


Course Description:
IS315 Computer Systems Analysis & Design I: 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. 3:0:3 Prerequisite: IS205.

Educational Philosophy:
The facilitator’s educational philosophy is one of interactiveness based on lectures, readings, quizzes, dialogues, examinations, internet, videos, web sites and writings. The facilitator will engage each student in an appropriate manner and will determine that learning is accomplished by each student.

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:

Grades will be given by accumulating points each week during the 8 week term of the course.  Points are accumulated by completing the assigned examinations, quizzes, presentations, projects, papers, case exercises, etc.

Grading:

There will be a total of 100 points available during the course.  These points are divided between a variety of assignments shown in the assignments section of the syllabus.  Grades will follow the normal Park University scale below:

A =  90- 100% (or 90 points or higher)

B = 80-89% (or 80 to 89 points)

C =  70-79% (or 70 to 79 points)

D = 60-69% (or 60 to 69 points)

F = < 60% (59 or fewer points)

Late Submission of Course Materials:
Work is expected to be turned in by on time.  If you cannot meet a deadline, let me know as soon as possible, BEFORE the deadline.  Leave an email or call me before the deadline and we should be able to make arrangements for late work.  If you make contact and have a valid reason, I will accept work up to one week late.  Any work later than one week will not be accepted.  Failure to make contact before the deadline will (except in extreme situations) result in a zero for the missed assignment.

Classroom Rules of Conduct:

1.  Everyone must participate in weekly classroom discussions. Discussions will be carried out is a courteous manner.

2.  You are expected to have original comments to add a discussion topic. You should also post a meaningful response to at least two of your fellow students. You should be prepared to explain and defend your discussion ideas.  In addition, all members of the class are encouraged and expected to participate in any and all discussion topics. 

3.  Don't take comments in the classroom discussion personally.

4.  Do not aim comments at individuals, that is inappropriate. 

5.  Please use email or cell number for messages or questions to the me.

Course Topic/Dates/Assignments:

Week 1: Systems Analysis Fundamentals

Overview & Introductions: Review the syllabus, course policies, and assignment schedule. Tell the class about yourself and what you expect from the class.
 
Lecture: Read the lecture on "Using a CASE Tool".

Reading Assignment: Systems Analysis & Design Chapters 1, 2. Search the Internet for CASE tool software information including: http://www.visible.com/Products/Analyst/index.htm

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 23 or 52.  Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 52. Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor.
 
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.

Quiz: Take a weekly quiz on the weekly learning objectives.

Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 23 or 51 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

Week 2: Managing Systems Analysis & Design Activities

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

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 99. Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 100 and submit it to the instructor
 
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 instructor.
 
Quiz: Take a weekly quiz on the weekly learning objectives.
 
Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 99 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

Week 3: Requirements Analysis

Lecture: Read the lecture on "Technology Connectors".

Reading Assignment: Systems Analysis & Design Chapters 4, 5. Search the Internet for information gathering techniques.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 133 or 164.  Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 134 or 165.  Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor.
 
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. Submit to the instructor for evaluation.
 
Quiz: Take a weekly quiz on the weekly learning objectives.
 
Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 133 or 164 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

Week 4: Systems Analysis Methods

Lecture: Read the lecture on "System Alignment With Organizational Needs"

Reading Assignment: Systems Analysis & Design Chapter 6, 7. Search the Internet for system feasibility analysis information.

Discussion Question: Choose one question from Systems Analysis & Design Review Questions on page 206 or 252.  Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 207 or 252.  Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor.
 
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. Submit the weekly work to the instructor for evaluation.
 
Quiz: Take a weekly quiz on the weekly learning objectives.

Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 206 or 252 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

Week 5: Data Analysis

Lecture: Read the lecture on "Structured Analysis Concepts".

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 291.  Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 291.  Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor.
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. Submit to the instructor for evaluatioin.
 
Quiz: Take a weekly quiz on the weekly learning objectives.

Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 291 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

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 329. Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 330.  Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor.
 
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. Submit to the instructor for evaluation.
 
Quiz: Take a weekly quiz on the weekly learning objectives.

Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 329 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

Week 7: Financial Analysis

Lecture: Read the lecture on “Estimating Software Costs”

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 370.  Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 371. Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor. .
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. Submit to the instructor for evaluation.
 
Quiz: Take a weekly quiz on the weekly learning objectives.
 
Lessons Learned: After completing all the assignments, then develop a 'one paragraph' comment on individual course activities during the week. The paragraph should 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 370 and include related examples from your personal observation or your work. Submit the lessons learned paragraph to the instructor.

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 749.  Develop a 'one paragraph' answer to the question and submit it to the instructor.
 
Homework Problem: Choose one problem from Systems Analysis & Design on page 749. Develop a 'one paragraph' solution for the problem including examples and submit it to the instructor.

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 instructor for evaluation.

Final Examination: Take the final exam
 
Student Opinion Survey: Complete the Student Opinion Survey form at the Park College Distance Education web page.

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 2008-2009 Undergraduate Catalog Page 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 2008-2009 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 "F".
  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.

Park University 2008-2009 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 .



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:12/9/2008 9:11:08 PM