Note: This unit version is currently being edited and is subject to change!
COMP5615: Software Engineering Project (2020 - Semester 2)
| Unit: | COMP5615: Software Engineering Project (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Postgraduate |
| Faculty/School: | School of Computer Science |
| Unit Coordinator/s: |
Dr. Suleiman, Basem
|
| Session options: | Semester 2 |
| Versions for this Unit: |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | None. |
| Prohibitions: | COMP3615 OR INFO3600 OR SOFT3413 OR COMP3600. |
| Brief Handbook Description: | The Software Engineering project will provide students an opportunity to apply the knowledge and practise the skills acquired in the prerequisite and qualifying units, in the context of designing and building a substantial software system in diverse application domains including life sciences. In particular, students will need to demonstrate sensible application of software development knowledge and skills in their project including deciding on and implementing most suitable software design and architecture, appropriate testing techniques, coding with maintainability and extensibility in-mind, and realizing relevant system’s non-functional properties including performance, security, reliability, and usability. Student will also need to demonstrate the proper use of software development tools and practices that lead to effective and efficient development processes. Working in groups for an external client combined with academic supervision, students will need to carry out the full range of activities including requirements capture, analysis and design, coding, testing and documentation. Students will use the XP methodology and make use of professional tools for the management of their project. |
| Assumed Knowledge: | INFO6007. or equivalent project management knowledge |
| Lecturer/s: |
Dr. Suleiman, Basem
|
|||||||||||||||||||||||||
| Timetable: | COMP5615 Timetable | |||||||||||||||||||||||||
| Time Commitment: |
|
|||||||||||||||||||||||||
| T&L Activities: | Site Visit: Meeting with project client Project Work - own time: Team and individual work Meeting: Weekly meeting with coordinator |
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.
(6) Communication and Inquiry/ Research (Level 3)
1. Produce written report of student’s work, in style that conforms to their discipline and is appropriate for clients to check.
2. Give an oral presentation of the student’s work and its rationale to the student’s discipline.
(7) Project and Team Skills (Level 3)
3. Work in a group of approximately 4-5 students, to deliver substantial results for clients.
(8) Professional Effectiveness and Ethical Conduct (Level 3)
4. Follow a systematic process of work, with appropriate mechanisms for dealing with risks, such as unforeseen factors and delays.
(2) Engineering/ IT Specialisation (Level 3)
5. Use previously unfamiliar tools and to integrate with previously unfamiliar software/systems, learning their use from examples and documentation.
(3) Problem Solving and Inventiveness (Level 3)
6. Work with clients: to discover their needs and to demonstrate that the delivered results meet those needs.
(1) Maths/ Science Methods and Tools (Level 3)
7. Apply discipline expertise in software engineering to solve problems and meet the needs of clients.
| Assessment Methods: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Assessment Description: |
1. First project demo & presentation: present the work done to understand the client`s requirements and complete the first set of requirements; this should be a major release, with some working and useful outcomes for the client and some parts presented in proposed form such as storyboards. All team members must be present. 2. First project report (group): reports the work done to understand the client`s requirements and complete the first set of requirements. It should also report on the group work and processes followed, systems and software tools used, and client interaction. It is largely a draft for the final report (see below). 3. First project report (individual): similar to the first project report but focuses on the individual contributions to the work completed in the project by this stage. All students will be required to give some feedback about the other team members of their group, in order to validate the individual reports. Individual advice will be given on performance and areas of improvement. This stage should also identify individuals at risk. 4. First client deployment: First set of test and implemented requirements must be deployed at client site. Students need to demonstrate that that the group has had a professional approach to the project deployment and worked to ensure that the client will be satisfied. The client will be consulted to ratify the deployment. 5. Final delivery to client: final product and relevant documentation delivered to the client. This includes all the sources, necessary technical documentation and any product or documentation that the client required at the start of the project. Students need to demonstrate that the group has had a professional approach to the product delivery and worked to ensure that the client will be satisfied with the final product. The client will be consulted to ratify the final product delivery. The final assessments are: 6. Final project demo & presentation: Commemorative group demo & presentation of the final product as delivered to the client. This must provide a convincing demonstration that the group has performed a substantial work that meets client needs and had a professional approach to achieve that. Groups need to demonstrate the use and application of their discipline knowledge to meet client`s needs. All team members must be present. 7. Final project report (group): This report discusses important aspects including technical details of final delivered product, how did it meets client`s needs, approach followed to interact with the client, group`s discipline knowledge and skills used to tackle problems, the quality of the processes followed and the effectiveness of group management processes. 8. Final project report (individual): report on the individual contributions throughout the project in terms of the demonstrable amount and quality. Again, validation from other team members will be sought through team member`s feedback. NOTE: The individual grade acts similarly to the exam in other subjects. To pass, you need to achieve at least 40%. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Assessment Feedback: | Students will be given individual feedback on their participation during the tutor meetings (tutorials) with each group each week. Tutors will follow up with individuals if there is a problem identified. Students will also receive feedback on their demonstrations, presentations, individual and group reports. Feedback from clients through interactions, demonstrations and presentations should be useful for the students. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Grading: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of Computer Science may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so. Other policies 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 on Resources: | Refer to the web site which contains many links to electronic resources. |
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 | Description |
| Week 1 | Overview, presentation of projects offered, collection of preferences |
| Lab time to meet with some clients. End of lab, allocations announced. | |
| Week 2 | Group contract, XP, on-ling group management tools, initial meeting with client |
| Tutor meet all managers. Tutor meets each group. | |
| Group work and Big 5 theory for efficient team work | |
| Week 3 | XP and test-first |
| Review of first user stories, XP roles, demo of group's online progress | |
| Tutor meet all managers. Tutor meets each group. | |
| Week 4 | Workload management and awareness of teamwork |
| Tutor meet all managers. Tutor meets each group. | |
| Working towards first demo and report. | |
| Week 5 | First demos early in lab - break and then feedback |
| Assessment Due: First project demo & presentation | |
| Assessment Due: First project report (group) | |
| Assessment Due: First project report (individual) | |
| Week 6 | Feedback whole class on demos. Share examplars. |
| Tutor meet all managers. Tutor meets each group. | |
| Week 7 | Tutor meet all managers. Tutor meets each group o discuss feedback on first reports. |
| Whole class feedback on reports. | |
| Week 8 | Refactoring, finalise acceptance tests. |
| Tutor meet all managers. Tutor meets each group to discuss client deployment and testing plan. | |
| Week 9 | Deployment at client site. |
| Assessment Due: First client deployment | |
| Week 10 | Progress on project development and testing. |
| Week 11 | Progress on project development and testing. |
| Week 12 | Practicing demos. Finalising report. |
| Week 13 | Final demos and finsl reports. |
| Assessment Due: Final delivery to client Product | |
| Assessment Due: Final demo & presentation | |
| Assessment Due: nal project report (group) | |
| Assessment Due: Final project report (Individual) | |
| STUVAC (Week 14) | N/A |
| Exam Period | N/A |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
| Attribute | Practiced | Assessed |
| (6) Communication and Inquiry/ Research (Level 3) | No | 23% |
| (7) Project and Team Skills (Level 3) | No | 15% |
| (8) Professional Effectiveness and Ethical Conduct (Level 3) | No | 16% |
| (5) Interdisciplinary, Inclusiveness, Influence (Level 3) | No | 0% |
| (4) Design (Level 3) | No | 0% |
| (2) Engineering/ IT Specialisation (Level 3) | No | 5.5% |
| (3) Problem Solving and Inventiveness (Level 3) | No | 20% |
| (1) Maths/ Science Methods and Tools (Level 3) | No | 20.5% |
These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 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.
