SDLC – Software Development Life Cycle
In view of the recent but not over yet Hall-Of-Fame event, it is with great surprise that despite this event has been broadcasted for nearly a month (from start till end of event), it is still able to mess up and still unable to pull off a smooth execution.
Therefore it leads to my thinking that whichever company or group of people that are incharge of implementing such a program / event, has to be really made aware of or be taught of SDLC. You guys are, after all a software company, having software needed to be developed and implemented.
So let’s begin.
As the title already suggested – SDLC stands for software development life cycle. It is a process that a good software development company or group of people adopts so to ensure whatever it is that you’re trying to implement, comes out being implemented correctly, and most of all bug free.
There are a number of SDLC models available that are widely adopted as well, let’s choose a simple one – The Waterfall model.
In the Waterfall model, you do your software thing following these phases:
1. Requirement gathering
2. Design
3. Implementation / Construction
4. Verification / Testing
5. Maintenance (might not be applicable in the case of HoF event).
Requirement Gathering
You gather your requirements. In this case of HoF, is to reward players whom BR at the end of the event (27/Nov) having 250k / 300k / 350k / 400k / 450k accordingly on the various items depending on which tier they stand, along with the lower tiers etc etc etc. This I “think†you guys might already have, else the HoF won’t even be here. So kudos – you have your requirements defined (sort of).
Design
You design your programs (note: design only, no coding yet). This is the time you think through on how you want to implement this requirement that you’ve defined above. When will you do it, at which juncture, and how many processes involved etc etc etc. Failing in this, you will fail the following section, and as a whole failing the meet the requirement. If you’re doing this correctly, you would’ve stuff like flow-charts, pseudo codes, process-flows etc etc in place to supplement the design.
Implementation / Construction
This is the time you do your coding. The coding is based on the “Design†that you’ve defined earlier which is of course having the objective to meet the requirements. People who do stuff in this phase, usually should not be the same people who do the design, and neither do they need to understand the design. Just code based on the given blueprints.
Verifications / Testing
This is the interesting part. It is the mother of all cupcakes if you don’t do it. Whatever it is that you’ve designed and coded in hope to achieve the requirement, MUST be verified whether or not it works in this phase. You short-cut this one, you end up with cupcakes. This is guaranteed.
You must only deploy stuff into a live environment once the software that you’ve made passed through this stage and gives an accurate result / outcome. If this one fails due to whatsoever reason, trace back to the stage above this one, and review it again all the way from coding then onto design once more if need be.
So finally – once you gone through the 4 stages above, and assuming all 4 stages are completed to satisfactory result, you put it to live environment. When the time comes, just push the button and voila – event completed, everyone’s happy, no surprises.
I don’t know which stage did you not do, or rather if you have any of such practice at all.
I took 25 mins to type out all the above in a Microsoft Word document, and pasted it into the forum.
At best, I think if you have someone doing this for you in your organization, it will probably that a week to iron through the requirements to design. Coding 2 weeks. Testing 1 week. Done. After all the requirement is not THAT complicated IMO.
So the next time when you wanna implement some event of such, please, for the sake of your mods / GMs / ticketing system and most of all your entire player community – do try to follow the SDLC. It saves life.
And yep, I have some free time today to type all these out. Thank you for reading.
In view of the recent but not over yet Hall-Of-Fame event, it is with great surprise that despite this event has been broadcasted for nearly a month (from start till end of event), it is still able to mess up and still unable to pull off a smooth execution.
Therefore it leads to my thinking that whichever company or group of people that are incharge of implementing such a program / event, has to be really made aware of or be taught of SDLC. You guys are, after all a software company, having software needed to be developed and implemented.
So let’s begin.
As the title already suggested – SDLC stands for software development life cycle. It is a process that a good software development company or group of people adopts so to ensure whatever it is that you’re trying to implement, comes out being implemented correctly, and most of all bug free.
There are a number of SDLC models available that are widely adopted as well, let’s choose a simple one – The Waterfall model.
In the Waterfall model, you do your software thing following these phases:
1. Requirement gathering
2. Design
3. Implementation / Construction
4. Verification / Testing
5. Maintenance (might not be applicable in the case of HoF event).
Requirement Gathering
You gather your requirements. In this case of HoF, is to reward players whom BR at the end of the event (27/Nov) having 250k / 300k / 350k / 400k / 450k accordingly on the various items depending on which tier they stand, along with the lower tiers etc etc etc. This I “think†you guys might already have, else the HoF won’t even be here. So kudos – you have your requirements defined (sort of).
Design
You design your programs (note: design only, no coding yet). This is the time you think through on how you want to implement this requirement that you’ve defined above. When will you do it, at which juncture, and how many processes involved etc etc etc. Failing in this, you will fail the following section, and as a whole failing the meet the requirement. If you’re doing this correctly, you would’ve stuff like flow-charts, pseudo codes, process-flows etc etc in place to supplement the design.
Implementation / Construction
This is the time you do your coding. The coding is based on the “Design†that you’ve defined earlier which is of course having the objective to meet the requirements. People who do stuff in this phase, usually should not be the same people who do the design, and neither do they need to understand the design. Just code based on the given blueprints.
Verifications / Testing
This is the interesting part. It is the mother of all cupcakes if you don’t do it. Whatever it is that you’ve designed and coded in hope to achieve the requirement, MUST be verified whether or not it works in this phase. You short-cut this one, you end up with cupcakes. This is guaranteed.
You must only deploy stuff into a live environment once the software that you’ve made passed through this stage and gives an accurate result / outcome. If this one fails due to whatsoever reason, trace back to the stage above this one, and review it again all the way from coding then onto design once more if need be.
So finally – once you gone through the 4 stages above, and assuming all 4 stages are completed to satisfactory result, you put it to live environment. When the time comes, just push the button and voila – event completed, everyone’s happy, no surprises.
I don’t know which stage did you not do, or rather if you have any of such practice at all.
I took 25 mins to type out all the above in a Microsoft Word document, and pasted it into the forum.
At best, I think if you have someone doing this for you in your organization, it will probably that a week to iron through the requirements to design. Coding 2 weeks. Testing 1 week. Done. After all the requirement is not THAT complicated IMO.
So the next time when you wanna implement some event of such, please, for the sake of your mods / GMs / ticketing system and most of all your entire player community – do try to follow the SDLC. It saves life.
And yep, I have some free time today to type all these out. Thank you for reading.
Comment