College of Business Administration
Semester Course Syllabus
Spring 2006
COURSE PREFIX/TITLE: CIS 4600 Advanced Systems Development
INSTRUCTOR: Jack Russell, Ph.D., CCP
Office: 114F Russell Hall
Phone: 357-5751
Office Hours: Posted and by Appointment
E-Mail: jrussell@nsula.edu
REQUIRED TEXT AND MATERIALS
Systems Analysis & Design, Second Edition or Third Edition Alan Dennis and Barbara Wixom, ISBN
0-471-07322-9, Copyright 2003, Wiley (this is the same text also used in CIS 3900)
Systems Analysis & Design An Object-Oriented Approach with UML Dennis, Wixom, and Tegarden, ISBN 0-471-41387-9 [the book used in the Object-Oriented Analysis 4200 class.
SA&D PowerPoint slides found on Blackboard under Course Contents.
Course Assignments found on Blackboard under Assignments.
USB Jump Disks– Get 2 disks --One zip or jump disk to store all of your assignments and solutions. A second zip disk should be available as a backup.
CATALOG COURSE DESCRIPTION
(3-3-0) A capstone, project-oriented study of the planning, analysis, design and implementation of a business system using model-based software tools and other development platforms. Much attention is given to communication and teaming skills. Student teams will be given a user-request for development. Deliverables include: 1) user interviews, 2) project plan, 3) feasibility study and cost-benefit analysis, 4) business model, 5) interface design, 6) database design, 7) program design and 8) program functionality of a sub-system. A final project presentation by each student team will be required. Prerequisite: CIS 3900 and last semester senior standing.
DETAILED COURSE DESCRIPTION
This course is the capstone experience in information systems. It is to be taken during the CIS student’s last semester prior to graduation. A student must have taken an introductory Systems Analysis and Design course prior to signing up for this class. Prior background in systems analysis concepts and basic business modeling, database design and an advanced programming language is assumed.
The focus of this course is on the entire software development process including planning, analysis, design and implementation of a business system. The purpose of the course is to insure that a student participates in all phases of a business system project including the data collection, feasibility analysis, business modeling, GUI and web interface design, data base design, decision tables, program design and program implementation. This course will also concentrate on more advanced concepts of business modeling as well as review what you have previously learned. The purpose of this is to make sure students are competent in business modeling techniques which is one of the most sought after skills by industry.
This course is project-driven and team-oriented. This means that students will work as team participants working with their respective team members. Participants will have an opportunity to exercise the project management techniques and skills acquired in the first SA&D course.
Students will be provided with a semester problem statement that will include a set of deliverables that they are expected to turn in or present for the semester. The student’s professor will hopefully offer inspiration and motivation and many necessary skill-sets, but it is the student’s responsibility to be a self-starter and be willing to work effectively within a team environment. This is a senior-level capstone class, and students are expected to perform and behave in a professional manner. Your grade will depend on it since a portion of the grade is associated with both individual effort and team performance. An evaluation will be required from each student for each individual on the team. In other words, each member evaluates each person’s performance; therefore, everyone must “pull their own weight.”
GOALS AND OBJECTIVES
Goals:
1. To provide the prospective graduating senior with a comprehensive experience in exercising both their business skills and computer competencies in a realistic business project.
2. To enable the student to gain experience in conducting data collection interviews, enhancing proposal writing skills and making oral presentations in front of the class.
3. Completing all four phases of a systems project.
Performance Objectives:
1. Complete a series of entity relationship diagrams to comprehend structured analysis data modeling methods.. Some are advanced in nature.
2. Complete a series of data flow diagramming exercises to comprehend structured process modeling. Some are advanced in nature.
3. Complete a series of class diagrams, “use case” diagrams, sequence and state chart diagrams for a review of the object-oriented analysis paradigm.
4. Conduct a “mock” data collection interview based on the semester project narrative.
5. Participate as a team member in a semester project.
6. Complete a feasibility analysis and report. This will include a payback analysis also.
7. Complete the ERD for the semester project’s business narrative using Visible Analyst [structured approach].
8. Complete a Class Diagram for the semester project’s business narrative using Visible Analyst [OOA approach].
9. Complete the Decomposition Diagram and Data Flow Diagrams for the business narrative using Visible Analyst.
10. Complete a Use Case Diagram that is equivalent to the Decomp and DFDs.
11. Compose and Present the Proposal to Perform Systems Design.
12. Design the business system. The deliverables will include: graphical user interface design, navigation design, database design and program design. For an OOA approach: Design sequence diagrams for each use case, and a state chart diagram for each volatile class prior to developing action diagrams.
13. Develop the code for the program design using an acceptable development platform. VB.Net is suggested since we have this in the labs.
TOPICS TO BE COVERED
1.) The student will complete a series of entity relationship diagrams using various CASE tools.
2.) The student will complete a series of “structured analysis” business process modeling (Decomp and DFD) exercises.
3.) The student will complete a series of “object-oriented analysis” business model using “use case” and class diagramming.
4.) The student will be given a semester project problem statement and will be asked to collect data through surveys and interviews.
5.) The student will become a part of a project team and their initial responsibility will be to perform a feasibility analysis and present the feasibility report to the class. This feasibility report will consist of two parts: a.) a formal “hard copy” document submitted to the teacher, b) A Power Point slide show delivered in class.
6.) The student will participate with his/her team in modeling the business (ERD, Decomposition Diagram, DFDs).
7.) The teams will design the system. This design will include: GUI/web interface design, navigation design, database design and program design.
8.) The student teams will produce a partial implementation (construction) of the applications using a software development platform. The construction or implementation of the project will completed using any acceptable development platform.
9.)
COURSE REQUIREMENTS AND POLICIES
1. The student should attend class regularly unless excused by the professor. A student with NO ABSENSES will be awarded TWO EXTRA semester points. In other words, if your semester average is 88 then your final semester average is 90 instead.
2. The various assignments are due at the beginning of each class; therefore, it is not wise to miss class simply because you failed to complete an assignment. Since the assignment is already late you are encouraged to attend class and work on the assignment after class.
GRADING:
Mid-Term Exam (Business Modeling) 10%
Business Modeling Assignments 10%
Peer Evaluation Score 10%
Interviews: (average of team grade and individual grade) 10%
Feasibility Study& Proposal Hardcopy Document 10%
Feasibility Study& Proposal Individual Standup Presentation 10%
Functional Program Code (functionality) 10%
Final Project Documentation: Design Specification
(includes interface, database and program design) 10%
Final Project Individual Presentation 10%
Final Exam 10%
Total 100%
ACADEMIC DISHONESTY
Academic Dishonesty will not be tolerated. Students guilty of academic dishonesty will be reported to the College Dean and recommended for dismissal from the course and/or college.
Assignments or exams brought into question related to academic dishonesty will be scored as zero. A student caught cheating on an exam will be given a zero for that exam. Any home work assignment copied from someone else will be graded as zero. When the teacher is unable to distinguish from original and copied work then the teacher will award all students involved a letter grade of zero for that work. It is incumbent upon students to disassociate themselves from perilous situations that could bring into question their integrity.
Plagiarism:
Copying another student’s homework, computer program, business model, web site, database and so forth is considered plagiarism. Students are expected to always do their own assignments themselves. The overused expression, “we worked on it together” is not acceptable. If you work with another student on homework it is your responsibility to insure that the work that you do is a “signature” of your own work and no one else’s work. When a teacher grades an assignment and can detect obvious elements of cheating or copying then the assignment, project, or exam will be labeled “plagiarism.” It is your responsibility to not be involved in plagiarism. Students guilty of plagiarism can be recommended for class dismissal. Severe cases of plagiarism can result in dismissal from the university.
Software Theft:
A student guilty of software theft will be recommended to the dean for removal from my class and from the College of Business. Software theft is defined as any act connected to copying another student’s program, copying university system software, network software, and university software applications connected to university alliances and partnerships.
SPECIAL NEEDS
It is the policy of NSU to accommodate students with disabilities, pursuant to federal law, state law, and the University's commitment to educational opportunities. Any student with a disability, who needs accommodation, for example in seating placement of arrangements for examinations, should inform the instructor at the beginning of the course. Students with disabilities are encouraged to contact Services for Students with Disabilities, second floor of Kyser Hall, Steve Hicks, extension 5000.
CLASSROOM CIVILITY STATEMENT:
Each Northwestern State University student is encouraged to help create an environment that promotes learning, dignity, and mutual respect for everyone in the learning environment. Students who speak at inappropriate times, take frequent breaks, interrupt the class by coming to class late or leaving early, engage in loud or distracting behaviors, use cell phones or pagers (other noise-making devices like watches with alarms), listen to headphones/CDs, play with computers or hand held games, use inappropriate language, are verbally abusive, display defiance or disrespect to others, or behave aggressively toward others during the class period may be asked to leave the class and subjected to disciplinary action under the Northwestern State University Student Code of Conduct and Sanctions (Article VII Sanctions). The instructor of a course may deem additional behaviors or actions inappropriate; these action or behaviors will be outlined in the course syllabus. Copies of the infractions and sanctions are available on the NSU web sits at http://www.nsula.edu/studenhandbook/page100.htm.
POLICY ON ACCEPTING LATE ASSIGNMENTS:
Point deductions will apply when an assignment is turned in after the beginning of the class period when the assignment is due. This means that after the class starts the assignment is just as late as if the student turned it in later in the day. It is wise to not skip class to work on a late assignment since this further detracts from the learning process.
This point deduction policy will be strictly enforced. Unless you have documented extenuating circumstances beyond your control then the point deduction below will apply. If you believe you have had an extenuating circumstance then please email or phone me immediately. I will consider the information you provide in determining point deduction.
Please do not embarrass yourself by turning in work later than described below in hopes I will be lenient. It will not be graded. I will turn it back with a zero or no grade. Nothing personal. These are rules and policies that must be followed to be fair to everyone.
Situation Number Points Deducted
|
Turned in on time at the beginning of the class |
0 points deducted |
|
Turned in same day but after beginning of class |
10 points deducted |
|
Turned in on 2nd Day before 5:00 PM |
20 points deducted |
|
Assignments turned in after the 2nd Day |
Not accepted without special permission from instructor. Prior notice of reason must be agreed upon. |
If you are aware of an extenuating circumstance or other uncontrollable situation please document this circumstance or situation and notify the professor prior to the due date. The professor will make an evaluation on whether to not apply the point deduction above. Any reason must be documented in writing, and it cannot be an oral comment. Missing class is no excuse for not turning in an assignment on time. If you know you have to miss class then submit assignment early by placing the assignment in the Drop Box or sliding it under the professor’s door.