Syllabus Entrance
Printer Friendly
Email Syllabus

IS 315 Computer Sys Analysis & Design I
Hubbard, William B.


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

F2F 2007 MY

Faculty

Hubbard, William B.

Title

Senior Instructor/Adjunct Faculty

Degrees/Certificates

MS, Information Systems, Strayer University, 1991
BS, Management/Computer Information Systems, Park University, 1987
AAS, Data Processing, Community College of the Air Force, 1980

Office Location

Fort Myer, Virginia

Office Hours

By Appointment

Daytime Phone

703-578-0521

E-Mail

William.Hubbard@park.edu

whubbard39@hotmail.com

Semester Dates

10/15/2007 to 12/16/2007

Class Days

-M-----

Class Time

5:00 - 10:00 PM

Prerequisites

IS 205 3:0:3

Credit Hours

3


Textbook:
Seventh Edition by Kendall & Kendall, Prentice Hall ISBN-0-13-615405-0. For papers, including laboratory assignments, either the American Psychological Association (APA) style or the Modern Language Association (MLA) style will be the only writing styles accepted.  

Textbooks can be purchased through the MBS bookstore

Textbooks can be purchased through the Parkville Bookstore

Additional Resources:
1.   Structured System Development, 2nd Edition, Fraser Publishing 1990, 2001.

 
2.   Systems Analysis and Design, Addison-Wesley Publishing Co. 1987.

3.   Software Engineering: A Practitioner’s Approach, Roger S. Pressman, McGraw-Hill, 1992.

4.   Database Systems: Concepts, Languages, & Architectures, McGraw-Hill, 1999.

5.   Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design,
 
Addison-Wesley Publishing Co., 2000.

6.   The Data Model Resource Book: A Library of Data Models for Specific Industries,

John Wiley & Sons, 2001.

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:
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:
I encourage lively discussion based on both my experiences and the students’ experiences along with our current activities. Moreover, each student is encouraged to engage interactively with both fellow students and instructor to share and provide experiences with research and laboratory activities from both class assignments and employment activities. Each student is encouraged to bring and discuss articles from periodicals, newspapers, Internet and technical writings that are germane to the Computer Systems Analysis and Design discipline.

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.


  Instructor Learning Outcomes
  1. The Student will understand and be able to use a CASE tool.
  2. The Student will understand and be able to use Microsoft Visio.
  3. The Student will understand and be able to use Microsoft PowerPoint.
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:

The course will consist of Lectures, Class Discussions, Computer Lab/Workshop Sessions, Computer Lab/Workshop Assignments, Reports, Briefings, Weekly Homework Quizzes, Midterm and Final Exams, Project Term Paper combined with Presentation. 
 
Additionally, each student’s homework must be typed (via word processor) and neat.

 

1.   Quizzes: Weekly homework quizzes will be assigned in advance to the student.

2.   Labs/Workshops: Students will be assigned three labs/workshops using the team concept, designing a system, and will brief the class and instructor on the progress of the system chosen.

3.   Mid-term and Final Exams: Students will complete one Mid-term and one Final Examination.

4.   Research Paper and Presentations: A topic is to be chosen using system research material gathered, and a system design in the form of a term paper supporting a Team Project accomplished. This topic will include the organization or firm that you want represented.   That organization or firm may be real or imagined, but have a degree of validity (such as “Boilermakers Union” ,”Southern Football Association”, “Feed & Grain Administration”, “U.S. Army”, “U.S Department of State”, and so on).   For example, this could be a check cashing system, ticket sales system, speed control system, sports information system, or an inventory system. Research material should be information gathered from, but not limited to, software system literature, including specifications and cost material.  A minimum of four references must be used and cited. Use your book, vendor material, information technology periodicals, and the Internet when choosing the system (all must be used for references). Ensure that these selections are categorized with the same platform types and cost types for comparison purposes. For example, choose those that are only personal computer platform systems, and chose those that are only retail prices, or chose those that are only mini-computer platforms, and choose those that are only wholesale prices. Your system selections and topic must be approved by the instructor.
 
      You should use the first paragraph to introduce the topic to the reader and to introduce the main points of the paper. The main points of the paper will include the main topics of a modern computer software system methodology that would be useful to the public sector, U.S. Government, or a local government. Develop a specification analysis, and a cost benefit analysis detailing system specifications (pros and cons), cost, and performance.   Additionally, you will provide a summarized cost and specification analysis for the system methodology you have chosen. Diagrams and Graphics using Microsoft PowerPoint or Visio are encouraged. Ensure that transition sentences should be used to tie one system summary into the next. A final concluding paragraph depicting your choice of the system methodology you have chosen must be included. This term paper is due both electronically and on paper as scheduled.


The paper will be graded to include: grammar, flow of thought, transitions, content, and format. Other factors may be considered in the grading of this paper. If you have any questions while completing this assignment, it is the student's responsibility to contact the instructor to have the question answered. Student teams (with each team member participating) will present their paper to the class (slides are encouraged).  Guidelines: APA or MLA format, 10-15 pages of body text, with not more than 25 pages total, 1" margins, double space, header, title page, table of contents, reference page (Grading criteria: format/references-10, grammar-10, introduction-5, transitions and flow of thought-5, conclusion-10, system summaries-40, graphics/diagrams-10; presentation-10)

 

Grading:

Eight homework quizzes, class participation, three workshops toward team project, a midterm exam, a term project paper with presentation, and a final exam will determine your course grade. Further details of labs and term paper with presentation will be covered in class. The relative weight of the course will be as follows:

 

METHOD

PERCENT

POINTS

Homework Quizzes (10)

 10% (Collectively)

 100

Class Participation

 5% (Collectively)

   50

Lab/Workshops and Student Briefs (3)

 10% (Collectively)

 100

Midterm Exam

 20%

 200

Term Paper

 25%

 250

Final Exam

 30%

 300

***TOTAL***

100%

1000

  Points:

A = 95-100%                      1000-950

B = 85-94%                          949-850

C = 75-84%                          849-750

D = 70-74%                          749-700

F = Less than 70%               699-Below

Late Submission of Course Materials:
If an assignment is due on a night that the student is not present, it is the student's responsibility to get the assignment to the instructor on the due date. Five points will be deducted each day an assignment is late. Assignments will not be accepted after three dates of the due date without prior approval from the instructor.

Classroom Rules of Conduct:
 

·         Class participation is expected and will form a part of the final grade.

·         Students are expected to attend all classes and be on time.

·         Students are required to read all material assigned prior to class and apply the material during class discussions, activities, and exercises.

·         The student is responsible for providing the instructor with justification for an excused absence, either prior to or immediately after the absence.

·         Computers are now an integral part of our educational experience.

·         Students must be responsible for planning ahead and meeting deadlines.

·         Students will conduct themselves in a professional manner at all times.

·         Students are expected to respect other students' opinions and values, even if they disagree with those opinions and values.

·         There should only be one person talking at a time. Side bar conversations will not be tolerated.

Course Topic/Dates/Assignments:
  Course Topic/Dates/Assignments:

DATE

CHAPTER(S)

TOPIC(s)

STUDY ASSIGNMENT

15 October 2007

(Week 1)

1

Assuming the Role of a Systems Analyst – CASE Tool.

Read Chapters 1;

Answer questions at end of Chap. 1;

22 October 2007

(Week 2)

2

Organizational Style and Its Impact on Information Systems.

Read Chapter 2;Answer questions at end of Chap.  2; Homework Assn. Chap. 1 Due; Project Proposals Due.

29 October 2007

(Week 3)

3

Determine Feasibility; Managing Analysis and Design Techniques.

Read Chapter 3; Answer questions at end of Chap. 3;. Homework Assn. Chap. 2 Due; Lab/Workshop 1; Student Brief.

5 November 2007

(Week 4)

4

MID-TERM Exam Review

Information Gathering: Interactive Methods.

Read Chapter 4; Answer questions at end of Chap. 4; Homework Assn. Chap.3 Due.

12 November 2007

(Week 5)

5

MID-TERM Exam

Information Gathering: Unobtrusive Methods.

Read Chapter 5; Answer questions at end of Chap. 5; Homework Assn. Chap. 4 Due; Lab/Workshop 2; Student Brief.

19 November 2005

(Week 6)

6

Agile Modeling and Prototyping

Read Chapters 6; Answer questions at end of Chapters 6; Homework Assn. Chap. 5 Due.

26 November 2007

(Week 7)

7

Using Data Flow Diagrams.

Read 7; Answer questions at end of Chap. 7; Homework Assn. Chap. 6 Due;

Lab/Workshop 3; Student Brief.

3 December 2007

(Week 8)

8

FINAL Exam Review
 
Describing Process Specifications

FINAL Exam Review; Analyzing Systems Using Data Dictionaries; and Project Presentations

Read Chap 8; Homework Assn. Chap. 7 Due; Final Exam Review; Project Presentations

10 December 2007

(Week 9)

9

FINAL Exam

Describing Process Specifications

Describing Process Specifications and Structured Decisions; FINAL Exam and Project Presentations

Read Chap. 9;

Homework Assn. Chap. 8 Due;

Project Presentations; and 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 2007-2008 Undergraduate Catalog Page 85-86

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 2007-2008 Undergraduate Catalog Page 85

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.
  3. Work missed through unexcused absences must also be made up within the semester/term of enrollment, but unexcused absences may carry further penalties.
  4. 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".
  5. A "Contract for Incomplete" will not be issued to a student who has unexcused or excessive absences recorded for a course.
  6. 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.
  7. 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 2007-2008 Undergraduate Catalog Page 87-88

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:11/19/2007 1:12:31 PM