Skip to main content

Are Requirements for Web Applications Obsolete?

In a comment on the Requirements Defined blog, curious jim wrote:
How much is useful for defining requirements for web apps development? Simulation or prototyping seems the efficient approach. Software by iRise and Simunication allows build of real simulations of web apps to identify requirements (the latter even hosts online build) so much of the discussion seems a bit dated for this sector.
Asking whether it is useful to define requirements for web app development is equivalent to asking,
Is it useful to understand the problem a web application is supposed to solve?
A requirement is a statement of the least stringent conditions that must hold to solve or avoid a prospect problem. As such, it is nothing more than a logical transposition of a problem statement.

Does the fact that a product or system is a web application mean that understanding the problem it solves is "dated" and not useful? Curious, indeed.


Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware