Requirement Gathering & Analysis Phase in SDLC

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: Design 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:02 Requirements Gathering
  • 0:29 Analyzing Requirements
  • 2:39 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.

When a company needs a new software program, they have some idea of what they want the new program to do. This lesson describes the purpose and importance of the gathering and analyzing requirements in the software development lifecycle.

Requirements Gathering

SDLC is an acronym for software development lifecycle and is the process used as the framework for software development. Project managers and business organizations use the SDLC as a blueprint for completing each step of the lifecycle for software development. Each step of the SDLC is called a phase. The requirements gathering and analysis phase is the first phase of the SDLC.

Analyzing Requirements

Gathering requirements for the project is the most important part of the SDLC for project managers and internal stakeholders of a project. During this phase, the customer states the expectations of the project including who will use the product, how the customer will use the product, and the specific information included with any special customer requirements related to the software. The customer meets with business managers and analysts to provide the requirements. It's important for the project team to understand the needs of the customer because this information is critical to developing the product the customer requests.

After the customer provides requirements for the product, the project manager and members of the project team begin to analyze the requirements. The business managers analyze each requirement to ensure the requirement can be included in the software without causing breaks or problems with system functionality.

For example, Lane wants to develop a software application that will help users find inventory in retail stores faster. To start this process, Lane provides a list of customer requirements to his project manager:

  • First, the software must include all inventory in each retail store
  • Next, each retail store has the same inventory part numbers
  • Next, there are five stores in three states
  • Lastly, the application must be able to provide accurate inventory availability within 60 seconds of performing the search

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