CIS 3310: SYSTEMS DESIGN (with the CIS Common Case Crabgrass Books)

Course Prerequisites

CSP 1, CIS 3300 and a Programming Track (CIS 3260, CIS 3280 or CIS 3260, CIS 3270 or CIS 3210, CIS 3215). The programming track requirement went into effect at the start of the Fall 2001 Semester. 

Prerequisites are strictly enforced!

Students who have not fulfilled these requirements are subject to removal from the class.

Additionally, it is assumed that the students have some familiarity working with computers. Specifically, it is assumed that students be able to, or will learn outside of class, the following:

• Principles of Programming,
• An object oriented programming language or Integrated Development Environment,
• creation of web documents,
• the syntax of Java and J2EE OR any Microsoft .NET’s Object Oriented web application development languages (C++, C#, VB.NET)
• Use of MS Office or similar tool to write business reports, academic papers and specification documents.
• Additionally, it is expected that students will quickly learn how to
  • use email and a browser,
  • to set up a website and load/download files there from,
  • newsgroups and,
  • how to work effectively in groups

Primary Text and Software 

• Bernd Oestereich, Developing Software with UML. Object-Oriented Analysis and Design in Practice, Addison Wesley, 2002 (ISBN 0-201-75603-X). 
• Boggs, W. and Boggs, M., Mastering UML with Rational Rose, Sybex, 1999 (ISBN0-7821-2453-4)
• Rational Rose Enterprise Suite: Available from course’s rational rose web site

Additional Helpful Resources/Material

FOR THE .NET ENTHUSIASTS

• Visual Studio .NET, Professional Edition for Academic Market, Microsoft Corporation. Available for FREE download through the CIS Department's MSDNAA program (Strongly recommended for groups that will be using .NET to complete course project). You MUST be a CIS major to qualify for this edition.  Sign up for the MSDNAA program at: http://www2.cis.gsu.edu/cis/student/sn.asp. 

FOR THE JAVA ENTHUSIASTS

• A java software development kit
• An integrated development environment for Java e.g. Netbeans 3.0, JWSDK (Java Web Services Development Kit). Available for free from http://java.sun.com ; IBM Websphere studio, etc.  OR A simple editor for Java programs e.g. TextPad, Jcreator, etc.

Catalog Description

The general description of this course can be obtained in the University’s Undergraduate Catalog:

http://www.gsu.edu/~wwwreg/0304undergrad/images/undergradcatalog0304.pdf

Prerequisite:

CIS 3300 and completion of a CIS programming track (CIS 3260 and CIS 3280, or CIS 3260 and CIS 8270, or CIS 3210 and CIS 3215). CSP 1. This course builds upon the skills and knowledge developed in CIS 3300. Emphasis is placed upon the design and development of information systems, including the software and databases that are needed to support the business needs of the organization. Both data-oriented and process-oriented design methods are covered. These methods are discussed in the context of managing a systems development project, including issues such as project estimation and project management techniques, software quality assurance, and configuration management.

Detailed Course Description:

This course provides an introduction to the logical and physical design of computer based information systems. Emphasis is placed on object-oriented development paradigms for the design of business information systems.  The course extensively utilizes the CIS Common Case suite (CISCC) and, in particular, the Crabgrass Books case as a known context from which students extend their knowledge of all topics covered in the course. 

The focus of this course involves the use of a persistence framework to transition from UML classes to distributed web applications using Sun’s J2EE/J2SE framework or Microsoft’s .NET frameworks. The principles learned can also be applied to other leading frameworks for building distributed enterprise software. 

Information systems development is a process in which technical, organizational, and human aspects of a system are analyzed and changed with the goal of creating an improved system. In spite of the advanced technologies that surround computer-based information systems, the process of systems analysis and design is still largely an art. There is a high dependency on the skills of the individual analysts and designers even though there are established principles, methods, and tools. This course will give students an understanding of the most common tools, techniques, and theories currently used in systems design.

Detailed Course Objectives


At the end of the semester, the student will be able to:

• Read an Analysis Document for design
• Use a Persistence Framework in the Design of an Information System
• Create and document a Logical Design
• Create and document a Physical Design
• Create and document an Application Database
• Use a CASE tool to assist in systems design
• Create a commonly expected “deliverables” of systems design
• Determine the architecture and technology requirements for implementation of a system’s design
• Implement a system’s blue-print as a working information system

Conduct of Course: Lecture/Discussions, Demos, and Labs:

Class sessions will be divided between: (1) lecture/discussion of certain software concepts and features, (2) instructor demonstrations of these same software concepts and features, and (3) student laboratory sessions working with these same software concepts and features.

The purpose of this pedagogical approach is to introduce and reinforce ideas and skill sets so that students can master these on their own after class hours. To bring this knowledge to a highly proficient, professional level, students will have to spend time and effort outside of class working in the GSU computer labs or on their own micros.

To ensure that you have the basic knowledge that will allow you to function on your own after class, be sure to ask the instructor questions during class, either during the lecture/discussion, demo, or lab.

Course Project:

For the course project, students, working in groups of three, will prepare fully functioning distributed applications that address a typical business need. The application will be of significant complexity and will be developed in any of the .NET programming languages or in Java’s J2EE framework.  The complete specifications for the projects will be covered in a separate handout.

Each member of a project team shall work on a separate, well defined portion of the design problem. The entire team’s solution is expected to be synchronized and integrated (For, example, team must use common vocabulary for classes, attributes, methods etc. and the design diagrams they create must be interrelated). There will be points for the individual parts designed by each team member, and separate points for the quality of the entire team’s integrated solution. Therefore it is possible for members within the same group to earn different grades on the project.

All parts of the project shall be submitted electronically by posting your group’s solution to your web site by the due date. Each group MUST use a web site that can adequately deploy the web-application in the framework/programming-platform that each initially selects for the project. Therefore, (1) groups using .NET must find web space on a server that has been configured for deployment of .NET applications and components; while (2) groups using J2EE/J2SE must locate space on a server that is configured to host servlets, java beans, jsps, conventional java programs and applets.

CIS TUTORS are available in RCB suite 822 for assistance with issues relating to software installation; program debugging; and, the use of Rational Rose to draw design models for the project’s solution. You can get details about the CIS TUTOR program at http://www2.cis.gsu.edu/cis/tutors/index.asp.  NOTE: Tutors will not do your assignments/project for you!

All work must be your own.  Duplicate project submissions will be given a grade of "zero".  ALL members of both the teams copying the assignment and the teams supplying the copy will be penalized equally!

Quizzes/Homeworks

A maximum of 5 take-home quizzes shall be administered in the duration of the course. Each student’s best 4 quiz scores shall count towards course credit for the calculation of the final grade.  Quizzes will be posted on the course web site three days prior to the due date. Therefore quizzes due on Wednesdays shall be posted the prior Sunday in the evening.

Quizzes MUST be submitted IN CLASS on the due date. They will be collected at the start of class. Only Paper copies (hard-copies) of the quizzes will be accepted. Therefore print your quiz (making sure that your script contains your name, and that all questions answered are adequately numbered) BEFORE coming to class.

Policies

Grading Policy:

Policies on Student Conduct and Academic Honesty

• Prerequisites are strictly enforced. Students failing to complete a prerequisites with a grade of “C” or higher will be administratively withdrawn from the course in which they are in violation with a loss of tuition fees. There are no exceptions.
• Students are expected to attend all classes and group meetings, except when precluded by emergencies, religious holidays or bona fide extenuating circumstances.  If one or more class is missed, it is the student's responsibility to determine the specific material covered during their absence and make the necessary arrangements for making up what is missed.  Class discussion is strongly encouraged.  More than two missed classes in a row without the instructor's permission will be considered a withdrawal on the part of the student. 
• Make-up assignments will not be given for any reason whatsoever. 
• Students who, for non-academic reasons beyond their control, are unable to meet the full requirements of the course should notify the instructor. Incompletes may be given if a student has ONE AND ONLY ONE outstanding assignment.
• A “W” grade will be assigned if a student withdraws before mid-semester while maintaining a passing grade. Withdrawals after the mid-semester date will result in a grade of “WF”. Refer to GSU catalog or Registrar’s office for details.
• Spirited class participation is encouraged and informed discussion in class is expected. This requires completing readings and assignments before class.
• Unless specifically stated by the instructor, all assignments and teaching examples are to be completed by the student alone.
• Within group collaboration is allowed on project work. Collaboration between project groups will be considered cheating unless specifically allowed by an instructor.
• Copy work from the Internet without a proper reference and citation will be considered plagiarism and subject to disciplinary action as delineated in the Student Handbook.
• Any non-authorized collaboration will be considered cheating and the student(s) involved will have an Academic Dishonesty charge completed by the instructor and placed on file in the Dean’s office and the CIS Department. All instructors regardless of the type of assignment will apply this Academic Dishonesty policy equally to all students. See excerpt from the Student Handbook below:

Academic Honesty

(Abstracted from GSU’s Student Handbook Student Code of Conduct “Policy on Academic Honesty and Procedures for Resolving Matters of Academic Honesty” - http://www.gsu.edu/~wwwcam/academichonesty.html)

“As members of the academic community, students are expected to recognize and uphold standards of intellectual and academic integrity. The University assumes as a basic and minimum standard of conduct in academic matters that students be honest and that they submit for credit only the products of their own efforts. Both the ideals of scholarship and the need for fairness require that all dishonest work be rejected as a basis for academic credit. They also require that students refrain from any and all forms of dishonorable or unethical conduct related to their academic work.

Students are expected to discuss with faculty the expectations regarding course assignments and standards of conduct. Here are some examples and definitions that clarify the standards by which academic honesty and academically honorable conduct are judged at GSU.

Plagiarism. Plagiarism is presenting another person’s work as one’s own. Plagiarism includes any paraphrasing or summarizing of the works of another person without acknowledgment, including the submitting of another student’s work as one’s own. Plagiarism frequently involves a failure to acknowledge in the text, notes, or footnotes the quotation of the paragraphs, sentences, or even a few phrases written or spoken by someone else. The submission of research or completed papers or projects by someone else is plagiarism, as is the unacknowledged use of research sources gathered by someone else when that use is specifically forbidden by the faculty member. Failure to indicate the extent and nature of one’s reliance on other sources is also a form of plagiarism. Failure to indicate the extent and nature of one’s reliance on other sources is also a form of plagiarism. Any work, in whole or part, taken from the internet or other computer based resource without properly referencing the source (for example, the URL) is considered plagiarism. A complete reference is required in order that all parties may locate and view the original source. Finally, there may be forms of plagiarism that are unique to an individual discipline or course, examples of which should be provided in advance by the faculty member. The student is responsible for understanding the legitimate use of sources, the appropriate ways of acknowledging academic, scholarly or creative indebtedness, and the consequences of violating this responsibility.

Cheating on Examinations. Cheating on examinations involves giving or receiving unauthorized help before, during, or after an examination. Examples of unauthorized help include the use of notes, texts, or “crib sheets” during an examination (unless specifically approved by the faculty member), or sharing information with another student during an examination (unless specifically approved by the faculty member). Other examples include intentionally allowing another student to view one’s own examination and collaboration before or after an examination if such collaboration is specifically forbidden by the faculty member.

Unauthorized Collaboration. Submission for academic credit of a work product, or a part thereof, represented as its being one’s own effort, which has been developed in substantial collaboration with assistance from another person or source, or computer honesty. It is also a violation of academic honesty knowingly to provide such assistance. Collaborative work specifically authorized by a faculty member is allowed.”

Typical Schedule