Home | Login | Recent Changes | Search | All Pages | Help

SoftwareArchitects

Currently an area I'm trying to figure out. In terms of the text book stuff, not so difficult but in practical terms still struggling.

For example, how do you determine whether a product meets your NonFunctionalRequirements if you're only just beginning to understand what NonFunctionalRequirements are. Is part of the role of SoftwareArchitects to demonstrate product capabilities in the absence of stated NonFunctionalRequirements?

For a concrete example, I've just been asked to review an online certification application we're planning to use. Is it reasonable to ask the vendor to prove (or should that be proove?) how the application behaves under load? If they refuse, what do we do (other than offer no guarantees that it will, of course!).

2004.03.05 PhilStubbington

What's the question? What's the important guestion? What's the general question here? What kind of solution would satisfy you?

I'm asking those questions about your query Phil. I also believe those questions have a lot to do with "software architecture" the practice, distinct from "software architect" the title you give a fairly senior developer who wants to feel valued, whom you won't (usually wisely) promote into management.

-- JimBullock, 2004.03.08

I agree 100% - I (personally) don't give a monkeys for job titles - it's the practice that's important.

I guess the questions fall into two broad camps - one relating to determining if a COTS solution works in relation to NonFunctionalRequirements and the second (more interesting, IMHO) relates to how you ensure (at the outset, and as an ongoing process during the SoftwareLifeCycle that a product has the capabilities you require.

Since I wrote the above I've found a potential solution to many of my questions, courtesy of the SEI. Check out for more info.

2004.03.12 PhilStubbington