Defect Tracking System - ASP.NET Project

DEFECT TRACKING SYSTEM

Development of a web based Defect Tracking System

• Title of the project: Defect Tracking System
• Domain: Software Industry
• Sub Domain:  Testing and Quality Division
• Project Architecture: N-Tire Architecture
• SDLC methodologies: Waterfall model
• Abstract of the project:

This project is aimed at developing an online defect tracking system useful for applications developed in an organization. The Defect Tracking System (DTS) is a web based application that can be accessed throughout the organization. This system can be used for logging defects against an application/module, assigning defects to individuals and tracking the defects to resolution. There are features like email notifications, user maintenance, user access control, report generators etc in this system.

The software is fully integrated with CRM (Customer Relationship Management) as well as CMS (Content Management System) solution and developed in a manner that is easily manageable, time saving and relieving one from manual works.

A: Following tasks can be performed with the application:

• User Maintenance
• Component Maintenance
• Defect Tracking
• Report

 

User Maintenance: Creating, Granting & Revoking access and deleting users from application.
Component Maintenance: Creating a component (application being developed/ enhanced), Granting & Revoking access on components to Users and Marking a component as “Active” or “Closed”.
Defect Tracking: Creating, Assigning defects to users, Modifying and Closing a defect. A defect screen should at least have following details

• Defect Id and Title
• Defect priority
• Date created
• Defect description
• Defect diagnosis
• Name of originator
• Status
• Resolution

Report: Generate reports on defects.

B: Following additional tasks also can be performed by this application:

• Find User
• Find component
• Find defect

 

Find User: A search screen to find users and display results.
Find component: A search screen to find components and display results.
Find defect: A search screen to find defects and display results.

 

7. EXISTING SYSTEM:

• Defect Tracking System is a web-based application designed to help a workgroup keep track of Defects and tasks via a shared central resource. The system was designed specifically with the IT department in mind, where quick access to shared data and history is a requirement, both from an internal organizational perspective, as well as to fulfill the needs of the customers.

 

• It provides one roof solution for all the Defects issues in the software development.  It doesn’t provide any kind of solution to any kind of problem. It only acts as a means to transmit the issues and their details to the concerned office personnel with accuracy. It is a tool that helps in providing the solution for the Employee request Log in right time.

• In addition to all these, it also maintains the preferences, customized settings, priorities, users, etc.  It is very critical to solve different kind of reports at a time in the existing system.  The IT departments have different Operational Administrators who were providing so many problems in each and every day. Tracking these defects is a tough job.

 

8. PROPOSED SYSTEM:

• The development of the new system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.
• User friendliness is provided in the application with various controls. The system makes the overall project much easier and flexible to the end user. It can also be deployed over the Internet. Various classes have been used to provide file upload and mail features. There is no risk of data mismanagement at any level while the project development is under process. It provides high level of security using different protocols like https etc. The system Interface provides good environment to solve any kind of defect.
• The system capture the overall details of any defect from this user interface and send it to the particular administrator. Every defect details must be stored in the centralized data base server which can be organized by the company.

 

9. MODULES:                                               
1) Administrator
2) Operational Administrator
3) Operator
4) Defect Tracking
5) Search
6) Reports
7) Registration and Authentication

 

10. Functionalities of the System:
1. A user should be able to:

• Login to the system through the first page of the application.
• Change the password after logging into system.
• View the defects assigned to the User.
• Find defects for components on which the user has access.
• Find components on which the user has access.
• Modify the defects by changing / putting values in fields.
• Assign defects to other users having access to the component.
• Find details of other Users.
• Generate reports of defects for components on which the user has access.

2. As soon as a defect is assigned to a user a mail should be send to the User.
3. The Application Admin should be able to do the following tasks

• Add a new component.
• Remove Component Admin privilege from a user.
• Add a new user.
• Remove a user.

11. Keywords:

• Generic Technology Keywords: Databases, User Interface, Programming
• Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server
• Project Type Keywords: Analysis, Design, Implementation, Testing
• SDLC Keywords: Presentation, Business Object, Data Access Layers

12. Environment:

• Servers:
• Operating System Server: - Microsoft Windows 2000 or Higher
• Data Base Server: Microsoft SQL Server 2000/2005
• Clients: Microsoft Internet Explorer,
• Tools: Microsoft Visual Studio .Net
• User Interface: ASP.NET with AJAX
• Code Behind: VC#.NET

13. Requirements:

• Hardware requirements:

Number	Description
1	PC with 2 GB hard-disk and 256 MB RAM

• Software requirements:

Number	Description
1	Windows 2000/ XP/ or Higher with MS-office
2.	MS-SQL server2000/2005
3.	Ms-Visual Studio .Net 2005
4.	Ms-Internet Explorer

 

14. Milestones:

No.	Milestone Name	Milestone Description	Remarks
1	Requirements Specification	Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made.	Attempt should be made to add some more relevant functionality other than those that are listed in this document.
2	Technology familiarization	Understanding of the technology needed to implement the project.	The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.
3	Database creation	A database of at least 10 entries of users with at least 1 should application admin.	It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.
4	High-level and Detailed  Design	Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario.	The scenarios should map to the requirement specification
5	Development of front end functionalities.	Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options	During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6	Integrating the front-end with the database	The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing.
7	Integration Testing	The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).	Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
8	Final Review	Issues found during the previous milestone are fixed and the system is ready for the final review.	During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

 

 

Defect Tracking System - Screens by finalyearprojects

Read More

Customer Query Tracker System - ASP.NET Project

Title of the Project	Customer Query Track
Software Requirements	Operating System Server: Windows XP or later Database Server: Microsoft SQL Server-2005 Client: Microsoft Internet Explorer Tools: Microsoft Visual Studio .Net-2008 User Interface: Asp.Net with Ajax Code Behind: C#.Net
Hardware Requirements	Processor: Intel Pentium or More Ram:  512 MB Ram Hard Disk: PC with 20GB

Abstract
This project is mainly used to track the queries of the customers in the organization and resolve the queries. This Project also sends the services to the customer to find out the customer satisfaction and employee performance.
The system has a major problem in finding the product support and service activities that are undertaken by the employees. Once the products have installed at the client’s site, the cycle of warranty maintenance starts. To keep the customers in a proper chain of satisfaction the system needs the data to be organized in a proper relational way.
The project is to maintain the relational communication among the project is to maintain this relational communication among the data, such that consistency, reliability and integrity can be achieved. The major technicality within the system lies in managing the coordination among the sales and service departments, which is the major hold upon the system to gain or achieve profits.
This project is been divided into two modules. These are:
1. Customer’s Module
2. Employee’s Module

Customer’s Module: The Customer’s Module is designed to provide the following services.
Posting a Query:

• Customers should be free to post their queries to the concern department.
• The system must identify each query with an automatically generated Query Id, for future references.

Survey Details:

• Customers should be able to post the survey details on a department by simply selecting the department and post the survey details to the organization.
• In survey details service the system provides the rate of satisfaction of the customer on a particular employee.
• The rate of satisfaction can be known by giving ratings to the employee.

Status

• Customers should be allowed to check the status of their query, by using the unique Query Id provided by the system.
• The system must display the answers along with the Query to the customer, after posting the query.

Employee’s Module: In this Employee’s Module we have two services, which are
Posted Queries:

• The employees should be able to see the posted queries, which are posted by the customers.
• An employee can visit the queries posted to that department only.
• The employee should post back the solution to the queries he has received.
• An employee cannot only see his rating but also rating of other employees who are working in other departments.

Survey:

• The employees should be able to see the survey details posted by the customers.
• He can able to see the survey details of all the departments.
• This system should also provide registration of new customers for the organization.
• The customers should be able to see the frequently asked question asked by the customers.

A password protection with secure mode option is provided to guard from un-authorized access to database.

• Features:
• The Customers should be free to post their queries to the concern department.
• The Customers should be able to post the survey details on a department by simply selecting.
• The Customers should be allowed to check the status of their query, by using the unique Query Id provided by the system.

• The employees should be able to see the posted queries, which are posted by the Customers.
• The Employee can visit the queries posted to that department only.
• The employee should post back the solution to the queries he has received.
• An employee cannot only see his rating but also rating of other employees who are working in other departments.
• The employees should be able to see the survey details posted by the customers.
• This system should also provide registration of new customers for the organization.
• The customers should be able to see the frequently asked question asked by the customers.

The software is fully integrated with CRM (Customer Relationship Management) as well as CMS (Content Management System) solution and developed in a manner that is easily manageable, time saving and relieving one from manual works.

• Keywords:

• Generic Technology Keywords: Databases, User Interface, Programming
• Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server
• Project Type Keywords: Analysis, Design, Implementation, Testing
• SDLC Keywords: Presentation, Business Object, Data Access Layers

Customer Query Track Screens by finalyearprojects

Read More

Cargo Management System - ASP.NET Project

1. INTRODUCTION

Cargo Manager is a comprehensive cargo management module, designed for addressing the areas of General cargo, Bulk cargo operations. All the aspects of cargo like documentation handling, movement, and storage are addressed in this module.
Key Features Include

• General Cargo Booking (Manifestation of cargo)
• Storing of Cargo (actual cargo weight, volume etc. are recorded)
• Generating the gate pass for bringing the cargo into the warehouse
• Marking the truck exit
• Delivery order for rejected or damaged cargo
• Generating gate pass for redelivery of cargo
• House keeping movements for maintenance i.e., moving the cargo from one place to another
• Extensive report and querying facilities
• Creation of master like cargo agents, commodity master.

Managing The Data
The fundamental building blocks to cargo revenue maximization begin with sufficient, reliable and accessible data. Full air waybill capture is a good starting point. The waybill history should be stored in an accessible format in a database that can be updated daily.
The real challenge is not just to capture the complete life cycle of a shipment from original booking through to invoicing, but to do so in a dynamic and timely way. With new developments in data handling and communications, it is now possible to build a data warehouse that receives seamless, real time updates from reservation systems and with minimal changes to existing systems.

 

Unconstrained Demand
Shipment dimensions cannot be given accurately at the time the booking request is made. Often the actual dimensions received at tender do not anyway become part of any permanent record. Since flights will reach their volume limitations before they hit weight limits on some sectors, some heuristic calculation, such as a density code, is needed to forecast likely volumes. The first step is to use historic data to gauge the total market demand regardless of the airline’s available capacity. This unconstrained demand is set for each product type by origin and destination (O&D), day of week, time of day.
Most cargo customers, unlike passengers, are more concerned with speed and reliability than with routings. That gives the cargo carrier an opportunity to route shipments away from congested bottlenecks and give a better spread of revenues across the network.
For example, a booking request comes through the reservation center to ship between a hub airport and major destination. The route is consistently oversold, so the bid rate is high. The router will evaluate alternative feasible routes which meet both the shipper’s requirements and the carrier’s business rules.
Removing The Politics
Effectively, the cargo revenue optimization system will allow decisions to be taken that make optimal use of another, then the choice will not be made. There will be times when the users override the system’s decisions, but overall it provides the basis for objective network-wide decision-making, taking away the guesswork and the politics.

Cargo Management System - Screens by finalyearprojects

Read More

Budget Planner - ASP.NET Project

Budget Planner

• Title of the project: Budget Planner
• Domain: Open Industry
• Sub Domain:  Finance and Account Division
• Project Architecture: N-Tire Architecture
• SDLC methodologies: Waterfall model
• Abstract of the project:

This project is aimed at developing a system by which the employees in the organization submit the bills to their managers. The bills could of various types and also of various amounts. The employee after submitting the bill will automatically provide the manager’s name to which the bill will be submitted. The bill will pass through a workflow process and the owner of the bill can view the status of the bill at any time. An email will be sent to the concerned people to let them know about the status of the bill.

The software is fully integrated with CRM (Customer Relationship Management) as well as CMS (Content Management System) solution and developed in a manner that is easily manageable, time saving and relieving one from manual works.

Functional components of the project: Following is the list of functionalities which is expected to be provided by the system:

• User will log on to the application and the login will be based on the role of the user. The user will directly take into ‘My open requests’, where the user can view the details of the request and can also view the status at which the request is.

 

• The access to the system will be based on the roles. The roles will be based on the type of department the user belongs to.

Details are:
(1) Any user can create a request by login to the system, the parameters for creating the request will be

• Name of the user (should be defaulted from the login)
• Dept of the user (should be defaulted from the login)
• Type of the bill being submitted (e.g., telephone bill, electricity bill etc)
• Amount of the bill
• Date of expense incurred
• Whether the request is supported by the bills
• Whether the bill amount should be credited to the user account in the bank
• Bank name, address and account number
• Any other mode by which the user will want to get the payment

(2) The manager of the user should be able to view the details of the request but cannot modify the details entered; he can either approve the request or reject it. Every time he performs and operation the approver has to write the comments for the same.

(3) Finance Manager – there will be number of finance managers and each finance manager will be responsible for 1 or 2 departments. Users in this role can only close the application, they can only view the requests and after crediting the amount to the request creator the request will be closed by the finance manager

• The workflow process would be

 

• User creates the request
• Request is send to his manager, this should be done automatically. An email should be sent to the manager and also the request creator with the details of the request.
• Request creator should be able to recall the request from manager, if the request has not been acted on else it cannot
• User if not sent to requestor can cancel the request altogether as well
• User can save the request in draft mode without sending to the approver
• Manager of the concerned request creator can  view the details of the request but cannot modify.
• Request once approved by the manager is sent to the concerned finance dept manager
• If rejected the request is sent back to the request creator.
• In all the above scenarios an email should be sent to the concerned parties for necessary action
• Finance manager after receiving the request has to credit the user account and has to send the request to the creator with proper comments as appropriate.
• Now the creator will close the request after the amount has been credited to the creator.
• After sending the email, the system will keep checking on the daily basis on the status of the request, if no actions is performed in 24 hrs a reminder email is generated which is sent to the user email address as stored in the database.

Screens should also be provided to the administrator of the system to create the employee as well as their manager.

• Keywords:
• Generic Technology Keywords: Databases, User Interface, Programming
• Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server
• Project Type Keywords: Analysis, Design, Implementation, Testing
• SDLC Keywords: Presentation, Business, Data Access Layers
• Environment:
• Servers:
• Operating System Server: - Microsoft Windows 2000 or Higher
• Data Base Server: Microsoft SQL Server 2000/2005
• Clients: Microsoft Internet Explorer,
• Tools: Microsoft Visual Studio .Net
• User Interface: ASP.NET with AJAX
• Code Behind: VC#.NET
•  Requirements:
• Hardware requirements:

 

Number	Description
1	PC with 2 GB hard-disk and 256 MB RAM

• Software requirements:

 

Number	Description
1	Windows 2000/ XP/ or Higher with MS-office
2.	MS-SQL server2000/2005
3.	Ms-Visual Studio .Net 2005
4.	Ms-Internet Explorer

• Manpower requirements:

 3 to 4 Developers can complete this in 3-4 months.

•  Milestones:

No.	Milestone Name	Milestone Description	Remarks
1	Requirements Specification	Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made.	Attempt should be made to add some more relevant functionality other than those that are listed in this document.
2	Technology familiarization	Understanding of the technology needed to implement the project.	The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.
3	Database creation	A database of at least 10 entries of users with at least 1 should application admin.	It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.
4	High-level and Detailed  Design	Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario.	The scenarios should map to the requirement specification
5	Development of front end functionalities.	Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options	During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6	Integrating the front-end with the database	The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing.
7	Integration Testing	The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).	Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
8	Final Review	Issues found during the previous milestone are fixed and the system is ready for the final review.	During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

•  The following steps will be helpful to start off the project:

 

• Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server.
• Gather some knowledge of product hierarchies and maintenance before starting the design.
• Create a user database with different access levels.
• Start with creating the login screen.
• Create menus for navigation and group the functionalities as sub menus.
• Create the help-pages of the application in the form of FAQ. This will helps user.

Budget Planner - Screenshots by finalyearprojects

Read More

Online Blood Donation Portal - ASP.NET Project

BLOOD DONATION PROJECT
ABSTRACT
This project is aimed to developing an online Blood Donation Information. The entire project has been developed keeping in view of the distributed client server computing technology, in mind. The Blood Donation Agent is to create an e-Information about the donor and organization that are related to donating the blood. Through this application any person who is interested in donating the blood can register himself in the same way if any organization wants to register itself with this site that can also register. Moreover if any general consumer wants to make request blood online he can also take the help of this site. Admin is the main authority who can do addition, deletion, and modification if required.
The project has been planned to be having the view of distributed architecture, with centralized storage of the database. The application for the storage of the data has been planned. Using the constructs of MS-SQL Server and all the user interfaces have been designed using the ASP.Net technologies. The database connectivity is planned using the “SQL Connection” methodology. The standards of security and data protective mechanism have been given a big choice for proper usage. The application takes care of different modules and their associated reports, which are produced as per the applicable strategies and standards that are put forwarded by the administrative staff.
The entire project has been developed keeping in view of the distributed client server computing technology, in mind. The specification has been normalized up to 3NF to eliminate all the anomalies that may arise due to the database transaction that are executed by the general users and the organizational administration. The user interfaces are browser specific to give distributed accessibility for the overall system. The internal database has been selected as MS-SQL server 2000.The basic constructs of table spaces, clusters and indexes have been exploited to provide higher consistency and reliability for the data storage. The MS-SQL server 2000 was a choice as it provides the constructs of high-level reliability and security. The total front end was dominated using the ASP.Net technologies. At all proper levels high care was taken to check that the system manages the data consistency with proper business rules or validations. The database connectivity was planned using the latest “SQL Connection” technology provided by Microsoft Corporation. The authentication and authorization was crosschecked at all the relevant stages. The user level accessibility has been restricted into two zones namely.

 

Blood Bank System-screens by finalyearprojects

Read More

Back to My Village - ASP.NET Project

Back To My Village

1. Project Title: Back to My Village

2. Category: Application Development, Enterprise.

3. Abstract:

BTMV is a charity group of professionals those want to voluntarily contribute in their village/town’s development. Issues like Primary education, people’s health, government policies awareness and availability of basic facilities/infrastructure are on main focus among others.

Through the website group want to help their members collaborate, to plan, assess and implement different activities and learn with others experience/feedbacks/suggestions. Group also wants to encourage others to join their initiatives and recognize their contributions.

4. Existing System:

• The existing system is a semi-automated at where the information is stored in the form of excel sheets in disk drives.  The information sharing to the Volunteers, Group members, etc. is through mailing feature only. The information storage and maintenance is more critical in this system.  Tracking the member’s activities and progress of the work is a tedious job here.  This system cannot provide the information sharing by 24x7 days. 

5. Proposed System:

• The development of this new system objective is to provide the solution to the problems of existing system.  By using this new system, we can fully automate the entire process of the current system.  The new system would like to make as web-enabled so that the information can be shared between the members at any time using the respective credentials.  To track the status of an individual process, the status update can be centralized using the new system.  Being a web-enabled system, the process can be accessed across the world over net. 
• This system also providing the features like Chatting, Mailing between the members; Images Upload – Download via the web site; updating the process status in centralized location; generated reports can also be exporting to the applications like MS-Excel, PDF format, etc. In this new system, the members like Donors can give their valuable feedback to the Volunteers so that the Volunteers can check their progress of the tasks.

 

• The entire process categorized as different modules like Admin module, Volunteer module, etc. at where we can classify the functionality as an individual process.

• Using the new system entering into Admin module we can perform….

 

• In this new system using the Volunteer module we can do….

• In the Reports module we can generate reports like Weekly Status Report.

 

6. MODULES:

          The system after careful analysis has been identified to be presented with the following modules:

1. Web Administration
2. Group Member
3. Anonymous Users
4. Member Communications
5. Registration
6. Search
7. Reports
8. Authentication

 

7. Functional Requirements:

• Secure registration and profile management facilities for group members
• Tracking member’s activities and progress.
• Facilitating communication - Discussion chat/mail – very important
• Assessment of current situation: With the help of online questionnaires, members need to access the mature ness of primary education, health facilities etc. and based on the assessment need to categorize (total 5 categories) and chalk out a plan of actions by choosing from system suggested activities.
• Each plan of action would be shared with other members before execution so that they can share their experiences, feedbacks and suggestions.
• Your creativity is required to frame the activities in each field. For example, to promote child education one can start giving scholarship to top 3 students in each class, you can also award best teachers on the basis of class result etc. These activities may be executed in many phases.
• Group promotes its activities by providing online information and Face-to-face meetings with professionals to raise funds. They create case studies and share with everyone to motivate them to contribute.
• Members are advised to develop a volunteers group in the village so that they can monitor, stabilize the changes and report to you.
• Group also runs a monthly magazine and mails it to all members and those who had subscribed. Anyone can subscribe for it for free.
• Basic and advance admin facilities like add/update members, backup/recovery of data, generating various reports etc.

8. Non Functional Requirements:

• Secure access of confidential data (user’s details). SSL can be used.
• 24 X 7 availability
• Better component design to get better performance at peak time
• Flexible service based architecture will be highly desirable for future extension

 

 

• KEYWORDS:

 

• Generic Technology Keywords: Database, User Interface, Programming
• Specific Technology Keywords: Asp.Net 3.5, C#.Net, MS SqlServer-05
• Project Keywords: Analysis, Design, Implementation, Testing
• SDLC Keywords: Presentation, Business Object, Data Access Layer

•  ENVIRONMENT:

                 Servers:

• Operating System Server: Windows XP or later
• Database Server: Microsoft SQL Server-2005
• Client: Microsoft Internet Explorer
• Tools: Microsoft Visual Studio .Net-2008
• User Interface: Asp.Net with Ajax
• Code Behind: VC#.Net

11. Requirements:
          Hardware Specification:

• Intel Pentium or More
• 512 MB Ram
• PC with 20GB

       Software Specification:

• WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)
• Visual Studio .Net 2008 Enterprise Edition
• Internet Information Server 5.0 (IIS)
• Visual Studio .Net Framework (Minimal for Deployment)   version 3.5                        
• SQL Server 2005 Enterprise Edition

 

Back to My Village Screens by finalyearprojects

Read More

Remote Networking Service - ASP.NET Project

REMOTE NETWORKING SERVICE

Abstract:
An Remote networking service group is an online community that lets you meet your friend’s friends. It's where people meet with people online, get to know each other, interact, and share ideas with each other, just like a real community. This is  not only allows users to manage and archiving mailing list, but also provides a method for true communication and collaboration with group members. It provides ads for various pages.
Module Description:
Remote Networking Service Mainly Divided Into Four Modules.

• Create Groups

                    Create Groups again divided into some Sub Modules
1. Post
By using this option we can post the message to all members.
2. Messages
Messages option can give the messages to the others.
3. Photo
By using this we can upload the photo and delete the photo.
4. File
By using this option we can upload the files and delete the file.
5. Video
By using this we can add the video and delete the video.
6. Invite
Invite module is used for the invite friends for online.
7. Profile
Profile Module which gives the update the profile and delete the profile

• Search        By Using Search Module we Can Search The Groups.

• Manage      By using Manage Module We Can do the Leave Group, Edit Group, Delete Group and Edit Profile.
  

• Change Password. It Is used for change The Password.

Features:
The various features provided by the system are

• Making new group: Making a group is easy – just  enter a name and start inviting members
• Join a group: join straight away or request an invitation and can share a lot of information.
• Share files and member information: Group members can upload files and share with others in the group.
• Share photos: downloading and uploading photos in the system.
• Search or browse for groups: search for various groups present in the system and find out the relevant messages present in the groups.
• Share videos: can share videos.
• Provides various messengers in the system by which the user can chat with various domains.

Remote Networking Groups - Screens by finalyearprojects

Read More