Release Sprint: Implementation and Testing

1. About this Sprint
2. User Stories covered in this Sprint
3. Course Goals covered in this Sprint
4. Introduction
5. Learning Material
6. Experiential Learning
- 6.1. Assignment: Implement System
- 6.2. Assignment Submission
7. Sprint Acceptance Tests

1 About this Sprint

This is a release sprint. This means that you package things that you have done in other sprints in order to create a release (an assignment delivery). You are expected to integrate what you have learnt previously and test/evaluate your release candidate to maximise your potential for passing the assignment.

2 User Stories covered in this Sprint

As a teacher I want to evaluate the students’ ability to transfer a theoretical design into a workable software solution so that I know they fulfil the corresponding course goals.
As a teacher I want to evaluate the students’ ability to transfer a theoretical design into a workable software solution so that I know they have an understanding of the difficulties this entails.
As a teacher I want to evaluate the students’ ability to transfer a theoretical design into a workable software solution so that I know they have an understanding of how to read a design consisting of several viewpoints (e.g. dynamic and static) and combine them in a software solution.
As a teacher I want to evaluate the students’ ability to transfer a theoretical design into a workable software solution so that I know they understand how to maintain updated design documentation alongside with an implementation.
As a teacher I want to evaluate the students’ ability to test an implemented system according to a test plan so that I know they understand how to translate a design to a test plan and how to execute this test plan.

3 Course Goals covered in this Sprint

(PA1415) i grupp kunna implementera ett mjukvaruprogram inom rimlig tid, baserat på en kravspecifikation och en objektorienterad design.
(PA1415) på en grundläggande nivå i grupp kunna planera och genomföra testning av producerad programvara, baserat på en kravspecifikation.

Färdigheter och förmåga
- (PA1435, PA1443) kunna korrekt transformera en objektorienterad design till källkod.
Värderingsförmåga och förhållningssätt
- (PA1434, PA1435) kunna analysera källkod för eventuella förbättringar.
- (PA1434, PA1435, PA1443) kunna analysera och kritiskt diskutera en design för eventuella förbättringar.

4 Introduction

In this release sprint you implement and test your design for your first iteration.

5 Learning Material

Please review the sprints concerning

6 Experiential Learning

6.1 Assignment: Implement System

In this assignment you are expected to implement your system according to your own design. You do not need to implement the entire system, but you need to implement enough to:

Get a working system with the basic cases for your most important use cases.
Show that you have at least partially created all the classes required for a Minimal Viable Product.
Show that you understand how to implement a system according to the overall architectural style you have chosen.
Show that you understand how to implement any design patterns you make use of. This probably includes at least one instance of the observer pattern, and possibly one instance of the strategy pattern.
Are able to execute your test plan for your most important use cases and see whether your tests adequately exercises the source code or not.
Are able to study your implementation and reason about ways to improve it and your design.

Remember to update your design documentation while you are implementing to reflect any changed design decisions you make.

Tasks:

Identify a relevant subset of your system.
Implement your system according to your design documentation.
Document deviations from your design and update the design documentation accordingly.
Execute your test plan on your implemented system and document the results.

Commit and push this document to your project repository.

Conditions of Satisfaction:

When marking this part of the assignment we are looking for the following:

Size of assignment: Does the implemented subset of the system represent a Minimal Viable Product?
Does it compile and run?
Does the test plan adequately test relevant aspects of the system?
Is the design documentation up to date according to what is implemented?
Are the students able to show a mapping between the design and the implementation?
Are the students able to show a mapping between the design and the test plan?
Are the students able to explain what their code does, in particular in relation to their design?
Are the students able to identify areas where their implementation may be improved, and reason about why, in particular in relation to their design?
Are the students able to identify areas where their design may be improved, and reason about why?

6.2 Assignment Submission

Submit the assignment as one or several PDFs on It’s Learning.

Your submission shall include the following documents:

Class and Package Diagram
Implementation (Link to Github project is ok)

7 Sprint Acceptance Tests

You are done with this sprint when:

You have submitted the documents for marking.
You have received a passing grade from the teacher.

You may be asked to complement your submission with additional information.

You may also have:

Updated your Sprint Test Plan
Updated your Course Backlog