[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]
Monash University

FIT3083 e-Business software technologies - Semester 2, 2014

The emphasis in this unit is on the software technologies and data formats used to implement e-Business Systems. Although this unit is entirely suitable for a future developer of e-Business Systems, it is optimally targeted at future managers of such development. Thus practical exercises will be illustrative rather than industrial strength and technology issues will be given equal coverage with technology details. The primary aim of the unit is to familiarise students with as many of the currently popular e-Business technologies as possible so that their design and implementation decisions in the future will be informed and therefore produce successful systems with a high degree of probability.

Mode of Delivery

Clayton (Day)

Workload Requirements

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

  • Two hours of lectures
  • One 2-hour laboratory

(b.) Additional requirements (all students):

  • A minimum of 2-3 hours of personal study per one hour of contact time in order to satisfy the reading and assignment expectations.

Additional workload requirements

In this unit lecture and lab preparation are critical and should occupy at least 4-5 hours of the 12 hours per unit recommended in the Workload Requirements.

Unit Relationships

Prohibitions

FIT2013

Prerequisites

FIT1002 or FIT2081 or equivalent

Chief Examiner

Campus Lecturer

Clayton

Stephen Huxford

Tutors

Clayton

Hongli Song

Ammar Haider

Your feedback to Us

Monash is committed to excellence in education and regularly seeks feedback from students, employers and staff. One of the key formal ways students have to provide feedback is through the Student Evaluation of Teaching and Units (SETU) survey. The University’s student evaluation policy requires that every unit is evaluated each year. Students are strongly encouraged to complete the surveys. The feedback is anonymous and provides the Faculty with evidence of aspects that students are satisfied and areas for improvement.

For more information on Monash’s educational strategy, see:

www.monash.edu.au/about/monash-directions/ and on student evaluations, see: www.policy.monash.edu/policy-bank/academic/education/quality/student-evaluation-policy.html

Previous Student Evaluations of this Unit

This unit is being rewritten from the ground up for the 2014 S2 delivery due to technological changes in the real world.

Requirement for less theory and more practice: An example based approach to learning will be adopted with theory minimised as much as possible.

Students enjoyed the variety of technologies taught. This will continue except with updated technologies likely to be critically important as soon as the students graduate.

If you wish to view how previous students rated this unit, please go to
https://emuapps.monash.edu.au/unitevaluations/index.jsp

Academic Overview

Learning Outcomes

On successful completion of this unit, students should be able to:
  • describe the major architecture, framework and technology options currently available to eBusiness solution developers (including SaaS, SOA and cloud computing);
  • use a range of current eBusiness technologies to design and develop non-trivial eBusiness solutions (technologies include: JavaScript, HTML5, CSS3, Ajax, XML, XPath, XSLT, XML Schemas, DTDs, JSON, JQuery, MVP);
  • use the facilities of a popular, industrial-strength IDE to implement such eBusiness solutions.

Unit Schedule

Week Activities Assessment
0   No formal assessment or activities are undertaken in week 0
1 Admin + HTML5 and CSS3 No tutorial
2 HTML5 and CSS3 Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
3 JavaScript Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
4 JavaScript Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
5 JavaScript Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
6 JavaScript Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
7 JQuery and other JavaScript toolkits Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
8 JQuery and other JavaScript toolkits Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
9 MVC Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
10 MVC Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
11 MVC Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
12 MVC Lecture Quiz (2%, top 10 count), Lab (2%, top 10 count)
  SWOT VAC No formal assessment is undertaken in SWOT VAC
  Examination period LINK to Assessment Policy: http://policy.monash.edu.au/policy-bank/
academic/education/assessment/
assessment-in-coursework-policy.html

*Unit Schedule details will be maintained and communicated to you via your learning system.

Teaching Approach

Lecture and tutorials or problem classes
This teaching approach provides facilitated learning, practical exploration and peer learning.

Assessment Summary

Examination (3 hours): 60%; In-semester assessment: 40%

Assessment Task Value Due Date
10 Laboratory Assessments 20% (10 best marks will contribute 2% each) Lab work will be marked in labs
10 Lecture Quizzes 20% (10 best marks will contribute 2% each) Lecture quiz questions will be answered in the lecture they are presented in
Examination 1 60% To be advised

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

  • Assessment task 1
    Title:
    10 Laboratory Assessments
    Description:
    During the semester their wiill be 11 lab assessments. For any stsudent only the top 10 marks from these assessments will be used to calculate their final mark for the unit.
    Weighting:
    20% (10 best marks will contribute 2% each)
    Criteria for assessment:

    Students will be awarded marks for completing coding tasks according to the principles and styles enumerated in lectures. It is important to understand working code will NOT attract full marks in its own right. Students will be questioned on their code. Marks will only be given for code the student can clearly describe and sematically interpret to the satisfaction of the tutor.

    Due date:
    Lab work will be marked in labs
  • Assessment task 2
    Title:
    10 Lecture Quizzes
    Description:
    It will be assumed students have prepared for each lecture prior to its delivery by reading published lecture slides and/or specified reading material. During the lecture the main points of the prescribed materials will be discussed freely. Essentially the lecturer will lead a Q&A session.

    There will be multiple question breaks in the lecture in which students will be asked to write the answer to a previously unseen question based on the material discussed just prior to the question break. The questions will not be difficult. They will try to confirm that the student has understood the targeted material. Students may also be asked to solve a problem as evidence that the implications of an important or critical point have been appreciated.

    During a question break students may freely talk to other students and the lecturer to discuss the question and its solution.

    Lecture quizzes will be held in Week 2 to Week 12. Therefore there will be 11 lecture quizzes in all.

    The quiz questions in each lecture are worth 2% of the final mark. For each student the best 10 of these marks will constitute 20% of the non-exam mark for each student.
    Weighting:
    20% (10 best marks will contribute 2% each)
    Criteria for assessment:

    Correctness of quiz answers

    Due date:
    Lecture quiz questions will be answered in the lecture they are presented in

Examinations

  • Examination 1
    Weighting:
    60%
    Length:
    3 hours
    Type (open/closed book):
    Closed book
    Hurdle requirements:
    Exam mark and non-exam mark must both be 40% or above

    Combined mark must be 50% or above
    Electronic devices allowed in the exam:
    None

Learning resources

Monash Library Unit Reading List (if applicable to the unit)
http://readinglists.lib.monash.edu/index.html

Faculty of Information Technology Style Guide

Feedback to you

Examination/other end-of-semester assessment feedback may take the form of feedback classes, provision of sample answers or other group feedback after official results have been published. Please check with your lecturer on the feedback provided and take advantage of this prior to requesting individual consultations with staff. If your unit has an examination, you may request to view your examination script booklet, see http://intranet.monash.edu.au/infotech/resources/students/procedures/request-to-view-exam-scripts.html

Types of feedback you can expect to receive in this unit are:

  • Informal feedback on progress in labs/tutes
  • Quiz results
  • Solutions to tutes, labs and assignments

Extensions and penalties

Returning assignments

Assignment submission

It is a University requirement (http://www.policy.monash.edu/policy-bank/academic/education/conduct/student-academic-integrity-managing-plagiarism-collusion-procedures.html) for students to submit an assignment coversheet for each assessment item. Faculty Assignment coversheets can be found at http://www.infotech.monash.edu.au/resources/student/forms/. Please check with your Lecturer on the submission method for your assignment coversheet (e.g. attach a file to the online assignment submission, hand-in a hard copy, or use an online quiz). Please note that it is your responsibility to retain copies of your assessments.

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Required Resources

Please check with your lecturer before purchasing any Required Resources. Limited copies of prescribed texts are available for you to borrow in the library, and prescribed software is available in student labs.

Microsoft Visual Studio.Net 2013 (already installed in the labs and a free version is downloadable)

Latest versions of popular browsers (eg. Chrome, Firefox, IE)

Recommended text(s)

Matthew MacDonald. (2014). HTML5: The Missing Manual. (2nd Edition) O'Reilly Media (ISBN: 978-1-449-36326-0).

Alan Forbes. (2013). The Joy of jQuery. (2nd Edition) Plum Island Publishing.

Adam Freeman. (2013). Pro ASP.NET MVC 4. (4th Edition) Apress (ISBN: 978-1430242369).

Other Information

Policies

Monash has educational policies, procedures and guidelines, which are designed to ensure that staff and students are aware of the University’s academic standards, and to provide advice on how they might uphold them. You can find Monash’s Education Policies at: www.policy.monash.edu.au/policy-bank/academic/education/index.html

Key educational policies include:

Faculty resources and policies

Important student resources including Faculty policies are located at http://intranet.monash.edu.au/infotech/resources/students/

Graduate Attributes Policy

Student Charter

Student services

Monash University Library

Disability Liaison Unit

Students who have a disability or medical condition are welcome to contact the Disability Liaison Unit to discuss academic support services. Disability Liaison Officers (DLOs) visit all Victorian campuses on a regular basis.

Other

The following websites contain relevant and useful information:

www.w3c.org,

developer.mozilla.org/en-US/,

www.codecademy.com/,

asp.net/mvc, 

[an error occurred while processing this directive]