This phase in the systems life cycle is concerned about determining system requirements not in design.

The phase in the system life cycle that is concerned with determining system requirements, not design, is the Analysis phase. Here are the steps:

1. Identify the Problem: The first step in the analysis phase is to identify and understand the problem that the system is supposed to solve. This involves meeting with the various stakeholders to discuss what the issues are and what the new system is expected to achieve.

2. Gather Information: The next step is to gather detailed information about the problem and the current system (if there is one). This could involve reviewing existing documentation, observing the current system in operation, and interviewing people who use or will use the system.

3. Define System Requirements: Based on the information gathered, the next step is to define the system requirements. These are detailed descriptions of what the system must do to solve the problem. They are usually divided into functional requirements (what the system must do) and non-functional requirements (how the system should perform).

4. Prioritize Requirements: Since it may not be possible to meet all the requirements due to constraints such as time and cost, the next step is to prioritize the requirements. This involves deciding which requirements are most important and must be included in the system, and which ones can be left out if necessary.

5. Document Requirements: The final step in the analysis phase is to document the requirements in a formal Requirements Specification document. This document serves as a contract between the stakeholders and the developers, specifying what the system will do.