Assessment Feedback Sheet
Reflection and Re-submission
Request
Overall Assessment
Grade Achieved
Learner Name
Assessor Name
Qualification Title BTEC Level 3 National Extended Diploma in Computing
Unit/Module No./Title Unit 23: Systems Methodology
Assignment No./Title Unit 23.2
Learning Aim(s) B: Apply systems methodology tools and techniques to identify and solve a
computing problem
C: Review a solution to a computing problem.
Issue Date Planned Submission Date Actual Submission Date
First/Second Submission
Criteria Criteria Assessor’s Feedback Your feedback should include:
Achieved What the learner has done well. (Knowledge, skills, etc.)
What the learner has not achieved and what was missing.
Information or guidance available to the learner they could have drawn on (e.g. class
notes; handouts; resources in assignment brief etc.)
☐
☐
☐
☐
BTEC Rules
All resubmissions must be authorised by the Lead Internal Verifier. Only one resubmission is possible per assignment, providing:
The learner has met initial deadlines set in the assignment, or has met an agreed deadline extension.
The tutor considers that the learner will be able to provide improved evidence without further guidance.
Evidence submitted for assessment has been authenticated and accompanied by a signed and dated declaration of authenticity by the learner.
Any resubmission evidence must be submitted within 10 working days of receipt of results of assessment (BTEC only)
,Wider Skills (Linked to Positive Futures) Comment on the quality of the learner work, the learner’s process and practice during assessment, research
skills, presentation, general behaviour and conduct, meeting deadlines, etc.
I certify that, to the best of my knowledge, the evidence submitted for this assignment/assessment is the learner’s own. I
Assessor Declaration understand that false declaration is a form of malpractice.
Assessor Signature: Date:
I certify that the evidence submitted for this assignment/assessment is my own. I have clearly referenced any sources
Learner Declaration used in the work. I understand that false declaration is a form of malpractice.
, Learner Signature: Date:
Learner Actions
Actions linked to
Learner’s Targets/Actions
following Positiv
What needs to be developed to improve future work?
Futures outcome
☐ Confiden
☐ Commitm
☐ Collabora
☐ Resilienc
, Unit 23.2 – Systems Methodology
Task 1 - P3
In this assignment, we are assigned to work with one of the chosen scenarios and I
have chosen the Noughts and crosses/ Tic Tac Toe scenario. We have to now
design, develop and plan to work with the scenario.
Tic-Tac-Toe is played on a three by three grid by two players, who place X or O turn
by turn in one of the nine spaces of the grid.
I have to design, develop and plan this game with the requirements written above
using systems methodology. Furthermore, I would need to produce enough
documentation so that this work can be continued if needs be.
This project has a timeline till June which equates to two months.
Before I can start with solving this problem given, I would need to confident that I
have the relevant tools (MS Visio, Unity, Visual Studio, MS Project etc) and the
relevant knowledge.
I have chosen to do Rapid Application Methodology for this project.
Requirements of the scenario:-
The requirements for this scenario are quite ambiguous so I'll be assuming some of
the requirements myself.
A simple menu to select and start the game.
A simple interface to enhance the user experience as the game is supposed
to have a GUI.
There can only be two players at once max, either the player vs the PC or two
players playing on the same machine simultaneously.
Creating a game of Noughts & Crosses that will be run on Windows OS using
C#.
The game has to have a GUI.
Must use systems methodology to complete the project.
Problem Statement
Tic-Tac-Toe is played on a three by three grid by two players, who place X or O turn
by turn in one of the nine spaces of the grid.
I have to design, develop and plan this game with the requirements written above
using systems methodology. Furthermore, I would need to produce enough
documentation so that this work can be continued if needs be.
This project has a timeline till June which equates to two months.
,Before I can start with solving this problem given, I would need to confident that I
have the relevant tools (MS Visio, Unity, Visual Studio, MS Project etc) and the
relevant knowledge.
Rules for the Game
The game has to be played on a grid that’s 3 squares by 3 squares.
One player is X and one is O, and both take turns in inputting their marks in the
empty squares.
The first player to get 3 of their marks in a row (either up, down, across or diagonally)
is declared as the winner.
If all the 9 squares become full, then the game is over.
This also means that if no player has been able to have 3 marks in a row, then the
game ends in a tie.
Players must only get one turn, with no way to return (stays permanent).
Methodology
I have chosen to use the Rapid Application Methodology (RAD) for this project.
I think RAD (agile methodology) is the best choice as a methodology for this project
for a couple of reasons: -
Less time spent on planning and modelling and more actually on creating
prototypes.
As it’s a game (this means that the requirements are very likely to change)
and the requirements given are also very ambiguous so this agile
methodology is able to accommodate those changes.
The GUI requirements are ambiguous, so with each prototype the I could get
more feedback from my client (teacher) and this way I would be able to better
meet the client’s expectations.
RAD allows for free movement in any stage within the project which is not
possible with traditional methodologies like Waterfall.
, More chances of success / client satisfaction as the solution will go through
prototypes and not just one final solution.
,Task 2: Apply systems methodology to develop
the project solution
Design
User interface
I have decided to create this game in command line interface (CLI) so this game will not
have very special design. To show where the users can place their crosses or ticks, a table
will be shown to them, but it will be created with all ASCII characters as this game will be
made in CLI.
Just for reference purposes, I have attached an example image that I have taken inspiration
from and decided to create user interface similar to this: -
| | (" {0} | {1} | {2}_____|_____|_____ | | {0} | {1} | {2} _____|_____|_____ | | {0} | {1} | {2} | |
Structure Diagram
, Pseudocode
Flow chart
, Class diagrams (Not OOP so not included)
Testing plan
Test Description Test Data Expected Result
Number of Test
1a Program “Hello, and Welcome to the The program should output the data once the
outputs a Tic-Tac-Toe Game” game starts
welcome
message
2a The program “Please enter your The program lets the user input and stores
lets the user username” the username
input their
username.
3a) The program ["-", "-", "-", The program outputs an empty board
outputs a "-", "-", "-", prompting the user to input their answer
plain board. "-", "-", "-"]
3b) Check if the “10” The program wouldn’t let the user to choose
position of a position that is not within the board.
the
responses is
within the
range of 1-9
3c) Check if the “2” The program would output that the position is
position the “2” already taken.
user is
entering is
already
taken or not.
4a) Check if the XXX in board 3,4,5 = WIN The program would return win if either player
game is has successfully entered their responses in
over/ check three boxes either straight or diagonally.
for win
4b) Check if the XOX in board 1,2,3 = DRAW The program should output “DRAW” to tell
game is at a the players that the game has concluded at a
draw draw and no one has won
5a The program | | (" {0} | {1} | The program should have a GUI in the form
Reflection and Re-submission
Request
Overall Assessment
Grade Achieved
Learner Name
Assessor Name
Qualification Title BTEC Level 3 National Extended Diploma in Computing
Unit/Module No./Title Unit 23: Systems Methodology
Assignment No./Title Unit 23.2
Learning Aim(s) B: Apply systems methodology tools and techniques to identify and solve a
computing problem
C: Review a solution to a computing problem.
Issue Date Planned Submission Date Actual Submission Date
First/Second Submission
Criteria Criteria Assessor’s Feedback Your feedback should include:
Achieved What the learner has done well. (Knowledge, skills, etc.)
What the learner has not achieved and what was missing.
Information or guidance available to the learner they could have drawn on (e.g. class
notes; handouts; resources in assignment brief etc.)
☐
☐
☐
☐
BTEC Rules
All resubmissions must be authorised by the Lead Internal Verifier. Only one resubmission is possible per assignment, providing:
The learner has met initial deadlines set in the assignment, or has met an agreed deadline extension.
The tutor considers that the learner will be able to provide improved evidence without further guidance.
Evidence submitted for assessment has been authenticated and accompanied by a signed and dated declaration of authenticity by the learner.
Any resubmission evidence must be submitted within 10 working days of receipt of results of assessment (BTEC only)
,Wider Skills (Linked to Positive Futures) Comment on the quality of the learner work, the learner’s process and practice during assessment, research
skills, presentation, general behaviour and conduct, meeting deadlines, etc.
I certify that, to the best of my knowledge, the evidence submitted for this assignment/assessment is the learner’s own. I
Assessor Declaration understand that false declaration is a form of malpractice.
Assessor Signature: Date:
I certify that the evidence submitted for this assignment/assessment is my own. I have clearly referenced any sources
Learner Declaration used in the work. I understand that false declaration is a form of malpractice.
, Learner Signature: Date:
Learner Actions
Actions linked to
Learner’s Targets/Actions
following Positiv
What needs to be developed to improve future work?
Futures outcome
☐ Confiden
☐ Commitm
☐ Collabora
☐ Resilienc
, Unit 23.2 – Systems Methodology
Task 1 - P3
In this assignment, we are assigned to work with one of the chosen scenarios and I
have chosen the Noughts and crosses/ Tic Tac Toe scenario. We have to now
design, develop and plan to work with the scenario.
Tic-Tac-Toe is played on a three by three grid by two players, who place X or O turn
by turn in one of the nine spaces of the grid.
I have to design, develop and plan this game with the requirements written above
using systems methodology. Furthermore, I would need to produce enough
documentation so that this work can be continued if needs be.
This project has a timeline till June which equates to two months.
Before I can start with solving this problem given, I would need to confident that I
have the relevant tools (MS Visio, Unity, Visual Studio, MS Project etc) and the
relevant knowledge.
I have chosen to do Rapid Application Methodology for this project.
Requirements of the scenario:-
The requirements for this scenario are quite ambiguous so I'll be assuming some of
the requirements myself.
A simple menu to select and start the game.
A simple interface to enhance the user experience as the game is supposed
to have a GUI.
There can only be two players at once max, either the player vs the PC or two
players playing on the same machine simultaneously.
Creating a game of Noughts & Crosses that will be run on Windows OS using
C#.
The game has to have a GUI.
Must use systems methodology to complete the project.
Problem Statement
Tic-Tac-Toe is played on a three by three grid by two players, who place X or O turn
by turn in one of the nine spaces of the grid.
I have to design, develop and plan this game with the requirements written above
using systems methodology. Furthermore, I would need to produce enough
documentation so that this work can be continued if needs be.
This project has a timeline till June which equates to two months.
,Before I can start with solving this problem given, I would need to confident that I
have the relevant tools (MS Visio, Unity, Visual Studio, MS Project etc) and the
relevant knowledge.
Rules for the Game
The game has to be played on a grid that’s 3 squares by 3 squares.
One player is X and one is O, and both take turns in inputting their marks in the
empty squares.
The first player to get 3 of their marks in a row (either up, down, across or diagonally)
is declared as the winner.
If all the 9 squares become full, then the game is over.
This also means that if no player has been able to have 3 marks in a row, then the
game ends in a tie.
Players must only get one turn, with no way to return (stays permanent).
Methodology
I have chosen to use the Rapid Application Methodology (RAD) for this project.
I think RAD (agile methodology) is the best choice as a methodology for this project
for a couple of reasons: -
Less time spent on planning and modelling and more actually on creating
prototypes.
As it’s a game (this means that the requirements are very likely to change)
and the requirements given are also very ambiguous so this agile
methodology is able to accommodate those changes.
The GUI requirements are ambiguous, so with each prototype the I could get
more feedback from my client (teacher) and this way I would be able to better
meet the client’s expectations.
RAD allows for free movement in any stage within the project which is not
possible with traditional methodologies like Waterfall.
, More chances of success / client satisfaction as the solution will go through
prototypes and not just one final solution.
,Task 2: Apply systems methodology to develop
the project solution
Design
User interface
I have decided to create this game in command line interface (CLI) so this game will not
have very special design. To show where the users can place their crosses or ticks, a table
will be shown to them, but it will be created with all ASCII characters as this game will be
made in CLI.
Just for reference purposes, I have attached an example image that I have taken inspiration
from and decided to create user interface similar to this: -
| | (" {0} | {1} | {2}_____|_____|_____ | | {0} | {1} | {2} _____|_____|_____ | | {0} | {1} | {2} | |
Structure Diagram
, Pseudocode
Flow chart
, Class diagrams (Not OOP so not included)
Testing plan
Test Description Test Data Expected Result
Number of Test
1a Program “Hello, and Welcome to the The program should output the data once the
outputs a Tic-Tac-Toe Game” game starts
welcome
message
2a The program “Please enter your The program lets the user input and stores
lets the user username” the username
input their
username.
3a) The program ["-", "-", "-", The program outputs an empty board
outputs a "-", "-", "-", prompting the user to input their answer
plain board. "-", "-", "-"]
3b) Check if the “10” The program wouldn’t let the user to choose
position of a position that is not within the board.
the
responses is
within the
range of 1-9
3c) Check if the “2” The program would output that the position is
position the “2” already taken.
user is
entering is
already
taken or not.
4a) Check if the XXX in board 3,4,5 = WIN The program would return win if either player
game is has successfully entered their responses in
over/ check three boxes either straight or diagonally.
for win
4b) Check if the XOX in board 1,2,3 = DRAW The program should output “DRAW” to tell
game is at a the players that the game has concluded at a
draw draw and no one has won
5a The program | | (" {0} | {1} | The program should have a GUI in the form
