Tom Gilb

Orcid: 0000-0001-6047-5735

According to our database1, Tom Gilb authored at least 32 papers between 1978 and 2024.

Collaborative distances:
  • Dijkstra number2 of four.
  • Erdős number3 of four.

Timeline

Legend:

Book 
In proceedings 
Article 
PhD thesis 
Dataset
Other 

Links

Online presence:

On csauthors.net:

Bibliography

2024
A Typology of Knowledge Creation in Design Science Research Projects.
Proceedings of the Design Science Research for a Resilient Future, 2024

2021
Scalable Requirements: One Size Can Fit All.
IEEE Softw., 2021

2010
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.
J. Softw. Eng. Appl., 2010

2008
Point/Counterpoint.
IEEE Softw., 2008

2007
No cure no pay: How to contract for software services.
Comput. Sci. Inf. Syst., 2007

2006
How to quantify quality: Finding scales of measure.
Proceedings of the ICSOFT 2006, 2006

2005
Design Evaluation: Estimating Multiple Critical Performance and Cost Impacts of Designs.
Proceedings of the Computer Safety, 2005

Competitive Product Engineering: 10 Powerful Principles for Winning Product Leadership, Through Advanced Systems Engineering, Compared to 10 Failure Paths Still Popular in Current Culture.
Proceedings of the Product Focused Software Process Improvement, 2005

2004
Quantifying the Unquantified.
Proceedings of the Software Audit and Metrics, 2004

Project Failures: Continuing Challenges for Sustainable Information Systems.
Proceedings of the Enterprise Information Systems VI, 2004

Evolutionary Project Management: Multiple Performance, Quality and Cost Metrics for Early and Continuous Stakeholder Value Delivery - An agile approach.
Proceedings of the Enterprise Information Systems VI, 2004

Competitive Engineering: A Totally Metrics-Based System-Development Method.
Proceedings of the ICEIS 2004, 2004

Evolutionary Project Management: Multiple Performance, Quality and Cost Metrics for Early and Continuous Stakeholder Value Delivery.
Proceedings of the ICEIS 2004, 2004

2000
The Ten Most Powerful Principles for Quality in (Software and) Software Organizations for Dependable Systems.
Proceedings of the Computer Safety, 2000

1998
Can Internet-Based Applications Be Engineered?
IEEE Softw., 1998

1997
Towards the engineering of Requirements.
Requir. Eng., 1997

1996
Level 6: Why We Can't Get There from Here.
IEEE Softw., 1996

1993
Practical Purposeful Creativity Constructs.
AI Soc., 1993

1989
A Planning Language (a PLanguage).
Proceedings of the Conference Proceedings on APL as a Tool of Thought, 1989

1988
The pre-natal death of the CIS project: A software disaster story.
J. Syst. Softw., 1988

Principles of software engineering management.
Addison-Wesley, ISBN: 978-0-201-19246-9, 1988

1987
Design by objectives.
ACM SIGSOFT Softw. Eng. Notes, 1987

1986
Estimating software attributes: some unconventional points of view.
ACM SIGSOFT Softw. Eng. Notes, 1986

Software specification and design must "Engineer" quality and cost iteratively.
ACM SIGSOFT Softw. Eng. Notes, 1986

Deadline Pressure: How to Cope with Short Deadlines, Low Budgets and Insufficient Staffing Levels.
Proceedings of the Information Processing 86, 1986

1985
Evolutionary Delivery versus the "waterfall model".
ACM SIGSOFT Softw. Eng. Notes, 1985

1984
Software engineering: using "design by objectives" tools (DBO).
ACM SIGSOFT Softw. Eng. Notes, 1984

1981
System attribute specification: a cornerstone of software engineering.
ACM SIGSOFT Softw. Eng. Notes, 1981

Evolutionary development.
ACM SIGSOFT Softw. Eng. Notes, 1981

1980
The "Design by Objectives" Method for Controlling Maintainability: A Quantitative Approach for Software.
Proceedings of the Programmiersprachen und Programmentwicklung, 1980

1979
A comment on "the definition of maintainability".
ACM SIGSOFT Softw. Eng. Notes, 1979

1978
Multidimensional quantified goals should direct software design processes.
ACM SIGSOFT Softw. Eng. Notes, 1978


  Loading...