Search results

"tag:"nonfunctionalrequirements""


Title and summary Date/time
1
Software architecture is a platform for conversation
If you're writing software as a part of your day-to-day job, then it's likely that your software isn't going to live in isolation. We tend to feel safe in our little project teams, particularly when everybody knows each other and team spirits are high. ...
01-Dec-2009
22:03:13
2
A developer's guide to load testing - video
Just a quickie ... the video from A developer's guide to load testing at Skills Matter last week is now available to view online. The microphone picked up the questions and comments quite well, which is excellent. Enjoy, and feel free to use the Google ...
15-Jun-2009
23:27:51
3
A developer's guide to load testing - slides
Thanks to everybody that came along to the CTA user group earlier in the week. The tube strike may had reduced the numbers but we still had some great discussion about load testing. My slides are available to download (~4MB) and if anybody wants to ...
11-Jun-2009
19:40:49
4
A developer's guide to load testing
Here are the details of the June 2009 London User Group. Title : A developer's guide to load testing Summary : Load testing is an often forgotten and seemingly difficult task that many people shy away from doing. It doesn't have to be this way though, ...
02-Jun-2009
09:39:00
5
Who should own the non-functional tests?
This is a follow-up to a post entitled Performance tuning Java systems that I made last year, which talked about some performance testing that I was doing for a customer. Last week, I went back to the same customer to make some small tweaks to the test ...
07-Jul-2008
11:03:00
6
NFRs for system replacements
As software architects, we tend to write about non-functional requirements a lot; particularly about how they should be defined and challenged because of the influence they have. One of the reasons for talking about NFRs a lot is that, in the majority, ...
28-May-2008
11:35:00
7
Scalability Principles
At the simplest level, scalability is about doing more of something. This could be responding to more user requests, executing more work or handling more data. While designing software has its complexities, making that software capable of doing lots of ...
21-May-2008
14:12:25
8
Architectural Assumptions
Most of the systems I've worked on in the recent past have been latency rather than throughput orientated. However my current project is definitely throughput focused and scales horizontally rather than vertically (this is a simplification but basically ...
24-Dec-2007
12:44:59
9
Monitoring Java systems
Earlier in the week I wrote about performance tuning Java systems and I hinted that being able to monitor a system is a really useful first step in proving and diagnosing the cause of performance issues. Of course, there are times where you need a ...
09-Nov-2007
11:18:45
10
Performance tuning Java systems
One of my current projects involves me performance testing a third party Java system. In essence, it's a distributed/n-tier Java EE web application and we're hitting it with a high simulated load thanks to Apache JMeter. One of the things we found is ...
05-Nov-2007
12:23:34
11
Separating the non-functionals
I was recently involved in a discussion where we were talking about the best way to increase the scalability of a software system, which is essentially a Java EE web application. The most obvious way to do this is to horizontally scale-out the ...
02-Oct-2007
12:07:00
12
Nines
I've been reviewing some software architecture documents as part of a training course today, where the authors had restated the non-functional requirements. Given that the non-functional requirements are some of the key architectural drivers, restating ...
26-Sep-2007
23:21:00
13
What about the application tier?!
I've recently become involved in a project with a very clear idea of its functional and data requirements - so much so that the presentation technology has been selected and the database vendor and schema determined. The suppliers of these have also been ...
24-Sep-2007
16:05:32
14
Engaging without non-functional requirements
In The influence of non-functional requirements, I wrote that putting together a ballpark cost for a software project is near impossible if you don't have any information about the non-functional requirements. Something I've witnessed recently is a ...
06-Sep-2007
20:22:00
15
The influence of non-functional requirements
As technical people, it's really easy for us to think about software as a purely technical endeavour when we should always remember that software is really about solving business problems or providing some benefit to somebody. Over the past few years, ...
09-Jul-2007
14:11:00
16
Defining the non-functional requirements
First a quote from a recent comment. The architect might not be responsible for defining the non-functional requirements, but they're definitely responsible for fulfilling them. I agree, typically the architect will fulfil the requirements rather ...
13-Jun-2007
12:14:00
17
Code Metrics
There's nothing particularly new about code metrics but they perhaps have an increasing relevance as development teams become geographically and ideologically separated from those charged with code quality and an increasing degree of freedom is granted to ...
15-Dec-2006
13:40:00
18
Mastering the Requirements Process
I've just received a copy of Addison-Wesley's "Mastering the Requirements Process" 2nd Edition to review over the next few weeks. The blurb says: Mastering the Requirements Process, Second Edition, sets out an industry-proven process for gathering and ...
25-Apr-2006
21:19:20
19
Introducing Character Sets and Encodings
The W3C have just released a short article about internationalisation (i18n), called Introducing Character Sets and Encodings. One of the responsibilities associated with being a technical architect is to ensure that the non-functional requirements are ...
26-Jan-2006
10:33:59