Fall 2013 MIS306 Syllabus
Course Information
Room: GMCS329
Time: Monday 1600 – 1840
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
don’t ignore you)
Office Hours: Monday: 1500 – 1600; Tuesday 1600-1800; or by appointment
Book: Dennis, A., Wixom, B. H., and Roth, R.M.; Systems Analysis Design, fifth edition. John
Wiley & Sons, Inc., 2012.
Additional readings will be posted on Blackboard
Course Approach
MIS306 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:
Student Learning Outcomes
After succeeding in this course, students will be able to:
• work in a project-team setting
• perform all aspects of the SDLC planning phase
• perform all aspects of the SDLC analysis phase
• understand and articulate the benefits and limitations of the steps and deliverables used
in information systems projects
• analyze the competitive advantage that IS projects can bring to an organization
To achieve these outcomes 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:
Understand the principles of software development project management
Discuss the roles of project manager and system analyst
Discuss software quality
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
Grading - Assignments
The course grade will be determined using the following scale and assessment items:
Grade
A
AB+
B
BC+
C
Cother
Range
>=
>=
>
>=
>=
>
>=
>=
<
94%
90%
87.5%
83%
80%
77.5%
73%
70%
70%
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. Students who only attend class and do not participate in discussion will earn
no better than a 7 for participation, students who actively engage in class discussions and attend
consistently will earn scores above 7 depending on their level of participation.
Statement of Work document (team effort) with presentation, 10%, Presentations are on 9/23 with
the write up due 9/30
System Requirements Specification (team project) (25%) with presentation on 12/9 and write-up
due 12/16 (write up turn in is the final)
Three Exercises (10% each):
User Case Exercise, 10/14
DFD Exercise, 10/28
ERD Exercise, 11/18
Exam on Systems Analysis concepts worth 25%. Material covered on exam are chapters 1-6 of
the text plus blackboard material. Exam is on 11/25
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 student’s work
2. Final Deliverables are due 12/16
3. Deliverables are a Project Notebook 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)
Use Cases
Other
· 2) Set of user requirements
· 3) Assessment of alternatives
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
The below reading assignments are from the text, additional reading will be on
blackboard
Date
8/26
9/2
9/9
Reading
none
none
Ch 1
9/16
9/23
9/30
10/7
10/14
10/21
10/28
11/4
11/11
11/18
11/25
12/2
12/9
12/16
Ch 2
Ch 3
Ch 4
Ch 5
none
None
Ch 6
none
Topic
Intro to Software Engineering
Labor Day
The Systems Analyst And Information Systems
Development
Project Selection And Management
Statement of Work
Requirements Determination
Use Case Modeling
Use Case review
DFD Modeling
DFD modeling review
ERD Modeling
Veterans Day
ERD Modeling Review
Ch 1-6 exam
Finalizing Requirements/Catchup
Team Presentations
Final
Assignment
SOW presentations
SOW turn in
Use Case Exercise
DFD Exercise
ERD Exercise
Ch 1-6 Exam
Project Write Up
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 other’s work for your own. This can be done by not properly citing or
referencing other’s work in your papers, copying other’s work into your own (even if cited and
referenced), and/or copying other’s 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.