CPSC 480 Software Engineering (SE) Spring 2023

News

• Week 4 Class 8 Thu Feb 02 Posted: Feb 02

  After Class

  • Crosswords

    Crossword Labs had an update in the past couple of days. Printing is much more standard. So now you can

    1. Print using the Print feature in your browser
    2. Use the print button

  Announcements

  • Exercise 14: Requirements Report Repository

    If you did not create your repository in GitHub Classroom for Project 1, then I will assume you will not be working on it, and therefore I can already give you a 0 on the project. It is too late to get credit for the exercise, but if you still want to submit the project later, create your repository in GitHub Classroom.

  • Team Folders Take your graded work from the Team folder during the Team Meeting time. Do not leave it in the folder. If you are working on paper, use a clean sheet of paper for each Team Meeting.

  Class

  • HFSD Chapter 4

  • Exercise 15: HFSD Chapter 4 Crossword

  • Exercise 16: Team Tasks

  • Exercise 17: Individual Tasks

    Divide up the user stories without tasks among all present members of the team.

    For next class, create tasks for each of your user stories. Do this on paper or electronically. Do not write them on the cards until the next class meeting time.

    At no time are you to take home the user story or task cards from the team folder.

    Upload a PDF or PNG to Brightspace.

    This is due by 4:30 pm on Monday, Feb 6

  Unless otherwise indicated, exercises are due by 4:30 pm on Fri Feb 03

• Exercise 16: Team Tasks Posted: Feb 01

  Reminders

  • Every time you look at the set of user stories, you may see improvements. These improvements include wording, grammar, capitalization, terminology, and even if the team should split a user story. The user stories can be updated right up until implementation. So, if you see any improvements, make them.

    In particular, make sure your user story titles are as good as they can be:

    • The title has to complete the sentence "A user should be able to …". Say the title outloud multiple times.
    • I see a lot of missing articles, i.e., "A", "An", "The".
    • Avoid weak words "Info", "Data", "System"

  • Remember to take your graded assignments from the folder.

  Steps

  1. Pick one of the user stories that you already have an estimate for. Create tasks for this user story only. I will provide smaller cards to write the tasks on.
  2. Use the estimation process to create an estimate for each task.
  3. Total the estimates for the tasks and compare them to the estimate for the user story.

  Each team member will turn in to Brightspace a separate document that includes each round of planning poker:

  • Title of the user story or task
  • The spread of estimates, indicating which one is yours
  • The team consensus (if the team was able to reach one in this round)
  • If the consensus changes the overall estimate of the user story
  • Any assumptions that you made
  • Any questions or confusions on the user story or task that is of interest

  I recommend you take notes as you go along. If on paper, do this exercise on a new sheet of paper. The uploaded document can be a PDF or a JPG.

• Project 1: Requirements Report Posted: Jan 31

  Project 1 is due 11:59:59 pm Friday, Feb 10, in the file Requirements.md in a GitHub Classroom repository. You will need a GitHub account. Once you have an account, an invitation link to create the repository is on the Brightspace course page.

  Description

  At your place of work, you need to submit a formal report describing the project's current state. Write a report of your individual and team activities, including:

  • User Stories with title, description, estimate, and space for priority
  • Details of the process and procedure that created the User Stories and their Estimates, including the spread and any assumptions
  • General observations on how the team interaction worked, what did and did not work well, and the overall process

  In other words, all the work and processes followed while creating the user stories and their estimates. The details of the process and procedure and the general observations are in the form of a narrative, i.e., describe what you did, how you did it, and the result, ordered by time. The report's tone is professional, with a clear, consistent presentation.

  The team created the User Stories and Estimates, but this report is an individual project. In your report, make changes to User Stories if they do not follow the guidelines given in the book. These changes are especially crucial for the Title and the Description. Split User Stories if the Estimate is too large. Explain any changes in your report.

  Format

  • Written in the plain-text formatting syntax Markdown
  • Identify yourself completely at the top of the page. That includes your name, email, team name, and section
  • Do not address me at the top of the page
  • Do not sign it at the bottom
  • The entire report must be in the single, self-contained file: Requirements.md
  • The report is to look good both as raw Markdown and as a web page in GitHub
  • Plain text (no .pdf, .doc, .docx, etc.)
  • UTF–8 encoding Note: An ASCII document is a UTF–8 document

  Score

  The report content, report format, and your involvement in team activities are all considered for your score.

  Think very carefully about the presentation of the report, including how you are using Markdown. Remember, the User Stories are an unordered set not an ordered list.