Assignment

This assignment is a group assignment. The course management have created the groups and created a gitlab-group under ([https://gitlab.lnu.se/2dv013/student]) in this course group on Gitlab.lnu.se were you and your group members have access.

Assignment 3 (code 2203) is group assignment where the group submit it´s assignment by a "merge request" from the project repo in the team group.

  • Deadline 2024-01-14 23:59
  • Deadline 2024-02-16 23:59 (resubmission)
  • Deadline 2024-06-17 23:59 (resubmission, last chance for this course round)

The assignment

You group should create the social-media platform litter. How ever there are some none-functional requirements to fullfil.

Report 1

Must be submitted by December 8th in the group wiki.

From this date forward, the URL submitted should always respond with an HTTP 200.

The wiki should contain:

  • Link to start URL of the application.
  • Your deployment pipeline anatomy
  • Continuous Delivery principles adopted
  • Design
    • Microservices
    • Communication protocols, patterns (queues, et.c.)
    • Data persistency
    • Schematic drawing of the system (separate design meeting will be held to discuss this prior to hand-in.)

Report 2

Must be submitted by January 14th in the group wiki.

  • Link to start URL of the application.
  • Your deployment pipeline anatomy, incl. a reflection of the outcome
  • Continuous Delivery principles adopted, incl. a reflection of the outcome
  • Design, Up to date
    • Microservices
    • Communication protocols, patterns (queues, et.c.)
    • Data persistency
    • Schematic drawing of the system (separate design meeting will be held to discuss this prior to hand-in.)
  • A Post mortem
    • Title of project, authors, and date
    • Abstract: Explain briefly and concisely what your report is about and what conclusions you have reached.
    • Introduction and background: Describe the final product and purpose/goals of the project, methods, implementation/techniques, and other relevant information about what was done and how in the project. Keep to the facts and avoid expressing personal opinions. Consider that the reader may have a very different background and may not have much experience with software development, so refer to widely available sources as needed. Include one or more images showing important parts of the product. A brief description of the overall architecture may also be included here.
    • Positive experiences: Describe what you consider to have gone particularly well in your project and your analysis of why it was successful and how you can replicate this success in future projects.
    • Negative experiences: Describe what you consider to have gone poorly in your project and your analysis of why it was unsuccessful and how you can avoid this in future projects.
    • Summary: Bring your report together and draw conclusions from your experiences and lessons learned. Look ahead and see potential for development for both yourself and your product.

Final delivery

The project is submitted through a final delivery. This final delivery basically means that you create a "merge request" on the project you were assigned at the start of the course and which contains your Wiki.

Instructions:

  • Navigate to the project named "Project Litter" in your group on Gitlab.
  • Create a MR from your 'main' branch to your 'lnu/submit' branch.
  • Use the title "Submission, Final Delivery"
  • Carefully fill in the description. (see below)
  • Select the Milestone to which your final delivery is intended. (Important!)
  • Do not close your Merge Request. This is considered a withdrawn submission.
  • You can edit your "merge request" after it has been submitted. For example, test that all links work and fix those that are not correct.

You can also give feedback to the course staff by writing a comment to the course staff. Do this if you make any changes after the deadline.