Syllabus Entrance
Printer Friendly
Email Syllabus

IS 315 Computer Sys Analysis & Design I
Sullivan, Kevin D.


Mission Statement: Park University provides access to a quality higher education experience that prepares a diverse community of learners to think critically, communicate effectively, demonstrate a global perspective and engage in lifelong learning and service to others.

Vision Statement: Park University, a pioneering institution of higher learning since 1875, will provide leadership in quality, innovative education for a diversity of learners who will excel in their professional and personal service to the global community.

Course

IS315 Computer Sys Analysis & Design I

Semester

F2Y 2011 MN

Faculty

Sullivan, Kevin D.

Title

Adjunct Instructor

Degrees/Certificates

MA    Webster University - 2005
BS     University of Phoenix - 2002
Certified Information Systems Security Professional (CISSP)

Office Location

NSA Millington, TN

Office Hours

By appointment

Daytime Phone

(901) 240-1186

Other Phone

(901) 240-1186

E-Mail

kevin.sullivan@park.edu

sulkevsr@gmail.com

Semester Dates

October 17th - December 11th

Class Days

-----F-

Class Time

5:00 - 9:40 PM

Credit Hours

3


Textbook:

Systems Analysis & Design , Kendall & Kendall, 8th ED, Prenhall Systems Analysis and Design (Custom) • 2011
ISBN978-0-558-81728-2  
 

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 instructor's educational philosophy is one of interactive learning. Text, videos, lecture, readings, writings, Internet, web sites, quizzes, examinations, and classroom dialogues and debates will be employed. The instructor will engage each student and solicit ideas and feedback. It is important to note that proactive student participation significantly enhances the classroom experience.

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:

Assessment will be determined via examinations, quizzes, presentations, papers, and projects.

Grading:

 

Class participation - 15%

Project - 20%

Presentation - 15% 

Mid-term - 25%

Final exams - 25%

 

 

 

 

 

 

Late Submission of Course Materials:

The instructor will not accept assignments late. Assignments not submitted on the due date will receive a grade of "zero".

Classroom Rules of Conduct:

- Faculty members are expected to dismiss from their classrooms students whose behavior is detrimental to good order in the classroom.

- As a common practice in college level academic education, the greatest range of acceptance will be given to all view points; each student will have intellectual advancement as their primary goal, respect will be given to all other students, the class as a group and the school environment.

- Cell phones must be turned off or in vibrate mode. If you receive a call, leave the classroom and go to the school lobby. Do not stand in the hallway as that disrupts other classes.

Course Topic/Dates/Assignments:

***Read Units 1 prior to first class***

Date

Day

Ch.

Topic

Oct 21

Friday

1

Assuming the role of the Systems Analyst



       2 Understanding Organizational Style and its Impact on Information Systems




Oct 28

Friday

3

Determining Feasibility and Managing Analysis and Design Activities



       4  Information Gathering: Interactive Methods







  
Nov 4
Friday
       5      
Information Gathering: Unobtrusive Methods


       6  Agile Modeling and Prototyping







Nov 11
Friday

Mid-Term








Nov 18
Friday
       7     Using Data Flow Diagrams


       8 Analyzing Systems using Data Dictionaries




Nov 25
Friday
       9    Describing Process Specifications and Structured Decisions








Dec 2
Friday
       
Students' Presentations


       
Research Papers 





Dec 9
Friday

Final Exam

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 students and faculty members are encouraged to take advantage of the University resources available for learning about academic honesty (www.park.edu/current or http://www.park.edu/faculty/).from Park University 2011-2012 Undergraduate Catalog Page 93

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. from Park University 2011-2012 Undergraduate Catalog Page 93

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 2011-2012 Undergraduate Catalog Page 96

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:



Bibliography:



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:9/28/2011 11:10:57 PM