Analyzer uses a database to write out results of a database audit. Really you are ‘the analyzer’ because the tool extract all the information and you have to work on it.
I have found in Lotus Sandbox a person who built useful views to use Analyzer. It helped me a lot because the default views of the analyzer template are not enough to come to a conclusion
Now I’m involved in a Project with a new Customer.
After the first meetings with them and after they receipt some minutes of the progress of the Project the client starts to be more confident with the state of the work.
Up to this moment everything right.
Last week we had a problem with the design of the production environment. There was something that made the system unstable. As usual, I tried to get the solution ASAP, reporting the client about the status of the emergency regularly…
Finally the problem was fixed and I only had to send 2 mails before fix the problem. I didn’t receive feedback so I waited till the weekly meeting.
During the weekly meeting we reviewed the mentioned issue and the different measures done to return to an stable state.
Well, so the client read the mails and waited for the weekly meeting to review the status of the system. There’s no rush with the communications. Of course they wait we fix the problem ASAP but, for them, it never mind to wait till the next scheduled meeting to review the status of the works.
I’m used to close the urgent issues with the feedback of the client ensuring that they agree with the work done, but this client is not going to take the trouble to mail me.
Delta uses this database for writing out difference reports between documents or design elements.
Today I have extracted some report with different options. It has helped me to compare code between different design elements.
The problem I see is that you cannot compare in an agent, for instance, which parts of the code are really different.
The ‘hide identical objects’ property avoids the presence of garbage in the report.
It’s useful but it could be more powerful.
We cannot forget usability when we think in solutions for users. This sensitivity must be present even in all things that we do.
I have read some of these articles
that remember us the basic rules of this important aspect of a successful project.
IBM has published a new product, many eyes, that tries to enter new concepts mixing Social Networking with graphic data procesing.
A collection of publicly shared data sets held on the site. All these visualizations are commented as a blog Entry or a forum, you can rate them…
One of the most exciting features is the ability to create your visualization from any of the data sets on the site or your own data set.
The idea tries you to build differents points of view and compound different analysis around a data set.