Table of Contents

INTRODUCTION................................................................................................................................3
INTRODUCTION............................................................................................................................4
REQUIREMENT AND ANALYSIS........................................................................................................5
PROBLEM DEFINITION.................................................................................................................6
SELECT SOFTWARE DEVELOPMENT MODEL................................................................................6
REQIUREMENT SPECIFICATION....................................................................................................7
EXISTING SYSTEM........................................................................................................................7
PROPOSED SYSTEM......................................................................................................................8
JUSTIFICATION OF THE PROPOSED SYSTEM................................................................................8
BENEFITS OF THE PROPOSED SYSTEM.........................................................................................9
PROJECT PLANNING.....................................................................................................................9
PROJECT SCHEDULING...............................................................................................................10
FEASIBILITY STUDY.................................................................................................................10
TECHNICAL FEASIBILITY..........................................................................................................11
OPERATIONAL FEASIBILITY....................................................................................................12
ECONOMIC FEASIBILITY.........................................................................................................12
SOCIAL FEASIBILITY................................................................................................................12
MANAGEMENT FEASIBILITY...................................................................................................12
LEGAL FEASIBILITY..................................................................................................................13
TIME FEASIBILITY...................................................................................................................13
SOFTWARE REQUIREMENT SPECIFICATION..................................................................................14
Introduction...............................................................................................................................15
PURPOSE................................................................................................................................15
SCOPE.....................................................................................................................................15
ACRONYMS AND ABBREVIATIONS........................................................................................15
REFERENCES...........................................................................................................................15
OVERVIEW..............................................................................................................................16
OVERALL DESCRIPTION..................................................................................................................17
PRODUCT PRESPECTIVE.............................................................................................................18
PRODUCT FUNCTIONS...............................................................................................................18
USER CHARACTERISTICS............................................................................................................18
CONSTRAINTS............................................................................................................................19
ASSUMPTIONS AND DEPENDENCIES.........................................................................................19
SPECIFIC REQUIREMENTS..............................................................................................................20
 EXTERNAL INTERFACE................................................................................................................21
FUNCTIONAL REQUIREMENTS...................................................................................................21
PERFORMANCE REQUIREMENTS...............................................................................................21
LOGICAL DATABASE REQUIREMENTS........................................................................................21
DESIGN CONSTRAINTS...................................................................................................................23
SOFTWARE AND HARDWARE REQUIREMENT............................................................................27
INTRODUCTION
INTRODUCTION
“Technical community” is a new technical based community site. This site provides an
access to different kinds of expertise having a software background in a particular
platform. This community site is developed to create a discussion forum and a get
togetherness of programmers of different platforms. In this technical community based
site we cast two different types of users (General and Expertise). The general user is
common man who will like to know the latest software trends and different source
codes. Expertise is the member of this community who belongs to one specified
subcategory in which he/she might be specialized in like C, C++, Java, ASP.NET, and SQL
SERVER. Etc.

Technical community provides on line discussion where members or public can

demand for the technical solution. When the users become more technically relevant,
the system becomes more efficient. As time goes this system becomes efficient for about
all the technical topics now we have. Always technical questions does not answered well
as it takes some time to be answer by any skilled person. Thus On -line technical
discussions not only reduces the time but also the efficiency of the system. On –line
technical person are so efficient to deal with any problems those asked by client. The
client may be public or other technical person.

This is purely technical oriented web service. All those who utilize this service are
strictly technical person. Service have many technical branches like java, .net, c, c++ etc.
Each technical person undergoes one or more technical branches. After registration, each
one should submit a set of programs if they want to become an Expert User with which
the evaluation of the person is done. After evaluation, if necessary points are achieved,
then that person is rewarded with gold silver or brown membership. According to degree
of membership, payment of particular technical person also varies. Evaluation process is
done by other active members.

OBJECTIVES

The main objectives of the proposed system are

  Eliminate the limitations of the existing system.

 Automate the manual activities.

 Easily find out a solution for technical questions

 Practice makes perfect in technical aspect also

The proposed system should be capable of processing large amount of data in a quickly
and efficient manner, store the data and give accurate results. It has to provide quality
reports to the concerned department.
REQUIREMENT AND ANALYSIS
PROBLEM DEFINITION
Analysis is the detail study of the various operations performed by a system and their
relationships within and outside the system. It defines the boundaries of the system.

Most of the techies, irrespective of beginner as well as expert, will be in need of help
during their work. People get stuck in between their coding and will be in need of help to
move on from the problem. Sometimes an error occurring first time in their experience
may lead to loss of time. So, to continue without time delay they may be in need of help.

Appraisal is an inevitable factor in profession. Appraisal of employee is always a

motivation for the employees to work further. Appraisal outside a company will be more
appreciable for the employee. Getting an expert grade which is known to others is a
highly motivated thing in their career life.

SELECT SOFTWARE DEVELOPMENT MODEL

 Requirement Gathering and analysis : All possible requirements of the system to
be developed like processing speed, data security, acquiring more functions etc.,
are captured in this phase and then documented in a requirement specification
document.
 System Design: The requirement specifications from first phase are studied in this
phase and system design is prepared. System Design helps in specifying hardware
and system requirements and also helps in defining overall system architecture.
 Implementation: With inputs from system design, the system is divided as units
which are integrated in the next phase. Each unit is developed and tested for its
functionality which is referred to as Unit Testing.
 Integration and Testing: All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire
system is tested for any faults and failures.
 Deployment of system: Once the functional and non-functional testing is done,
the software is deployed in the customer environment or released it.
 Maintenance: There are some issues which come up in the client environment.
To fix those issues patches are released. Also, to enhance the product some
 better versions are released. Maintenance is done to deliver these changes in
the customer environment

REQIUREMENT SPECIFICATION
System analysis is a detailed study of the various operations performed by the
system and their relationship within and module of the system. This phase involves the
study of parent system and identification are affected by or who use the system. During
analysis, data are collected on the variable files, decision point and transactions handled
by the present system.

System analysis involves gathering the necessary information and using the
structured tool for analysis. This includes the studying existing system and its drawback,
designing a new system and conducting cost benefit analysis. In this project, the
requirements are studied in details. Information are collected and documented. The
requirement analysis determines what the input should be. The inputs are Project
details, Module details, Schedule details etc. the processing job transforms the input to
output.

Existing System
There is no such existing system which provides all these features. The existing systems
only provide individual features. There are some systems which provide majority of the
features of the proposed system but the availability of such systems is very much
minimum at many places. Also, their user interface is somehow confusing, that the user
interface is not much simple to handle by the common users

Proposed system
“Technical community” is a new technical based community site. This site provides an access to
different kinds of expertise having a software background in a particular platform. This
community site is developed to create a discussion forum and a get togetherness of
programmers of different platforms.

Technical community provides on line discussion where members or public can demand for the
technical solution. When the users become more technically relevant, the system becomes more
efficient. As time goes this system becomes efficient for about all the technical topics now we
have. Always technical questions does not answered well as it takes some time to be answer by
any skilled person. Thus On -line technical discussions not only reduces the time but also the
efficiency of the system. On –line technical person are so efficient to deal with any problems
those asked by client. The client may be public or other technical person

JUSTIFICATION OF THE PROPOSED SYSTEM

The proposed system is designed to eliminate all the disadvantages of the existing
system. The proposed system deals with the manipulation of various master files and
transaction files, which is used for storing efficiently, the valuable details regarding
various management details. The proposed system aims at

o Speed in processing

o Reduce man power

o Security of data

o Reduce of stop errors

o Availability of reports

If any particular information about the employee details is needed it can be collected
from database file. The primary aim of the new system is to speed up the transaction.

There is no chance of errors since checking all the files validate the data.

BENEFITS OF THE PROPOSED SYSTEM

The proposed system simplifies the task of storage of data and report generation.
Automatic and regular backup of data safeguard the stored valuable information so as to
retrieve as and when we require. All these factors make a very clear picture of avoiding
redundancy of data to the maximum. The whole of this enable to restore the less time
taken and more effective output retrieved giving the minimum manpower.
 The proposed system is wholly e-recorded, thus making it user friendly.
The system is efficient, reliable, accurate and fast. The proposed system simplifies the
task of storage of data and report generation. Automatic and regular backup of data
safeguard the stored valuable information so as to retrieve as and required. The benefit
or advantages of the proposed system are:

• User friendliness I provided in the application with various controls.

• The system makes the overall project management much easier and
flexible.

• It provides high level of security with different level of authentication.

PROJECT PLANNING

The project have 4 months from July 4th. Considering the total available
time I have prepared a plan and schedule which is given below.

Sl.No Duration Activity

1 Sep 27– Sep 30 Identification of need.

2 Oct 1– Oct 9 Feasibility study

3 Oct 11– Oct 18 Analysis

4 Oct 19 – Oct 23 Design

5 Oct 24 – Oct 27 Testing

6 October Implementation

PROJECT SCHEDULING
 Once we have estimates of the effort and time requirement for the
different phases, a schedule for the project can be prepared. A conceptually simple and
effective scheduling techniques like calendar oriented charts are prepared. Progress can
be represented easily by ticking off each milestone when completed. Alternatively, for
each activity another bar can be drawn specifying when the activity actually started and
ended, i.e., when these two milestones were achieved. Once we have estimates of the
effort and time requirement for the different phases, a schedule for the project can be
prepared.

Feasibility Study

Feasibility is the determination of whether or not a project is worth doing. The process
followed in making this determination is called a feasibility study. It is the procedure for
identifying the candidate system, evaluating and electing the most feasible system. This is
done by investigating the existing system in the area under investigation or generally
ideas about a new system. It is a test of a system proposal according to its workability,
impact on the organization, ability to meet user needs, and effective use of resources.
The objective of feasibility study is not to solve the problem but to acquire a sense of its
scope.

Some of the steps involved in the feasibility analysis are:

 Prepare system flow charts.

 Describe and identify characteristics of candidate systems.

 Determine and evaluate performance and cost effectiveness of the candidate
system.

 Weigh system performance and cost data.

 Repair and report final project directive to management.

In the conduct of the feasibility study, I had to consider seven distinct types of feasibility.
These included:

 Technical feasibility

 Operational feasibility

 Economic feasibility

 Social feasibility

 Management feasibility

 Legal feasibility

 Time feasibility

Technical feasibility

This is concerned with specifying equipment and software that will successfully satisfy
the user requirement. The technical needs of the system includes:

 The facility to produce outputs in the given time.

 Response time under certain conditions.

 Ability to produce a certain volume of transaction at a particular speed.

 Facility to communicate data to distant location.

Operational feasibility

It is mainly related to human organizational and political aspects. The points to be

considered were:
 What changes would be brought with the system?

 What organizational structures would be disturbed?

 What new skills would be required? Does the existing staff members have these
skills? If not, could they be trained in due course of time?

Economic feasibility

Economic analysis is the most frequently used technique for evaluating the effectiveness
of a proposed system. More commonly known as cost/benefit analysis; the procedure is
to determine the benefits and savings that are expected from a proposed system and
compare them with costs. If benefits outweigh costs, a decision is taken to design and
implement the system.

Social feasibility

Social feasibility is the determination of whether a proposed system will be acceptable to

the people or not. This determination typically examines the probability of the project
being accepted by the group directly affected by the proposed system change.

Management feasibility

It is a determination of whether a proposed project will be accepted to management. If

management does not accept a project or gives a negligible support to it, the analyst will
tend to view the project as a non-feasible one.

Legal feasibility

Legal feasibility is a determination of whether a proposed project infringes on known

Acts, Statutes, as well as any pending legislation. Although in some instances the project
might appear sound, on closer investigation it may be found to infringe on several legal
areas.

Time feasibility

Time feasibility is the determination of whether a proposed project can be implemented

fully within a stipulated time frame. If a project takes too much time it is likely to be
rejected.
SOFTWARE REQUIREMENT SPECIFICATION
Introduction
A software requirements specification (SRS) is a document that describes what the
software will do and how it will be expected to perform. It also describes the
functionality the product needs to fulfil all stakeholders (business, users) needs.

PURPOSE

In short, the purpose of this SRS document is to provide a detailed overview of our
software product, its parameters and goals. This document describes the project's target
audience and its user interface, hardware and software requirements.

SCOPE

This system is used globally and everyone can access the system irrespective of their
region. All over the world people can ask doubts and can discuss about the topics. People
with internet can access the system.

ACRONYMS AND ABBREVIATIONS.

Acronyms and Abbreviations

Acronyms Meaning

SQL Structured Query Language

PHP PHP:Hypertext Preprocessor

REFERENCES.

• IEEE 830-1998 standard for writing SRS document.

• I Somerville, Software Engineering, 8th ed, Addison-Wesley, 2007.

• Developer’s Responsibility Overview

The developer is responsible for :

• Developing the system.

• Installing the software.

• Maintaining the system.

OVERVIEW

The remaining sections of this document provide a general description, including

characteristics of the users of this project, the product's hardware, and the
functional and data requirements of the product.  General description of the project is
discussed in section 2 of this document.  Section 3 gives the functional requirements,
data requirements and constraints and assumptions made while designing the system.  It
also gives the user viewpoint of product.  Section 3 also gives the specific requirements of
the product.  Section 3 also discusses the external interface requirements and gives
detailed description of functional requirements.
OVERALL DESCRIPTION
PRODUCT PRESPECTIVE.

A product requirements specification establishes a bridge between product

management and development. It defines a product in terms of stakeholder
requirements, containing all those requirements that sensibly should be described
explicitly and be available permanently. The product is supposed to be an open source,
under the GNU general Public License. It is a web-based system implementing client-
server model. The system provides simple mechanism for users to share and acquire
knowledge. The product will be developed completely independent and standalone. Each
user will have to have an individual copy of the product.

PRODUCT FUNCTIONS.
The product function will include the following areas:

The application is capable enough to store different products and also perform
some editing on them that is added. It will be having user friendly GUI’s that will guide
the user to easily achieve the same.

• Adminform

• Userform

USER CHARACTERISTICS.
Admin:

1. Login
2. Manage users
3. Manage grades
4. View discussion
Users

1. Login
2. Registration
3. Add questions
4. Add answers
5. Mark correct answer

CONSTRAINTS.
• The system must be user friendly.

• Designed in PHP using MYSQL

ASSUMPTIONS AND DEPENDENCIES

Customers can just retrieve the connection details and offers from the
database. The user can create bills, add new connection, details by changing some
limited portions of the database. Administrator will have entire access throughout the
database. System should have proper user authentication.
SPECIFIC REQUIREMENTS
External interface
External interface requirements are types of functional requirements. They’re important
for embedded systems. And they outline how your product will interface with other
components. Since our system does not contain any embedded system we don’t have
external interface

Functional requirements
• Provide the facility for users to enquire the doubts through the system.

• Facilitate option for searching solutions on their problems.

• Provide simple and attractive interface.

• Ensure security for the database.

• The system should be able to handle high volume of data.

PERFORMANCE REQUIREMENTS
• Should run on windows 7/8/8.1

• Reasonable response time.

• Reports should be generated within in a reasonable time.

• Searching should be done within minimum time.

LOGICAL DATABASE REQUIREMENTS

• System should have installed with MySql as back end.

• Create different tables for customer details, connection details, whole billing
details, bill payment and these tables should be linked using primary key and foreign
keys.
• Insert valid data’s to the created tables
DESIGN CONSTRAINTS
Design constraints are those constraints that are imposed on the design solution, which
in this example refers to the ESS design. These constraints are typically imposed by the
customer, by the development organization, or by external regulations. The constraints
may be imposed on the hardware, software, data, operational procedures, interfaces, or
any other part of the system.Design constraints can have a significant impact on the
design and should be validated prior to imposing them on the solution. A straightforward
approach to address design constraints is to categorize the type of constraints (e.g.,
hardware, software, procedure, algorithm), identify the specific constraints for each
category, and capture them as system requirements in the Requirements package along
with the corresponding rationale. The design constraints are then integrated into the
physical architecture.

The system shall be built using a standard web page development tool that conforms to
either IBM’s CUA standards or Microsoft’s GUI standards. There are no memory
requirements. The computers must be equipped with web browsers such as Internet
explorer. The product must be stored in such a way that allows the client easy access to
it. Response time for loading the product should take no longer than five minutes. A
general knowledge of basic computer skills is required to use the product. The user
interface for the software shall be compatible to any browser such as Internet Explorer,
Mozilla or Netscape Navigator by which user can access to the system. The user interface
shall be implemented using any tool or software package like Java Applet, MS Front Page,
EJB etc
SOFTWARE SYSTEM ATTRIBUTES

• Reliability

The software should not have any reliability issues. The software will be thoroughly
tested and any issues resolved.

• Availability

The software will execute as a standalone system so as long as the machine is running,
the program will be available. The key to maintaining availability will be by ensuring a
connection to the database server is available. Failure to connect to the database will
make data unavailable.

• Security

This software is intended to communicate over an internal network; therefore security is

of little concern. The user will have to enter the username and password so the program
can connect to the database server. The username and password will not be stored
because encryption of such information is outside thpe scope of the project.

• Maintainability

The software will be composed of various modules decreasing the complexity of

expansion.

• Portability

As states previously, this software will only run under the Windows OS. The setup file,
setup.info, can be copied to multiple machines so that each program does not have to be
setup separately.
ORGANIZING THE SPECIFIC REQUIREMENTS

• Functional Hierarchy

In this system the overall functionality is organized by Data flow diagrams and E-R
diagrams. Based on these diagrams, data relationships and dependencies are found and a
functional hierarchy is made for organizing the specific requirements.
SOFTWARE AND HARDWARE REQUIREMENT
Tools / Platform

SOFTWARE SPECIFICATION

Operating System : Windows Vista or higher

Web Server : WAMP

Front End : PHP

Back End : MySQL

IDE : Net Beans

Protocol : Http, SMTP, Pop3

Browser : Internet Explorer, Mozilla Firefox,

Google Chrome

FRONT END

PHP is a server-side scripting language designed for Web development but also used
as a general-purpose programming language. PHP is now installed on more than 20
million Web sites and 1 million Web servers. While PHP originally stood for Personal
Home Page, it is now said to stand for PHP: Hypertext Preprocessor, a recursive acronym.

PHP code is interpreted by a Web server with a PHP processor module which generates
the resulting Web page: PHP commands can be embedded directly into an HTML source
document rather than calling an external file to process data. PHP includes free and open
source libraries with the core build. PHP is a fundamentally Internet-aware system with
modules built in for accessing File Transfer Protocol (FTP) servers, many database
servers.
PHP was conceived in 1994 and was originally the work of one man, RasmusLerdorf. It
was adopted by other talented people and has gone through four major rewrites to bring
us the broad, mature product we see today. As of November 2007, it was installed on
more than 21 milliondomains worldwide, and this number is growing rapidly. PHP is an
Open Source project, which means we have access to the source code and can use, alter,
and redistribute it all without charge.

PHP’s Strengths

• Performance and Scalability

• Interfaces to many different database systems

• Built-in libraries for many common web tasks

• Low cost

• Ease of learning and use

• Strong object-oriented support

• Portability

• Flexibility of development approach

• Availability of source code

• Availability of support and documentation

BACK END

A database is a collection of information that’s related to a particular subject or

purpose, such as tracking client orders or maintaining a list of project details. If the
database isn’t stored on a computer, or only part of it are one may be tracking
information from a variety of sources that one is having to co-ordinate and organize
himself using MySQL Server, one can manage all information from a single database file.
Within the file, data is divided into separate storage containers called tables; view, add
and update data by using online forms; find and retrieve just the data wanted for reports.
MySQL Server allows the user to view, update or analyze the database from the Internet
of an intranet by creating data access pages. MySQL Server as a relational database
stores data in many related tables.

A table is a collection of data about a specific topic such as projects or clients. Using a
separate table for each topic means that, store that data only once. This makes the
database more efficient and reduces data-entry errors.

Tables organize data into columns (called fields) and rows (called records). A common
field relates two tables so that MySQL Server can bring together the data from the two
tables for viewing, editing, or printing. In table Design view one can create an entire table
from scratch or add, delete or customize the fields in an existing table.

The user can also display records from tables that are related to the current table by
displaying sub datasheets within the main datasheet. With some restrictions, the user
can work with the data in sub datasheets in many of

the same ways that they work with data in the main datasheet. To store data, create one
table for each type of information that is to be tracked. To bring the data from multiple
tables together in a query, form, report, or data MySQL Server page, define relationships
between the tables

About The OS

The Operating System used for this software is Windows Operating System.

Windows OS

The hall mark software of Microsoft, which had created a new wave of
graphical user interface in the industry, WINDOWS XP stands in the top of its popularity.
The advent of Microsoft plus has cured whatever faults were there in the original
WINDOWS XP version and made it and useful tool to work with the memory resident
programs of it, make the reloading of WINDOWS XP easier, it plug and play connectivity
for input output devices makes a new dimension towards the use of computer system.
Connectivity to the information networks like Internet through modems makes it
overstate software. Almost all new software has their windows version also. The
programmer and file manager facilities of it had made a leap way towards giving a new
dimension towards the operation of computer systems.

HARDWARE SPECIFICATION

In order to implement a new system the choice of a processor with maximum

possible speed is made. There should be sufficient memory to store data and software
tools for efficient processing.

Processor : Pentium III or above.

RAM : 3GB.

System memory : 128MB recommended.

Cache memory : 512KB.

Hard disk : 250GB.

Monitor : SVGA color.

Keyboard : Standard keyboard.

Mouse : Two button mouse roller mouse

recommended.

Modem : Any modem.