News
-
Week 2 Class 4 Thu Sep 04 Posted: Sep 04
Announcements:
- Office Hours The 10:30 - 11:30 am Office Hours are only from 10:30 - 10:45 am
-
Exercise 3: App Idea The feedback on Tuesday for this exercise included "If you fail to fix your issues or view your feedback by 3 pm on Wed Sep 03 I will change your score to a 0". Viewing feedback on an assignment is part of the exercise and project process. If you did not fix your issues or view the feedback, I changed your score to a 0.
-
Pattern Recognition
Pattern recognition and adaptation are essential skills in software development. This involves closely following examples while adjusting them to fit specific needs, whether working with APIs, formatting code, handling data, or configuration. Lacking this skill can complicate development, introduce bugs, and waste development time.
For the first team exercise, Exercise 6: Teams, the instructions clearly state to attach a file with the name
members.csv. Here is the list of attachment file names I received:As far as the content of the file:
Correct format:
Missing field name row:
Spaces that are not part of the data:
Quotes everywhere:
Wrong section format:
Very wrong section format:
Duplicate emails:
This is not even mentioning the lack of a EOL at the EOF.
Note For those teams who did not attach the file
members.csv, you can make it up by sending me a new email. The contents of members.csv must be exactly the same as the previous attachment.
Class
- HFSD Chapter 2
-
Exercise 7: HFSD Chapter 2 p42 User Story Interview
- Be sure to save your response
- You cannot go back and edit your response
- The number correct is your score out of 10
-
- Note that almost all Team Exercises will have individual notes due by the end of class.
Unless stated otherwise, all exercises are due by 3 pm on Fri Sep 05
-
Exercise 8: Team User Stories Posted: Sep 04
Each Team is assigned a separate App with the description in Brightspace.
As a Team, create as many User Stories as you can for that app from the app description. For now, this is just the Title and the Description. The Title is just an action that a user can perform. The Description is from 1 to 3 sentences that describes what that action is. Follow the examples given in the book.
The User Stories are written on the provided index cards. I will provide a folder for you to put the cards in as I will collect the cards at the end of class.
- I want a lot of user stories. Do not make any judgments on whether they are worthwhile or not. Do not stop at 6 or some specific number. Generate as many unique user stories as you can.
- You do not "own" a user story. The user story is part of the project. If you leave the project, the user stories do not go with you.
- For any assignment in this class, no user story should have a title that includes "Login" or any similar terms. Assume that they have already logged in or (much better) do not have to log in.
In addition to the team work of extracting user stories from the app description, each team member will turn in to Brightspace separate, individual notes that include:
- The total number of user stories created
- The titles of at least 3 user stories
The individual notes are due by the end of class uploaded to Brightspace. They can be in the form of a PDF (print to file from a computing device), or a JPG (picture taken via your phone).