Fear began to unfold as Google launched yet another web clean-up update; formally named as the Penguin update. With all new algorithms and stringent methods for penalizing the web spam, Penguin upd...

This system will provide scientists, engaged life science practices, with online tools that will increase their productivity. The best way to achieve this is by providing such tools on a social networking platform.
This platform will enable them to collaborate with other scientists, manage shared laboratory equipment, order supplies, and archive lab results and documents.
The project is centered on organizing the laboratory. The site will help lab scientists to manage their colleagues and friends in groups and can share their reagent, protocol and facility details accordingly. A Timer will help them set audio or visual alarms or a text message.
From the Reagent section they can upload their reagent inventory online, network their inventory with colleagues, place orders for reagents and read member comments.
Protocols should be fully integrated with the reagent inventory, and helps members to organize and network their protocols with their labmates. Facilities should help labs administer shared facilities, such as microscopes and FACS machines. Timer should make it easy to time member's experiments without carrying around a bulky timer.
Along with this, members can also set their profile and share their academic pursuits, publications, with the community. Other scientists can benefit from their expertise and experience.
Members can search other members from their profile details and can visit their profile. They can manage their colleagues and friends from the network section. They can add new members to their group as well.
Members can communicate with others from message center with its sub sections. It is divided into different categories according to message. They can set their account related details and other preferences from account settings section.
Team faced the following challenges while project development:
| PHP (Server-side Language) | A suitable managed code development environment for handling the extensive project. |
| Red hat Linux | Sturdy and stable operating system with high level functionalities for online development. |
| MySQL Engine | Versatile, low-maintenance database management system. Cross-platform compatible database component of the LAMP platform. |
| Microsoft Visio | Integrated tool best suited for modular architecture and iterative development of software. |
| Zend Studio | Versatile web development tool with exhaustive support for CSS, JavaScript, and various server-side scripting frameworks. |
| Subversion (SVN) | Ideal application providing stratified storage and back up of code files. |
| Symfony Framework | Symfony is a full-stack framework, a library of cohesive classes written in PHP. |
| Project Leader | 1 |
| Developers | 4 |
| Designers | 2 |
| Quality Assurance Testers | 1 |
The following four-tier development approach was adopted to equip the site with numerous features and functionality mentioned before:
N-tier architecture was adopted to efficiently meet the needs of the enormous website. Following are the layers involved which are loosely coupled with each other:
User Interface Layer: This will include the page level layer which will be accessing the other layers beneath to present the data.
Business Specific Layer:This acts as a bridge between the User Interface layer and database layer. This will contain all the business logic for the different components involved in the project.
Database Specific Layer:This acts as a bridge between the physical database and the business logic accessing the data.
Physical Database Layer:This includes My SQL with the tables, views and stored procedures etc.
The design approach was built around PHP 5 and MySQL SERVER 5 due to the social networking nature of the website. Modules like User Profiles, Reagents, Protocols and Facilities were developed in PHP such that they can be executed directly from the UI layer. In order to most effectively access the database in an object-oriented context, an interface translating the object logic to the relational logic was used to communicate with the relational databases in an object-oriented manner. An intermediary abstraction layer was created for accessing data from the database. Triggers were used only for complex update and deletion of data from multiple tables and were entirely avoided with conditional syntax to ensure smooth performance of the website. The UI layer was kept free of any business logic with images, applications and data being called from their respective servers. Web usability guidelines were strictly followed during development and the interface was made easily navigable through judicious use of AJAX, CSS and HTML controls. The site was developed and fully functional within a span of 8 months.