Marking scheme for the course
|COURSE COMPONENT||WEIGHT||DUE DATE|
|Business assignment||20%||May 14|
|Technology assignment||20%||June 19|
|Policy assignment||20%||July 18|
|Project||40%||August 31 (new! it was July 30 before)|
For detailed information on assignments, please check the web page of the respective module.
Please direct questions on assignments to the coordinator of the corresponding module.
Questions on the project should be directed to the course coordinator, A. Rau-Chaplin.
Submission of the business assignment will be by email attachment to Prof. Sunny Marche.
All remaining submissions (technology and policy assignment, and the project) will be electronic, in hyptertext (HTML) format, that you will publish on your password-protected group web site on borg.cs.dal.ca.
For instructions on how to use your Dalhousie account, please check AccountsHelp.txt
According to University regulations, all users of university computing facilities are bound by the rules stated in Appendix I (Guide to Responsible Computing) of the document shown here.
If you have any technical questions having to do with your account, the posting of your assignments, password protection of your site, or access to the on-line digital libraries, you should contact the Help desk of the Faculty of Computer Science, Dalhousie University. The Help Desk e-mail address is email@example.com and their telephone number is (902) 494-2593.
If you have any questions on the subject matter of the assignments, you should contact the instructor closest to the subject of your question. If you are unsure about who to ask, send email to firstname.lastname@example.org
Team up with your classmates into groups of size 3. The perfect team has people with technical, business and legal/policy backgrounds.
Agree on a topic for your case study. Ideally the topic should be your own organization and how
it can incorporate e-commerce (or e-business or e-services) in its operations. You should address this topic from
three viewpoints, technical, policy and business.
We would like to make the project useful to you, as well as to us. To this end, you may want to make your project relevant to your department (i.e. the department of one of the members of your group), and make it as "real" as possible. Perhaps it can form the basis for a real business case that you may want to propose to your department head for implementation in the near future.
As a rough length guideline, your project report should be about 30 pages typed, 1.5 spaced, point size 11. Feel free to generate a shorter of a longer report, if necessary or appropriate for your project.
Consider carefully the scope of your project. If you make the scope too broad, the project may
end up too superficial. If you make the scope too narrow, it may be less interesting, or give you less issues to
To ease collaboration within the group, you may wish to maintain an evolving draft of your report on your group web site as you work on it.