IT4107 Fundamentals of Software Development Assessment T2 2026

IT4107 Fundamentals of Software Development 

Aim 

This project covers learning outcomes 2 and 3:

• Apply fundamental programming, mathematical and logical concepts and use relevant software development tools, including logic diagrams and pseudocode, in developing a simple application.
• Apply software development life cycle and other relevant development practices increating a simple application.” 

Due Date: Week 17 (some deliverables will be required at an earlier stage; please refer to the suggested due dates below)

How to Submit 

1. This assessment will be divided into smaller, more achievable parts called“Stages”, which will follow the typical steps of SDLC. 
2. Every stage will have its own due date, and every completed stage will earn you corresponding marks. (Refer to  Available Marks for Project  section below) 
3. Submit required files in Moodle. Remember to keep a backup copy of your assessment. 

Note:

• If an assessment is not handed in by the due date, a mark of zero will be recorded.
• NO extensions will be given, except in very rare situations (and only with the permission of the tutor).

Extensions: 

If you have a valid reason to ask for an extension, please send your tutor an email before the due date.

• Sickness – in which case a medical certificate must be presented to the tutor.
• Bereavement – in which case the tutor must be informed as soon as possible.
• Extenuating circumstances – these circumstances must be explained to the tutor, and proof may be required.

Available Marks for Project

Stages

Hold the Ctrl key and click on each stage for additional information

Stage 1: Plan and Analyse Requirements

Available Marks: 5
Due Date: August 8, 2025
Learning Outcome/s:3

Instructions:

You will be working with the client to complete this stage. (Note: For this project, the client is your tutor.) 

A meeting with the client will be held on week 7 (before the break) during your laboratoryclass.

Before the Meeting:

A statement of the client’s needs is provided below. Review this and come up with a list of questions and or suggestions for the meeting with the client.

Client

Can you help me develop an application that I can use for my car rental company? The application should do the following:

• Ask for the age of the driver.
• If the age of the driver is less than 16, the car should display on the screen“Sorry, you are too young to drive.” Then it should ask for the age of the driver again.
• If the age of the driver is at least 16, the car should ask the driver to scan their license.
• If the license is a Learner license, then the car should ask if the driver is accompanied by a supervisor.
• If the driver is accompanied by a supervisor, the car should ask the driver to scana supervisor’s license. 
• If the supervisor’s license is a Full license, the car should display on the screen“Thank you, drive safely.” 
• If the supervisor’s license is NOT a Full license, the car should display on the screen “A supervisor must have a full license.” Then it should ask for the age ofthe driver again.
• If the driver is not accompanied by a supervisor, the car should display on the screen “Sorry, you cannot drive on your own.” Then it should ask for the age ofthe driver again.
• If it’s not a learner’s license, then the license is a Full license, and the car should display on the screen “Thank you, drive safely.

During the Meeting:

Interact with the client. Find out what the client really needs by asking questions related to the client’s initial statement before the meeting. Suggest solutions when necessary. Remember that the client controls cost, functionality, and time, so you might want to ask questions related to these factors.

This activity should allow you to determine the scope of your work and outline the client’s requirements so that you can outline them in your Software Requirement Specification. 

After the Meeting:

Submit your notes on Moodle. This should be composed of the information gathered during the meeting. You may use the Minutes of the Meeting template provided by your tutor

Submission:

Submit the Minutes of the Meeting as aWord File (.docx)on Moodle.

Stage 2: Define Requirements

Available Marks: 10

Due Date: August 22, 2025

Learning Outcome/s:3

Instructions:

You may start attempting this stage only after you’ve met with the client to finalize therequirements of the product.

In this stage, your task is to convert the information gathered from stage 1 (Customer Requirement) to a more formal document called the Software Requirement Specification.

Use the MoSCoW method to specify the requirements of the client.

You may use the template provided by your tutor.

When you are finished drafting the Specification. Finalise it by adding two more pages to make it look more professional:

Cover Page – should include your logo and organisation name, a title, your name, and the date created.

Signature Page – a separate page placed at the end of the document; it should contain the following:

• a short sentence stating that both parties agree
• your signature above your name and your title
• a space for the client to sign above their name and their title

Submission:

Submit your signed Software Requirement Specification on Moodle. Your tutor will return it to you with the client’s signature. Submit the Specification as a Word File (.docx)on Moodle.

Stage 3: Design Your Simple Application

Available Marks: 15
Due Date: September 26, 2025 
Learning Outcome/s:2 and 3

Instructions: 

Before you start coding, show that you understand how the required simple application will function by constructing a flowchart showing the flow of your program.

Follow best practice to earn full marks. Refer to Lecture 3 for “Tips for an Effective Flowchart ”.

You may use this tool to construct the flowchart:https://app.diagrams.net/ 

Submission: Submit your design as anXML File (.drawio)on Moodle.

Stage 4: Develop Your Application

Available Marks: 50
Due Date: October 17, 2025 
Learning Outcome/s:2 and 3

Instructions: 

Using your flowchart as a guide, start coding the simple application using the Python language.

Your program should show your knowledge of the following coding techniques:

• Decisions
• Loops
• Arrays or Lists

Follow the coding guidelines and best practices identified in “Lecture 4: Introduction to Python”. This will include the following:

• Commenting on your code
• Proper indentations
• Naming convention for your variables
• Having one task per line of code

Submission:

Submit your simple application as a Python File(.py) on Moodle.

Stage 5: Test Your Application

Available Marks: 15
Due Date: October 24, 2025
Learning Outcome/s:2 and 3

Instructions: 

In this stage, you need to produce two documents:

1. Test Plan

• To ensure that you will produce an application set to the standard of the client, this document should outline your test strategy to cover every pre-conceived flaw of your application
• You may use the template provided by the tutor as a guide
• The client may ask for this document in one of your meetings before its due date

2. Test Report

• should report all defects found, including how issues were fixed, and that they were retested until the application reaches the quality agreed in our Software Specifications (Stage 2).
• You may refer to the sample test report provided by the tutor

Submission

Submit both documents as a Word File (.docx)on Moodle. Do not forget to attach a cover page to each document.

Stage 6: Deploy and Maintain

Available Marks: 5
Due Date: October 31, 2025
Learning Outcome/s:3

Instructions:

This is the last stage of your project.

You may start attempting this after you receive feedback from your client on your code and test report.

Depending on how happy your client is, your simple application will be released as it is or released with suggested enhancements.

In addition, your tutor will require you to write a closing report reflecting on your journey to accomplishing your project. A template will be provided to you.

Submission:

If there are suggested enhancements from the client, you will need to resubmit your .pyapplication and modified test report.

Submit the Closing Report as aWord File (.docx)on Moodle. Please remember to attach a cover page to make it more presentable.