This is my site for fun and work. I am Sander, a software architect.
Centrical is my playground. Blogs, news and resources are updated regularly.
My articles are published on Infoworld, AutomatiseringsGids and Emerce, too.
I gather worldwide news, whether it is about e-commerce or service oriented architectures.
My resume, the Web Unified Process and the general conditions are offered in several formats.
Some more information about me is shown here, like a resume, professional history and more.
Things I do are audits, architecture design and strategic advice.
Read the cases of customers like Akzo Nobel, Sanoma Publishers and VNU.
To contact Centrical, you could either use the contact information or fill out the contact form.
Past publications, sorted by date of publication, are shown in my archive.
A short overview on what this website has to offer is shown here.
For a legal disclaimer and privacy issues according to international laws, check out this chapter.
For access to the systems of Centrical, you could use this entry.
This is an rss feed for news only. After clicking, copy the URL into your feedreader.
Stuff that happens to me sometimes inspires me to write. It may be nonsense, though.
WUP (Web Unified Process) is a lightweight and agile development method for web projects.
This where I keep technical posts that might come in handy.
Roleplaying and modeling
You can capture end user requirements in many ways: use cases,
business rule definitions, user stories, feature definitions, shall
statements and personas, to name a few. Wait a minute. Personas?
In the latest Software Development Newsletter, Scott Ambler explains.
You’re probably familiar with actors. In use case modeling, they represent the roles that users, and even other systems, can take with respect to your system. Persona are a different ballgame. In the absence of real users to speak with, invent "persons" with according behaviour. They will be your onsite customers. Roleplaying galore! You could be Ross. Or even Frances.
Because they act as user stand-ins, helping to guide your decisions about functionality and design, personas are extremely useful in the absence of easy access to real users. Questions such as "How would Ross use this feature?" or "Would Frances even be interested in this?" can start great conversations within your team, forcing you to think the way that your users do. Personas are often used when building public-access Web-based software, such as the Amazon or eBay systems, as well as shrink-wrapped software; they’re one of the artifacts described in Microsoft’s Agile MSF process. In short, personas are a valuable component in your modeling technique toolkit.
Play on.
In the latest Software Development Newsletter, Scott Ambler explains.
You’re probably familiar with actors. In use case modeling, they represent the roles that users, and even other systems, can take with respect to your system. Persona are a different ballgame. In the absence of real users to speak with, invent "persons" with according behaviour. They will be your onsite customers. Roleplaying galore! You could be Ross. Or even Frances.
Because they act as user stand-ins, helping to guide your decisions about functionality and design, personas are extremely useful in the absence of easy access to real users. Questions such as "How would Ross use this feature?" or "Would Frances even be interested in this?" can start great conversations within your team, forcing you to think the way that your users do. Personas are often used when building public-access Web-based software, such as the Amazon or eBay systems, as well as shrink-wrapped software; they’re one of the artifacts described in Microsoft’s Agile MSF process. In short, personas are a valuable component in your modeling technique toolkit.
Play on.
Transform to PDF
Print this item-
Send to a friend
You are trying to view the newsticker in a browser that doesn't support it. I am sorry.
