Month: April 2018

Learning Objective: to demonstrate understanding of the Software Requirements Specification in relation to your folio.

Theory:

No new theory this week. You’ll be working on constructing your SRS for your folio.

Programming:

This week we’ll discuss how to “edit” existing users in a CSV file. This requires loading a CSV file, updating a single user in the file, and saving the modified data back to the file.

• Create a User Interface for editing a student in a Student Management System.
  This program must take as input:
  • Unique Identifier (CASES ID) – e.g.: SMI0001

  Once the data has been entered, the program should load the contents of the file allStudents.csv. It should check each line of the file to see if the unique identifier appears. If it appears, it should display the user details in the same way as shown on your ‘add student’ program, but with each entry pre-filled. Your program should allow for saving any changes back to the allStudents.csv file.

Homework:
Theory: Continue working on your SRS at home. Make sure you keep appropriate backups.
Programming: Complete the programming task for the week. Due: 09/05/201

Learning Objective: to be able to develop a Python application for saving and loading data.

Reminder: you have a SAT checkpoint this week – evidence will be checked in class time.

Theory:

We’ll be looking at functional and non-functional requirements as part of an SRS. You will have time to work on your Software Requirements Specification for your SAT in class time.

Programming:

The programming task is the same as last week.

Homework:
Programming: Complete the programming task for the week. Due: 2/05/2018.

Learning Objective: to be able to select solution designs based on relevant factors.

Reminder: you have a SAT checkpoint in Week 2 – evidence will be checked in class time in the double period.

Theory:

Read Chapter 5 of your textbook – pages 53-56 until the end of ‘Annotated diagrams or mock-ups’. Also read pages 64-68 starting at ‘Factors influencing the design of solutions’.

Programming:

1. Create a User Interface for adding a student for a Student Management System.
   Your program must take as input:
   • Unique Identifier (CASES ID) – e.g.: SMI0001
   • First name, last name
   • Date of birth
   • Team, as a dropdown
   • Year
   • Active (True/False)

   Once the data has been entered, it should save to a file called allStudents.csv. This file should contain all students (one per line) and be in CSV text format.

2. Extension: Create a User Interface for editing a student in a Student Management System.
   This program must take as input:
   • Unique Identifier (CASES ID) – e.g.: SMI0001

   Once the data has been entered, the program should load the contents of the file allStudents.csv. It should check each line of the file to see if the unique identifier appears. If it appears, it should display the user details in the same way as shown on your ‘add student’ program, but with each entry pre-filled. Your program should allow for saving any changes back to the allStudents.csv file.

Homework:

Theory: Answer questions 7 and 8 from your textbook. Due: 23/April/2018.
Programming: Complete the programming task for the week. Due: 2/May/2018.