Note: This unit version is currently under review and is subject to change!
ELEC3610: E-Business Analysis and Design (2017 - Semester 1)
|Unit:||ELEC3610: E-Business Analysis and Design (6 CP)|
|Faculty/School:||School of Electrical & Information Engineering|
Dr Yeoh, Phee
|Session options:||Semester 1|
|Versions for this Unit:|
|Site(s) for this Unit:|
|Brief Handbook Description:||This unit examines the essential pre-production stages of designing successful internet websites and services. It focuses on the aspects of analysis, project specification, design, and prototype that lead up to the actual build of a website or application. Topics include, B2C, B2B and B2E systems, business models, methodologies, modeling with use cases / UML and WebML, the Project Proposal and Project Specification Document, Information Architecture and User-Centred Design, legal issues, and standards-based web development. Students build a simple use-case based e-business website prototype with web standards. A final presentation of the analysis, design and prototype are presented in a role play environment where students try to win funding from a venture capitalist. An understanding of these pre-production fundamentals is critical for future IT and Software Engineering Consultants, Project Managers, Analysts and CTOs.|
Dr Yeoh, Phee
Ian Chunfeng Liu - firstname.lastname@example.org
Bo Liu - email@example.com
|T&L Activities:||Tutorial: tutorial exercises and project specification document (PSD)
Project Work - own time: PSD and prototype website
Presentation: Project presentation to peers
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
|Attribute Development Method||Attribute Developed|
|The students design a web-based solution||Design (Level 3)|
|Students will learn about the web technologies that support EBusiness||Engineering/IT Specialisation (Level 3)|
|The project includes extensive research work. It also includes a workshop activity with librarians||Information Seeking (Level 3)|
|The students must write a proposal that is 20% of the assessment, and give a presentation (an extra 5%)||Communication (Level 3)|
|Critical analysis of web projects
The project has a component assessable as a group
|Professional Conduct (Level 2)|
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.Engineering/IT Specialisation (Level 3)
Proposal Draft: Initial draft of Project Specification Document (PSD)
Peer review of Proposal: PSD peer review during tutorial session
Proposal Final Version: Final PSD submission
Presentation: Project presentation to be held during tutorial session
Final prototype: Demo website
Final Exam: Covering all aspects of the unit of study.
Mark summation: There may be statistically and educationally defensible methods used when combining the marks from each component to ensure consistency of marking between markers, and alignment of final grades with unit outcomes and grade descriptors.
Penalties for lateness: 20% per day
Similarity detection: The University has authorised and mandated the use of text-based similarity detecting software Turnitin for all text-based written assignments.
|Policies & Procedures:||See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.|
Note: Students are expected to have a personal copy of all books listed.
|Online Course Content:||Refer to Blackboard|
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
|Week 1||Course Overview, Information Databases|
|Week 2||Project Management, Formal Software Engineering RUP, Project Specification Document.|
|Week 3||Modelling Functionality and Use Case Scenarios|
|Week 4||Elements and Categories of E-Commerce, B2B - Business to Business Systems|
|Assessment Due: Proposal Draft|
|Week 5||Electronic Data Interchange, XML, E-marketplaces and Online Revenue Models|
|Assessment Due: Peer Review of Proposal|
|Week 6||B2E - Business to Employee Systems, Knowledge Management, Website Usability|
|Week 7||Modelling applications with WebML|
|Week 8||E-commerce Software for Small and Large Businesses - CSPs, CRM, ECM, KMS|
|Assessment Due: Proposal|
|Week 9||E-Commerce Security|
|Week 10||E-Commerce Legal and Ethical Issues|
|Week 11||B2C - Business to Customer Systems, Customer relationship management|
|Week 12||Social Networking and Mobile Commerce|
|Assessment Due: Presentation|
|Week 13||Unit Review: Assessment - preparing for the exam|
|Assessment Due: Website Prototype|
|Exam Period||Assessment Due: Final Exam|
The following is a list of courses which have added this Unit to their structure.
This unit contributes to the achievement of the following course goals:
|Design (Level 3)||Yes||0%|
|Engineering/IT Specialisation (Level 3)||Yes||32.5%|
|Information Seeking (Level 3)||Yes||20%|
|Communication (Level 3)||Yes||10%|
|Professional Conduct (Level 2)||Yes||12.5%|
|Project and Team Skills (Level 3)||No||25%|
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.