Report

User Role Permission Module - CRM
A PROJECT REPORT
Submitted by
Kevangi Patel
200160107102
In partial fulfilment for the award of the degree of
BACHELOR OF ENGINEERING
In
Computer Engineering
Guided By
Prof. Nainesh V. Nagekar
Assistant Professor
Department of Computer Engineering
Government Engineering College, Modasa
Gujarat Technological University, Ahmedabad

April, 2024
Shamlaji Rd, Modasa, Gajan - 383315, Gujarat, India
CERTIFICATE
This is to certify that the project report submitted along with the project entitled
User Role Permission Module - CRM has been carried out by Kevangi Patel
under my guidance in partial fulfillment for the degree of Bachelor of Engineering
in Information Technology, 8th Semester of Gujarat Technological University,
Ahmadabad during the academic year 2023-24.
Date of Submission:
Prof. N. V. Nagekar Prof. H. R. Patel
Internal Guide Head of the Department

Shamlaji Rd, Modasa, Gajan - 383315 , Gujarat, India
DECLARATION
I hereby declare that the Internship report submitted along with the Internship
entitled User Role Permission Module - CRM submitted in partial fulfilment for
the degree of Bachelor of Engineering in Information Technology to Gujarat
Technological University, Ahmadabad, is a bonofide record of original project
work carried out by me at Zignuts Technolab Limited Under the supervision Mr.
Divyesh Patel and that no part of this report has been directly copied from any
student’s report or taken from any other source, without providing due reference.
Kevangi B. Patel
200160107102
416478
ACKNOWLEDGEMENT
We have taken efforts in this project. However, it would not have been possible without the kind
support and help of many individuals and organizations. We would like to extend our sincere
thanks to all of them. We are highly indebted to Internal Guide (Prof. N. V. Nagekar) and
External Guide (Divyesh Patel) for their guidance and constant supervision as well as for
providing necessary information regarding the project. We take this opportunity to thank all our
friends and colleagues who started me out on the topic and provided extremely useful review
feedback and for their all-time support and help in each aspect of the course of my project
preparation. We are grateful to our college Government engineering college, Modasa for
providing me all required resources and good working environment. We would like to express
our gratitude towards Head of Department, Prof. H. R. Patel for their kind co-operation and
encouragement which help usin this project.
Gujarat Technological University i GEC MODASA

416478
ABSTRACT
The "User Role Permission Module - CRM" project revolutionizes user management by
implementing a robust system of role-based access control (RBAC) within a streamlined
framework. Administrators wield powerful tools to assign roles and permissions, precisely
tailoring user access to designated modules and functionalities. This granular control not only
enhances security but also ensures efficiency in data handling and workflow management. Upon
receiving invitations, users embark on a seamless onboarding journey. They are seamlessly
guided through the platform, encountering personalized welcome messages and prompt setups
for their accounts. With each user restricted to only permitted sections aligned with their
assigned roles, the project guarantees data integrity and confidentiality. By prioritizing user-
centricity and data protection, the "User Role Permission Module" project establishes a new
standard for modern user management solutions. Its meticulous attention to access control and
seamless user experiences fosters trust among administrators and users alike. Ultimately, , this
project empowers organizations to optimize their user management workflows while
safeguarding sensitive information within a controlled and intuitive platform environment.
Gujarat Technological University ii GEC MODASA

416478
List of Figures
Figure 1.1 Zignuts Pvt Ltd .............................................................................................. 2

Figure 2.1 Production Stages .......................................................................................... 6
Figure 4.3 Gantt Chart ................................................................................................... 18
Figure 5.1 User Activity Diagram ................................................................................. 27
Figure 5.2 Admin Activity Diagram ............................................................................. 28
Figure 5.3 E-R Diagram ................................................................................................ 29
Figure 5.4 User Use Case Diagram ............................................................................... 30
Figure 5.5 Admin Use Case Diagram ........................................................................... 30
Figure 5.6 Activity Logs and Companies...................................................................... 31
Figure 5.7 Failed Jobs and Meetings ............................................................................. 31
Figure5.8 Migrations and Modules ............................................................................... 32
Figure 5.9 Notes and Password Reset Tokens .............................................................. 32
Figure 5.10 Peoples and Permissions ............................................................................ 33
Figure 5.11 Permission Modules and Personal Access Tokens .................................... 33
Figure 5.12 Role Permission and Roles ........................................................................ 34
Figure 5.13 User Roles .................................................................................................. 34
Figure 5.14 Class Diagram ........................................................................................... 35
Figure 6.1 User Login Page........................................................................................... 46
Figure 6.2 Admin Home Page ....................................................................................... 46
Figure 6.3 Admin Module Listing Page ........................................................................ 47
Figure 6.4 Add User Page ............................................................................................. 47
Figure 6.5 Edit User Page ............................................................................................. 48
Figure 6.6 Delete Confirmation .................................................................................... 48
Figure 6.7Forgot Password Screen ............................................................................... 49
Figure 6.8 Reset Password Screen ................................................................................ 49
Figure 6.9 User’s Dashboard ......................................................................................... 50
Figure 6.10 Edit User Screen ........................................................................................ 50
Figure 6.10 Reset Password Screen .............................................................................. 51
Figure 6.10 Meeting Listing Screen .............................................................................. 51
Figure 6.10 Add Meeting Screen .................................................................................. 52
Gujarat Technological University iii GEC MODASA

416478
List of Tables
Table 3.6.1 Information Domain Values ....................................................................... 14
Table 3.6.2 Value Adjustment Factor ........................................................................... 15
Table 5.5.1 Users Table ................................................................................................ 36
Table 5.5.2 Modules Table ............................................................................................ 36
Table 5.5.3 Permissions Table ...................................................................................... 36
Table 5.5.4 permission_modules pivot table ................................................................. 37
Table 5.5.5 roles table ……………………………………………………………….37
Table 5.5.6 role_permissions pivot table ...................................................................... 37
Table 5.5.7 user_roles pivot table ……………………………………………………37
Table 5.5.8 peoples table ............................................................................................... 38
Table 5.5.9 companies table .......................................................................................... 38
Table 5.5.10 meetings table........................................................................................... 38
Table 5.5.11 notes table ................................................................................................ 38
Table 5.5.12 activity logs table ..................................................................................... 39
Table 7.1 Login Test Cases ........................................................................................... 55
Table 7.2 Module Test table.......................................................................................... 55
Table 7.3 Permission Test table .................................................................................... 56
Table 7.4 Role Test table .............................................................................................. 56
Table 7.5 User Test table ............................................................................................. 57
Gujarat Technological University iv GEC MODASA

416478
List of Abbreviations
Abbreviation Definition
JQ J Query
HTML Hyper Text Markup Language
CSS Cascading Style Sheets
DB Data Base
SQL Structured Query Language
PHP Hypertext Preprocessor
Gujarat Technological University v GEC MODASA

416478
Table of Contents
Acknowledgement ................................................................................................................ i
Abstract ................................................................................................................................ii
List of Figures .....................................................................................................................iii
List of Tables ...................................................................................................................... iv
List of Abbreviations ........................................................................................................... v
Table of Contents ................................................................................................................ vi
Chapter 1 Overview of Company ........................................................................................ 1
1.1 History ........................................................................................................................ 2
1.2 Scope Of Work ........................................................................................................... 2
1.3 Organization Profile ................................................................................................... 3
Chapter 2 Overview of Different Department ..................................................................... 4
2.1.1 Work Carried Out In Each Departments ............................................................. 5
2.1.2 Web Development ............................................................................................... 5
2.1.3 Mobile Application Development ....................................................................... 5
2.1.4 BA Development ................................................................................................. 5
2.1.5 DevOps Development.......................................................................................... 5
2.2 Technical Specifications Of Equipment ..................................................................... 6
2.3 Production Stages ....................................................................................................... 6
Chapter 3 Introduction to Internship Project ....................................................................... 8
3.1 Project Introduction .................................................................................................... 9
3.2 Purpose……………………………………………………………………………...9
3.3 Scope .......................................................................................................................... 9
3.4 Objective .................................................................................................................. 10
3.5 Technology and Literature Review .......................................................................... 10
3.6 Internship Planning…………………………………………………………...…...12
Gujarat Technological University vi GEC MODASA

416478
Chapter 4 System Analysis ................................................................................................ 19
4.1 Study Of Current System ......................................................................................... 20
4.2 Weaknesses of the current system ............................................................................ 20
4.3 Requirements in New System .................................................................................. 21
4.4 Feasibility Study....................................................................................................... 22
4.5 Feature of new System ............................................................................................. 23
4.6 System Architecture ................................................................................................. 24
4.6.1 Agile Development ............................................................................................ 24
4.6.2 Technologies ...................................................................................................... 24
4.7 Selection of Hardware/ Software ............................................................................. 25
Chapter 5 System Design ................................................................................................... 26
5.1 Activity Diagrams .................................................................................................... 27
5.1.1 User Activity Diagram....................................................................................... 27
5.1.2 Admin Activity Diagram ................................................................................... 28
5.2 E-R Diagram ............................................................................................................ 29
5.3 Use Case Diagram .................................................................................................... 29
5.4 Schemas/ Database Design....................................................................................... 31
5.4.1 Relationship Diagram of Models ....................................................................... 32
5.5 Data Dictionary…………………………………………….……………………...36
Chapter 6 Implementation.................................................................................................. 40
6.1 Implementation Environment ................................................................................... 41
6.2 Security Feature……………………………………………………………………42
6.3 Coding Standard…………………………………………………………………...44
6.4 Result........................................................................................................................ 45
Chapter 7 Testing ............................................................................................................... 53
7.1 Testing Plan .............................................................................................................. 54
7.1.1 Unit testing ........................................................................................................ 54
Gujarat Technological University vii GEC MODASA

416478
7.1.2 Integration Testing ............................................................................................. 54
7.1.3 Validation Testing ............................................................................................. 54
7.2 Test Result And Analysis ......................................................................................... 55
7.2.1 Test Cases .......................................................................................................... 55
Chapter 8 Conclusion ......................................................................................................... 58
8.1 Overall Analysis of Internship: ................................................................................ 59
8.2 Problem Encountered and Possible Solutions: ......................................................... 60
8.3 Summary of Internship: ............................................................................................ 60
8.4 Limitation and Future Enhancement: ....................................................................... 61
Gujarat Technological University viii GEC MODASA

416478 Overview Of the Company
1
OVERVIEW OF THE COMPANY
1.1 HISTORY
1.2 SCOPE OF WORK
1.3 ORGANIZATION PROFILE
Gujarat Technological University 1 GEC Modasa

1.1 HISTORY
Figure 1.1.1: Zignut Technolab Pvt Ltd
Founded in 2017, incorporation with our patent IT Company ZIGNUTS TECHNOLAB PVT.
LTD. has managed to make its own position in IT Sector. Zignuts Technolab is a top-rated Web
and On-demand Mobile App development company in the India, USA and Germany. We strive
to excel in the invention and development of the industry’s most advanced technologies
including mobile apps, web, eCommerce, blockchain, IoT, wearable, cloud integration, cross-
platform, on-demand, enterprise mobility, and alike.
We translate these technologies into value for our clients’ customers giving them professional
and best-in-class services; thereby helping businesses throughout the world harness their full
potential.
1.2 SCOPE OF WORK
 Mobile Application Development:

The company can provide mobile application development services using Flutter, a popular mobile
app development framework. This can include building custom applications, integrating with
third-party APIs, and providing ongoing support and maintenance.
 Web Application Development:

The company can also provide web application development services using Python, a widely
used programming language for web development. This can include building custom
applications, integrating with various web services, and providing ongoing support and
maintenance.

 Web Scraping:
The company can provide web scraping services using Python, which is a powerful language for
web scraping and data extraction. This can include extracting data from various websites,
automating data collection, and providing data cleaning and processingservices.
1.3 ORGANIZATION PROFILE
Name Of the company : Zignuts Technolab Pvt Ltd.

External guide : Mr. Divyesh Patel
Mobile Number : +91 95377 74775
Email : divyeshp@zignuts.com
Work : Web Development (PHP, Laravel, vue)
Address : A-409, Siddhraj Zori,, S. G. Road, Near Sargasan Circle,

Gandhinagar, Gujarat 382421

416478 OVERVIEW OF DIFFERENT DEPARTMENT
2
OVERVIEW OF DIFFERENT DEPARTMENT
2.1 WORK CARRIED OUT IN EACH DEPARTMENTS

2.2 TECHNICAL SPECIFICATIONS OF EQUIPMENT
2.3 PRODUCTION STAGES
4
Gujarat Technological University GEC, Modasa
2.1 WORK CARRIED OUT IN EACH DEPARTMENTS
2.1.1 Web Devlopment

 In this department I did my internship in React js front end development.
 In this department there is many technologies are there from
 There are React js, Vue js, Angular js for front end development in web development.
 There are Node js, PHP with laravel framework for back-end development in web
development.
2.1.2 Mobile Application Development
 There are mainly two OS in app development

 First OS is Android OS in that there is Java, Kotlin, Flutter and etc.
 Second OS is iOS OS in that there is Swift language for Mobile application
development
2.1.3 BA Development
 There is a major part of Business Analyst in the project.

 Basically, Business Analyst work is communication with client and know what is
actuallya requirement of client in project
 All other work regarding project like make flow chart, update to client about project
andall other things in project
2.1.4 DevOps Development
 DevOps department is very important department in company

 DevOps department work is to deploy our project or code to live server or testing
serverand maintenance of server.
 There are mainly two technologies or servers we use for that AWS and Bit bucket.
5
2.2 TECHNICAL SPECIFICATIONS OF EQUIPMENT
i. Desktop computers
ii. Processor: Mac mini M2
iii. Ram: 8GB
2.3 PRODUCTION STAGES
1. Requirement Analysis:
The first stage involves analysing the client's requirements to understand their needs and
expectations. This includes determining the scope of the project, identifying any technical
requirements, and defining the project goals.
2. Planning and Design:

The next stage involves creating a plan and designing the solution. This includes defining the
project schedule, determining the necessary resources, creating a project roadmap, and designing
the architecture of the solution.
3. Development:
The development stage involves building the solution according to the design. This includes
coding, testing, and debugging the solution. The team will ensure that the solution meets the
client's requirements and adheres to quality standards.
4. Deployment:
6
The deployment stage involves deploying the solution to the client's environment. This includes
installing the software, configuring the system, and testing the solution in the client's
environment.
5. Maintenance and Support:

The final stage involves maintaining the solution and providing support to the client. This
includes addressing any issues that arise, providing updates, and monitoring the system to ensure
it is running smoothly.
7
416478 INTRODUCTIONS TO PROJECT
3
INTRODUCTION TO PROJECT
3.1 PROJECT INTRODUCTION

3.2 PURPOSE
3.3 SCOPE
3.4 OBJECTIVE
3.5 TECHNOLOGY AND LITERATURE REVIEW
3.6 INTERNSHIP PLANNING
8
3.1 PROJECT INTRODUCTION
Zignuts Technolab offer end to end services across multiple technology clients around the world.
So being part of the Software developer at Zignuts Technolab gives me the opportunity to enhance
my skills career in Software developer.
By learning through the learning path at Zignuts Technolab , I am able to enhance my skills as a
developer and learn how to work with larger teams. In this company I have starting working on
Cazami website which is very useful for online buyers and sellers.
The "User Role Permission Module" project introduces a streamlined user management system
with precise role-based access control. Administrators effortlessly assign roles and permissions,
ensuring users access only authorized modules and functionalities. Seamless onboarding
processes guide users through the platform, enhancing security and data integrity. This project
sets a new standard for efficient user management, prioritizing user-centricity and data
protection within a controlled environment.
3.2 PURPOSE
The purpose of the "User Role Permission Module" project is to provide organizations with a
robust and efficient user management solution. By implementing role-based access control
(RBAC), the project aims to streamline access permissions, ensuring that users only interact with
modules and functionalities relevant to their roles. This precise control enhances security by
mitigating the risk of unauthorized data access and manipulation. Additionally, the project
prioritizes user-centricity by offering a seamless onboarding experience, guiding users through
the platform with personalized welcome messages and prompt setups. Overall, the purpose of
this project is to empower administrators with comprehensive tools for managing user roles and
permissions while safeguarding sensitive data within a controlled and intuitive environment,
thereby optimizing workflow efficiency and maintaining data integrity.
3.3 SCOPE
System Development: Create user interfaces for administrators to manage roles, permissions,
9
and user access. Implement database schema for storing user information, roles, permissions,
and access controls.Develop backend logic for role assignment, permission management, and
user authentication..
Feature Implementation: Implement User Role Permission Module system to assign roles and
permissions to users. Develop user invitation feature allowing seamless onboarding for new
users. Design intuitive interfaces for users to manage their profiles, passwords, and access
permissions. Implement secure password reset and forget password functionalities for user
account management.
Integration and Testing: Integration with existing systems and applications within the
organization will be a part of the project scope. Perform unit testing to ensure the reliability and
functionality of core features. Conduct integration testing to validate interactions between
different system components. Perform user acceptance testing (UAT) to ensure the system meets
user requirements and expectations.
3.4 OBJECTIVE
 Develop a role-based access control (RBAC) system within Laravel to manage user
permissions effectively.
 Ensure data security and integrity by restricting user access to authorized functionalities
based on their assigned roles.
 Streamline user onboarding processes by implementing seamless invitation and account

management features.
 Improve user experience through intuitive interfaces for role and permission management.
 Optimize workflow efficiency by providing administrators with comprehensive tools for

managing user roles and permissions within Laravel applications.
3.5 TECHNOLOGY AND LITERATURE REVIEW
3.5.1 Front End : Vue, JQuery

10
Component-Based Architecture: Vuexi theme utilizes a component-based architecture,
allowing for modular development and easy integration of UI elements.
Responsive Design: The theme is designed to be responsive, ensuring optimal user experience
across various devices and screen sizes.
Custom Styling: CSS and custom styling options are available to tailor the appearance of the
theme to match the project's branding and design requirements.
Interactive Elements: JavaScript and jQuery enable the implementation of interactive elements
and dynamic behaviors to enhance user engagement.
Data Binding: Vue.js principles of reactive data binding facilitate efficient data management
and seamless synchronization between the UI and underlying data.
Routing: Custom routing mechanisms can be implemented using JavaScript to enable

navigation between different views and pages within the application.
Dynamic Content Rendering: HTML templates combined with Vue.js and jQuery allow for
dynamic content rendering based on user interactions and application state changes.
3.5.2 Back End : Laravel / MySql
Laravel is a powerful PHP framework known for its elegant syntax, expressive features, and
developer-friendly environment. It follows the Model-View-Controller (MVC) architectural
pattern, which promotes code organization, separation of concerns, and scalability.
Eloquent is Laravel's built-in Object-Relational Mapping (ORM) system, which provides an

intuitive and expressive way to interact with the database. With Eloquent, developers can define
database models and relationships using simple, fluent syntax, reducing need for complex SQL.
MySQL is an open-source relational database management system (RDBMS) that is widely used
for web-based applications. It was created by Swedish developers Michael Widenius and David
Axmark in 1995 and is now owned by Oracle Corporation.
MySQL is known for its scalability, reliability, and ease of use. It is used by many popular websites
and applications, including Facebook, Twitter, YouTube, and WordPress. MySQL supports a
variety of programming languages, including PHP, Python, Java, and C++.
Some key features of MySQL include:
11
 Ease of Use: MySQL is easy to install, set up, and use, even for users with limited technical
knowledge.
 High Performance: MySQL is optimized for high performance and can handle large
amounts of data.
 Scalability: MySQL can handle large databases and can be scaled up or down as needed.
 Security: MySQL offers robust security features, including encryption and user
authentication.
3.6 INTERNSHIP PLANNING
3.6.1 Project Development Approach
The software development models are the various processes or methodologies that are being
selected for the development of the project depending on the project’s aims and goals. There are
many development life cycle models that have been developed in order to achieve different required
objectives. The models specify the various stages of the process and the order in which they are
carried out.
The selection of model has very high impact on the testing that is carried out. It will define the
what, where and when of our planned testing, influence regression testing and largely determines
which test techniques to use.
Scrum Methodology
Scrum is an agile development methodology used in the development of Software based on an

iterative and incremental processes. Scrum is adaptable, fast, flexible and effective agile framework
that is designed to deliver value to the customer throughout the development of the project. The
primary objective of Scrum is to satisfy the customer’s need through an environment of
transparency in communication, collective responsibility, and continuous progress.
Scrum Methodology & Process

Scrum is precisely an evolution of Agile Management. Scrum methodology is based on a set of
very defined practices and roles that must be involved during the software development process. It
is a flexible methodology that rewards the application of the 12 agile principles in a context agreed
by all the team members of the product.
12
Figure 3.6.1: Agile Scrum Methodology
Following are the phases of Agile Scrum Methodology:

Scrum is executed in temporary blocks that are short and periodic, called Sprints, which usually
range from 2 to 4 weeks, which is the term for feedback and reflection. Each Sprint is an entity in
itself, that is, it provides a complete result, a variation of the final product that must be able to be
delivered to the client with the least possible effort when requested.
The process has as a starting point, a list of objectives/ requirements that make up the projectplan.
It is the client of the project that prioritizes these objectives considering a balance of the valueand
the cost thereof that is how the iterations and consequent deliveries are determined.
On the one hand the market demands quality, fast delivery at lower costs, for which a companymust
be very agile and flexible in the development of products, to achieve short development cyclesthat
can meet the demand of customers without undermining the quality of the result. It is a very easy
methodology to implement and very popular for the quick results it gets.
Scrum methodology is used mainly for software development, but other sectors are also taking
advantage of its benefits by implementing this methodology in their organizational models such as
sales,
13
3.6.2 Internship Effort and Time, Cost EstimationEffort Estimation
Project Estimation proper evaluation of the system and to get the estimation of the
Project, it was needed to do some metrics calculation for this project. Software project metrics are
the way to do this task efficiently. Project metrics allow knowing the size and complexity of the
project and helping us on the planning and cost estimation.
For this project, function-oriented metrics were used to get the size of the project at the abstract
level (without taking the language in consideration). For that purpose, Function Points (FP)was
used.
Function Points can be counted using the following information domains:
Number of external inputs (EIs) – inputs given by a user or another system
Number of external outputs (EOs) – outputs derived within the system or given toanother
system
Number of external inquiries (EQs) – as an online input that results in generation of some
immediate software response in the form of an on-line output
Number of internal logical files (ILFs) – logical grouping of data that resides with in the
application’s boundary and is maintained via external inputs
Number of external interfaces files (EIFs) - logical grouping of data that residesexternal to
the application but provides data that may be of use to the application
Step 1: You have to compute the count-total which will be used to define the complexity of a
project.
You will do that by completing the table below:

Measurement parameter Count Weighting Resul
factor t
Number of user inputs 3 4 12
Number of user outputs 2 5 10
Number of user inquiries 2 3 6
14
Number of files 1 7 7
Number of external interfaces 2 5 10
Count total= 45
Table 3.6.1 Information Domain Values
Effort Estimation of My Project based on FP:-
Step 2: You have to find the complexity adjustment values based on responses to the
questions below:
1 Does the system require reliable backup and 4

recovery?
2. Are data communications required? 3
3. Are there distributed processing functions? 0
4. Is performance critical? 0
5. Will the system run in an existing, heavily 3

utilizedoperational environment?
6. Does the system require on-line data entry? 5
7. Does the on-line data entry require the input 0

transaction to bebuilt over multiple screens or
operations?
8. Are the master files updated on-line? 0
9. Are the inputs, outputs, files, or inquiries 1

complex?
10 Is the internal processing complex? 1
15
11 Is the code designed to be reusable? 5
12 Are conversion and installation included in the 0

design?
13 Is the system designed for multiple 0

installations in differentorganizations?
14 Is the application designed to facilitate change 5

and ease of useby the user?
Count 27
Table 3.6.2 Value Adjustment Factors (VAF)
FP=Count * [0.65+0.01 * SUM [fi]] FP=Count *[0.65+0.01*27] FP=45*0.92FP=41.40
For this project our FP/pm is 14. Hence we need 3 months to complete the project
Cost Analysis
The cost spent in the making of the project is categorized into two parts:
A.) Direct cost: This is in terms of money. In our project it is the estimated cost of:8 GB RAM
1.5 GHZ PROCESSOR
500 GB FREE SPACE IN HARD DISKDVD WRITER OR USB PORT

1024*768 displaySERVER2008
System study
So cost of this is between 13000 Rs. – 25000 Rs.
B.) Indirect cost:
In my project it is the estimated cost in terms of:
Time spent in system analysis and design Managing time for coding.
Total Person Month Require for the project :-

16
Total Person Month = FP / (FP/pm)
Total Person Month = 41.40 / 14
Total Person Month = 2.957
Round up to 3 person-month.
If we assume cost per person month, says 25000 Rs. , then total cost of the project would be :
Total Indirect Cost = Total Person Months * Cost Per Person Month
Total Indirect Cost = 3 * 25000
Total Indirect Cost = 75000

So Total Cost of the project is 88000 Rs. – 100000 Rs.
3.6.3 Roles and ResponsibilitiesScrum Mater

The person who leads the team guiding them to comply with the rules and processes of the
methodology. Scrum master manages the reduction of impediments of the project and works with
the Product Owner to maximize the ROI. The Scrum Master is in charge of keeping Scrum up to
date, providing coaching, mentoring and training to the teams in case it needs it.
Product Owner
Product is the representative of the stakeholders and customers who use the software. They focus
on the business part and is responsible for the ROI of the project. They translate the vision of the
project to the team, validate the benefits in stories to be incorporated into the Product Backlog and
prioritize them on a regular basis.
Team
A group of professionals with the necessary technical knowledge who develop the project jointly
carrying out the stories they commit to at the start of each sprint.
17
3.6.4 INTERNSHIP SCHEDULING – GANTT CHART
Week 1 2 3 4 5 6 7 8 9 1 1 1
0 1 2
Month
Activity
February March April
Learning
Process
Domain
Understanding
Future Analysis
Design
Coding and
Testing
Documentation
Final
Documentation
Table 3.6.3 Gannt Chart
18
416478 SYSTEM ANALYSIS
4
SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM

4.2 WEAKNESSES OF CURRENT SYSTEM
4.3 REQUIREMENTS OF NEW SYSTEM
4.4 FEASIBILITY STUDY
4.5 SELECTION OF HARDWARE / SOFTWARE
19
4.1 STUDY OF CURRENT SYSTEM
 Fragmented Data Management: The existing system suffers from fragmented data
management, lacking a centralized platform for streamlined communication and collaboration
among users. This decentralized approach results in inefficiencies in managing data and
processes, leading to fragmentation and inconsistencies in data management.
 Insufficient Features: Critical features essential for effective project management are lacking
in the current system. Key functionalities such as task assignment, progress tracking, and
milestone management are either absent or poorly developed, impairing project planning and
execution.
 Poor User Experience: Users encounter usability challenges with the current system due to
its unintuitive interface and navigation. Tasks such as creating and updating projects or
assigning tasks require cumbersome navigation through multiple screens, resulting in user
frustration and decreased productivity.
 Security Vulnerabilities: The current system exhibits vulnerabilities in terms of data security,
raising concerns about unauthorized access and data breaches. Weak authentication
mechanisms and inadequate data encryption protocols pose risks to the confidentiality and
integrity of project-related information stored within the system, necessitating the
implementation of robust security measures.
 Lack of Integration: The existing system lacks integration with external tools and platforms,
hindering seamless collaboration and data sharing across teams. This limitation restricts the
system's ability to leverage the full potential of external resources and tools, impeding project
progress and efficiency.
4.2 WEAKNESSES OF CURRENT SYSTEM
 Lack of Centralization: The current system suffers from a decentralized approach, resulting
in scattered data and communication channels. This fragmentation leads to inefficiencies in
managing project information and collaboration, hindering effective coordination and
decision-making.
 Inadequate Feature Set: Critical features essential for comprehensive project management
20
are either missing or poorly developed in the current system. This limitation undermines the
organization's ability to effectively handle tasks such as task assignment, progress tracking,
and milestone management, impacting project planning and execution.
 Poor User Experience: Users encounter usability challenges with the current system due to
its complex and unintuitive interface. Tasks such as creating and updating projects or
assigning tasks require excessive navigation and manual input, resulting in frustration and
reduced productivity for project managers and team members.
 Security Vulnerabilities: The current system lacks robust security measures, leaving project-
related data vulnerable to unauthorized access and breaches. Weak authentication mechanisms
and inadequate data encryption protocols pose risks to the confidentiality and integrity of
project information, necessitating immediate attention to enhance data security protocols.
 Integration Challenges: The existing system struggles with integration with external tools
and platforms, limiting seamless collaboration and data sharing across teams. This limitation
impedes the system's ability to leverage external resources effectively, hindering project
progress and efficiency.
4.3 REQUIREMENTS OF NEW SYSTEM
4.3.1 Functional Requirement:
Employee Registration and Management: The system should facilitate easy registration of
new users and efficient management of user profiles. HR administrators should be able to add
new users, update existing user information, and maintain accurate user records.
Security and Access Control: Prioritizing data security, the system should implement robust
access controls and encryption protocols to safeguard sensitive information. This includes
authentication mechanisms, role-based access controls, and encryption techniques to ensure data
confidentiality and integrity.
User Interface and Experience: The system should feature an intuitive user interface and
provide a seamless user experience for all stakeholders. This involves designing user-friendly
interfaces, intuitive navigation menus, and responsive layouts to enhance usability and
productivity.
Task Assignment and Management: The system should enable efficient task assignment and
management, allowing administrators to assign tasks to users, track task progress, and monitor
21
task completion status. This includes functionalities for creating tasks, assigning deadlines, and
tracking task dependencies.
4.3.2 Non-Functional Requirement:
 Usability: The system should be user-friendly and easy to navigate, even for non-technical
users.
 Performance: The system should be fast and responsive, even with many users and data.
 Scalability: The system should be scalable and able to handle a growing number of users
and data.
 Security: The system should have robust security features to protect user data and prevent
unauthorized access.
 Reliability: The system should be always reliable and available to users, with minimal
downtime for maintenance.
 Accessibility: The system should be accessible to users with disabilities, including support
for assistive technologies such as screen readers.
 Compatibility: The system should be compatible with various web browsers and mobile
devices to ensure a broad range of users can access the platform.
4.4 FEASIBILITY STUDY
 Feasibility study is the analysis of the problem to determine whether the problem can be
solved more effectively. It is evaluation of proposed projects.
 The result of feasibility study also determines whether the solution for the problem should
be implemented.
 Feasibility study allows determining all positive and negative points of the project.
4.4.1 Technical Feasibility:
 Evaluate compatibility of proposed technologies (Laravel, MySQL) with project

requirements and existing systems.
 Assess availability of skilled personnel proficient in chosen technologies for system
development and maintenance.
 Analyze feasibility of integrating essential functionalities (centralized data management,
time tracking, reporting) within project architecture and timeline constraints.
22
4.4.2 Economical Feasibility:
 Conduct a thorough analysis of the costs associated with developing, implementing, and
maintaining the User Role Permission Module compared to the expected benefits and cost
savings over time. Calculate the return on investment (ROI) and payback period to
determine the financial viability of the project.
 Estimate the total cost of ownership over the lifecycle of the User Role Permission
Module, including development costs, licensing fees, hardware/software costs,
maintenance expenses, and operational costs.
 Estimate the total cost of ownership over the lifecycle of the User Role Permission
Module, including development costs, licensing fees, hardware/software costs,
maintenance expenses, and operational costs.
4.4.3 Operational Feasibility:
 Operational feasibility refers to the nature of solving problems efficiently and it is easy for
the end user to operate it.
 Operational feasibility analysis the behaviour of the proposed system and whether the
proposed system is easier than the existing system for the users of the system.
 Evaluate how well the proposed User Role Permission Module aligns with existing HR
processes and workflows within the organization. Identify areas where the system can
improve efficiency, productivity, and collaboration.
 Assess the level of organizational readiness for adopting the new User Role Permission
Module, considering factors such as user training requirements, change management
strategies, and potential resistanceto change.
4.5 FEATURES OF NEW SYSTEM
 Centralized Project Management Platform : A centralized platform for storing and managing
all project-related information securely.
 User Registration and Management: Intuitive interface for administrators to register new
users, update user profiles, and manage data efficiently.
 Task and Project Management: Tools for creating and managing tasks and projects within the
system, including task assignment, progress tracking, and project timelines.
23
 Time Tracking and Reporting: Features for accurately tracking user time and generating
reports on time spent on tasks and projects.
 Collaboration and Communication: Collaborative tools for facilitating communication and

collaboration among users, including messaging, file sharing, and team collaboration features.
 Performance Evaluation and Feedback:Tools for setting performance goals, conducting

evaluations, and providing feedback to users.
4.6 SYSTEM ARCHITECTURE
 Presentation Layer: The presentation layer of the project is responsible for providing a user-
friendly interface for users to interact with the system. It is built using HTML, CSS, JavaScript,
and jQuery for frontend development. These technologies ensure cross-browser compatibility
and flexibility in designing an intuitive user interface for tasks such as user registration, data
entry, and report generation.
 Application Layer: The application layer handles the processing of business logic within the
system. It receives requests from the presentation layer, processes them, and generates
appropriate responses. Laravel, a PHP framework, is used to build the application layer,
providing a scalable and efficient environment for developing robust web applications. This
layer ensures smooth functioning of features such as user authentication, data validation, and
business rule enforcement.
 Data Layer: The data layer is responsible for managing the storage and retrieval of data within
the system. It utilizes MySQL, a relational database management system, to store and organize
project-related information securely. MySQL ensures data integrity, reliability, and accessibility,
facilitating seamless interaction between the application layer and the underlying database.
Additionally, Eloquent ORM in Laravel simplifies database operations, enhancing the efficiency
of data handling and manipulation.
The system architecture follows the Model-View-Controller (MVC) design pattern, ensuring
separation of concerns and modularity in development. This design pattern promotes scalability,
maintainability, and extensibility of the system, facilitating efficient management of project data
and processes.
24
4.7 SELECTION OF HARDWARE / SOFTWARE
Hardware:
 Server: A robust server is required to host the User Role Permission Module application and
database. A server with at least 8GB RAM, a multi-core processor, and sufficient storage
capacity (e.g., 256GB SSD) is recommended to ensure optimal performance and scalability.
 Network: A reliable and high-speed internet connection is crucial for User Role Permission
Module to support concurrent user access and data transmission.
Software:
 Operating System: The application is designed to be compatible with various operating systems,
including Linux-based distributions such as Ubuntu, Debian, and CentOS, as well as Windows and
macOS.
 Database Management System: MySQL is selected as the database management system for
User Role Permission Module. It is a widely-used open-source relational database system
renowned for its performance, reliability, and scalability.
 Programming Language: Laravel is chosen as the programming language for the application
layer of User Role Permission Module. It provides scalability, asynchronous I/O, and event-
driven architecture, making it suitable for building high-performance networkapplications.
 Framework: Vue.js and jQuery are selected as the frameworks for the presentation layer of
User Role Permission Module. They offer flexibility, ease of development, and compatibility
across various browsers, ensuring a seamless user experience.
 Version Control: Git is the chosen version control system for User Role Permission Module.
It enables collaborative development, code versioning, and codebase management, ensuring
code integrity and facilitating team collaboration.
 Integrated Development Environment (IDE): Visual Studio Code (VS Code) is selected as
the IDE for User Role Permission Module development. It is a lightweight, feature-rich IDE
with built-in support for JavaScript, Vue.js, and Laravel development, providing developers
with tools for efficient coding, debugging, and collaboration.
25
416478 SYSTEM DESIGN
5
SYSTEM DESIGN
5.1 Activity Diagrams

5.2 E-R Diagram
5.3 Use Case Diagram
5.4 Schemas / Database Design
5.5 Data Dictionary
26
5.1 Activity Diagrams
5.1.1 User Activity Diagram
Figure 5.1 User Activity Diagram (4)

27
5.1.2 Admin Activity Diagram
Figure 5.2 Admin Activity Diagram
28
5.2 E-R Diagram
The Entity-Relationship (ER) diagram is a visual representation of the data model that
describes the relationships between different entities within a system. It consists of
entities, which represent real-world objects or concepts, and relationships, which depict
how these entities are related to each other. Entities are represented by rectangles, with
attributes listed inside, while relationships are represented by lines connecting entities,
often with cardinality indicators to specify the nature of the relationship.
Figure 5.3 E-R Diagram (6)
5.3 Use Case Diagram
The use case diagram serves as a visual representation of the system's functionalities from
the perspective of its users and external entities. In this diagram, actors, representing users
or external systems, interact with the system through various use cases, each representing
a specific action or task. Actors are depicted as stick figures, while use cases are
represented by ovals. Associations between actors and use cases illustrate the interactions,
with solid lines indicating primary 29associations. Additionally, include and
extend relationships depict the inclusion of common functionalities across multiple use
cases and optional or exceptional behaviors, respectively.
Figure 5.4 User Use Case Diagram (7)
Figure 5.5 Admin Use Case Diagram (8)
30
5.4 Schemas/ Database Design
Figure 5.6 Activity Logs and Companies (9)
Figure 5.7 Failed Jobs and Meetings (10)
31
Figure5.8 Migrations and Modules (11)
Figure 5.9 Notes and Password Reset Tokens (12)
32
Figure 5.10 Peoples and Permissions (13)
Figure 5.11 Permission Modules and Personal Access Tokens (14)
33
Figure 5.12 Role Permission and Roles (15)
Figure 5.13 User Roles (16)
34
5.4.1 Relationship Diagram of Models
Figure 5.14 Class Diagram (17)
35
5.5 Data Dictionary

Table 5.5.1 Users table
1 Users
Field Datatype is_Null Comments
Id INT No PK, Unique, AI
first_name VARCHAR(64) No
last_name VARCHAR(64) Yes
Email VARCHAR(128) No Unique
phone_number VARCHAR(16) Yes
Address VARCHAR(256) Yes
Password VARCHAR(256) No
is_active TINYINT No O or 1
invitation_token VARCHAR(128) Yes
I=Invited,
Status enum(I,A,R) No A=Accepted,
R=Rejected
Table 5.5.2 Modules table
2 modules
is-
Field Datatype Comments
Null
Code VARCHAR(8) No PK, Unique
Name VARCHAR(64) No
Description VARCHAR(256) Yes
parent_code VARCHAR(8) Yes FK > modules
Table 5.5.3 Permission table
3 permissions
Name VARCHAR(64) No
Description VARCHAR(256) Yes
36
Table 5.5.4 permission_modules pivot table
4 permission_modules
permission_id INT No FK > permissions
module_code VARCHAR(8) No FK > modules
add_access TINYINT No O or 1
view_access TINYINT No O or 1
edit_access TINYINT No O or 1
delete_access TINYINT No O or 1
Table 5.5.5 Roles table
5 roles
Name VARCHAR(64) No
description VARCHAR(256) Yes
Table 5.5.6 role_permissions pivot table
6 role_permissions
role_id INT No FK > roles
permission_id INT No FK > permissions
Table 5.5.7 user_roles pivot table
7 user_roles
user_id INT No FK > users
role_id INT No FK > roles
Table 5.5.8 Peoples table
8 peoples

37
Name VARCHAR(64) No
Designation VARCHAR(64) No
Email VARCHAR(128) No
phone_number VARCHAR(16) Yes
Address VARCHAR(256) Yes
Table 5.5.9companies table
9 companies
PK, Unique, AI, Not

Id INT No
Null
name VARCHAR(64) No
owner_name VARCHAR(64) No
industry VARCHAR(64) No
Table 5.5.10 meetings table
10 Meetings
Title VARCHAR(64) No
description VARCHAR(256) Yes
Date DATE No
Time TIME No
Table 5.5.11 notes table
11 notes
Title VARCHAR(50) No
description VARCHAR(255) No
38
Table 5.5.12 activity_logs table
12 activity_logs
C=Coding, M=Meeting,
Type enum(C,M,P,V) No P=Playing, V= Watching
Video
Log VARCHAR(256) No
39
416478 IMPLEMENTATION
6
IMPLEMENTATION
6.1 IMPLEMENTATION ENVIRONMENT

6.2 SECURITY FEATURE
6.3 CODING STANDARD
6.4 RESULTS
40
6.1 IMPLEMENTATION ENVIRONMENT
The Systems Development Life Cycle (SDLC) is a software engineering framework that is
usedto describe the various phases used to develop an information system.
These phases include planning, analysis, design, development, testing, and implementation.
SDLC environments describe the activities and tools required to perform a particular
processwithin the SDLC.
They are also defined as controlled points where software engineers can carry out
activitiesrelated to development, testing, installation, and configuration.
These environments are associated with the different phases that make up the SDLC. The main
SDLC environments include:
 The analysis and design environment
 The development environment
 The common build environment
 The testing environment, which has two components:
o The systems integration testing environment
o The user acceptance testing environment
 The production environment
The analysis and design environment is aligned to the planning and analysis phases of the SDLC.
In this environment, the main processes that take place include carrying out an in-depth
examination of the current system and the proposed system. The system architecture is also
defined and includes developing the design of the hardware, software, and network requirements
for the system. Within this environment, systems and business analysts work closely with
softwareengineers.
Development & Common Build Environment-
The development environment is aligned to the development phase of the SDLC. This is where
processes related to software development are carried out. The development environment contains
a set of different processes and tools for programming. These are used to develop the final
software.
The development environment can also be a physical space where development takes place and
41
where software engineers interact. Another example of the development environment is the
integrated development environment (IDE). The IDE provides a platform where tools and
development processes are coordinated in order to provide software engineers a convenient way
of accessing the resources they require during the development process.
The common build environment is closely aligned to the development phase of the SDLC. In
this environment, software engineers merge the work done in the development environment.
Within this environment, software engineers build systems. These are used to automate the
processof software compilation.
Testing Environment-
The testing environment is closely aligned to the testing phase of the SDLC. The testing
environment comprises the following components: the System Integration Testing Environment
and the User Acceptance Testing Environment.
Production Environment-
Production is the final environment in your software development process. It is the work that it
ready to be publicly available, and only the most thoroughly tested code should end up here.
While most people associate the production environment with the product being live, this is not
necessarily the case. Until the URL is actually shared with the public, your production site can
instead act as a platform where the public-ready code is kept.
6.2 SECURITY FEATURE
Secure software development includes enabling software security (security requirements

planning, designing a software architecture from a security perspective, adding security features,
etc.) and maintaining the security of software and the underlying infrastructure (source code
review, penetration testing).
Application security is the process of developing, adding, and testing security features within
applications to prevent security vulnerabilities against threats such as unauthorized access and
modification.
Application security is important because today’s applications are often available over various
networks and connected to the cloud, increasing vulnerabilities to security threats and breaches.
There is increasing pressure and incentive to not only ensure security at the network level but also
42
within applications themselves. One reason for this is because hackers are going after apps with
their attacks more today than in the past. Application security testing can reveal weaknesses at the
application level, helping to prevent these attacks.
Different types of application security features include authentication, authorization, encryption,

logging, and application security testing. Developers can also code applications to reduce security
vulnerabilities.
 Authentication:
When software developers build procedures into an application to ensure that onlyauthorized
users gain access to it. Authentication procedures ensure that a user is who they say they are.
This can be accomplished by requiring the user to provide a user name and password when
logging in to an application. Multi-factor authentication requires more than one form of
authentication—the factors might include something you know (a password), something you
have (a mobile device), and something you are (a thumb print or facial recognition.
 Authorization:
After a user has been authenticated, the user may be authorized to access and use the
application. The system can validate that a user has permission to access the application by
comparing the user’s identity with a list of authorized users. Authentication must happen
before authorization so that the application matches only validated user credentials to the
authorized user list.
 Encryption:
After a user has been authenticated and is using the application, other security measures can
protect sensitive data from being seen or even used by acybercriminal. In cloud-based
applications, where traffic containing sensitive data travels between the end user and the
cloud, that traffic can be encrypted to keep the data safe.
 Logging:
If there is a security breach in an application, logging can help identify who got access to the
data and how. Application log files provide a time- stamped record of which aspects of the
application were accessed and by whom.
 Application security testing:

A necessary process to ensure that all of these security controls work properly.
43
6.3 CODING STANDARD
 A coding standard gives a uniform appearance to the codes written by different

engineers.
 It improves readability, and maintainability of the code and it reduces complexity
also.
 It helps in code reuse and helps to detect error easily.
 It promotes sound programming practices and increases efficiency of the programmers.
 The following are some representative coding standards:
Figure 6.3.1: Coding Standard
 Indentation:
Proper and consistent indentation is essential in producing easy to read and maintainable
programs.
Indentation should be used to:
44
o Emphasize the body of a control structure such as a loop or a select statement.

o Emphasize the body of a conditional statement
o Emphasize a new scope block
 Inline comments:
Inline comments analyze the functioning of the subroutine, or key aspects of the algorithm shall
be frequently used.
 Rules for limiting the use of global:

These rules file what types of data can be declared global and what cannot.
 Structured Programming:
Structured (or Modular) Programming methods shall be used. "GOTO" statements shall not be
used as they lead to "spaghetti" code, which is hard to read and maintain, except as outlined line
in the FORTRAN Standards and Guidelines.
 Naming conventions for global variables, local variables, and constant identifiers:
A possible naming convention can be that global variable names always begin with a capital
letter, local variable names are made of small letters, and constant names are alwayscapital letters.
 Error return conventions and exception handling system:

Different functions in a program report the way error conditions are handled should be standard
within an organization. For example, different tasks while encountering an error condition should
either return a 0 or 1 consistently.
6.4 RESULT
The project takes shape during the implementation phase. This phase involves the construction of
the actual project result. Programmers are occupied with encoding, designers are involved in
developing graphic material, contractors are building, the actual reorganisation takes place. It is
during this phase that the project becomes visible to outsiders, to whom it may appear that the
project has just begun. The implementation phase is the doing phase, and it is important to
maintain the momentum.
45
Figure 6.4.1: Login Screen
Figure 6.4.2: Admin Dashboard
46
Figure 6.4.3: Modules Listing screen in Admin Side
Figure 6.4.4:User Add Screen
47
Figure 6.4.5: User Screen with Edit User
Figure 6.4.6: Permission Delete Screen
48
Figure 6.4.7: Forgot Password Screen
Figure 6.4.8: Reset Password Screen
49
Figure 6.4.9: User’s Dashboard Screen
Figure 6.4.10: Edit User Details Screen
50
Figure 6.4.11: User Reset Password Screen
Figure 6.4.12: Meeting Listing Screen
51
Figure 6.4.13: Add Meeting Screen
52
416478 TESTING
7
TESTING
7.1 TESTING PLAN / STRATEGY

7.2 TEST RESULTS AND ANALYSIS
53
416478 TESTING
7.1 TESTING PLAN / STRATEGY
Unit Testing
Ensure the functionality, reliability, performance, and security of the User Role
Permission Module. Develop comprehensive test cases covering all aspects of the User
Role Permission Moddule, including positive and negative scenarios, boundary
conditions, and error handling.
Perform performance testing to evaluate the system's responsiveness, scalability, and

reliability under various load conditions.
Perform penetration testing, vulnerability scanning, and code review to assess the
system's resilience against common security risks such as SQL injection, cross-site
scripting (XSS), and data breaches.
Whenever the application is ready and given to the Test engineer, he/she will start
checking every component of the module or module of the application independently
or one by one, and this process is known as Unit testing or components testing.`
Integration Testing
Data can be across an interface; one module can have an adverse effect on another’s
sub function, when combined may not produce the desired major function; global data
structures can present problems. Integration testing is a symmetric technique for
constructing tests to uncover errors associated with the interface. All modules are
combined in this testing step. Then the entire program was tested as a whole.
Validation Testing
At the culmination of integration testing, software is completely assembled as a

package. Interfacing errors have been uncovered and corrected and the final series of
software test-validation testing begins. Validation testing can be defined in many
ways, but a simple definition is that validation succeeds when the software functions in
a manner that is reasonably expected by the consumer. Software validation is achieved
through a series of black box tests that demonstrate conformity with requirements.
After the validation test has been conducted, one oftwo conditions exists.
54
416478 TESTING
7.2 TEST RESULTS AND ANALYSIS
7.2.1 Test Cases
Table 7.2.1: login Test Table
Step TestStep Test Data ExpectedResult Actual Result Status

(Pass/Fail)
1 Click Login Blank Fields Give the message of Give Validation PASS
Button mandatoryfield message to enter
mandatoryfield
2 All Data would be Enter Email, Give the message of Show a PASS
entered Password Login Successfully dashboard
according to role
Table 7.2.2:Module Test Table

(Pass/Fail)
1 Edit Employee Edit Detail Update data in Module PASS
to Edit Module Module table dataupdated
form
3 Status Changed Click On toggle See Confirmation to Status changed PASS

Module Change status successfully
Table 7.2.3: Permission Test Table

(Pass/Fail)
1 Create Permission Add Details Add Permission data Permission PASS
ils Permission Created displayon
tableand Permission listing
permission_modules
pivot table
2 Edit Permission Click on Edit Permission data Permission PASS
Edit Button ils Permission Updated
andchange the tableand
fields permission_modules
pivot table
55
416478 TESTING
3 Delete Permission Show DeleteDialog Delete Data of Permission PASS
permission from deleted
table and reflect the
change
Table 7.2.3: Role Test Table

(Pass/Fail)
1 Create Role Add Details Add Role datails Role Created PASS
Role tableand displayon Role
user_roles pivot listing
table
2 Edit Role Click on Edit Role datails Role Updated PASS
Edit Button Role tableand
andchange the fields user_roles pivot table
3 Delete Role Show DeleteDialog Delete Data of role Role deleted PASS
from table and
reflect the change
Table 7.2.3: User Test Table

(Pass/Fail)
1 Create User Add Details Add User datails User Created PASS
User tableand displayon Role
user_roles pivot listing
table
2 Edit Role Click on Edit User datails User Updated PASS
Edit Button User tableand
andchange the fields user_roles pivot table
3 Delete User Show DeleteDialog Delete Data of user User deleted PASS
from table and
reflect the change
56
416478 CONCLUSION AND DISCUSSION
8
CONCLUSION AND DISCUSSION
8.1 CONCLUSION
8.2 OVERALL ANALYSIS OF INTERNSHIP
8.3 DATES OF CONTINUOUS EVALUATION (CE-1 ANDCE-1)
8.4 PROBLEMS ENCOUNTERED AND POSSIBLE SOLUTIONS
8.5 SUMMARY OF INTERNSHIP / PROJECT WORK
8.6 LIMITATIONS AND FUTURE ENHANCEMENT
57
416478
8.1 CONCLUSION
In conclusion, the development of our project has resulted in a comprehensive solution that
addresses key challenges and enhances efficiency. Built on a robust architecture, it offers
scalability and security for future growth. Our team's collaborative efforts have been crucial to
its success, and we're grateful for stakeholders' support. As we conclude this phase, we're
committed to continuous improvement and innovation. The project marks a significant step
towards digital transformation, empowering our organization for success in a dynamic
environment. Thank you to everyone involved for their dedication and contribution.
8.2 OVERALL ANALYSIS OF INTERNSHIP
Since the very first day of internship, I started learning a lot of new things from the
respected industry guides and fellow interns.
First of all, the first week was all about project selection. So, discussed about various
domains and technology with the industry mentor
Then, Selected one of the project from the suggested projects by industry mentor. Then
started requirement gathering and analysis about the domain.
Started designing UML diagrams also used some alike commercial domains for the project
to have a better idea about it.
Started planning for the project. Started by designing front-end UI of customer and then
continued by working on its back end.
And likewise continued my work on further modules and learned many new things while
developing the project by self also from the industry mentor.
Had some difficulties in between in development part but the industry mentor was very
supportive and always up for any kind of help.
So, my overall experience during the internship was very fruitful as I got to learn many
new things both on how organization works also on the development part.
58
416478
8.3 PROBLEMS ENCOUNTERED AND POSSIBLE SOLUTIONS
Problem:
Got some difficulty in the database and logic part while working on the project.
Solutions:
Consulted my external guide about the problem and she suggested some changes, after that things
went fine.
8.4 SUMMARY OF INTERNSHIP / PROJECT WORK
During my internship, I had the opportunity to work on various projects and tasks, gaining valuable
experience and skills in Laravel, Vue , MySql , Php . Over the course of 3 months, I actively
contributed to Learning and create projects and collaborated with team and mentors to achieve
project objectives and deliverables..
Throughout the internship, I gained hands-on experience with cutting-edge technologies such as
Php, Laravel, jQuery, and MySQL. I had the opportunity to apply these technologies in real-
world scenarios, enhancing my technical skills and proficiency in web development and database
management.
One of the most rewarding aspects of my internship was seeing the User Role Permission Module
come to life and knowing that my contributions played a part in its success. It was gratifying to
witness the impact of our work on improving employee management processes and facilitating
organizationalefficiency.
8.5 LIMITATIONS AND FUTURE ENHANCEMENT
Limitations:
While the current version of User Role Permission Module is designed to handle a moderate
number of users and data, scalability may become a concern as the organization grows or if there
is a sudden increase in user activity. The system architecture may need to be revisited to ensure
scalability andperformance under heavy loads.
59
416478
Although security measures such as encryption, access controls, and authentication mechanisms
are implemented, there may still be vulnerabilities that could be exploited by malicious actors.
Regular security audits and updates are necessary to identify and address potential security risks.
Integrating User Role Permission Module with existing systems or third-party applications may
present challenges, particularly if there are compatibility issues or data format mismatches.
Close collaboration with IT teams and thorough testing are essential to ensure seamless
integration.
Future Enhancements:
There are several future enhancements that can be made to Team Track to enhance its functionality
and reach. Some possible enhancements include:
 Advanced Reporting and Analytics: Augmenting our system with customizable dashboards,
predictive analytics, and data visualization tools to provide deeper insights.
 User Self-Service Portal: Implementing a user self-service portal to empower users in
managing their information, accessing resources, and initiating requests.
 Enhanced Security Measures: Strengthening security with features like multi-factor
authentication, role-based access control, and data encryption to fortify data protection.
 Workflow Automation: Streamlining HR processes such as onboarding, evaluations, and
payroll through automation tools for increased efficiency.
 Continuous User Experience Enhancement: Iteratively improving the user experience by
gathering feedback, conducting usability testing, and implementing refinements based on
insights.
60
416478
REFERENCES
 J. Resig, “Pro javascript Techniques,” New York, NY, USA: Apress, 2006
 D. Flanagan, “Javascript: The Definative Guide ,” 6th ed. Sebastopol, CA, USA: O’Relly
Media, 2011
 K. Beck, “Test Driven Development: By Example”, Boston, MA, USA:Addison-Wesley
Professional, 2002
 J. Duckett, “HTML and CSS: Design and Build Websites,” Indianapolis, IN, USA: JohnWiley
& Sons, 2011.
 S. McConnell, “Code Complete: A Practical Handbook of Software Construction, ” 2nd ed.
Redmond, WA, USA: Microsoft Press, 2004.
61

Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Report

Uploaded by

Copyright:

Available Formats

User Role Permission Module - CRM

In partial fulfilment for the award of the degree of

Government Engineering College, Modasa

Gujarat Technological University, Ahmedabad

under my guidance in partial fulfillment for the degree of Bachelor of Engineering

in Information Technology, 8th Semester of Gujarat Technological University,

Ahmadabad during the academic year 2023-24.

Prof. N. V. Nagekar Prof. H. R. Patel

Internal Guide Head of the Department

the degree of Bachelor of Engineering in Information Technology to Gujarat

Technological University, Ahmadabad, is a bonofide record of original project

Gujarat Technological University i GEC MODASA

Gujarat Technological University ii GEC MODASA

Figure 1.1 Zignuts Pvt Ltd .............................................................................................. 2

Gujarat Technological University iii GEC MODASA

Gujarat Technological University iv GEC MODASA

Gujarat Technological University v GEC MODASA

List of Figures .....................................................................................................................iii

List of Tables ...................................................................................................................... iv

List of Abbreviations ........................................................................................................... v

Table of Contents ................................................................................................................ vi

Chapter 1 Overview of Company ........................................................................................ 1

1.1 History ........................................................................................................................ 2

1.2 Scope Of Work ........................................................................................................... 2

1.3 Organization Profile ................................................................................................... 3

Chapter 2 Overview of Different Department ..................................................................... 4

2.1.1 Work Carried Out In Each Departments ............................................................. 5

2.1.2 Web Development ............................................................................................... 5

2.1.3 Mobile Application Development ....................................................................... 5

2.1.4 BA Development ................................................................................................. 5

2.1.5 DevOps Development.......................................................................................... 5

2.2 Technical Specifications Of Equipment ..................................................................... 6

2.3 Production Stages ....................................................................................................... 6

Chapter 3 Introduction to Internship Project ....................................................................... 8

3.1 Project Introduction .................................................................................................... 9

3.3 Scope .......................................................................................................................... 9

3.4 Objective .................................................................................................................. 10

3.5 Technology and Literature Review .......................................................................... 10

3.6 Internship Planning…………………………………………………………...…...12

Gujarat Technological University vi GEC MODASA

Chapter 4 System Analysis ................................................................................................ 19

4.1 Study Of Current System ......................................................................................... 20

4.2 Weaknesses of the current system ............................................................................ 20

4.3 Requirements in New System .................................................................................. 21

4.4 Feasibility Study....................................................................................................... 22

4.5 Feature of new System ............................................................................................. 23

4.6 System Architecture ................................................................................................. 24

4.6.1 Agile Development ............................................................................................ 24

4.6.2 Technologies ...................................................................................................... 24

4.7 Selection of Hardware/ Software ............................................................................. 25

Chapter 5 System Design ................................................................................................... 26

5.1 Activity Diagrams .................................................................................................... 27

5.1.1 User Activity Diagram....................................................................................... 27

5.1.2 Admin Activity Diagram ................................................................................... 28

5.2 E-R Diagram ............................................................................................................ 29

5.3 Use Case Diagram .................................................................................................... 29

5.4 Schemas/ Database Design....................................................................................... 31

5.4.1 Relationship Diagram of Models ....................................................................... 32

5.5 Data Dictionary…………………………………………….……………………...36

6.1 Implementation Environment ................................................................................... 41

6.2 Security Feature……………………………………………………………………42

6.3 Coding Standard…………………………………………………………………...44

Chapter 7 Testing ............................................................................................................... 53

FP=Count * [0.65+0.01 * SUM [fi]] FP=Count [0.65+0.0127] FP=45*0.92FP=41.40