TR 12:15 - 1:30 pm (CAS) 135
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:
Our class starts are 12:15 pm as typical, but the Team's meeting starts at 12 pm as Team's has a limitation to selecting non-half-hour start and end times.
Announcements
Project 2 Keep in mind the following:
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.
Class
Make
$@
, $<
, and $^
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.
All exercises due by 3 pm on Monday, Oct 21
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.
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:
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 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:
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
TA: Ms. Afia Asante aa998@uakron.edu