Fall 2011 MIS695 Syllabus Course Information

Room: GMCS329 Time: Monday 1900 2140 Professor: Murray E. Jennex, Ph.D., P.E., CISSP, CSSLP, PMP Office: SS3206 Phone: 594-3734 Email: murphjen@aol.com OR mjennex@mail.sdsu.edu Instant Message Office Hours: whenever online (be sure to identify yourself immediately so I dont ignore you) Office Hours: Monday and Tuesday: 1600 1800 or by appointment Book: Systems Analysis and Design Methods, 7th edition, Whitten and Bentley, McGraw-Hill, 2007

Course Approach
MIS695 is a combination seminar and lecture based course. Students are expected to be prepared for class and to contribute to class discussions. Class nights will focus on a topic and will not specifically cover the assigned reading chapter. Students are expected to be prepared to ask questions and fully participate in class discussions:

Course Goals
The objective of this course is to prepare you to analyze process problems, build process and data models, and to generate a system requirements document. To do this we will cover in detail the analysis portion of the System Development Life Cycle, SDLC. Course topics include life cycle methodologies, analysis requirements using structured methodology, automated tools, and process and data modeling, feasibility studies, development strategies, needs management, and prototyping. Students completing the course will be able to draw Data Flow and Entity Relation Diagrams and to generate a System Requirements Specification. Specific Objectives are: At the end of the course the student will have accomplished the following objectives (objectives are listed with enabling activities): Understand the principles of software development project management Discuss the roles of project manager and system analyst Discuss the definition of software engineering Discuss software quality Describe and create the software development plan Understand the lifecycle approach to systems analysis Discuss the need for a lifecycle approach to systems analysis State the goals of the lifecycle approach List and describe the steps in the structured lifecycle List and describe the steps in the RAD lifecycle List and describe the steps in the Evolutionary lifecycle Discuss when to use each lifecycle Understand the project selection process Describe the purpose of the Statement of Work document

Describe and list the different types of feasibility Describe methods for estimating project size and cost Understand the various system analysis graphical methods Describe and create the use case for a specified system use Describe and create the Entity Relation Diagram for a specified system Describe and create the Data Flow Diagram for a specified process Describe and create Logic Models for a specified process Describe and create the Security Model for a specified system Describe and create the Network Model for a specified system

Grading - Assignments
The course grade will be determined from the following: Class participation is worth 10% of the grade. Participation is not just showing up to class. Participation is active interaction in discussions, asking questions, answering questions, providing context and opinion. System Requirements Specification (team project) with presentation, 12/5, 25%, Write-up due 12/12 Statement of Work document (team effort) with presentation, 10%, Due 10/10 Software Development Plan (team effort) presented with final project, 15%, Write-up due 12/12 Four Exercises: DFD Exercise, 10%, 10/24 User Case Exercise, 10%, 10/31 ERD Exercise, 10%, 11/14 Security Model Exercise, 10%, 11/21 The Project will be to generate a System Requirements Specification for a knowledge management system for the organization of your choice. 1. The organization for the analysis may come from the students work 2. Final Deliverables are due 12/12 3. Deliverables are a Project Notebook (turned in on 12/12) that includes: a. Statement of the problem via a SOW (turned in earlier and included in the notebook) b. System Requirements Specification including: 1) Modeling Diagrams Data Flow Diagrams (DFD) Entity Relation Diagrams (ERD) Decision Trees/Tables Security Diagram Use Cases Other 2) Set of user requirements 3) Assessment of alternatives c. System Development Plan (turned in 12/12) The Software Development Plan is the overall plan for accomplishing the project and is similar to PMIs Project Management Plan. It is due 12/12 and should be part of the final presentation and included in the project notebook. A sample format is available on blackboard and includes:

1. 2. 3. 4. 5.

Resources needed for the project Work Breakdown Structure Tentative schedule of activities with resource loading Budget Estimate Risk analysis with mitigation plans

A 10% late penalty will be assigned for late assignments. Nothing will be accepted if over 2 weeks late. All turn in work needs to be typed and have a cover page. Be sure to include your name, the class, and what the turn in work is on the cover sheet.

Reading Assignments
Date----Reading--Topics 8/29------None--------Introduction, SDLC 9/5--------None--------Labor Day, no class 9/12-----Ch 1-3------SDLC, System Analyst, Alternative Methods (RAD, Agile, Extreme) 9/19-----Ch 4--------Managing/Identifying/Selecting Projects 9/26-----Ch 11-------Initiating/Planning Projects 10/3-----Ch 5, 6------System Analysis 10/10---None--------SOW Presentations, CASE 10/17---Ch 7---------Process Modeling Use Cases 10/24--- Ch 9----------Process Modeling DFDs, Use Case Exercise 10/31---- Ch 8----------Conceptual Data Modeling, DFD Exercise 11/7--- BB----------- Security Modeling, 11/14--None----------Network Modeling, ERD Exercise 11/21--- BB------------Assessing Alternatives, outsourcing, Security Modeling Exercise 11/28----BB------------Catch up (we will probably be behind, else there will be PMI discussion) 12/5----None----------Project Presentation 12/12---None---------Project Write-up due BB=Blackboard

Course Polices
Students are expected to be prepared to discuss the assigned readings and to attend class. It is understood that there may be occasions when you will have to miss class, on these occasions I request you send me an email letting me know prior to class. Should it be necessary that you miss class on the night an assignment is due or the exam or presentation is scheduled I request notification prior to the absence so that exams/presentations can be rescheduled. I will accept assignments via email on the due date as long as a hard copy is submitted at the next class the student is at. Excessive absences, more than 4, or a lack of participation, or excessive unrelated conversation, or excessive use of computers for non class work will result in a 5% grade deduction. Excessive will be in my opinion but students will be warned and given an opportunity to improve before the deduction will be assessed. Cheating is defined as the effort to give or receive help on any graded work in this class without permission from the instructor, or to submit alterations to graded work for re-grading. Any student who is caught cheating receives an F for the class, will be reported to Judicial Procedures, and be recommended for removal from the College of Business. Plagiarism will not be tolerated and rampant or repeated plagiarism will be treated as cheating. Plagiarism is claiming others work for your own. This can be done by not properly citing or

referencing others work in your papers, copying others work into your own (even if cited and referenced), and/or copying others work into your own without citing or referencing the source. Citation and referencing errors will result in grade deductions for the first offense, repeated offenses will result in reduction by a full grade on the assignment, an F for the assignment, or an F for the class depending upon the severity and intent of the offense. A 10% penalty will be assigned for late assignments. No assignment will be accepted if over 2 weeks late. All turn in work needs to be typed, have a cover page, and be single-spaced with appropriate spacing. Be sure to include your name, the class, and what the turn in work is on the cover sheet.