OFFICE HOURS: Before class and by appointment

COURSE APPROACH: The development of electronic commerce and other Web-based systems is not simply a specialized programming venture. It is a critical endeavor that crosses multiple functional areas in a business. Similarly, e-commerce systems development is not the domain of any one functional area, but a multidisciplinary process that requires coordination, communication, and integration. This course will exploit the management of technology and computer science link by creating cross-disciplinary teams involving both academic programs. Students will work with fellow team members to apply the necessary skills to develop an electronic commerce system from the conceptual idea phase to implementing the infrastructure.

SPONSORED PROECTS: Multiple projects will be developed during the semester. Each 4-6 person team will be assigned to work on a project sponsored by industry. Team members will be expected to coordinate with the project manager from the corresponding firm.

ACADEMIC INTEGRITY: Students are expected to work within the letter and spirit of the NCSU Code of Student Contact. The code can be found at http://www.fis.ncsu.edu/ncsulegal/41.03-codeof.htm

STUDENTS WITH DISABILITIES: If you have a disability that may affect your participation in this class, please contact the NC State Disability Services for Students. Their office is in 2000 Harris; information also can be found at
http://www.ncsu.edu/provost/offices/affirm_action/dss/

 EVALUATION PROCEDURE:

• Iteration #0: The documentation produced in Iteration #0 documents your organizational structure and lays the groundwork for the project. Project documentation is due according to the schedule. The evolution of these documents will be the subject of many of the early weekly meetings. Additionally, teams may want an opportunity to revise these documents based upon instructor feedback. Therefore, teams can submit a revised document according to the schedule. The final grade recorded for the deliverable will be an average of the two grades.
• Iteration #1: Teams will divide their project into two iterations. For each iteration, requirements, a test plan, and a design will be submitted for that iteration, including an update/revision of what has occurred in prior iterations. If the project invovles a business plan, this document is also evolved in three phases. These documents are due according to the schedule. Weekly Risk Assessment Forms must be turned in. A partial working system based on iteration requirements will be demonstrated.
• Iteration #2 and Final Presentation:For each iteration, requirements, a test plan, and a design will be submitted for that iteration, including an update/revision of what has occurred in prior iterations. Documentation for the iteration is submitted according to the schedule. Final submission list includes:
• 2 Sets of CD's of the following for the professors--
  • Graded documentation [the versions of each iterations plus the final documentation] and all RAF [Risk Assessment Forms]
  • All code and any file needed to run your code.
  • Readme file explaining what is on the CD and how to setup everything.
  • Final Presentation [ppt] slides
  • Lessons Learned document
• 1 or more sets of CD's for customer which includes--
  • Final versions of all graded Documents excluding RAF'S
  • All code and any additional files needed to run the code
  • Readme file eExplaining what is on the CD and how to setup.

  There will be a 15-minute final presentation for all the sponsors. The team will choose which students will make the presentation to best represent your team.You will also demo your project to the instructors and to your sponsor.Every team member must participate in this demo.

• Peer Evaluation, Attendance, and Class Participation: Attendance is mandatory for all students for the entire class period. You are expected to do your fair share of the work on your team.Based on input from peer evaluation, your attendance, and your class participation, the instructors may assign different grades to members of the same team. If it is apparent to the instructors that a particular student's actions and behavior will compromise the success of the team, he/she may be asked to drop the course.