COURSE SYLLABUS

	COURSE SYLLABUS DAKOTA STATE UNIVERSITY MADISON, SD SUMMER 2009
COURSE ID:	CIS 332 – D31
COURSE NAME:	STRUCTURED SYSTEMS ANALYSIS AND DESIGN
CRN #	53795
COURSE DESCRIPTION:	Skills In Structured Systems Analysis Techniques Used To Define Information Systems Solutions To Business Problems By Producing Detailed Systems Specifications.
PREREQUISITE:	CSC 150 OR CIS 130
SEMESTER CREDIT HOURS:	THREE (3)
CLASS LOCATION:	INTERNET
COURSE SCHEDULE:	JUNE 29, 2009 TO AUGUST 7, 2009
LAST DAY TO DROP AND RECEIVE REFUND:	JULY 2, 2009
LAST DAY TO DROP AND RECEIVE A “W”	JULY 27, 2009
INSTRUCTOR:	WAYNE E.PAULI, PhD
INSTRUCTOR HOMEPAGE	Http://www.homepages.dsu.edu/pauliw
INSTRUCTOR EMAIL:	Wayne.pauli@dsu.edu
INSTRUCTOR OFFICE:	DSU – 820 N. WASHINGTON AVENUE – EAST HALL – ROOM 3A – MADISON, SD 57042
OFFICE HOURS:	8:00 AM TO NOON MONDAY THROUGH FRIDAY
OFFICE TELEPHONE #:	605-256-5800
CONTACTING THE INSTRUCTOR:	Since this course is being delivered via the Internet and face-to-face contact is not one of the delivery mechanisms being used the preferred method of contact will be email. Please use the email address given above as this is preferred to the email system in the course management system, D2L. If there will be periods of time that the Instructor will be away from the office he will alert the learners via email and post on the course homepage in D2L.
ADA STATEMENT:	If you have a documented disability and/or anticipate needing accommodations (e.g., non-standard note taking, test modifications) in this course, please arrange to meet with the instructor. Also, please contact Dakota State University’s ADA coordinator, Keith Bundy in the Student Development Office located in the Trojan Center Underground or at 256-5121, as soon as possible. The DSU website containing additional information, along with the form to request accommodations is http://www.departments.dsu.edu/disability_services/ You will need to provide documentation of your disability. The ADA coordinator must confirm the need for accommodations before officially authorizing them.
ATTENDANCE:	This course is being offered online in a concentrated six (6) week summer session. It is paramount that the student be engaged on a daily basis with reading and homework in order to successfully complete the required work of a 300 level university course.
DISHONESTY	Cheating and other forms of academic dishonesty run contrary to the purpose of higher education and will not be tolerated in this course. All forms of academic dishonesty will result in the student receiving a zero (0) for a grade on the submission. Please be advised that, when the instructor suspects plagiarism, the Internet and other standard means of plagiarism detection will be used to resolve the instructor’s concerns. DSU’s policy on academic integrity (DSU Policy 04-05-00) is available online at http://www.departments.dsu.edu/hr/newsite/policies/040500.htm
FREEDOM TO LEARN:	Students are responsible for learning the content of any course of study in which they are enrolled. Under Board of Regents and University policy, student academic performance shall be evaluated solely on an academic basis and students should be free to take reasoned exception to the data or views offered in any course of study. It has always been the policy of Dakota State University to allow students to appeal the decisions of faculty, administrative, and staff members and the decisions of institutional committees. Students who believe that an academic evaluation is unrelated to academic standards but is related instead to judgment of their personal opinion or conduct should contact the dean of the college which offers the class to initiate a review of the evaluation.
TEXT:	Systems Analysis & Design ~ Fourth Edition by Alan Dennis, Barbara Haley Wixom, and Roberta M. Roth. Published by John Wiley & Sons, Inc. ISBN #: 978-0-470-22854-8
TEXT AVAILABILITY:	The Text is available for purchase through the DSU Bookstore by using the following URL: http://www.dsubookstore.com/. The drop down box to order text books is located on the left-hand side of the bookstore homepage.
SOFTWARE:	Microsoft Visio Professional 2007 ~ The required software is available as a free download via the msdn academic alliance that Dakota State University has entered into with the Microsoft. Under a separate email the learners will receive download instructions and the obtaining of the product key in order to activate a legal copy of the software. If any learners already have this version or an earlier version of the Visio product it will be sufficient for course deliverables. Office 2007 ~ Excel and Word from the Office suite will also be needed for assigned work. Web Browser ~ one of your choice that will work sufficiently with the course management system, D2L. All course materials as well as quizzes and examinations will be accessed through D2L. The Instructor prefers Internet Explorer as D2L seems to work a bit better with IE 6.0/7.0/8.0.
INSTRUCTOR LECTURES:	A series of prerecorded lectures on the course content will be made available to all learners. The videos are meant to augment the learners reading of the course materials, not as a replacement for same. The videos will be available through D2L. It is highly recommended that the learners download these videos and use them as study guides.
GROUP WORK:	There will be no group work during this class. The curriculum is intended for individual learner investigation and skill set development.
SELF DIRECTED LEARNING:	Distance education can be a wonderful experience for a learner if they have some or all of the following characteristics: A self starter, dedicated to learning, work within a schedule, and understands when and how deliverables are due. The concentrated time frame of this summer section does not lessen the amount of work to be completed.
ASSIGNMENTS:	The course consists of a series of twelve (12) assignments with each assignment building upon those before it. Systems Analysis follows a step by step approach to development and it is being taught in the same step by step fashion that software engineers and analysts use during the System Development Life Cycle (SDLC). Each assignment will be worth a possible 25 points for a total of 300 points.
QUIZZES:	The course has ten (10) quizzes. They will be objective in nature with each quiz being worth 20 points for a total of 200 points.
EXAMINATIONS:	The course has two (2) examinations. They will be objective in nature with each exam being worth 100 points for a total of 200 points.
GRADING SCALE:	The course will use 700 points as the maximum available. Each assignment will be worth 25 points (12 * 25 = 300), each quiz will be worth 20 points (10 * 20 = 200), and each exam will be worth 100 points (2 * 100 = 200). 625 points to 700 points will result in an A 555 points to 624 points will result in a B 485 points to 554 points will result in a C 416 points to 484 points will result in a D Lower than 415 will result in a failing grade
EXTENSIONS OF TIME:	Extensions of time for turning in work will not be granted, as the deadlines for the work assigned will be communicated and posted on the assignment page much in advance of due date. This is an upper level course; be proactive with assigned work, do not procrastinate. Any assigned work not submitted by due date will be graded a ZERO. A six (6) week course does not allow for distractions, please plan accordingly.
FORMAT OF WORK:	All assignments will be delivered electronically via Desire2Learn (D2L) submission. Specifics for the assignments will be posted on the Assignment page of D2L. Paper copies will not be accepted unless requested by Instructor. All quizzes will be objective in nature and will cover topics in the assigned reading materials. Quizzes will be delivered electronically via D2L and do not require a proctor. They are also open book and open note. All exams will be objective in nature, the first exam will cover the materials form the first six (6) chapters of the text, and the final exam will be based on material from the final eight (8) chapters of the text. Exams will be delivered electronically via D2L and do not require a proctor. They are also open book and open note.
TIME LINE	Instructor reserves the right to make any changes to the Syllabus throughout the semester. Last Day to drop this course and receive a 100% refund is Thursday, July 2, 2009. The last day to drop this course and receive an automatic "W" is Monday, July 27, 2009. A Plan of Action has been created and follows in this document.

CIS 332 - PLAN OF ACTION
WEEK #	DATE	CHAPTER	ASSIGNMENT	QUIZ	EXAM	TIME DUE
1						PART 1 - THE PLANNING PHASE
	29-Jun	ONE
	30-Jun	ONE		ONE		Q1 DUE MIDNIGHT
	1-Jul	TWO	ONE			A1 DUE 10 PM
	2-Jul	TWO				Last day to drop and get refund
	3-Jul	TWO	TWO	TWO		A2 DUE 10 PM & Q2 DUE MIDNIGHT
2						PART 2 - THE ANALYSIS PHASE W1
	6-Jul	THREE
	7-Jul	THREE
	8-Jul	THREE	THREE	THREE		A3 DUE 10 PM & Q3 DUE MIDNIGHT
	9-Jul	FOUR
	10-Jul	FOUR	FOUR	FOUR		A4 DUE 10 PM & Q4 DUE MIDNIGHT
3						PART 2 - THE ANALYSIS PHASE - W2
	13-Jul	FIVE
	14-Jul	FIVE		FIVE		A5 DUE 10 PM & Q5 DUE MIDNIGHT
	15-Jul	SIX	FIVE
	16-Jul	SIX		SIX		Q6 DUE MIDNIGHT
	17-Jul	SIX	SIX		MID-TERM	COVERS CHAPTERS 1 - 6 IN YOUR TEXT A6 DUE 10 PM & EXAM1 DUE MIDNIGHT

WEEK #	DATE	CHAPTER	ASSIGNMENT	QUIZ	EXAM	TIME DUE
4						PART 3 - THE DESIGN PHASE - W1
	20-Jul	SEVEN
	21-Jul	SEVEN		SEVEN		Q7 DUE MIDNIGHT
	22-Jul	EIGHT	SEVEN			A7 DUE 10 PM
	23-Jul	EIGHT		EIGHT		Q8 DUE MIDNIGHT
	24-Jul	NINE	EIGHT			A8 DUE 10 PM
WEEK #	DATE	CHAPTER	ASSIGNMENT	QUIZ	EXAM	TIME DUE
5						PART 3 - THE DESIGN PHASE - W2
	27-Jul	NINE				Last day to drop and receive a “W”
	28-Jul	TEN
	29-Jul	TEN	NINE	NINE		A9 DUE 10 PM & Q9 DUE MIDNIGHT
	30-Jul	ELEVEN
	31-Jul	ELEVEN	TEN			A10 DUE 10 PM
6						PART 4 - THE IMPLEMENTATION PHASE
	3-Aug	TWELVE
	4-Aug	TWELVE		TEN		Q10 DUE MIDNIGHT
	5-Aug	THIRTEEN	ELEVEN			A11 DUE 10 PM
	6-Aug	FOURTEEN
	7-Aug		TWELVE		FINAL	COVERS CHAPTERS 7 - 14 IN YOUR TEXT A12 DUE 10 PM & EXAM2 DUE MIDNIGHT

ASSIGNMENTS: Listed on the next four (4) pages are the assignments for the course. They will also be available in D2L. Each Assignment is worth 25 points, and builds on the objectives of the science of Systems Analysis and Design. The objectives of the course are listed immediate after the assignments.

ASSIGNMENT #1	DUE:	7/1/09	25 POINTS	SUBMIT THROUGH D2L
Create a system request form (SRF) (see page 17) for a system that you would like to create. You will be using this system throughout the class. Keep it very focused as that will make it easier to answer the 5 elements of the SRF and to later build upon this concept. You will be working with this system for six weeks. Attached to this drop box area is a spreadsheet template that allows you to work on the economic feasibility of your project. The CFO is always going to want to know Return on Investment. Here is a tool to help you understand the pieces of what makes up ROI (see page 38, Figure 1B-1). The deliverables are the SRF and the Economic Feasibility Analysis.


ASSIGNMENT #2	DUE:	7/3/09	25 POINTS	SUBMIT THROUGH D2L
Your textbook describes 7 methods for system development (pages 47 - 54). Select a method and explain your choice using the criteria outlined on pages 55 and 56. Remember, this is your project and your decision making that you must justify. The justification should be written in business memo form addressed to your Instructor as they CIO of your firm. It should be a professional business communication that is double spaced with 1 inch margins and written with a high degree of intellect. If you wanted funded your story much be compelling.


ASSIGNMENT #3	DUE:	7/8/09	25 POINTS	SUBMIT THROUGH D2L
Based on the development methodology you selected in assignment #2 create a work plan for the project. A Work Breakdown Structure (Figure 2-12) is a necessary tool for such a plan. Use the Project Work Plan on pages 61 and 62 as a template for your plan. Would the use of CASE tools have made your plan easier? More reliable? Have you ever worked with a Gantt Chart? Address these questions as well. Perhaps Visio has a tool in its toolbox that will help build the Gantt chart.


ASSIGNMENT #4	DUE:	7/10/09	25 POINTS	SUBMIT THROUGH D2L
During the analysis phase, you determine the business requirements for your new system. A requirement is simply a statement of what the system must do or what characteristics it needs to have. It can be confusing trying to separate business requirements from system requirements. You will look much closer at system requirements during the third phase (Design) of the SDLC. The author describes in detail many requirements-gathering techniques that are employed by analysts. (pages 113 - 132). Select the most appropriate technique for your system, describe how it was utilized and what your findings are. This report is your deliverable for the assignment.


ASSIGNMENT #5	DUE:	7/15/09	25 POINTS	SUBMIT THROUGH D2L
Use cases describe in more detail the key elements of the requirements definition. In effect they depict a set of activities performed to produce the desired output result. Try to be as specific as possible when creating Use cases. Figure 4-2 on page 148 illustrates the steps taken to build use case statements for your system. Complete these four steps for each identified use case for your system. Submit the use case documents for this assignment. See pages 155 - 157 for samples. Use the template provided to create your use cases.


ASSIGNMENT #6	DUE:	7/17/09	25 POINTS	SUBMIT THROUGH D2L
Data Flow Diagrams (DFD) create a model of the business processes impacted by the system development. It is a formal way of representing how the system will operate. The syntax if you will of the analysis phase. They are structured and use a common language of shapes, lines, and arrows. The image that you create of a process will describe its many characteristics such as name, number, inputs, outputs and etc. DFD's are created the majority of the time with the use of CASE tools. There are four (4) levels of the DFD are Context, Level 0, Level 1 and Level 2. Basically as you progress through each level you intentionally decompose (breakdown) your business processes ultimately Level 2 diagrams are the most decomposed and will be numbered with multiple decimal points as a way of recognizing which level you are describing. The minimum submission for this assignment is the Level 1 DFD. If you feel bold please breakdown your system to Level 2. It is amazing how the DFD will increase in size and complexity from level to level. The secret is understanding that there are only 2 states when dealing with flow charting, yes and no (or on and off). Just like the power button on your computer it is either on or off. Now you will see those Visio skills at work. Please use the Visio stencil and template that I have provided, this will take the guess work out of which objects and shapes I would like to see you use when creating the DFD.


ASSIGNMENT #7	DUE:	7/22/09	25 POINTS	SUBMIT THROUGH D2L
A data model describes the data that flow through the business processes in an organization. The data model represents the logical organization of data without indicating how the data are stored, created, or manipulated so that analysts can focus on the business without being distracted by technical details. The tool we use for these purposes in the Entity Relationship Diagram (ERD). If you have had any database courses you are already familiar with ERDs but if you have not then you will be gaining knowledge of ERDs for future coursework. An added bonus for taking this class this summer. There are three (3) basic elements of the ERD, those being: entities, attributes, and relationships. Your deliverable for this assignment is an ERD of your system. (pages 210 - 228 in your textbook).


ASSIGNMENT #8	DUE:	7/24/09	25 POINTS	SUBMIT THROUGH D2L
In assignment #4 earlier you (during the analysis phase) created the business requirements for your system. Now as we enter the design phase we turn our attention to the system requirements. What are your system requirements? What is your strategy for acquiring the needed requirements? Chapter 7 of your textbook discusses these strategies. Throughout your studies at DSU you will constantly be faced with decisions such as custom development or shrink wrap solutions, in-house development or out-sourcing. Now is your chance to answer some of these questions. It should be a professional business communication that is double spaced with 1 inch margins and written with a high degree of intellect. If you wanted funded your story much be compelling.


ASSIGNMENT #9	DUE:	7/29/09	25 POINTS	SUBMIT THROUGH D2L
In assignment 8 you created your system requirements and how to accomplish the development strategies. Whether you are looking at shrink wrap or custom developed applications by in-house developers or by outsourcers you must be able to share your vision of what the architecture will consist of. Chapter 10 walks you through the elements of architecture design. This is the first of four designs that will be part of your project. As you compare and then determine which architecture design you will desire to use you must keep in mind the six (6) main characteristics: Cost of Infrastructure, Cost of Development, Difficulty of Development, Interface Capabilities, Control and Security, and Scalability. Address these characteristics in your architectural design deliverable. It should be a professional business communication that is double spaced with 1 inch margins and written with a high degree of intellect. If you wanted funded your story much be compelling.


ASSIGNMENT 10	DUE:	7/31/09	25 POINTS	SUBMIT THROUGH D2L
For many new systems, the Graphical User Interface (GUI) has a great deal to do with the ultimate success or failure. If you think about this in your own personal computing time, applications that are not user friendly are just not apps that you spend a great deal of time with. So here is your chance to create the killer app that users will flock to and be not able to get enough of. Figure 9 - 1 on page 303 describes the principles of User Interface Design. GUIs need to minimize the amount of effort needed by the user to accomplish tasks. Think of it like this; You are the smartest most highly skilled person who will see the GUI so what makes perfect sense to you does not necessarily make sense to the mainstream user. Taking this into consideration create prototypes of your GUIs. You can chose a storyboard, html, or a language specific design (see pages 317 - 320).


ASSIGNMENT 11	DUE:	8/5/09	25 POINTS	SUBMIT THROUGH D2L
Earlier in this class you created DFDs and ERDs. They may or may not be sufficient by now since you have worked through architectural and GUI design steps. Most of the time moving from the logical representations of DFDs and ERDs to the physical models during the design phase makes changes in the DFD and ERD necessary. These steps are referred to as the Physical Data Flow Diagram and the Data Storage Design of the Physical Entity Relationship Diagram. These are the last steps before the Implementation phase of the SDLC. Revisit the DFDs and the ERDs that you created in assignments six and seven. Make the necessary physical changes and document why the changes were necessary. The updated diagrams and your rationale are the deliverables for this assignment.


ASSIGNMENT 12	DUE:	8/7/09	25 POINTS	SUBMIT THROUGH D2L
As the design phase is completed, the systems analyst begins to focus on the tasks associated with building the system, ensuring that it performs as designed and developing the documentation for the system. While programmers will carry out the "code crunching", you will prepare plans for system testing. A variety of tests will have to be completed before the system is ready to go online and into production. Are you going to be on time and on budget? Your reputation and future employment may hinge on this being reality. Your deliverable for this final assignment is a list of the types of tests you would have performed on the new system as well as a FAQ listing of questions for system documentation purposes. These items are covered in Chapter 12. Good luck.

COURSE OBJECTIVES:

Each Chapter in the textbook has specific objectives for the learner to understand.

1) The Systems Analyst and Information System Development

· Understand the role played in information systems development by the systems analyst

· Understand the fundamental systems development life cycle and its four phases

· Understand how organizations identify IS development projects

· Understand the importance of linking the information system to business needs

· Be able to create a system request

· Understand how to assess technical, economic, and organizational feasibility

· Be able to perform a feasibility analysis

2) Project Selection and Management

· Understand how projects are selected in some organizations

· Understand various approaches to the SDLC that can be used to structure a development project

· Understand how to select a project methodology based on project characteristics

· Be familiar with project estimation

· Be able to create a project work plan

· Understand how to staff a project

· Understand techniques to coordinate and manage the project

· Understand how to manage risk on the project

3) Requirements Determination

· Become familiar with the analysis phase of the SDLC

· Understand how to create a requirements definition

· Become familiar with requirements analysis techniques

· Understand when to use each requirements analysis technique

· Understand how to gather requirements by using interviews, JAD sessions, questionnaires, document analysis, and observation

· Understand when to use each requirements-gathering technique

4) Use Case Analysis

· Understand the role of use cases

· Understand the process used to create use cases

· Be able to create use cases

5) Process Modeling

· Understand the rules and style guidelines for data flow diagrams

· Understand the process used to create data flow diagrams

· Be able to create data flow diagrams

6) Data Modeling

· Understand the rules and style guidelines for creating entity relationship diagrams

· Be able to create entity relationship diagrams

· Become familiar with the data dictionary and metadata

· Understand how to balance between entity relationship diagrams and data flow diagrams

· Become familiar with the process of normalization

7) Moving Into Design

· Understand the initial transition from analysis to design

· Understand how to create a system specification

· Be familiar with three ways to acquire a system: custom, packages, and out-sourced alternatives

· Be able to create an alternative matrix

8) Architecture Design

· Understand the fundamental components of an info system

· Understand server-based, client based, and client server architectures

· Understand how operational, performance, security, cultural, and political requirements affect the architectural design

· Be familiar with how to create an architectural design

· Be familiar with how to create a hardware and software specification

9) User Interface Design

· Understand several fundamental use interface design principles

· Understand the process of user interface design

· Understand how to design the user interface structure

· Understand how to design the user interface standards

· Be able to design a user interface

10) Program Design

· Be able to revise logical DFDs into physical DFDs

· Be able to create a structure chart

· Be able to write a program specification

· Understand the use of pseudocode

· Become familiar with event-driven programming

11) Data Storage Design

· Become familiar with several file and database formats

· Understand several goals of data storage

· Be able to revise a logical ERD into a physical ERD

· Be able to optimize a relational database for data storage and data access

· Become familiar with indexes

· Be able to estimate the size of a database

12) Moving Into Implementation

· Be familiar with the system construction process

· Understand different types of test and when to use them

· Understand how to develop user documentation

13) Transition to the New System

· Be familiar with the system installation process

· Be familiar with the elements of a migration plan

· Understand different types of conversion strategies and when to use them

· Understand several techniques for managing change

· Be familiar with postinstallation processes

14) The Movement to Objects

· Understand basic concepts of the object approach and UML

· Be able to create a use case diagram

· Be able to create a class diagram

· Be able to create a sequence diagram

· Be able to create a behavioral state machine diagram