Note: This unit version is currently under review and is subject to change!
ELEC3609: Internet Software Platforms (2016 - Semester 2)
|Unit:||ELEC3609: Internet Software Platforms (6 CP)|
|Faculty/School:||School of Electrical & Information Engineering|
|Session options:||Semester 2|
|Versions for this Unit:|
|Site(s) for this Unit:||
|Pre-Requisites:||INFO1103 AND INFO2110 AND (INFO2120 OR INFO2820).|
|Brief Handbook Description:||This unit of study will focus on the design, the architecture and the development of web applications using technologies currently popular in the marketplace including Java and .NET environments. There are three key themes examined in the unit: Presentation layer, Persistence layer, and Interoperability. The unit will examine practical technologies such as JSP and Servlets, the model-view-controller (MVC) architecture, database programming with ADO.NET and JDBC, advanced persistence using ORM, XML for interoperability, and XML-based SOAP services and Ajax, in support of the theoretical themes identified.
On completion the students should be able to:
- Compare Java/J2EE web application development with Microsoft .NET web application development.
- Exposure to relevant developer tools (e.g. Eclipse and VS.NET)
- Be able to develop a real application on one of those environments.
- Use XML to implement simple web services and AJAX applications.
|T&L Activities:||Project Work - own time: The project requires students to design and develop web services. It involves group meetings, discussions and development sessions|
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|
|Ability to conceive, design, build and test a web service in a team project environment.||Design (Level 3)|
|Develop in-depth technical skills and knowledge of web technologies and the development lifecycle and management of web-based projects.||Engineering/IT Specialisation (Level 4)|
|Proficiency in researching and creatively applying technical principles, design methodology, and knowledge of tools and materials in the design of web services.||Information Seeking (Level 2)|
|Ability to produce clear and well-constructed engineering documents for web–based projects; ability to produce clear and informative diagrams and models for web–based projects||Communication (Level 3)|
|Ability to undertake engineering design and problem solving in a team project environment using a clearly defined, systems based approach to web services.||Project and Team Skills (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.Design (Level 3)
Project: Group Project with 4 deliverables:
Deliverable 1 due week 5 (worth 10% of total course grade): Use case modelling, requirements analysis and system specification.
Deliverable 2 due week 7 (worth 5% of total course grade): System design specification.
Deliverable 3 due week 12 (worth 30% of total course grade): System implementation
Deliverable 4 due week 13 (worth 15% of total course grade): System deployment and testing
|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: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
|Online Course Content:||http://www.eelab.usyd.edu.au/ELEC3609/outline.html|
|Note on Resources:||.NET Framework Developer Center”, http://msdn.microsoft.com/en-us/netframework/default.aspx|
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||Introduction, Course Mechanics & Web Fundamentals|
|Week 2||Web Fundamentals (cont.), Use Case Modelling, Wireframing, Requirements Analysis and Requirements Specification for Web Applications|
|Week 3||Web Servers and Application Architecture|
|Week 4||Web back-end technologies and development environments|
|Week 5||Deliverable: 5 min pitches & requirements doc|
|Front-end technologies, methods and security|
|Assessment Due: Use case modelling, requirements analysis, spec.|
|Week 6||Deploying, configuring, and securing pre-packaged software|
|Week 7||Deliverable: System design specification|
|Cloud services and deployment|
|Assessment Due: System design specification|
|Week 8||Tying it all together|
|Week 9||Continuous Integration & Testing|
|Week 10||Advanced Web Services|
|Week 11||Web Security Introduction/Overview & Policies|
|Week 12||Scaling to millions of users|
|Deliverable: Working system - demos|
|Assessment Due: System implementation|
|Week 13||Group Project Deliverable 4 due week 13: Test results and user documentation|
|Assessment Due: System deployment and testing|
|STUVAC (Week 14)||Prepare for exam|
|Exam Period||Final examination|
|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||25%|
|Engineering/IT Specialisation (Level 4)||Yes||47.5%|
|Information Seeking (Level 2)||Yes||6.25%|
|Communication (Level 3)||Yes||8.75%|
|Professional Conduct (Level 2)||No||0%|
|Project and Team Skills (Level 2)||Yes||12.5%|
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.