MIS 160 (Systems Development Life Cycle I) - Spring 2013 COURSE OUTLINE
Instructor
Office
Office Hours
Office Phone
E-mail
Web Page
Spiros Velianitis, MS/MIS
TAH-2077
Monday and Wednesday 4:20 – 5:50 pm and by appointment
278-5940
Spiros@CSUS.edu
http://www.csus.edu/indiv/v/velianitis
[Course Description] [Course Objectives] [Text] [Tools] [Systems Development Project] [Exams] [Grading] [Schedule]
Prerequisites
Course
Description
[Top]
Course
Objectives
[Top]
Text [Top]
Course
Methodology
1|Page
MIS 101, MIS 120, MGMT 102.
MIS 160. Systems Development Life Cycle I. Student teams analyze and design business information
systems of moderate complexity to solve the information needs of "real clients" including, but not limited,
to developing new systems and redesigning, or intergrading existing systems. We study various analysis
and design methodologies and we use the most current Project Management and UML tools in our projects.
Students are involved in several team development and leadership activities and are required to produce
oral and written reports. Note: The project will be continued in MIS 161; therefore, taking MIS 160 and
MIS 161 in consecutive semesters is highly recommended. Prerequisite: MIS 101, MIS 120, MGMT 102. 3
units.
 Think and work as a professional consultant
 Become a dependable team player and a leader
 Learn to learn
 Prepare yourself for the "real world"
 Develop systems development skills
 Synthesize skills and knowledge from other classes into an innovative technology solution
John W. Satzinger, et al. Systems Analysis and Design in a Changing World, Fifth Edition, 2009, Boston
MA: Thomson Course Technology.
I will not lecture on the material of this book "cover to cover". Lectures will be presented to supplement the
subject covered in the text. In most cases, I will explain the most important topics covered in each chapter,
then we will work cooperatively to analyze and understand the use of the subject matter in organizations.
Systems
Development
Methodology
[Top]
You are expected to have completed the reading assignments prior to class and to participate in class
discussions.
We will follow the Systems Development Life Cycle (SDLC) methodology in our class. A methodology
includes the Models, Tools and Techniques for systems development.
Models
We will use the Unified Modeling Language (UML) 2.0.
Tools




Microsoft Project 2007 or later for Project Management
Microsoft Visio Professional 2007 for UML modeling
MySQL 5.0 or later for data storage
Microsoft Office 2003 or later for project documents
Note that we do not have the time to explore in detail these tools. You must spent time outside class to learn
how to use these tools and complete the assigned work.
How to download the software tools?
The MIS area has subscription to the Microsoft Developer Network (MSDN), which give faculty and
students access to many titles of Microsoft software. Most of the software is downloadable, so there is
virtually no cost to you.
If you are interested, complete the http://www.csus.edu/indiv/v/velianitis/msdnaa.htm form and will prepare
you for access (must use your Saclink ID).
Please visit the following link to see a partial list of available software. http://msdn08.eacademy.com/elms/Storefront/Home.aspx?campus=csus_mis
Techniques
We will use specific techniques as guidelines for development activities or tasks (i.e.,
Economic Analysis Techniques and Interviewing Techniques). You can use your own techniques only after
prior approval.
2|Page
Systems
Development
Project [Top]
Exams [Top]
A Sacramento-area client has hired your project team to develop a web based Information System to
automate one or more business functions. You will conduct all activities and prepare all deliverable
products associated with the development process. At the conclusion of your study, you will prepare a
comprehensive, high-quality project report containing your results. You will also design and program a
working prototype model of your system using the programming language of your choice.
Details on this project can be found in the Assignments page.
I will give two in-class term examinations and one final. Each exam consists of twenty five multiple-choice
questions, ten identification questions and two essay questions. You will need a scantron form 882 to
answer the multiple-choice questions; I will provide you with paper for the identification and essay
questions. Examination material will be drawn from the textbook reading, any other assigned readings, and
class lectures and discussion. Emphasis will be placed on the conceptual understanding of the material and
NOT on memory alone. Understanding the application of the concepts will greatly enhance your grade.
No make-up examination will be given without the prior approval of the instructor. If you fail to take the
exam, without valid documentation, I will prepare a different exam which you will take at 75% of its grade
value.
Grading [Top] Final grades will be assigned according to the total points you have obtained through exams and group
homework assignments relative to the total possible number of points.
Assignment
Points
System Development Project
200
3 Term Exams
300
Total Points
500
Your grade is also affected by the number of unexcused absences. You are allowed to have 3 unexcused
absences. For each absence after your allowance, 10 points will be deducted. Note that absences are only
excused for a valid reasons (health problems, jury duty etc) and MUST be accompanied with
documentation (i.e., health center note with a phone number to call for questions) provided within a week of
returning to class.
Pluses and minuses will be awarded along the extremities (i.e., greater than 3% below the upper limit and
3|Page
less than 3% of the lower limit, respectively).
Based on the total points, your grades will be assigned as follows:
Academic
Dishonesty
Percent
Grade
90-100
A
80-89
B
70-79
C
60-69
D
0-59
F
Grading system may change for compelling reasons.
Unfortunately, the subject of academic dishonestly must be discussed for those who are inclined toward
such activities. The university's policy is discussed in the following paragraphs. Please, there is no need to
engage in any unethical behavior in this class! If you need help, my door is always open.
Academic dishonesty involves acts which may subvert or compromise the integrity of the educational
process of the university. Included is any act by which a student gains or attempts to gain an academic
advantage for him/herself, or another, by misrepresenting his/her, or another's work or by interfering with
the completion, submission, or evaluation of work. These include, but are not limited to, accomplishing or
attempting any of the following acts:








4|Page
Using any materials that are not authorized by the instructor for use during an examination.
Copying from another student's paper during an examination.
Collaborating (i.e., talking, passing notes and/or signals, etc.) during an examination with any other
person by giving or receiving information without specific permission of the instructor.
Stealing, buying or otherwise obtaining information about an unadministered examination.
Substituting for another person or permitting any other person to substitute for oneself to take an
examination.
Submitting another person's work as yours either in its original or altered form.
Giving someone else your work to fulfill his/her assignment.
Using the assignment of another class to fulfill an assignment for this class without authorized
consent of the instructor.

Plagiarizing
Violations of proper ethical conduct will NOT be tolerated. A failing semester grade will be assigned to all
involved parties (NO exceptions). Severe cases of academic dishonesty will be handled at the university
level.
If you are aware of any academic dishonesty, please notify me either personally (your identity will remain
confidential) or anonymously. Cheating devalues everyone's grade and degree, including your own.
Incomplete (I) An incomplete grade (I) will only be issued in accordance to College of Business Administration policy.
and
Among the conditions imposed by the instructor that must be met are: (1) a current passing grade (70
Unauthorized percent or better), (2) the successful completion of all prior assignments and exams, and (3) an unforeseen
Withdrawal
and unusual event beyond your control which prevents you from completing the semester, and can be
(WU) Grades documented and verified (employment-related events do not qualify). (4) An incomplete will only be
considered after it has been determined that a withdrawal (W) cannot be issued. If you do not meet (1)
through (4), you do not qualify for an incomplete. As stipulated by the University, an incomplete cannot be
assigned when it is necessary for the student to attend additional class meetings to complete the course
requirements.
Other
Unauthorized Withdrawal (WU) indicates that a student did not officially withdraw from the course but
failed to complete it. Among the conditions imposed by the instructor that must be met are: (1) a passing
grade (70 percent or better) at the time that the student stopped attending classes, (2) attendance stopped
before the 11th week of the semester. If you do not meet (1) and (2), you do not qualify for an unauthorized
withdrawal (WU) grade and as a result you will be assigned a failing (F) grade.
Laptop and cell phone regulation: No photographing, recording or text messaging is allowed without
permission of the instructor.
If you have a disability and require accommodations, you need to provide disability documentation to
SSWD, Lassen Hall 1008, (916) 278-6955. Please discuss your accommodation needs with me after class or
during my office hours early in the semester.
Schedule
5|Page
A disruptive student is a student who engages in classroom behavior that interferes with the process of
teaching and learning. If a student is disruptive to my class, I will follow the Procedures for dealing with
incidents of disruptive behavior described in the DEALING WITH INCIDENTS OF DISRUPTIVE
STUDENT BEHAVIOR IN THE CLASSROOM document
(http://www.csus.edu/umanual/student/UMD03250.htm).
Please look at our current semester's schedule.htm web page.
The above items of this syllabus are subject to change, update, or more specific interpretation: (i) material to be covered in the lectures, (ii) material
to be covered in the exams and exam format, (iii) the exact way of group collaboration for each project part, and (iv) the exact cutoff point (specific
second or third decimal) for every letter grade. Changes and updates will be posted on the WWW and announced in class ahead of time.
SCHEDULE
Date
Topic
Introduction - Syllabus, projects, MISA
Chapter
Deliverable
1/28
The World of the Information Systems Analyst
Approaches to System Development
1
2
2/4
The Analyst as a Project Manager
TC
3
Form Teams
Appendix A: Principles of Project Management
Appendix E: Guide to Using Microsoft Project
2/11
Appendix C: Calculating NPV, Payback Period and ROI
2/18
2/25
Confirm Project Feasibility & Select Projects
Beginning the Analysis: Investigating System Requirements
4
PS
5
SP
First Exam
Modeling System Requirements
3/4
Exercise: Class Diagrams
The Object-Oriented Approach to Requirements
3/11
7
Exercise: Use Case Diagrams
6|Page
Evaluating Alternatives for Requirements
8
3/18
3/25
4/1
BA
Object-Oriented Design: Principles
Spring Recess - Campus Closed
Cesar Chavez Holiday - Campus Closed
4/8
11
Second Exam
Elements of Systems Design
9
Object-Oriented Design: Use Case Realizations
12
4/22
Designing Databases
13
4/29
Designing the User Interface
14
5/6
5/13
SR Presentations
Review
4/15
SA
5/20
SPI and SR
Final Exam @ 5:15 pm
[Systems Development Project] [Project Deliverables]
SYSTEMS DEVELOPMENT PROJECT
OVERVIEW
A Sacramento-area client has hired your project team to develop a web based Information System which will automate one
or more business functions. You will conduct all activities and prepare all deliverable products associated with the
development process. At the conclusion of your study, you will prepare a comprehensive, high-quality project report
containing your results. You will also design and program a working prototype model of your system using the
programming language of your choice.
PROJECT INITIATION
Locate a company or agency that is interested in either automating a manually based information system or enhancing its
7|Page
current computer-based system. You may choose any type of organization (company or agency). If you choose a small
company, cover a fairly wide range of business functions. If you choose a medium- to large-sized company, confine your
scope to a more narrowly defined business application (e.g., customer billing and collection). It is better to have a deeper,
more comprehensive analysis of a narrow-sized application scope.
Explain to your client that your project team is willing to help them define their requirements and build a new system. They
can use your study for either custom development or software package selection. Your consulting services could easily cost
your client $20,000. You are willing to provide this service free in return for the client's cooperation for the project.
Perform a quick feasibility analysis to ensure that the potential project is viable and complete the SystemScope.doc. Here
are some things to consider:





Your Use Case Diagram must have at least three meaningful processes
Your project must result in deliverable software in one of the following forms:
o Automated replacement of current manual system
o Substantial reprogramming of an existing automated system
o New automated interface to be placed on existing automated system
o Other (by prior approval)
Your project must be web based (we will further discuss the architecture)
DBMS must be MySQL (unless the instructor approves a different DBMS)
I permit students to work on a project for their employer under the following assumptions:
o The entire group supports this project
o The client understands that the entire team will be involved in the development process (interviews, e-mail,
prototyping, programming, etc) and the client cannot be involved in assigning tasks for the group
o The student that works for the client, will not be the primary contact with that client
o This project is not part of the student's (who works for the client) regular work
ASSIGNMENT SUBMITTING STANDARDS FOR HARD COPIES
1.
2.
3.
4.
All assignments are due at the beginning of the class period.
Late assignments will NOT be accepted.
All assignments should include the cover letter statement (click for sample) as the first page of the document.
Unless otherwise stated, all printed documents should be single spaced, with 1 inch margins, and times new roman
11 font size.
5. Systems Recommendation (SR) reports should have spiral binding (see details below). On the inside of the back
cover of your document, attach an envelop that will contain single CD which contains all the submitted documents
8|Page
in an electronic format.
There will not be re-grading of your deliverables.
PROJECT DELIVERABLES
1. TEAM COMPOSITION (TC)
The MIS 160 teams will consist of 5 team members assigned one of the following roles:





Project Manager/Lead Systems Analyst
Database Developer/Administrator
Web Developer/Lead Programmer
Web Developer/Programmer
Network Designer/Administrator/Integrator
You will form groups in class on the specified date. I will provide you with the paper forms and you must complete the
names of the group members, phone numbers, class schedules, work schedules, and roles. You must also include the agreed
upon weekly team meeting times.
NOTE: Because you have a primary role, it does not mean that you will not be involved in activities outside your primary
role. You will be involved in all project activities but you are expected to lead in the activities within your primary role.
Other
In addition to the primary role, each developer must also assume a supporting role
Deliverables
1. An e-mail from the project manager with all the team member names, phone numbers, and e-mail addresses
2. Each team member's resume attached to the e-mail
Grading
Note that this deliverable will not be graded.
9|Page
2. PROJECT SCHEDULE (PS) - 20 points
Use the MS Project software to create this deliverable.
From the description of the project deliverables described in this document, create a project Gantt Chart to:




Include all deliverables described in this document (i.e., PS, SP) as summary activities.
o Beginning day for summary activities is the day after the previous deliverable is due. Ending day for
summary activities is the deliverable due date.
o Include all tasks within each summary activity. Should, at least, include all tasks that have deliverables.
For each task in the Gantt chart provide name of the developers responsible (2 developers should be assigned the
same task who will work together for the completion of the task) and the estimated time to complete this task.
Each deliverable is a milestone. You may include your own milestones.
Create a network diagram for your project.
Deliverable
E-mail me a softcopy of your project file. Note that I will give you an initial grade for this deliverable. After the end of the
semester you will submit the updated project file when you will receive the remaining PS points.
Grading
2.1 Gantt Chart
10
2.2 Resource Allocation 5
2.3 Network Diagram
5
3. SYSTEM PROPOSAL (SP) - 30 points
In this deliverable you will provide documentation related to the business analysis activities of your project.
Deliverable
Service Request
1. Name of Client Company or Organization, address, line of business, company contact, contact's phone number, and
10 | P a g e
2.
3.
4.
5.
6.
7.
8.
9.
contact's e-mail address
A description of how the project was initiated (provide the name of the project initiator)
A brief description of the problem/opportunity to be investigated
Anticipated business benefits
System capabilities
Indication of company size, geographical locations
Personnel (by type)
An organization chart for the part of the organization you are studying
Business transaction types and monthly volumes
Objectives
1. Statement of the mission/goal of the organization
2. Define 2-3 clear and measurable objectives for your proposed system (must support the mission/goal of the
organization)
Feasibility Study
1.
2.
3.
4.
Technical Feasibility
Economic Feasibility (MIS160EconomicAnalysis.xls)
Operational Feasibility
Schedule Feasibility
Note: When I review your proposal, I may require that you modify and resubmit it.
Grading
3.1 Project Scope (SR 1-5)
11 | P a g e
10
3.2 Company Information (SR 6-9)
2
3.3 Objectives
5
3.4 Technical Feasibility
2
3.5 Operational Feasibility
2
3.6 Schedule Feasibility
2
3.7 Economic Feasibility
7
4. BUSINESS ANALYSIS (BA) - 40 points
In this deliverable you will provide documentation related to the business analysis activities of your project.
Deliverable (submit 1 copy)
Business Analysis (BA) reports should have spiral binding and should include the items below:
Conduct of Analysis
1.
2.
3.
4.
5.
6.
7.
Analysis methods used
End-users contacted
Records, forms and reports analyzed
Processes observed
Problems encountered with data collection
Data collection instruments
Synopsis of interviews
User Requirements
1.
2.
3.
4.
5.
Customer expectations and requirements
Output requirements (specify type, layout, and frequency)
User training requirements
System Constraints (skills, technology, etc)
Business Constraints (time, funds, external factor constraints, etc)
Infrastructure Analysis
1.
2.
3.
4.
Hardware
Software
Networking
Standards
Grading
12 | P a g e
4.1 Conduct of Analysis
10
4.2 User Requirements
20
4.3 Infrastructure Analysis
10
5. SYSTEMS ANALYSIS (SA) - 45 points
In this deliverable you will provide documentation related to the systems analysis activities of your project.
Deliverable (submit 1 copy)
Systems Analysis (SA) reports should have spiral binding and should include the items below:
UML Diagrams of the Existing System
1.
2.
3.
4.
One Use Case Diagram which will show all processes
Detailed description of each use case in the Use Case Diagram
For each use case in the Use Case Diagram, create an Activity Diagram
Provide a list of the processing volumes/times for each activity in the Activity Diagram
UML Diagrams of the Proposed System
1.
2.
3.
4.
5.
One Use Case Diagram which will show all processes
Detailed description of each use case in the Use Case Diagram
For each use case in the Use Case Diagram, create an Activity Diagram
Design Level Class Diagrams
Design Level Sequence Diagrams
Grading
5.1 Use Cases of Existing System
5
5.2 Activity Diagrams of Existing System
5
5.3
13 | P a g e
Use Cases of Proposed System and their
descriptions
10
5.4 Activity Diagrams of Proposed System
5.5 Class Diagrams
5.6 Sequence Diagrams
5
15
5
6. SYSTEM PROTOTYPE & INTERFACE (SPI) - 30 points
Prototype and Interface Design
Build a working prototype of your system which will serve as the proof-of-concept. The prototype must include:
1.
2.
3.
4.
5.
6.
A MySQL database to store the data defined in your UML diagrams
The main GUI Interface
All sub-menus/interfaces needed by your system
One form (form should update one or more tables in your database)
One report generated by your system (soft or hard copy)
Installation and use instructions
Grading
6.1 Prototype GUI Interface
10
6.2 Prototype Database
10
6.3 Prototype Report
5
6.4 Installation and Use Instructions
5
7. SYSTEM RECOMMENDATION (SR) - 35 points
This document is addressed to your client and summarizes all your findings (includes all prior deliverables) and your
recommendations.
Systems Recommendation (SR) reports should have spiral binding (see details below). On the inside of the back cover of
your document, attach an envelop that will contain single CD which contains all the submitted documents in an electronic
format.
14 | P a g e
Deliverable
1. Transmittal Letter addressed to your client and includes your findings
2. Executive Summary that includes:
o Description of problems
o The proposed solution
o Summary of cost/benefit analysis of the proposed solution
o Implementation time frame of proposed solution (reference the Project Schedule as Appendix D)
o Outline of Systems Study
3. Detailed Results of Analysis (references corrected/updated Systems Proposal as Appendix A, corrected/updated
Business Analysis document as Appendix B and corrected/updated Systems Analysis Document as Appendix C)
4. Systems Alternatives (at least three different configurations)
o Design Architecture
o Hardware
o Software (all other types of software alternatives used to implement your system)
o Networking
5. Systems Analysts’ Recommendations
o Describe and support the recommended solution)
o Provide only an updated Present Value model. You must show all cost and benefits in detail. Assume 8%
rate. Create graphs for the economic analyses data. Use the NPV worksheet provided above.
6. Proposal Summary
PowerPoint Presentation Guidelines
Each team will make a short (10 to 12 minutes) project presentation as shown on the syllabus schedule. Each
presentation must provide the following:
1.
2.
3.
4.
5.
6.
Grading
15 | P a g e
Description of the problem
Proposed solution
Systems Analysts' Recommendations
Demonstration of the prototype
Printed output of the PowerPoint presentation (Handouts - 3 slides per page)
At least three (3) team members must actively participate in the presentation and all other non-active team
members must be available for questions
7.1 Transmittal Letter
3
7.2 Executive Summary
5
7.3 Detailed Results of Analysis
5
7.4 System Alternatives
5
7.5 Recommendations
5
7.6 Proposal Summary
2
7.7 Presentation
10
PEER EVALUATION
In the MIS workplace, you will be asked to evaluate your subordinates, your peers, and even your managers. In this class
you must complete the peer evaluation forms provided below.
../PeerEvaluationForm.xls
I will average the Percent Contribution over all forms submitted for each team member. This average will be used to
allocate project points for that team member. For example, if the team members feel an individual contributed 80% towards
the team project (all deliverables), then that individual will receive 80% times the total team points awarded for the
semester. If a team member fails to evaluate one or more of his/her peers, it will be assumed that the contribution was
100%.
GENERAL DOCUMENTS
System Change Request is a document (I will provide Word template to each group) with the purpose to record and control
all System Change Requests allowing the project team to improve the system. You must complete a System Change
Request for each change to your system design that was made after you submitted the deliverable.
ADVICE FOR A SUCCESSFUL PROJECT




16 | P a g e
Try to obtain a client that has a manual process that your team may automate.
The proposed automated system should be designed for a PC rather than a mainframe.
The sooner you can complete the information-gathering phase of the analysis, the more time you will have to devote
to the design phases of the project.
Try not to spend an excess amount of time on the diagrams.


17 | P a g e
Realize that doing everything, as a whole team is often slow and inefficient. Use whole-team meetings primarily for
brainstorming and coordinating sessions. Break the team up into smaller units, and delegate specific tasks to each of
these units. These smaller units of one or two members are more efficient in completing the project "milestones"
than trying to do it as the whole team.
One member should be designated as "quality control" person. She/he should scrutinize the specifications for
completeness. She/he should also check narrative pages using spell check and a grammar package (e.g.,
Grammartique).