27-08-2014, 03:33 PM
Why is WeFollow being created? I mean, do we really need Twitter inside organizations too? The use of social media technologies—such as blogs, wikis, social networking sites, social tagging, and microblogging—is proliferating at an incredible pace. One area of increasing adoption is organizational settings where managers hope that these new technologies will help improve important organizational processes. Apparently some do and are finding it extremely beneficial. In many organizations team wants and needs features that many social networks offer but needed them within a secure and private area. It is a tool built to essentially solve their own problem. You can quickly see updates from everyone, those you are following, or direct messages you have received or sent. From here you can post replies, view a thread, forward messages. In view of these benefits and a discussion with my project guide produced enthusiastic response and I decided to take the challenge to develop this project.
WeFollow is a simple way for employees to connect and share by posting messages. As employee participation grows, WeFollow becomes a corporate social network, discussion board, and knowledge base all rolled into one easy-to-use interface. See what colleagues are working on such as Share news, documents, links, images, files. Ask a question and get quick answers. Start a discussion and solicit ideas. Form private or public groups within the company. Search for co-workers, content, expertise in your organization
Objectives:
· WeFollow is a simple way for employees to connect and share by posting messages. As employee participation grows.
· WeFollow becomes a corporate social network, discussion board, and knowledge base all rolled into one easy-to-use interface.
· It acts like a huge database where you can find whatever web link that you want.
· Short status updates keep employees constantly aware of what their colleagues are working on.
· Each employee has a WeFollow profile displaying their photo, title, expertise and background. Only employees with a valid company email address can participate in your private company network. You can get the option to filter the most interesting links that will be sent to you directly.
· Use WeFollow to share news, questions, links, opinions, and information within your private company network.
· Search for any topic to see who.s talking about it and what.s been said. Great for getting new employees up to speed.
.
Methodologies to be Used:-
Prototyping Model has been used for software development according to which a throwaway prototype of the proposed system, based on the currently known requirements, is given to the user so that he has a fair idea about how the proposed system is going to be like. This will help him in deciding the interface, input and output requirements.
It can be easily adjudged that inputs and outputs are big in number, can increase exponentially and may create a big chaos if not restricted properly. As the user spends some time on the prototype, he will become more precise about his own input and output requirements. This prototype will provide him with an environment analogous to the proposed system.s environment.
Because of object oriented support in .NET, various concepts (like reusability, polymorphism, isolation etc.) are already there but for the efficient management of system components, Component based Software Engineering will also be exercised which will help in a resultant library of components, the benefit of which will be reusability and fast development.
Because of lack of hierarchical structure in object oriented approach, there is no meaning of Bottom-up or Top-down testing. Testing will begin from the most rudimentary levels of the system and will move towards higher level components which will be based on design phase rather than coding phase. In little words, it can be said that .CLUSTER Testing. will be exercised to scrutinize all the parts and their associative functionality.
Hardware and Software Requirements:-
Project will be developed using ASP .NET 4.5. So most of requirements are based on Microsoft Environment. Like as Follows
· Server Hosting ASP.Net 4.5 application.
· Server or Windows 2000 Server with ASP.Net 4.5 and SQL Server 2008 support .
· Client machine accessing ASP.Net 4.5 application.
· Any machine that can access a webpage Development machine for ASP.Net 4.5 application
· Operating System: Windows
· Hardware: 160GB Hard Disk, 2GB RAM