Deliverables

You are responsible for teaching your team mates how to use the tools that your roll adds. In order to do this, you will be giving a lecture to the class, and have a tangible deliverable for your team. To find the date for the lecture you will teach in the calendar, look for:

Note: This is your lecture, not mine. If you are not set up and ready to present at the front of the classroom when the lecture starts, it will cost your team 5 points, so arrive early to give yourself time to connect your computers, etc.

You will also give one of the on the progress of your project. To find the date for this in the calendar, look for TL :Software Development Specialists individual deliverable (You don't get a mark when you present)
Each week, when you are not the Team Lead you have a tangible deliverable that I will be looking for in the current Team Lead’s Weekly Status report. You do not get a mark for this the week you present. These deliverables are listed below in Team member deliverables.
See the FAQ below.

Team member deliverables:

For TL1 Presentation

Most importantly, by the time your team lead presents you should have a copy of your team’s basic project loaded onto your personal computer and you should know how to update your team’s code. You should have the following skills mastered:

Adding to your code repository
Updating your team’s Gantt chart.
Communicating electronically with your team
For the marks: Put a readme file in your Assets folder with a brief description of your feature.

Your team lead has created a doc folder on GIT. By the time you give your System’s Analysis Presentation I should find in this folder:

Your group’s RFP
Your Champion document (prefixed with your initials)

In your doc folder, by the time team lead 1 presents I should also find

Your feature’s class diagram (prefixed with your initials)

It must include inheritance and aggregation

Your feature’s sequence diagram (prefixed with your initials)

It must include at least 3 classes

Your team lead has created a src folder on GIT. By the time team lead 1 presents in it I should find:

At least one file code file for your feature that you intend for team lead 2 to integrate into the initial build. (It does not have to be integrated at this point).

For TL2 Presentation

In the src/name directory put your basic C# files with stubs for most functions. (Note: In this directory EVERYTHING goes into your sub-folder. No one will look at this except you and the person your company hires 10 years from to take over your code. Target any documentation to help future developers. I.e. if you are using third party code, think about what happens if the company that made that code no longer exists.)

Give team lead 2 a list of your .cpp or .cs files and ensure you know how to add/delete to your variable.
Work with your team lead to determine 1 or 2 functions from your section that are needed for your team leads minimum viable product. Complete those functions.
Ensure you understand the process of updating, compiling and running your part of your team’s code. (You can NOT edit code owned by a team member. Only your own).

For TL3 Presentation

Note: All tests must be fully automatic and not require user input except to start the test case. Each test case must return a clear pass fail (or a failure point for stress tests). Note 2: You get double credit for this since it is also your initial test plan.

Define at least one stress test case and add it to the group’s stress tests. Each stress test must define a failure condition. The stress test should start at a success position, then gradually increase the stress until a failure is detected. It should then return the value where the failure occurred.
Create at least 2 initial boundary tests for the automated testing system that your team lead will set up. Be purposeful in your testing. Think about your boundary conditions.

Team lead 3 will be responsible for tying it all together, but each of you will have to come up with your own tests.

For TL4 Presentation

Add to the Gantt chat of all the work items you have completed so far and what you have left to do (with time estimates in hours).
Be specific about what tasks you will be doing. (i.e. “Searching the internet for graphics”, or “Coding layout for level 2”, etc.)
You must keep this chart up to date each week.

For TL5 Presentation

Continue to develop your feature.

For TL6 Presentation

Continue to develop your feature.

FAQ:

Q: My laptop is not powerful enough to run Unity. Can I do my presentation via Zoom?
A: You are being marked on style, so being in-person is REALLY important.
One solution would be to make a video of your game running (or your stress test), and show the video as part of your in-person presentation. If you have no laptop at all, you can use the computer in the classroom to give the presentation from.