![]() |
other persons with the same name:
| 2008 | ||
|---|---|---|
| 74 | EE | Michael Jackson: Automated software engineering: supporting understanding. Autom. Softw. Eng. 15(3-4): 275-281 (2008) |
| 73 | EE | Mike Hinchey, Michael Jackson, Patrick Cousot, Byron Cook, Jonathan P. Bowen, Tiziana Margaria: Software engineering and formal methods. Commun. ACM 51(9): 54-59 (2008) |
| 72 | EE | Jon G. Hall, Lucia Rapanotti, Michael Jackson: Problem Oriented Software Engineering: Solving the Package Router Control Problem. IEEE Trans. Software Eng. 34(2): 226-241 (2008) |
| 2007 | ||
| 71 | EE | Michael Jackson: The Problem Frames Approach to Software Engineering. APSEC 2007: 14 |
| 70 | EE | Michael Jackson: Specialising in Software Engineering. APSEC 2007: 3-10 |
| 69 | Robin C. Laney, Thein Than Tun, Michael Jackson, Bashar Nuseibeh: Composing Features by Managing Inconsistent Requirements. ICFI 2007: 129-144 | |
| 68 | EE | Michael Jackson: The Name and Nature of Software Engineering. Lipari Summer School 2007: 1-38 |
| 67 | EE | Jon G. Hall, Lucia Rapanotti, Michael Jackson: Problem Oriented Software Engineering: A design-theoretic framework for software engineering. SEFM 2007: 15-24 |
| 66 | EE | Michael Jackson: Specialising in Software Engineering. SEFM 2007: 3 |
| 2006 | ||
| 65 | EE | Michael Jackson: Testing the Machine in the World. Haifa Verification Conference 2006: 198-203 |
| 64 | EE | Michael Jackson: Structural Relationships among Models. MMOSS 2006 |
| 63 | EE | Daniel Jackson, Michael Jackson: Separating Concerns in Requirements Analysis: An Example. RODIN Book 2006: 210-225 |
| 62 | EE | Michael Jackson: What Can We Expect from Program Verification? IEEE Computer 39(10): 65-71 (2006) |
| 2005 | ||
| 61 | EE | Michael Jackson, Pamela Zave: Where do you go when you're through the turnstile? ICSE 2005: 44 |
| 60 | EE | Michael Jackson: Problem frames and software engineering. Information & Software Technology 47(14): 903-912 (2005) |
| 59 | EE | Jon G. Hall, Lucia Rapanotti, Michael Jackson: Problem frame semantics for software development. Software and System Modeling 4(2): 189-198 (2005) |
| 2004 | ||
| 58 | EE | Leonor Barroca, José Luiz Fiadeiro, Michael Jackson, Robin C. Laney, Bashar Nuseibeh: Problem Frames: A Case for Coordination. COORDINATION 2004: 5-19 |
| 57 | EE | Robin C. Laney, Leonor Barroca, Michael Jackson, Bashar Nuseibeh: Composing Requirements Using Problem Frames. RE 2004: 122-131 |
| 56 | EE | Luncheng Lin, Bashar Nuseibeh, Darrel C. Ince, Michael Jackson: Using Abuse Frames to Bound the Scope of Security Problems. RE 2004: 354-355 |
| 55 | EE | Lucia Rapanotti, Jon G. Hall, Michael Jackson, Bashar Nuseibeh: Architecture-driven Problem Decomposition. RE 2004: 80-89 |
| 54 | EE | Michael Jackson: Problem Structure and Dependable Architecture. WADS 2004: 322-330 |
| 53 | EE | Michael Jackson: Seeing More of the World. IEEE Software 21(6): 83-85 (2004) |
| 2003 | ||
| 52 | EE | Luncheng Lin, Bashar Nuseibeh, Darrel C. Ince, Michael Jackson, Jonathan D. Moffett: Introducing Abuse Frames for Analysing Security Requirements. RE 2003: 371-372 |
| 51 | EE | Michael Jackson: Why software writing is difficult and will remain so. Inf. Process. Lett. 88(1-2): 13-25 (2003) |
| 2002 | ||
| 50 | EE | Michael Jackson: Where, Exactly, Is Software Development? 10th Anniversary Colloquium of UNU/IIST 2002: 115-131 |
| 49 | EE | Babak Khazaei, Michael Jackson: Is There Any Difference in Novice Comprehension of a Small Program Written in the Event-Driven and Object-Oriented Styles? HCC 2002: 19- |
| 48 | EE | Babak Khazaei, Michael Jackson: Is There Any Difference in Novice Comprehension of a Small Program Written in the Event-Driven and Object-Oriented Styles? IEEE Symposia on Human Centric Computing Languages and Environments 2002: 19- |
| 47 | EE | Jon G. Hall, Michael Jackson, Robin C. Laney, Bashar Nuseibeh, Lucia Rapanotti: Relating Software Requirements and Architectures Using Problem Frames. RE 2002: 137-144 |
| 46 | EE | Michael Jackson: Formalism and Informality in Software Development. Soft-Ware 2002: 356 |
| 45 | EE | Michael Jackson: Descriptions in Software Development. UML 2002: 1 |
| 44 | EE | Pamela Zave, Michael Jackson: A Call Abstraction for Component Coordination. Electr. Notes Theor. Comput. Sci. 66(4): (2002) |
| 43 | EE | Michael Jackson: Some Basic Tenets of Description. Software and System Modeling 1(1): 5-9 (2002) |
| 2001 | ||
| 42 | EE | Michael Jackson: Formalism and Informality in RE. RE 2001: 269 |
| 2000 | ||
| 41 | EE | Kevin D. Reilly, Norman W. Bray, Michael Jackson: Approaches to Cognitive System Simulation: Architectures and Animations. Annual Simulation Symposium 2000: 198- |
| 40 | Michael Jackson, Helen Lowe: System Description: Interactive Proof Critics in XBarnacle. CADE 2000: 502-506 | |
| 39 | EE | Raul Camposano, Jacob Greidinger, Patrick Groeneveld, Michael Jackson, Lawrence T. Pileggi, Louis Scheffer: Design closure (panel session): hope or hype? DAC 2000: 176-177 |
| 38 | Pamela Zave, Michael Jackson: New Feature Interactions in Mobile and Multimedia Telecommunications Services. FIW 2000: 51-66 | |
| 37 | EE | Carl A. Gunter, Elsa L. Gunter, Michael Jackson, Pamela Zave: A Reference Model for Requirements and Specifications-Extended Abstract. ICRE 2000: 189 |
| 36 | Michael Jackson: Christopher Strachey: A Personal Recollection. Higher-Order and Symbolic Computation 13(1/2): 73-74 (2000) | |
| 35 | EE | Carl A. Gunter, Elsa L. Gunter, Michael Jackson, Pamela Zave: A Reference Model for Requirements and Specifications. IEEE Software 17(3): (2000) |
| 1999 | ||
| 34 | EE | Michael Jackson: The Role of Formalism in Method. World Congress on Formal Methods 1999: 56 |
| 33 | EE | Andrew Ireland, Michael Jackson, Gordon Reid: Interactive Proof Critics. Formal Asp. Comput. 11(3): 302-325 (1999) |
| 32 | EE | Michael Jackson: Specializing in Software Engineering. IEEE Software 16(6): 119-121 (1999) |
| 1998 | ||
| 31 | Karthikeyan Bhargavan, Carl A. Gunter, Elsa L. Gunter, Michael Jackson, Davor Obradovic, Pamela Zave: The Village Telephone System: A Case Study in Formal Software Engineering. TPHOLs 1998: 49-66 | |
| 30 | Michael Jackson: Will There Ever Be Software Engineering? IEEE Software 15(1): 36-39 (1998) | |
| 29 | EE | Michael Jackson: Defining a Discipline of Description. IEEE Software 15(5): 14-17 (1998) |
| 28 | EE | Pamela Zave, Michael Jackson: A Component-Based Approach to Telecommunication Software. IEEE Software 15(5): 70-78 (1998) |
| 27 | EE | Michael Jackson, Pamela Zave: Distributed Feature Composition: A Virtual Architecture for Telecommunications Services. IEEE Trans. Software Eng. 24(10): 831-847 (1998) |
| 26 | EE | Michael Jackson: Formal methods and traditional engineering. Journal of Systems and Software 40(3): 191-194 (1998) |
| 1997 | ||
| 25 | EE | Michael Jackson: Problem complexity. ICECCS 1997: 239- |
| 24 | EE | Pamela Zave, Michael Jackson: Requirements for Telecommunications Services: An Attack on Complexity. RE 1997: 106-117 |
| 23 | EE | Pamela Zave, Michael Jackson: Four Dark Corners of Requirements Engineering. ACM Trans. Softw. Eng. Methodol. 6(1): 1-30 (1997) |
| 22 | Michael Jackson: The Meaning of Requirements. Ann. Software Eng. 3: 5-21 (1997) | |
| 21 | Pamela Zave, Michael Jackson: Telecommunications Service Requirements: Principles for Managing Complexity. Requir. Eng. 2(2): 92-101 (1997) | |
| 1996 | ||
| 20 | EE | Michael Jackson: Problems, Methods, and Structures (Abstract). SIGSOFT FSE 1996: 1 |
| 19 | EE | Pamela Zave, Michael Jackson: Where Do Operations Come From: A Multiparadigm Specification Technique. IEEE Trans. Software Eng. 22(7): 508-528 (1996) |
| 1995 | ||
| 18 | EE | Michael Jackson, Pamela Zave: Deriving Specifications from Requirements: An Example. ICSE 1995: 15-24 |
| 17 | EE | Michael Jackson: The World and the Machine. ICSE 1995: 283-292 |
| 16 | EE | Michael Jackson: Problems and requirements (software development). RE 1995: 2-9 |
| 15 | Michael Jackson: Desert Island Column. Autom. Softw. Eng. 2(4): 353-355 (1995) | |
| 14 | EE | Michael Jackson: Critical Reading For Software Developers. IEEE Software 12(6): 103-104 (1995) |
| 1994 | ||
| 13 | Michael Jackson: Problems, Descriptions and Objects. OOIS 1994: 25-35 | |
| 12 | EE | Michael Jackson: Problems, Methods and Specialization. IEEE Software 11(6): 57-62 (1994) |
| 1993 | ||
| 11 | EE | Pamela Zave, Michael Jackson: Conjunction as Composition. ACM Trans. Softw. Eng. Methodol. 2(4): 379-411 (1993) |
| 1991 | ||
| 10 | Jonah Z. Lavi, Ashok K. Agrawala, Raymond J. A. Buhr, Ken Jackson, Michael Jackson, Bernard Lang: Computer Based Systems Engineering Workshop. CSEE 1991: 149-163 | |
| 9 | Michael Jackson: Description is our Business. VDM Europe (1) 1991: 1-8 | |
| 8 | Pamela Zave, Michael Jackson: Techniques for Partial Specification and Specification of Switching Systems. VDM Europe (1) 1991: 511-525 | |
| 7 | Pamela Zave, Michael Jackson: Techniques for Partial Specification and Specification of Switching Systems. Z User Workshop 1991: 205-219 | |
| 1989 | ||
| 6 | Michael Jackson: Software Engineering for Business DP: Looking Back and Looking Forward. ICSE 1989: 135 | |
| 5 | Michael Jackson: Software Development in the Year 2000. ICSE 1989: 257 | |
| 1987 | ||
| 4 | Christopher J. Van Wyk, Michael Jackson, David W. Wall: Processing Transactions. Commun. ACM 30(12): 1000-1010 (1987) | |
| 1982 | ||
| 3 | Michael Jackson: Software Development as an Engineering Problem. Angewandte Informatik 24(2): 96-103 (1982) | |
| 1978 | ||
| 2 | Michael Jackson: Information Systems: Modelling, Sequencing and Transformations. ICSE 1978: 72-81 | |
| 1976 | ||
| 1 | Michael Jackson: Constructive Methods of Program Design. ECI 1976: 236-262 | |