代做ISYS 1108、代做Software、代写Python，c++，Java编程语言

日期：2020-09-26 09:04

Software Engineering Project Management

Team-Based Assignment: Part 1

Assessment Type: In a group of 5-6 (no individual submissions will be accepted).

Assignment: Submit online via Canvas → Assignments → Team-based Assignment, Part 1 → Team-based Assignment 1.

Clarifications/updates may be made via announcements/relevant discussion forums.

Due date for the Assignment submission: 9th August 2020, 23:59 (Sunday of Week 3).

Unless special consideration has been granted, the late penalty is 10% of the total mark for the assessment per business

day late for up to 5 business days late (so the maximum late penalty is 50%). Submissions more than 5 days late are not

accepted.

Weighting: 7 points (worth 7% of the total score, i.e., 1 point = 1% of the total score)

1. Overview

For this assignment, assume that you are a Scrum team working on a software development project.

The scenario was inspired by a real industrial project contacted previously in collaboration between RMIT and CBA.

You will be writing code to create the software along with the important project management documents. Some specific details on

the software/product are not known at the start, these will emerge during the project. This is very close to real life projects.

You must register your application for a team role using the Form provided in Canvas.

The deadline for registration is Sunday, July 28th, 23:59 (Sunday of Week 2). No registration == No submission.

Scenario:

A company would like to use a humanoid robot to conduct a tour over an exhibition centre under the control of an assistant. As

a part of their larger project, they contacted your team to create an application for management of the tour information. A

web-based solution is preferred, but a desktop solution might be also an option.

The company would like that their admins can

? create accounts for new admins and assistants,

? deactivate admin and assistant users,

? add new locations to the set of locations: a location should be specified by its name, x-y coordinates, description, and the

min. time to be spent on the location (the time depends on the length of the description, as the robot will “pronounce” it

using text-to-voice feature),

? edit existing locations (name, x-y coordinates, description, min. time),

? copy existing locations,

? remove existing locations,

? create a new tour out of the specified locations: the tour should be specified by its name, type, min. duration (which is a

sum of the minimal times to spend at each location),

? edit the set of tour types – add new types, remove the types that are unnecessary, change the type label,

? edit existing tours (add or remove locations, edit the tour name,

? remove existing tours.

Page 2 of 5

When you start working on the team-based assignment:

1) If you have questions on the assignment tasks and/or the corresponding course material, you might

? bring these questions to weekly feedback sessions held by lecturer, or

? post them in the discussion board Assignment folder.

Please prepare your questions for the session properly, as this is planned not as pre-check of your work before you

submit, but as opportunity to answer your questions on the material and to clarify your doubts.

2) Before your team starts working on 3 development sprints within the Part 2 of the team-based assignment (Sprint 1 starts from

the beginning of Week 6), you have to complete Sprint 0 tasks prepare the Project Charter and your Product Backlog using the

provided templates. Parts of your Product Backlog will be checked within the first Work Progress Check on Week 5, where the

deliverable of your Team-Based Assignment 1 is the Project Charter.

2. Assessment Criteria

This assessment will determine your ability to:

1. Follow Agile to prepare for management of a software development project.

2. Create corresponding Project Charter by recalling concepts taught in class, understanding and applying concepts relevant

to solution, analysing components of the problem, evaluating different approaches.

3. Ability to provide references where due.

4. Meeting deadlines.

5. Seeking clarification from your “supervisor” (tutor) when needed via discussion forums.

3. Learning Outcomes

This assessment is relevant to the following Course Learning Outcomes (CLOs):

? CLO 1: Illustrate a working knowledge of how to plan, execute and close projects to required standards

? CLO 2: Use a range of proprietary and non-proprietary project management tools to carry out and report on your team

projects

? CLO 3: Use project management frameworks that ensure successful outcomes

? CLO 4: Analyse and apply critical project management concepts, such as: Why Projects Fail; Project Governance and

Methodologies; Software Development Life Cycles – From Waterfall to Agile; Software Engineering Fundamentals; Software

Requirements Engineering as basis for Project Management; Hybrid methodologies; Planning and Scheduling; Risk and

Issues Management; Quality Assurance; Change Management; Release Management; Service Delivery and Support; The

Team Dynamic; Collaboration and Communication skills; Organisations, People and Culture

? CLO 5: Apply critical analysis, problem solving, and team facilitation skills to software engineering project management

processes using real-world scenarios.

Page 3 of 5

4. Assessment details

Note: Please ensure that you have read sections 1-3 of this document before going further.

Marking Guide: Please check the marking rubrics on the last page.

Your group must submit one PDF file with the Project Charter. Please use the provided template for the Project Charter, but add at

the last page the following table to indicate the contributions of the team members:

Full Name Student ID Agreed

contribution

Sum of agreed contributions (please calculate carefully so that the result is exactly

100%)

100%

Note, that even when the assignment will be marked as a whole, the marks will be provided individually:

Each student will a receive final mark based on a final mark for the project and their contribution, as per above table.

You will need to agree on contribution fractions before you submit this assignment. This will be moderated if necessary.

Here are some examples:

1. An excellent Project Charter, assessed at 10/10. Five students in the group, all students contributed equally, all

students get a mark of 10.

2. A good project, assessed as 7/10. Five students in the group. Contributions were not equal:

- students A and B contributed each 20%,

- students C and D contributed each 15%,

- student D contributed 30% of the overall work.

There are 35 marks to be distributed: 7*5 = 35.

Students A and B will receive for this assignment 7 marks each: min (35*0.2, 10) = min (7, 25) = 7.

Students C and D will receive for this assignment 5.25 marks each: min (35*0.15, 10) = min (5.25, 10) = 5.25,

Student D will receive 10 marks: min (35*0.3, 10) = min (10.5, 10) = 10.

5. Referencing guidelines

What: This is a group assignment and all submitted contents must be your own. If you have used sources of information other than

the contents directly under Canvas → Modules, you must give acknowledge the sources and give references using IEEE referencing

style.

Where: Add a code comment near the work to be referenced and include the reference in the IEEE style.

How: To generate a valid IEEE style reference, please use the citethisforme tool if unfamiliar with this style. Add the detailed

reference before any relevant code (within code comments).

Page 4 of 5

6. Submission format

Submit one PDF file online via Canvas → Assignments → Team-based Assignment, Part 1 → Team-based Assignment 1.

It is the responsibility of the student to correctly submit their files. Please verify that your submission is correctly submitted by

downloading what you have submitted to see if the files include the correct contents.

7. Academic integrity and plagiarism (standard warning)

Academic integrity is about honest presentation of your academic work. It means acknowledging the work of others while

developing your own insights, knowledge and ideas. You should take extreme care that you have:

? Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e. directly copied),

summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods,

? Provided a reference list of the publication details so your reader can locate the source if necessary. This includes material

taken from Internet sites.

If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work

and ideas of another person without appropriate referencing, as if they were your own.

RMIT University treats plagiarism as a very serious offence constituting misconduct. Plagiarism covers a variety of inappropriate

behaviours, including:

? Failure to properly document a source

? Copyright material from the internet or databases

? Collusion between students

For further information on our policies and procedures, please refer to the University website.

8. Assessment declaration

When you submit work electronically, you agree to the assessment declaration.