Month: March 2018

Learning Objective: to understand the role of DFDs and Context Diagrams in creating an SRS.

Theory

This week we’ll be looking at Data Flow Diagrams and Context Diagrams which are methods of describing systems and how users and external processes interact with them.

Programming:

• Complete the Hangman program that’s due first day back next term.
• If you’ve finished, use the double period to complete the Context Diagram and Data Flow Diagram tasks in Visio.
• If you don’t have time to finish it at school, use the following program to complete it at home: http://dia-installer.de/download/index.html – Dia is also available for MacOS.

Homework:
Complete the DFD and Context Diagram tasks from class. Due 16/Apr/2018.

Learning Objective: to understand the role of Use Case Diagrams in creating an SRS.

Theory

This week we’ll be looking at Use Case Diagrams, a method of describing systems and how users and external processes interact with them.

You should also be documenting your interviews with your client. Your interviews and other data collection will be part of the next SAT Observation Checkpoint, early next term.

Programming:

• Continue working on the hangman program that you started last week – implement the core functionality to get a word, then play the game.

Homework:
Theory: Complete the Use Case Diagram tasks given to you in class. Due: Monday, 26th March, 2018.
Programming: Complete the Hangman program. Due: Wednesday, 28th March, 2018.

Learning Objective: to demonstrate your ability to make user interfaces in Python.

This week is a SAC week.

ATTENTION YEAR 11s: You are exempt from attending the study skills workshop periods 1 & 2 and will instead attend Periods 3 & 4. Please see Ms McGongegal to confirm your attendance for Periods 3 & 4.

You will be required to respond to a design brief to produce a user interface in Python. You may be required to get data from the user interface and/or update widgets in the user interface.

At a minimum, you should be comfortable using the following widgets:

1. Label, including images
2. Entry, including getting information from an entry
3. OptionMenu
4. Button

You will receive a practice SAC in Tuesday’s class, however, if you have completed all of the programming homework this year, this is adequate preparation for the SAC.

This SAC is worth 15% of the SAC outcome for Unit 3.

Homework: Prepare for the SAC.

Learning Objective: to know the components of the Software Requirements Specifications and how it relates to the SAT.
Learning Objective: to demonstrate knowledge of programming techniques to read and write to files.
Learning Objective: to know how to display and changes images in Python using Tkinter.

Theory

This week we’ll be looking at a Software Requirements Specification template. You should begin following your Gantt chart in regards to client interviews and data collection.

Programming

This week we’ll be looking at reading and writing to files, as well as creating more user interfaces for practice.

You are required to program a hangman game with a GUI interface. The words used in the game will be randomly chosen from a text file that will be provided to you. The images you will use to represent the hangman getting “hung” will also be provided to you.

1. Design the GUI on paper or in excel, using the grid system.
2. Annotate your UI design to explain why you chose some of your design elements, such as how the user inputs a letter.
3. Create the user interface (only) in Python.
4. Begin incorporating the logic of hangman into your program.

Homework
Theory: continue following your project plan. Begin collecting data and schedule your first interviews with your client.
Programming: Finish the user interface for hangman. Due: 14th March, 2018.