WUP - Centrical

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.

Suggestions

The next set of suggestions makes using WUP a lot easier...

Don’t try to design the whole system in advance;
Try to think about scalability well in advance though;
During implementation, please keep on designing (creative, functional, technical);
Don’t try to keep the functional requirements fixed;
Let the functional decision maker choose the order in which use cases are implemented;
Don’t produce huge documents in analysis and development phase, save that for the post-deployment phase for documentation and evaluation purposes;
focus on communication;
produce only documents that are actually used;
take note carefully of the reports;
let every team member contribute in the creative process;
don’t build for tomorrow: building for today is hard as it is and maybe tomorrow doesn’t fit your expectations;
don’t build for yesterday but for the current standard, i.e. don’t let yourself get restricted by old versions of browsers that won’t exist anymore before you can say Netscape, unless the customer demands it.

Have fun!

You are trying to view the newsticker in a browser that doesn't support it. I am sorry.