Robin F. Goldsmith, JD, has been president of Go Pro
Management Inc. consultancy since 1982. He works directly with and trains business and systems
professionals in requirements analysis, quality and testing, software acquisition, project
management and leadership, metrics, and process improvement. He partners with ProveIT.net in
providing ROI Value Modeling tools, training, and advisory services.
Previously he was a developer, systems programmer/DBA/QA, and project leader with the City of
Cleveland, leading financial institutions, and a "Big 4" consulting firm.
Author of numerous articles and the recent Artech House book Discovering REAL Business
Requirements for Software Project Success, and a frequent speaker at leading professional
conferences, Robin was formerly International Vice President of the Association for Systems
Management and Executive Editor of the Journal of Systems Management. He was founding
chairman of the New England Center for Organizational Effectiveness. He belongs to the Boston SPIN
and served on the SEPG'95 Planning and Program Committees.
Robin chaired BOSCON 2000 and 2001, ASQ Boston Section's Annual Quality Conferences, and he is a
member of the ASQ Software Division Methods Committee and the IEEE Software Test Documentation Std.
829 revision Committee. He is a subject expert for the International Institute of Business Analysis
(IIBA) Business Analysis Body of Knowledge (BABOK).
Robin holds the following degrees: Kenyon College, A.B. with Honors in Psychology; Pennsylvania
State University, M.S. in Psychology; Suffolk University, J.D.; Boston University, LL.M. in Tax
Law. He is also a member of the Massachusetts Bar and licensed to practice law in
Massachusetts.
Contributions from Robin F. Goldsmith
- Tools that generate test cases from software requirements
- Types of software requirements: Business, functional, stakeholder, and "real"
- Using a traceability matrix to map requirements to test cases
- What is a test case? What is a requirement?
- Four tips for gathering requirements for the new Business Analyst
- How to handle requirements creep
- How to settle conflicting software requirements between users and stakeholders
- Defining a User Interface (UI) during the requirements phase: A mistake?
- Requirements rethinking tutorial: Improving pre-development software analysis - Part 2
- Problem pyramid discovering REAL software requirements
- Reliably estimating the requirements effort - Part 2
- Reliably estimating the software requirements effort
- Functional vs non-functional requirements, what is the difference?
- Which requirements have the greatest effect on quality in software development?
- How to write an SRS document for three different databases
- How to write a Software Requirements Specification (SRS) document
- Problems caused by skipping analysis stage of SDLC
- How to improve software project requirements estimates tutorial
- Software development life cycle phases, iterations, explained step by step
- Waterfall versus iterative development misconceptions