join at : http://www.causes.com/causes/559679-be-a-veggie-stop-eating-non-veg
Stop feeding on flesh of other animals. Show some love towards nature, just by joining this cause and leaving non-veg.
Non veg food has many deficiencies and it is advisable to be aware of them. The Non veg food is devoid of Fiber and roughage and many vitamins like B complex and C. Not only this it is high on cholesterol and the canned meat may contain high amount of preservatives.(~Dr.Ashish Jain)
There is a wide debate as to whether it is better to be a vegetarian or a non-vegetarian. People in either camp have pretty much dug their heels in swearing by the benefits of being a vegetarian or a non-vegetarian respectively. There is, however, a worldwide trend of more and more people crossing over and becoming vegetarians. In this article we explore the issue from a spiritual perspective.
(http://www.spiritualresearchfoundatio... )
In this article on Sattva, Raja and Tama, the three subtle components of the universe, it is explained how everything in the universe at a subtle level is made up of these three subtle components, including food.
"Nothing will benefit human health and increase chances for survival of life on Earth as much as the evolution to a vegetarian diet."
- Albert Einstein
Eating diets containing sufficient amounts of fruits and vegetables can help lower your risk of heart diseases and type 2 diabetes. Doing this may also protect against some cancers and decrease bone loss. Also, getting potassium (plentiful in both fruits and vegetables) will help prevent the forming of kidney stones.
(Taken from www.wikipedia.com)
Monday, March 7, 2011
Tuesday, July 6, 2010
How to make your weekends productive.
Really simple and nice way to be productive.
I am already following this, and yes, it works. It allows me to complete more tasks, and make my weekends more productive then ever.
As a software engineer, I have fixed office hours for 5 days of week, and on weekends I like to complete many other non-official works. For the whole week, we keep thinking to do certain things on the weekend, but by the time weekends, those things are also gone. This keeps us postponing things for several weeks.
Then I started writing the important tasks on a to-do-list for weekends. On Friday night, i look at the list again, and plan for the things that I want to do next morning. By this, I can finish up most (or at least the important ones) on Saturday itself, and can take out a happy and satisfied Sunday for my family also.
It really works well !!
Saturday, March 14, 2009
Change Request Management System
eChaRMS, an acronym for "Enterprise Rent-A-Car company's Change Request Management System", was first suggested by Mizz Funmi Fakeye, during her MS in Business Information System, from Royal Holloway, University of London.
This project was developed as the major project in fulfillment of the above mentioned MS degree. A team of 8 students (all for the course MS in BIS ) worked with IT Department of Enterprise Rent A Car, Surrey Branch, with the help and support of Mr Hunjan, IS Application Manager of the company. More details about this are available on http://personal.rhul.ac.uk/mttm/066/eChaRMS/homepage.html
The purpose of this project is to address the problem that the IT department of Enterprise rent-a-car is facing- tracking and managing the IT Requests, which includes bugs in IT systems and other IT related issues. eChaRMS will allow all users with a valid username and password, to submit requests; authorized users called approvers (usually departmental managers) to authorize requests; and the IT department to assign and work on the approved requests. eChaRMS provides a means for more reliable, timely and easily accessible information for the IT department.
This project was developed as the major project in fulfillment of the above mentioned MS degree. A team of 8 students (all for the course MS in BIS ) worked with IT Department of Enterprise Rent A Car, Surrey Branch, with the help and support of Mr Hunjan, IS Application Manager of the company. More details about this are available on http://personal.rhul.ac.uk/mttm/066/eChaRMS/homepage.html
The purpose of this project is to address the problem that the IT department of Enterprise rent-a-car is facing- tracking and managing the IT Requests, which includes bugs in IT systems and other IT related issues. eChaRMS will allow all users with a valid username and password, to submit requests; authorized users called approvers (usually departmental managers) to authorize requests; and the IT department to assign and work on the approved requests. eChaRMS provides a means for more reliable, timely and easily accessible information for the IT department.
eChaRMS is an easily modifiable and extensible working model of the proposed system, which we hope will be carried out by Enterprise rent-a-car. Our objective is that the company will to evolve the prototype into the fully working system.
Currently, a modified version of this project is running live in the Enterprise Rent A Car, providing all the benefits of centralized repository of data, quicker access, and immediate decision making capabilities to its users.
For more details on this project, and its developers, please visit http://personal.rhul.ac.uk/mttm/066/eChaRMS/homepage.html
Friday, February 6, 2009
The Agile Process
Agile Software Development Process is a collection of various software development processes, having similar working principles. This process provides an excellent channel of communication between clients and the developers, resulting into clear understanding of goals, excellent feedback process, and accurate output. [wiki, 2009]
In this process, the work is done in small incremental blocks, with a minimum need of planning. Each small iteration, around 1-4 weeks, has its software development life cycle of planning, analysis, designing, coding and unit testing. At the end of each iteration, we get some working product (but not ready for market release) to show to the client. In this way, client is well aware of what and how things are going in the project, and he can give regular feedback. It reduces overall risk of failure, and also allows adjustment of frequently changing requirements, which is most common cause of disaster in software projects.
Beginning the project: After the initial meeting with client, the project is analyzed by the business heads, and then passed on to the working team members to review. The project Manager divides the whole work into smaller chunks, called story, having separate functionality.
For example, for a simple 'Inventory Management System' the various smaller chunks, or stories could be adding new item to inventory, searching for an item, listing the items n some order or printing reports out of the system.
Project Proceedings: It usually does not include long term planning, but only short modules (called sprints) of work are decided with strict deadlines. Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of each sprint, some deliverable are produced, and customer feedback is sought for them. Any suggestion or changes advised by client can be incorporated in the next sprint, without any serious burden of re-work, minimizing the overall risk of project failure.
Project Completion: Nearing the completion, project will already been reviewed by the customers many times, preventing hm for unusual surprises at the end. This is also followed by a complete set of documents for each and every small module(sprint), allowing hm to analyze in detail the bottlenecks, or scope of improvements.
Thus, agile methodology could provide a win-win situation to both the client, and the project manager, providing a smooth methodology for project development.
References:
Wikipedia 2009, adapted from 'http://en.wikipedia.org/wiki/Agile_software_development' on 6th Feb, 2009.
In this process, the work is done in small incremental blocks, with a minimum need of planning. Each small iteration, around 1-4 weeks, has its software development life cycle of planning, analysis, designing, coding and unit testing. At the end of each iteration, we get some working product (but not ready for market release) to show to the client. In this way, client is well aware of what and how things are going in the project, and he can give regular feedback. It reduces overall risk of failure, and also allows adjustment of frequently changing requirements, which is most common cause of disaster in software projects.
Beginning the project: After the initial meeting with client, the project is analyzed by the business heads, and then passed on to the working team members to review. The project Manager divides the whole work into smaller chunks, called story, having separate functionality.
For example, for a simple 'Inventory Management System' the various smaller chunks, or stories could be adding new item to inventory, searching for an item, listing the items n some order or printing reports out of the system.
Project Proceedings: It usually does not include long term planning, but only short modules (called sprints) of work are decided with strict deadlines. Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of each sprint, some deliverable are produced, and customer feedback is sought for them. Any suggestion or changes advised by client can be incorporated in the next sprint, without any serious burden of re-work, minimizing the overall risk of project failure.
Project Completion: Nearing the completion, project will already been reviewed by the customers many times, preventing hm for unusual surprises at the end. This is also followed by a complete set of documents for each and every small module(sprint), allowing hm to analyze in detail the bottlenecks, or scope of improvements.
Thus, agile methodology could provide a win-win situation to both the client, and the project manager, providing a smooth methodology for project development.
References:
Wikipedia 2009, adapted from 'http://en.wikipedia.org/wiki/Agile_software_development' on 6th Feb, 2009.
Subscribe to:
Posts (Atom)