DESIGN REQUIREMENTS
PURPOSE
The purpose of the program is to add teams of people or individuals into a tournament so they can
compete against each other with mental challenges such as sports and academic as well as get
scored based on how they do in those challenges.
USER REQUIREMENTS
Be able to add individuals and teams
Be able to remove individuals and teams
Maximum of 4 teams with 5 members
Maximum of 20 spaces for individuals
Teams will compete in 5 events
Individual will compete in 5 events
Each event to be defined as team or individual event
Will get points based on their ranking within each event
Will display who won each event and the overall tournament
Include the possibility for competitors can enter for one event only
CONSTRAINTS
Programmer Constraints
One of the main constraints that I’ll have is time. I have about 7 weeks to plan the programs
development and to make it functional. To make sure I complete it in time I will measure out my
time so I can complete each aspect of the program to a working standard and so I don’t end up
rushing it.
The next constraint that I’ll face is the amount of skill I have. I am still relatively new to Visual Studio,
so I might struggle to complete certain aspects of the program which slows down the completion
time. To make this less of an issue I will start to learn more about forms so I can get the program to
function correctly.
Finally, the hardware I create the program on could be a constraint. If the computer I use is not fast
enough, this could slow down progress as the computer will keep crashing, freezing and might not
be able to handle what the program requires. To prevent it from doing this I will use a good enough
computer to be able to run the program and Visual Studio.
User Constraints
A constraint that the user might face is knowing how to use the program. The program will have to
be very clear with how to use the program as if it is not clear enough, the user will get frustrated
with the program and might give up on trying to use the program. I will make sure that this problem
is minimised by creating labels that will point them in the correct direction.
The final constraint that the user might face is the design of the program. If the colours are to
unappealing or the general layout of the program is unorganised, the user will struggle to use the
program effectively which could make the tournament come to a halt at certain points. This can
make the user and the participants become restless and impatient, which could lead to them leaving
,the tournament. To prevent this from happening I will use an organised layout which is easy on the
eyes, plus clear on how to use the program.
SOFTWARE DEVELOPMENT LIFE CYCLE
The software development life cycle is a model for software developers to plan and produce new
software.
The first step is to define the range and scope. To do this you can conduct a study to ensure the
software project is ok to make, this will determine whether it’s legal, politically correct, the
technology is available, you have enough time to complete the program and there is enough money
to create the program. Once the study is complete the next step is to decide if the project should
continue, be delayed or cancelled.
After that, carry out an investigation to establish what the client is expecting from the program
including what they need it for, the current systems in place and the expected characteristics of the
program such as the user interface. To collect this information, you should interview the client to
fully understand what they expect from the program.
The next phase is the design. This should contain enough information for any software builder to
build it, it should contain the processing performance, RAM requirements, functionality
requirements, how data will be held, data types that are going to be used, relationships between
different data entities, data validation and wireframes.
Fourthly, developing the program. This is when the program is created, the programmer will have to
keep looking at the requirements to make sure that everything is added.
When the program is created, it’s time to test it which is a very important stage because this is
where you can see others interacting with the program and see if they can use the program
efficiently.
Then it’s time to deploy the program. This means where the program is going to be used such as
replacing the old system, many organisations using the system, and systems where safety is an issue.
The final phase is the maintenance of the program. This enables people to make sure that it is up to
date, has as little bugs as possible and problems are fix as when they appear.
, DESIGNS
PROJECT TIMELINE
Dates Stage Work to be completed Date
Completed
09/03/20-15/03/20 Analysis
Understand the assignment 11/03/20
Produce Project timeline/ plan 11/03/20
Design requirements – Purpose and User 11/03/20
requirements
16/03/20-22/03/20 Design
Create the design for the application 18/03/20
Create Overall Flow Chart 19/03/20
23/03/20-29/03/20 Design
Create Flow Charts for each form 26/03/20
30/03/20-05/04/20 Design
Create Pseudo code 02/04/20
20/04/20-26/04/20 Develop
Create the Menu form 21/04/20
Create the Events form 21/04/20
Create the Participant form 21/04/20
Create the TeamOrIndividual form 21/04/20
Create the AddTeam form 21/04/20
Create the AddIndividual form 21/04/20
Create the TeamCheck form 22/04/20
Create the IndividualCheck form 22/04/20
Create the TeamScores form 22/04/20
Create the IndividualScores form 22/04/20
27/04/20-03/05/20 Develop
Add code to add Teams 27/04/20
Add code to add individuals 30/04/20
04/05/20-10/05/20 Develop
Add code to add Teams scores
Add code to add Individuals scores
PURPOSE
The purpose of the program is to add teams of people or individuals into a tournament so they can
compete against each other with mental challenges such as sports and academic as well as get
scored based on how they do in those challenges.
USER REQUIREMENTS
Be able to add individuals and teams
Be able to remove individuals and teams
Maximum of 4 teams with 5 members
Maximum of 20 spaces for individuals
Teams will compete in 5 events
Individual will compete in 5 events
Each event to be defined as team or individual event
Will get points based on their ranking within each event
Will display who won each event and the overall tournament
Include the possibility for competitors can enter for one event only
CONSTRAINTS
Programmer Constraints
One of the main constraints that I’ll have is time. I have about 7 weeks to plan the programs
development and to make it functional. To make sure I complete it in time I will measure out my
time so I can complete each aspect of the program to a working standard and so I don’t end up
rushing it.
The next constraint that I’ll face is the amount of skill I have. I am still relatively new to Visual Studio,
so I might struggle to complete certain aspects of the program which slows down the completion
time. To make this less of an issue I will start to learn more about forms so I can get the program to
function correctly.
Finally, the hardware I create the program on could be a constraint. If the computer I use is not fast
enough, this could slow down progress as the computer will keep crashing, freezing and might not
be able to handle what the program requires. To prevent it from doing this I will use a good enough
computer to be able to run the program and Visual Studio.
User Constraints
A constraint that the user might face is knowing how to use the program. The program will have to
be very clear with how to use the program as if it is not clear enough, the user will get frustrated
with the program and might give up on trying to use the program. I will make sure that this problem
is minimised by creating labels that will point them in the correct direction.
The final constraint that the user might face is the design of the program. If the colours are to
unappealing or the general layout of the program is unorganised, the user will struggle to use the
program effectively which could make the tournament come to a halt at certain points. This can
make the user and the participants become restless and impatient, which could lead to them leaving
,the tournament. To prevent this from happening I will use an organised layout which is easy on the
eyes, plus clear on how to use the program.
SOFTWARE DEVELOPMENT LIFE CYCLE
The software development life cycle is a model for software developers to plan and produce new
software.
The first step is to define the range and scope. To do this you can conduct a study to ensure the
software project is ok to make, this will determine whether it’s legal, politically correct, the
technology is available, you have enough time to complete the program and there is enough money
to create the program. Once the study is complete the next step is to decide if the project should
continue, be delayed or cancelled.
After that, carry out an investigation to establish what the client is expecting from the program
including what they need it for, the current systems in place and the expected characteristics of the
program such as the user interface. To collect this information, you should interview the client to
fully understand what they expect from the program.
The next phase is the design. This should contain enough information for any software builder to
build it, it should contain the processing performance, RAM requirements, functionality
requirements, how data will be held, data types that are going to be used, relationships between
different data entities, data validation and wireframes.
Fourthly, developing the program. This is when the program is created, the programmer will have to
keep looking at the requirements to make sure that everything is added.
When the program is created, it’s time to test it which is a very important stage because this is
where you can see others interacting with the program and see if they can use the program
efficiently.
Then it’s time to deploy the program. This means where the program is going to be used such as
replacing the old system, many organisations using the system, and systems where safety is an issue.
The final phase is the maintenance of the program. This enables people to make sure that it is up to
date, has as little bugs as possible and problems are fix as when they appear.
, DESIGNS
PROJECT TIMELINE
Dates Stage Work to be completed Date
Completed
09/03/20-15/03/20 Analysis
Understand the assignment 11/03/20
Produce Project timeline/ plan 11/03/20
Design requirements – Purpose and User 11/03/20
requirements
16/03/20-22/03/20 Design
Create the design for the application 18/03/20
Create Overall Flow Chart 19/03/20
23/03/20-29/03/20 Design
Create Flow Charts for each form 26/03/20
30/03/20-05/04/20 Design
Create Pseudo code 02/04/20
20/04/20-26/04/20 Develop
Create the Menu form 21/04/20
Create the Events form 21/04/20
Create the Participant form 21/04/20
Create the TeamOrIndividual form 21/04/20
Create the AddTeam form 21/04/20
Create the AddIndividual form 21/04/20
Create the TeamCheck form 22/04/20
Create the IndividualCheck form 22/04/20
Create the TeamScores form 22/04/20
Create the IndividualScores form 22/04/20
27/04/20-03/05/20 Develop
Add code to add Teams 27/04/20
Add code to add individuals 30/04/20
04/05/20-10/05/20 Develop
Add code to add Teams scores
Add code to add Individuals scores
