Category Archives: Software requirements

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 »

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 »

Non-functional requirements

 Non-functional requirements Non-functional requirements, as the name suggests, are requirements that are not directly concerned with the specific functions delivered by the system. They may relate to emergent system properties such as reliability, response time, and store occupancy. Alternatively, they may define constraints on the system such as the capabilities of VO devices and the… Read More »