COMP SCI 4414B - Software Engineering Research Project B
North Terrace Campus - Semester 2 - 2024
-
General Course Information
Course Details
Course Code COMP SCI 4414B Course Software Engineering Research Project B Coordinating Unit Computer Science Term Semester 2 Level Undergraduate Location/s North Terrace Campus Units 6 Contact Up to 3 hours per week Available for Study Abroad and Exchange N Prerequisites COMP SCI 4414A Restrictions BEng (Software) students only Assessment Assignments and/or project Course Staff
Course Coordinator: Professor Ali Babar
Course Timetable
The full timetable of all activities for this course can be accessed from Course Planner.
-
Learning Outcomes
Course Learning Outcomes
This project consists of 2 semesters duration, with 3 units in semester 1 (part A) and 3 units in semester 2 (part B). Following on the project A, the project B will be built upon what would have been achieved during the project A. However, each part of the project has independent grading.
At the conclusion of the course, the students are expected to be able to:
1. Apply software engineering principles and research to industry projects.
2. Gain exposure to state-of-the-art research and technologies in an area of software engineering.
3. Learn to interpret and assess literature related to a current area of research.
4. Learn to present work to an audience, both in written form and orally.
5. Apply security and privacy principles to a specific industry project.
6. Apply an ethical lens to the software engineering practice within a specific industry project and reflect on the broader ethical issues raised by the project.
7. Learn to work and plan in groups following ICT professionalism principles.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) Attribute 1: Deep discipline knowledge and intellectual breadth
Graduates have comprehensive knowledge and understanding of their subject area, the ability to engage with different traditions of thought, and the ability to apply their knowledge in practice including in multi-disciplinary or multi-professional contexts.
1, 2 Attribute 2: Creative and critical thinking, and problem solving
Graduates are effective problems-solvers, able to apply critical, creative and evidence-based thinking to conceive innovative responses to future challenges.
1, 2, 4 Attribute 3: Teamwork and communication skills
Graduates convey ideas and information effectively to a range of audiences for a variety of purposes and contribute in a positive and collaborative manner to achieving common goals.
2, 5 Attribute 4: Professionalism and leadership readiness
Graduates engage in professional behaviour and have the potential to be entrepreneurial and take leadership roles in their chosen occupations or careers and communities.
5 Attribute 5: Intercultural and ethical competency
Graduates are responsible and effective global citizens whose personal values and practices are consistent with their roles as responsible members of society.
1, 5 Attribute 7: Digital capabilities
Graduates are well prepared for living, learning and working in a digital society.
1, 2, 3, 4, 5 Attribute 8: Self-awareness and emotional intelligence
Graduates are self-aware and reflective; they are flexible and resilient and have the capacity to accept and give constructive feedback; they act with integrity and take responsibility for their actions.
1, 2, 3, 4, 5 -
Learning Resources
Online Learning
All the learning material will be provided through Canvas (MyUni). please check that site for the material regularly.
GitHub will be used for artefacts management and project management.
Slack will be used for adhoc commuincation among all the stakeholders. -
Learning & Teaching Activities
Learning & Teaching Modes
The teaching and learning activities are carried out in face to face sessions. The online participation is avaiable based on the need/request.
The teaching and learning material is made avaiable via MyUni, GitHub and Slack.Workload
The information below is provided as a guide to assist students in engaging appropriately with the course requirements.
As a guide, each student is expected to work on the project between 10-12 hours per week as expected for a 3 Units course.Learning Activities Summary
This is a final year research project, jointly supervised by software engineering and computer science academics with external industry involvement. The research topic will be selected from CS staff research interests, while the area of application will be negotiated with industry partners. Students will be expected to learn and demonstrate the application of SE principles to conduct research for industry-based clients outside the school. The project will provide a pathway to enrolment in a higher degree by research.
The learning activities cover:
- Research and development on the proposed project topic.
- Implementing Scrum Process model (e.g.,define backlog items, run sprint review and retrospectives, live demo of working produt) in pracice with real industrial clients.
- Oral presentation to the clients and teaching staff
- Written + Oral presentation to a larger audience through Ingenuity event
Specific Course Requirements
It is expected that the students would be leveraging the learning from the following courses of the BE (Software) degree.
Engineering Software as Services I (ESS I)
Engineering Software as Services II (ESS II)
Software Engineering Workshop I - (Requirements Analysis, Modelling, Specifications)
Software Engineering Workshop II - (Software Design)
Research Methods in Software Engineering and Computer Science
Software Engineering Research Project B -
Assessment
The University's policy on Assessment for Coursework Programs is based on the following four principles:
- Assessment must encourage and reinforce learning.
- Assessment must enable robust and fair judgements about student performance.
- Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
- Assessment must maintain academic standards.
Assessment Summary
The assessment for SERP B (4414B) will be based on the following components:
• Sprint Review Meetings (20) – Individual
4 deliveries, fortnightly
• Prototyping (25) – Group (G) and Individual (I)
– Development process – G - (5)
– Development process – I - (5)
– Project quality – G - (7.5)
– Project quality – I - (7.5)
• Final Report – 20 (G)
• Final Presentation - 10 (I)
• Poster ingenuity – 10 (I)
• Client Assessment – 5 (I)
• Retrospective Reports – 10 (G)
- 5 deliverables, fortnightly.
Similar to last semester the assessment is broken down into Group and Individual components. While the project outcome is largely based on group work and group contribution, it is important to also have clear and significant individual contributions in the project. Hence, please be aware of the hurdle requirement in this regard:
Hurdle Requirement: If your overall mark for the course is greater than 44 F but, your mark for the individual work process and project quality component is less than 40%, your overall mark for the course will be reduced to 44 F.
Marking Schedmes:
• Fail: 0 – 49
• Pass: 50 – 64
• Credit: 65 – 74
• Distinction: 75 – 84
• High Distinction: 85 – 100
Assessment Related Requirements
Asssessment Guidelines:
- GitHub Flow: all feature development should happen in branches and only be merged into the master branch via pull requests once code review has been completed.
- Two-week sprints: After the initial weeks of getting up to speed (e.g., up to proposal week), you should have a milestone every two weeks. This pattern continues to SERP B.
- Commit messages, issues and pull requests: Make sure you write good commit messages (some ideas: http://chris.beams.io/posts/git-commit/) and that your issues and pull requests are understandable by somebody from outside your project (some ideas: https://wiredcraft.com/blog/how-we-write-our-github-issues/).
- Linking of artifacts: Each commit should be linked to an issue (feature or bug) or pull request (if it's a merge).
- Distribution of work: We'll be looking at your GitHub issues and who they are assigned to (and who made the corresponding commits).
- Testing: Depending on the technologies you use different testing frameworks might be able to help with that. By the end of the semester, most of your code should be covered by test cases.
- Deployment: Also depends on the technologies you use. There might be tools that can do this for you automatically, e.g., by taking the latest version from your GitHub's master branch and running it on some server.
- Client management: Make sure you're on time and well-prepared for all client meetings. The expectation is that you're able to demonstrate your latest version in each meeting to gather feedback from the client. It is your responsibility to plan these meetings.
Assessment Detail
No information currently available.
Submission
No information currently available.
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
- Academic Integrity for Students
- Academic Support with Maths
- Academic Support with writing and study skills
- Careers Services
- International Student Support
- Library Services for Students
- LinkedIn Learning
- Student Life Counselling Support - Personal counselling for issues affecting study
- Students with a Disability - Alternative academic arrangements
- YouX Student Care - Advocacy, confidential counselling, welfare support and advice
-
Policies & Guidelines
This section contains links to relevant assessment-related policies and guidelines - all university policies.
- Academic Credit Arrangements Policy
- Academic Integrity Policy
- Academic Progress by Coursework Students Policy
- Assessment for Coursework Programs Policy
- Copyright Compliance Policy
- Coursework Academic Programs Policy
- Elder Conservatorium of Music Noise Management Plan
- Intellectual Property Policy
- IT Acceptable Use and Security Policy
- Modified Arrangements for Coursework Assessment Policy
- Reasonable Adjustments to Learning, Teaching & Assessment for Students with a Disability Policy
- Student Experience of Learning and Teaching Policy
- Student Grievance Resolution Process
-
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.
