Professional Documents
Culture Documents
Knowledge Guidance PDF
Knowledge Guidance PDF
Chandkheda, Ahmedabad
Affiliated
Academic year
(2017-2018)
SSEC,BHAVNAGAR
A PROJECT REPORT
ON
SSEC,BHAVNAGAR
GUJARAT TECHNOLOGICAL UNIVERSITY
CHANDKHEDA AHMEDABAD
SHANTILAL SHAH ENGINEERING COLLEGE
BHAVNAGAR
Certificate
This is to certify that Mr. Rahul mal c . from Shantilal Shah Engineering Collage Bhavnagar
College having Enrollment No: 150433116020 has completed Semester V Project Report having
titleknowledge guidance, in a group consisting of 3 persons under the guidance of the faculty
guide
Date:
SSEC,BHAVNAGAR
GUJARAT TECHNOLOGICAL UNIVERSITY
Enrollment
150433116020
Number
Email ID malrahul60@gmail.com
College Name Shantilal Shah Engineering College, Bhavnagar College Code: 043
Enrollment
Name
Number
Student Team
No one
SSEC,BHAVNAGAR
Acknowledgement
It is a matter of proud and immense pleasure to extend by heartiest thanks to all who provide
assistance me in starting my project on Secure Communication System.
Thank You.
Rahul mal c. (150433116020)
SSEC,BHAVNAGAR
Abstract
I am making this system to share the information which is helpful to all students, research scholar,
PhD scholar, employee, and industrialist.
Through system user can share idea or information can also ask query or problem for any related
subjects. Students or other users post a question or query, search topic, view question, answer to
question and also user can get guidance from author or virtual guidance
This system developed for the guidance to the student teacher, professor also PhD scholar in any
language like .NET, PHP, JAVA, ANDROID.
User register in our system through unique ID and password. user can ask question to other user
and also post project and query or question related to their field. Other
SSEC,BHAVNAGAR
INDEX
SR No. Page No.
1 Introduction 0
I. Project Profile 1
2
II. Purpose
3
III. Scope
2 System Requirement Analysis 4
5
I. Current System Study
6
II. Weakness of Current System
8
IV. Requirement of New System
9
V. Feasibility Study
9
i. - Technical Feasibility
9
ii. - Time Schedule Feasibility
9
iii. – Economical
iv. – Operational 10
11
VI. Development model used
3 System Design 18
………………………………………………………
I. Database Design 19
…………………………….
i. Entity-Relationship Diagram 20
Data Dictionary
21
ii. Canvas Designing
23
iii. GUI Design (Self-Created GUI Screen shot) 27
iv. Canvas Designing
SSEC,BHAVNAGAR
4 Testing 36
Testing Plan 37
Testing Strategy 38
5 II. Conclusion 39
i. Benefit 40
ii. 40
iv. Limitation
vi.
65
SSEC,BHAVNAGAR
1.Introduction
i. Project Introduction
ii. Purpose
iii. Scope
SSEC, BHAVNAGAR 1
INTRODUCTION
i. Project Introduction / Profile
Submitted by:
Rahul mal c.
SSEC, BHAVNAGAR 0
1.2 Purpose
Purpose of developing this system to share the idea to the user in any related subject or their field.
Through system user can get information. If user have any query or question user post the query or
the project to get the information.
1.3 Scope:
System share the information which is helpful to all students, research scholar, PhD scholar,
employee, and industrialist.
SSEC, BHAVNAGAR 1
2.System Requirement Analysis
i. Current System Study
ii. Weakness of Current System
iii. Problem Identification / Definition
iv. Requirement of New System
v. Feasibility Study
a. Technical
b. Economical
c. Operational
d. Schedule(Time)
vi. Development model used (Software
Process Model)
vii. Requirement Validation
viii. Tools and Technology / Minimum
Hardware and Software Requirements
ix. System Architecture
x. Data Flow Diagram
SSEC, BHAVNAGAR 2
i. Current System Study:
SSEC, BHAVNAGAR 3
iv. Requirement of New System
SSEC, BHAVNAGAR 4
v. Feasibility Study
a. Technical Feasibility
Technical feasibility of a project determines whether a project can be developed using the
technology on hand. The system is technically feasible as the front-end and the back-end required
for it is available and already installed.
- During the study it was decided for this application that it will be developed using Visual
studio 2010, SQL Server 2008.
- The selected front – end and back- end are very popular, efficient and available easily from the
internet and are famous for such applications.
- The hardware configuration for this application is not so high and available hardware full fills
the requirements.
- It can be also expanded after development
- Most of the security concepts of our understanding level are included in our GTU syllabus and
we have studied these concepts deeply as possible with the guidance of our college faculties.
- So this application is technically feasible.
b. Economic Feasibility
The tools that will be used for the system are latest one and thus the cost involved in tools,
designing and developing the system will be a good investment for the project.
The benefits of using the system are not in monetary terms, but it increased efficiency of learning.
The modules designed can be easily navigated. The hardware available with us is already the best
available and hence no new purchase is required.
- This application does not require higher economical investments to start working.
- A personal computer which already we have.
- Necessary things for user are computer with installed .Net framework 4.0
- So this application is economically feasible.
SSEC, BHAVNAGAR 5
c. Operational Feasibility
The main purpose of checking operational feasibility is to find out whether the system will be
function after its development and installation or not. During operational feasibility one has to take
care about the system impact on other system and its tendency to fulfill the requirement. It means
that the proposed system should full fill the organization’s requirements while working interfering
to the existing system.
- This application is easy to use and user friendly.
- User does not at all have to learn new things.
- This application can run on any computer in which .Net Framework 3.5 / 4.0 is installed.
- Our system can give knowledge to user in simple terms so any one understands information
security concepts.
- So this application is operationally feasible.
Time feasibility is the period of time within it a software should produce relevant result. Means it
is a time taken to develop a complete product. It's the maximum time software is supposed to do
answer. We can compare two or more software with time feasibility. Software having least time
feasibility will be better one under the same category.
e. Environmental Feasibility
Environmental Feasibility is generally used to show the environment where you work is feasible or
people are inherently resistant to change &computers have been known to facilitate to change.
The system is environmentally feasible because all users are well known & educated.
This system is also easy & used by knowledgeably.
SSEC, BHAVNAGAR 6
vi. Development model used (Software Process Model)
- We want to develop versioning system in which after each cycle we will develop version of
software and then communicate to guide for change and requirements refinements.
- In our project risk is major factor because our project must be secure for communication
- We have studied security topics in our syllabus and some of the features we will study in 6th
semester so risk is major factor so we choose spiral model for the development.
SSEC, BHAVNAGAR 7
vii. Tools and Technology / Hardware and Software Specification
- Technologies used
This project is software that will develop in VB.NET as front end having SQL Server as back end.
1. Database Design (SQL Server)
2. Input Design (isual studio)
3. Coding (VB as Code behind language)
- Hardware Interface
Client Side:
Processor: Any
RAM: 512 MB
Server Side:
Processor: Pentium P4 2.4 Hz as well as core
RAM: 2 GB
Disk space: 160 GB
- Software Interface
SSEC, BHAVNAGAR 8
viii. Requirement Validation
- System must include practice of all types of security well known algorithms
used for encryption and decryption
- System must include hashing technics like MD5, SHA etc.
- System must include demo of brute force attack so any one can understand
that how brute force attack works
- System must include steganography which tries to hide information in the
image format which provides best security then encryption
- System must include password strength analyzer which analyze the strength of
the password and decide its strength
- System must provide secure communication between two users
SSEC, BHAVNAGAR 9
ix. System Architecture
- .
SSEC, BHAVNAGAR 10
x. Data Flow Diagram
The data flow diagrams are pictorial or graphical representation of the outline of the system study.
The data flow diagram covers all the processes and data storage area which takes place during any
transaction in the system. The data flow diagrams are functionally divided into context level, Zero
level and First level data flow diagrams.
2. External Entity: A source or destination of data, which is external to the system. E.g.
Customer etc.
3. A Data Flow: It is packet of data. It may be in the form of document, letter etc.
4. Data store: Any store data but with no reference to the physical method of storing.
SSEC, BHAVNAGAR 11
Level – 0
(Context Diagram)
Login verify
user log into the system through ID and password. admin verify the user ID. And send back with
approved or reject.
Level -1
Login Logout
Search topic
View question
User registered in system. User login to system and add profile , search topic, view question,
answer to question, post query,.
SSEC, BHAVNAGAR 12
3.System Design
i. Database Design
a. Entity-Relationship Diagram
b. Use Case Diagram
c. Data Dictionary
d. Canvas Designing
ii. GUI Design (Self-Created GUI Screen
shot)
SSEC, BHAVNAGAR 13
i. Database Design:
a) ER Diagram
EID
MOB
name addre
s
User system
registered
ID
name
has Account
ID
SSEC, BHAVNAGAR 14
b) Use Case Diagram
user
View question
SSEC, BHAVNAGAR 15
c) Data Dictionary
Login:
Field name Data type(size) Constraint Description
Uid Varcha2(10) Primary key User id
Pwd Varchar(100) Not null User password
Type Varchar(20) Not null Type of depending on his given rights
This table contains the authentication details of user from which system authenticate the user.
Registration:
Field name Data type(size) Constraint Description
Uid Varcha2(10) Primary key Employee id
Uname Varchar(20) Not null Name Of User
Address Varchar(20) Not null User address
Mob no Varchar(20) Not null User Post
email_id Varchar(20) Not null User’s Email_id
This table contains the registration details of user which contains the details of the user.
SSEC, BHAVNAGAR 16
d) Canvas Designing
AEIOU canvas
SSEC, BHAVNAGAR 17
Empathy Mapping
SSEC, BHAVNAGAR 18
Product Development Canvas
SSEC, BHAVNAGAR 19
Ideation Canvas
SSEC, BHAVNAGAR 20
ii. GUI Design
1. Registration Form
This is frist page of our website. This is for new user. There all are required
field. Our system can check password strength take security answer from user.
SSEC, BHAVNAGAR 21
2 sign up
SSEC, BHAVNAGAR 22
3. view profile
SSEC, BHAVNAGAR 23
4. post project
SSEC, BHAVNAGAR 24
5. successfully posted
SSEC, BHAVNAGAR 25
6. admin login
SSEC, BHAVNAGAR 26
7. logout
SSEC, BHAVNAGAR 27
4.Testing
i. Testing Plan
ii. Testing Strategy
SSEC, BHAVNAGAR 28
i) Testing Plan:
A Test Plan is a document detailing the objectives, target market, internal beta team, and processes
for a specific beta test for a software or hardware product. The plan typically contains a detailed
understanding of the eventual workflow.
Master Plan: A single high-level test plan for a project/product that unifies all other test plans.
Testing Level Specific Plan: Plans for each level of testing.
List test deliverables, and links to them if available, including the following:
- Make the plan concise. Avoid redundancy and superfluousness. If you think you do not need a
section that has been mentioned in the template above, go ahead and delete that section in your
test plan.
- Be specific. For example, when you specify an operating system as a property of a test
environment, mention the OS Edition/Version as well, not just the OS Name.
- Make use of lists and tables wherever possible. Avoid lengthy paragraphs.
- Have the test plan reviewed a number of times prior to base lining it or sending it for approval.
The quality of your test plan speaks volumes about the quality of the testing you or your team
is going to perform.
- Update the plan as and when necessary. An out-dated and unused document stinks and is worse
than not having the document in the first place.
SSEC, BHAVNAGAR 29
ii) Testing Strategies:
• A strategy for software testing integrates the design of software test cases into a well-
planned series of steps that result in successful development of the software
• The strategy provides a road map that describes the steps to be taken, when, and how much
effort, time, and resources will be required
• The strategy incorporates test planning, test case design, test execution, and test result
collection and evaluation
• The strategy provides guidance for the practitioner and a set of milestones for the manager
• Because of time pressures, progress must be measurable and problems must surface as
early as possible
• To perform effective testing, a software team should conduct effective formal technical
reviews
• Testing begins at the component level and work outward toward the integration of the
entire computer-based system
• Testing is conducted by the developer of the software and (for large projects) by an
independent test group
• Testing and debugging are different activities, but debugging must be accommodated in
any testing strategy
SSEC, BHAVNAGAR 30
5 Conclusion
.
i. Benefits
ii. Limitations
iii. Future Enhancements
SSEC, BHAVNAGAR 31
Benefits:
Provide information through system any related subjects. Through discussion form user get the
answer for query.
Limitations:
If any unauthorized user registered in system, then he will create the problem like
give wrong answer of the question
If any guide has less knowledge or improper information, then he will not guide in
proper way
Future Enhancements:
References:
www.google.com
SSEC, BHAVNAGAR 32