Software Requirements Engineering Second Edition: 44 (Practitioners) - Tapa blanda

Acerca del autor

Richard H. Thayer, PhD, is a Professor of Computer Science at California State University, Sacramento, California, United States of America. He travels widely where he consults and lectures on software requirements analysis, software engineering, project management, software engineering standards, and software quality assurance. He is a Visiting Researcher at the University of Strathclyde, Glasgow, Scotland. As an expert in software project management and requirements engineering, he is a consultant to many companies and government agencies.
Thayer is a Senior Member of the IEEE Computer Society and the IEEE Software Engineering Standards Subcommittee. He is Chairperson for the Working Group for a Standard for a Software Project Management Plans. He is a Distinguished Visitor for the IEEE Computer Society.
He is also an Associate Fellow of the American Institute of Aeronautics and Astronautics (AIAA) where he served on the AIAA Technical Committee on Computer Systems, and he is a member of the Association for Computing Machinery (ACM). He is also a registered professional engineer.
He has a BSEE and an MS degree from the University of Illinois at Urbana (1962) and a PhD from the University of California at Santa Barbara (1979) all in Electrical Engineering.
He has edited and/or co-edited numerous tutorials for the IEEE Computer Society Press: Software Engineering Project Management (1988), System and Software Requirements Engineering (1990), and Software Engineering--A European Prospective (1992). He is the author of over 40 technical papers and reports on software project management, software engineering, and software engineering standards and is an invited speaker at many national and international software engineering conferences and workshops.

Merlin Dorfman, PhD, is a Technical Consultant in the Space Systems Product Center, Lockheed Martin Missiles and Space Company, Sunnyvale, Calif. He specializes in systems engineering for software-intensive systems (requirements analysis, top-level architecture, and performance evaluation), in software process improvement, and in algorithm developments for data processing systems. He has performed concept exploration, system implementation, and operations and maintenance of data systems and has worked on proposal teams and company-funded technology projects as well as on development contracts. He was in charge of the development of the Automated Requirements Traceability System (ARTS). He was the first chairman of Space Systems Division's Software Engineering Process Group. He represented the Lockheed Corporation on the Embedded Computer Software Committee of the Aerospace Industries Association, and was Vice-Chairman of the Committee.
He has a BS and MS from the Massachusetts Institute of Technology and a PhD from Stanford University, all in Aeronautics and Astronautics. He is a registered Professional Engineer in the state of California and Colorado and is a member of the Tau Beta Pi and Sigma Gamma Tau honorary societies.

De la contraportada

This new edition describes current best practices in requirements engineering with a focus primarily on software systems but also on systems that may contain other elements such as hardware or people. The text consists of original papers, written by experts in the fields, plus reprints of survey articles on many aspects of requirements engineering. The book begins with an introduction to current issues and the basic terminology of the software requirements engineering process. In addition, the text covers the five basic phases of software requirements engineering: elicitation, analysis, specification, verification, and management. The book:

• Looks at the science and discipline of establishing and documenting software requirements
• Describes the process through which developers' and users' discover, review, articulate, and understand the users' needs and the constraints on the software and development
• Shows how to analyzes the users' needs to arrive at a definition of their software requirements
• Examines software requirements and the need to clearly document and precisely record each requirement
• Looks at verification to ensure that the software requirements specifications are in compliance with the system requirements and conform to document standards
• Details software requirements management including planning and controlling of all these activities.