Full Combined Progress Report

BSHIP (Arya Vysya Business Networking Group) 2020
BSHIP Arya Vysya Business Networking Group

A project submitted to
CHATTISGARH SWAMI VIVEKANAND TECHNICAL

UNIVERSITY BHILAI CHATTISGARH (INDIA)
For the partial fulfilment of degree
MASTER OF COMPUER APPLICATIONS

(MCA)
By
Vidhi Bavaria
Roll No.: 500102118321

Enrollment No.: BG2035
Under the Guidance of

Mr.Benny Verghese
DEPARTMENT OF COMPUTER APPLICTAIONS

BHILAI INSTITUTE OF TECHNOLOGY, DURG
CHATTISGARH (INDIA)
Session : 2017-2020
By- Vidhi Bavaria Page 1

CERTIFICATE OF SUPERVISOR(S)/GUIDE
This is to certify that the work incorporated in the project BSHIP Arya Vysya
Business Networking Group is a record of six month project work assigned by
our institution, successfully carried out by Vidhi Bavaria bearing Enrolment No.:
BG2035 under my guidance and supervision for the award of Degree of Master of
Computer Applications (MCA) of Bhilai Institute of Technology, Durg, C.G.,
affiliated to Chhattisgarh Swami Vivekanand Technical University (CSVTU),
Bhilai, C.G., India. To the best of my knowledge and belief the report embodies
the work of the candidate herself and has duly been successfully completed.
Signature of the Supervisor/Guide

Name: Mr.Benny Verghese
Designation: Associate Professor
Date:
DECLARATION BY THE CANDIDATE
I, Vidhi Bavaria, Student of 6th Semester MCA, Bhilai Institute of Technology,

Durg, C.G., India, bearing Enrolment No.: BG2035 hereby declare that the
project entitled “BSHIP Arya Vysya Business Networking Group” has been
carried out by me under the Guidance of External Guide Dr.Sanjeev Karmakar,
Associate Professor submitted in partial fulfilment of the requirements for the
award of the Degree of Master of Computer Applications (MCA) by the
Chhattisgarh Swami Vivekanand Technical University during the academic year
2015. This report has not been submitted to any other Organization/University for
any award of Degree/Diploma.
Signature of Candidate
Date:
Place:
CERTIFICATE OF FORWARDING
This is to certify that Vidhi Bavaria, a bonafide Student of Master of Computer

Applications (M.C.A.) at Bhilai Institute of Technology, Durg, C.G., India, has
carried out his project work as mentioned in this project entitled “BSHIP Arya
Vysya Business Business Networking Group”, during his sixth semester of
studies in M.C.A. from Chhattisgarh Swami Vivekanand Technical University
(CSVTU), Bhilai, C.G., India to which the institute is affiliated.
This certificate issued by undersigned does not cover any responsibility regarding
the statements made and work carried out by the concerned student.
The current dissertation is hereby being forwarded for evaluation for the purpose
for which it has been submitted.
Signature of Project Coordinator Signature of HOD
Name: Dr.Sanjeev Karmakar Name: Dr.Ramesh Kumar

Designation: Associate Professor Designation: HOD[MCA]
Institution: BIT DURG Institution: BIT DURG
Date: Date:
CERTIFICATE OF APPROVAL
This is to certify that the project the entitled “BSHIP Arya Vysya Business
Networking Group”, carried out by “Vidhi Bavaria” a student of sixth semester,
M.C.A. at Bhilai Institute of Technology, Durg, C.G., India, is hereby
approved after proper examination and evaluation as a creditable work for the
partial fulfilment of the requirement for awarding the degree of Master of
Computer Applications (M.C.A.) from Chhattisgarh Swami Vivekanand
Technical University (CSVTU) , Bhilai , C.G., India.
(Internal Examiner) (External Examiner)

Name: Dr.Sanjeev Karmakar Name:
Designation: Associate Professor Designation:
College Name: BITDURG College Name:
Date: Date:
ACKNOWLEDGEMENT
I have great pleasure in the submission of this project report entitled “BSHIP
Arya Vysya Business Networking Group” for Bhilai Institute of Technology,
Durg, C.G., India, in partial fulfilment of the degree of Master of Computer
Applications. While submitting this project report , I take this opportunity to thank
those directly or indirectly related to project work.
I would like to thank my guide Dr.Sanjeev Karmakar in college who has
provided the opportunity and organizing project for me. Without his active co-
operation and guidance, it would have become very difficult to complete task in
time.
I would like to express sincere thanks to Dr.Arun Arora, Principal, Dr.Ramesh
Kumar, Head of Department (M.C.A.).
While submission of the project, I also like to thanks project coordinator and the
all professors of Bhilai Institute of Technology, Durg, C.G., India, for their
continuous help and guidance throughout the course of MCA.
Acknowledgement is due to our parents, family members, friends and all those
persons who have helped us directly or indirectly in the successful completion of
the project work.
(NAME OF STUDENT)
VIDHI BAVARIA
ABSTRACT
“BSHIP BUSINESS NETWORKING”
BSHIP (Business Support Help Information Promotion) is the first Arya Vysya Network
Organisation, which has successfully bought vysya businessmen together with pride and
integrity. A network that enabling the creation of seamless connectivity with professional
structure of connecting each other.
BSHIP offers referrals, business leads, help, information, practical advice which boost your
business profitability, performance and changed the way we business.
We are the most sought after and respected forum among Arya Vysya’s where entrepreneurs of
integrity and diverse backgrounds openly connect, understand, inspire to do business with one
another. So, let’s begin the part of it and expand your business with proper security.
HARDWARE AND SOFTWARE REQUIREMENTS [Android Studio 3.5]
• RAM - min 4GB , 8GB recommended
• OS - Windows 7 (and above)
• ROM - 2GB
• JAVA - Version 8 (Prerequisite)
Database – SQLite (Room Database) and SQL Server 2014 Management
For Running Application
• Android 5 and above
• RAM - min 512 MB
Guided by : Submitted by :
Mr.Benny Verghese Vidhi Bavaria

a) List of tables
S.No. Name
1 Login Page
2 Home Page
3 View Attendance
4 Update Attendance
b) List of Figures
S.No. Name
1 Class Diagram
2 Event Flow Diagram
3 Data Flow Diagram
4 ER-Diagram
c) List of Abbreviations / symbol
 DFD - Data Flow Diagram

 ER - Entity Relationship diagram
A. Software Requirement Specification
S.No. Content Page No.
1. INTRODUCTION
1.1 Project description 12
1.2 Company profile 12
2. SYSTEM STUDY
2.1 Existing system 12
2.2 Proposed system 13
3. SOFTWARE REQUIREMENT SPECIFICATION
3.1 Introduction 13
3.2.1 Purpose of the SRS
3.2 Overall descriptions 14
3.2.1 Product perspective
3.2.2 Product functions
3.2.3 User characteristics
3.2.4 Constraints, assumptions and dependencies
3.3 Non functional requirements 15
3.3.1 External interface requirement
3.3.2 User interface
3.3.3 Hardware interface
3.3.4 Software interface
3.3.5 Communication interface
3.4 Functional requirements 15-16
3.4.1 Subsystem 1
Functional requirement 1.1
Functional requirement 1.2
…
Functional requirement 1.n
……
3.4.2 Subsystem m
Functional requirement n.1
Functional requirement n.2
3.5 Performance requirements 16

3.5.1 Static performance
3.5.2 Dynamic performance
3.6 Design constraints 16

3.6.1 Standards compliance
3.6.2 Hardware limitations
3.6.3 Reliability and fault Tolerance
3.6.4 Security
B. Detail design
4. SYSTEM DESIGN
4.1 Object/classes model
4.1.1 Data dictionary containing description of class 17-18

attributes
4.1.2 Association between classes 19
4.1.3 Simplifying objects classes using inheritance 20
4.1.4 Group classes into module 21
4.1.5 Object diagram 22
4.2 Dynamic model
4.2.1 Scenario(project interaction sequence) 23
4.2.2 Event flow diagram(EFD) 24
4.2.3 State diagram(SD) for each classes 25
4.3 Functional model
4.3.1 Use case diagram 26
4.3.2 Identification of input/output values 27-28
4.3.3 DFD as needed to show functional dependencies 29-30
4.3.4 Identification of constraints 31
4.4. Database design
4.4.1 Schema description including keys 31
4.4.2 E-R diagram 32

C. Implementation and testing report(C&T)
5. IMPLEMENTATIONS
5.1 Operating system(OS) used(including explanation) 33
5.2 Coding language used(including explanation) 33-34
5.3 RDBMS used 34
5.4 Table relationship diagram 35
5.5 Code description 36
5.6 Input/output interfaces(Screen shots) 37-43
6. SOFTWARE TESTING(Test cases)
6.1 Software testing tools used (if any) 44
6.2 Black-box testing 44
6.2.1 Unit(program) testing 44
6.2.2 Sub-system testing 44
6.2.3 System testing 44-45
6.3 White-box testing 46
6.3.1 Unit(program testing) 46
7. Software costing by using COCOMO Model 47-48
8. Limitation & future Enhancement 49
9. Conclusions 49
10. Bibliography/references 49
A. Software Requirement & Specification

1. INTRODUCTION
1.1 Project Description (Initial Description of the problem)
BSHIP is the first Arya Vysya Business Networking Organization. This was initiated by the
ideology of business networking among Vysya’s to build strong business group by uniting all
business personnel from our Arya Vysya community.
It provides business networking, fellowship, business transactions, business connects, trusted

partners, verified vendors, business collaborations etc. All the BSHIP members meet and
introduce their business, exchange business contacts and referrals. It helps in increasing
business potential among the group and grow much faster.
1.2 Company Profile
Centura Technologies is a Software development and Service based Company. Focused on

solving critical business problems in Retail, Financial Services, Telecommunication, Health
Care and Hi Tech domain. Majorly into Mobile Enterprise solutions and IOT solutions.
Mission & Vision :

Our prime Mission & Vision is “GO SMART”. We are here to tackle and provide solutions for
the Enterprise and End Users. We build our products with an aim to make technology much
simpler which can be used by the consumers of any skill level. Our tagline stands by
"SMARTER WAY TO GROW”.
2. SYSTEM STUDY
2.1 Existing System
The existing system is less sophisticated Graphical User Interface (GUI). In that, there are no
proper methods. Businesses not get profit because they have no proper deals, they do not proper
manage their business.
Systems are not well maintained because they do not have proper techniques and
communication and that is why they cannot enhance their businesses properly in time.
2.2 Proposed System

The proposed system is having many advantages over the existing system. In this, we can easily
obtain the business information from the business networks, transactions, and connects very
easily. It provides new technique to promote our business online and offline. In this way,
members get opportunity to discuss their projects in proper way and techniques so that they can
enhance their business with long terms and securities.
2.3 Feasibility Study

Feasibility study is the process of determination of whether or not a project is worth doing.
Feasibility time constraints and normally culminate in a written and oral feasibility report. The
content SRS of this feasibility study helped us as a sound basis deciding how to proceed.
Feasibility study should be performed on the basis of various criteria and parameters which are :
 Technical Feasibility
Technical feasibility deals with the technology used in the system. It deals with the hardware
and software used in the system whether they are of latest technology or not. This system uses
window platform, Room Database as front end technology and SQL as backend technology.
 Economic Feasibility
Economic analysis is the most frequently used method for evaluating the effectiveness of a new
system more commonly known as cost/benefit analysis, android studio 3.5.
 Operational Feasibility
Operational feasibility describes the feasibility of the product to be operational. The project has
been implemented such that is easier for business with computer and technical knowledge to
operate it. This software is very user friendly and requires technician to operate.
3. SOFTWARE REQUIREMENT SPECIFICATION (SRS)

3.1 Introduction
3.1.1 Purpose of the SRS
The main purpose of SRS is that it will provide a detailed description of the requirements for
the Business Support Help Information Promotion (BSHIP) system.
This SRS will allow for a complete understanding of what is to be expected of the system to be
constructed. The clear understanding of the system and its functionality will allow for the
correct software to be developed for the end user and will be used for the development of the
future stages of the project. This SRS will provide the foundation for the project. From this
SRS, the BSHIP system can be designed, constructed, and finally tested.
3.2 Overall Description

3.2.1 Product Perspective
This product perspective is the Software Requirement Specification for the BSHIP for business
enhancement with proper securities. The purpose of this is to describe the functionality,
requirements and general interface of our project.
3.2.2 Product Function

 It provides the user a membership id for login.
 It provides all business details like connects, transactions, ec member list, member list,
hub it, meeting dates, events, bship policy, location and performance of user.
 It provides user performance also for greater deals.
3.2.3 User Characteristics

To use this software user have the knowledge of business. They should know about the proper
deals and transactions. And the most important is how to communicate with people for expand
their business in proper way and long term with proper securities.
3.2.4 Constraints, assumptions and dependencies

 Software Constraints
1. The system will run under windows 7.
2. The system must have android studio.
 Hardware Constraints
1. Minimum 4 GB RAM
2. Intel core i5 processor
 Assumptions and Dependencies

1. Users will be having a valid membership id and phone to access the software.
2. Complete training is provided to all end users to handle the product.
3. The software would not take into account the business impact i.e., the risks associated with
constraints imposed by the management .
3.3 Non Functional Requirements

3.3.1 External Interface Requirement
All the interactions of the software with people, hardware, and other software should be clearly
specified and for the user interface, the characteristics of each user interface of the software
product should be specified.
3.3.2 User Interface
The interface will be in the browser with good internet connectivity. It is designed business
purpose. Here we deals with various connections with proper securities.
3.3.3 Hardware Interface

 Processor : Intel core i5
 Processor Speed : 1.90 GHz or above
 RAM : 4GB, 8GB.
 Disk Space : 1 TB
3.3.4 Software Interface

 Operating System : Windows 7
 Client Side : Java, XML
 Server Side : JSON, Room Database, SQL Server MS
3.3.5 Communication Interface

This project supports all type of web browser.
3.4 Functional Requirements

3.4.1 Login : User have to login through email / phone and password with membership id.
3.4.2 Homepage : Here user can update his profile and different grids are there like connects,
transactions, ec member list, member list, hub it, meeting dates, events, bship policy, location
and performance of user.
3.4.3 Connects : User can build various connections through different hubs and members.
3.4.4 Transactions : User can perform various deals through different members.
3.4.5 Member and EC Member List : Provides the list of the members and ec members.
3.4.6 Hub IT : User can interact with different it hubs.

3.4.7 Meeting Dates : Provides user fixed meeting date for business deals.
3.4.8 Events : User can perform in various events for business expand in long term .
3.4.9 BSHIP Policy : User has to follow some rules and regulations under this policy.
3.4.10 Location : Provides user proper location for business deals.
3.4.11 Performance : Here user can view their performance of their business with well security.
3.5 Performance Requirements

3.5.1 Static Performance
In this system, users have to register with member id and it supports n number of users to access
the system with same time from anywhere .
3.5.2. Dynamic Performance

The dynamic performance of the system is not applicable.
3.6 Design Constraints

3.6.1 Standards Compliance
The system shall be built using Microsoft's API standards and MySQL to store the database and
here we perform various operations like connects, transactions, ec member list, member list,
hub it, meeting dates, events, bship policy, location and performance of user.
3.6.2 Hardware Limitations

The system which are using having Intel core i5 1.90 GHz processor, 8 GB RAM and 1 TB disk space.
3.6.3. Reliability and Fault Tolerance

In this system, we have recovery technique by storing the backups of database in the server.
3.6.4. Security
In this system, only the member have the authority to access and deals with the various
connections with long term and securities.
B. Detail Design
4. SYSTEM DESIGN
4.1 0bject/classes model
4.1.1 Data dictionary containing description of class attributes (data members
and methods)
Table: User Login
Fields Data Type Description Range
Registration_id Integer Provides the id -2,147,483,648 to

+2,147,483,647
Email / Phone Varchar (20) Provides Email / Phone 0 to 8000 char
for login
Password Varchar (20) Provides Password for 0 to 8000 char

successful login
Table: Home Page

Connects Varchar Two types connects 0 to 65,535 char
and myconnects
Transactions Varchar Two types transactions 0 to 65,535 char
and mytransactions
EC Member List Varchar List of the ec members 0 to 65,535 char
Member List Varchar List of the members 0 to 65,535 char
Hub IT Varchar List of the various IT 0 to 65,535 char

Hubs
Meeting Dates Integer Details of meeting 0 to 65,535 char
dates
Events Varchar Details of various 0 to 65,535 char
events
BSHIP Policy Varchar Details of BSHIP 0 to 65,535 char
Policy
Location Varchar Provides proper 0 to 65,535 char

location
My Performance Varchar Provides user 0 to 65,535 char
performance
Table: View Attendance

Start_date Date Starting date of the 1000-01-01 to 9999-

meeting 12-31
End_date Date End date of the 1000-01-01 to 9999-
meeting 12-31
Member name and Varchar Provides member name 0 to 65,535 char
Presence and presence
Member name and Varchar Provides member name 0 to 65,535 char
Absence and absence
Table: Update Attendance

Member List Varchar Provides names of the 0 to 65,535 char

members
4.1.2 Association between classes
Registered User Homepage
Email ID : Varchar Connects : Varchar

Phone : Integer Transactions : Varchar
EC Member List : Varchar
Member List : Varchar
HUB IT : Varchar User Profile
Meeting Dates : Integer Change Password : Integer
Events : Varchar Renew : Varchar
BSHIP Policy : Varchar View Contacts : Integer
Location : Varchar Publish Ads : Varchar
My Performance : Varchar
Admin View Receipt : Varchar
Email ID : Varchar
Phone : Integer
Connects
Connects : Varchar
My Connects : Varchar
View Attendance Update Attendance
Date of joining : Integer Member List : Varchar

End of joining : Integer
Member name and presence :Varchar
Member name and absence : Varchar
4.1.3 Simplifying object classes using Inheritance
User Admin
Login
Email ID
Contact Number
4.1.4 Group classes into module
“BSHIP BUSINESS NETWORKING”
Login
 User first login

 User have to take membership id for registration.
 User then have to fill email / phone and password for next page.
Home Page
 First user can edit their profile like change password, add meeting dates and publish ads.
 Then user has different fields like connects, transactions, ec member list, member list, hub
it, meeting dates, events, bship policy, location and performance.
View Attendance
 User can view date of joining and date of ending.

 User can view members name with their presence and absence.
Update Attendance
 User can update attendance by viewing member list.

4.1.5 Object diagram
Registration User Detail

User BSHIP Admin
Successful Response
4.2 Dynamic model
4.2.1 Scenario (Project Interaction)
User Admin User Profile Connections View Attendance Update Attendance
Login Verification
Return Status
Change Password
Return Status
Add Meeting Dates
Return Status
Publish Various Ads
Return Status
Select Hub and Member
Return Status
View total Connections received
Return Status
View Date of Joining and Ending
Return Status
View total Member Presence and Absence
Return Status
Update Members List
Return Status
Logout
4.2.2 Event Flow Diagram (EFD)
Start
Requires No
Login directly by Contact Number
Membership ID ?
Yes
Homepage
Connections User Profile
Connects directly by Name No Requires

Hub and
Member ?
Yes Total Connections Received
View Attendance
End
4.2.3 State Diagram (SD) for each class
Login
Check User Profile Select Connections
Select Hub and Member
Connections Received
Logout
4.3 Functional Model
4.3.1 Use case diagram
Login
Registration
Add Business Details
Edit User Profile
Make Connections
Add Hub and

Members Admin
User
View Connections
Received
View Attendance
Logout
4.3.2 Identification of Input/ Output values
Login
Input Description Constraints

Register User have to register with It must contain predefined
registration id for signin characters.
Email / Phone User email or phone must be It must contain 20 character
type alpha numeric including 1 special character
Password User password must be type of It must contain & character with
alpha numeric 1 special character.
Homepage

Connects Provides various connections of It must contain predefined
members characters
Transactions Provides transactions of It must contain predefined
business deals characters
EC Member List View the list of the ec members It must contain predefined
characters
Member List View the list of the members It must contain predefined
characters
Hub IT Provides information of It must contain predefined
different IT Hubs characters
Meeting Dates Provides particular dates of It must contain predefined
meetings characters
Events Performance of different fields It must contain predefined
characters
BSHIP Policy Describes the policy in detail It must contain predefined
characters
Location Provides fixed location It must contain predefined
characters
My Performance Describes user performance It must contain predefined
characters
View Attendance

Start Date Start date of the meetings It contain 10 digits
End Date End date of the meetings It must be 10digits
Member name & presence Provides name and presence of It must contain predefined
member characters
Member name & absence Provides name and absence of It must be predefined characters
member
Update Attendance

Member List List of the members It must be predefined characters
4.3.3 DFD as needed to show functional dependencies
0 – Level DFD
Registration User Detail

User Admin
BSHIP
Successful Response
1– Level DFD
Login for Admin

Membership ID
Response
Login View
View
Connections Details Homepage
User
View
Check total
Connections received User Performance
View
View
attendance User Profile
of User
4.3.3. Identification of constraints
 primary key
 foreign key
4.4 Database Design
4.4.1 Schema description
S.No ClassName Constant Method / Function Purpose

1 User User_id Add() User first have to
Email / Phone Search() take membership
Password Select() id and login with
email / phone and
password
2 Homepage User Profile Search() User here edit

User Connections, Select() their profile and
User Transactions deals with various
Member List connections
Location, Meeting
Dates, Events
User Performance
3 View Attendance Date of Search() User can view

joining Date Select() date of joining
of ending User and ending and
Presence User member presence
Absence and absence
4.4.2 E-R Diagram
Member List
Transactions
EC Member List
Email / Phone Password
Meeting Dates
Connects
User Login Homepage Hub It
My Performance Events
Registration
Location
BSHIP Policy
Admin
User Profile
Change Password View Receipt
Renew Publish Ads
View Connects
Connects
Connects My Connects
Date of joining Date of ending

Select Hub Select Member
Connections Received
C. Implementation and Testing Report(C&T)

5. IMPLEMENTATIONS
5.1 Operating system(OS) used
Windows 7 and above can be used as which is an operating system for computers. It is more
reliable, compatible and fast. It supports virtual hard disks, improved performance on multi-core
processors, improved boot performance, direct access and kernel improvements. Its action
centre encompasses security and maintenance of the computer. In this way, it is most usable and
better operating system with proper security and maintenance.
5.2 Coding language used
Client Side
1. Java : Java is the technology of choice for building applications using managed code that
can execute on mobile devices. The android platform allows developers to write managed code
using java to manage and control the android device. Android applications can be developed by
using the Java programming language and the Android SDK.
The mobile edition of java is called Java ME. Java ME is based on Java SE and is supported by
most smartphones and tablets. The Java Platform Micro Edition (Java ME) provides flexible,
secure environment for building and executing applications that are targeted at embedded and
mobile devices. The applications that are built using Java ME are portable, secure and can take
advantage of the native capabilities of the device.
2. XML : Android provides a straightforward XML vocabulary that corresponds to the view
classes, such as those for widgets and layouts. It allows you to separate the presentation of your
app from the code that controls its behaviour. Using XML files also makes easy to provide
different layouts for different screen sizes and orientations. .
Server Side
1. JSON : JSON stands for JavaScript Object Notation. It is structured, light weight, human
readable and easy to prase. It is a best alternative to XML when our android app needs to
interchange data from server. It is shorter, quicker and easier way to interchange our data.
Android provide us four different classes to manipulate JSON data. These classes are
JSONObject, JSONArray, JSONString and JSONTokenizer. In this way JSON is very usable
and quicker format to be used in api connectivity with proper security.
2. Room Database : Room provides an abstraction layer over SQLite to allow fluent database
access while harnessing the full power of SQLite. There are three major components of room:
i) Entity : It represents a table within the database.

ii) Database : It is an abstract class where we define all our entities.
iii) DAO : It contains the methods used for accessing the database.
2. SQL Server MS : SQL Server is an integrated environment for managing any SQL
infrastructure, from SQL Server to Azure SQL database. It provides tools to configure, monitor,
and administer instances of SQL Server and database.
In this way we use SQL Server to query, design, upgrade the data-tier components used by our
applications and manage our databases properly and with security.
5.3 Relational Database Management System(RDBMS) used
This is an RDBMS based project which is currently using SQL Server MS for all the transaction
statements. SQL Server MS is a Microsoft product. RDBMS is a database management system
that is based on the relational model. It become a predominant choice for the storage of
information in new databases used for financial records, manufacturing, personnel data, and
much more.
Relational database have often replaced legacy hierarchical databases and network databases
because they are easier to understand and use. However, relational databases have been
challenged by object databases, which were introduced in an attempt to address the object-
relational impedance mismatch in relational database, and XML databases.
5.4 Table relationship diagram
Registered User Homepage
Email ID : Varchar Connects : Varchar

Phone : Integer Transactions : Varchar
EC Member List : Varchar
Member List : Varchar
HUB IT : Varchar User Profile
Meeting Dates : Integer Change Password : Integer
Events : Varchar Renew : Varchar
BSHIP Policy : Varchar View Contacts : Integer
Location : Varchar Publish Ads : Varchar
My Performance : Varchar
Admin View Receipt : Varchar
Email ID : Varchar
Phone : Integer
Connects
Connects : Varchar
My Connects : Varchar
View Attendance Update Attendance
Date of joining : Integer Member List : Varchar

End of joining : Integer
Member name and presence :Varchar
Member name and absence : Varchar
5.5 Code Description
Subsystem 1 : Admin
File No. Source file name Description LOC
1. Login.java Admin have to login first and do their 121

further process
2. Connects.java After successful admin login, admin 250

add hub and member details
3. Update_Attendance.java After proper adding admin update the 139
attendance of members
Subsystem 2 : User
File No. Source file name Description LOC
1. Login.java User have to register first by taking 100

membership id and then can siginin
2. Homepage.java User edit their profile and and can view 250
the business details
3. Connects.java User connects with various hub and 270
members with proper details
4. EC_Member_List.java User view the list of the ec members 200
5. Member_List.java User view the list of the members 200
6. Meeting_Dates.java User choose the meeting dates for their 100

business deals
7. User_Perforamance.java User see their performance in detail 178
with proper security
8. View_Attendance.java User view the attendance of all the 189
business members
5.6 Input/Output Interfaces(Screenshots)
User Login
Homepage
Connects
Member & EC Member List

Meeting Dates
User Performance
View & Update Attendance

6. SOFTWARE TESTING(Test Cases)

6.1 Software testing tools used (if any)
System verification testing is the highest test level; it is also usually the one with the fewest
requirements remaining to be verified. Only those requirements relating to subsystem
interactions, quantity of field devices, external interfaces, and system performance should
remain to be formally verified. System acceptance testing is performed after all lower level
testing has been successfully completed. It is performed in the operational environment using all
available and previously installed and tested system hardware and software.
6.2 Black Block Testing

This method enables the software engineer to device set of input techniques that fully exercise
all functional requirements for a program . Black Box tests the input, the output and the external
data. It checks whether the input data is correct and whether we are getting the desired output.
6.2.1 Unit(Program) testing

Unit testing tests the minimal software component, or module. Each unit (basic component) of
the software is tested to verify that the detailed design for the unit has been correctly
implemented. In an object-oriented environment, this is usually at the class level, and the
minimal unit tests include the constructors and destructors.
6.2.2 Sub-System testing

Any testable collection of objects, components, and modules . It is executable and testable as a
whole. It implements a cohesive set of responsibilities. It does not provide all of the
functionality of the application under test
6.2.3 System testing

It is executing programs to check logical changes made in it with intention of finding errors. A
system is tested for online response, volume of transaction, recovery from failure etc. System
testing is done to ensure that the system satisfies all the user requirements. System testing is
series of different tests whose primary purpose is to fully exercise the computer based system.
Although each test has a different purpose, all the work should verify that all system elements
have been properly integrated and perform allocated functions.
There are essentially three kinds of system testing :
i) Alpha Testing: Alpha testing refers to the system testing carried out by the test team within
the development organization.
ii) Beta Testing: Beta testing is the system testing performed by a select group of friendly
customers.
iii) Acceptance Testing: Acceptance testing is the system testing performed by the customers
to determine whether to accept or reject the delivery of system.
S.No. Name of page Purpose Input Output
1. Home.java Display the overall view All the details Redirect to

of BSHIP Business Grid of BSHIP the admin
information page
2. Login.java Membership id, email id Membership Login
and password for check id, email id successfully
credential and password
3. Connects.java Display the various Connection Connects
connections of members details successfully
4. EC_Member_List.java Display the list of the ec EC Member List

members List details successfully
5. Member_List.java Display the list of the Member List List
members details successfully
6. Meetings_Dates.java Particular meeting date Meeting date Meeting
provides for transaction details successfully
7. User_Performance.java Performance of user in User User details
detail Performance successfully
8. View_Attendance.java Display the particular Display the Member
meeting date and member members presence
list attendance successfully
9. Update_Attendancde.java Update attendance of Display the Updation
the members update successfully
attendance
6.3 White Box Testing
White Box Testing is defined as the testing of a software solution's internal structure, design,
and coding. In this type of testing, the code is visible to the tester. It focuses primarily on
verifying the flow of inputs and outputs through the application, improving design and usability,
strengthening security. White box testing is also known as Clear Box testing, Open Box testing,
Structural testing, Transparent Box testing, Code-Based testing, and Glass Box testing. It is
usually performed by developers.
White box testing involves the testing of the software code for the following:
 Internal security holes

 Broken or poorly structured paths in the coding processes
 The flow of specific inputs through the code
 Expected output
 The functionality of conditional loops
 Testing of each statement, object, and function on an individual basis
The testing can be done at system, integration and unit levels of software development. One of
the basic goals of white box testing is to verify a working flow for an application.
6.3.1 Unit Testing
It is often the first type of testing done on an application. Unit testing is performed on each
unit or block of code as it is developed. Unit Testing is essentially done by the programmer. As
a software developer, you develop a few lines of code, a single function or an object and test it
to make sure it works before continuing Unit Testing helps identify a majority of bugs, early in
the software development lifecycle. Bugs identified in this stage are cheaper and easy to fix.
7. SOFTWARE COSTING BY COCOMO MODEL
COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. Any of the
three forms can be adopted according to our requirements. These are types of COCOMO model:
1. Basic COCOMO Model
2. Intermediate COCOMO Model
Estimation of Effort: Calculations –
1. BASIC MODEL
E = a(KLOC)b
The above formula is used for the cost estimation of for the basic COCOMO model, and also is
used in the subsequent models. The constant values a and b for the Basic Model for the different
categories of system:
Software Projects A B C D
Organic 2.4 1.05 2.5 0.38
Semi Detached 3.0 1.12 2.5 0.35
Embedded 3.6 1.20 2.5 0.32
The effort is measured in Person-Months and as evident from the formula is dependent on Kilo-
Lines of code. These formulas are used as such in the Basic Model calculations, as not much
consideration of different factors such as reliability, expertise is taken into account, henceforth
the estimate is rough.
Model Used: Organic
Formula Used:
Effort = 2.4(KLOC)1.05
Time = 2.5(Effort).38
People = Effort/Time
Calculating Total Lines Of Code (LOC) :
Page Name Number of Lines Of

Code(LOC)
Login.java(Admin) 121
Login.java(User) 100
Homepage.java 250
Connects.java(Admin) 250
Connects.java(User) 270
EC_Member_List.java 200
Member_List.java 200
Meeting_Dates.java 100
User_Performance.java 178
View_Attendance.java 189
Update_Attendance.java 139
Total 1997
Estimating Effort
:
Effort = 2.4(1997)1.05
Effort = 7008.22 PM
Estimating Time
:
Time = 2.5(7008.22)0.38
Time = 72.32 Months
People required
:
P = 7008.22/72.32
P = 96.90 PM
8. LIMITATIONS & FUTURE TESTING
Limitations
 This application is only for business people.

 It reduces the manual process, time and human effort.
 It reduces the multiple registration of a member.
 Admin manages data about business.
 One time only one member can register.
Future Enhancement
 The scope of this project BSHIP business grid is that it takes the entrepreneurs &
business community is here together, as one able platform that helps you to network,
collaborate and grow, fact that they provide best-in-class product and services.
 BSHIP strives to enhance your business by building your network. It helps you to
achieve your long term goals by connecting you with the quality business professionals.
9. CONCLUSIONS
This system has been developed successfully and the performance of the system has been
found satisfactory. Member should have registration id to connect with people. This system will
provide the ease of handing the business related things that extend the network.
10. BIBLIOGRAPHY/REFERENCES
1. www.abhiandroid.com
2. www.tutorialspoint.com
3. www.javatpointandroid.com
Comment of guide (Satisfactory / Not Satisfactory) :-
Remark (if any)
Name and Signature of Candidate Signature of Guide
Comment of Coordinator
Remark (if any)
Signature of Project Coordinator
Name : Dr. Sanjeev Karmakar

Department of Computer Applications
Bhilai Institute of Technology, Durg

Full Combined Progress Report

Uploaded by

Document Information

Original Description:

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

Full Combined Progress Report

Uploaded by

Copyright:

Available Formats

BSHIP (Arya Vysya Business Networking Group) 2020

BSHIP Arya Vysya Business Networking Group

CHATTISGARH SWAMI VIVEKANAND TECHNICAL

MASTER OF COMPUER APPLICATIONS

Roll No.: 500102118321

Under the Guidance of

DEPARTMENT OF COMPUTER APPLICTAIONS

By- Vidhi Bavaria Page 1

Signature of the Supervisor/Guide

DECLARATION BY THE CANDIDATE

I, Vidhi Bavaria, Student of 6th Semester MCA, Bhilai Institute of Technology,

This is to certify that Vidhi Bavaria, a bonafide Student of Master of Computer

Signature of Project Coordinator Signature of HOD

Name: Dr.Sanjeev Karmakar Name: Dr.Ramesh Kumar

(Internal Examiner) (External Examiner)

“BSHIP BUSINESS NETWORKING”

HARDWARE AND SOFTWARE REQUIREMENTS [Android Studio 3.5]

• RAM - min 4GB , 8GB recommended

• OS - Windows 7 (and above)

• JAVA - Version 8 (Prerequisite)

Database – SQLite (Room Database) and SQL Server 2014 Management

For Running Application

• Android 5 and above

• RAM - min 512 MB

Mr.Benny Verghese Vidhi Bavaria

2 Event Flow Diagram

3 Data Flow Diagram

c) List of Abbreviations / symbol

 DFD - Data Flow Diagram

A. Software Requirement Specification

S.No. Content Page No.

1.1 Project description 12

1.2 Company profile 12

2.1 Existing system 12

2.2 Proposed system 13

3. SOFTWARE REQUIREMENT SPECIFICATION

3.5 Performance requirements 16

3.6 Design constraints 16

4.1 Object/classes model

4.1.1 Data dictionary containing description of class 17-18

4.1.3 Simplifying objects classes using inheritance 20

4.1.4 Group classes into module 21

4.1.5 Object diagram 22

4.2 Dynamic model

4.2.1 Scenario(project interaction sequence) 23

4.2.2 Event flow diagram(EFD) 24

4.2.3 State diagram(SD) for each classes 25

4.3 Functional model

4.3.1 Use case diagram 26

4.3.2 Identification of input/output values 27-28

4.3.3 DFD as needed to show functional dependencies 29-30

4.3.4 Identification of constraints 31

4.4. Database design

4.4.1 Schema description including keys 31

4.4.2 E-R diagram 32

C. Implementation and testing report(C&T)

A. Software Requirement & Specification

It provides business networking, fellowship, business transactions, business connects, trusted

1.2 Company Profile

Centura Technologies is a Software development and Service based Company. Focused on

Mission & Vision :

2.2 Proposed System