Grade: Distinction
Software Development Life Cycle
When designing a new program to meet client requirements, it is beneficial for the programmer to use
SDLC so that they exactly know what stages must be undertaken to create a successful solution to the
problem given. Software development life cycle (SDLC) is a process, which focuses on the development
and the detail that go in to making software. This consists all stages that software must go through,
before the release. There are several different methodologies that all go about in describing the process,
in more detail then others however generally they all present the same types of ideas about developing,
improving and the upkeeping of the software. Some of the SDLC methodologies are called SCRUM, V-
CYCLE and WATERFALL. Each of these methodologies can be modified to fit the needs of an individual
user as well as to fit the type of software being developed. The most common software development
methodology is called SPIRAL:
Most software development cycle methodologies consist of these stages:
• Requirement Analysis (STAGE 1)
In this stage, the overall problem is presented and the user requirements are established. This is to
ensure that the program will be fit for the purpose to solve the problem given. This is the most
crucial stage of software development as this ensures that the software will be made with a
purpose to fulfill the requirements. To do that the programmer can research about the types of
software that were made similar to the one given in task.
,Grade: Distinction
In my case, I have been provided with a set of requirements listed below that my program must
fulfil. The fact that I have been given those requirements means that I can now use those
requirements as a benchmark of what the program that I will create must do, this will exactly allow
me to identify the progress that I’m making as well as make me aware if I am going in the right
direction.
• Design specification (STAGE 2)
This stage is mainly based on stage of the requirement. This is because in this stage the
programmer must think about the best way, to find a solution for a problem given that meets the
requirements. This includes the layout of the program such as the GUI, all the inputs and outputs
required to make this solution successful, the timescale required to make the solution and the
extent to which will the program will meet client requirements.
In my case, I will be thinking about the best way to structure the program not only the code,
however I will be thinking on how to make the GUI as efficient as possible. I am going to be thinking
about the information that will need to be inputted such as the Employee name and number of
hours worked as well as the outputs required such as total pay. Finally, I will need to think on how
to make my solution meet all the client requirements such as being compliant with the GDPR. I also
intend on creating a test plan, that will cover the requirements and ensure the final software meets
its purpose and functionality. I will also be making a flowchart to illustrate how the program will
work.
• Develop code (STAGE 3)
In this stage, the program is developed. This means that any initial algorithms and pseudo codes are
written. When developing a solution, it is crucial that the programmer chooses the language that is
the mostly suited for solving the problem given. It is important to keep the program organized and
well commented to ensure, any adjustments and further continuation can be made with ease.
In my case, I have decided to make the program in VBA this is due to the flexibility and the
suitability of the language as it allows for the use of GUI’s as well as coding. This should make the
whole user experience better and easier therefore it’s the most suitable language for the task. I will
also be keeping my code neat through the paradigm used by the language. When suitable I will
write pseudo code to fit the flow chart I have created in stage 2 about the functionality of the
program. I will be thinking about the structure of the program.
• Implementation and Coding Phase (STAGE 4)
In this stage, this is where the programmers need to think about the paradigms they are using and
take all the designs of pseudo-codes, flowcharts and algorithms and make the functional product in
actual life. This is an important stage, because this is where everything comes together, with the
focus on the program. This stage tends to be the longest stage in the entire cycle.
In my case, I will be using an Object orientated paradigm and I will take all the designs I have made
from stage 3 and transfer them into code to create a fully functional software that meets the
requirements ready to be tested within the next phase of the cycle. I will be aiming to make the
solution as robust as possible.
, Grade: Distinction
• Testing (STAGE 5)
In this stage the software made, is tested for functionality against the original client requirements.
This should verify that all the features are working correctly and should identify some possible
improvements that can be made to improve the programs robustness to make it more optimized.
I my case, I intend on using a test plan from stage 2 to focus the software’s functionality as well as
the user requirements given in the requirements stage. I will also be modifying the test plan created
to ensure its suitability in regard to the software while trying to focus on ensuring there are no
internal errors and bugs that may affect the users experience. I intend on clarifying that the
program works as intended as well as meets all the requirements mentioned. Dependent on the
results of the test plan I will be trying to make refinements in the software to improve its
robustness as well as efficiency.
• Deployment (This stage is optional dependent on the type of software being developed and
methodology used)
This stage is where the improved and tested version of the program is released, and has started
being used by the company. This stage replaces the old software with the new one ensuring that
the new software meets the requirements
In my case, I will not be replacing any software as this is the initial release as there has not been any
software used prior to this one.
• Maintenance / Evolution (STAGE 6)
Maintenance is after the software has been implemented, the software will constantly be
monitored for any errors, if found this stage is there in place to ensure that those errors/bugs get
fixed. In addition, this stage allows for modification of the software to increase the functionality and
meet any additional needs, if software is found to be incapable to be modified the cycle starts again
to create a software that will meet the requirements.
In my case, I will not be there to maintain the software and add any improvements after the release
however I will try to make the program as optimized as possible (I will be using the testing phase to
find any possible areas of improvements), and I will leave suitable code comments to ensure
anyone else in the future can modify and maintain the software if required.
Introduction
As a junior software developer for a games company, the department of finance have assigned a task for
me to develop a basic payroll system that calculates the weekly wages for the employees. I have been
given requirements which I must work with. These requirements are:
• Pay Rates must be introduced as a list
• An employee must work 35 basic hours before overtime can be added
• Access to overtime must be restricted but not password restricted
• Overtime hours are paid double
• The program should alert its users when 20 hours of overtime have been reached but this
should not stop the calculations
Software Development Life Cycle
When designing a new program to meet client requirements, it is beneficial for the programmer to use
SDLC so that they exactly know what stages must be undertaken to create a successful solution to the
problem given. Software development life cycle (SDLC) is a process, which focuses on the development
and the detail that go in to making software. This consists all stages that software must go through,
before the release. There are several different methodologies that all go about in describing the process,
in more detail then others however generally they all present the same types of ideas about developing,
improving and the upkeeping of the software. Some of the SDLC methodologies are called SCRUM, V-
CYCLE and WATERFALL. Each of these methodologies can be modified to fit the needs of an individual
user as well as to fit the type of software being developed. The most common software development
methodology is called SPIRAL:
Most software development cycle methodologies consist of these stages:
• Requirement Analysis (STAGE 1)
In this stage, the overall problem is presented and the user requirements are established. This is to
ensure that the program will be fit for the purpose to solve the problem given. This is the most
crucial stage of software development as this ensures that the software will be made with a
purpose to fulfill the requirements. To do that the programmer can research about the types of
software that were made similar to the one given in task.
,Grade: Distinction
In my case, I have been provided with a set of requirements listed below that my program must
fulfil. The fact that I have been given those requirements means that I can now use those
requirements as a benchmark of what the program that I will create must do, this will exactly allow
me to identify the progress that I’m making as well as make me aware if I am going in the right
direction.
• Design specification (STAGE 2)
This stage is mainly based on stage of the requirement. This is because in this stage the
programmer must think about the best way, to find a solution for a problem given that meets the
requirements. This includes the layout of the program such as the GUI, all the inputs and outputs
required to make this solution successful, the timescale required to make the solution and the
extent to which will the program will meet client requirements.
In my case, I will be thinking about the best way to structure the program not only the code,
however I will be thinking on how to make the GUI as efficient as possible. I am going to be thinking
about the information that will need to be inputted such as the Employee name and number of
hours worked as well as the outputs required such as total pay. Finally, I will need to think on how
to make my solution meet all the client requirements such as being compliant with the GDPR. I also
intend on creating a test plan, that will cover the requirements and ensure the final software meets
its purpose and functionality. I will also be making a flowchart to illustrate how the program will
work.
• Develop code (STAGE 3)
In this stage, the program is developed. This means that any initial algorithms and pseudo codes are
written. When developing a solution, it is crucial that the programmer chooses the language that is
the mostly suited for solving the problem given. It is important to keep the program organized and
well commented to ensure, any adjustments and further continuation can be made with ease.
In my case, I have decided to make the program in VBA this is due to the flexibility and the
suitability of the language as it allows for the use of GUI’s as well as coding. This should make the
whole user experience better and easier therefore it’s the most suitable language for the task. I will
also be keeping my code neat through the paradigm used by the language. When suitable I will
write pseudo code to fit the flow chart I have created in stage 2 about the functionality of the
program. I will be thinking about the structure of the program.
• Implementation and Coding Phase (STAGE 4)
In this stage, this is where the programmers need to think about the paradigms they are using and
take all the designs of pseudo-codes, flowcharts and algorithms and make the functional product in
actual life. This is an important stage, because this is where everything comes together, with the
focus on the program. This stage tends to be the longest stage in the entire cycle.
In my case, I will be using an Object orientated paradigm and I will take all the designs I have made
from stage 3 and transfer them into code to create a fully functional software that meets the
requirements ready to be tested within the next phase of the cycle. I will be aiming to make the
solution as robust as possible.
, Grade: Distinction
• Testing (STAGE 5)
In this stage the software made, is tested for functionality against the original client requirements.
This should verify that all the features are working correctly and should identify some possible
improvements that can be made to improve the programs robustness to make it more optimized.
I my case, I intend on using a test plan from stage 2 to focus the software’s functionality as well as
the user requirements given in the requirements stage. I will also be modifying the test plan created
to ensure its suitability in regard to the software while trying to focus on ensuring there are no
internal errors and bugs that may affect the users experience. I intend on clarifying that the
program works as intended as well as meets all the requirements mentioned. Dependent on the
results of the test plan I will be trying to make refinements in the software to improve its
robustness as well as efficiency.
• Deployment (This stage is optional dependent on the type of software being developed and
methodology used)
This stage is where the improved and tested version of the program is released, and has started
being used by the company. This stage replaces the old software with the new one ensuring that
the new software meets the requirements
In my case, I will not be replacing any software as this is the initial release as there has not been any
software used prior to this one.
• Maintenance / Evolution (STAGE 6)
Maintenance is after the software has been implemented, the software will constantly be
monitored for any errors, if found this stage is there in place to ensure that those errors/bugs get
fixed. In addition, this stage allows for modification of the software to increase the functionality and
meet any additional needs, if software is found to be incapable to be modified the cycle starts again
to create a software that will meet the requirements.
In my case, I will not be there to maintain the software and add any improvements after the release
however I will try to make the program as optimized as possible (I will be using the testing phase to
find any possible areas of improvements), and I will leave suitable code comments to ensure
anyone else in the future can modify and maintain the software if required.
Introduction
As a junior software developer for a games company, the department of finance have assigned a task for
me to develop a basic payroll system that calculates the weekly wages for the employees. I have been
given requirements which I must work with. These requirements are:
• Pay Rates must be introduced as a list
• An employee must work 35 basic hours before overtime can be added
• Access to overtime must be restricted but not password restricted
• Overtime hours are paid double
• The program should alert its users when 20 hours of overtime have been reached but this
should not stop the calculations
