Implementation & Coding Phase in SDLC

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: Testing Phase in SDLC

You're on a roll. Keep up the good work!

Take Quiz Watch Next Lesson
Your next lesson will play in 10 seconds
  • 0:03 The SDLC
  • 0:48 Implementation
  • 1:26 Coding
  • 2:19 Lesson Summary
Save Save Save

Want to watch this again later?

Log in or sign up to add this lesson to a Custom Course.

Log in or Sign up

Speed Speed

Recommended Lessons and Courses for You

Lesson Transcript
Instructor: Noel Ransom

Noel has taught college Accounting and a host of other related topics and has a dual Master's Degree in Accounting/Finance. She is currently working on her Doctoral Degree.

This lesson defines and explains the use of the implementation and coding phase of the software development life cycle. The lesson also provides a brief explanation of the documentation used within this phase.


Most companies that design and develop software use some form of the software development life cycle (SDLC) to plan for, create, and release their products. The implementation and coding phase of the software development life cycle is the third phase of the SDLC process. The first phase of the SDLC is the requirements gathering and analysis phase, which is when the project team and business managers gather the wants and needs of the customer. After the project team obtains the customer's requirements for the project, the second phase of the SDLC starts, which is when the team designs the software. The project team then uses the design to begin the implementation and coding phase.


During implementation, the project team creates the actual product. Product implementation can be an exciting phase for the customer, because their idea for the project becomes something tangible. Project developers begin building and coding the software.

For example, if a customer wants a new gaming application, the project developers must program the application to perform the customer's gaming requirements. As the team develops the code, the team must follow specific coding requirements. Customer requirements may call for specific computer programming languages or upgrades, and developers need to run the applications to ensure they function properly.


If the software application is designed properly and requirements are gathered accurately, the coding process is more streamlined. Project teams are better able to meet software coding deadlines when the correct information is gathered upfront from the customer.

For example, Sandy is a developer for a software company with a new project to develop code for a customer. Before Sandy can develop code, she needs to understand what the customer wants. She can learn this by requesting a requirements specification document with the customer's details for the project. She also needs the design documents to ensure the product design will handle the specific coding requirements.

To unlock this lesson you must be a Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use

Become a member and start learning now.
Become a Member  Back
What teachers are saying about
Try it risk-free for 30 days

Earning College Credit

Did you know… We have over 200 college courses that prepare you to earn credit by exam that is accepted by over 1,500 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.

To learn more, visit our Earning Credit Page

Transferring credit to the school of your choice

Not sure what college you want to attend yet? has thousands of articles about every imaginable degree, area of study and career path that can help you find the school that's right for you.

Create an account to start this course today
Try it risk-free for 30 days!
Create an account