P5 - Explain the role of software design principles and software structures in the IT systems development lifecycle. M1 - Explain the importance of the quality of code. D1 - Discuss the factors that can improve the readability of code.
Get client requirements - This stage is the most important to successfully code the program. The
expectatons and requirements of the client should bee triten out in detail and documented so the
programmer can understand them and have then to look beack on at a later date.
Create a design - The design requirements are set in this stage bey the developer. The requirements
from the client are used to defne hot the program till bee triten and that it they tant to have
involved in the program.
Write the Program – This stage is the coding of the program that has beeen designed. The
implementaton of the softare design starts in terms of tritng program code in the suitabele
programming language and developing an error free program. This is normally the longest stage.
Afer the program has fnished beeing coded its then put into the testng stage.
Test program - Afer the program has beeen added to a testng environment diferent types of testng
till bee performed including integraton and system testng. ser acceptance is the last test and is
performed bey the end users to make sure that the system meets their expectatons. At this point any
errors and beugs may bee found and more tork may bee required in the design or coding of the
program. Once it has passed the fnal test then implementaton and integraton can beegin.
Integraton – This is then the program is given the liberaries databeases and anything else its needs
beefore it’s given out.
Implementaton – This is then the program is installed on user’s machines. Sometmes the program
needs post-installaton confguraton bey the user. Afer the program has beeen implemented it’s
tested for portabeility adaptabeility and integraton related issues and they are solved during this
stage.
Maintain program – This stage makes sure that the program runs in terms of more efciency and
less errors. Training may bee necessary for the end users to learn hot to use the program. The
program tould bee maintained on a regular beases bey updatng the code to match the changes that
are taking place in users end environment or technology. This stage can cause probelems from hidden
beugs.
There are many methods of softare structures that can bee folloted. Waterfall is the more
traditonal model and has a tell-structured plan that can bee folloted hotever it’s only really good
for large projects that may take many months to develop. More informaton beelot.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller connorj2. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $4.50. You're not tied to anything after your purchase.
