Rakesh K

METHODS OF PROJECT ESTIMATIONS 1. POKER ESTIMATE Bring together a team of programmers and BAs, voice client's request for them, let each do own estimation quietly and then compare and discuss. Those who give the highest and lowest estimations provide arguments and the whole team should negotiate on the realistic and doable amount of man-hours to be sent to the prospect. 2. COMPARISON TO SIMILAR PROJECTS Here you need to compare the current project to the actually spent man-hours on a similar project in the past, but not to the initially estimated scope! There's also a complexity factor that should be defined and multiplied by man-hours planned. 3. BOTTOM UP & TOP DOWN Step one is to decompose your main task into several or many sub-tasks and estimate each separately. Then sum up the results to get a final estimate. Step two is to estimate the task as a whole. If discrepancy between bottom up and top down estimations is huge, you need to find a reason...

Both tools are powerful, fast, in-memory data stores that are useful as a cache. Both can help speed up your application by caching database results, HTML fragments, or anything else that might be expensive to generate. Points to Consider When used for the same thing, here is how they compare using the original question's "Points to Consider": Read/write speed : Both are extremely fast. Benchmarks vary by workload, versions, and many other factors but generally show redis to be as fast or almost as fast as memcached. I recommend redis, but not because memcached is slow. It's not. Memory usage : Redis is better. memcached: You specify the cache size and as you insert items the daemon quickly grows to a little more than this size. There is never really a way to reclaim any of that space, short of restarting memcached. All your keys could be expired, you could flush the database, and it would still use the full chunk of RAM you configured it with. redis: Se...

Phases within the ADM are as follows: The  Preliminary Phase  describes the preparation and initiation activities required to prepare to meet the business directive for a new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles. Phase A: Architecture Vision  describes the initial phase of an architecture development cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals. Phase B: Business Architecture  describes the development of a Business Architecture to support an agreed Architecture Vision. Phase C: Information Systems Architectures  describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures. Phase D: Technology Architecture  describes the development of t...