480-020 SE News Archive

Archive

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.
- Exercise 4: HFSD Chapter 1 Sharpen Your Pencil - Results
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
- Exercise 8: Team User Stories
  - 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).
Week 2 Class 3 Tue Sep 02 Posted: Sep 02

Announcements:
- Exercise 3: App Idea I posted scores and feedback in Brightspace
  - "Do not identify yourself in the description"
  - "Submit via Brightspace in PDF form" Word documents are not PDFs
  View your feedback even if you got a 10 / 10. In some cases, a 10/10 does not mean there was nothing wrong.
  
  Fix any issues that I identified.
  
  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
- Exercise 4: HFSD Chapter 1 Sharpen Your Pencil - Results
Class
- HFSD Chapter 1
- Exercise 5: HFSD Chapter 1 Crossword
  - Print using browser (not a screenshot)
  - Include a timestamp with Headers and Footers (Chrome: More settings/Options; Safari: Safari/Print headers and footers)
- Exercise 6: Teams
Unless stated otherwise, all exercises are due by 3 pm on Wed Sep 03
Exercise 6: Teams Posted: Sep 02
Form a team of 4 members. The final team composition is at the discretion of the instructor.

After forming a team, your team needs to decide on a name from the following choices:
- Three Stooges (Moe, Larry, Curly, Shemp, Curly Joe)
- Marx Brothers (Chico, Harpo, Groucho, Gummo, Zeppo)
- Star Wars Characters
Pick at least 4 names.

Send Dr. Collard and Mr. Iddrisu an email with the following:
- Subject is CPSC480-020 Team
- CC all members of the team using their UA email address
- An attachment file, members.csv, in the CSV (Comma-Separated Values) format. Use the following as an example:
```
Firstname,Lastname,Email,Section,Team
John,Doe,johndoe@uakron.edu,020,Harpo
Jane,Doe,janedoe@uakron.edu,020,Harpo
Brian,Doe,briandoe@uakron.edu,020,Harpo
Suzy,Doe,suzydoe@uakron.edu,020,Harpo
```
- The body of the email is a list of requested team names in priority order, e.g.,
```
Harpo
Moe
Yoda
Zeppo
```
The purpose of a team is not just to divide the work but also to meet a required level of quality. All members of the team must check any team assignment in this course. You, as a team, are responsible for these directions. Any emails sent as part of an assignment (including exercises) must have the correct subject, CC list, and contents. Exercises are not accepted and do not receive points if they do not have the proper form and content.

The exercise is due by the end of class.
Week 1 Class 2 Thu Aug 28 Posted: Aug 28

Announcements:
- Scores I posted the feedback and scores in Brightspace for Exercises 1 & 2
- Survey Results
- Notes The class notes have a bunch of default and custom hotkeys. Type a "?" to see a list.
Class
- Notes: Roots
- Exercise 3: App Idea - Submit via Brightspace in PDF form. Due by 3 pm on Mon, Sep 1
  
  All applications start with an idea or a need. As a user, write a description of an application. The description should include who would use it and its features. The application can be one that you create yourself or an existing program.
  
  Guidelines:
  - The description must be at least 350 words long
  - Include a name for the app at the top
  - Do not identify yourself in the description
  - Assume this is a smartphone app
  - The description should be of the what not the how. Do not include any discussion of programming languages, libraries to use, or software design. Do not talk about how easy or difficult it would be to create the app. Do not describe the screens, views, or user interaction.
  - If the application already exists, be creative with your name and description
  Comments:
  - This is not the place if you have a great app idea. Your app idea may be shared with others or discussed (anonymously) with the entire class.
  - This is not the app that you or your future team will work on.
- HFSD: Chapter 1
- Exercise 4: HFSD p7 Sharpen Your Pencil Due by 3 pm on Fri, Aug 29
Week 1 Class 1 Tue Aug 26 Posted: Aug 26

Announcements
- Syllabus
- GitHub We use GitHub and GitHub Classroom in the class to manage documents and source code for projects, exercises, and examples. You are required to have a GitHub account. Optionally, you can apply for the Student Github Developer Pack and get a free GitHub Pro account. To apply, your account email can be a school account or a personal account if you upload documents to prove your current enrollment status.
- O'Reilly Online Learning The course textbooks are available in O'Reilly Online Learning. You do not have to be on the campus network (e.g., via VPN) to access O'Reilly Online Learning. To access, click the "Institution not listed?" link below the dropdown and enter your UA email. You will then create an account and use that account from now on. For more information: Library LibGuide
Exercises
- Exercise 1: SE Survey
- Exercise 2: Software Development Diagram
  
  Draw the Software Development Diagram that I present in class. Upload a PDF or JPG through Brightspace.
- Notes: Context
- For next class: Read Chapter 1 of the HFSD (Head First Software Development) book.
All exercises are due by 3 pm on Wed Aug 27
Welcome Posted: Aug 20
Greetings and welcome to CPSC 480 Software Engineering (SE) section 020 for Fall 2025.
- Syllabus The draft syllabus for the course is on the main course page. I will finalize the syllabus before our first class meeting.
- Survey The first exercise is to fill out the class survey. The survey is due after our first class meeting, but you can complete it before.
- Textbook The course has two textbooks. We start with the Head First Software Development (HFSD), available from Safari Books Online via a link at the bottom of the main course page.
- GitHub In the class, we use GitHub and GitHub Classroom to manage documents and source code for projects and examples. You are required to have a GitHub account. The account email (not necessarily the account name) should be your @uakron.edu email address. If it is, you can apply for the Student Github Developer Pack and get a free GitHub Pro account.
See you on Tuesday, Aug 26 at 12:15 - 1:30 pm in (CAS) room 134

CPSC 480-020 Software Engineering (SE) Fall 2025

Section 020 TR 12:15 - 1:30 pm (CAS) 134

Archive