CPSC 480 Software Engineering (SE) Fall 2024

News

---

• Week 8 Class 15 Tue Oct 15 Posted: Oct 15

  After Class

  • Tab indent with a Makefile in Visual Code

    You can use the Command Palette (View > Command Palette) and type Convert Indentation to Tabs and hit Enter.

  Special Announcement Tuesday's Class

  I have COVID and unable to be on campus for Tuesday, Oct 15:

  • Class will be online in Teams
  • Office Hours are online in Teams. Contact me there at collard@uakron.edu

  Our class starts ends at 3:15 pm as typical, but the Team's meeting ends at 3:30 pm as Team's has a limitation to selecting non-half-hour start and end times.

  Announcements

  • Mr. Kyle Rossi A public thanks to my RA for covering class last week.
  • Last Week I attended the 40th ICSME (International Conference on Software Maintenance & Evolution) in Flagstaff, Arizona. We took an academic family picture (which wasn't as large as this one. We had social events. We had a keynote from Denae Ford, one of the editors of Equity, Diversity, and Inclusion in Software Engineering. But the real work was that I conducted (along with my colleagues) a srcML workshop. A student presented our paper. And the MIP (Most Influential Paper), the paper from the same conference 10 years ago that had the most impact on the field, used srcML and, during their talk, specifically mentioned srcML
  • eduroam

  • Project 2 Keep in mind the following:

    • Each plan includes all user stories
    • Carefully check your calculations, including the numbers you are using
    • The unit of granularity for an iteration plan is an iteration, not day-by-day
    • Do not assign work to each developer
  • Project 2 Grading I will post some type of preliminary feedback on your plans by end-of-day on Wednesday. See the "After Class" for details.

  • Exercise 23: Project 1 "Fix spelling of "calendar": I posted scores and some feedback for the optional exercise, 23. I also added those to your Project 1 score.

    A large number of you did not do this exercise. If so, you missed an opportunity to improve your Project 1 grade by a whole letter grade by not completing an optional exercise. The exercise covered a crucial git workflow for software development and engineering. essential to software development and engineering.

  • Midterm Exam

  Class

  • Make

    build-files-020

    • GNU Make
    • Make Rule Introduction What a rule looks like
    • Special Note: recipes are indented using a tab character, not spaces. Using spaces (or an editor that expands tabs to spaces) will result in an invalid Makefile.
    • Automatic Variables including $@, $<, and $^
    • NMake Microsoft's version of Make
    • srcML Playground Generate new srcML of source code, input format for srccomplexity

  • Exercise 31: Makefile

    Code along and make the same commits with the same commit messages as I do in class.

    I suggest you use GitHub Codespaces as all necessary packages are installed.

  • Exercise 29: Make Crossword
  • Exercise 30: HFSD Chapter 6.5 Crossword

  All exercises due by 3 pm on Monday, Oct 21

• Midterm Exam Posted: Oct 03

  Note: I removed Chapter 6.5, cmake, and make from the Midterm. It will be on the Final Exam instead.

  The Midterm Exam is Thursday, October 17, during our regular class time and classroom. It covers Chapters 1 - 6 6.5 of the Head First Software Development book, plus notes and in-class examples.

  • Big Bang approach to development - description, the path it takes, and disadvantages
  • Iterative approach to development - description, the path it takes, and advantages
  • Role of the customer/client
  • User Stories - all parts, description, creation, valid user story titles
  • Use Case - Diagram and text, differences with User Stories
  • Estimates and the Estimation Process, including all details of planning poker
  • Iteration and deadline planning
  • Utopian vs. Real-World days
  • Velocity - description, standard rate, what does it mean if velocity is higher or lower
  • Big Board - basics of what it shows and how developers use it
  • Good-enough design, SRP, DRY
  • Version control - jobs that it does, commit messages, branches (specific git information not on this midterm)
  • Role and importance of build artifacts (code, configuration, tools), the general purpose of make and cmake; Given a Makefile, what would happen with specific targets.

  The exam has various problem types, including short answers, definitions, comparisons, creation of user stories, and planning. The question may require you to:

  • Explain a process or terminology of a process
  • Answer specific questions about parts of the process. E.g., "Explain why the recommendation is to come up with user stories whose estimates are 15 or less."
  • Explain what process and activities you would follow for a particular scenario

  It is a good idea to review the "Dumb Questions" and the answers.

  The questions are based on what we covered in the book, the exercises, and the projects. If I did not cover it in class, it is not on the exam.

  A calculator is not needed for any required math and, therefore, not permitted.

• Project 2: Iteration Plan Posted: Oct 01

  Project 2 is due on Tuesday, Oct 15 at 11:59:59 pm. A GitHub Classroom invitation link is on the Brightspace course page.

  For Project 2, take all the user stories from Project 1 and create a series of iteration plans.

  Use the examples in the book to show which parts of the user story you should show in your iteration plan (e.g., do not restate descriptions in the plans). Also, clearly state the entire new iteration plan for each plan, not just the changes. However, make sure to thoroughly discuss what the change was and what effect it had.

  This is an individual project. Each member of a team has different user-story priorities. To get individual priorities for Project 2, select the number of user stories:

  User Stories:
  

  Note: You may get a warning from your browser that the information is not secure. You can safely ignore that.

  Put these in the Priority field in the order in which you listed the user stories. In the report, do not discuss how you generated your report's priorities, i.e., pretend that the customer gave them.

  The following plans may require you to add additional user stories. This violates our rule that only the development team can create estimates. However, as part of the exercise, put in an estimate.

  Each plan is a point in time. For each plan, show the entire estimation iteration plan, including the iterations already completed.

  Plan	Events
  1	Create an initial iteration plan: 2 Weeks (14 calendar days) iteration, 2 developers, 0.6 velocity
  2	The customer adds two new user stories of the highest priority at the end of the first iteration. For the two new user stories, one is a new feature, and one is an emergency. Create a non-trivial estimate (i.e., an estimate that makes the planning interesting) for these new user stories.
  3	A user story with a non-trivial estimate takes twice as long. Assume this occurred right before the last iteration.
  4	At the beginning of the last iteration of your current plan, the other developer leaves for another project, and it is up to you to finish the project.

  After the plans, create a section with all of your user stories, including their titles, descriptions, estimates, and priorities. You will need estimates for all of your user stories.

  Regarding the format, GitHub Codespaces, checkmd, and a Final Check with an asciinema session, all of those requirements of Project 1 are also in effect for Project 2.

  Submit the URL via this form: Project 2

Archive