From start to end
A quest to understand things big and small... or how to survive as a Business Analyst and beyond.
Non-functional requirements: Logging
›
Understanding what activities are processed through a system is critical to knowing whether it is behaving as expected and central to diagno...
Non-functional requirements: Error Handling
›
How should a system handle the unexpected? This is a fundamental consideration of any solution. Key points to keep in mind are: What are the...
Non-functional requirements: Data Retention
›
Data retention refers to the storage of a system's information for a specified period of time. This information should be examined accor...
Non-functional requirements: Security
›
One of the most important non-functional requirements is security. Security requirements can come in many different forms: Privacy - Require...
2 comments:
Extreme availability & reliability test
›
Earlier in the week, I wrote about Availability and Reliability . Yesterday on Digg.com there was an interesting post showing an HP Storage...
Non-functional requirements: Data Currency & Internationalization
›
This is my third post on non-functional requirements. Let me reiterate that non-functional requirements describe characteristics of a system...
Non-functional requirements: Disaster Recovery
›
One thing that was implied in my previous post, Availability & Capacity , was that higher levels of reliability are costly. Costly becau...
Non-functional requirements: Availability & Capacity
›
I've spent a bit of time writing on basic presentation , communication and innovation themes. Now I'm going to refocus and go into...
2 comments:
Big and small
›
Innovations can come in all sizes: big or small. Look at the little innovation square from my post, Types of innovation . They don't hav...
1 comment:
Questions lead to innovation
›
By nature, people do not like change. They develop comfort with routine, regardless of whether it makes sense or not. It's some sort of ...
‹
›
Home
View web version