Transcription of IEEE Recommended Practice for Software Requirements ...
{{id}} {{{paragraph}}}
Example: quiz answers
IEEE Recommended Practice for Software Requirements ...
IEEE Std 830-1998 (Revision ofIEEE Std 830-1993) IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications IEEE Computer Society Sponsored by the Software Engineering Standards Committee 20 October 1998SH94654 Authorized licensed use limited to: Michigan State University. Downloaded on February 23,2010 at 09:32:48 EST from IEEE Xplore. Restrictions apply. The Institute of Electrical and Electronics Engineers, East 47th Street, New York, NY 10017-2394, USAC opyright 1998 by the Institute of Electrical and Electronics Engineers, rights reserved. Published 1998. Printed in the United States of 0-7381-0332-2No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the Std 830 -1998(R2009)(Revision ofIEEE Std 830-1993)IEEE Recommended Practice for Software Requirements SpecificationsSponsorSoftware Engineering Standards Committeeof theIEEE Computer SocietyReaffirmed 9 December 2009 Approved 25 June 1998 IEEE-SA Standards BoardAbstract: The content and qualities of a good Software Requirements specification (SRS) are de-scribed and several sample SRS outlines
meet the requirements of IEEE/EIA 12207.1-1997, IEEE/EIA GuideÑIndustry Implementation of ISO/IEC 12207: 1995, Standard for Information TechnologyÑSoftware life cycle processesÑLife cycle data. Authorized licensed use limited to: Michigan State University.
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: