Software Design 2e - DIM

458BibliographyShapiro S. (1997). Splitting the difference: the historical necessity of synthesis in SoftwareEngineering. IEEE Annals of the History of Computing, 19(1), January–March, 20–54Sharp H., Robinson H. and Woodman M. (2000). Software engineering: community and culture.IEEE Software, 17(1), 40–47Shaw M. and Clements P. (1997). A field guide to boxology: preliminary classification of architecturalstyles for software systems. Proceedings COMPSAC’97, 21st International ComputerSoftware and Applications Conference, August 1997, Washington, DC, pp. 6–13. LosAlamitos, California: IEEE Computer Society PressShaw M. and Garlan D. (1996). Software Architecture: Perspectives on an Emerging Discipline.Prentice-HallSheetz S.D. and Tegarden D.P. (1996). Perceptual complexity of object oriented systems: astudent view. Object Oriented Systems, 3(4), 165–95Shepperd M. and Ince D. (1993). Derivation and Validation of Software Metrics. ClarendonPressSimon H.A. (1984). The structure of ill-structured problems. In Developments in DesignMethodology (Cross N., ed.), 145–66. WileySimpson H.R. and Jackson K. (1979). Process synchronisation in MASCOT. Computer J.,22(4), 332–45Snyder A. (1993). The essence of objects: concepts and terms. IEEE Software, 11(1), 31–42Sommerville I. (2001). Software Engineering, 6th edn. Addison-WesleySpivey M.J. (1992). The Z Notation: A Reference Manual, 2nd edn. Prentice-HallStevens P. and Pooley R. (2000). Using UML: Software Engineering with Objects and Components.Addison-WesleyStevens W.P. (1991). Software Design: Concepts and Methods. Prentice-HallStevens W.P., Myers G.J. and Constantine L.L. (1974). Structured design. IBM Systems J., 13,115–39Sutcliffe A. (1988). Jackson System Development. Prentice-HallSwartz A. J. (1996). Airport 95: Automated baggage system? ACM Software Engineering Notes,21(2), 79–83Szyperski C. (1998). Component Software: Beyond Object-Oriented Programming. Addison-WesleyTaivalsaari A. (1993). On the notion of object. J. Systems & Software, 21(1), 3–16Tomayko J.E. (1996). Carnegie Mellon’s Software Development Studio: A Five Year Retrospective.In Proceedings 9th Conference on Software Engineering Education, Daytona, FL,119–29. Los Alamitos, California: IEEE Computer Society Press.Traas V. and van Hillegersberg J. (2000). The software component market on the internet:Current status and conditions for growth. ACM Softw. Eng. Notes, 25(1), 114–17Troy D.A. and Zweben S.H. (1981). Measuring the quality of structured designs. J. Systems andSoftware, 2, 113–20Truex D., Baskerville R. and Klein H. (1999). Growing systems in emergent organisations.Comm. ACM, 42(8), 117–23Van Vliet H. (2000) Software Engineering Principles and Practice, 2nd edn. WileyVessey I. and Conger S.A. (1994). Requirements specification: learning object, process and datamethodologies. Comm. ACM, 37(5), 102–13Visser W. (1987). Strategies in programming programmable controllers: a field study on a professionalprogrammer. In Empirical Studies of Programmers: Second Workshop (Olsen G.M.,Sheppard S. and Soloway E., eds.), 217–30. AblexVisser W. and Hoc J.-M. (1990). Expert software design strategies. In Psychology of Programming(Hoc J.-M., Green T.R.G., Samurçay R. and Gilmore D.J., eds), 235–49. Academic PressWard P.T. (1986). The transformation schema: an extension of the data-flow diagram to representcontrol and timing. IEEE Trans. Software Eng., SE-12(2), 198–210