There are two possible answers to this. The first could be requirements analysis, because the requirement analyst needs to know what the end user needs the software to do. Without the end user, the requirement analyst would need to guess at the requirements.
The other could be testing. Without the end user testing the software, he/she/they will have no idea if the software works until he/she/they put it in a production environment.
Requirements analysis phase
for gathering data and information.
time consuming, cost increasing,large number of information nessary to collected
The various phases are as follows : 1) Feasibility study 2) Requirement analysis and specification 3) Design 4) Coding and unit testing 5) Integration and system testing 6) Maintenance
There are number of SDLC models in software engineering. Using life cycle model we can divide the work in different phases thus making it easy and convenient .
Requirements analysis phase
analyze phase
for gathering data and information.
Actually - all phases of SDLC can be a source for Errors. The later in the life cycle an error is detected, the costlier it will be to fix it
defects
A signed-off, up and working application system.
False5) Testing and Installation: The next step in the SDLC is testing the program to ensure that it works properly and then installing the program so that it can be used.
what are the phases of the sdlc
During the DESIGN PHASE of the SDLC or "System Development Life Cycle" is where a detailed plan for programmers to follow is developed.
PlanningThe Planning Phase is the first phase of the SDLC. During this phase, the group that is responsible for creating the system must first determine what the system needs to do for the organization. Often this means asking questions such as...What do we need this system for?What will the system do for the organization?How are we going to make this system?During this initial phase, resources (both human and technology resources) are put together and a project plan is devised by the project manager.AnalysisThe Analysis Phase is the second phase of the SDLC and is when the group that has been placed in charge of the project must decide if the project should go ahead with the resources available. This also includes looking at any existing system to see what it is doing for the organization and how well that system is doing it's job. The feasibility of the project is also considered, and the group has to ask questions such as...Can this system be created with the resources (and budget) we have available?Will this system significantly improve the organization?Does the old system even need to be replaced?DesignThe Design Phase is the third phase of the SDLC and it involves the actual creation and design of a system. This involves putting together the different pieces that will create the system. In a database approach, this would include...The server hosting the databaseThe software that will form the database (Access, Oracle, mySQL, etc)Other needed DBMS (DataBase Management System) softwareImplementationThe Implementation Phase is the final phase of the SDLC and it involves the actual construction and installation of a system. This phase also includes the maintenance of the system and any future updates or expansion of the system.
The deliverables in the requirement gathering and analysis phase of the SDLC typically include a requirements document outlining business needs, functional requirements, non-functional requirements, and system constraints. Other deliverables may include use cases, user stories, workflow diagrams, personas, and a requirements traceability matrix to ensure alignment with project goals.
SDLC has both verification and validation activities where as STLC has only validation activity. Simply STLC is a part of SDLC