E-Commerce Education and the Development of Digital Business Skills

Abstract

E-commerce education has always carried a difficult curriculum burden: it must prepare graduates to implement technical systems and to make defensible digital business decisions, yet curriculum evidence often separates those two domains.

I frame this review around that tension rather than as a simple institutional timeline. The article examines the MSc in E-Commerce associated with The Hong Kong Polytechnic University, the Department of Computing, and HKCyberU as an educational institution supporting admission and delivery. Based on reported figures, the normal duration of the MSc award was 2.5 years, which matters because the programme design had to sequence technical, managerial, and research work across a part-time postgraduate pattern.

The analysis covers five domains: curriculum structure, subject coverage, blended-learning infrastructure, assessment models, and research training. I treat the programme as a case of early e-commerce institutionalisation in Hong Kong, where computing infrastructure, electronic payment, enterprise integration, and marketplace strategy had to be taught as one field rather than as adjacent topics.

Research Problem and Institutional Context

The central problem was not whether e-commerce belonged in computing or business. The harder question was how a postgraduate curriculum could make both claims credible at the same time.

Within the institutional arrangement, The Hong Kong Polytechnic University served as the awarding university, while the Department of Computing functioned as the curriculum authority. HKCyberU operated as the admission and delivery partner, giving working professionals access to a blended postgraduate route. That division of labour is important. It separates award governance, academic content, and learner-facing delivery without treating any one element as ornamental.

The programme also sat within a wider Hong Kong policy context shaped by the Digital 21 infrastructure agenda. I do not read that alignment as a claim that every syllabus topic came directly from policy. Rather, it helps explain why electronic commerce was treated as infrastructure, business process, security problem, and knowledge-management challenge at the same time.

Note: In this review, the institutional triad is defined narrowly: PolyU as awarding body, the Department of Computing as curriculum authority, and HKCyberU as delivery partner. That scope prevents the analysis from drifting into general commentary on online education.

Methodology

I conducted a qualitative documentary analysis of programme facts and administrative records. The source base was organised into five categories: HKCyberU Bulletin Board materials, handbook materials, subject syllabi, dissertation and project instructions, and reminder notices.

This method suits the question because the programme’s design logic is embedded in operational details. A reminder about proposal submission tells us something about supervision discipline. A bulletin-board notice about multimedia access tells us something about the assumed technical environment. A course code reveals progression when it is read beside prerequisites, exclusions, and assessment routes.

I therefore treated codes such as COMP5122, COMP5123, and COMP5322 as traceable curriculum units rather than merely administrative labels. That choice matters. It allows the analysis to connect course naming, technical vocabulary, assessment structure, and programme sequencing without assuming that a modern syllabus maps directly onto the historical one.

Research evaluations reveal the value of separating curriculum claims from delivery artifacts, but this article stays with the documentary record. The findings regarding curriculum effectiveness apply strictly to documented design intent and cannot be extended to actual completion rates or labour-market outcomes without external validation.

Curriculum Architecture: Core Subjects and Progression Logic

Foundation: COMP5122 E-Commerce Fundamentals and Development

COMP5122 provided the foundation for digital commerce concepts. Its role was to introduce web infrastructure, payment systems, security topics, and the basic development environment that made electronic commerce more than a managerial slogan.

The subject appears to have carried the first major integration task: linking the language of commerce to the machinery of the web. That includes marketplace forms, transaction processes, and the security assumptions behind networked payment. In curriculum terms, COMP5122 worked as the threshold subject. Without it, later enterprise and implementation topics would have floated without a common frame.

Bridge: COMP5123 Intelligent Information Systems

COMP5123 served a different purpose. It linked e-commerce to enterprise decision support, data mining, agents, personalisation, customer relationship management, and knowledge-based systems.

This is where the curriculum moved from transaction enablement to decision capability. The subject positioned intelligence not as abstract artificial intelligence, but as a practical layer of electronic business: recommend, personalise, classify, support, and learn from interaction records. For a postgraduate learner managing technology adoption, that bridge is crucial.

Implementation: COMP5322 Internet Computing and Applications

COMP5322 formed the technical implementation layer. The curriculum materials point to HTTP, XML, Java Servlet, SSL, DOM, SAX, and client/server interaction as the working vocabulary of implementation.

According to available data, Internet Computing was initially offered in September 2000, which places the subject inside a technical environment where web standards, server-side programming, and document processing were still being consolidated in professional practice. The course did not simply teach “the Internet”; it exposed learners to the protocols and parsing models that made Internet applications operational.

Technical Skill Domains in Digital Commerce Education

The technical coverage was broad, but not random. I group it into three domains: web development, enterprise integration, and secure transaction infrastructure.

Web Development and Document Processing

The curriculum materials map web development across HTML, XML, JavaScript, VRML, Front Page, CGI, Java Servlet, DOM, SAX, DTD, and XSL/XLS terminology. Some of those items now read as historical markers. That is precisely why they are useful evidence.

Front Page and VRML show the authoring and immersive-web assumptions of the period. DOM and SAX show a more durable concern: how applications process structured documents. CGI and Java Servlet mark the transition from static publishing to server-side interaction. The programme was not only teaching learners to make pages; it was teaching them how web applications received, transformed, and returned structured information.

Enterprise Integration

System integration appeared through XML, EDI, Internet EDI, enterprise application integration, Enterprise Java Bean architecture, and enterprise application communication.

The controlled comparison here is between document exchange and application integration. EDI and Internet EDI emphasise trading-partner messages. Enterprise application integration and Enterprise Java Bean architecture emphasise internal system coordination. Both matter in e-commerce, but they solve different problems. One connects organisations; the other connects enterprise functions.

Security and Payment Infrastructure

Security coverage included PKI, certificate authority concepts, SSL, IPSec, SET, message digest, digital signature, digital cash, smart card payment, and PPS as payment-related examples.

The curriculum treated trust as a technical and institutional problem. A certificate authority is not just a cryptographic detail; it is a governance mechanism for identity. A digital signature is not just a mathematical operation; it supports non-repudiation. Payment examples such as smart cards and PPS grounded the topic in the administrative realities of Hong Kong electronic transaction practice.

Business and Management Skill Formation

The programme translated technical competence into business capability by teaching marketplace models and strategic systems vocabulary together.

B2B, B2C, C2C, and G2B models gave learners a classification structure for digital commerce relationships. The value of that structure is practical: procurement, consumer retailing, peer exchange, and government-facing transactions each carry different identity, workflow, payment, and trust requirements.

Subjects such as COMP5133 Information Systems and E-Commerce Strategy and COMP5136 B2B & B2C E-Commerce and Management show how the programme joined systems thinking with managerial decision-making. Topics including business process re-engineering, eSCM, virtual marketplace models, CRM, information systems outsourcing, netcentrism, and trust metrics gave the curriculum a strategic layer.

The launch of Web Advertising and Web Publishing was recorded around January 2001, and that timing helps locate the programme’s marketing and content-management concerns. Push-based and pull-based advertising, web publishing, electronic publishing, digital libraries, and user tracking were not side topics. They were early expressions of what later became routine digital marketing and platform analytics work.

Quick Tip: When reading an e-commerce curriculum, do not separate “business model” topics from protocol and security topics too quickly. In practice, the marketplace model determines what kind of identity, payment, fulfilment, and audit trail the system must support.

Blended Delivery, Online Discussion, and Learning Infrastructure

HKCyberU’s role was operational as well as instructional. It supported admission, delivery, reminders, and bulletin-board communication for a postgraduate population that included working professionals.

I treat the threaded online discussion environment as a primary teaching tool, not as an accessory. In a blended postgraduate programme, discussion boards carry more than conversation. They hold prompts, clarifications, peer exchange, and time-sensitive reminders. When the learner is not always physically present, the bulletin board becomes part of the academic infrastructure.

The documentary evidence also preserves the technical requirements of the period. Real Player 7.0 and broadband access were specified for multimedia access. Hang Seng Bank and PPS appeared as administrative payment channels. These details may look mundane, but they show the programme operating inside the same electronic service ecosystem it was teaching.

The trade-off is clear. Blended delivery expanded access for professionals, yet it also required learners to maintain a minimum technical setup and to follow online administrative signals carefully. Platform availability alone would be a weak measure of blended-learning quality; supervision rhythm and submission deadlines matter just as much.

Assessment Design and Applied Research Training

The assessment architecture gave learners several capstone pathways: COMP5091 E-Commerce Dissertation, COMP5940 Dissertation, COMP5093 Project, COMP5933 Project, COMP5009 Independent Study in E-Commerce, and COMP5923 Independent Study.

The documentary record shows mutual exclusion rules across dissertation, project, and independent study routes. That design prevented learners from stacking overlapping capstone formats and forced a clearer choice between research depth, applied project work, and independent study.

Dissertation and project formats operated over two semesters. Supervisor-student tutorials were expected on a bi-weekly frequency, and proposal deadlines were set within four weeks. Those constraints shaped research behaviour more effectively than a general statement about academic rigour would have done.

Applied Research functioned as the dissertation methodology. Core tasks included Literature Review, Literature Survey, requirements specification, and prototypical implementation. The sequence is practical: define the problem, examine what is already known, specify what the system or study must do, then build or evaluate a prototype where appropriate.

Key Findings

1. The curriculum integrated implementation and decision-making. COMP5122, COMP5123, and COMP5322 formed a progression from e-commerce concepts to intelligent information systems and Internet application implementation.
2. Technical topics reflected the early-2000s web stack. HTML, XML, JavaScript, CGI, Java Servlet, DOM, SAX, DTD, XSL/XLS terminology, SSL, and PKI were presented as working knowledge for digital commerce systems.
3. Business models were taught as system requirements. B2B, B2C, C2C, and G2B models shaped how learners would think about process design, payment, trust, and integration.
4. Blended learning had an operational identity. Bulletin boards, reminders, multimedia requirements, and payment channels were part of programme delivery, not merely administrative background.
5. Applied research training was structured through constraints. Mutual exclusions, two-semester formats, bi-weekly supervision, and four-week proposal expectations made the capstone routes concrete.

Summary: The MSc in E-Commerce was designed as an integrated postgraduate programme where web infrastructure, enterprise systems, security, marketplace strategy, and applied research were meant to reinforce one another.

Limitations of the Documentary Evidence

The analysis relies on curriculum and administrative records, including materials associated with HKCyberU and Hong Kong I-Education Limited as copyright holder. It does not use longitudinal graduate data, employer feedback, or independent labour-market tracking.

Several artifacts also belong clearly to their period. Real Player 7.0, Front Page, SET, VRML, and specific 2003/2004 administrative deadlines mark an early-2000s environment. I read those markers historically rather than treating them as deficiencies. A curriculum built for that environment should be assessed against the protocols, tools, and institutional expectations of its time.

The remaining unanswered question is effectiveness. The documentary record shows design intent, sequencing, and operational discipline. It does not show how individual learners experienced the workload, how many completed within expected time, or how employers valued the credential.

Implications for Current Programme Design

The historical curriculum logic still travels well, even where the tools have changed.

XML and EDI concepts can be updated into modern API integration, platform interoperability, and data-exchange governance. Early PKI and SSL coverage can be extended into contemporary cybersecurity governance, certificate lifecycle management, and secure platform assurance. CRM, personalisation, user tracking, and knowledge-based systems can be reframed through learning analytics, data ethics, and responsible artificial intelligence.

The more durable lesson is structural. A strong e-commerce programme should not isolate coding, strategy, security, and research methods. It should make learners move among them, because real digital business decisions rarely arrive in tidy disciplinary packets.