A

PROJECT REPORT
ON

“NSERVICES24”
Submitted
To

“ SURESH GYAN VIHAR UNIVERSITY “

JAIPUR,302017

As A Partial Fulfilment for the Degree Of

MASTERS OF COMPUTER APPLICATION
(M.C.A.)

ACADEMIC YEAR: 2020-21

SUBMITTED BY:-
PATIL KALPESH MANOJ
( ROLL NO :- 1839868)

:: SURESH GYAN VIHAR UNIVERSITY ::

Jaipur,302017
 ACKNOWLEDGEMENT
It was a highly eventful Session at the Suresh Gyan Vihar University ( S. G. V. U)
working with highly developed Computer Teacher and will probably remain the
most memorable experience of our lives. Hence it is pleasure to acknowledge
out obligation to all those who were directly to indirectly involved in our
project work and were immense help us to successfully complete this project.

We also humbly thankful to our Principal Dr.Shruti Tiwari and our course
ordination for their valuable suggestions & co-ordination in developing our
project. We would like to thank our Internal guide Prof. Snehal Ukirade for her
valuable assistance & guidance imported which has enable us to complete this
documentation according to prescribed standards of Suresh Gyan Vihar
University.

From :- Patil Kalpesh

 DECLARATION

This project report on “ Online News Management System “ submitted to Suresh

Gyan Vihar University, Surat In partial fulfillment of the requirements for the
degree of Master Of Computer Application ( M. C. A).

This project report is entirely an outcome of my own effort It is not been

submitted either in part or in whole by any Other to any institution or any other
degree. The sources
From where the data has been collected have been duly Acknowledged.

KALPESH MANOJ PATIL

 PREFACE

It is great pleasure for as student of Suresh Gyan Vihar University to prepare a

project on “Online News Management System” for the partial fulfillment of the
requirements of the degree of Master Of Computer Application ( M. C. A).

As a student of computer field, we are encouraged by growth and rapid

development in the software industries, Keeping in mind that increase demand
for software and software engineers the University has arranged project Work for
third year.

Thus it is our model and obligatory duty to take project as a part of our studies
with great enthusiasm and seriousness. For this we have gone through a
development program of 3 months.
 2. Current /Existing System
Study
2.1 MAJOR COMPONENTS
2.2 MINIMUM HARDWARE / SOFTWARE CONFIGURATION
2.3 DRAWBACKS OF EXISTING SYSTEM
2. 1 Major Components
In each and every system there is a particular system component through the system is
running till now. All system has common component like maintain Service Provider details
and User information.
Here Admin can have the authorization to see the all Service Provider and user details in
website.

2.2 Minimum Hardware / Software Configuration

 Hardware Requirement:

Processor Pentium IV Processor And Onward

Ram 256 MB or Higher

HDD 20 GB or Higher

 Software Requirement:

Front-End ASP.NET

Back-End MS SQL Server

Operating System Windows7 , Windows8 , Windows10

2.3 Drawbacks of existing system
 Manual work for Service Provider and User.
 Time consuming.
 Cost effective.
 Difficult to collect information related to Services.
 Lack of Security.
 Limited information sharing Services.
 3. Propose Project Profile

3.1 INTRODUCTION
3.2 OBJECTIVE
3.3 SCOPE
3.4 TYPE OF PROJECT
3.5 TECHNOLOGIES
3.6 APPLICABILITY OF THE SYSTEM
3. 1 Introduction
 It can be accessed from website and android application
 This project is based on C2C [Customer to Customer]
 Here user can easily get services from service Providers
 Users and Service Providers can make their profiles
 Users and service providers can update their profile from website and application
 User can easily get the nearest available service.
 Admin can access all the information of users and service Providers

3.2 Objective
 Users can easily get any local service whichever would be available in the
nearest area
 Users do not need to go elsewhere to find out to a service provider.
 Users can easily contact any service provider, at any time and at anywhere.
 Here service providers can easily get work.
 To help communicate users and service providers
 Service providers can easily earn money by getting work

3.3 Scope

 To store information of Users and Service Providers

 User can send a request to Service providers
 Service providers will get the notification of request sent.
 Service provider will be able to accept or cancel a request
 Users can check the status of the request
3. 4 Type of Project

Creating Website and Android Application to provide the facilities to user:

 Website and android application to help the people to get Local services.

 To help the people getting best services.

 It can be accessed from any browser connectivity with the internet.

3.5 Technology /

Environments MVCFramework-

Introduction

The Model-View-Controller (MVC) is an architectural pattern that separates an application

into three main logical components: the model, the view, and the controller. Each of these
components are built to handle specific development aspects of an application. MVC is one
of the most frequently used industry-standard web development framework to create scalable
and extensible projects.

MVC Components

Following are the components of MVC –

Model
The Model component corresponds to all the data-related logic that the user works with. This
can represent either the data that is being transferred between the View and Controller
components or any other business logic-related data. For example, a Customer object will
retrieve the customer information from the database, manipulate it and update it data back to
the database or use it to render data.

View
The View component is used for all the UI logic of the application. For example, the
Customer view will include all the UI components such as text boxes, dropdowns, etc. that
the final user interacts with.

Controller
Controllers act as an interface between Model and View components to process all the
business logic and incoming requests, manipulate data using the Model component and
interact with the Views to render the final output. For example, the Customer controller will
handle all the interactions and inputs from the Customer View and update the database using
the Customer Model. The same controller will be used to view the Customer data.
ASP.NET MVC
ASP.NET supports three major development models: Web Pages, Web Forms and MVC
(Model View Controller). ASP.NET MVC framework is a lightweight, highly testable
presentation framework that is integrated with the existing ASP.NET features, such as
master pages, authentication, etc. Within .NET, this framework is defined in the System.
Web. Mvc assembly. The latest version of the MVC Framework is 5.0. We use Visual
Studio to create ASP.NET MVC applications which can be added as a template in Visual
Studio.

ASP.NET MVC Features

ASP.NET MVC provides the following features −

 Ideal for developing complex but lightweight applications.

 Provides an extensible and pluggable framework, which can be easily replaced and
customized. For example, if you do not wish to use the in-built Razor or ASPX View
Engine, then you can use any other third-party view engines or even customize the
existing ones.

 Utilizes the component-based design of the application by logically dividing it into

Model, View, and Controller components. This enables the developers to manage the
complexity of large-scale projects and work on individual components.

 MVC structure enhances the test-driven development and testability of the

application, since all the components can be designed interface-based and tested
using mock objects. Hence, ASP.NET MVC Framework is ideal for projects with
large team of web developers.
  Supports all the existing vast ASP.NET functionalities, such as Authorization and
Authentication, Master Pages, Data Binding, User Controls, Memberships,
ASP.NET Routing, etc.

 Does not use the concept of View State (which is present in ASP.NET). This helps in
building applications, which are lightweight and gives full control to the developers.

Android (Operating System)

Android is a mobile operating system developed by Google. It is based on a modified
version of the Linux kernel and other open source software, and is designed primarily for
touchscreen mobile devices such as smartphones and tablets. In addition, Google has further
developed Android TV for televisions, Android Auto for cars, and Wear OS for wrist
watches, each with a specialized user interface. Variants of Android are also used on game
consoles, digital cameras, PCs and other electronics.
Android Activity Lifecycle
Initially developed by Android Inc., which Google bought in 2005, Android was unveiled in
2007, with the first commercial Android device launched in September 2008. The operating
system has since gone through multiple major releases, with the current version being 9
"Pie", released in August 2018. Google released the first Android Q beta on all Pixel phones
on March 13, 2019. The core Android source code is known as Android Open Source Project
(AOSP), and is primarily licensed under the Apache License.
Android is also associated with a suite of proprietary software developed by Google, called
Google Mobile Services (GMS) that very frequently comes pre-installed in devices, which
usually includes the Google Chrome web browser and Google Search and always includes
core apps for services such as Gmail, as well as the application store and digital distribution
platform Google Play, and associated development platform. These apps are licensed by
manufacturers of Android devices certified under standards imposed by Google, but AOSP
has been used as the basis of competing Android ecosystems, such as Amazon.com's
Fire OS, which use their own equivalents to GMS.

Android has been the best-selling OS worldwide on smartphones since 2011 and on tablets
since 2013. As of May 2017, it has over two billion monthly active users, the largest installed
base of any operating system, and as of December 2018, the Google Play store features over
2.6 million apps.

Feature of Android

1) Near Field Communication (NFC)

Most Android devices support NFC, which allows electronic devices to easily interact across
short distances. The main aim here is to create a payment option that is simpler than carrying
credit cards or cash, and while the market hasn’t exploded as many experts had predicted,
there may be an alternative in the works, in the form of Bluetooth Low Energy (BLE).

2) Alternate Keyboards
Android supports multiple keyboards and makes them easy to install; the SwiftKey, Skype,
and 8pen apps all offer ways to quickly change up your keyboard style. Other mobile
operating systems either don’t permit extra keyboards at all, or the process to install and use
them are tedious and time-consuming.

3) Infrared Transmission
The Android operating system supports a built-in infrared transmitter, allowing you to use
your phone or tablet as a remote control.

4) No-Touch Control
Using Android apps such as Wave Control, users can control their phones touch-free, using
only gestures. Have messy hands but need to turn off your screen or change a song? Simple.
This could prove especially useful if you’re driving, so you can keep both eyes on the road.

5) Automation
The Tasker app lets you not only control app permissions but also automate them. Do you
only want your location services to be active during the day? Want to create a customized
way to start your music—for example, with a voice command and at a certain volume?
Tasker can help.
6) Wireless App Downloads
Accessing app stores on any mobile device can be frustrating, but iOS makes it a little more
difficult—download an app on your computer, and it won’t sync to your mobile device until
you plug in and access iTunes. Using the Android Market or third-party options like
AppBrain, meanwhile, let you download apps on your PC and then automatically sync them
your Droid, no plugging required.
7) Storage and Battery Swap
Android phones also have unique hardware capabilities. Google’s OS makes it possible to
remove and upgrade your battery or to replace one that no longer holds a charge. In addition,
Android phones come with SD card slots for expandable storage.
8) Custom Home Screens
While it’s possible to hack certain phones to customize the home screen, Android comes with
this capability from the get-go. Download a third-party launcher like Nova, Apex or Slide and
you can add gestures, new shortcuts, or even performance enhancements for older-model
devices.
9) Widgets
Apps are versatile, but sometimes you want information at a glance instead of having to open
an app and wait for it to load. Android widgets let you display just about any feature you
choose, right on the home screen—including weather apps, music widgets, or productivity
tools that helpfully remind you of upcoming meetings or approaching deadlines.
10) Custom ROMs
This is a big one. Because the Android operating system is open source, developers can
tweak the current OS and build their own versions, which users can download and install in
place of the stock OS. Some are filled with features, while others change the look and feel of
a device. Chances are if there’s a feature you want; someone has already built a custom ROM
for it.
3.6 Applicability of the system
Viewing available near services and User can send the request to the Service Provider at
anytime and anywhere

Service Provider can have the authorize to accept or cancel the request

Service provider can get the notification for new request which send by user
 4. Software Analysis
4.1 PRELIMINARY INVESTIGATION
4.2 PROBLEM IDENTIFICATION
4.3 FEASIBILITY STUDY
4.3.1 TECHNICAL FEASIBILITY
4.3.1 TECHNICAL FEASIBILITY
4.3.2 ECONOMICAL FEASIBILITY
4.3.3 OPERATIONAL FEASIBILITY
4.3.4 MANAGEMENT FEASIBILITY
4.3.5 TIME FEASIBILITY
4.4 REQUIREMENT ANALYSIS
4.4.1 FACT FINDING TECHNIQUES
4.4.2 TIME LINE CHART
4.4.3 MODEL WITH JUSTIFICATION
4.4.4 FLOW CHART
4.4.5 DFD AND/OR UML
4.4.6 PROCESS / CONTROL SPECIFICATION
4.4.7 DATA DICTIONARY
4.1 Preliminary Investigation
In our case as we were developing Nservices24 (Locale Services) site it provides answers of
questions like.

1) What is the basic functionality of Website and Android application?

2) How can you establish communication?
3) What kind of functionality should be developed to make the access easy to use
for both User and Admin?
4) How can we build attractive site so that more and more users can join this Website
and Android application?

4.2 Problem Identification

Definition of the Problem:

To create or develop new system first we have to study the [C2C] Customer to
Customer system, analysis difficult problem faced by the operator of that system.
System analysis therefore understands such problems and proposes a new system in
which the above problems are rectified.

4.3 Feasibility study

The main purpose of feasibility analysis is to check the economic viability of the purpose
system. The result of the feasibility study will indicate whether to proceed with the
proposed system or not. If the results of the feasibility study are positive, then we can
proceed to develop a system otherwise the project should not be perused.

4.3.1 Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes
the following: -

 Does the necessary technology exist to do what is suggested?

 Do the proposed equipment have the technical capacity to hold the data required
to use the new system?
  Will the proposed system provide adequate response to inquiries, regardless of
the number of locations of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability ease of access and
data security?

4.3.2 Economical feasibility

Proposed system requires development tools and software such as visual studio 2017 Express
and Android Studio and for developing purpose system, we need various resources such as
computer systems, internet connection for e-help, recommended disk space and memory
speed as mentioned in technical requirement.

We have many benefits from proposed system such are

 As existing system is manual, where data may not accurate, up-to-date available on
time. But proposed will be computerized, so we can overcome all limitations of
existing system.

This system will reduce the paperwork and quality of data will be improved.

4.3.3 Operational Feasibility

 Users of the system will be registered as a user of the website and Android
Application by the Services Provider or Service getter department of the Website and
App.
 Here there are two types of users 1. Services Provider 2. Services Getter

4.3.4 Management Feasibility

 Management feasibility is not coming in basic feasibility of system.

 It’s arise and aspects of management use. Here all level of management revise all
related basic feasibilities and know the require of that all, after that all manager gives
their decision for those feasibility to use or not.

4.3.5 Time Feasibility

  Time feasibility describes the time cost for converting the present system to new
system.
 As an aspect of time feasibility our system takes 3 months for completion. This
system is developed under the time period of just 3 months. So we can say that this
system is time feasible.

4.4 Requirement Analysis

4.4.1 Fact Finding Techniques

Record Review:-

 As we have started this project from the scratch; there were no previous
records or documentation available therefore no record review has being done
for our project.
 But our project guide made it a point to conduct a project status meeting every
week; just to know the status of the project.
 In this meeting we have the opportunity to present our ideas and innovations
in front of our project manager; which were later discussed in the meeting and
further decision were taken on the same. At the end of every meeting a MOM
(minutes of meeting) is prepared.
 Minutes of meeting is the careful recording of a meeting, i.e., the writing of
minutes, is an essential part of meeting though it involves time and expense
even after the meeting has ended.
 There are no strict rules in writing minutes. Minutes may be written in detail
or in brief depending on the anticipated readership. But the main element are
always the same (sometimes some of them are omitted):
 4.4.2 Time Line Chart

Index Month1 Month2 Month3

1. Information gathering & scheduling
1.1 Meeting Conducted
1.2 Information Collecting about system
1.3 Identified Needs and project constraint
Milestone: Information gathering completed
2. Scope & Planning
2.1 Problem Specification
2.2 Feasibility Study
2.3 Risk Analysis
2.4 Scheduling Chart
Milestone: Scope & planning completed
3. Scope & Planning
3.1 Database Design
3.2 Data Dictionary
3.3 Data Flow Diagram
Milestone: Design completed
4. Coding
4.1 Coding of Admin Module
4.2 Coding of User Module
4.3 Coding of Service Provider
Milestone: Coding completed
5. Testing
5.1 Testing All Module
5.2 Integration Testing
5.3 System Testing
Milestone: Coding completed
4.4.3 Model with Justification

SDLC- IterativeModel

In the Iterative model, iterative process starts with a simple implementation of a small set of
the software requirements and iteratively enhances the evolving versions until the complete
system is implemented and ready to be deployed.

An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part of the
software, which is then reviewed to identify further requirements. This process is then
repeated, producing a new version of the software at the end of each iteration of the model.

Iterative Model - Design

Iterative process starts with a simple implementation of a subset of the software

requirements and iteratively enhances the evolving versions until the full system is
implemented. At each iteration, design modifications are made and new functional
capabilities are added. The basic idea behind this method is to develop a system through
repeated cycles (iterative) and in smaller portions at a time (incremental).

The following illustration is a representation of the Iterative and Incremental model −

Iterative and Incremental development is a combination of both iterative design or iterative

method and incremental build model for development. "During software development, more
than one iteration of the software development cycle may be in progress at the same time."
This process may be described as an "evolutionary acquisition" or "incremental build"
approach."

In this incremental model, the whole requirement is divided into various builds. During each
iteration, the development module goes through the requirements, design, implementation
and testing phases. Each subsequent release of the module adds function to the previous
release. The process continues till the complete system is ready as per the requirement.

The key to a successful use of an iterative software development lifecycle is rigorous

validation of requirements, and verification & testing of each version of the software against
those requirements within each cycle of the model. As the software evolves through
successive cycles, tests must be repeated and extended to verify each version of the
software.

Iterative Model - Application

Like other SDLC models, Iterative and incremental development has some specific
applications in the software industry. This model is most often used in the following
scenarios
−

 Requirements of the complete system are clearly defined and understood.

 Major requirements must be defined; however, some functionalities or

requested enhancements may evolve with time.

 There is a time to the market constraint.

 A new technology is being used and is being learnt by the development team
while working on the project.

 Resources with needed skill sets are not available and are planned to be used
on contract basis for specific iterations.

 There are some high-risk features and goals which may change in the future.

Advantages of Iterative Model:

It is extremely necessary to know the advantages of the Iterative model, before implementing
it in the Software Development Life Cycle (SDLC). The biggest advantage of this model is
that, it is implemented during the earlier stages of software development process, which
allows developers and testers to find functional or design related flaws as early as possible,
which further allows them to take corrective measures in a limited budget. Other benefits or
advantages of this model are:

 Some working functionality can be developed and early in the software development
life cycle (SDLC).

 It is easily adaptable to the ever changing needs of the project as well as the client.

 It is best suited for agile organisations.

 It is more cost effective to change the scope or requirements in Iterative model.

 Parallel development can be planned.

 Testing and debugging during smaller iteration is easy.

 Risks are identified and resolved during iteration; and each iteration is an
easily managed.

 In iterative model less time is spent on documenting and more time is given
for designing.

 One can get reliable user feedback, when presenting sketches and blueprints of
the product to users for their feedback.

Disadvantages of Iterative Model:

Even though, iterative model is extremely beneficial, there are few drawbacks and
disadvantages attached to it, such as, each phase of an iteration is rigid with no overlaps.
Also, system architecture or design issues may arise because not all requirements are
gathered in the beginning of the entire life cycle. Other disadvantages of iterative model are:

 More resources may be required.

 Although cost of change is lesser, but it is not very suitable for

changing requirements.

 More management attention is required.

 It is not suitable for smaller projects.

 Highly skilled resources are required for skill analysis.

 Project progress is highly dependent upon the risk analysis phase.

  Defining increments may require definition of the complete system.

4.4.4 Flow Chart

Flowchart is a diagrammatic representation of an algorithm. Flowchart are very helpful in

writing program and explaining program to others.

Symbols Used In Flowchart

Different symbols are used for different states in flowchart, For example: Input/output
and decision making has different symbols. The table below describes all the symbols that are
used in making flowchart.

Symbol Purpose Description

Flow line Used to indicate the flow of logic by connecting symbols.

Terminal(Stop/Start) Used to represent start and end of flowchart.

Input/output Used for input and output operation.

Processing Used for arithmetic operations and data-manipulations.

Used to represent the operation in which there are two

Decision
alternatives, true and false.

On-page Connector Used to join different flow line

Off-page Connector Used to connect flowchart portion on different page.

4.4.5 UML Diagram

What is UML Diagram?

UML is a way of visualizing a software program using a collection of diagrams. The notation
has evolved from the work of Grady Booch, James Rumbaugh, Ivar Jacobson, and the
Rational Software Corporation to be used for object-oriented design, but it has since been
extended to cover a wider variety of software engineering projects. Today, UML is accepted
by the Object Management Group (OMG) as the standard for modeling software
development.

Types of UML Diagrams

The current UML standards call for 13 different types of diagrams: class, activity, object, use
case, sequence, package, state, component, communication, composite structure, interaction
overview, timing, and deployment.
These diagrams are organized into two distinct groups: structural diagrams and behavioral or
interaction diagrams.
Structural UML Diagrams

 Class diagram
 Package diagram
 Object diagram
 Component diagram
 Composite structure diagram
 Deployment diagram

Behavioural UML Diagrams

 Activity diagram
 Sequence diagram
 Use case diagram
 State diagram
 Communication diagram
 Interaction overview diagram
 Timing diagram
Use Case Diagram for Admin
Use Case Diagram for User
Use Case Diagram for Service Provider
Sequence Diagram for Admin Login
Sequence Diagram for User Login
Sequence Diagram for User Register
Sequence Diagram for Send Request
Sequence Diagram for Update Profile
Activity Diagram for Admin
Activity Diagram for User
1.1

5.1
Activity Diagram for Service Provider
2.1
3.1
4.4.6 Process / Control Specification

Registration for user

User Login
4.4.7 Data Dictionary

1) Data Dictionary for Admin

Data Data Store
Name tblAdmin
Alias Admin
When to used and For Admin Login.
How to used
Description Id--> It is used to unique id for admin.
Username-> For Username.
Password-> For Password.

2) Data Dictionary for User

Data Data Store

Name tblRegistration
Alias User Registration
When to used and For User Login and Registration.
How to used
Description User_id--> It is used to unique id for User.
Name-> For Name.
Mobile-> For Mobile.
Email-> For Email.
City-> For City.
State-> For State.
Token-> For Token.
Profile-> For Profile.
DateTime-> For DateTime.
CheckServices->For Check user is Service Provider or not.
Password-> For Password.
3) Data Dictionary for Service Provider

Data Data Store

Name tblServicePro
Alias Service Provider Registration
When to used and For Service Provider Login and Registration.
How to used
Description Service_id --> It is used to unique id.
Name-> For Name.
Mobile-> For Mobile.
Email-> For Email.
City-> For City.
State-> For State.
ServiceType->This is for service name.
Des->For Description.
Token-> For Token.
Profile-> For Profile.
DateTime-> For DateTime.
 5. Software Design
5.1 PROJECT DESIGN PROCESS HIERARCHY
5.2 DATABASE DESIGN
5.2.1 JUSTIFICATION OF NORMALIZATION
5.3 ARCHITECTURAL DESIGN
5.4 SECURITY ISSUES
5.5 QUALITY / RELIABILITY MEASURES
5.6 SYSTEM MAP
5.1 Project Design Process Hierarchy
5.2 Database Design
TABLE NO: - 1

TABLE NAME: - tblRegister

PURPOSE: -This table is for User Register.

Sr. No Field Type Length Key/constraint Description

1 User_id bigint Primary key For Unique User

id.
2 Name nvarchar 50 Not null For User name.

3 Email nvarchar 50 Not null For Email.

4 Mobile nvarchar 50 Not null For User Mobile

Number.
5 Password nvarchar 50 Not null For User
Password.
6 Token nvarchar MAX Null For Notification.

7 Check_service_provider nvarchar 2 Null Check User is

Service Provider
or Not.
8 RegisterDateTime DATE Null Register Date
and Time.
9 Image nvarchar MAX Null For User Profile.
TABLE NO: - 2

TABLE NAME: - tblServiceprovider

PURPOSE: - This table is for Service Provider Register.

Sr. No Field Type Length Key/constraint Description

1 Service_id Bigint Primary key For Unique Service

Provider id.
2 Name nvarchar 50 Not null Service provider name.

3 Mobile nvarchar 12 Not null Mobile Number.

4 Email nvarchar 50 Not null For Email.

5 Address nvarchar MAX Not null For Address.

6 City nvarchar 50 Not null For Get City.

7 State nvarchar 50 Not null For Get state.

8 Servicetype nvarchar 50 Not null Get the Service type.

9 Description nvarchar MAX Not null For Description.

10 Latitude nvarchar 50 Not null For Service provider

Latitude.
11 Longitude nvarchar 50 Not null For Service provider
Longitude
12 DateTime DATE Null Register Date and Time.

14 Ratting nvarchar 50 Null Service provider Rating.

15 Available status nvarchar 10 Not null Service Provider available

or not.
TABLE NO: -3

TABLE NAME: - tblAdmin

PURPOSE: -This is Admin table for admin login.

Sr.No Field Type Length Key/constraint Description

1 Id bigint Primary key User id

2 Username nvarchar 50 Not null For Username.

3 Password nvarchar 50 Not null For Password.

5.2.1 Justification of Normalization

→ It is a process of converting a relation to a standard form. The process is used
to handle the problems that can arise due to data redundancy i.e. repetition of
data in the database, maintain data integrity as well as handling problems that
can arise due to insertion, updating, deletion anomalies

Insertion anomaly: - Inability to add to the database to absence of other data.

Deletion anomaly: - Unintended loss of data due to deletion of data.

Update anomaly: - Data inconsistency resulting from data redundancy and partial update
Normal Forms: - These are the rules for structuring relations that eliminate anomalies .

First Normal Form:

→ A relation is said to be in first normal form if the values in the relation are
atomic for every attribute in the relation . By this we mean Simply that no
attribute value can be a set of values or, as it sometimes expressed , a
repeating group.

Second Normal Form:

→ A relation is said to be in second normal form is it is in first normal form and it
should satisfy any one of the following rules :
 → Primary Key is not a composite primary Key
→ No non key attribute are present
→ Every non key attribute is fully functionally depended on full set of primary key

Third Normal Form :

→ A relation is said to be in third normal form if there exits

no transitive dependencies.

Transitive Dependencies :-

If two non key attributes depend on each other as well as on the primary key
then they are said to be transitively dependent .
The above normalization principles were applied to decompose the data in
multiple tables. Thereby making the data to be maintained in a consistent state .

5.3 Architectural Design

When you making design of a system, it is more necessary to develop the
architecture design of the system. Which is useful for now basic flow and the detailed.

Design Flow
Architecture with Data Design:
In this design we describe all the aspects to related to external data and entities for
the software to be built. Here, we consider the data connected resources with our system
and connection with the database.
In architectural data design, we follow the two abstraction: -
 High level abstraction (Data abstraction):
Data abstraction is the collection of data that describes the data objects like
name, weight, dim, etc.

 Architecture with data flow:

In this architectural design, consider the data flows of the system. For
knowing the flow of the system. We , consider some phases of the analysis
 like data flow diagram and process specification which gives the detail
transaction and transform flow.

 Mapping with architectural Design:

Software requirements can be mapped into various representation of data

model. The architectural design considers the various mapping flow for
developing a good and attractive design of the system.

5.4 Security Issues

While an internet website is accessible primarily to select individual, an internet web
site is accessible to millions of users all over the world never to use clear text passwords to
protect sensitive information distributed to and from an internet websites. When
distributing sensitive information via the internet, configure your website to encrypt the
data.
ASP.NET, in conjunction with Microsoft internet information services (IIS), can
authenticate users credential such as names and passwords using any of the following
authentication methods.

 Windows: Basic, digest, integrated windows authentication (NTLM or Kerberos).

 Forms authentication, in which you are login page and manage authentication in
your application.
 Microsoft Password Authentication.
 Client Certificate Authentication.

ASP.NET membership supports facilities

for:

 Creating new users and passwords

 Storing membership information like user name, password, supporting data
in Microsoft SQL server, Active Directory or alternate data stores.
 Integrates with the ASP.NET personalization and role management System.

Connecting to SQL server using Integrated Security

You should connect to computers running SQL server using integrated security to
avoid the possibility to your connection string being compromised and your user id and
password being exposed. When you specify a connection that users integrated security to
connect to a computer running SQL server, the membership features reverts to the identity
of the process, you should ensure that the identity of the process running ASP.NET(For
example, the application pool ) is the default process account or a restricted user account.

SQL Server Express Worker Process Identity

 SQL server Express 2008 includes a new mode of operation where it can start a
worker process running as the identity of the connecting user. This capability is referred to
as “run as faster” mode. Although this mode of operation is suitable for desktop
development while using IIS, starting worker processes is not appropriate on web servers
hosting multiple, entrusted customer code bases. Shared hosting servers that contain
application that do not trust each other should explicitly disable the “run as user”
functionality, this functionality can be turned off by connecting to the SQL expressinstance.

Securing Against Denial of Service Attacks

Method that performs updates or large search operation can reduce the responsiveness of
your membership data source if called concurrently by a number of clients. To reduce
exposure to a denial of service attack, restrict access to ASP.NET pages that use methods
that perform database updates or search to administrative users, and expose only ASP.NET
pages that provides validation and password management for general use.

5.5 Quality / Reliability Measures.

To produce high quality software is a goal to develop the software with all kinds of
the satisfaction with user cost and assurance also with developers.
If requirement is not considered or gathered properly then the lack of adaption or
confirmation to requirement is also lack of quality.so to build quality software first we
define and consider the meaningful and useful requirement.
To develop quality software, we must compare our software with some known data. So for
that we measure or software in 3 different division
→ Software Operation
→ Software Revision
→ Software Transition

 Software Operation

In this we define the quality with correction, reliability, usability, efficiency and
integrity.
In our system there are many different modules and submodules are exists and to
manage their quality we follow all above factors.
 Correction:

In any changes occur in our module then we easily correct them. So

the quality of those module become as usual and not decrease.
  Integrity :

If all module are completed successfully then we integrate them and

manage the quality of all those modules.

5.6 System Map

 6. Software Coding
6.1 Tools & Techniques
6.2 Result Snapshot
6.1 Tools & Techniques

Title Description
Front End ASP.NET MVC (C#)
Android

Back End SQL Server 2012

Other Tools JavaScript, CSS, Bootstrap, JQuery,
Google API, Firebase API, Web API,
JSON.

Support Browser Chrome, Microsoft Edge, Mozilla, etc.

Operating System Windows XP, Windows 7,8,10
Website

User Registration

User Login
Service Provider Registration

Service Provider
Service Provider List
 7. Software Testing
7.1 TEST CASES & TEST DATA DESIGN
7.2 OUTPUT COMPARISON
7.3 TESTING STRATEGIES
7.4 UNIT TESTING
7.5 INTEGRATION TESTING
7.6 SYSTEM TESTING
7.7 ALPHA TESTING
 7.1 Test Cases & Test Data Design

Test ID Input Expected Remarks Actual Remarks

1 Correct username & System, should accept It. Get login User
password of Student.

2 Incorrect username & System should reject It. Invalid username or

password of Student. password.

3 Correct username & System should accept It. Get login of admin.
password of admin.

4 Incorrect username & System should reject It. Invalid username or

password of Company. password

5 User keeps blank fields for System should give User not gets registered.
registration. warning to fill blank fields.

6 Admin keeps blank fields System should give Admin not gets Login.
for Login. warning to fill blank fields.

7.2 Output Comparison

Generally testing is used to compare all the aspects related to input , output validation. Etc.
but most important comparison is the output comparison for user satisfaction and for
develop use full website

We performed different testing to compare the many requirements and constraint related
to the system. we compare many outputs and data with predefined document and the user
satisfaction.

7.3 Testing Strategies

A testing strategy is a general approach to the testing process rather than a method of
devising particular system or component tests. Different testing strategies may be adopted
depending on the type of system to be tested and the development process used. There are
two different strategies available: Top-Down Testing and Bottom-Up Testing.
In Top-Down Testing, high levels of a system are tested before testing the detailed
components. The application is represented as a single abstract component with sub-
components represented by stubs. Stubs have the same interface as the component but very
limited functionality.

After the top-level component has been tested, its sub-components are implemented and
tested in the same way. This process continues recursively until the bottom - level
components are implemented. The whole system may then be completely tested. Top-down
testing should be used with top-down program development so that a system component is
tested as soon as it is coded. Coding and testing are a single activity with no separate
component or module testing phase.

If top-down testing is used, unnoticed design errors may be detected at an early stage in the
testing process. As these errors are usually structural errors, early detection means that
extensive re-design re-implementation may be avoided. Top-down testing has the further
advantage that we could have a prototype system available at a very early stage, which itself
is a psychological boost. Validation can begin early in the testing process as a demonstrable
system can be made available to the users.

Bottom-Up Testing is the opposite of Top-Down. It involves testing the modules at the
lower levels in the hierarchy, and then working up the hierarchy of modules until the final
module is tested. This type of testing is appropriate for object-oriented systems in that
individual objects may be tested using their own test drivers. They are then integrated and the
object collection is tested.

7.4 Unit Testing

UNIT Testing is defined as a type of software testing where individual units/ components of
a software are tested.

Unit Testing of software applications is done during the development (coding) of an

application. The objective of Unit Testing is to isolate a section of code and verify its
correctness. In procedural programming, a unit may be an individual function or procedure.
Unit Testing is usually performed by the developer.

In SDLC, STLC, V Model, Unit testing is first level of testing done before integration testing.
Unit testing is a WhiteBox testing technique that is usually performed by the developer.
Though, in a practical world due to time crunch or reluctance of developers to tests, QA
engineers also do unit testing.

7.5 Integration Testing

Integration Testing is defined as a type of testing where software modules are integrated
logically and tested as a group.

A typical software project consists of multiple software modules, coded by different

programmers. Integration Testing focuses on checking data communication amongst these
modules.

Hence it is also termed as 'I & T' (Integration and Testing), 'String Testing' and sometimes
'Thread Testing'.

→ Top-down integration testing:

Testing takes place from top to bottom, following the control flow or architectural
structure (e.g. starting from the GUI or main menu). Components or systems are
substituted by stubs. Below is the diagram of ‘Top down Approach’:

Bottom-up integration testing:

Testing takes place from the bottom of the control flow upwards. Components or systems
are substituted by drivers. Below is the image of ‘Bottom up approach’:
7.6 System Testing

System Testing is the testing of a complete and fully integrated software product. Usually,
software is only one element of a larger computer-based system. Ultimately, software is
interfaced with other software/hardware systems. System Testing is actually a series of
different tests whose sole purpose is to exercise the full computer-based system.

Two Category of Software Testing

 Black Box Testing

 White Box Testing

7.7 Alpha testing

 Alpha testing takes place at the developer's site by the internal teams, before release
to external customers. This testing is performed without the involvement of the
development teams.

Alpha Testing - In SDLC

The following diagram explains the fitment of Alpha testing in the software development
life cycle.
8. Software Implementation
8.1 USER TRAINING
8.2 USER MANUAL
8.1 USER TRAINING

User training is designed to prepare the user for testing and converting the system. User
involvement and training take place parallel with programming for three reasons.
1. The system group has time available to spend on training while the
programs are being written.
2. Initiating a user training program use the system group a clear image of
the users interest in the new system.
3. A trained user participates more effectively in the system

testing. The training programmes should be planned and organised.

→ Training programmes should

o Identify the user and trainer’s needs
o Design a comprehensive training program
o Select the best method of instruction
o Determine whether the system need the objectives

8.2 USER MANUAL

A well designed user manual can reduce the overall cost of training and support.

User documentation for modem system is almost always electronic and is usually integrated
part of the system. User manual are the important organizational assests.
Components of user manuals
→ Title and version of software release
→ Table of content
→ Features of product
→ Installation guide and system requirement
→ Getting started
→ Sample Scenario
→ Glossary of the terms used in the manual
9. Limitations / Constraints
Though we tried our best to develop this system, there are some limitation to the system that
is being developed. Due to time constraint in our project, we had to cover lots of requirement
that were given to us and along with that we have to learn entire new language. Some
limitations of Nservices24 portal are:

 No such online bank transaction in this system.

 Security issues.
 We are not providing better communication facilities like chatting and video calling.
 In this system there is no FAQ (Frequently Ask Question) facility.
 In this system users cannot upload their services video.
 10. Future Enhancement
There is always a scope of future enhancement as the requirements are every changing. There
is always a change in the necessities of the end user. Thus, these changes can be
accommodated by the means of the future enhancements. The enhancements and limitations
that may be covered up in the future are listed as under:

 We can enhance our system by providing SMS facilities through which system
users will be inform latest news and updates.

 We can further implement video conferencing and chatting facility which will
make our user to be in touch with each other.

 Further we can upload videos regarding Services.

 We can implement online bank transaction for users.

11. Bibliography
REFERENCES

Book:

Sr. No. Book Name Author Name Publisher

1 Professional John Wiley & Sons
ASP.NET MVC 5 Galloway Jon Inc.

2 Spring MVC Packt Publishing

Beginner's Guide Amuthan G. Limited

3 Android Packt Publishing

Programming for Horton John Limited
Beginners

4 Software Engineering Richard Fairley McGraw

5 System Analysis & Elias M Galgotia Publishing

Design

Website:

https://www.android.com/

https://www.androidhive.info/

https://firebase.google.com/

https://console.developers.google.com/

https://www.tutorialspoint.com/

https://medium.com/

https://www.journaldev.com/

https://github.com/
https://docs.microsoft.com/

https://www.tutorialsteacher.com/mvc/asp.net-mvc-tutorials

https://getbootstrap.com/

https://mindorks.com

https://www.w3schools.com/