SOFTWARE REQUIREMENTS
Software Engineering
___
Notes
According to IEEE, a requirement is:
1. A prerequisite or capacity that a user needs in order to resolve an issue or
accomplish a goal
2. A requirement that a system or a system component must meet in order to comply
with a formal document, standard, specification, or contract.
3. A recorded depiction of an attribute or capacity as in 1or 2
Software prerequisites
● includes both the developer's perspective (internal characteristics) and the user's
perspective (outside view) of the requirements.
User's specifications
- Natural language statements and a graphic outlining the expected functions and
limitations of the system
● System Requirements: Describe the services, functionality, and state of operation
of the system.
Software prerequisites
● Functional Requirements for the System
- A list of the services that the system ought to offer
- Explain the actions in specific contexts. Describes how the system responds to
specific inputs.
● Non-functional Conditions
- Limitations on the features or services the system provides Apply to the entire
system. Incorporate standards, time restrictions, and development process
constraints.
● Domain Conditions
- Requirements pertain to a particular system application
- Reflect the limitations and features of that system.
The functional prerequisites
●It need to be thorough and reliable.
● Wholeness
- Every service that the user needs should be specified consistently.
- Requirements shouldn't be defined in conflict with one another.
-For a large system, achieving consistency and completeness is difficult.
DISTINCTIVE REQUIREMENTS
Different Kinds of Non-Functional Needs 1. Product Requirements
- Describe the behavior of the product.
-Contain the subsequent
- Efficiency
- Usability
-Dependability
- Mobility
2. Requirements for Organizations
- Original from guidelines and protocols
- Comprise the subsequent:
- Delivery
- Execution
- Normal
3. External Conditions
- resulting from elements outside of the system and the process of its creation
-Contains the subsequent
- Ethics of Interoperability
- Lawmaking
DIFFICULTIES IN USING NATURAL LANGUAGE
1. Lack of clarity: Due to the ambiguity of natural language, this might generate
misunderstandings.
2. Difficulty in determining if requirements are the same or different: Overly flexible
requirements might cause confusion at times.
3. The amalgamation problem: It is challenging to modularize the needs for natural
language
LANGUAGE STRUCTURE DESCRIPTION
●The format of requirements is standard.
● guarantees a level of consistency
● Give templates for describing the specifications of the system.
● To divide the specification, use graphical highlighting and control constructs.
SYSTEM DEMANDS COMMON FORM
● Function
● Specifications
● Source
●Inputs
●Outputs
● Location
● Action
● Prior to Arrival
●Following condition
● Adverse consequences
Interface Definition.
●The new system's operation must align with that of the current system.
● Interface offers this functionality and is very specific.
There are three kinds of interfaces.
1. Procedural interface:
-This allows new applications to call older ones.
2. Structures for data
-Offer data transmission across subsystems
3. Data Representations
- Bit ordering to conform to the current scheme
- Most prevalent in embedded systems and real-time
The requirements document for software
The formal declaration of what is expected of the system developers is found in the
requirements document. ought to have a description of the system needs as well as a
definition of the user requirements. This document is NOT a design. Whenever feasible,
the focus should be on WHATthe system should accomplish rather than HOW it should
accomplish it.
The requirements document for software suggests that the requirement document
should meet the following six requirements.
●It ought to solely describe the behavior of the external system.
● Indicate the limitations of the execution.
● Be adaptable.
● act as a resource for system administrators
●Note consideration for the system's life cycle.
● Describe appropriate reactions to undesirable occurrences.
Why SRS Is Used ?
● Interactions between analysts, system developers, maintainers, and customers
solid
● base for the stage of design assist with system testing operations
● Encourage project oversight and management
● regulating the system's evolution
IEEE requirements standard
outlines a general format for a requirements document that needs to be implemented for
every unique framework.
- Overview.
- Overview of the situation.
- particular specifications.
- Addenda.
-Index
IEEE requirements standard
1.
● Overview
● Definitions, Synonyms, and Abbreviations;
● Objective
● Overview
●Citations
2.
● Synopsis From a product standpoint
● Summary of the product's function
● user attributes
● general limitations
● Dependencies and presumptions
3.
● Particular Conditions
- Functional specifications
● Requirements for external interfaces
- Performance standards
- Design limitations Features such as availability, maintainability, security, and
transferability/conversion
- Additional prerequisites
- Addenda
-Index
