Syllabus Entrance
Printer Friendly
Email Syllabus

IS 315 Computer Systems Analysis and Design I
Hanrahan, Robert


SYLLABUS Park University

COURSE SYMBOL AND NUMBER: IS 315
COURSE DESCRIPTOR: MGE/GE or MLL/LL.MGE
COURSE TITLE: Computer Systems Analysis & Design I
SEMESTER/TERM COURSE BEING TAUGHT: Summer, 2005
NAME OF FACULTY MEMBER: Robert (Bob) P. Hanrahan, ASQ CSQE, CLA, CCP
TITLE OF FACULTY MEMBER: Senior Instructor, Computer Science
FACULTY OFFICE LOCATION: Hill AFB, Utah, Bldg 383, Room TBD
FACULTY OFFICE HOURS: Monday – Sunday evenings until 9:00 p.m.
FACULTY OFFICE TELEPHONE NUMBER: Home (801) 525-9841 (until 9:00 p.m.)
FACULTY PARK EMAIL ADDRESS: Robert.Hanrahan@pirate.park.edu
OTHER FACULTY EMAIL ADDRESS: HanrahanBobster@aol.com
FACULTY WEB PAGE ADDRESS: TBD
DATES OF THE SEMESTER/TERM: June 5, 2005 – July 31, 2005
CLASS SESSIONS DAYS: Mondays and Wednesdays
CLASS SESSION TIME: 4:30 p.m. – 7:15 p.m.
PREREQUISITE (S): CS 205
CREDIT HOURS: 3
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 DESCRIPTION:
This course presents various philosophies, terminology, and techniques used in the analysis and implement of the system development life cycle. The student will investigate such areas as project proposals, logical systems, flow diagrams, data modeling dictionaries, and documentation. The student will learn how to use a CASE tool. Prerequisite: CS205

FACULTY’S EDUCATIONAL PHILOSOPHY:
My educational philosophy is one of interactiveness based on lectures, readings, dialogue, and use of practical case studies, random quizzes, examinations, Internet, videos, web sites and writings. I will engage each learner in what is referred to as disputatious learning to encourage the lively exploration of ideas, freedom to explore the technology at hand (Telecommunications, Computer Based Information Systems, emerging hardware and software technologies, software engineering, security, privacy and ethics etc.), and issues/contradictions with regard to management style.

COURSE OBJECTIVES:
Upon completion of this course, the student should be able to: Identify stakeholders and describe their roles and individual needs in system development; understand the Information Systems professional 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; evaluate strengths/weaknesses and applicable roles of several strategies/methodologies for design of information systems including Model Driven, RAD, Agile, OO development, and Prototyping; identify problem/opportunity/directive, cause/effect and business requirements for a given problem scenario; understand and explain the project management life cycle, approaches to scheduling, measuring of project progress and relationship to the system development life cycle; Identify the responsibilities of the Project Manager and discuss why they are important to the success of the project. Practice systems analysis traditional tasks: Problem analysis; requirements analysis; decision analysis; build process and data models for analysis within the system development life cycle; differentiate between logical and physical models; build communication skills, both oral and written as well as teamwork.

COURSE TEXTBOOK (S):
Kendall and Kendall, Systems Analysis and Design, 6th Edition, ISBN 0-13-118879, with Visible Analyst 7.5 CD

ACADEMIC HONESTY: “Academic Honesty is required of all members of a learning community. Hence, Park will not tolerate cheating or plagiarism on tests, examinations, papers or other course assignments. Students who engage in such dishonesty may be given failing grades or expelled from Park.”

PLAGIARISM:
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 the Park University academic honesty policies, which can be found on page 101 of the Park University Undergraduate Catalog.
Academic dishonesty in the School of Online Learning includes but is not limited to:
• Plagiarism occurs when a writer represents another person’s words or ideas as his/her own. Most often, plagiarism results when writers fail to enclose direct quotations in quotation marks; fail to include citations in the text or as footnotes; and/or fail to furnish a reference/works consulted list to accompany researched writing.
• Cheating occurs when the integrity of an activity or examination is compromised through dishonesty or deceit. Cheating includes unsanctioned student collaboration or the use of unsanctioned collateral materials. Cheating includes exchanging information about proctored examinations, quizzes, or other class activities that are designed to be completed independently.
• Misrepresentation involves providing false information in an academic assignment, furnishing false or misleading information to instructors or other University personnel, or presenting misleading or fabricated data as valid.
In the event of alleged academic dishonesty, an Academic Dishonesty Incident Report will be submitted to the Online Academic Director who will then investigate the charge. Students who engage in academic dishonesty are subject to a range of disciplinary actions, from a failing grade on the assignment or activity in question to expulsion from Park University.
ATTENDANCE POLICY: Instructors are required to keep attendance records and report absences. The instructor may excuse absences for cogent reasons, but missed work must be made up within the term of enrollment. Work missed through unexcused absences must also be made up within the term of enrollment, but unexcused absences may carry further penalties. In the event of two consecutive weeks of unexcused absences in a term of enrollment, the student will be administratively withdrawn, resulting in a grade of “F”. An Incomplete will not be issued to a student who has unexcused or excessive absences recorded for a course. Students receiving Military Tuition Assistance (TA) or Veterans Administration (VA) educational benefits must not exceed three unexcused absences in the term of enrollment. Excessive absences will be reported to the appropriate agency and may result in a monetary penalty to the student. Reports of F grade (attendance or academic) resulting from excessive absence for students receiving financial assistance from agencies not mentioned above will be reported to the appropriate agency.

Roll will be checked each class meeting. Classes missed for legitimate reasons, such as temporary duty and illness, are excusable; however, the student must make up the missed work as follows: The instructor for both assignments and programs will provide new assignments. Temporary duty orders may be given to the instructor or turned in to the school office.

LATE SUBMISSION OF COURSE MATERIALS: Assignments turned in late will be assessed a 20% penalty for each class it is late.

COURSE ASSESSMENT:
Students are required to read all assigned material prior to class and be prepared to discuss the reading material and assignments. Participation in class discussion is required to obtain full value from the material under consideration. There will be mid term and final exams, pop quizzes, an application of moderate complexity (project), textbook homework assignments and points for class participation. Textbook homework assignments and computer-based assignments will be turned in no later than the first class of the week after an assignment is given (Monday and Wednesday assignments will be due on Monday of the following week).

CLASSROOM RULES OF CONDUCT:
Computers and Interactive Development Environments (IDEs) make programming and testing much easier and more productive. Students must recognize though that technology can also cause problems. Printers run out of ink and hard drive crash. Students must be responsible for planning ahead and meeting deadlines in spite of technology. Be sure to save copies of your work to disk, hard drive, and print out paper copies for backup purposes.

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 American with Disabilities Act of 1990, regarding students with disabilities and, to the extent 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: www.park.edu/disability.

COURSE TOPICS/DATES/ASSIGNMENTS:
Date Chapter Topic Study Assignment

6 Jun Course Overview, Goals, Objectives etc.
1 Assuming the Role of the Systems Analyst All Sections
System Life Cycle and Software Development Life Cycle (Handouts)

8 Jun 1 Assuming the Role of the Systems Analyst (continued) All Sections
2 Understanding Organizational Style and its Impact on Information Systems All Sections
3 Jun 2 Understanding Organizational Style and its Impact on Information Systems (cont’d) All Sections
The Capability Maturity Model (CMM) and CMM Integrated (CMMI) (Handouts)
15 Jun 3 Determining Feasibility and Managing Analysis and Design Activities All Sections

20 Jun 4 Information Gathering: Interactive Methods All Sections


22 Jun 4 Information Gathering: Interactive Methods (cont’d) All Sections

27 Jun 5 Information Gathering: Unobtrusive Methods All Sections

29 Jun *********** MID-TERM EXAMINATION ***********

4 Jul (HOL) Lab: Work on Analysis and Design Projects

6 Jul 6 Prototyping, RAD and Extreme Programming All Sections
Personal Software Process (PSP) (Handouts)
11 Jul 7 Using Data Flow Diagrams All Sections

13 Jul 8 Analyzing Systems using Data Dictionaries All Sections

18 Jul 9 Describing Process Specifications and Structured Decisions All Sections

20 Jul 10 Preparing the System Proposal All Sections
******Review for Final Examination*******

25 Jul 10 Preparing the System Proposal (cont’d) All Sections
System Design Reviews – Group Presentations
****** Review for Final Examination ******

27 Jul System Design Reviews – Group Presentations
****** FINAL EXAMINATION ******


GRADING PLAN:
The final course grade will be determined by the following measurements:

Assignments:
Textbook 10% 100 points
Project (Analysis/Des) 30% 300 points
Class Participation 5% 50 points
Quizzes 5% (two 25 point “pop quizzes”) 50 points
Midterm Exam 25% 250 points
Final Exam 25% 250 points

The midterm exam will cover Chapters 1 through 5 and topics discussed in class.

The final exam will be cumulative and cover all the assigned textbook chapters, sections and related topics covered in class.

The course letter final grades will be determined by the following:

900 - 1000 A
800 - 899 B
700 - 799 C
600 - 699 D
Below 600 F (or four or more inexcusable absences)

There will be no curve used in the grading nor will extra work be accepted for credit, except as previously described for participation credit for excused absences or participation credit for excused absences.