use cases
Articles
 |
Who’s Using Your App? Examine Logs for Testing Insight When testing an application, have you ever thought to yourself, "I wonder who uses this"? Examining the app's logs can give you some idea. Logs are helpful for testers because they provide real feedback and insight into an application as it’s being used, as well as information that describes or can even help solve bugs. Here's how to use them to inform your testing. |
|
 |
Overcoming Cognitive Friction to Engineer Better Software The problems customers face are difficult to anticipate while developing software. However, looking at support issues can give a clearer idea about how to look for defects in the future. Sometimes users don’t know how to find certain information; other times, software doesn’t work as expected. In both cases, cognitive friction is at play. |
|
 |
Managing Acceptance Criteria Plans Some of the hardest and most crucial instances in any project execution are the user acceptance test phases. But having a thorough and clearly documented process for evaluating acceptance and exit criteria that you previously agreed on with the end-user will help you handle expectations and plan on results. |
|
 |
Designing Scenarios for Agile Stories The needs to improve the time to market of a quality product and adapt to a changing business environment are driving organizations to adopt agile practices in order to be competitive in the marketplace. However, a project team is bound to face difficulties if it is not trained on the fundamentals of agile. Read on to learn how to design scenarios for agile stories using a structured framework. |
Better Software Magazine Articles
 |
How Do You Write Good User Stories? Expert answers to frequently asked questions. In this issue, David Hussman explains how to write good user stories. |
|
 |
Building a Foundation for Structured Requirements: Aspect-Oriented Requirements Engineering Explained (Part 2) Aspect-oriented requirements engineering (AORE) is a new methodology that can help us to further improve the analysis, structure, and cost of development of software requirements. The second part of this two-part series focuses on the AORE specification techniques. |
Yuri Chernak
February 26, 2009 |
 |
Building a Foundation for Structured Requirements: Aspect-Oriented Engineering Explained (Part 1) Aspect-oriented requirements engineering (AORE) is a new methodology that can help us improve the analysis, structure, and cost of development of software requirements. AORE does not replace but rather complements any of the existing requirements methodologies. This two-part paper explains to software practitioners the AORE concept, illustrates how it can be applied on software projects, and discusses the benefits of AORE. Part I focuses on the AORE analysis techniques. |
Yuri Chernak
December 30, 2008 |
 |
Form Fitting: Patterns to Judge the Effectiveness of Use Cases You don't have to be Giorgio Armani to fashion effective use cases. Use case patterns can provide you with a vocabulary to help you describe and judge the quality of your use cases. Find out how you can use these patterns to improve your requirements modelin |
Steve Adolph
April 14, 2005 |
Interviews
 |
The "Show Me the Money" Approach to Software Development: An Interview with Michael Harris
Podcast
In this interview, Michael Harris, the president and CEO of David Consulting Group, explains his five-step Value Visualization Framework. He discusses how he came up with the idea, how it can help your team right now, and its similarities to the agile methodology. |
|
 |
Designing for Engagement: An Interview with Jaimee Newberry
Podcast
In this interivew, UX coach Jaimee Newberry talks about how to create a more engaging product for your users. She explains why it's so important to connect with customers on an emotional level, as well as how empathy and tone can change how a developer creates software. |
Conference Presentations
 |
By the Reader, for the Reader: The Wall Street Journal’s Secrets to Customer-Centric Experiences
Slideshow
Readers of The Wall Street Journal have seen many stories about companies shutting their doors after years of success. |
Sumeet Mandloi
|
 |
Behavior-Driven Development: Real-World Mind Reading
Slideshow
Imagine this scenario: Business users are excited to finally get their hands on an implementation delivery that is on schedule, (mostly) on budget, and passed rigorous testing with flying colors. Unfortunately, when working with the new app or feature, the users realize that the way they described their needs didn’t translate into what they actually needed. Sound familiar? While she may not be able to offer telekinetic mind-reading tools, Kim Tatum is convinced that leveraging a behavior-driven development (BDD) approach helps bridge the gap between domain experts and technical teams. Join Kim to discuss how natural, human-readable language ultimately creates shared accountability and reduces misunderstandings. Review how this framework is implemented on a variety of delivery projects and walk through an implementation approach and leading practices. |
Kim Tatum
|
 |
Rightsizing User Stories
Slideshow
User stories and their big brothers, epics, are an excellent way to describe requirements for a software system. They act as stakes in the ground to keep track of what the system needs to do, the type of user most interested in each feature, and the reason the requirement... |
Dave Todaro
|
 |
When User Stories Are Not Enough
Slideshow
IT organizations adopting agile development often struggle when applying agile to anything other than small, mid-sized, or non-critical applications. Because IT organizations must deal with the myriad business rules, non-functional requirements, industry regulations, and associated audits... |
Tony Higgins
|
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.