IT 215 Analysis and Design Techniques

Syllabus

Summary of the course:

This course will present a practical approach to systems analysis and design using a blend of traditional development with current technologies. It will also serve as preparation for courses where systems implementation is the goal. The role of the systems analyst will be considered as well the skills necessary to interact with users, management, and other information systems professionals in a typical business organization. The five phases of the systems development life cycle (SDLC) will be defined and described in detail. An in-depth study of the supporting components, i.e. process flowcharting, data flow and entity relationship diagramming, data dictionary, will be presented. Case studies will promote critical-thinking skills as well as provide the foundation for a student project that incorporates the skills attained throughout the quarter. There is no programming requirement for this class.

Prerequisites:

The prerequisite for Undergraduates for this course is CSC319 (Database Technology). Graduate students who are taking this class as a prerequisite are not required to complete CSC319. Students are expected to:

· Be familiar with the general terms in information technology such as file, record, field, database, hardware, operating system, network and software.

· Be familiar with general programming concepts.

Required Text: IT215 Analysis and Design Techniques

Required: Systems Analysis and Design, 6th Edition

Shelly, Course Technology, 2006. ISBN:0-619-25510-2

Objectives:

The activities involved in System Analysis and Design fall into three broad categories:

· Behavioral, Sociological and Technical Analysis and Design: Business system success or failure depends on a good fit between the system and the organization. A system can be superior from a technological viewpoint, but still be a miserable failure in an organization. It is also possible to design a comfortable system that makes people happy, but doesn't solve the business problem. One of the underlying themes for this class is to understand the importance of incorporating all three areas - behavioral, sociological and technical - in the analysis and design of business information systems.

· Analysis and Design Toolkit: You will learn tools to help you perform analysis and design tasks. Some of these tools will help you create models of business systems. These modeling tools include data flow diagrams and entity-relationship diagrams. Other tools will help you communicate more effectively with people in an organization. These tools include project scheduling, interviewing techniques, listening skills, writing methods, and presentation expertise. All the tools you learn in this class will compose your personal analysis and design toolkit.

· Technological Products in Computer Systems Analysis and Design: Systems analysis and design does not always result in a technical solution to a business system problem. Sometimes a procedural or personnel change produces spectacular results. Other times, however, a technologically based solution is the preferred choice to solve a problem. You need to know about the availability of technical solutions in order to make sensible recommendations. You also need to know how to deal with vendors and get good information about existing technological solutions.

Upon successful completion of the course, students are expected to be able to:

• Analyze a business need for information and develop an appropriate strategy to solve the problem.
• Prepare and use various information gathering techniques for eliciting user information requirements and system expectations.
• Construct and interpret a variety of system description documents, including process flowcharts, data flow diagrams, data dictionary and entity-relationship diagrams as well as screen, form and report layouts.
• Describe the major alternative methodologies used in developing information systems and the considerations involved in choosing which methodology to use.
• Design a system to meet the business problem including all of the above plus the system architecture, implementation plan and budget.
• Communicate system specifications effectively and be persuasive in these presentations, in both written and oral forms.

Grading:

Exam (2) – 25% each

There will be two open note/open book take-home exams.

Project – 50%

The quarter-long team project includes the following deliverables:

· Title Page that includes project name, team name, team members, date.

· Table of Contents that includes a list of report sections with page numbers.

· System Requirements Document that includes a statement of the problem and project objectives.

· Analysis

o Process Description

o Context Diagram

o Dataflow Diagrams (Level 0 and Level 1)

· Design

o Entity Relationship Diagram (3NF)

o CRUD Analysis

o Revised Process Flowchart

o Revised Dataflow Diagrams

o Data Dictionary

o Sample Input/Output that includes some of the top-level interfaces that the user will see by activity needs (one per page with a narrative). This gives users a chance to immediately grasp how they will use the system and also how it will take care of their functional needs.

o Architecture Overview that includes a description of the hardware that is being recommended that supports the system requirements. Include networking, individual workstations, peripheral devices, communication capabilities, etc.

o Implementation Plan – This is a proposed project plan. Using MS Project (available in the 8^th floor lab), produce a Gantt chart. It is impossible to be totally accurate at this point. Try to give the decision-makers a good projection. Make sure they understand that it is not “written in stone” in your narrative.

o Budget - Cover major cost areas in this estimate: hardware, software, personnel costs, installation costs, training costs, backup and maintenance costs over a period of time. If possible, include a projection of savings your system will bring about using cost-benefits analysis.

Grading Standards:

Letter Minimum % Letter Minimum %

Grade of Total Points Grade of Total Points

A 92.00 C+ 78.00

A- 90.00 C 72.00

B+ 88.00 C- 70.00

B 82.00 D+ 68.00

B- 80.00 D 60.00

F 0.00

Incomplete Grade:

An incomplete grade is given only for an exceptional reason such as a death in the family, a serious illness, etc. Any such reason must be documented. Any incomplete request must be made at least two weeks before the final, and approved by the Dean of the School of Computer Science, Telecommunications and Information Systems. Any consequences resulting from a poor grade for the course will not be considered as valid reasons for such a request.

Course Policies:

You are expected to take an active role.

It is your responsibility to work within the course framework and learn about systems analysis and design. I expect you to ask questions and communicate with me and your fellow class members via email or in the classroom. I welcome questions both during class and during my office hours.

If you feel you are not learning the material, it is up to you to take steps to change that situation. I am available for assistance, but it is up to you to make the overture and ask for help. Please don't struggle for hours with an issue that could be answered by me or by another member of the class. Send email, ask questions in class, visit me during my office hours, make an appointment to see me. Take an active role.

You are responsible for completing all assignments on time.

I am providing you with a schedule that details exactly when each project deliverable is due. It is your responsibility to see that each assignment is completed on time and is the very best work you are able to produce within your personal time constraints. I guarantee that every student in this class is doing something in addition to going to school. Create a schedule that allows you to fulfill the assignment expectations of this class within the constraints of your other obligations. Assignments are due on the assigned day. No late assignments will be accepted.

You are responsible for knowing material covered in class.

I will be lecturing about material that is not in your text and I expect you to know this material for your exams. If you have missed a class you have missed important information! It is up to you to obtain notes from a classmate.

General Guidelines:

Don't cheat. Cheating includes plagiarism, fraud and other forms of academic dishonesty. If you are working in a group, I consider it cheating if you don't do your fair share of the work. The division of labor within a group is the group's responsibility. If, however, there are reports from a group about a non-participating member, then I will consider that member to be cheating the group. Peer evaluations will be part of each group project and will be considered when assigning individual grades. University guidelines on academic integrity and plagiarism can be found in the Student Handbook (http://studentaffairs.depaul.edu/handbook/).

Don't be late. Please be on time for class so that we can make full use of our limited class meeting time without interruptions.

Turn off all beeping devices. Please make sure that all pagers, phones, watches, computers, and other beeping devices are turned off during class.

Don't hold side discussions. If you have a question, or want to present your opinion about an issue under scrutiny, say it loud enough for the class to hear. Don't chat with your neighbor during my class time.

Frequently Asked Questions:

Is there any programming in this class? No.

Why isn't there any programming? The goal of this class is to teach critical thinking and problem solving skills independent of any computer technology.

Shouldn't all CTI classes emphasize technical skills? Employers say that the most important skills for IS people are communication and analysis. This class emphasizes that skill set. Many of the problems solved by IS professionals are related to communication, rather than technology.

How much time will this class take? An "average" 4 credit quarter course should take about 8 hours a week outside of class in addition to the time you spend in class. Depending on your prior skill set and that a team project is required, this course may take more time than an average course.

Why does it take so much time? You will learn modeling skills that take time and practice to master. In addition, the class requires a great deal of writing which is time-consuming. Teams should also plan on meeting in person at least once a week. I have allowed the last half-hour of class to minimize the number of outside meetings required.

Is there any extra credit? No.

Can I get a job with the skills I learn in this class? Yes and no. Yes, because you will use the skills from this class for just about any job in information systems. No, because you may never use the specific tools learned in this class to analyze a system - that will probably be up to you because few employers actually enforce the use of specific tools or methodologies.

Where can I work as a systems analyst? Many companies hire systems analysts. You can as a systems analyst analyzing the internal systems of the organization. You can work for a hardware or software vendor such as Oracle, SAP-AG, IBM or Unisys analyzing the systems of their customers. You can work for a consulting company analyzing the systems of their consulting customers. It depends on how hard you want to work, how much you are willing to travel, and how much money you want to make.

Changes to Syllabus:

This syllabus is subject to change as necessary during the quarter. If it occurs, it will be thoroughly addressed during class.