Use Cases and Wireframes

An easier way to identify requirements for software systems I found to be these two essential techniques: use cases and wireframes.

When you write your functional requirements in use cases and visually model them in wireframes, you create the perfect combination to get your business stakeholders and technical implementers on the same page about the requirements.

Use cases are a type of requirements specification that captures exactly how a user will interact with a software system to achieve a specific goal.
  • Software developers find them easy to work from when designing and implementing code.
  • Testers love them as they provide exactly the information they need to create test cases.
  • Even more important, your business stakeholders will actually understand your software requirements if you document them in use cases.
Wireframes (also referred to as user interface prototypes or mock-ups) capture how the screens of the software system might look, and help provide visual context for software requirements.

Everyone loves a wireframe because they are able to see exactly what a software screen might look like, even before it’s implemented.

With a quickly created wireframe, you’ll clear up dozens of miscommunication issues before they even have the chance to plague your project.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s