Software Design 2e - DIM

Guindon R. (1990). Designing the design process: exploiting opportunistic thoughts. Human–Computer Interaction, 5, 305–44Guindon R. and Curtis B. (1988). Control of cognitive processes during software design: Whattools are needed? In Proceedings of CHI’88, 263–8. ACM PressHall N.R. and Preiser S. (1984). Combined network complexity measures. IBM J. Research andDevelopment, 28(1), 15–27Hall A. (1990). Seven myths of formal methods. IEEE Software, 7(5), 11–19Halstead M.H. (1977). Elements of Software Science. North-HollandHardy C.J., Thompson J.B. and Edwards H.M. (1995). The use, limitations and customizationof structured systems development methods in the United Kingdom. Information & SoftwareTechnology, 37(9), 467–77Harel D. (1987). Statecharts: a visual formalism for complex systems. Science of ComputerProgramming, 8, 231–74Harel D. (1988). On visual formalisms. Comm. ACM, 31(5), 514–30Harel D. (1992). Biting the silver bullet: toward a brighter future for system development. IEEEComputer, 25(1), 8–20Harel D., Lachover H., Naamad A., Pnueli A., Politi M., Sherman R., Shtull-Trauring A. andTrakhtenbrot M. (1990). STATEMATE: a working environment for the development of complexreactive systems. IEEE Trans. Software Eng., SE-16(4), 403–13Harel D. and Gery E. (1997). Executable object modeling with Statecharts. IEEE Computer,30(7), 31–42Hatley D.J. and Pirbhai I. (1988). Strategies for Real-Time System Specification. DorsetHouseHayes I.J. and Jones C.B. (1989). Specifications are not (necessarily) executable. SoftwareEngineering J., 4(6), 330–38Heineman G.T. and Councill W.T. (2001). Component-Based Software Engineering: Puttingthe Pieces Together. Addison-WesleyHenderson-Sellers B. and Constantine L.L. (1991). Object-oriented development and functionaldecomposition. J. Object-Oriented Programming, 3(5), 11–17Henderson-Sellers B. and Edwards J.M. (1990). The object-oriented systems life-cycle. Comm.ACM, 33(9), 142–59Henry S. and Kafura D. (1984). The evaluation of software systems’ structure using quantitativesoftware metrics. Software Practice and Experience, 14, 561–73Hoare C.A.R. (1978). Communicating sequential processes. Comm. ACM, 21(8), 666–7Huang R. (1998). Formalizing hierarchical object-oriented design method. ACM Software Eng.Notes, 23(5), 82–8Humphrey W.S. (1991). Managing the Software Process. Addison-WesleyIivari J. (1995). Object-orientation as structural, functional and behavioural modelling: a comparisonof six methods for object-oriented analysis. Information & Software Technology,37(3), 155–63Jackson M.A. (1975). Principles of Program Design. Academic PressJackson M.A. (1983). System Development. Prentice-HallJacobson I., Christerson M., Jonsson P. and Overgaard G. (1992). Object-Oriented SoftwareEngineering: A Use Case Driven Approach. Addison-WesleyJacobson I., Booch G. and Rumbaugh J. (1999). The Unified Software Development Process.Addison-WesleyJézéquel J-M. and Meyer B. (1997). Design by contract: the lessons of Ariane. IEEE Computer,30(1), 129–30Johnson R.E. (1997). Frameworks = (Components + Patterns). Comm. ACM, 40(10), 39–42Johnson R.A. and Hardgrave W.C. (1999). Object-oriented methods: current practices and attitudes.J. Systems & Software, 48(1), 5–12455Bibliography