CmpE 272: Enterprise Software Overview
(Fall 2008)

Course Description

This course introduces the major concepts and technologies that arise in the design and implementation of enterprise software systems. Issues including architectural decision, enabling technologies and software integration will be discussed. By the end of this course, you will be familiar with the technologies related to middleware, OSs, SQL database, XML, distributed objects, Web-based development, SOA, etc. This course will prepare you for other Enterprise Software Technologies classes with the necessary knowledge spectrum.

Learning outcomes

1) Understand different software architecture models of enterprise software systems and can make architectural decision according to different system requirements.
2) Be able to identify available technologies for a design/implementation need.
3) Know the strength and weakness of different technologies and be able to choose the right ones according to different requirements.
4) Be familiar with emerging software design paradigm and technologies.

Prerequisites

Admission to the MS Software Engineering program or instructor consent.

Textbook

• Required textbook (short for “C” in the syllabus):
  Client/Server Survival Guide, Third Edition, by Robert Orfali, Dan Harkey, and Jeri Edwards (Wiley, 1999).
• Reference textbook (short for “S” in the syllabus):
  Enterprise SOA: Service-oriented Architecture Best Practices, Dirk Krafzig, Karl Banke, and Dirk Slama, Prentice-Hall Inc., 2004
• Lecture notes and other reading materials posted on the course website.

Syllabus

Resources:

• IEEE and ACM digital library. Go to the university subscription page and click "IEEE Xplore" and "ACM Digital LIbrary" to get free access to publications.

Class Structure:

This class is based on weekly lectures. All the assignments must be submitted at the beginning of lectures. In-class activities include quizzes, surveys and short presentations (tentative).

Grading Policy

Grades will be assigned on a curve. Your final grade will be based on assignments, exams, and class participation. These will be weighted as follows.

• The instructor reserves the right to change the percentages listed above by ±5%
• No late submission will be accepted unless a written evidence such as a physician's letter is accompanied with the request for late submission.

Description of assignments:

• Class participation: Participation in classroom discussion and other in-class written assignments. Students may be required to give short presentations based on assigned papers or to demonstrate software related to the lecture topics.
• Quizzes: Quizzes will be given to students during lectures. Questions may include explanation to terms, comparison between different design, evaluation of data structures, or coding.
• Exams: There are two written exams: one midterm exam and one final exam. Exams contain multiple choice and paragraphs questions.
• Project: Students will work in groups on a semester-long project. The project counts for 30% toward your final grade. The purpose of the project is encouraging you to explore the area of Enterprise Software Engineering, strengthen your understanding, and bring your new findings to the class. You will be required to give a presentation and submit project documents that include a project proposal, a progress report and a final report.

Academic Honesty

Your own commitment to learning, as evidenced by your enrollment at San Jose State University, and the University’s Integrity Policy, require you to be honest in all your academic course work. Faculty members are required to report all infractions to the office of Judicial Affairs. The policy on academic integrity can be found at:

http://sa.sjsu.edu/judicial_affairs/index.html

Things (among many others) you may not do when working with other students (not applicable to team work):

• The term “solution” mentioned below anything (code, design document, description, etc.) you will submit for assignments and exams.
• Work on an assignment together, type in solutions (separately or together) and turn in separate copies.
• Each works on a part of an assignment and turn in separate copies after combining solutions.
• Give any part of your solution (through paper, board writing, email, web posting, reading loud, letting someone else look at your screen, etc.) to other students before the assignment deadline.

Things you may do when working with other students:

• Discuss with other students and leave the discussion with empty hands.
• Share assignment solutions after the assignment deadline in order to compare different techniques used for solving the problems.

Plagiarism

San José State University defines plagiarism as the act of representing the work of another as one's
own without giving appropriate credit, regardless of how that work was obtained, and submitting it to
fulfill academic requirements.
Plagiarism includes:

1.2.1 Knowingly or unknowingly incorporating the ideas, words, sentences, paragraphs, or parts
of, or the specific substance of another's work, without giving appropriate credit, and
representing the product as one's own work;
1.2.2 Representing another’s artistic/scholarly works such as musical compositions, computer programs, photographs, paintings, drawing, sculptures, or similar works as one's own.

Note:

• Copying online content without correct quote is treated as plagiarism in this class.
• Both the person who copies and the person who facilitates the copying will be prosecuted for academic dishonesty.
  

Accommodation for Disabilities

If you need course adaptations or accommodations because of a disability, or if you need special arrangements in case the building must be evacuated, please make an appointment with me as soon as possible, or see me during office hours. Presidential Directive 97-03 requires that students with disabilities requesting accommodations must register with DRC to establish a record of their disability.