Countries citing papers authored by John D. McGregor
Since
Specialization
Citations
This map shows the geographic impact of John D. McGregor's research. It shows the number of citations coming from papers published by authors working in each country. You can also color the map by specialization and compare the number of citations received by John D. McGregor with the expected number of citations based on a country's size and research output (numbers larger than one mean the country cites John D. McGregor more than expected).
Fields of papers citing papers by John D. McGregor
This network shows the impact of papers produced by John D. McGregor. Nodes represent research fields, and links connect fields that are likely to share authors. Colored nodes show fields that tend to cite the papers produced by John D. McGregor. The network helps show where John D. McGregor may publish in the future.
Co-authorship network of co-authors of John D. McGregor
This figure shows the co-authorship network connecting the top 25 collaborators of John D. McGregor.
A scholar is included among the top collaborators of John D. McGregor based on the total number of
citations received by their joint publications. Widths of edges
represent the number of papers authors have co-authored together.
Node borders
signify the number of papers an author published with John D. McGregor. John D. McGregor is excluded from
the visualization to improve readability, since they are connected to all nodes in the network.
McGregor, John D., et al.. (2010). Reasoning about Safety during Software Architecture Design.. 1–8.
3.
McGregor, John D., et al.. (2010). Reasoning about Attribute Architectures.. Software Engineering and Knowledge Engineering. 165–171.
4.
McGregor, John D., et al.. (2010). Locating Defects in Software Architectures Through Debugging.. 15–20.
5.
Hunt, John & John D. McGregor. (2009). Building software that is predictable by Construction. Journal of computing sciences in colleges. 25(2). 203–204.1 indexed citations
6.
Chastek, Gary & John D. McGregor. (2009). Modeling Variation in Production Planning Artifacts.. 45–50.2 indexed citations
7.
McGregor, John D.. (2009). Proceedings of the 47th Annual Southeast Regional Conference.1 indexed citations
Hunt, John & John D. McGregor. (2006). Software product lines: a pedagogical application. Journal of computing sciences in colleges. 22(2). 295–302.1 indexed citations
Böckle, Günter, et al.. (2003). A cost model for software product lines. Publikationsdatenbank der Fraunhofer-Gesellschaft (Fraunhofer-Gesellschaft).2 indexed citations
12.
McGregor, John D.. (1998). The Year 2000 Crisis and the Search for Absolute Truth.. Journal of Object-oriented Programming. 11. 10–12.4 indexed citations
13.
McGregor, John D.. (1998). Quality, Thy Name Is Not Testing.. Journal of Object-oriented Programming. 11. 8–12.33 indexed citations
14.
McGregor, John D.. (1998). Testing Models: The Requirements Model.. Journal of Object-oriented Programming. 11.4 indexed citations
15.
McGregor, John D.. (1998). Test Cases from a Specification: An Example.. Journal of Object-oriented Programming. 10. 66–70.1 indexed citations
16.
McGregor, John D.. (1998). Let's Don't and Say We Did.. Journal of Object-oriented Programming. 11.1 indexed citations
17.
McGregor, John D.. (1997). A component testing method. 10(3). 5–9.1 indexed citations
18.
McGregor, John D.. (1997). An Overview of Testing.. Journal of Object-oriented Programming. 9. 5–9.3 indexed citations
19.
McGregor, John D., et al.. (1992). Object-oriented software development: engineering software for Reuse. CERN Document Server (European Organization for Nuclear Research).27 indexed citations
20.
McGregor, John D.. (1987). Object-oriented programming with SCOOPS. Computer Languages. 4(7). 49–56.1 indexed citations
Rankless uses publication and citation data sourced from OpenAlex, an open and comprehensive
bibliographic database. While OpenAlex provides broad and valuable coverage of the global
research landscape, it—like all bibliographic datasets—has inherent limitations. These include
incomplete records, variations in author disambiguation, differences in journal indexing, and
delays in data updates. As a result, some metrics and network relationships displayed in
Rankless may not fully capture the entirety of a scholar's output or impact.