Software Requirements Specifications

A How To Guide for Project Staff

Author: David Tuffley
Length: 92 page(s)
Written: Apr 2011
Sales Rank: -
Views: 544

Software Requirements Specifications: A Guide for Project Staff outlines how project staff can develop requirements list (RL), statement of user requirements (SUR) and software requirements specification (SRS).

The end product of the requirements capture process is the complete and accurate definition of the functionality of the proposed system. It is a 'top down' process which proceeds from the general to the specific through a series of predefined steps.

This book gives a detailed outline of the requirements capture process. It discusses how to apply the steps contained in the requirements capture standards.

Developing Software Requirements Specifications: A Guide for Project Staff outlines how project staff can develop:

• Requirements Lists(RL),
• Statement of User Requirements (SUR) and
• Software Requirements Specifications (SRS).

The end product of the requirements capture process is the complete and accurate definition of the functionality of the proposed system. It is a 'top down' process which proceeds from the general to the specific through a series of predefined steps.

This book gives a detailed outline of the requirements capture process. It discusses how to apply the steps contained in the requirements capture standards (IEEE Std 830 Guide to Software Requirements Specifications, IEEE Std P1233 Guide for Developing System Requirements Specification).

How this book is organised:

Part A: Introduction
Part B: Requirements List (RL)
Part C: Statement of User Requirements (SUR)
Part D: Software Requirements Specification (SRS)
Part E: References

The nature of requirements capture

Developing a comprehensive understanding of user requirements is one of the most problematic aspects of the entire software development process.

High quality software can only be developed based on such an understanding, and this calls for close cooperation and understanding between users and developers, particularly during the requirements gathering and analysis stage. The challenge for any developer is to recognize the interdependency of the stakeholders and to work towards creating the conditions in which the sub-systems work harmoniously with each other.

Software developers by nature have a technological mindset. Years of technical education and on-the-job training which develops their technical skills to a higher standard? The pursuit of technical excellence is a matter of professional pride, as it should be. Conversely though many if not most software users have a non-technical or limited technical view of the world. Their interaction with software is a means to an end, not an end in itself.

Bringing users and developers into closer cooperation through improved mutual understanding is in the best traditions of Socio-Technical Design. There should be substantial user involvement in the system design process. In this book, systems are defined broadly. A system can be comprised of networks of users, developers, information technology at hand, and the environments in which the system will be used and supported.

Achieving this closer cooperation and mutual understanding requires an understanding of the dynamics of the organisational culture in which systems development is performed.

About the Author

David Tuffley
Member since: Apr 2011
Publications on XinXii:  25

My social profiles on...

David Tuffley PhD is lecturer and researcher at Griffith University in Australia. David is a Software Engineer, though his interests range across Comparative Religion, Philosophy, Psychology, Anthropology, Literature, History, and Architecture.

David has been an academic since 1999. Before academia he was a consultant for public and private sector IT clients in Australia and the United Kingdom. He combines theory and practice in a focussed and disciplined way that has proved effective for solving problems for clients.

No review yet.