Soren Lauesen:Softwareanforderungen: Stile & Techniken von Soren Lauesen (englisch) Taschenbuch
- pocketboek ISBN: 9780201745702
By Soren Lauesen. What are the highlights?. Who is it for?. Who is the author?. Soren Lauesen is currently professor at the IT-University of Copenhagen. Author Soren Lauesen. The book ill… Meer...
By Soren Lauesen. What are the highlights?. Who is it for?. Who is the author?. Soren Lauesen is currently professor at the IT-University of Copenhagen. Author Soren Lauesen. The book illustrates everything through real-life examples. The Nile on eBay FREE SHIPPING UK WIDE Software Requirements by Soren Lauesen A practical guide to successfully specifying software requirements. This book cuts through the haze and offers clear, practical guidance on how to specify requirements in reality. The book takes the author's unique approach focusing on Styles i.e. whether you specify the requirement as plain text, diagrams, tables and Techniques i.e. ways of eliciting, checking and validating them. FORMATPaperback LANGUAGEEnglish CONDITIONBrand New Publisher Description Most IT systems fail to meet expectations. They don't meet business goals and don't support users efficiently. Why? Because the requirements didn't address the right issues. Writing a good requirements specification doesn't take more time. This book shows how it is done - many times faster and many times smarter. This book covers many aspects of requirements. Styles: Traditional and more cost/effective ways of expressing requirements. Techniques: Ways of gathering, verifying, and maintaining requirements; ways of getting commitment from the stakeholders and support - yet limit - innovation; ways of ensuring that you meet your business goals. It discusses the styles and techniques useful for different project types, for instance software developed specifically for the customer, software bought off-the shelf and adapted for the customer (COTS), and software developed for a broad market. The book illustrates everything through real-life examples. It also deals with difficult requirements, for instance how to specify ease-of-use, how to specify very complex computations, and how to deal with 200 reports that the old system has, and the new system may or may not need. The book shows two complete, real-life specifications and large parts of several others. It also has exercises and figures for presentation. Back Cover Most IT systems fail to meet expectations. They don't meet business goals and don't support users efficiently. Why? Because the requirements didn't address the right issues. Writing a good requirements specification doesn't take more time. This book shows how it's done - many times faster and many times smarter. What are the highlights? Two complete real-life requirements specifications (the traditional and the fast approach) and examples from many others. Explanations of both traditional and fast approaches, and discussions of their strengths and weaknesses in different project types (tailor-made, COTS, and product development). Real-life illustrations of all types of requirements, stakeholder analysis, cost/benefit and other techniques to ensure that business goals are met. Proven methods for dealing with difficult or complex requirements, such as specifying ease-of-use, or dealing with 200 reports that might be needed because they are in the old system. Who is it for? Everyone involved in the software supply chain, from analysts and developers to end users, will learn new techniques, benefit from requirements written by other specialists, and discover successes and failures from other companies. Software suppliers will find ideas for helping customers and writing competitive proposals. Programmers and other developers will learn how to express requirements without specifying technical details, and how to reduce risks when developing a system. Students aspiring to IT careers will learn the theory and practice of requirements engineering, and get a strong foundation for case studies and projects. Who is the author? Soren Lauesen is currently professor at the IT-University of Copenhagen. He has worked in the IT industry for 20 years and has been a professor at Copenhagen Business School for 15. He has been co-founder of three educational and two industrial development organizations. His industry projects have encompassed compilers, operating systems, process control, temporal databases, and software quality assurance. His research interests include human-computer interaction, requirements specification, object-oriented design, quality assurance, marketing and product development, and interaction between research and industry. He has a broad range of other interests ranging from biology to dancing and foreign cultures. Author Biography Soren Lauesen has close to forty years' industrial and academic experience in software development. He has worked as a developer of real-time systems and other software, co-founded software development centers at two companies, and worked as a management consultant for ILO in Ghana. He is currently a professor at the IT University, Copenhagen, Denmark, dividing his time between research, teaching and consulting. Table of Contents Preface Introduction & Basic Concepts Data Requirements Functional Requirements Non-Functional Requirements The Requirements Process Elicitation Checking & Validation Detailed Techniques References App A Danish Shipyard App B Public Health Admin App C Noise Source Location App D Budgeting & Accounting Long Description Most IT systems fail to meet expectations. They don't meet business goals and don't support users efficiently. Why? Because the requirements didn't address the right issues. Writing a good requirements specification doesn't take more time. This book shows how it is done - many times faster and many times smarter. This book covers many aspects of requirements. Styles: Traditional and more cost/effective ways of expressing requirements. Techniques: Ways of gathering, verifying, and maintaining requirements; ways of getting commitment from the stakeholders and support - yet limit - innovation; ways of ensuring that you meet your business goals. It discusses the styles and techniques useful for different project types, for instance software developed specifically for the customer, software bought off-the shelf and adapted for the customer (COTS), and software developed for a broad market. The book illustrates everything through real-life examples. It also deals with difficult requirements, for instance how to specify ease-of-use, how to specify very complex computations, and how to deal with 200 reports that the old system has, and the new system may or may not need. The book shows two complete, real-life specifications and large parts of several others. It also has exercises and figures for presentation. Feature * The requirements market is growing, as evidenced by the success of other Addison-Wesley requirements titles. * The author's extensive academic experience shows through in his ability to teach the practice of requirements. * The reader will learn the role that requirements play in the development process, how to elicit better requirements from the customer, and how to express better requirements to the development team. * Teaches the reader the best questions to ask the customer while gathering requirements. Introduction or Preface Have you ever used a new piece of software that didn''t meet your expectations? If so, it might be because nobody stated the expectations in a tangible manner. Software requirements are about writing the right expectations in the right way. These days, many people get involved in writing requirements. It is not only a job for specialists; users, customers, suppliers, and programmers also get involved. In small companies we sometimes even see employees without special training being asked to write requirements for a new software product. Furthermore, the roles of expert user, analyst, designer, and programmer seem to blend more and more. This book is important and relevant for many people involved in software requirements: The analyst, working as a requirements engineer or a consultant, can find tricks here and there, and he can look at requirements written by other specialists. The customer can find ways to ensure that the new product will meet his business goals, and suggestions for handling contracts and tenders. Software suppliers can find ideas for helping the customer and for writing competitive proposals. Users can prepare themselves for working with specialists or the developers. They can also find ways to describe their work tasks, and examples of what to write and what not to write in their requirements. Programmers and other developers can learn how to express requirements without specifying technical details, and how to reduce risks when developing a system. IT students can learn about theory and practice in requirements engineering, and get a foundation for case studies and projects. You don''t have to read the whole book. How can we cover so many topics for so many audiences? The answer is simple: you don''t have to read all of the book. If you read most of Chapter 1, you should then be able to read sections of the book in almost any order, according to your needs. Background When I began to work in the software industry in 1962, software requirements were relatively unimportant since at the time hardware was very expensive, and software was comparatively cheap. Renting a computer for an hour cost the same as paying someone to work for 30 hours and computers were 5000 times slower than they are today. Software development was carried out either on a time and materials basis, or as a small part of the really important job -- making better hardware. The customer paid until he had a program that printed results he could use with some effort. Nobody thought of usability. Everything to do with computers was a specialist''s job. Today things have completely changed. Hardware is cheap, and software development is expensive and ve, Pearson Education The Limited<
