Ieee recommended practice for software requirements specification

Results Citations. Citation Type. Has PDF. Publication Type. More Filters. The proposal of functional user requirements generation. View 2 excerpts, cites background. Verifying software requirements with XSLT. Requirements Engineering. View 1 excerpt, cites background.

The increasing complexity of software systems makes Requirements Engineering activities both more important and more difficult. This article is about user requirements development, mainly the … Expand. Evaluating software specifications by comparison. Eliciting required characteristics for usable requirements engineering approaches. SAC ' View 1 excerpt, cites methods. All rights reserved. It describes the content and qualities of a good software requirements specification SRS and presents several sample SRS outlines.

However, application to already-developed software could be counterproductive. When software is embedded in some larger system, such as medical equipment, then issues beyond those identified in this standard may have to be addressed.

This recommended practice describes the process of creating a product and the content of the product. The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard. This recommended practice does not identify any specific method, nomenclature, or tool for preparing an SRS. Christy Bahn. The necessary information content and recommended organization for a software design description are specified.

A software design description is a representation of a software system that is used as a medium for communicating software design information. The recommendations, which may be applied to commercial, scientific, or military software that runs on any digital computer, are not limited to specific methodologies for design, configuration management, or quality assurance, or to any particular descriptive technique.

Applicability is not restricted by the size, complexity, or criticality of the software. IEEE Withdrawn Standard. Withdrawn Date: Mar 06, No longer endorsed by the IEEE. The application of design methods and design documentation recommended in IEEE Std is described.