Essay:

Essay details:

  • Subject area(s): Engineering
  • Price: Free download
  • Published on: 7th September 2019
  • File format: Text
  • Number of pages: 2

Text preview of this essay:

This page is a preview - download the full version of this essay above.

Chapter1

INTRODUCTION

A meeting is usually a gathering of two people, which constitutes of project debate and discussions. The project "GoLive" is the standard web application which is related to the live meeting of the employees in an organisation. The main purpose is to communicate with employees of the different locations.

This project is a very good platform which is set for all type of employees in organisations like Project leaders, admin and developers to keep in constant touch and gather status of the progress of the project. In this project we use Client Server technology. The existing system is a manual system which is should be converted into automated one. There is very much high risk of data mismanagement in the existing system.

The administrator can contact and communicate with the project managers/leaders and developers or any level employees instantly and also can know the login and logout time of the employee. The administrator can also chat with both the project leaders and developers about the progress of the project and also can give his valuable suggestions regarding project. This project also contains a valuable feature like offline messages. The project leader can give immediate report about the project ongoing progress to the administrator.

1.1 Project Description

In this project first the admin, project leaders and developers have to register themselves before logging in. While registering they have to their personal details in the necessary fields. The details such as their first and last name, their date of birth, their email id etc. Once the registration is done the user will get the confirmation message of the successful registration and then the user can login using the required authentication.

The administrator can contact and communicate with the project managers/leaders and developers or any level employees instantly and also can know the login and logout time of the employee. The administrator can also chat with both the project leaders and developers about the progress of the project and also can give his valuable suggestions regarding project. This project also contains a valuable feature like offline messages. The project leader can give immediate report about the project ongoing progress to the administrator.

Through our Golive application whenever an user, i.e., project leader or developer logs in to the system, the login details of that user will be recorded in the administrators system which will be done automatically. The administrator then can check the log in a log out time of the employees and can send a message and also keep track of the needed information's. This project also contains a valuable feature like offline messages. The project leader can give immediate report about the project ongoing progress to the administrator.

Through this application the administrator checks which employee is online as he can see through the login and logout details of the employees. The administrator can scan through the list of online employees and can send messages to a single individual employee or a group of employees, developers, or set of developers, project leaders or set of project leaders simultaneously.

The project makes most of the complicated and difficult work to minimise. These makes the project leaders and developers to concentrate more on their work rather than wasting much time on these type of works.

The software is developed in very good manner which helps work making easy, manages complex works easily, user friendly and highly scalable. Our project is totally integrated with Customer Relationship Management (CRM) and Content Management Solutions (CMS) which provides best output to the solution as the result.

The proposed system maintains the following activities:

' Constant and regular interactions between project leaders/managers and developers of the project.

' The login and logout time of the users will be recorded automatically.

' Message view feature has been added and also our project maintains online and offline messages.

' Hierarchy of the employee is maintained.

1.2 Company Profile

Company Name : Goal Technologies

Address                      : 4th Floor, Raj Towers

                              Near City Bus Stand

                              Udupi -576101

                               Karnataka, India

Contact                       : +91 820 4296777

                                +91 820 4293444

Email ID                    : [email protected]

 Website                     :  www.goaltechnologies.in

Operating since         : 1997

Goal Technologies as popularly known for Global Technologies Pvt. Ltd. This is located in the heart of Mangalore city and the branch office is located in the heart of Udupi city. This city is an educational hub of the nation and also gem of coastal Karnataka. The main objective of the Goal Technologies is to develop the profession of information technology in the coastal Karnataka.

Goal Technologies progressed further in the information technology field by  having tie ups with international firms such as Microsoft and Redhat. The certifications from international standard organizations are obtained to maintain the standard and quality of our organization. Goal Technologies have been certified with ISO 9001-2000 and again in the year 2008, ISO 9001-2008 certification by NAQ Ukas of USA as a party of the successful audit. Goal Technologies is the first institution which is pertaining to the quality of the deliverables.

Goal Technologies has one of the best infrastructures in the city.

1. Facilities ' the director himself is very well experienced in the field and is a certified person. At the time of hiring the faculty's deep screening of their knowledge and teaching skills is done. Only certified and experienced faculties are hired in the institution.

2. Laboratories ' The institution stresses more on practicals. With which the latest technologies very well equipped computer systems are provided in the laboratory.

3. Library ' The student reference books and the latest books related on Technologies are placed in the library.

The focus of Goal Technologies is what makes us different from other training institute in the city. The Goal Technologies concentrate more on new innovations over technologies and guaranteed returns in investment with the immense knowledge the students get after the training. The main goal of Goal Technologies is not only on the working projects but also focus on the results. Goal Technologies offer the unique courses in the industry.

Chapter 2

LITERATURE SURVEY

2.1 Existing and Proposed System

The existing system is the one which is followed till date. It simply means the application which is present in the current day market. The existing system uses manual system. This manual system needs to convert to the automated system. While doing this there is a high risk of data mismanagement. This process is less secured and can't find much coordination between different types of applications and users.

Third party public mail service has been used in the existing system. They use public domain which is not meant to be so safe. Unknown users can be allowed here in these domains. It is dangerous to share information in such environment. Manual system is used in some organisations. In the manual system discs and drivers are used to store data and information.

2.2 Feasibility Study

Feasibility study is done to estimate and analyse the proposed application or project if it's quiet feasible or not, if it is feasible then whether it's under the estimated cost or whether it is profitable. It is to make sure that the project which we develop performs effectively. First study of the feasibility must be performed to evaluate feasibility. This study determines whether is the solution has completed all the requirements and is effective in the software.

Users should accept the software and we should create the reasons for developing such software's. This is major objective of the feasibility. Technical feasibility, Operational feasibility and Economical feasibility are the three common types of feasibility.

In Technical feasibility, the existing resources are considered such as software and hardware, and the technology in which user requirements can be completed within the prescribed span of time. Skills and technical capabilities of the development team are examined in this type of technical feasibility. Made sure the technology used is safe and secured.

In Operational feasibility, the scope to which the software required performs the following steps which solve the necessities of the users and requirements for the business. Whether the software or project is acceptable by the software development team or not is decided by the operational feasibility. It makes sure whether the user can be able to adjust to this new type of software or not.

In Economic feasibility make sure whether this software which we developed contributes in the financial improvement and growth of an organisation. The projects developed can be economically feasible if it is developed on making note that it should run on long term basis for an organisation and also taking care of its cost. The cost of hardware, other requirements and also development team and their training are to be taken care.        

The project "GoLive" is the standard web application which is related to the live meeting of the employees in an organisation. The main purpose is to communicate with employees of the different locations. This application is made sure if it is technically, operationally and economically feasible. This application consists of existing resources such as hardware and software requirements, which helps to build the application and also help to complete the requirements of the user.

This project is a very good platform which is set for all type of employees in organisations like Project leaders, admin and developers to keep in constant touch and gather status of the progress of the project. In this project we use Client Server technology. The existing system is a manual system which is should be converted into automated one. There is very much high risk of data mismanagement in the existing system.

The administrator can contact and communicate with the project managers/leaders and developers or any level employees instantly and also can know the login and logout time of the employee. The administrator can also chat with both the project leaders and developers about the progress of the project and also can give his valuable suggestions regarding project. This project also contains a valuable feature like offline messages. The project leader can give immediate report about the project ongoing progress to the administrator.

2.3 Tools and Technology Used

The tools and technologies used for GoLive application are Visual studio .Net 2005 Enterprise Edition, SQL Server 2000 Enterprise Edition, Internet Information Server 5.0 (IIS), and Visual Studio .Net Framework. Visual studio is an Integrated Development Environment (IDE) used for developing Dot Net platform.

2.3.1 Dot Net Framework

The .Net framework is a platform for computation which can simplify development of application in the environment which is distributed on the internet.   Consistent object oriented programming environment will be provided. Software deployment and conflicts f the versioning will be minimised. Safe execution of the code will be guaranteed including code developed by unknown person or semi third party.

The Common Language runtime and .Net framework are the two main components of the .Net framework. The common language runtime is the foundation of the .Net Framework. Managing code at execution time, and core services such as memory management, thread management etc are managed by Common Language Runtime.

The file access operations, registry access operations or other sensitive operations are might or might not be able to perform even being used in the same application.The.Net Framework Class Library is tightly bound with common language runtime which is a collection of reusable types. The class library is object oriented which usually provides types from which our code can derive its functionality.

2.3.2 ASP.Net

ASP.Net is built on Common language runtime is a programming framework. This is used on a server to build some extraordinary web applications. Early binding, Just in Time compilation and native optimizations are the advantages of the ASP.Net. Automatic deployments drag and drop controls, What You See What You Get Features and also there in ASP.Net when used in the software Visual Studio.  

Common tasks are performed easily in ASP.Net such as submission of forms, authentication of clients, deployments etc. ASP.Net also has features such as scalability and availability. The features of ASP.Net can be customised and also can be extend on necessity. In ASP.Net the applications are highly secure with built in windows authentication.

2.3.3 SQL Server

The user access to their data is given by the data base management system or the DBMS. This helps them to transfer data into information. Such database management system includes sql server. Users can create, update and extract information from the database through his system.

Structured collection of data is called as database. Characteristics of people, things and events refer to data. Each data is stored in its own field in the sql server. Can't have same field name in the sql server relating to each other.

Table is used to store records in a sql server.  Tables are grouped together to form a database. Field or combination of fields which uniquely identifies each record in a table is known as primary key.

It's easy to link the data in a multiple tables using sql server. This is what it makes a relational database management system, RDBMS. When a primary key of one table is matched with field of another table then it's called as Foreign Key. Sql server allows maintaining consistency between multiple tables.

Abstract view of data is allowed in the sql server. Physical level is the lowest level of abstraction, shows how the data actually stored. Conceptual level shows the relationship among data.  View level is the highest level of abstraction.  

2.4 Hardware and Software Requirements

2.4.1 Hardware requirements:

This system doesn't require any special hardware interface, and is executable with minimum current hardware configuration.

' Monitor as a display

' Processor with a minimum speed of 2.8 GHz

' Minimum RAM capacity of 1GB.

' Minimum Hard Disk capacity of 160GB

2.4.2 Software requirements:

This package has been developed using Visual Studio 2012. The language used is ASP.Net. Using C#

The Other Software Requirements are:

' Operating system is Windows XP, Windows 2000, and Windows 7.

' Technology used is ASP.NET (Using C#)

' Front End: Visual Studio 2012

' Back End: SQL Server 2008 (As Database tool).

Chapter 3

SOFTWARE REQUIREMENTS SPECIFICATION

3.1 Users

This project is a very good platform which is set for all type of employees in organisations like Project leaders, admin and developers to keep in constant touch and gather status of the progress of the project. In this project we use Client Server technology. The existing system is a manual system which is should be converted into automated one. There is very much high risk of data mismanagement in the existing system.

3.1.1 Admin

The admin is super power of our project GoLive. The admin Logs in with the given username and password. Once the admin login, the welcome page will be displayed. There the admin gets the main menus like Home, Add, View, Reports and Change Password. In the Add menu the admin can add country, state, place, city etc. In the View Menu, the admin can view all the users who are online, the login and logout history of the users, the feedbacks sent by the users. The admin can send message to those who have sent the feedback. The admin can send messages in group or a single individual person. The admin can check the member reports where he can do this by selecting the form and to date. Admin can generate report though excel format or pdf format and also can print report directly.

3.1.2 Users

The employees in the organisations are the real users of this software. The user logs in with the suitable user id and password. If there is a new user, he/she has to register first. While registering the user need to fill all the mandatory details in the registration form. And at the end the user have to inert the captcha code given and then click on submit button.

Once the user gets registered with pour system he/she logs in with the authenticated username and password. The home page of the user will be displayed. Here the user has options like Update his profile, Check Mail, Join Chat room, Change password and Feedback.

In the update profile menu, the user can update his profile if any changes has to be done while registering. In the check mail menu, mail box will be opened. The user can compose mail, save mail as drafts, send mail, check sent items etc. to his co-employees. The user also can join the chat room and chat with his fellow colleague or the project leader about the progress and status of the project he is handling. The user can change password if he/she wishes to do so.

3.2 Functional Requirements

The communication between the admin and the software to manage this application as related to the existing addition. All the information should be in the correct format to avoid the failure. The functional requirement is the explanation of the capability or characteristic required. It will describe what system should do or what should make available for user.

3.2.1 User Interfaces

This software provides good graphical interface for users to access the application easily and it is also easy to maintain.

3.2.2Hardware requirements:

This system doesn't require any special hardware interface, and is executable with minimum current hardware configuration.

' Monitor as a display

' Processor with a minimum speed of 2.8 GHz

' Minimum RAM capacity of 1GB.

' Minimum Hard Disk capacity of 160GB

3.2.3 Software requirements:

The software requirements are explanation of features and functionality of the objective system. The application requirements are hidden or seen, known or unknown expected or unexpected from the client's point of view.

' Operating system is Windows XP, Windows 2000, and Windows 7.

' Technology used is ASP.NET (Using C#)

' Front End: Visual Studio 2012

' Back End: SQL Server 2008 (As Database tool).

3.3 Non- Functional Requirements

Non-functional requirement describes the detail constrains, control device for the system, performance, response time, security, safety and target value such as the purpose of building this application. It also describes how well this application will work and standard function should be provided for the application.

3.3.1 User friendly

The application is easy to learn and understand. A younger generation users can also use the application effectively, without any difficulty.  It helps the user to operate easily. Any user can use this application and it is easy to use.

3.3.2 Security

The software has login facility through which only valid authenticated user can login. In this software only authorized people can access this database. This application has high security which helps to avoid unauthenticated users to use this application. Without login the passengers cannot update the information or any contents.

3.3.3 Safety

The safety requirements will help to provide the error free application to users. This is very helpful to access information from this application

3.3.4 Maintainability

Maintainability is the capability of the system which undergoes changes with no difficulty. These changes will be show on components, services and interfaces so on.

3.3.5 Performance

Performance indicates the how immediate the response will be given according to the user's needs within the given interval time. It can be measured by quick response and the throughput.   

3.3.6 Response time

Response time will indicate how much time it will take to response for one interface to another interface. If the response is low then it will take more time. This can be reduced by good quality planning.

3.3.7 Cost element

The GoLive application is much cost effective and highly economical. It is highly recommended for organisations to betterment of communication between their employees.   

3.3.8 Reliability

Reliability is the ability of the application to remain equipped over time. Reliability is measured as the possibility that a application will not fail to perform its proposed functions over a specified time interval.

Chapter4

SYSTEM DESIGN

4.1 System Perspective

System design has its own importance and has a very important role in the whole software development process in the software engineering. System design is a much more than systematic approach to the system in a broader way. In a system design all the requirements are fulfilled perfectly. All the aspects such as efficiency, security, scalability and flexibility are also taken care by the system design.

The processes which are defined by the system design usually are those of components', architecture of the system, modules involved in the system, data required to the system and also the interfaces. In the system design we use hot to apply the theory of systems into the designs in the product development process.  In the system development process we create or alter the systems along with different methodologies and practise.

4.1.1 Admin Module

The admin Logs in with the given username and password. There the admin gets the main menus like Home, Add, View, Reports and Change Password. In the Add menu the admin can add country, state, place, city etc. In the View Menu, the admin can view all the users who are online, the login and logout history of the users, the feedbacks sent by the users. The admin can send messages in group or a single individual person. The admin can check the member reports where he can do this by selecting the form and to date.

4.1.2 Online Chat Module

Here in this module the registered members or employees of an organisation can chat with another member through chat module in this software. Before entering into the chat room the members need to be authenticated, i.e., the members need to be logged in to the system. The new user can register first and then login in order to use the chat room. Two type of chats available in our system. 1. Single person ' where a member chats with only one person. 2. Group ' where a member chats with multiple people.          

4.1.3 Member Registration Module

The member has to register before signing in the system for registering the member has to provide his details given in the registration form. Once the successful registration is done, the member can sign using authenticated user name and password.

4.1.4 Email Module

Members can send, receive or view mails by making use of this module. There are also many features like the members can edit, view or delete the mails. The members can forward the mails to other members, also can send attachments through mail and can send group mails and also can manage mails in folders.

4.1.5 Feedback Module

The registered members can send feedback to any other registered member or to the admin directly. The feedback may be regarding the project issues, project development stages, the project progress etc. The other members once logged in gets the feedback and can respond back to the user who has sent. Members can also send attachment through feedbacks.

4.2 Context Diagram

Boundary between system and the part of the system is defined by the Context Diagram. The entities which can interact with the system can be shown in Context diagram. The high level view of the system is context flow diagram. It is much more similar to the block diagram. System frequency has been frequently shown in the context diagram on the software.                       

Context flow diagram is the level 0 of the data flow diagram and it is the best first level of diagram to represent a system design. The flow of control of the method or analysis is defined in the context flow diagram.  One process node is contained by the context flow diagram which means for the purpose of the entire system. The case condition and also if-then-else condition is contained in the context flow diagram. Arrows are used to indicate flow from one to another. Context flow diagrams is also a another version of data flow diagram.

Great level of the system production is represented by the Context flow diagrams. System field under verification is also defined by the Context flow diagrams. The outgoing data flow of process is linked to external entities. The Context flow diagrams are a very popular tool for displaying and scope of the project. The choice of the limitations of the system is well discussed in the Context flow diagrams. This makes compulsory to recognize the diagram. It's very easy to draw the notation. These Context flow diagrams include broad number of viewers including all the expert of business, data analysts etc.

  

Figure 4.1 Context flow diagram of GoLive application

In this application the user first registers with the application and then after verifying the details the user can login to the application GoLive. Once the user logs in the user can go through his profile where he can update his profile, check mail, join chat room and also send feedback. Parallel the admin can login with the given user id and password and then can update place details, view login and logout history of the registered users. The admin also can generate the reports of the members.

4.2.1 Data Flow Diagram

A Data Flow Diagram (DFD) is a diagram that describes how the data flows. In dfd the process can change or alter data through entire system. DFD is a structure tool which is usually used to design a flow chat which shows or depicts how the system process works.

The Data Flow Diagram makes arrangements for input and output, checks the current system, specifies the plan to implement it, etc. The Basic symbols used to construct data flow diagrams are

Process

The information of the data flows within the system is shown in this process.

Data Flow

This shows the flow of information from source to destination.

Data Store

Stores the data that can be retrieved when needed.

External Entity

These are outside the system but they either provide input data into the system or use system output.

4.2.2 Level 0 DFD

Figure 4.2 Level 0 DFD

This diagram represents the entire working of the system. The application has two main working authorities, Admin and Users. The users logs in with the authenticated user id and password. For the new user they have to register first and then login. The users can update their profile, check mails, send mails and receive mails, send feedback etc. The user can also join chat room and chat with other registered members. Parallel the admin can login with the valid user id and password. The admin can add places, edit or deleted members, view login and logout history of the employees and also generate member wise reports, and respond to user feedback though mails.

4.2.3 Level 1 DFD ' Admin Login

Figure 4.3 Level 1 DFD- Admin Login

In this diagram the admin logs in with the valid user id and password which is already given to them. The login details are stored in the table tbl_AdminLogin. Once successful login the admin gets access to the Golive Application.

4.2.4 Level 1 DFD ' User Login

Figure 4.4 Level 1 DFD ' User Login

In this diagram the user logs in with the valid user id and password. If the user is new he/she has to register first and then log in with authenticated user id and password. The login details are stored in the table tbl_UserLoginAccount. Once successful login the admin gets access to the Golive Application.

4.2.5 Level 1 DFD ' Change Password for Admin

Figure 4.5 Level 1 DFD ' Change Password for Admin

In this diagram the admin can change his/her password by entering the old/current password and updating the new password.

4.2.6 Level 1 DFD ' Change Password for User

Figure 4.6 Level 1 DFD ' Change Password for User

In this diagram the User can change his/her password by entering the old/current password and updating the new password.

4.2.7 Level 2 DFD ' User Profile

Figure 4.7 Level 2 DFD ' User Profile

In this diagram the user logs in with authenticated user id and password and redirects to the GoLive user home page. There user can update his/her profiles, Check mails where user can send mails, check inbox, save as drafts etc. The user also can join chat room where user can chat with other registered members. The user can send feedback to the other users or project leaders or the admin directly.

4.2.8 Level 2 DFD ' View Details for Admin

Figure 4.8 Level 2 DFD ' View Details for Admin

In this diagram the admin can add country, state, income, interest, industry and occupation column of the employees which they can fill while registering.

4.2.9 Level 2 DFD ' Add Place Details for Admin

Figure 4.9 Level 2 DFD ' Add Place Details for Admin

In this diagram the admin can view the details of users such as login history, logout history and all user details. The admin can select the form and to date to which he/she want to see the login and logout details of the users. The admin also can view the feedback sent by the users and respond to the feedback via email.

4.2.10 Level 2 DFD ' Generate Report for Admin

Figure 4.10 Level 2 DFD ' Generate Report for Admin

In this diagram the admin can generate the member wise report of all the employees and also can export the list trough excel format or pdf format or can print directly from the screen.

Chapter 5

DETAILED DESIGN

5.1 Use Case Diagram

The use case diagrams are commonly known as Behaviour diagrams. Set of use cases and actions are used to describe by the use case diagrams. The use case diagrams can perform with one or more external users of the systems. Use cases will provide valuable result to the system and users who sues it.

Unified Modelling Language 2.0 to 2.4 qualifications can also described as use case diagrams as a field of a class diagram and class diagram is also referred as structure diagram. Use case diagrams explain the performance of the system. It is also known as structure diagrams.

It is important to continue the dynamic behaviour of the system to model the system. The performance of the system when it is running or operating is known as dynamic behaviour of the system.

It is necessary for use case to be dynamic in nature and there should be some external or internal factors for making the communication. These are known as actors. Use case diagrams are consists of actors, use cases and their relationships.

The dynamic aspects of the system are displayed in the use case diagrams. The other four diagrams like activity, sequence collaboration and state chart are also having the similar purpose.  

Use case diagrams are used to collect the requirements of the system including external and internal influences. These requirements are design requirements. So when the system is analysed to assemble its functionalities use cases are prepared and actors are recognized. Now when the preliminary task is completed use case diagrams are modelled to present the external view.

Use cases are nothing but the system functionalities written in an ordered manner.  The second things which are relevant to the use cases are the actors. Actors can be defined as somewhat that interacts with the system.

5.1.1 Use case Diagram of GoLive

Figure 5.1 Use case diagram of GoLive

5.2 Sequence Diagram

The subsets of interaction diagrams are called as sequence diagrams. In order make clear activities sequence diagrams are used. A Sequence diagram shows how processes function with one another and in what order. Message sequence chart is used. Object communications arranged in time to sequence is shown in a sequence diagram. It shows the objects and classes which are used in the development of the system and the series of messages are inter exchanged between them. Sequence diagrams are generally associated with use case of the system under development.

The system must wait until the message is done such as an invoking a subroutine if a caller sends a synchronous message. The system can continue processing and does not have to remain for a answer if a caller sends an asynchronous message. Multithreaded applications and in the message oriented middleware the asynchronous calls are represented. To represent that processes are being performed in response to the message that is Execution Specifications in Unified Modelling Language, the activation boxes or the method call boxes are used.

Add new activation boxes on top of any others to allocate a additional level of processing. An X is drawn on top of the lifeline if an object is removed from message and the dashed line ceases to be drawn below of it. It should be the result of a message either from the object itself or another.

Until the message is done such as invoking a subroutine, the caller must wait and then sends a synchronous message. The caller doesn't have to remain for a answer then it can continue the processing work until the caller send and asynchronous message. In the multithreaded boxes and in the message oriented middleware there presents asynchronous calls. To represent that the process are being performed in response to the message are the thick rectangles drawn on top of the lifelines which is called as activation boxes of method call boxes.

To allocate an additional level of processing, the objects which call themselves and use the messages and add new connection boxes on the top of any other. An X is drawn on the top of the lifeline and dashed line is ceased to be drawn below if an object is removed from a message. This should be the result of a message.

5.2.1 Sequence Diagram Components

The different types of sequence diagram components are:-

Object - This is box in shape which represents class or objects in unified modelling language. This shows how an object behaves in the system. Class attributes are not supposed to list in this type of shape.

Activation Boxes - This is a rectangular shaped box.  The time needed for an object to complete a task is represented by the activation boxes. The longer the time it takes to complete a task, the longer will be the activation box.

 Actors - Stick figure is represented by the actors. Actors are the type of entities that are interactive both with and external to the system.

Package - It is also called as Frame. To contain interactive elements, the rectangular shaped notation is used in the unified modelling language 2.0. In this shape it has the small inner rectangular used for labelling the diagram.

Lifeline - The passage of time as it extends downwards is represented by the dashed vertical lines. This is called as lifelines. The sequential events are represented along with time.  These lifelines may begin with labelled rectangular shape or an actor.

Option Loops - This is rectangular shaped and has smaller label within it. The 'if then' scenarios are modelled in this symbol.

Alternatives - The choice which is usually equally exclusive between two or more message sequences are signified here. The labelled rectangular shape with a dashed line inside represents the alternatives.

Messages - Information's are transmitted between objects are in the form of packets. They may display the start and end of an operation process or also the sending and response of signal.

5.2.2 Sequence diagram for Admin Track User Login Details

 Figure 5.2 Sequence diagram of Admin Track User Login Details

In this diagram the admin sends login details request to the system, the system then gets the request from the admin. The class login executes the data and sends to the database. The database then executes the data and responds back to the class login which then sends login details back to the admin.

5.2.3 Sequence diagram for Admin Track User Logout Details

Figure 5.3 Sequence diagram of Admin Track User Logout Details

In this diagram the admin sends logout details request to the system, the system then gets the request from the admin. The class login executes the data and sends to the database. The database then executes the data and responds back to the class login which then sends logout details back to the admin.

5.2.4 Sequence diagram for User Check Mail

Figure 5.4 Sequence diagram of User Check Mails

The diagram depicts the mail activities undertaken by the user in the system. The user sends mail by inserting mail details. The class mail will execute the query and the database responds to the mail back to the user.

5.2.5 Sequence diagram for User Chat Details

Figure 5.5 Sequence diagram of User Chat Details

This diagram depicts the sequence diagram of user chats. The user can chat with other users and the details are executed in the database and it responds back to the user.

5.3 Collaboration Diagram

Collaboration diagram is a second integration diagram. Numbering technique is used to indicate the method call sequence here in this collaboration diagram. The methods are called one after the other and the numbers indicate these methods. The method calls are as similar to that of a sequence diagram.

The sequence diagram does not explain the object organization where as the collaboration diagram displays the object organization. Sequence diagram is used if the time succession is important and collaboration diagram is used if association is required.

The objects and relationships involved in a communication and the messages exchanged sequentially among the objects during the interaction of the processes. In a sequence diagram the objects and messages involved in an interaction are shown.

In a sequence diagram only the timing of the messages are shown but not the associations among the objects. Class, class diagram, or a part of the class diagram is disintegrated in the collaboration diagram. The collaboration diagram can also be disintegration of a use case, use case diagram, or part of a use case diagram.

Communication diagram or interaction diagram is also been called for the collaboration diagram. The collaboration diagram is an interaction among objects of software and also the illustration of the relationship in the Unified Modelling Language.

A collaboration diagram displays the functionalities, role and behaviour of objects individually and as well as the overall operations and functioning of the system. The collaboration diagram resembles a flowchart. Rectangles with identification labels are called as objects. The labels may be underlined and are preceded by colons. The lines connecting the rectangles are the relationships between the objects.

Along with the labels that define the sequencing of the messages, the arrows are used to show the messages between objects that are connecting the rectangles. Among moderately small numbers of objects, the collaboration diagrams are best suited to represent the connections which are simple.

5.3.1 Collaboration diagram for Admin Track User Login Details

Figure 5.6 Collaboration diagram of Admin Track User Login Details

In this diagram the admin sends login details request to the system, the system then gets the request from the admin. The class login executes the data and sends to the database. The database then executes the data and responds back to the class login which then sends login details back to the admin.

5.3.2 Collaboration diagram for Admin Track User Logout Details

Figure 5.7 Collaboration diagram of Admin Track User Logout Details

In this diagram the admin sends logout details request to the system, the system then gets the request from the admin. The class login executes the data and sends to the database. The database then executes the data and responds back to the class login which then sends logout details back to the admin.

5.3.3 Collaboration diagram for User Chat Details

Figure 5.18 Collaboration diagram of User Chat Details

This diagram depicts the collaboration diagram of user chats. The user can chat with other users and the details are executed in the database and it responds back to the user.

5.4 Activity Diagram

Another significant diagram in unified modelling language is Activity Diagram. This diagram depicts dynamic aspects of the system. Flow from one activity to another activity is described as the system procedure. So from one operation to another the control flow is drawn. Activity Diagram uses fork, join etc type of different elements.

Executable systems by using forward and reverse engineering techniques are constructed by the Activity Diagrams. The message part is missing flow from one activity to another is not shown in this. It is also considered as flowchart sometimes. The flowcharts which consist of activities that are performed by the systems are the activity diagrams usually. Branching, parallel flow and swim lanes are the supplementary features which make it different from the flow charts.

It's necessary to have clear idea about the elements used in the activity diagrams before drawing it. Activity itself the main element of it. It is a function which is performed by the system. The diagrams consists activities, states and its transition between the activities are coordinated in order to perform better service. The events needed to achieve operations are also described here.

Another significant diagram in unified modelling language is Activity Diagram. This diagram depicts dynamic aspects of the system.  Flow from one activity to another activity is shown in this diagram. The activity is described as the system procedure. So from one operation to another the control flow is drawn. Activity Diagram uses fork, join etc type of different elements.

The basic purposes of activity diagrams are similar to other four diagrams. It captures the dynamic performance of the system. Other four diagrams are used to show the message flow from one object to another. But activity diagram is used to show communication flow from one activity to another.

5.4.3 Activity diagram for Admin Activities

Figure 5.17 Activity diagram for Admin Activities

The diagram shows the admin can manage user details, update or delete them, admin can also check all user details, their login and logout history and also generate reports of the users.

5.4.4 Activity diagram for User Activities

Figure 5.18 Activity diagram for User Activities

This diagram depicts that the user logins to the system after successful registration. The user can update his/her profile, send or receive mails and also can chat with other registered members.

5.4.6 Activity diagram for Admin Login Logout Details

Figure 5.19 Activity diagram for Admin Login Logout Details

The diagram depicts that the admin logins with valid username and password. The admin can check the login and logout details of the user by selecting from and to date in the form.

5.5 Database Design

The method of producing detailed model of data in a database is called as Database Design. All necessary physical and logical designs and the information of physical storage which needed to generate the design in data definition language are contained in the database design. Databases are created using this database designs.

A database can store information about entities, attributes of those entities and relationship among entities. For attributes and indexes data types are also been contained. Appropriate database structure will be determined in the database design. To fulfil given set of requirements the appropriate attributes tables and relationships are decided. They are represented as views and tables in the relational model.

5.5.1 Table Name: tbl_AdminLogin

Field Name Data Type Constraints Description

LoginName Varchar (30) Not null Admins login name

Password Varchar (15) Not null Password of the admin

Table 5.1 Admin Login Table

5.5.2 Table Name: tbl_Country_Master

Field Name Data Type Constraints Description

CountryId Int Primary Key Country id of Admin

CountryName Varchar (50) Not null Country Name of Admin

Table 5.2 Admin Manages Country

5.5.3 Table Name: tbl_Draft

Field Name Data Type Constraints Description

Id Int Primary key ID of the user

LoginName Varchar (50) Not null Login name of user

From Varchar (100) Not null From address of the mail

To Varchar (100) Not null To address of the mail

Subject Varchar (100) Not null Subject of the mail

FullMessage Varchar (500) Not null Clicked to read the full message

Date DateTime Not null Date of the email sent.

Attachment Varchar (50) Not null Attachment is stored in this field.

Size Varchar (20) Not null The size of the email.

MailStatus Char(10) Not null Mail status is stored here.

SendStatus Char(15) Not null Status of sent mails is stored here.

SaveStatus Char(20) Not null Status of saved mails are stored

Table 5.3 Drafts of the Mail

5.5.4 Table Name: tbl_Feedback

Field Name Data Type Constraints Description

Id Int Not null ID of the user.

From Varchar (50) Not null From address of the user

To Varchar (50) Not null To address of the user

Subject Varchar (50) Not null Subject of the feedback

Feedback Varchar (200) Not null Feedback to be sent.

Date DateTime Not null Date of the feedback

Attachment Varchar (50) Not null Attachment is stored in this field.

Size Varchar (20) Not null The size of the feedback

MailStatus Char(10) Not null Mail status can be seen here.

Table 5.4 User Feedback

5.5.5 Table Name: tbl_Inbox

Field Name Data Type Constraints Description

Id Int Primary key ID of the user

LoginName Varchar (50) Not null Login name of user

From Varchar (100) Not null From address from which the mail has to be sent

To Varchar (100) Not null To address to which the mail has to be sent

Subject Varchar (100) Not null Subject of the mail

FullMessage Varchar (500) Not null Clicked to read the full message

Date DateTime Not null Date of the email sent.

Attachment Varchar (50) Not null Attachment is stored in this field.

Size Varchar (20) Not null The size of the email.

MailStatus Char(10) Not null Mail status is stored here.

SendStatus Char(15) Not null Status of sent mails is stored here.

SaveStatus Char(20) Not null Status of saved mails are stored

Table 5.5 Inbox of the Mail

5.5.6 Table Name: tbl_Income

Field Name Data Type Constraints Description

Id Int Not null Serial Number

Income Varchar (50) Primary Key Income of the user

Table 5.6 Income of the User

5.5.7 Table Name: tbl_Income

Field Name Data Type Constraints Description

Id Int Not null Serial Number

IndustryType Varchar (80) Primary Key Industry type of the user

Table 5.7 Income of the User

5.5.8 Table Name: tbl_Industry

Field Name Data Type Constraints Description

Id Int Not null ID of the Admin

IndustryType Varchar (80) Primary Key

Table 5.8 Industry of the User

5.5.9 Table Name: tbl_Interest_Master

Field Name Data Type Constraints Description

Id Int Not null Serial Number

Interest Varchar (80) Primary Key Interest options of the user

Table 5.9 Interest of the User

5.5.10 Table Name: tbl_Occupation_Master

Field Name Data Type Constraints Description

Id Int Not null Serial Number

Occupation Varchar (80) Primary Key Occupation lists of the users.

Table 5.10 Occupation of the User

5.5.11 Table Name: tbl_OfficialAddressBook

Field Name Data Type Constraints Description

Id int Not null User id is stored here

LoginName Varchar (50) Not null Login Name of the user is stored here.

CompanyName Varchar (50) Not null Company Name of the user is stored here.

FirstName Varchar (50) Not null First Name of the user is stored here.

LastName Varchar (50) Not null Last Name of the user is stored here.

Address Varchar (50) Not null Address of the user is stored here.

City Varchar (50) Not null City Name of the user is stored here.

Country Varchar (50) Not null Country Name of the user is stored here.

State Varchar (50) Not null State Name of the user is stored here.

Pincode Varchar (50) Not null Pin code of the user is stored here.

Phone Varchar (50) Not null Phone number of the user is stored here.

MobileNo Varchar (50) Not null Mobile Number of the user is stored here.

FaxNo Varchar (50) Not null Fax Number of the user is stored here.

Email Varchar (50) Not null Email Id of the user is stored here.

Table 5.11 Official Address Book of the User

5.5.12 Table Name: tbl_State_Master

Field Name Data Type Constraints Description

StateId Int Not null ID of the State is stored

StateName Varchar (50) Not null Name of the State is stored

CountryId Int Not null ID of the Country is stored

Table 5.12 State of the User

5.5.13 Table Name: tbl_User_LoginAccount

Field Name Data Type Constraints Description

LoginName Varchar (50) Primary Key Login name of the user is stored

Password Varchar (50) Not null Password of the user is stored

Question Varchar (100) Not null Security question is stored

Answer Varchar (80) Not null Answer for the security is stored

Date DateTime Not null Date is stored.

Table 5.13 User Login

5.5.1 Entity Relationship Diagram

The graphical representation of a system which shows relationship between objects, people, concepts or the system events is known as Entity Relationship Diagram (ERD). The entity relationship diagram can be used as the foundation for the relational database. The ERD also helps in defining business process and its one of the data modelling technique used in the system design process.

The entity relationship explains the entities and the relationship between the entities in a graphical representation format. In ERD, the entity framework is illustrated graphically and conceptually.

Entities, Relationships and attributes are the elements used in a Entity Relationship Diagram. Semi Structured or unstructured data cannot be sufficiently represented in the ER diagram. Entities are the objects that can store the data about them, the cardinality and the relationship between those specified entities.

The relationship is defined in terms of numbers. To design a very good database entity relationship diagrams plays a vital role. This is a very high level logical data model. Conceptual designs are developed very effectively using ERD.

The entity does exist on its own and is a real word concept or the object. In a relational database these entities are similar to those of database tables. Here each row of the table represents the instance of any entity. The particular property that describes the entities is called as attributes of an entity.

5.5.1 Entity relationship diagram of GoLive

Figure 5.5 Entity relationship diagram of GoLive

Chapter 6

IMPLEMENTATION

6.1 Introduction

The theoretical design is converted into a working system; this stage of the project is known as Implementation. The implementation phases constructs of installations and operations of the new system. To ensure that our new system will work efficiently and effectively implementation in the documentation part is used.

Training for End user

The officers working the department play a vital role on the successful implementation of the system. The necessary training on the new technology is given to the officers and end users.

Education for End user

Once the implementation and testing is done, the end users need to be educated about the software. To make end users aware of the system, extra effort should be put towards them when the system seem be much more complicated to understand. Necessary documents and materials about understanding the system should be provided.

Application software training

Once the training on basic computer awareness has been given, the users should be trained on how the application software works. The users should be made sure about how the flow takes places; errors while miss handling the data in the system etc. Should also inform about the validation process and how to check it and made proper.

Post View of the implementation

It's very important for a user to know about the post implementation process. The implementation problem and success should be discussed.

6.1 Screenshots

Welcome Window

Figure 6.1 Welcome Window of the GoLive Application

After the deployment of the project the home page or the welcome screen of the application is displayed. Here the user can login with valid username and password; a new user can register before login. The user can contact the development team, can read about the software and also can send feedback directly.

Mail

Figure 6.2 Email Window for the User

The user here will register himself with his/her details and then logins with the authenticated user id and password. After successful login the user will enter into the home page where user can update his profile, check mail, join chatroom, send feedback etc. The user can compose mail, keep mails as drafts and also send attachment along with mails.

User Chat Room

Figure 6.3 Chatroom for the User

After the successful login the user can join chatroom anytime and can chat with other registered members if they are online. The other members who are online can get instant messages and also can reply to the messages.

User Feedback

Figure 6.4 Feedback of the User

The user can send feedback to the other registered members or the admin directly about the project ongoing and can receive feedbacks though emails.

All User List

Figure 6.5 All User List

This screen is for admin. Here the admin logins with already given username and password. After successful login, the admin homepage will be displayed where admin can manage county, state, income, occupation, industry and interest of the users for registration purpose. The admin can also view the details of the user. He can delete or update any user directly.

Login History

Figure 6.6 Login History of the User

The admin can see the login history of the user by selecting the form and to date and by clicking view button. Along with the login date the login time will also be displayed.

Logout History

Figure 6.7 Login History of the User

The admin can see the logout history of the user by selecting the form and to date and by clicking view button. Along with the logout date the login time will also be displayed.

User Reports

Figure 6.8 User Reports

The admin can generate the reports of the member who registered on particular date. The admin have to select from and to date. The admin can directly export the report to excel format or pdf format or can print directly.

Chapter 7

SOFTWARE TESTING

For a successful system texting plays a vital role. The Goal will be achieved successfully if all part of the system is correct and this is made possible by the system testing. Testing is done in a system using various test data. Operation of a system and evaluation of results under the certain circumstances are involved in the phase of testing. Both normal and abnormal conditions are used while testing. If error found, then it should be corrected and for future reference those errors are recorded.

Testing Objectives

With an intention of finding an error the testing process is done. The yet undiscovered errors are found out with the good testing process. Testing objectives verifies the software performance and its appearance.

Reasons for Bugs

' Lack of proper understanding between applications what should not do.

' The complexity of the software is also one of the reasons for the bugs. Large database, too many modules and structure, making compatible to all types of operating systems etc can cause high amount of temperament and may lead to bugs if not handled properly.

' Errors while coding or programming the application can also cause bugs.

' Frequent changes in requirements, the time pressure to develop an application and the documentation poorly done can also cause bugs in the software.

1. Unit Testing

Also called as Microsoft scale testing. This is used to test some modules of code or particular functions used in the software. This is usually done by the programmers and not by the testers. Without affecting any other module we can test and correct the error in this type of testing. Each module is tested and made sure it's working as per the requirement and results are as expected.

2. Integration testing

When sub modules are brought together and combined that data can be lost across the interface of the software. One module can effect negatively on other module when combined together which we may not get desired output.

3. Acceptance Testing

In this type of testing the realistic data of the client is taken in order to check whether the software is working as desired. In this testing the external system behavior is more concentrated rather than internal logic.

Test Cases

By inspecting visually the result is verified in each of the test cases. In the below table all the conditions are checked by inserting the different possible values and also giving the proper description of the test case.

   7.1 Login Form

Test Case ID Description Condition being tested Expected Output Result

TC_LF_01 Checking valid username and password Valid username, Valid password Displays Main window Pass

TC_LF_02 Checking invalid username, invalid password Invalid username and password Displays Error message 'Invalid User Name or Password' Pass

TC_LF_03 Checking Valid username, Invalid password Valid username and Invalid password Displays Error message 'Invalid User Name or Password' Pass

TC_LF_04 Checking Invalid username, Valid password Invalid username and Valid password Displays Error message 'Invalid User Name or Password' Pass

Table No. 7.1: Test Case of Admin and User Login Form

 

7.2 UserLogin/Logout history

Test Case ID Description Condition being tested Expected Output Result

TC_LH_01 Checking whether From and To Date is selected Valid Date Displays the Details of the user who Login/Logout on particular Date Pass

TC_LH_02 Checking for invalid date Invalid Date Displays Error message 'Please specify the valid From and To date' Pass

TC_LH_03 Checking whether view

Button shows the user details Clicking on view button Displays the user Login/Logout Details Pass

Table No. 7.2: Test Case of Admin to check User Login and Logout History

  7.3 Report Generation

Test Case ID Description Condition being tested Expected Output Result

TC_RG_01 Checking whether From and To Date is selected Valid Date Displays the Details of Report Generated on particular Date Pass

TC_RG_02 Checking for invalid date Invalid Date Displays Error message 'Please specify the valid From and To date' Pass

TC_RG_03 Checking whether view

Button shows the user details Clicking on view button Displays Detailed Report Pass

Table No. 7.3: Test Case of Admin to check Member-wise reports

  7.4 User Full Information

Test Case ID Description Condition being tested Expected Output Result

TC_UI_01 Checking for FirstName Valid FirstName FirstName will be displayed if inserted or else the Error message 'Please Enter the FirstName'. Pass

TC_UI_02 Checking for LastName Valid LastName LastName will be displayed if inserted or else the Error message 'Please Enter the LastName'. Pass

TC_UI_03 Checking for Address Valid Address Address will be displayed if inserted or else the Error message 'Please Enter the Address'. Pass

TC_UI_04 Checking for City Valid City City will be displayed if inserted or else the Error message 'Please Enter the City'. Pass

TC_UI_05 Checking for State Valid State City will be displayed if inserted or else the Error message 'Please Enter the state'. Pass

TC_UI_06 Checking for Pincode Valid Pincode City will be displayed if inserted or else the Error message 'Please Enter the valid Pincode'. Pass

TC_UI_07 Checking for EmailId Valid EmailId Error message will be displayed if email id not entered 'Please Enter the EmailId'. Pass

TC_UI_08 Checking for Gender Valid Gender Gender will be displayed if inserted or else the Error message 'Please Enter the Gender'. Pass

TC_UI_09 Checking for Income Valid Income Income will be displayed if inserted or else the Error message 'Please Enter the Income'. Pass

TC_UI_10 Checking for Occupation Valid Occupation Occupation will be displayed if inserted or else the Error message 'Please Enter the Occupation'. Pass

Table No. 7.4: Test Case of the User Full Information page

  7.5 User Check Mail

Test Case ID Description Condition being tested Expected Output Result

TC_UC_01 Checking whether mails are received in Inbox Checking Inbox of the mail On success ' mails will be received. Error message on mail failure Pass

TC_UC_02 Checking whether messages are stored in draft Close the composed message The messages are stored in the Draft Pass

TC_UC_03 Checking whether Sent messages are stored in Sent Items Sent Items of the Email The sent Mail are found in Sent items Pass

TC_UC_04 Checking whether Message can be saved Saved Message of the Email The messages from Inbox and Sent Items can be saved Pass

Table No. 7.5: Test Case of the User Check Mail

  7.6 User Chatroom

Test Case ID Description Condition being tested Expected Output Result

TC_CR_01 Checking if any number is online Number List column of the Chatroom List of Numbers are Displayed Pass

TC_CR_02 Checking if Chat messages are sent Messages in the Chat Box The Chat Message are displayed in the Chat Box of the Chatroom Pass

Table No. 7.6: Test Case of the User Chatroom

  7.7 Feedback

Test Case ID Description Condition being tested Expected Output Result

TC_FB_01 Checking whether Feedback message are sent From and To of the Feedback Feedback will be sent to the other Registered number Pass

TC_FB_02 Checking whether files can be attached to the Feedback Attachment in the Feedback Files are been attached and are sent through Feedback Pass

Table No. 7.7: Test Case of the User Feedback

Chapter 8

CONCLUSION

This project is very challenging and highly exciting. It gave me great pleasure for me to work on this. This project also provided very good knowledge for me about Client Server Technology along with the knowledge of ASP.NET, Visual Studio and sql server. Also helped in understanding the latest technologies used in client server technology and also in the development of web based applications.

GoLive is a web based application in which data can be entered in simple forms which is highly interactive. Data validation is done so frequently and made sure that user concern is fulfilled. The user gets warning message whenever he/she enters invalid data. Options are provided for the user to update his records whenever he wishes to do that. To maintain the validity of the data the restrictions are made so that the user cannot update the primary data field.

The user can navigate easily to any part of he project easily with the quick links and menus provided in the project. The project is very much user friendly as per the concern of the users. In a single database Data is stored in a much systematic manner which makes storage and retrieval of Data much faster and easier.

Database size will increase day by day which generally creates load on database and might make the maintenance bit difficult. Proper training should be given to the users about the functioning of the software so that they won't make any mistakes which might be a problematic to the system in future perspective.

Chapter 9

FUTURE ENHANSEMENTS

The Golive application is the very efficient application to communicate with the employees of an organisation. This can work with any level of employee in an organisation. Files can be sent though attachment and also instant messages can be sent through online chat module. The feedback can be sent and for the admin the member reports can be generated and also the offline messages can be sent to any of the employee.

In the future perspective we ought to develop an android and IOS application for much better functionality of the users directly from their smart phones. Email verification and sms verification features will also be included. The video calling facility is planned to make possible in coming days to make better function ability to the purpose of the development of the system.

After all the additional features implemented in the software as per the requirements of the user, the application will be rolled out to the market. The user review column is also made available in the software so as to write reviews and feedback about the software by the users.

...(download the rest of the essay above)

About this essay:

This essay was submitted to us by a student in order to help you with your studies.

If you use part of this page in your own work, you need to provide a citation, as follows:

Essay Sauce, . Available from:< https://www.essaysauce.com/essays/engineering/essay-2016-05-29-000BB7.php > [Accessed 24.10.19].