COMP SCI 3304 - Engineering Software as Services II

North Terrace Campus - Semester 2 - 2019

The objectives of this course are to enable students to advance and apply the knowledge, understanding, and skills for engineering Software as a Service, SaaS, acquired by successfully completing Engineering Software as Services I. This course will put more emphasis on challenging project work that will require students to complete a semester-long, group-based, software engineering project that will implement and deploy a SaaS Cloud based web application to solve a practical business problem. The course will be a 3 Unit one semester course offered in the second semester of third year of the BE(SE) degree program.

  • General Course Information
    Course Details
    Course Code COMP SCI 3304
    Course Engineering Software as Services II
    Coordinating Unit School of Computer Science
    Term Semester 2
    Level Undergraduate
    Location/s North Terrace Campus
    Units 3
    Contact Up to 4 hours per week
    Available for Study Abroad and Exchange N
    Prerequisites COMP SCI 3303
    Incompatible COMP SCI 3006, COMP SCI 3015B, COMP SCI 3018, COMP SCI 3310, COMP SCI 3311, COMP SCI 3312, COMP SCI 3313
    Restrictions Available to BE(Software) students only
    Course Description The objectives of this course are to enable students to advance and apply the knowledge, understanding, and skills for engineering Software as a Service, SaaS, acquired by successfully completing Engineering Software as Services I. This course will put more emphasis on challenging project work that will require students to complete a semester-long, group-based, software engineering project that will implement and deploy a SaaS Cloud based web application to solve a practical business problem.
    The course will be a 3 Unit one semester course offered in the second semester of third year of the BE(SE) degree program.
    Course Staff

    No information currently available.

    Course Timetable

    The full timetable of all activities for this course can be accessed from Course Planner.

  • Learning Outcomes
    Course Learning Outcomes
    On successful completion of this course students will be able to:

     
    1 Demonstrate an in-depth knowledge of different concepts and mechanisms underpinning Software as a Service, Service Oriented Architecture, Agile Approaches, and Cloud Computing.
    2 Explain the new challenges, opportunities, and open problems of Software as a Service.
    3 Construct a Software as a Service project from conception through planning, development, assessment/testing, deployment, and operations, experiencing the attendant challenges of each stage, using Ruby on Rails for development and Cloud Computing for deployment.
    4 Explain and use agile development methodologies and tools, including lo-fi UI sketching, user stories, behavior-driven development, version control for team-based development, and management tools for cloud-computing environments.
    5 Develop both technical and collaboration skills for working in "one-pizza" software teams.
    6 Discuss and apply fundamental programming constructs and techniques including design patterns for software architecture, higher-order functions, metaprogramming, reflection, etc. to improve the maintainability, modularity and reusability of their code.

     
    The above course learning outcomes are aligned with the Engineers Australia Stage 1 Competency Standard for the Professional Engineer.
    The course is designed to develop the following Elements of Competency: 1.1   1.2   1.3   1.4   1.5   1.6   2.1   2.2   2.3   2.4   3.1   3.2   3.3   3.4   3.5   3.6   

    University Graduate Attributes

    This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:

    University Graduate Attribute Course Learning Outcome(s)
    Deep discipline knowledge
    • informed and infused by cutting edge research, scaffolded throughout their program of studies
    • acquired from personal interaction with research active educators, from year 1
    • accredited or validated against national or international standards (for relevant programs)
    1, 2, 6
    Critical thinking and problem solving
    • steeped in research methods and rigor
    • based on empirical evidence and the scientific approach to knowledge development
    • demonstrated through appropriate and relevant assessment
    2, 3, 6
    Teamwork and communication skills
    • developed from, with, and via the SGDE
    • honed through assessment and practice throughout the program of studies
    • encouraged and valued in all aspects of learning
    3, 4, 5
    Career and leadership readiness
    • technology savvy
    • professional and, where relevant, fully accredited
    • forward thinking and well informed
    • tested and validated by work based experiences
    1, 2, 3, 4, 5, 6
    Intercultural and ethical competency
    • adept at operating in other cultures
    • comfortable with different nationalities and social contexts
    • Able to determine and contribute to desirable social outcomes
    • demonstrated by study abroad or with an understanding of indigenous knowledges
    3, 5
    Self-awareness and emotional intelligence
    • a capacity for self-reflection and a willingness to engage in self-appraisal
    • open to objective and constructive feedback from supervisors and peers
    • able to negotiate difficult social situations, defuse conflict and engage positively in purposeful debate
    3, 4, 5
  • Learning Resources
    Required Resources
    The text book for the course is: Armando Fox and David Patterson, Engineering Software as a Service: An Agile Approach Using Cloud Computing, 1st Edition, Strawberry Canyon LLC., ISBN-13: 978-0984881246.
    All students are expected to have their own copy of the textbook.
    A Kindle version is available on the Australan Amazon site and is automatically updated.
    Online Learning
    All lectures, assignment descriptions and links to on-line resources are available on the course website.

    This course uses the School of Computer Science's GitHub Enterprise Server rather than subversion for all assignment work:
            https://github.cs.adelaide.edu.au

  • Learning & Teaching Activities
    Learning & Teaching Modes
    Each week there will be two one-hour lectures followed by a two hour workshop, you are expected to attend all of the lectures and workshops.

    The lectures will present new material and be used to conduct peer reviews of different process aspects of the group projects.

    The workshops will be dedicated to group project work.
    Workload

    The information below is provided as a guide to assist students in engaging appropriately with the course requirements.

    You are expected to spend 10 hours per week on this course including attending all scheduled classes.
    Learning Activities Summary

    The topics taught in this course can be broadly classified as shown below:

    WeekTopic
    2 Javascript
    3 Design Patterns
    4 Performance, Releases, Reliability, Security
    1 to 12 Group Project
  • Assessment

    The University's policy on Assessment for Coursework Programs is based on the following four principles:

    1. Assessment must encourage and reinforce learning.
    2. Assessment must enable robust and fair judgements about student performance.
    3. Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
    4. Assessment must maintain academic standards.

    Assessment Summary
    Assessments
    Assessment TaskTask TypeDue*WeightOutcomesACS CBOK Areas
    Individual Project Work** Formative Weeks 2, 4, 6, 8, 10, 12 50% 1, 3, 4, 5, 6 1.1, 1.2, 2.4, 3.1, 3.2, 4.1, 4.2, 4.3
    Individual Reports+ Formative Weeks 6, 8, 10, 12 20% 1, 2, 4, 6 2.4, 3.2, 4.3
    Group Project Summative Week 12 30% 1, 2, 3, 4, 5, 6 1.1, 1.2, 2.4, 3.1, 3.2, 4.1, 4.2, 4.3

    * The specific due date for each assessment task will be available on MyUni.

    +The individual reports are mandatory: a submission must be made for each report within one week of its due date or any opportunity for an additional assessment may be denied.

    ACS CBOK Areas
    CBOK is the Core Body of Knowledge for ICT Professionals defined by the Australian Computer Society. The alignment in the table above corresponds with the following CBOK Areas:

    1. Problem Solving
    1.1 Abstraction
    1.2 Design

    2. Professional Knowledge
    2.1 Ethics
    2.2 Professional expectations
    2.3 Teamwork concepts & issues
    2.4 Interpersonal communications
    2.5 Societal issues
    2.6 Understanding of ICT profession

    3. Technology resources
    3.1 Hardware & Software
    3.2 Data & information
    3.3 Networking

    4. Technology Building
    4.1 Programming
    4.2 Human factors
    4.3 Systems development
    4.4 Systems acquisition

    5.  ICT Management
    5.1 IT governance & organisational
    5.2 IT project management
    5.3 Service management 
    5.4 Security management
    Assessment Related Requirements
    **Hurdle Requirement: If your overall mark for the course is greater than 44 F but, your mark for your individual project work is less than 50%, your overall mark for the course will be reduced to 44 F.
    Assessment Detail

    No information currently available.

    Submission

    All work will be submitted using a combination of the School's GitHub server and the course website. Submission details will be included in the assignment descriptions that will be published on the course website.

    Penalties for Late Submission of Individual Reports

    If you hand in your work late, your mark may be capped, based on how many days late it is, as follows:

    • Up to 1 day late — mark is reduced to 75%, marks below 75% are not affected.
    • Up to 2 days late — mark is reduced to 50%, marks below 50% are not affected.
    • Up to 3 days late — mark is reduced to 25%, marks below 25% are not affected.
    • More than 3 days late — mark is reduced to 0.
    Extensions for Individual Reports

    If you are unable to complete a report by the due date because of medical or compassionate circumstances, you must submit a request to the course coordinator prior to the due date. In your request you must attach supporting documentation – a medical certificate and/or a letter from the student counseling service. Work requirements are not considered grounds for extensions. If you are working, please make sure you are available for all activities.

    Penalties for Late Submission of Group Assignments

    The late submission of group assignments is not possible. The assessment will be based on material present in each group's GitHub repository at the due date.

    Course Grading

    Grades for your performance in this course will be awarded in accordance with the following scheme:

    M10 (Coursework Mark Scheme)
    Grade Mark Description
    FNS   Fail No Submission
    F 1-49 Fail
    P 50-64 Pass
    C 65-74 Credit
    D 75-84 Distinction
    HD 85-100 High Distinction
    CN   Continuing
    NFE   No Formal Examination
    RP   Result Pending

    Further details of the grades/results can be obtained from Examinations.

    Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.

    Final results for this course will be made available through Access Adelaide.

  • Student Feedback

    The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.

    SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.

  • Student Support
  • Policies & Guidelines
  • Fraud Awareness

    Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.

The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.