Requirements in software development are specific functionalities, constraints, and
expectations of the software. They ensure that the software meets the needs and
expectations of its users.

Functional requirements describe what the software should do, while non-functional
requirements specify quality attributes.
Defining requirements helps in 
effective planning, design, development, and testing processes.
assists in managing project scope, i want you to make a requirments defintion for my game the features of the game include a timed mode something that stores data and highscores 3 diffrent gamemodes such as guess the word beat the shark and a timed mode there is also a login page use this 
Requirements Definition Techniques
Year 11 So�ware Engineering
Requirements defini�on is a crucial phase in project management and development. It involves
gathering, analysing, and documen�ng the needs and expecta�ons of stakeholders to establish clear
and concise project requirements. Below are various techniques commonly used to define
requirements effec�vely.
1. Stakeholder Analysis: Stakeholder analysis helps iden�fy and understand the individuals or
groups impacted by the project. Analysing stakeholders' needs, expecta�ons, and poten�al
influences aids in capturing comprehensive project requirements.
2. Interviews: Conduc�ng interviews with stakeholders provides an opportunity to gather
requirements directly from them. Asking relevant ques�ons and ac�vely listening during
interviews helps elicit valuable informa�on and ensures a thorough understanding of stakeholder
perspec�ves.
3. Surveys and Ques�onnaires: Surveys and ques�onnaires are useful for gathering input from a
large number of stakeholders efficiently. Designing well-structured surveys with targeted
ques�ons allows for the collec�on of quan�ta�ve and qualita�ve data regarding requirements.
4. Observa�on: Observing stakeholders in their natural work environments provides insights into
their processes, challenges, and requirements. By directly witnessing their interac�ons and
behaviours, you can gain a deeper understanding of their needs and iden�fy poten�al
requirements.
5. Brainstorming: Brainstorming sessions encourage stakeholders to generate ideas, explore
possibili�es, and contribute to the requirements defini�on process. Facilita�ng brainstorming
sessions promotes collabora�ve thinking and helps uncover unique and innova�ve requirements.
6. Prototyping: Crea�ng prototypes or mock-ups allows stakeholders to visualize and interact with
the proposed solu�on early in the process. Prototyping helps validate requirements, gather
feedback, and refine the project's direc�on before finalizing the requirements.
7. Document Analysis: Reviewing exis�ng documents such as business cases, project charters, or
previous requirements specifica�ons provides valuable insights into the project's context and
requirements. Analysing these documents helps extract relevant requirements and ensures
alignment with project objec�ves.
8. Use Cases and User Stories: Use cases and user stories are effec�ve techniques for capturing
func�onal requirements. Use cases describe interac�ons between stakeholders and the system,
while user stories focus on specific user needs. These techniques provide a clear understanding
of how stakeholders will interact with the solu�on.
9. Valida�on and Verifica�on: Valida�ng and verifying requirements is crucial to ensure they are
complete, consistent, and testable. Techniques such as reviews, inspec�ons, walkthroughs, and
prototyping can be employed to validate requirements, while verifica�on involves confirming that
requirements meet predefined quality criteria.
Remember, selec�ng the most appropriate requirements defini�on techniques depends on the
project's nature, available resources, and stakeholder characteris�cs. Apply these techniques
strategically to ensure successful requirements defini�on and project outcomes. and this is the assigmnet 
Page
1
of 4
Year 11 Assessment Task Notification
TAS
Course: Software Engineering Student: __________________________________
Teacher: Ms Bell, Mr McCure Head Teacher: Ms Bell & Mr Skelton
Task Number: 1 Assessment Task: Programming Fundamentals
Date Issued: Week 6 Term 1 Due Date: Week 1 Term 2
Assessment Receipt:
You are to complete the Sign Off Quiz on Canvas to acknowledge receipt of your Year 11 Assessment Notification.
Task Type: Digital Folio and Practical Submission
Syllabus Outcomes, Weightings and Components:
Outcomes
Syllabus Components and Weighting Task
Weightings
Knowledge and understanding of
course content
Knowledge and skills in the practical
application of the content
SE-11-01, SE-11-02, SE-
11-06, SE-11-07 10% 20% 30%
Task Summary:
You are to individually develop a console-based guess the word game that conforms to the traditional rules of the
game. The game must have the following features:
• 3 difficulties for the player to choose from:
o Easy: 4-5 letter words
o Medium: 6-7 letter words
o Hard: 8+ letter words
• Guessed letters are displayed.
• Progress is displayed in the form of a console graphic i.e. Beat the shark, a race between a player and CPU.
• Scoring system – every player starts on 100 points and for each incorrect guess, 10 points are deducted. If a
player does not guess the word, they receive 0 points.
o High scores need to be saved for each difficulty AND saved between sessions along with the high
score player’s name. High Scores need to be readily accessible without having to play the game.
• Add 2 additional features of your choosing i.e. timer.
In addition, you are required to follow the waterfall approach when developing the game and create the following
documentation:
• Requirements Definition: Outline what the game needs to achieve.
• Design: Data dictionary, Structure chart, Screen designs and Algorithms
• Development: Create your ‘guess the word’ game.
• Testing: Test data for your game & perform and report errors and testing.
Game Development and accompanying documentation.
Component Marks
Requirements Definition: Clearly outlines the game's objectives and functionality and what the game
will achieve.
4
Design: Provides a comprehensive data dictionary, structure chart, screen designs and algorithms that
model the project effectively.
10
Development
Task understanding and implementation: Implements all task requirements provided from above. 10
Loops and conditional statements, data types and structures: Utilises a variety of loops, data
types and structures to effectively move data. Conditional statements are efficient in allowing choice
for the user.
5
Readability: Appropriate naming of functions and variables. All files have adequate commenting
throughout. The structure is logical and clear throughout all game development files.
10
Problem-solving: Applies a wide range of problem-solving and programming skills to meet the
requirements and specifications of the game.
10
User Interface and User experience: Implements an effective, intuitive, and consistent user
interface that is user-centred and simple to learn and navigate.
5
Testing: Provides appropriate sets of test data and results of desk checking. Explain 2 errors (e.g.
syntax, logic, and runtime errors), bugs and problems encountered during the project and how these
problems were resolved.
6
TOTAL 60
Year 11 Assessment Task Notification
TAS
Marking Criteria (Outcome Based):
Students will be assessed on how well they:
• Describes techniques and tools used to plan and document software solutions
• Describes the use of programming structures such as sequence, selection, and iteration and the purpose and
function of modular design.
• Uses appropriate software tools and programming environments to create and test solutions.
• Applies ethical standards and data privacy considerations when developing solutions.
Drafting Process and Assessment Feedback:
• There will be no formal submissions of drafts for this task, with no formal feedback being provided.
• Ongoing feedback will be provided in class verbally during assessment lessons only.
• Any other questions or feedback on the task will be provided through the discussion board for the task.
Submission Information:
Digital Submission:
• You are to submit your assessment via the Canvas drop box prior to 8.30am on Wednesday 30th April 2025.
This includes:
o Completed report as a word document (.doc file)
o Python source code file with detailed comments explaining the implementation key requirements
• You must keep a copy of your assignment
• No emailed submissions or flash drives will be accepted
• If you are unable to submit the assessment on or before the due date, you will need to complete an
illness/misadventure form and submit to the Faculty Head Teacher as per the Assessment Handbook
• Late submissions will result in marks being deducted as per Assessment Handbook
• Unjustified and/or unexplained absences in any periods the day before and/or the day of the task may
result in a penalty as per the Assessment Handbook
On submission of the hand-in assessment task, the student must:
a) Detach this cover sheet from the Assessment Task Notification and submit it with their assessment task at
the time of submission
b) Complete the Student Receipt below with the correct information
c) Ensure that both they and the teacher sign the Student Receipt
d) Ensure that the teacher detaches the Student Receipt from the cover page and returns it to the student
e) Retain the Student Receipt as evidence of the submission of their work
--------------------------------------------------------------------------✂-------------------------------------------------------------------
Student Receipt of hand-in Assessment Task Submission:
I have submitted the task, (task name) on / / (date)
The work I have submitted is all my own work and includes correct acknowledgement and reference to the work of
others used to create this task. I have read and accept the rules and procedures detailed in the school’s Preliminary
Assessment Handbook.
Student Name: Student Signature:
I acknowledge that I have received the above-mentioned task from this student on the date stated.
Teacher Name: Teacher Signature:
Additional Information:
• Please carefully read and follow the Task Description and Marking Criteria above.
• Read the Year 11 Assessment Handbook for further information about assessment rules and procedures.
• You must submit the task on Canvas prior to 8.30am on Wednesday 30 th April 2025.
Criteria Outstanding High Sound Basic Limited Total
Requirements
Definition
SE-11-01
SE-11-02
4 3 2 1 0
4
Provides a comprehensive and
detailed outline of the game's
objectives and functionality.
Provides a thorough outline of
the game's objectives and
functionality.
Provides an outline of some
of the game's objectives and
functionality.
Provides a basic outline
of the game's objectives
and functionality.
Provides a vague or
incomplete outline of the
game's objectives and
functionality.
Design
SE-11-01
SE-11-02
10 9-8 7-5 4-3 2-0
10
Provides comprehensive and
detailed design models including
all the following: data dictionary,
structure chart, screen designs,
and algorithms that effectively
meet the requirements of guess
the word.
Provides design models
including all the following: data
dictionary, structure chart,
screen designs, and algorithms
that meet the requirements of
guess the word.
Provides design models less
than 4 of the following: data
dictionary, structure chart,
screen designs, and
algorithms that meet the
requirements of guess the
word.
Provides some design
models of the following:
data dictionary, structure
chart, screen designs,
and algorithms that may
not meet the
requirements of guess
the word.
Provides minimal design
models that may not
meet the requirements of
guess the word.
Task
understanding
and
implementation.
SE-11-07
10 9-8 7-5 4-3 2-0
10
Implements all task requirements
accurately and effectively,
including difficulties, player
choices, scoring system, high
scores saving, and additional
features. Demonstrates complete
understanding of the task.
Implements most task
requirements accurately and
effectively. Demonstrates a high
level of understanding of the
task.
Implements some task
requirements accurately and
effectively and demonstrates
a good level of
understanding of the task.
Implements few task
requirements accurately
and effectively.
Demonstrates basic level
of understanding of the
task.
Demonstrates limited
understanding of the
task.
Loops and
conditional
statements, data
types and
structures
SE-11-07
5 4 3 2 1-0
5
Demonstrates exceptional use of
loops, data types, and structures,
with highly efficient and effective
conditional statements.
Demonstrates use of loops,
data types, and structures, with
mostly efficient and effective
conditional statements.
Demonstrates some use of
loops, data types, and
structures, with generally
efficient and effective
conditional statements.
Demonstrates basic use
of loops, data types, and
structures, with limited
efficiency and
effectiveness in
conditional statements.
Demonstrates minimal or
no use of loops, data
types, and structures,
with ineffective
conditional statements.
Readability
SE-11-07
10 9-8 7-5 4-3 2-0
10
Demonstrates an extensive
understanding of programming
logic and programming language
syntax to develop a highly
effective, reliable and efficient
solution. The solution is
accurately and clearly
documented using both internal
and intrinsic documentation
methods.
Demonstrates a thorough
understanding of programming
logic and programming
language syntax to develop a
mostly effective, reliable and
efficient solution. The solution is
documented using both internal
and intrinsic documentation
methods.
Demonstrates a sound
understanding of
programming logic and
programming language
syntax to develop a mostly
effective and reliable
solution. The solution is
documented using both
internal and intrinsic
documentation methods.
Demonstrates a basic
understanding of
programming logic and
programming language
syntax to develop a
somewhat effective
solution. The solution is
documented using either
internal or intrinsic
documentation methods.
Demonstrates an
elementary
understanding of
programming logic and
programming language
syntax. Coded solution
includes little or no
documentation.
Problem-solving
SE-11-07
10 9-8 7-5 4-3 2-0
10
Applies outstanding problem-
solving skills to code a solution
Applies highly developed
problem-solving skills to code a
Applies sound problem-
solving skills to code a
Applies basic problem-
solving skills to code a
Coded solution shows
little logical structure with
that follows a logical structure,
using the correct syntax, contains
an accurate and reliable algorithm
which is free of syntax and logic
errors, is highly readable and
efficient, and solves all
components identified in the
problem description.
solution that follows a mostly
logical structure, using mostly
correct syntax, contains an
accurate and reliable algorithm
which is mostly free of syntax
and logic errors, is mostly
readable, and solves most of
the components identified in the
problem description.
solution that follows a sound
logical structure, using
mostly correct syntax, has a
sound level of readability,
and solves most
components identified in the
problem description.
solution that shows some
basic logical structure,
using some correct
syntax, and solves some
components identified in
the problem description.
few examples of correct
syntax and readable
code and does not fully
solve components
identified in the problem
description.
User Interface and
User experience
SE-11-07
5 4 3 2 1-0
5
Implements an effective, intuitive,
and consistent user interface that
is user-centred and simple to
learn and navigate.
Implements an effective, and
consistent user interface that
mostly is user-centred and
simple to learn and navigate.
Implements a consistent
user interface that is simple
to learn and navigate.
Implements an
inconsistent user
interface that the user
can navigate.
Inconsistent user
interface.
Testing
SE-11-06
6 5 4 3-2 1-0
6
Provides comprehensive and
appropriate test data, thorough
desk checking results, and clear
explanations of 2 errors, bugs or
problems encountered with
effective resolutions.
Provides suitable test data,
detailed desk checking results,
and explanations of 2
errors/bugs encountered with
effective resolutions.
Provides adequate test data,
desk checking results, and
explanations of 2
errors/bugs encountered
with reasonable resolutions.
Provides limited test
data, minimal desk
checking results, and
brief explanations of 2
errors/bugs encountered
with basic resolutions.
Provides minimal or no
test data, desk checking
results, or explanations
of errors/bugs
encountered and
resolutions.
TOTAL
SE-11-06 /60 ensure i get 4/4 only do the requirments defination tracking progress
meeting desired objectives. incoprate this into the thing above A blueprint or set of guidelines for the software's development. 


Features, properties, or behaviours a system must have to
achieve its purpose. Each requirement must be verifiable.nitial stage is crucial and often overlooked
Failed projects result from poor requirements definition
Correct and accurate requirements are essential for project
success
Client agreement on system requirements is important Defining Requirements

Functional requirements define specific features
and behaviors that the software must exhibit.
The user should be able to create an
account and log in to the application using
their email and password.
The user should be able to search for
products by entering keywords in the
search bar.
The user should be able to add items to
their shopping cart and proceed to checkout
for payment.
The application should load within 3
seconds on both desktop and mobile
devices.
The application should be responsive and
compatible with popular web browsers
such as Chrome, Firefox, and Safari. 
The application should be secure and
protect user data using encryption and
secure authentication protocols.Compile a list of required outputs and determine the necessary
inputs, creating models that show the flow of data through the
system.
Consider all aspects of the system, including existing
requirements and hardware limitations, and consult with potential
users to determine their needs.
The set of requirements should clearly and precisely define each
aspect of the problem and will be used to test the success of the
solution.Client statements are often general or non-specific, requiring
refinement into achievable and verifiable statements.
Requirements should clarify and specify the client's requests to
ensure they are achievable and measurable.
Examples include monitoring sales across stores or improving
customer relations and turnaround times. use all this information to make a better requrments defintion using the thing i sent you before too the one with the assignkment task