Engelska · 591 sidor · 2002
- Språk
- Engelska
- Omfång
- 591 sidor
- Förlag
- Addison-Wesley
- Utgiven
- 2002
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.
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.
Priser & butiker
Priser & butiker
2 butiker · · lägsta pris först
Skriver du om boken på en blogg eller sajt? .
- Frakt
- Frakt från 29 kr · fri frakt över 249 kr
- Leverans
- 2-3 vardagar. Levereras hem, till ombud eller till paketskåp. Skickas med Budbee eller Instabox.
- Betalning
- Kort · Swish · Klarna · Faktura 30 dagar · Delbetalning
- Öppet köp
- 30 dagars öppet köp
- Medlemskap
- Bokus Play · 5 % medlemsrabatt · fri frakt för medlemmar
- Omdöme
- 3.4 av 5 på Trustpilot (1 639 omdömen)
- Frakt
- Frakt från 39 kr · fri frakt över 249 kr
- Leverans
- 2-4 vardagar. Levereras hem eller till ombud. Skickas med PostNord.
- Betalning
- Kort · Swish · Klarna · Faktura 30 dagar · Delbetalning
- Öppet köp
- 30 dagars öppet köp
- Omdöme
- 4.2 av 5 på Trustpilot (456 omdömen)
- Frakt
- Frakt från 29 kr · fri frakt över 249 kr
- Leverans
- 2-3 vardagar. Levereras hem, till ombud eller till paketskåp. Skickas med Budbee eller Instabox.
- Betalning
- Kort · Swish · Klarna · Faktura 30 dagar · Delbetalning
- Öppet köp
- 30 dagars öppet köp
- Medlemskap
- Bokus Play · 5 % medlemsrabatt · fri frakt för medlemmar
- Omdöme
- 3.4 av 5 på Trustpilot (1 639 omdömen)
- Frakt
- Frakt från 39 kr · fri frakt över 249 kr
- Leverans
- 2-4 vardagar. Levereras hem eller till ombud. Skickas med PostNord.
- Betalning
- Kort · Swish · Klarna · Faktura 30 dagar · Delbetalning
- Öppet köp
- 30 dagars öppet köp
- Omdöme
- 4.2 av 5 på Trustpilot (456 omdömen)
Samma ISBN jämförs hos alla butiker — priserna gäller samma utgåva.
Annonslänkar: Booki kan få provision när du handlar via våra länkar. Det påverkar inte ditt pris. Externa länkar utan pris ingår inte i jämförelsen.
Annonslänkar: Booki kan få provision när du handlar via våra länkar. Det påverkar inte ditt pris. Externa länkar utan pris ingår inte i jämförelsen.
Håll koll på priset
Håll koll på priset
Väntar du på ett lägre pris?
Bevaka priset på denna utgåva av Software Requirements och få besked när det sjunker.
Spara den här boken
Logga in för att lägga till i din bokhylla, bevaka priset och recensera.
Om boken
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.
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.
Bokfakta
Författare
Soren Lauesen
Förlag
Addison-Wesley
Utgivningsår
2002
Sidantal
591
Språk
Engelska
Fysiska detaljer
ill.
Dewey
005.12
ISBN
9780201745702

