CPSC 480-010 Software Engineering (SE) Fall 2023

Project 1 is due 11:59:59 pm Thursday, Sep 28, 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:

• 1. User Stories
  • User Stories with title, description, estimate, and space for priority
  • This will be shown to the customer
• 2. General Process
  • Details of the process and procedure that created the Estimates
  • This will be shown to the customer, so only data on the User Story cards should be mentioned.
• 3. Background Data
  • Details on spread, assumptions, issues, etc.
  • How did the team interaction work, and what did and did not work well
  • This will not be shown to the customer. It is for your supervisor.

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 account, 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

• The report is in the plain-text formatting syntax Markdown. Markdown is an almost universal format for text formatting in software development. Due to its direct mapping to/from HTML, Markdown has replaced HTML and other plain-text formatting languages in SE.
• Identify yourself clearly at the top of the page with 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 a 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, format, and 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.