DESIGN REQUIREMENTS
PURPOSE
The program's goal is to enter teams or individuals into a competition so they can compete against
one another in mental challenges like sports and academics and receive points based on how well
they perform in those difficulties.
USER REQUIREMENTS
Teams can compete in a maximum of four events
Each team has a maximum of five participants.
Individuals can compete in a maximum of five events.
Each event will be designated as either a team or individual event.
Competitors will receive points based on how they place in each event.
The results of each event and the overall tournament will be displayed.
Competitors can enter for just one event.
CONSTRAINTS
Programmer Constraints
The biggest restriction I'll face is time. I have roughly 7 weeks to organise the program's creation and
functionalization. I will schedule my time to ensure that I finish it on time and that I can complete
each component of the program to a functional standard without rushing it.
The second limitation I'll experience is my level of skill. Since I'm still learning how to use Visual
Studio, I might find it difficult to finish some parts of the program, slowing down its completion. I'll
start learning more about forms, so I can get the software to work properly to make this less of a
problem.
The hardware that I use to develop the application can also be a limitation. If the computer I use is
too slow, progress might be slowed down because it will continually be freezing and crashing, and it
might not be able to manage what the application needs. I'll use Visual Studio and a computer
powerful enough to run the software to stop it from doing this.
User Constraints
Understanding how to utilise the program could be a limitation for the user. The instructions for
using the program must be very clear because if they are not, the user may become annoyed and
may give up on trying to use the application. By making labels that will steer them in the right way, I
will make sure that this issue is minimised.
The design of the application may be the user's last restriction. The user will find it difficult to utilise
the program efficiently if the colours are too unappealing or the program's overall layout is
disorganised, which could cause the tournament to stall out at critical stages. The user and the
competitors may grow impatient and restless as a result, which may cause them to withdraw from
the competition.
I'll employ a well-organized interface that is pleasing to the eye and makes it plain how to utilise the
program to avoid this from happening.
,SOFTWARE DEVELOPMENT LIFE CYCLE
Software engineers can design and create new software using the software development life cycle as
a guide. Defining the scope and range is the first stage. To accomplish this, you can carry out
research to make sure the software project is appropriate to produce. This will ascertain whether it
is legal, politically correct, the technology is available, you have the time to finish the program, and
there is sufficient funding to produce the program. Determining whether the project should move
forward, be postponed, or be cancelled comes after the study is finished.
The next step is to conduct research to determine what the client expects from the program,
including what they need it for, the systems that are currently in place, and the anticipated qualities
of the program, such as the user interface. You should interview the customer to completely grasp
what they anticipate from the program to get this information.
The design stage comes next. The processing performance, RAM needs, functionality requirements,
how data will be held, data types that will be used, relationships between various data entities, data
validation, and wireframes should all be included in this for any software builder to construct it. And
finally, creating the program. As the program is being developed, the programmer must continue to
review the specifications to ensure that everything is included.
Once the program has been constructed, it is time to test it, which is a crucial stage since this is
when you can observe how other people interact with the program and determine whether they can
use it effectively. The program must then be deployed. This refers to situations where the program
will be used, such as when it replaces an outdated system, when it is utilised by numerous
organisations, or when safety is a concern. The continuation of the program is the last stage. This
makes it feasible for individuals to ensure that it is current, has the fewest defects possible, and that
issues are fixed as soon as they arise.
DESIGNS
PROJECT TIMELINE
Dates Stage Work to be completed Completed
09/03/20-15/03/20 Analysis
Recognize the goal of the assignment 13/03/20
Create a project schedule or plan. 13/03/20
User requirements for design requirements 13/03/20
16/03/20-22/03/20 Design
Make the application's design. 18/03/20
Make a general Flow Chart 21/03/20
23/03/20-29/03/20 Design
Make Individual Flow Charts 27/03/20
30/03/20-05/04/20 Design
Create Pseudo code 05/04/20
20/04/20-26/04/20 Develop
Make the Forms 25/04/20
27/04/20-03/05/20 Develop
Add code to add Teams 01/05/20
Add code to add individuals 03/05/20
04/05/20-10/05/20 Develop
Add code to add Teams scores 08/05/20
Add code to add Individuals scores 10/05/20
, FORMS AND DATA DESIGN
Exit
(Button)
Displays options for the user to view participants or scores.
Menus loads
ScoresButton = Input (Goes to the Scores page)
ParticipantsButton = Input (Goes to the Participants page)
PURPOSE
The program's goal is to enter teams or individuals into a competition so they can compete against
one another in mental challenges like sports and academics and receive points based on how well
they perform in those difficulties.
USER REQUIREMENTS
Teams can compete in a maximum of four events
Each team has a maximum of five participants.
Individuals can compete in a maximum of five events.
Each event will be designated as either a team or individual event.
Competitors will receive points based on how they place in each event.
The results of each event and the overall tournament will be displayed.
Competitors can enter for just one event.
CONSTRAINTS
Programmer Constraints
The biggest restriction I'll face is time. I have roughly 7 weeks to organise the program's creation and
functionalization. I will schedule my time to ensure that I finish it on time and that I can complete
each component of the program to a functional standard without rushing it.
The second limitation I'll experience is my level of skill. Since I'm still learning how to use Visual
Studio, I might find it difficult to finish some parts of the program, slowing down its completion. I'll
start learning more about forms, so I can get the software to work properly to make this less of a
problem.
The hardware that I use to develop the application can also be a limitation. If the computer I use is
too slow, progress might be slowed down because it will continually be freezing and crashing, and it
might not be able to manage what the application needs. I'll use Visual Studio and a computer
powerful enough to run the software to stop it from doing this.
User Constraints
Understanding how to utilise the program could be a limitation for the user. The instructions for
using the program must be very clear because if they are not, the user may become annoyed and
may give up on trying to use the application. By making labels that will steer them in the right way, I
will make sure that this issue is minimised.
The design of the application may be the user's last restriction. The user will find it difficult to utilise
the program efficiently if the colours are too unappealing or the program's overall layout is
disorganised, which could cause the tournament to stall out at critical stages. The user and the
competitors may grow impatient and restless as a result, which may cause them to withdraw from
the competition.
I'll employ a well-organized interface that is pleasing to the eye and makes it plain how to utilise the
program to avoid this from happening.
,SOFTWARE DEVELOPMENT LIFE CYCLE
Software engineers can design and create new software using the software development life cycle as
a guide. Defining the scope and range is the first stage. To accomplish this, you can carry out
research to make sure the software project is appropriate to produce. This will ascertain whether it
is legal, politically correct, the technology is available, you have the time to finish the program, and
there is sufficient funding to produce the program. Determining whether the project should move
forward, be postponed, or be cancelled comes after the study is finished.
The next step is to conduct research to determine what the client expects from the program,
including what they need it for, the systems that are currently in place, and the anticipated qualities
of the program, such as the user interface. You should interview the customer to completely grasp
what they anticipate from the program to get this information.
The design stage comes next. The processing performance, RAM needs, functionality requirements,
how data will be held, data types that will be used, relationships between various data entities, data
validation, and wireframes should all be included in this for any software builder to construct it. And
finally, creating the program. As the program is being developed, the programmer must continue to
review the specifications to ensure that everything is included.
Once the program has been constructed, it is time to test it, which is a crucial stage since this is
when you can observe how other people interact with the program and determine whether they can
use it effectively. The program must then be deployed. This refers to situations where the program
will be used, such as when it replaces an outdated system, when it is utilised by numerous
organisations, or when safety is a concern. The continuation of the program is the last stage. This
makes it feasible for individuals to ensure that it is current, has the fewest defects possible, and that
issues are fixed as soon as they arise.
DESIGNS
PROJECT TIMELINE
Dates Stage Work to be completed Completed
09/03/20-15/03/20 Analysis
Recognize the goal of the assignment 13/03/20
Create a project schedule or plan. 13/03/20
User requirements for design requirements 13/03/20
16/03/20-22/03/20 Design
Make the application's design. 18/03/20
Make a general Flow Chart 21/03/20
23/03/20-29/03/20 Design
Make Individual Flow Charts 27/03/20
30/03/20-05/04/20 Design
Create Pseudo code 05/04/20
20/04/20-26/04/20 Develop
Make the Forms 25/04/20
27/04/20-03/05/20 Develop
Add code to add Teams 01/05/20
Add code to add individuals 03/05/20
04/05/20-10/05/20 Develop
Add code to add Teams scores 08/05/20
Add code to add Individuals scores 10/05/20
, FORMS AND DATA DESIGN
Exit
(Button)
Displays options for the user to view participants or scores.
Menus loads
ScoresButton = Input (Goes to the Scores page)
ParticipantsButton = Input (Goes to the Participants page)
