|
MASTER SYLLABUS |
|||||||||
|
CST 2810 |
|||||||||
| Class Hours: 3.0 | Credit Hours: 4.0 | ||||||||
| Laboratory Hours: 3.0 | Date Revised: Spring 00 | ||||||||
| NOTE: This course is not intended for transfer credit. | |||||||||
| Catalog Course Description: | |||||||||
| A study of system analysis techniques. Management teams analyze, design and select hardware/software, and implement solutions to practical problems. A laboratory will be scheduled to enhance the student's ability to use tools and techniques of systems analysis and design in solving the problems. | |||||||||
| Entry Level Standards: | |||||||||
| The entering student is expected to be familiar with database concepts. The student should have moderate programming abilities in at least one high-level language as well as basic reading, writing, and word processing skills. Problem solving skills will be essential. Knowledge of Visual programming is preferred. | |||||||||
| Prerequisites: | |||||||||
| CST 2510 or departmental approval; ENG 1010 | |||||||||
| Textbook(s) and Other Reference Materials Basic to the Course: | |||||||||
| Textbooks and Other
Supplies:
Systems Analysis and Design Methods, by Jeffrey Whitten & Lonnie Bentley. System Architect; student version 4.0 CD Popkins Software Systems Incorporated. Suggested Reading Materials: Using Analysis, Design, and Implementation, by John Burch Systems Analysis and Design, by Kendall & Kendall Systems Analysis and Design and the Transition to Objects, by Sandra Donaldson Dewitz Systems Analysis and Design - A Project Approach, by David Harris Systems Analysis and Design, by Gibson and Hughes Systems Analysis and Design, by Wu and Wu |
|||||||||
| I. Week/Unit/Topic Basis: | |||||||||
| Week | Topic | ||||||||
| 1 | The Modern Systems Analyst; Information System Building Blocks; Sound Stage Entertainment Club Running Case | ||||||||
| 2 | Information System Development; Project and Process Management Techniques | ||||||||
| 3 | Systems Analysis; Fact-Finding and Information Gathering; Interpersonal Skills and Communications; Mini Case | ||||||||
| 4 | Data Modeling; Process Modeling | ||||||||
| 5 | Process Modeling (continued); Chapter-Specific Problems; Review, Test 1 | ||||||||
| 6 | Network Modeling; Object Modeling | ||||||||
| 7 | Feasibility and Cost-Benefit Analysis; Systems Design and Construction | ||||||||
| 8 | Joint Application Development; Application Architecture and Process Design; Database Design | ||||||||
| 9 | Input Design and Prototyping; Output Design and Prototyping | ||||||||
| 10 | Output Design and Prototyping (continued); Review, Test 2 | ||||||||
| 11 | User Interface Design and Prototyping; Software Design | ||||||||
| 12 | Software Design (continued); Object-Oriented Design | ||||||||
| 13 | Systems Implementation; Systems Support | ||||||||
| 14 | Presentation of Team Projects | ||||||||
| 15 | Presentation of Team Projects; Wrap up, Review | ||||||||
| 16 | Final Exam | ||||||||
| II. Course Objectives*: | |||||||||
| A. | Become familiar with the steps in developing and designing a system. V, VIII | ||||||||
| B. | Become familiar with the qualifications of a systems analyst and tools that are available to an analyst for solving a problem. IV, IX, X | ||||||||
| C. | Demonstrate through group discussion how to approach a problem and come up with different solutions. I, XII | ||||||||
| D. | Develop and write a system proposal. V, XI | ||||||||
| E. | Implement a system. III, VI | ||||||||
| F. | Analyze different alternatives available in getting hardware and software. II | ||||||||
| G. | Become familiar with the major guidelines in evaluating hard-ware/ software, and vendors. VII, IX | ||||||||
| *Roman numerals after course objectives reference goals of the Business and Computer Technologies department. | |||||||||
| III. Instructional Processes*: | |||||||||
| Students will: | |||||||||
| 1. | Analyze, design and develop a well-documented project based on end-user request. Communication Outcome, Problem Solving and Decision Making Outcome, Technological Literacy Outcome, Information Literacy Outcome, Transitional Strategy, Active Learning Strategy | ||||||||
| 2. | Participate in a software development team. Communication Outcome, Problem Solving and Decision Making Outcome, Transitional Strategies, Active Learning Strategy | ||||||||
| 3. | Use professional tools to produce software components and documentation. Technological Literacy Outcome, Transitional Strategy, Active Learning Strategy | ||||||||
| 4. | Practice elements of work ethic such as punctuality, professionalism, dependability, cooperation, and contribution. Personal Development Outcome | ||||||||
| 5. | Use professionally accepted methods and materials in completion of applications. Technological Literacy Outcome, Transitional Strategy, Active Learning Strategy | ||||||||
| 6. | Participate in a peer review of team projects. Problem Solving and Decision Making Outcome, Communication Outcome, Transitional Strategy, Active Learning Strategy | ||||||||
| 7. | Use the Internet as a medium for obtaining documentation and instruction. Communication Outcome, Technological Literacy Outcome, Information Literacy Outcome, Transitional Strategy, Active Learning Strategy | ||||||||
| *Strategies and outcomes listed after instructional processes reference Pellissippi State’s goals for strengthening general education knowledge and skills, connecting coursework to experiences beyond the classroom, and encouraging students to take active and responsible roles in the educational process. | |||||||||
| IV. Expectations for Student Performance*: | |||||||||
| Upon successful completion of this course, the student should be able to: | |||||||||
| 1. | Demonstrate an overview of general concepts of system and system analysis and design. A,C,E | ||||||||
| 2. | Understand the tools which are available in providing prelimi-nary and detailed investigation and a major guideline in developing gene-ral and detailed design specification. A,B,C,D,E | ||||||||
| 3. | Develop an understanding of the system's life cycle and the tools and techniques available to the analyst. A,B,C,D,E | ||||||||
| 4. | Develop an understanding of different alternative solutions to a given problem and cost/benefit analysis associated with each. A,B,C,D,E | ||||||||
| 5. | Develop an understanding of the Rent/Buy/Lease methods. F | ||||||||
| 6. | Develop an understanding of Request for Proposal and different methods of evaluation including benchmarking. B,D | ||||||||
| 7. | Develop an understanding of different criteria used in evaluating hardware/software and making a final decision. A,B,F,G | ||||||||
| *Letters after performance expectations reference the course objectives listed above. | |||||||||
| V. Evaluation: | |||||||||
| A. Testing Procedures: | |||||||||
| There will be three tests. They will cover material presented in class. The test will consist of multiple choice questions, fill-in-the-blank, true/false, and short essay questions. The points for each problem will be graded according to the degree of difficulty. The tests will be cumulative in as much as material builds upon itself. Tests are not to be missed without a valid excuse. In the unlikely event that an emergency does occur, it is the student's responsibility to contact the instructor before test time. There will be no make-up tests unless prior arrangements are made with the instructor. | |||||||||
| B. Laboratory Expectations: | |||||||||
| Students
will learn the System Architect CASE (Computer-Aided Software Engineering)
tools on major systems analysis and design concepts the first few weeks
of the class.
Team Project: Students will be assigned to a project team. Teams will consist of 2 to 3 students. The team may pick a business application from work experience, or may do some research at the library and invent a system. The team will define and formulate its project during the first few weeks, then apply the tools and techniques of systems analysis and design learned in class to develop and design the team's system. Systems Architect, MS Project, and other prototyping tools may be used in development of the team project. The Team Project has a total of 360 points which consists of a final report (330 points) and the presentation (30 points) that will be divided among team members. Each student may receive different points based upon his/her presentation and peer evaluation. Team members who worked equally according to all the specification will receive a maximum of 120 or 180 points (depending upon the number of people on the team). The prospect of working in a team carries the possibility that not all team members will pull their fair share of the load. For this reason, there will be a confidential peer evaluation during the semester. Individual evaluations are the property of the instructor and will not be shared with other team mem-bers under any circumstances. |
|||||||||
| C. Field Work: | |||||||||
| Students are required to read all library materials/handouts assigned in class. | |||||||||
| D. Other Evaluation Methods: | |||||||||
| Students are expected to do in-class group discussion on various cases/projects. Homework assignments may consist of selected ques-tions at the end of chapters. Homework will not be accepted late. | |||||||||
| E. Grading Scale: | |||||||||
| 3 Tests
(100 Pts. Each) 300 pts.
Quizzes, Homework 100 pts. Team Project +120 or 180 pts. 520 or 580 pts. A 93 - 100
|
|||||||||
| VI. Policies: | |||||||||
| A. Attendance Policy: | |||||||||
| Pellissippi State Technical Community College expects students to attend all scheduled instructional activities. As a minimum, stu-dents in all courses must be present for at least 75 percent of their scheduled class and laboratory meetings in order to receive credit for the course. Students who have excused absences must complete make-up work within two weeks. | |||||||||
| B. Academic Dishonesty: | |||||||||
| Plagiarism, cheating, and other forms of academic dishonesty are prohibited. A student caught cheating may be given a grade of "F" for the course. | |||||||||