Browse by Tags

Designing an Authentication and Authorization Strategy
What are the key steps to designing an effective authentication and authorization strategy? The keys are knowing your user stores, role stores, and who need to access what or perform which operations. In this post, I share the approaches we've used in Read More...
Posted 25 June 08 07:35 by J.D. Meier | 3 Comments   
Filed under ,
Security Principles
If you know the underlying principles for security, you can be more effective in your security design.  While working on Improving Web Application Security: Threats and Countermeasures , my team focused on creating a durable set of security principles.  Read More...
Four Stages of Market Maturity
You can tell the maturity of a market by the consumer patterns. If you know the life cycle stages of a market you can better anticipate what level of "needs" your product needs to match to be successful. (I always think of needs in stages like Maslow's Read More...
Kano, Satisfiers, and Dissatisfiers
If you're looking for yet another way to help you prioritize your backlog or to help you shape your product's design, consider the Kano model . One concept in the Kano model is satisfiers and dissatisfiers. You can think of satisfiers as features you Read More...
Human Shepherds and the Law of Relevancy
Yesterday, Ed helped me word a "law" that I use for important decisions and that I see show up quite a bit in a number of places. It's the law of human relevancy. The Law of Relevancy No matter how relevant the information is, it's more relevant with Read More...
Scenarios in Practice
Scenarios are a practical way to organize and focus your product design, development and release. (We use scenario-driven engineering in patterns & practices) Key Benefits Business value . You can use scenarios to evaluate business value. What pain Read More...
Roles and Goals
The next time I need to get a set of requirements, I'm simply going to start with roles with goals. I made the mistake of asking for a set of scenarios. What I ended up with is a list of user tasks. Tasks aren't the same as goals. Flying a kite is not Read More...
Requirements Perspectives
Here's a simple set of perspectives I use for rationalizing requirements: User Business Expert / Technical Industry/Standards Believe it or not, simply identifying these perspective helps a lot. You'd be surprised how many debates happen simply because Read More...
Scenario Frames for Guidance
When I tackle a problem domain, I first frame out the space. To do this, I list out scenarios and sub-scenarios. I group the scenarios under categories. Sometimes categories come first, sometimes scenarios do. I call the result, a Scenario Frame. I use Read More...
Task-Analysis Grid for Communicating Product Design
How do you communicate design decisions? … Srinath sent me a helpful link on the Task-Analysis Grid . A Task Analysis Grid is effectively columns of scenarios along with sub-tasks to complete the task. Here's the key points: The columns are organized Read More...
Actors, Personas, and Roles
In user modeling, I usually come across actors, personas, and roles (user roles). I thought it would be helpful to distinguish these so that I can use the right tool for the job, or at least understand their relationships, strengths and weaknesses. Summary Read More...
Personas at patterns and practices
At patterns & practices , we introduced personas a few years back to help design user experience for our deliverables. Personas helped with a few things: Understanding demographics. Building empathy by putting a face behind the user role. Building Read More...
Avoiding Do Overs - Testing Your Key Engineering Decisions
I noticed Rico has a Performance Problems Survey . From what I've seen, the most important problem is failure to test and explore key engineering decisions. By key engineering decisions, I mean the decisions that have cascading engineering impact. By Read More...
Idioms and Paradigms
John Socha-Leialoha wrote up a nice bit of insight on how Users are Idiomatic . John writes: "First, different users will have different definitions of "intuitive." ... Second, and this isn't conveyed directly by the definition of idiomatic, users actually Read More...
Posted 06 January 07 05:44 by J.D. Meier | 0 Comments   
Filed under
What's a Scenario
In general, "scenario" usually means a possible sequence of events. In the software industry, "scenario" usually means one of the following: 1. Same as a use case 2. Path through a use case 3. Instance of a use case #3 is generally preferred because it Read More...
More Posts Next page »

Search

Go

This Blog

Syndication

Page view tracker