Author Archives: M. Noman

Explain The Requirements Validation Process

Explain The Requirements Validation Process Requirements validation is concerned with showing that the requirements actually define the system that the customer wants. Requirements validation overlap analysis in that it is concerned with finding problems with the requirements. Requirements validation is important because errors in a requirements document can lead to extensive rework costs when they are… Read More »

What is Ethnography

What is Ethnography Software systems do not exist in isolation-they are used in a social and organizational context, and software system requirements may be derived or constrained by that context. Satisfying these social and organizational requirements is often critical for the success of the system. One reason why many software systems are delivered but never… Read More »

What Are Use-cases?

What Are Use-cases? Use-cases are a scenario-based technique for requirements elicitation which was first introduced in the Objective method (Jacobsen, et al., 1993). They have now become a fundamental feature of the UML notation for describing object-oriented system models. In their simplest form, a use-case identifies the type of interaction and the actors involved. For… Read More »

Explain The Requirements Discovery Process

Explain The Requirements Discovery Process Requirements discovery is the process of gathering information about the proposed and existing systems and distilling the user and system requirements from this information. Sources of information during the requirements discovery phase include documentation, system stakeholders, and specifications of similar systems. You interact with stakeholders through interviews and observation and… Read More »

What Is the Feasibility Study

What Is the Feasibility Study For all new systems, the requirements engineering process should start with a feasibility study. The input to the feasibility study is a set of preliminary business requirements, an outline description of the system, and how the system is intended to support business processes. The results of the feasibility study should… Read More »

Requirements, Elicitation And Analysis

 Requirements, Elicitation And Analysis The next stage of the requirements engineering process is the requirements elicitation and analysis. In this activity, software engineers work with customers and system end-users to find out about the application domain, what services the system should provide, the required performançe of the system, hardware constraints, and so on Requirements elicitation… Read More »

Requirements Engineering Process

Requirements Engineering Process The goal of the requirements engineering process is to create and maintain a system requirements document. The overall process includes four high-level requirements engineering sub-processes. These are concerned with assessing whether the system is useful to the business (feasibility study); discovering requirements (elicitation and analysis); converting these requirements into some standard form… Read More »

System Requirements

System Requirements System requirements are expanded versions of the user requirements that are used by software engineers as the starting point for the system design. They add detail and explain how the user requirements should be provided by the system. They may be used as part of the contract for the implementation of the system… Read More »

User Requirements

 User Requirements The user requirements for a system should describe the functional and non-functional requirements so that they are understandable by system users without detailed technical knowledge. They should only specify the external behavior of the system and should avoid, as far as possible, system design characteristics Consequently, if you are writing user requirements, you… Read More »

Domain Requirements.

Domain Requirements Domain requirements are derived from the application of the system rather than from the specific needs of system users. They usually include specialized domain terminology or reference to domain concepts.  Equation: They may be new functional requirements in their own right, constrain existing functional requirements, or set out how particular computations must be… Read More »