Skip to main content
SpringerLink
Log in

Unified and Holistic Approach

  • Chapter
DevOps for Developers

  • 3079 Accesses

Abstract

This chapter will discuss a unified and holistic approach to software engineering. We’ll start with a discussion of concepts, particularly nonfunctional requirements. Then we’ll discuss one of the main dangers for collaboration between development and operations in more detail. Called a conceptual deficit, this can cause a discrepancy between business needs, project results, and expectations of operations.

You can only able call yourself senior programmer if you are spend more minute in meeting as in write code. —DevOps Borat 1

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 34.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 44.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. See Dean Leffingwell, Agile Software Requirements (Addison-Wesley, 2011), Chapter 17.

    Google Scholar 

  2. See Dean Leffingwell, Agile Software Requirements (Addison-Wesley, 2011), page 342.

    Google Scholar 

  3. See Gojko Adzic, Specification by Example (Manning, 2011), page 108.

    Google Scholar 

  4. See Mike Cohn, User Stories Applied (Addison-Wesley, 2004), page 178.

    Google Scholar 

  5. See Vilfredo Pareto, Manual of Political Economy (A.M. Kelley, 1969).

    Google Scholar 

  6. See Niccolo Machiavelli, The Prince, trans. Harvey C. Mansfield (University Of Chicago Press, 1998), Chapter 3.

    Google Scholar 

  7. See Taiichi Ohno, Toyota Production System: Beyond Large Scale Production (Productivity Press, 1988), page 17.

    Google Scholar 

  8. Len Bass et al., Software Architecture in Practice (Addison-Wesley, 2009).

    Google Scholar 

  9. See Michael Hüttermann, Agile ALM (Manning, 2011), Chapter 4.

    Google Scholar 

  10. See Alistair Cockburn, Writing Effective Use Cases (Addison-Wesley, 2001), pages 14 and 161.

    Google Scholar 

  11. Frank Buschmann et al. describe testability as a nonfunctional property of software architecture. See their Pattern-Oriented Software Architecture, Vol. 1 (Wiley, 1996), page 408.

    Google Scholar 

  12. See Lisa Crispin and Janet Gregory, Agile Testing (Addison-Wesley, 2009), page 104.

    Google Scholar 

  13. See James Whittaker et al., How Google Tests Software (Addison-Wesley, 2012), page 197.

    Google Scholar 

  14. See Jez Humble and David Farley, Continuous Delivery (Addison-Wesley, 2011), Chapter 9.

    Google Scholar 

  15. See Michael T. Nygard, Release It! (Pragmatic Bookshelf, 2007).

    Google Scholar 

  16. See Donald C. Gause and Gerald M. Weinberg, Exploring Requirements: Quality Before Design (Dorset House, 1998), page 274.

    Google Scholar 

Download references

Authors
  1. Michael Hüttermann
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Michael Hüttermann

About this chapter

Cite this chapter

Hüttermann, M. (2012). Unified and Holistic Approach. In: DevOps for Developers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4570-4_7

Download citation

Publish with us

Policies and ethics

Search

Navigation