Tom Gilb
#13,434
Most Influential Person Now
Systems engineer, consultant, author
Tom Gilb's AcademicInfluence.com Rankings
Tom Gilbphilosophy Degrees
Philosophy
#5610
World Rank
#8460
Historical Rank
#1446
USA Rank
Ontology
#75
World Rank
#85
Historical Rank
#7
USA Rank
Logic
#8297
World Rank
#10357
Historical Rank
#1361
USA Rank
Download Badge
Philosophy Communications
Why Is Tom Gilb Influential?
(Suggest an Edit or Addition)According to Wikipedia, Tom Gilb is an American systems engineer, consultant, and author, known for the development of software metrics, software inspection, and evolutionary processes. Biography Tom Gilb was born in 1940 in Pasadena, California, United States. He emigrated to the United Kingdom in 1956 and to Norway in 1958. He took his first job with IBM in 1958 and became a freelance consultant in 1960.
Tom Gilb's Published Works
Number of citations in a given year to any of this author's works
Total number of citations to an author for the works they published in a given year. This highlights publication of the most important work(s) by the author
Published Works
- Principles of software engineering management (1988) (501)
- Software Inspection (1994) (348)
- Interactive Decision Making: The Graph Model for Conflict Resolution (1994) (328)
- Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, And Software Engineering Using Planguage (2005) (189)
- Can Internet-Based Applications Be Engineered (1998) (90)
- Evolutionary development (1981) (88)
- Evolutionary Delivery versus the "waterfall model" (1985) (56)
- Towards the engineering of requirements (1997) (37)
- Level 6: Why We Can't Get There from Here (1996) (18)
- 11.4.1 From Waterfall to Evolutionary Development (Evo): How we rapidly created faster, more user‐friendly, and more productive software products for a competitive multi‐national market (2005) (17)
- 11.4.2 Managing Priorities: A Key to Systematic Decision‐Making (2005) (17)
- Design by objectives (1987) (17)
- Humanized input : techniques for reliable keyed input (1977) (14)
- 1.6.1 Software Project Management: Adding Stakeholder Metrics to Agile Projects (2004) (13)
- Estimating the risk (1989) (13)
- What's Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right (2010) (11)
- Planning to Get the Most Out of Inspection (2000) (10)
- 9.1.5 Risk Management: A practical toolkit for identifying, analyzing and coping with project risks (2002) (9)
- Deadline Pressure: How to Cope with Short Deadlines, Low Budgets and Insufficient Staffing Levels (1989) (9)
- Evolutionary Project Management (2005) (8)
- Increasing software productivity (1983) (7)
- Project Failures: Continuing Challenges for Sustainable Information Systems (2004) (7)
- The 10 Most Powerful Principles for Quality in Software and Software Organizations (2000) (7)
- Estimating software attributes: some unconventional points of view (1986) (6)
- Advanced Requirements Specification: Quantifying The Qualitative (1999) (6)
- No cure no pay: How to contract for software services (2007) (6)
- Security and Quality in Cyber-Physical Systems Engineering: With Forewords by Robert M. Lee and Tom Gilb (2019) (5)
- 2 Quantifying The Qualitative: How to Avoid Vague Requirements by Clear Specification Language (1999) (5)
- Evolutionary Project Management: Multiple Performance, Quality and Cost Metrics for Early and Continuous Stakeholder Value Delivery (2004) (5)
- What's Wrong with Agile Methods? Some Principles and Values to Encourage Quantification (2007) (5)
- Rule-Based Design Reviews (2004) (4)
- 8.2.1 Agile Specification Quality Control: Shifting emphasis from cleanup to sampling defects (2005) (4)
- A planning language (a PLanguage) (1989) (4)
- Estimation: A Paradigm Shift towards Dynamic Design‐to‐Cost and Radical Management (2011) (3)
- Practical purposeful creativity constructs (2005) (3)
- How to quantify quality: Finding scales of measure (2006) (3)
- System attribute specification: a cornerstone of software engineering (1981) (3)
- 12.3 Project Failure Prevention: 10 Principles for Project Control (2005) (3)
- Understanding Complex Technology Quantitatively: Impact Estimation Tables (1999) (3)
- Impact Estimation Tables Understanding Complex Technology Quantitatively (3)
- 12.2 Fundamental Principles of Evolutionary Project Management (2005) (3)
- Tools for “Design by Objectives (1986) (3)
- The Ten Most Powerful Principles for Quality in (Software and) Software Organizations for Dependable Systems (2000) (3)
- Software engineering: using "design by objectives" tools (DBO) (1984) (3)
- 5.4.3 Real Requirements: How to find out what the requirements really are (2005) (2)
- Undergraduate Basics for Systems Engineering (SE), using The Principles, Measures, Concepts and Processes of Planguage (2007) (2)
- Reliable edp application design (1973) (2)
- The pre-natal death of the CIS project: A software disaster story (1988) (2)
- A comment on "the definition of maintainability" (1979) (2)
- 1.8.2 Managing Project Risks in Requirements, Design and Development using Planguage (2003) (2)
- Software specification and design must “Engineer” quality and cost iteratively (1986) (2)
- 7.4.2 What's fundamentally wrong? Improving our approach towards capturing value in requirements specification (2012) (2)
- The "Design by Objectives" Method for Controlling Maintainability: A Quantitative Approach for Software (1980) (1)
- 4.4.1 Rule‐Based Design Reviews (2007) (1)
- What's Wrong With Quality Function Deployment (QFD)? And How to Do Better With Impact Estimation Tables (2008) (1)
- Multidimensional quantified goals should direct software design processes (1978) (1)
- 6.3.2 No Cure No Pay: How to Contract for Software Services (2006) (1)
- Requirement Relationships: A Theory, Some Principles, and a Practical Approach (2007) (1)
- 6.2.2 Requirements for Outsourcing (2007) (1)
- Looking at problems through technoscopes (1983) (1)
- 7.6.4 Some Powerful Systems Engineering Heuristics (2007) (1)
- Experiences and Advances in Software Quality (2009) (1)
- Performance: How Good? (2005) (1)
- 6.2.4 Evolutionary Project Management (Evo): How to Manage Project Benefits and Costs (2003) (1)
- Scales of Measure: How to Quantify (2005) (1)
- 9.1.7 Towards the Engineering of Requirements (2002) (1)
- Software What is It Made of? (1978) (0)
- 10.4 A Conceptual Glossary for Systems Engineering (2004) (0)
- 12.1 Design Evaluation: Estimating Multiple Critical Performance and Cost Impacts of Designs (2005) (0)
- Impact Estimation: How to understand strategies (2005) (0)
- 3.6.2 Managing Priorities: Deadline Pressure Control (2002) (0)
- Competitive Product Engineering: 10 Powerful Principles for Winning Product Leadership, Through Advanced Systems Engineering, Compared to 10 Failure Paths Still Popular in Current Culture (2005) (0)
- Optimizing Systems Engineering Specification Quality Control Processes (1999) (0)
- Meet Tom Gilb (2012) (0)
- 9.1.6 Ten Powerful Principles for Quality in Systems Engineering and Software (2002) (0)
- 10.5.0 Panel 10.5.0: Cultural, Psychological and Motivational Factors in Risk Management: “Major Issues” or “Let's Not Go There” (2007) (0)
- Competitive Systems Engineering: How to Do Systems Engineering in Hot Competition. Detailed Pragmatic and Unconventional Techniques (2008) (0)
- Testing It: Confirmit (2010) (0)
- Design Ideas and Design Engineering (2005) (0)
- KR11 Virtual Team Communication (2008) (0)
- Agile Testing: From Waterfall to Evolutionary Development and Test (2009) (0)
- Planguage Basics and Process Control: The Purpose of Planguage (2005) (0)
- Point/Counterpoint (2008) (0)
- Competitive Engineering: A Totally Metrics-Based System-Development Method (2004) (0)
- A Conceptual Glossary for Systems Engineering: Define the Concept, don't quibble about the terms. (2007) (0)
- Specification Quality Control (2005) (0)
- 4.7.1 How to Quantify Quality: Finding Scales of Measure (2003) (0)
- 6.2.1 The Ten Most Powerful Principles for Quality in Systems Engineering and Software (2003) (0)
- Maintaining software systems (1984) (0)
- KR18 Decomposition of Projects: How to Design Small Incremental Steps (2008) (0)
- Design Evaluation: Estimating Multiple Critical Performance and Cost Impacts of Designs (2005) (0)
- SUMMARY OF THE ANALYSES OF THE PROJECTS (2012) (0)
- Estimating Software Attributes Some Unconventional Points of View (1987) (0)
- Functions: What systems ‘do’ (2005) (0)
- Resources, Budgets and Costs: Costs of Solutions (2005) (0)
- 8.5.3 Rule‐Based Design Reviews (2004) (0)
- Quantifying the Unquantified (2004) (0)
- 3.7.2 Exploiting Inspection: Some New Practices and Some Reminders (2003) (0)
- Agile Testing: EVERYONE IS DIFFERENT: AGILE CASE STUDIES (2009) (0)
- 8.1.1 The Use of Planguage to Improve Requirement Specifications (2004) (0)
- 4.1.1 Ten Design Principles: Some implications for multidimensional quantification of design impacts on requirements (2006) (0)
- 11.3.1 How Good Is A Process? Evaluating Engineering Processes' Efficiency (2006) (0)
- Scalable Requirements: One Size Can Fit All (2021) (0)
- Introduction to Requirements: Why? (2005) (0)
- 10.3 Architecture: A View Based on Multiple Impacts (2004) (0)
- 4.4.4 Systems Architecture: A View Based on Multiple Impacts (2007) (0)
This paper list is powered by the following services:
