ELEC3610: E-Business Analysis and Design (2013 - Semester 1)
|Unit:||ELEC3610: E-Business Analysis and Design (6 CP)|
|Faculty/School:||School of Electrical and Information Engineering|
|Session options:||Semester 1|
|Versions 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.|
Mr Hague, Decler
|T&L Activities:||Project Work - own time: PSD
Presentation: PSD presentation to peers
Tutorial: tutorial exercises
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 4)|
|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 4)|
|The students must write a proposal that is 20% of the assessment, and give a presentation (an extra 5%)||Communication (Level 4)|
|Critical analysis of web projects
The project has a component assessable as a group
|Professional Conduct (Level 3)|
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: Project Specification Document
Assignment: Project Specification Document - peer review
Proposal: Project Specification Document - final document
Assignment: System design and development
Presentation/Seminar: Presentation to peers
Final Exam: Exam
|Faculty Policies & Procedures:||Academic Honesty in Coursework. All students must submit a cover sheet for all assessment work that declares that the work is original and not plagiarised from the work of others.
Coursework assessment and examination policy. The faculty policy is to use standards based assessment for units where grades are returned and criteria based assessment for Pass/Fail only units. Norm referenced assessment will only be used in exceptional circumstances and its use will need to be justified to the Undergraduate Studies Committee. Special consideration for illness or misadventure may be considered when an assessment component is severely affected. This policy gives the details of the information that is required to be submitted along with the appropriate procedures and forms.
Special Arrangements for Examination and Assessment. In exceptional circumstances alternate arrangements for exams or assessment can be made. However concessions for outside work arrangements, holidays and travel, sporting and entertainment events will not normally be given.
Student Appeals against Academic Decisions. Students have the right to appeal any academic decision made by a school or the faculty. The appeal must follow the appropriate procedure so that a fair hearing is obtained.
Note that policies regarding assessment submission, penalties and assessment feedback depend upon the individual unit of study. Details of these policies, where applicable, will be found above with other assessment details in this unit outline.
All university policies can be found at http://sydney.edu.au/policy
Various request forms for the Faculty of Engineering and IT can be found at http://sydney.edu.au/engineering/forms/
|Note on Resources:||All readings available at the library`s e-reserve, and can be bought as a hardcopy at the copy centre.|
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||Information Literacy - Using the Digital Library resources.|
|How to find a needle in a haystack - databases and sources|
|Business ideas and models|
|What is ELEC3610 about?|
|Week 2||The e-project. Management, formal software engineering RUP, the project Specification Document.|
|Writing workshop - with USyd Learning Centre|
|Week 3||Business models and technology fundamentals|
|Database driven web applications|
|Week 4||B2C - Business to Consumer systems|
|Assessment Due: Proposal|
|Week 5||Total Cost of ownership - copyright|
|Assessment Due: Assignment|
|Week 6||B2B - Business to Business Systems: Supply Chains, Moving information, money and products.|
|Assessment Due: Proposal|
|Week 7||Modelling applications with WebML and Use cases scenarios|
|Week 8||WebML. Data, Hypertext models|
|Week 9||Standards-based Web programming –- XHTML, CSS.|
|Week 10||Design: The Design process, navigation, information architecture.|
|Week 11||B2E - Business to Employee Systems: Knowledge management, collaboration, E-learning and Customer relationship management.|
|Week 12||Approaches to Rapid Prototyping. CASE tools, Ruby on Rails, Application Frameworks|
|Assessment Due: Lab Skills - Prototype|
|Week 13||Unit Review: Assessment - preparing for the exam|
|Assessment Due: Presentation/Seminar|
|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 4)||Yes||0%|
|Engineering/IT Specialisation (Level 3)||Yes||32.5%|
|Information Seeking (Level 4)||Yes||20%|
|Communication (Level 4)||Yes||10%|
|Professional Conduct (Level 3)||Yes||12.5%|
|Project Management and Teamwork (Level 4)||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.