IEEE Recommended Practice for Software Requirements SpeciÞcations

@inproceedings{Tripp1993IEEERP,
  title={IEEE Recommended Practice for Software Requirements SpeciÞcations},
  author={L. Tripp and E. Byrne and Paul R. Croll and P. Deweese and Robin Fralick and Marilyn Ginsberg-Finner and J. Harauz and M. Henley and Dennis Lawrence and D. Maibor and Ray Milovanovic and J. Moore and Timothy Niesen and D. Rilling and T. Rout and R. Schmidt and N. Schneidewind and D. Schultz and B. Sherlund and P. Voldner and R. Wade and S. Ali and T. K. Atchinson and M. Auguston and R. Barry and L. Beltracchi and H. R. Berlack and Richard E. Biehl and M. A. Blackledge and S. Bologna and J. Borzovs and Kathleen L Briggs and M. Scott and Buck Michael Caldwell and J. E. Cardow and E. A. Carrara and L. Catchpole and K. Chan and Antonio Cicu and T. Clarke and S. Clermont and R. Coleman and V. Lee and Cooper W W Geoff Cozens and G. T. Daich and G. Darnton and T. Daughtrey and Bostjan K Derganc and J. Do and Evelyn S Dow and Carl Einar Dragstedt and S. Eagles and C. Ebert and Leo Egan and R. Fairley and J. Fendrich and J. Forster and K. Fortenberry and E. Freund and R. Fries and R. Fujii and Adel N Ghannam and G. John and J. Glynn and L. Gonzalez-Sanz and David A Gunther and J. Gustafson and J. Hagar and Robert T Harauz and H. Harley and William J. Hecht and Manfred He{\ss}ey and M. Hein and M. Heinrich and D. Henley and J. Herrmann and Jerry Horch and Peter L Huller and G. Hung and Frank V Jackelen and William S Jorgensen and G. Junk and R. Kambic and Ron S Karcich and Judith S Kenett and Robert J. Kerner and Dwayne L Kierzyk and Shaye Knirk and Thomas M. Koenig and John B Kurihara and J. Lane and L. Dennis and C. Fang and W. M. Lim and James J Lively and Dieter Longbucco and John Look and S. Lord and D. Magee and Harold Maibor and Robert A Mains and T. Martin and Mike Matsubara and P. McAndrew and C. Mccray and Jerome W Mcmacken and Bret Mersky and A. Michael and Celia Miller and James W Modell and P. Moore and Myrna L Navrat and Indradeb P Olson and A. Pal and Peter T Polack and L. S. Poon and Kenneth R Przybylski and Annette D Ptack and D. Reilly and Andrew P Rilling and Helmut Sage and Stephen R Sandmayr and H. Schach and N. Schaefer and David J Schneidewind and L. Schultz and Robert W Selmon and David M Shillato and Carl A Siefert and James M Singer and Richard S Sivak and Nancy M Sky and M. Smith and Harry M Smyre and Alfred R Sneed and Donald W Sorkowitz and L. Sova and Julia Spotorno and Fred J Stesney and Christine Strauss and S. Brown and T. Toru and H. Richard and B. Thayer and P. Thomas and Theodore J Trellue and Glenn D Urbanowicz and Udo Venables and David D Voges and D. Walden and W. Wallace and J. Walsh and Camille Walz and Scott A Swhite-Partain and P. Whitmire and P. Wolfgang and Natalie C Work and Janusz Yopconka and Geraldine Zalewski and P. F. Zimmerman and Zoll and Richard J Holleman and D. Heirman and V. Chair and J. Gorman and Member Emeritus and Valerie E Zelenty and S. Aggarwal and C. R. Camp and James T. Carlo and Gary R Engmann and H. E. Epstein and T. Garrity and R. D. Garz{\'o}n and J. Gurney and Jim Isaak and L. G. Johnson and Robert A. Kennelly and E. Kiener and Joseph L Koepþnger and S. R. Lambert and J. Logothetis and Donald C. Loughry and L. B. Mcclung and R. C. Petersen and G. H. Peterson and J. Posey and G. Robinson and H. Weinrich and D. Zipse},
  year={1993}
}
  • L. Tripp, E. Byrne, +188 authors D. Zipse
  • Published 1993
  • The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/EIA 12207.1-1997 are also provided. 
    On Non-Functional Requirements
    • 592
    • Highly Influenced
    • Open Access
    Improving the Quality of Requirements with Scenarios
    • 67
    • Open Access
    Model-Driven User Requirements Specification using SysML
    • 79
    • Open Access
    User’s manual as a requirements specification: case studies
    • 18
    • Open Access
    Verifying software requirements with XSLT
    • 13
    • Open Access
    A framework to measure and improve the quality of textual requirements
    • 101
    • Open Access

    References

    Publications referenced by this paper.
    SHOWING 1-6 OF 6 REFERENCES
    1 Compliance with information requirements of IEEE/EIA 12207
      2 discusses compliance with the generic content guideline (the ÒkindÓ of document) noted in column 3 of Table B.1 as a ÒdescriptionÓ. The generic content guidelines for a ÒdescriptionÓ appear in 5
        3 discusses compliance with the speciÞc requirements for a Software Requirements Description noted in column 4 of Table B.1 as prescribed by 6
          4 discusses compliance with the life cycle data objectives of Annex H of IEEE/EIA 12207.0- 1996 as described in 4.2 of IEEE/EIA 12207
            B.3.2 Compliance with generic content guidelines of IEEE/EIA 12207
              Copyright © 1998 IEEE. All rights reserved