Week9

7/Nov/2010

How to differentiate normal accountant and super accountant? Normal accountant can view only page group A but super accountant can view page group A and B. There are user roles there. One option is in master pages, checking sessions of user name and user type. Another option is using ASP.Net membership function. We never used it before so we need to research more. It means that we need time. Though we don't have enough time, it's still worth trying. See how it works. I am working on reporting function. Researched a lot but still cannot get good solution.


6/Nov/2010

Working on the final database structure.  More think, more confused. There is not one correct answer. But I want to know it! Anyway there are 34 tables in the database at the moment. And moved back to the client page. I need to design the create new client form. What will be the good solution? How should I display it? And I got another question. There are two different type of users in our client's page. One is normal accountant. Another one is super user or we could say system administrator user. The super user will assign the normal accountant to the particular client as to Mr. Client idea. So who will create clients? Only super users? It's not handy. We need to ask Mr.Client again.


5/Nov/2010


Reviewed yesterday's client meeting. By updating ERD, tried to make all thing clear.Some parts get more simple like Case page but some parts get more complexed like Event page. Also we need to think what will be the most appropriate database structure around client. Normalize? or De-normalize? Unfortunately it's my area to work on. Anyway we need to complete the database during this weekend.



4/Nov/2010


Ajax control toolkit is great and easy. Some of them are similar with jQuery but cording is not required for most of the controls. I try to keep study them. One big issue has solved. Logout function. What we needed was only three line of C# cording.
           Response.Cache.SetExpires(DateTime.UtcNow.AddMinutes(-1));
           Response.Cache.SetCacheability(HttpCacheability.NoCache);
           Response.Cache.SetNoStore();
Now our login function is really secured. We had forth and second client meeting. Forth with our client and second with Mr.Client. Actually it was very nice meeting ever. By demonstrating our prototype system, he could understand and imagine what exactly the system would be. He looked happy with our work and finally we could get his real requirement. However some functionalities are bit different from what he wants so we need to re-design the system and the database structure. And it seems he often use Microsoft Outlook so I better study it.


3/Nov/2010


I know it is not a good idea as a project manager not to update the Gantt chart for long time but I haven' t done that. Today finally I decided to update. Using weekly journal, I updated it day by day. I use MS Project but it has got too many functions so it's quite hard to manage it. This application is not for ease, for stress it seems. Anyway, now it's updated.


2/Nov/2010


I tried to solve something. My friend asked me something. I helped him/her. Looked on my monitor back and found "What am I doing?". There is always dilemma there. I am always happy to help friends. I can learn a lot of thing by teaching. On the other hand, I loose myself. Or I can say I have problem of my concentration. Anyway, I need to improve my part. By improving my page, I try to think how can I use Ajex technology on my page. What will be the industrial way? My team mate has been struggling how to code for perfect logout function. Browser's back button is problem. There are two ways. Allow back or not at all even during logging in. I asked my brother who works as a programmer in Japan. He replied me quickly. First we should disable cache on  the browser. And in every member page, needed to check session. So that during logging in, even browser hasn't cache, as long as having session available, it will regenerate page again as if it is back to the previous page. Logical. How to do that?



1/Nov/2010

I have been thinking how to solve the problem of the database. One client may have many contact channels and address. So we created individual table for both of them. Normalization. But, to think about inserting and retrieving the data, in cording point of view, it's not efficient enough at all. Suppose the client has three phone numbers and one fax number and two email addresses. To insert these data, I need to write same things again and again. After we discussed with our supervisor, we decided to de-normalize them. In database point of view, it may not good but we also need to care about the performance of the system.It was good to discuss. I again updated the data dictionary and the ERD. Time to code full function of the client pages.