ARCHITECTING SOFTWARE INTENSIVE SYSTEMS: A Practitioner's Guide

Architecting Software Intensive Systems: A Practitioner's Guide

Volumn , Issue , 2008, Pages 1-463

  Lattanze, Anthony J ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

EID: 85179244297     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1201/9781420045703     Document Type: Book

References (58)

1. Ambler, S. 2002. Agile modeling: Effective practices for extreme programming and the unified process. New York: John Wiley & Sons.
2. Barbacci, M., Ellison, R., Lattanze, A., Stafford, J., Weinstock, C., and Wood, W. 2003. Quality attribute workshops. 3rd ed. CMU/SEI-2003-TR-016, Carnegie Mellon University/Software Engineering Institute, Pittsburgh, PA.
3. Bass, L., Clements, P., and Kazman, R. 2003. Software architectures principles and practices. 2nd ed. Boston: Addison-Wesley.
4. Beck, K. 2000. Extreme programming explained: Embrace change. Reading, MA: Addison-Wesley.
5. Boehm, B. 1981. Software engineering economics. Englewood Cliffs, NJ: Prentice Hall.
6. Boehm, B. 1986. A spiral model of software development and enhancement. ACM SIGSOFT Software Engineering Notes 11:14-24.
7. Boehm, B., and Victor, B. 2001. Software defect reduction top 10 list. Technical Report USC CSE 2001-510, National Science Foundation/University of Southern California, Center for Empirically Based Software Engineering.
8. Bowman, T., Holt, R. C., and Brewster, N. V. 1999. Linux as a case study: Its extracted software architecture. In Proceedings of the 21st International Conference on Software Engineering, Los Angeles, May 16-22, 1999, pp. 555-63. New York: ACM Press.
9. Brooks, F. 1995. The mythical man-month: Essays on software engineering. Reading, MA: Addison-Wesley.
10. Broom, G., Casey, S., and Ritchey, J. 1997. Toward a concept and theory of organization-public relationships. Journal of Public Relations Research 9:83-98.
11. Broy, M., and Denert, E., eds. 2002. Software pioneers: Contributions to software engineering. New York: Springer.
12. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., and Stal, M. 1996. A system of patterns: Patternoriented software architecture. New York: Wiley.
13. Carney, D. 1998. Quotations from Chairman David: A little red book of truths to enlighten and guide on the long march toward the COTS revolution. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.
14. Clements, P., Bachmann, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., and Stafford, J. 2003. Documenting software architectures: Views and beyond. Boston: Addison-Wesley.
15. Clements, P., Kazman, R., and Klein, M. 2001. Evaluating software architectures: Methods and case studies. Boston: Addison-Wesley.
16. Clements, P., and Shaw, M. 2003. The golden age of software architecture: A comprehensive survey. CMU/ SEI-2003-TR-016, CMU-ISRI-06-101, Carnegie Mellon University/Institute for Software Research, Pittsburgh, PA.
17. CMMI Product Team. 2002. CMMI for systems engineering, software engineering, integrated product and process development, and supplier sourcing (CMMI-SE/SW/IPPD/SS, V1.1): Improving processes for better products: Staged representation. CMU/SEI-2002-TR-012, ESC-TR-2002-01, Carnegie Mellon University/ Institute for Software Research, Pittsburgh, PA.
18. Coleman, D., Lowther, B., and Oman, P. 1995. The application of software maintainability models in industrial software systems. Journal of Systems Software 29:3-16.
19. Fagan, M. E. 1976. Design and code inspections to reduce errors in program development. IBM Systems Journal 15:182-211.
20. Fagan, M. E. 1996. Advances in software inspections. IEEE Transactions on Software Engineering SE-12:744-51.
21. Forsberg, K., Mooz, H., Cotterham, H. 1996. Visualizing project management. New York: John Wiley.
22. Gamma, E., Helm, R., Johnson, R., and Vlissides, J. 1995. Design patterns: Elements of reusable object-oriented software. Boston: Addison-Wesley.
23. Garlan, D., and Shaw, M. 1996. Software architecture: Perspectives on an emerging discipline. Upper Saddle River, NJ: Prentice Hall.
24. Goodyear, M., Ryan, H., Sargent, S., Taylor, S., Boudreau, T., Arvanitis, Y., Chang, R., Kaltenmark, J., Mullen, N., Dove, S., Davis, M., Clark, J., and Mindrum, C. 2000. Enterprise system architectures. Boca Raton, FL: CRC Press.
25. Guo, G., Atlee, J., and Kazman, R. 1999. A software architecture reconstruction method. In Proceedings of the First Working IFIP Conference on Software Architecture (WICSA1), San Antonio, TX, February 22-24, 1999, pp. 225-43. Norwell, MA: Kluwer Academic Publishers.
26. Hamlin, A. D. F. 1909. A text-book of the history of architecture. New York: Longmans, Green, and Co.
27. Harris, D. R., Reubenstein, H. B., and Yeh, A. S. 1995. Reverse engineering to the architectural level, 186-95. In Proceedings of the 17th International Conference on Software Engineering (ICSE), Seattle, April 23-30, 1995. New York: ACM Press.
28. Hindo, B. 2007. At 3M, a struggle between efficiency and creativity: How CEO George Buckley is managing the yin and yang of discipline and imagination. BusinessWeek, June 11.
29. Hughes, T. P. 1989. American genesis: A century of invention and technological enthusiasm. Viking: New York.
30. Humphrey, W. 1995. A discipline of software engineering. Reading, MA: Addison-Wesley Professional.
31. Humphrey, W. 1989. Managing the software development process. Reading, MA: Addison-Wesley.
32. Humphrey, W. 1999. Team software process. Reading, MA: Addison-Wesley.
33. INCOSE (International Committee on System Engineering). http://www.incose.org/.
34. Jackson, M. A. 1983. System development. Englewood Cliffs, NJ: Prentice Hall.
35. Jacobson, I., Christenson, M., Jonsson, P., and Overgaard, G. 1992. Object-oriented software engineering: A use case driven approach. Reading, MA: Addison-Wesley.
36. Krutchen, P. 1995. The 4+1 view model of software architecture. IEEE Software 12:42-50.
37. Krutchen, P. 2004. The rational unified process: An introduction. 3rd ed. Reading, MA: Addison-Wesley Professional.
38. Maier, M., and Rechtin, E. 2000. The art of systems architecting. 2nd ed. Boca Raton, FL: CRC Press.
39. Marca, D., and McGowan, C. 1988. SADT: Structured analysis and design technique. New York: McGraw-Hill.
40. Martin, J. 1984. An information systems manifesto. Englewood Cliffs, NJ: Prentice Hall.
41. Martin, J. 1991. Rapid application development. New York: Macmillan Publishing.
42. McAndrews, D. 2000. The team software process (TSP): An overview and preliminary results of using disciplined practices. CMU/SEI-2000-TR-015, ESC-TR-2000-015, Carnegie Mellon University/Software Engineering Institute, Pittsburgh, PA.
43. Meason, G. L. 1828. The landscape architecture of the great painters of Italy. C. Hullmandel's Lithographic Establishment, London.
44. Oxford English Dictionary. 2004. Oxford: Oxford University Press.
45. Parnas, D. L. 1972. On the criteria to be used in decomposing systems into modules. Communications of the ACM 15:1053-58.
46. Paulk, M., Weber, C., Curtis, B., and Chrissis, M. 1995. The capability maturity model: Guidelines for improving the software process. Reading, MA: Addison-Wesley.
47. Pressman, R. 2005. Software engineering: A practitioners approach. 6th ed. Singapore: McGraw-Hill.
48. Rechtin, E. 1991. Systems architecting: Creating and building complex systems. Englewood Cliffs, NJ: Prentice Hall.
49. Sangwan, R., Bass, M., Mullick, N., and Paulish, D. 2006. Global software development handbook. New York: Auerbach Publishing.
50. Schwaber, K., and Beedle, M. 2004. Agile project management with Scrum. Redmond, WA: Microsoft Press.
51. Schwaber, K. 2007. The enterprise and Scrum. Redmond, WA: Microsoft Press.
52. Sowa, J. F., and Zachman, J. A. 1992. Extending and formalizing the framework for information systems architecture. IBM Systems Journal 31(3).
53. Thome, B., ed. 1993. Systems engineering: Principle and practice of computer-based system engineering. New York: John Wiley & Sons.
54. U.S. Government Accounting Office (GAO). 1999. Observations on FAA's air traffic control modernization program. Testimony before the Subcommittee on Aviation, Committee on Commerce, Science and Transportation, U.S. Senate, March 25.
55. Vitruvius. 1914. The ten books on architecture, trans. M. H. Morgan. Cambridge, MA: Harvard University Press.
56. Yourdon, E. 1989a. Modern structured analysis. Englewood Cliffs, NJ: Yourdon Press.
57. Yourdon, E. 1989b. Structured walkthroughs. 4th ed. Englewood Cliffs, NJ: Yourdon Press.
58. Zachman, J. 1987. A framework for information systems architecture. IBM Systems Journal 26(3).