Unit 4: Assessment 2
P4- Produce a design for a computer program to meet client requirements.
Brief
I'm a junior employee at a small software development company, and we've been invited by a local
college to judge an upcoming tournament. The college plans to host a competition where students
can participate either as individuals or part of a team. They are aiming for 4 teams, each with 5
members, and a total of 20 spaces for individual competitors. Every participant, whether in a team or
alone, will go through 5 events, which can be either team-based or individual challenges. These
events will cover various types, from sports to academic challenges.
For the scoring system, points for each event are yet to be decided, and the college is open to
suggestions. Also, they want to include an option for participants to enter for just one event if they
prefer.
My task is to design and develop a computer program to manage the scoring system for the
tournament. The program should handle the complexities of ranking individuals and teams based on
their performance in each event. This involves creating an interface where users can input scores and
ensuring that the program accommodates both team and individual events. I'll be gathering feedback
from potential users to make sure the program meets the needs of the tournament effectively.
Software Development Life Cycle
The Software Development Life Cycle is like a plan that helps make software really good without
spending too much money and time. It has different steps that make sure the software is well-made
and tested before people use it. This plan turns what users want into a form that programmers can
use to make the software just right for each person. The cycle can be long or short, but it always has
six steps. Understanding these steps is important to write the code and make a good design for a
finished product. Some ways to think about this plan include the waterfall model, spiral model, and
agile model. They help people understand the software development life cycle in more detail with
good quality and documentation.
First, in the beginning of the life cycle, there's a necessary check to understand a specific problem.
This problem could be about coming up with an idea, the steps to make it happen, the software, or
dealing with customers and people who will use it. The main goal in this first step is to guide the
developers so they really understand what they need to do and what the final goal is. This helps the
developers have a detailed description that's good enough to think about and makes the criteria right
for the work. Also, it helps them know what's expected from them and how to present it to the
community and the people they want to attract.
The second step in making software is to plan and design how it will work. The team needs to check if
the project is possible and figure out the best way to make it happen with the least risk. Using the first
step, where they checked the problem, makes the design easier to find because there are specific
points that the user needs to do for it to work. In the design, they make a flowchart that shows how the
code will be created, like what information needs to be put in and what comes out.
,For example, in the software I'm working on, I need to get the team's name, the members, individual
names, and the events. The team has to decide if the user puts in this info or if the program does it
with a formula. The output is what the program makes for the user, and they need to decide what
values to create and how to show them on the screen. In my case, I need to show the overall score
next to the person's name and the event number.
Another important part is designing how the user will use the software. Since my software is simple
and just records scores, I need to make sure it's easy to use. So, I design the screen layout, make clear
buttons, label text boxes, and show important info like overall scores. This helps users easily explore
and move around the system without a lot of trouble. To make it better, I can test it with users, get
feedback, and make changes if needed. They also need to figure out the calculations and checks the
software will use.
In my software, I want the program to pay attention to the specific tasks it was given so that important
points in the project, called 'milestones,' can be reached smoothly. This is crucial for making sure the
software development goes well and keeps clients happy with the progress. It's really important to
have enough details about the event, user, player, and team or individual involved in the project. This
makes sure that good decisions can be made, and the system's look is organized and easy to
understand, making it clear what needs to be done.
The third step is when the developer starts to build the actual code of the program using a
programming language they choose. They follow the design plan they made earlier, which is like a map
showing what parts to create. This helps them fix any mistakes and make sure everything works
smoothly. The values that go in and out of the program, and how they're shown, are crucial in picking
the right programming language.
For example, if the program needs the user to click a button to go to new screens, they'd choose an
event-driven language. But if the program only needs values to be entered, they'd go for an object-
oriented programming language. In my case, I picked Python because it's an object-oriented
language. This means it's based on 'objects,' like fields and components that make up something
bigger. For instance, it has variables, which are like building blocks that create larger pieces of data
such as words, blocks of code, and more.
Now, we're at the implementation stage. At this point, everything from the project comes together.
This includes things like code, design, the plan, documentation, and the final system. We need to
know details about the device, application or area used for programming, the operating system (OS),
and the type of language used (like Python, Java, C++, etc.). This helps make sure everything is safe
and the work is done really well with a lot of care and effort.
Now, we're at the testing stage. In this stage, we want to make sure there are no mistakes or issues in
the program. If there are any problems, they should be fixed right away. The testing needs to be visible,
showing the whole process clearly in the documentation. This makes sure the code has no errors, and
the user interface is simple and easy to use.
This testing process also makes sure the program is accurate and gives the same results from the
same data. It checks that the program is strong and won't crash or lag when handling a lot of data.
There are two ways to test a program. The first way is to think about how a user might use the
application – like creating a team or adding a person. This ensures that common tasks are easy for the
user. The second way is to use a trace table. This keeps track of the inputs, processes, and outputs of
, the program. It tests the data by putting it into the program and checking if the program gives the
expected output. For example, in my program, if a team wins three events, they should get ten points
for each win. If the program says they only won one point for each win, then there's a problem with
how the program calculates things.
The very last step in the software development life cycle is maintenance. There are two main reasons
for this. First, we take the feedback from users and the testing they did, then we make changes to the
program. This helps make the user's experience better because it improves how the program works
and makes it easier to use. Second, maintenance is done to make sure the program stays useful for a
long time. After finishing a program, we can add new features or make changes to match what the
users need and want. An example of this is in video games. They are often updated with new things,
fixing errors, and adding extra content. The goal is to make users keep playing the game for a longer
time and come back to enjoy new things, even after a year.
This is why software development life cycle is really helpful and important when we want to design,
document, and create programs.
[ Buy the assignment to see more ]
P4- Produce a design for a computer program to meet client requirements.
Brief
I'm a junior employee at a small software development company, and we've been invited by a local
college to judge an upcoming tournament. The college plans to host a competition where students
can participate either as individuals or part of a team. They are aiming for 4 teams, each with 5
members, and a total of 20 spaces for individual competitors. Every participant, whether in a team or
alone, will go through 5 events, which can be either team-based or individual challenges. These
events will cover various types, from sports to academic challenges.
For the scoring system, points for each event are yet to be decided, and the college is open to
suggestions. Also, they want to include an option for participants to enter for just one event if they
prefer.
My task is to design and develop a computer program to manage the scoring system for the
tournament. The program should handle the complexities of ranking individuals and teams based on
their performance in each event. This involves creating an interface where users can input scores and
ensuring that the program accommodates both team and individual events. I'll be gathering feedback
from potential users to make sure the program meets the needs of the tournament effectively.
Software Development Life Cycle
The Software Development Life Cycle is like a plan that helps make software really good without
spending too much money and time. It has different steps that make sure the software is well-made
and tested before people use it. This plan turns what users want into a form that programmers can
use to make the software just right for each person. The cycle can be long or short, but it always has
six steps. Understanding these steps is important to write the code and make a good design for a
finished product. Some ways to think about this plan include the waterfall model, spiral model, and
agile model. They help people understand the software development life cycle in more detail with
good quality and documentation.
First, in the beginning of the life cycle, there's a necessary check to understand a specific problem.
This problem could be about coming up with an idea, the steps to make it happen, the software, or
dealing with customers and people who will use it. The main goal in this first step is to guide the
developers so they really understand what they need to do and what the final goal is. This helps the
developers have a detailed description that's good enough to think about and makes the criteria right
for the work. Also, it helps them know what's expected from them and how to present it to the
community and the people they want to attract.
The second step in making software is to plan and design how it will work. The team needs to check if
the project is possible and figure out the best way to make it happen with the least risk. Using the first
step, where they checked the problem, makes the design easier to find because there are specific
points that the user needs to do for it to work. In the design, they make a flowchart that shows how the
code will be created, like what information needs to be put in and what comes out.
,For example, in the software I'm working on, I need to get the team's name, the members, individual
names, and the events. The team has to decide if the user puts in this info or if the program does it
with a formula. The output is what the program makes for the user, and they need to decide what
values to create and how to show them on the screen. In my case, I need to show the overall score
next to the person's name and the event number.
Another important part is designing how the user will use the software. Since my software is simple
and just records scores, I need to make sure it's easy to use. So, I design the screen layout, make clear
buttons, label text boxes, and show important info like overall scores. This helps users easily explore
and move around the system without a lot of trouble. To make it better, I can test it with users, get
feedback, and make changes if needed. They also need to figure out the calculations and checks the
software will use.
In my software, I want the program to pay attention to the specific tasks it was given so that important
points in the project, called 'milestones,' can be reached smoothly. This is crucial for making sure the
software development goes well and keeps clients happy with the progress. It's really important to
have enough details about the event, user, player, and team or individual involved in the project. This
makes sure that good decisions can be made, and the system's look is organized and easy to
understand, making it clear what needs to be done.
The third step is when the developer starts to build the actual code of the program using a
programming language they choose. They follow the design plan they made earlier, which is like a map
showing what parts to create. This helps them fix any mistakes and make sure everything works
smoothly. The values that go in and out of the program, and how they're shown, are crucial in picking
the right programming language.
For example, if the program needs the user to click a button to go to new screens, they'd choose an
event-driven language. But if the program only needs values to be entered, they'd go for an object-
oriented programming language. In my case, I picked Python because it's an object-oriented
language. This means it's based on 'objects,' like fields and components that make up something
bigger. For instance, it has variables, which are like building blocks that create larger pieces of data
such as words, blocks of code, and more.
Now, we're at the implementation stage. At this point, everything from the project comes together.
This includes things like code, design, the plan, documentation, and the final system. We need to
know details about the device, application or area used for programming, the operating system (OS),
and the type of language used (like Python, Java, C++, etc.). This helps make sure everything is safe
and the work is done really well with a lot of care and effort.
Now, we're at the testing stage. In this stage, we want to make sure there are no mistakes or issues in
the program. If there are any problems, they should be fixed right away. The testing needs to be visible,
showing the whole process clearly in the documentation. This makes sure the code has no errors, and
the user interface is simple and easy to use.
This testing process also makes sure the program is accurate and gives the same results from the
same data. It checks that the program is strong and won't crash or lag when handling a lot of data.
There are two ways to test a program. The first way is to think about how a user might use the
application – like creating a team or adding a person. This ensures that common tasks are easy for the
user. The second way is to use a trace table. This keeps track of the inputs, processes, and outputs of
, the program. It tests the data by putting it into the program and checking if the program gives the
expected output. For example, in my program, if a team wins three events, they should get ten points
for each win. If the program says they only won one point for each win, then there's a problem with
how the program calculates things.
The very last step in the software development life cycle is maintenance. There are two main reasons
for this. First, we take the feedback from users and the testing they did, then we make changes to the
program. This helps make the user's experience better because it improves how the program works
and makes it easier to use. Second, maintenance is done to make sure the program stays useful for a
long time. After finishing a program, we can add new features or make changes to match what the
users need and want. An example of this is in video games. They are often updated with new things,
fixing errors, and adding extra content. The goal is to make users keep playing the game for a longer
time and come back to enjoy new things, even after a year.
This is why software development life cycle is really helpful and important when we want to design,
document, and create programs.
[ Buy the assignment to see more ]
