The 4 Pegs of Software Requirements Engineering

Bad software requirements can jeopardize projects. There is a considerable literature on software requirements, but practice is far behind: what passes for requirements in industry usually consists of a few use cases or user stories, which are useful but not sufficient for a solution. Can we fix requirements engineering (known in other circles as business analysis) so that it is no longer the weak link in software engineering?

This video presents ongoing work intended to help industry produce more useful requirements. It includes precise definitions of software requirements concepts and a standard plan for requirements specifications, intended to replace the venerable but woefully obsolete IEEE standard from 1998. The plan contains four books covering the four “PEGS” of requirements engineering. The approach builds on existing knowledge to define a practical basis for software requirements engineering and provide projects with precise and helpful guidelines.

Video producer: https://www.acm.org/

Videos

Design Thinking Activities

This video explains that the six stages of the design thinking process can be supported by a very wide range of UX methods and activities. Don’t limit yourself to the most commonly mentioned methods.

Read More
Videos

Wardley Maps: Business Analysis, Experimentation & Evolution

This presentation explains how Wardley Maps were used to inform the always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more.

Read More
Videos

Analytics vs. Quantitative Usability Testing

Analytics and Quantitative Usability Testing UX research techniques help you gain quantitative insight into user behavior. However, each method provides different types of information and can answer different kinds of research questions.

Read More

Copyright © 2009-2021 Martinig & Associates