Non-Functional Requirements

Non-Functional Requirements

https://www.julianbrowne.com/article/nfrs/ · August 1, 2007

Hold on a tick

Hold on a tick People like their systems to be fast. It’s because we hate to wait. In software sometimes there are delays, but they don’t have to be annoying.

https://www.julianbrowne.com/article/hold-on-a-tick/ · July 18, 2007

Megaprojects

Megaprojects Don’t get seduced. When it comes to projects, big is most certainly not better. It’s a recipe for disaster.

https://www.julianbrowne.com/article/megaprojects/ · July 4, 2007

Interface Catalogue

Interface Catalogue A template for capturing interfaces between applications on a project. Quite simple, but very effective for planning and communication.

https://www.julianbrowne.com/article/interface-catalogue/ · July 1, 2007

Amdahls Law

Amdahls Law A simple calculator to explore the implications of Amdahl’s Law on business processes.

https://www.julianbrowne.com/article/amdahls-law/ · June 28, 2007

Space-based Archetypes

Space-based Archetypes The third of three articles on the space-based architecture. This one looks at how the patterns of SBA deployment naturally lend themselves to supporting systemic requirements.

https://www.julianbrowne.com/article/space-based-archetypes/ · June 27, 2007

Space-based Agility

Space-based Agility The second of three articles on spaced-based architecture. This one explains why using SBA can make you more agile.

https://www.julianbrowne.com/article/space-based-agility/ · June 25, 2007

Space-based Architecture

Space-based Architecture The first of three articles on the space-based architecture. This one describes what the SBA approach is all about.

https://www.julianbrowne.com/article/space-based-architecture-example/ · June 6, 2007

The Little Language

The Little Language A short word about domain specific languages and why they might hold much promise for software development, business relations, and effective reuse.

https://www.julianbrowne.com/article/the-little-language/ · May 28, 2007

Doing it right can mean doing it wrong

Doing it right can mean doing it wrong It’s really easy to get so hung up on principles like DRY, YAGNI, KISS, etc that we can’t even write a line of code for fear that it might be picked apart by the purists. Relax. Sometimes you should write poorly structured code to see where your going, as long as you track it and can fix it later.

https://www.julianbrowne.com/article/doing-it-right-doing-it-wrong/ · May 23, 2007