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.
Post-deployment phase
The post-deployment phase can include beta testing, performance tuning, maintenance and user training. All this depends heavily on the agreements that are made with the customer. Therefore, there are no standard procedures in WUP that describe what to do.
A couple of things have to be kept in mind, though. Be certain to define in detail which responsibilities the customer expects you to fulfill. Think about upgrades, maintenance, quality guarantees and so on. It is recommended to have direct access to the production server when you have to do stuff like this. Another useful rule is, that when the customer adjusts anything in the application himself (that is, or his developers), nothing can be guaranteed any longer.
A couple of things have to be kept in mind, though. Be certain to define in detail which responsibilities the customer expects you to fulfill. Think about upgrades, maintenance, quality guarantees and so on. It is recommended to have direct access to the production server when you have to do stuff like this. Another useful rule is, that when the customer adjusts anything in the application himself (that is, or his developers), nothing can be guaranteed any longer.
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.
