CS 4365/8803-IEC
Introduction to Enterprise Computing

Spring 2009

 


Instructor: Calton Pu ( mailto:calton@cc.gatech.edu
Office: KACB 3334
Office hours: By Appointment. 

First TA: Younggyun Koh (young@cc)
Office hours: By Appointment.


Classes: Tu/Th, 1:35 – 2:55pm
Class room : KACB 1456

UPDATE : final project deliverables should be upload through t-square.

 


Description | Assignment | Announcement | Tentative Course Schedule | Grading | Projects | Additional Links

Description

CS 4365/8803-IEC Introduction to Enterprise Computing

This course studies the impact of information technology on enterprises, with emphasis on both theoretical foundations and practical examples.

  1. Elements of enterprise computing.  Three-tier client/server systems.  Simplified examples of web electronic commerce systems.
  2. Core technologies for enterprise computing.  Transaction processing techniques.  Serializability, concurrency control, crash recovery.   Online transaction processing (OLTP) monitors.  Distributed database management systems, practical examples.  Application servers, practical examples.
  3. Case studies of enterprise transformation due to new information technology: mission-critical transaction processing, Internet and electronic commerce, data mining and decision support, etc.
  4. New research topics and technologies of potential impact: security, trust, privacy, micropayments, etc.


The course material consists primarily of papers and lectures/discussions led by instructor(s).  There will be a self-proposed project that applies the concepts and techniques discussed in the class to electronic commerce scenarios.  The comments and grade on project proposal will serve as the midterm feedback.  


Assignment

Commentary requirement
There is no specific format for the commentary as long as you cover the main points, limitation and relate the paper to your personal knowledge and other topics. One possible format is
--------------------------------------------------------------------------------
Commentary
Paper: Name of the paper
First paragraph: summarize the main points of the pape
Second paragraph: point out the limitation of the paper
Third paragraph: Relate this paper to your personal knowledge or related topics.
--------------------------------------------------------------------------------
The commentary should fit into one page.

Date

Lecturer

Topic

Assigned Readings

Slides

Due Time

Submission E-mail Subject

1/6

Calton

Introduction to course

none

 

 

 

1/8

Deepal

Tutorial on Web Services

none

 

 

 

1/13

Calton

Web Service Composition Tutorial

Web Services QoS: External SLAs and Internal Policies Or: How do we deliver what we promise?

 

 

 

1/15

Calton

Giant Scale Services

Lessons from Giant-Scale Services

 

 

 

1/20

Gueyoung Jung

Workflow tutorial

Availability Measurement and Modeling for an Application Server

 

 

 

1/22

Simon

Elba Tutorial

 

 

 

 

1/27

Calton

Application Server Tutorial

The Deployer's Problem: Configuring Application Servers for Performance and Reliability

 

 

 

1/29

Calton

Application Server Details

 

 

 

 

2/3

Calton

Continual Queries, XWrap

Conquer: A Continual Query System for Update Monitoring in the WWW

 

 

 

2/5

Calton

Event/stream processing

 

 

 

 

2/6

Project Proposal Due

 

 

2/10

Calton

Transactions: Serializability, CC

Chapter 2

 

 

 

2/12

Calton

Crash recovery

Chapter 6

 

 

 

2/17

Calton

2PC and Distribution

A dynamic two-phase commit protocol for self-adapting services

 

 

 

2/19

Gueyoung

Tutorial on code generation

Clearwater

 

 

 

2/24

Calton

OLTP monitors/RTF

A Practical and Modular Method to Implement Exended Transaction Models

 

 

 

2/26

Calton

TP tutorial

Research Issues in Large Workflow Management Systems

 

 

 

3/3

Calton

Transaction Activity Model

Transactional Model Activity for E-Commerce

 

 

 

3/5

Calton

ERP: Cisco Case Study and Introduction to SAP/R3

ERP a Savior or Slayer of Enterprise Competitiveness

 

 

 

3/10

Calton

Open source (MySQL)

Strategic Sourcing with mySAP Supplier Relationship Management

 

 

 

3/12

Calton

Open source (JBoss)

JBoss

 

 

 

3/17

 

Spring Break!

 

 

 

 

3/17

 

Spring Break!

 

 

 

 

3/24

Calton

E-commerce Case Study

Towards Requirements-Driven Information Systems Engineering

 

 

 

3/26

Calton

Discussion on Enterprise Education

 

 

 

3/31

Jinpeng

Security

Invited lecture

 

 

 

4/2

E. Maciel

Intercontinental Exchange

Invited lecture

 

 

 

4/7

Calton

Denial of Information

 

 

 

 

4/9

Calton

EC details: digital payments

 

 

 

4/14

Project Presentations (See T-Square for schedule)

 

 

 

4/16

Project Presentations (See T-Square for schedule)

4/21

Project Presentations (See T-Square for schedule)

4/23

Project Presentations (See T-Square for schedule)

4/24

Project Reports and Package due. Upload through T-Square.

Grading

The main component of the course grade is the project (10% proposal, 20% final presentation, 50% concrete deliverables - see below).  The written commentaries on the papers and student participation form the remaining 20%.  Student presentation and discussion of research papers carry bonus points. 

 

Projects

The main deliverable of the course is a self-proposed project.  Students (individually or teams of maximum 3) will design, propose, and implement a project relevant to the enterprise computing theme.  Typically, this will be the construction of some system component supporting enterprise computing (e.g., electronic commerce or supply chain) or an enterprise application.  Other ideas are certainly possible.  You are encouraged to discuss your ideas with the instructor before proceeding to the proposal stage.  Since this is the first time the course is being offered, there are no previous examples of project proposals.  However, you may want to look at the project proposals for the course CS8803H (Sp’04) Advanced Internet Application Development (see <http://www.cc.gatech.edu/~lingliu/courses/cs8803/project>).  You may find examples that give you an idea of the format and length of typical project proposals.  Some ideas for projects follow.

  1. Mainstream EComm software.  (1.A) Download one of the application servers (e.g., WebLogic or Websphere) and use it to build an ecommerce service; run a simulated or real workload to evaluate its performance.  (1.B) Take an existing ecommerce service and implement it on a different platform (e.g., take a service based on Websphere and implement a subset on .NET), then compare their complexity and performance.  (1.C) Add support for wireless (e.g., cell phone) access to some ecommerce service.
  2. Research topics: (2.A) Evaluate the privacy guarantees given by various ecommerce sites and how they are implemented.  (2.B) Evaluate the strategies the large ecommerce sites are using to defend themselves against denial-of-service attacks. 

Exceptional projects may be expanded as research projects for additional credit.

Project Requirement

Project Reports
Report
You will need to submit a project report as a capstone to your project work for this course. The report ties together your contributions and serves as a "map" or "root document" to guide us through the corpus of your group's work. We will use the requirements from last Spring's 8803 Internet Applications course (here).
Content: Your report should include the objectives of your project, the research problems you are addressing, the approach/methods you took for evaluation of your results, the architecture and functional components of your prototype system, three most interesting contributions of your project design and/or implementation. (Much of this can come from your proposal.) You are also expected to summarize

  1. what you have learned through the hand-on experience of doing this project, and
  2. what concepts and techniques you learned in class are used in the current project design,
  3. and (c) what concepts and techniques you learned in class can be considered for extension of your current project.

Format: I expect the report to be well written and documented with references. The presentation style and quality (syntax and grammar) are an important part of the evaluation and grading of your final project. As the length of the reports, there is no specific rules, and quality is more important than quantity. However, as a general guideline we'll be expecting report lengths of 5 to 10 pages.

Project Signup

Please use T-Square or e-mail young@cc.gatech.edu to sign up.