0% found this document useful (0 votes)
526 views26 pages

Project Synopsis Format

The document provides instructions for submitting a synopsis for an internship project. It includes formatting guidelines and specifies what should be included in the synopsis. The synopsis should follow an index format and include sections on the intern and company profile, project profile, problem statement, objectives, scope, modules, technologies used, hardware/software requirements, testing, usability, and resources. The instructions state to send the offer letter and that the synopsis is not valid until submitted. It also provides details on submitting the synopsis electronically and physically.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
526 views26 pages

Project Synopsis Format

The document provides instructions for submitting a synopsis for an internship project. It includes formatting guidelines and specifies what should be included in the synopsis. The synopsis should follow an index format and include sections on the intern and company profile, project profile, problem statement, objectives, scope, modules, technologies used, hardware/software requirements, testing, usability, and resources. The instructions state to send the offer letter and that the synopsis is not valid until submitted. It also provides details on submitting the synopsis electronically and physically.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 26

INSTRUCTIONS

 Font : Heading -Times New Roman 14 , Underline

Contents- Times New Roman 12

 Start page numbersfrom Chapter No. 1 in the index


 Internal Guide is allocated and sent to you via mail
 Use bullet points wherever required like objectives, scope.
 Scan and mail your offer letter to the respective guide and one of the
TPO
 Your synopsis will not be held valid until you have submitted the offer
letter
 As of now, you may mail the synopsis to the respective guide.
 You need to submit hard copy of synopsis at your first guide meet
(which will be scheduled and mailed to you)
 Few points from the given format may not be applicable for few
projects, in such concern you may omit the related point.
 For any other queries contact your respective guide or me Miss Sura
S.S., Project Co-ordinator
SYNOPSIS INDEX
Sr.No. Content Page No.
1 Intern and Company Profile
2 Project Profile
3 Problem Statement
4 Objective of the Project
5 Scope of the Project
6 Modules Allocated
7 Brief Description of Technology
Used
8 Hardware and Software to be used
9 Testing Technology Used
10 Usability of the Project
11 Resources allocated and Limitations
12 Any other aspect to be mentioned
I Intern and Company Profile
Name of Intern(Users) :

Roll No.: 11067

Contact Number :

Email-id :

Internal Guide Name:Mr

Employee ID( If applicable) : ___________________________

Company Name: Disha Technologies

Address:-9 A,Nirapam Society, Ashok Nagar,VijapurRoad,Soapur Pin-413004

Company Reference Email address:-disha.tech.solapur@gmail.com

Company Contact No. Or Project Lead Contact Number:-9822675379

Brief Description about Company:

II Project Profile
Project Title:-Maratha Seva Sangh

Project Lead Name (External guide):- Mr.SantoshGawade Sir

Estimated duration
______________________________________________________________

Nature of Project
_____________________________________________________________

(1. DBMS, 2. Web Based 3. Networking, 4. Others-Mention.)

Brief Description about Project :


III Problmen Statement

( The problems posed by the existing or the legacy system , the motivation
behind building the new system)

IVObjective of the Project:

(List the objectives of the project as well as the allocated module)

V Scope of the Project :

(List the scope of the module which you are going to deal with)

VIModules Allocated:

(Mention and briefly describe the modules allocated to you)

VII Brief Description of Technology Used:

(The technology and its description both front end as well as back end)
VIII Hardware and Software to be used :

(Mention at client and server side separately- all the hardware and the software
which is required to develop, implement and run the project)

IX Testing Technology Used(If applicable) :

(Any testing methnodology used for unit testing or any other testing related data
about the project)

X Usability of the Project :

(The output of the project and the actual use- in brief)

XI Resources allocated and Limitations :

(Resources allocated to you, the team size of the module or project and the
limitations related to the project or the scope of project)

XII Any other aspect to be mentioned :


Maratha Seva Sangh
Web site
ABSTRACT
The goal of the website is not only limited to attracting and encouraging
user to involve int it but it also aims to provide information about Maratha Seva Sangh keeping in
mind that the person visiting this website wants a full knowledge of the Marath Seva Sangh.

Website is aimed toward users who want to known the all information about Maratha Seba
Sangh such as History, Structure, Mission, Sangh Parivar, Social service and reform,Relief and
rehabilitation,Photo gallery and how to part of sangh.

1. INTRODUCTION

The purpose of the website is to provide a friendly set of web pages that are easy to
navigate and at the same time provides sufficient depth and information about sangh.

Two potential groups of viewers exist:

1. Users interested who want to known in-depth information about a Sangh.


2. Users that are in that Sangh but are seeking for some information.

The website will be authenticated and the site provides a safe environment for online users.

It may fall short of certain requirements and may require some additional functionality if it is to be
used for General Audience.

Benefits for using the site should include:


 All about Maratha Seva Sangh information under one roof
 Information such History, Structure, Mission, Sangh Parivar, Social service Events
 Timely and up to date information that encourages readers to return to the site
 Call to user for events which is conducted by Sangh.

Major features of the website include the following pages/subsections:


 Downloads
o Provide basic downloads for Members information and general information for
viewer of website seeking for information of Sangh
 News and events
o Daily activity and updates of Sangh
 Social Services
o Information and Schedule
 Our sister institutions
o Information about other Group
 About Us/Mission
o Specifies the aim of institute
 About Us/Our Uniqueness
1. INTRODUCTION

1.1 PROBLEM STATEMENT

This system is designed in favor of the Maratha Seva Sangh which helps them to save the records
of the Members. It helps them from the manual work from which it is very difficult to find the
record of the Members and other information and also publishing events and news.

All the Sanag at present are managed manually by the Sang office. The Membership form
verification to the different data processing are done manually. Thus there are a lot of
repetitions which can be easily avoided. And hence there is a lot of strain on the person who
are running the Sangh and software’s are not usually used in this context. This particular
project deals with the problems on managing a Sangh and avoids the problems which occur
when carried manually Identification of the drawbacks of the existing system leads to the
designing of computerized system that will be compatible to the existing system with the
system which is more user friendly . We can improve the efficiency of the system, thus
overcome the drawbacks of the existing system. We design this system of the Sangh
management, through this they cannot require so efficient person to handle and upload the things.
This system automatically done it.

1.2.OBJECTIVES OF PROJECT

This software product the Maratha Sevn Sangh to improve their services for all the users. This
also reduce the manual work of the persons in admin panel and the bundle of registers that were
search when to find the information of a previous member, because through this system you can
store the data of those members who had left the Sangh . Through this you can check the personal
profile of all the current member within few minutes the data base of the system will help you to
check a particular one. The system will help you to post and check the current events and news.
The system will help to check visitor information and member details.
REQUIREMENT ENGINEERING
REQUIREMENT ENGINEERING

Systematic requirements analysis is also known as requirements


engineering.[3] It is sometimes referred to loosely by names such
as requirements gathering, requirements capture, or requirements
specification. The term requirements analysis can also be applied specifically
to the analysis proper, as opposed to elicitation or documentation of the
requirements, for instance. Requirements Engineering can be divided into
discrete chronological steps:

 Requirements elicitation,
 Requirements analysis and negotiation,
 Requirements specification,
 System modeling,
 Requirements validation,
 Requirements management.
Requirement engineering according to Laplante (2007) is "a subdiscipline
of systems engineering and software engineering that is concerned with
determining the goals, functions, and constraints of hardware and software
systems. In some life cycle models, the requirement engineering process
begins with a feasibility study activity, which leads to a feasibility report. If the
feasibility study suggests that the product should be developed, then
requirement analysis can begin. The requirement engineering provides the
appropriate mechanisam for understanding what customer wants.

2.1 FEASIBILITY STUDY

Feasibility study conducted once the problem is clearly understood.Feasibility study is a


high level capsule version of the entire system-analysis and design process.The
objective is to determine quickly and at the minimum expense how to solve the problem
and to determine the problem is solved.The system has been tested for feasibility in the
following ways.

Technical feasibility
Operational feasibility
Economical feasibility

2.1.1 Technical feasibility

A study of function ,performance and constraints may effect the ability to achieve an
acceptable system so ,that necessary function and performance are achieved with in the
constraints uncovered during system analysis.The software developed for the
automation of Maratha Seva Sangh is platform independent and has predefined
functions and constraints such as to locate the charges ,validating functions etc.,so the
project is technically feasible.
2.1.2 Operational feasibility

The purpose of this project is to develop software named Sangh Management which
facilitates quick registration process.The activities of the system such as data
entry ,information retrieval ,updating and deletion of records from various tables etc are
made easy .All the operators of this project are trained in this area.So this project is
operational feasible.

2.1.3 Economical feasibility

Economic analysis includes a broad range of concerns that include cost benefit analysis
,long term cooperative income strategies,cost of resources needed for development .In
existing they had to maintain a large number of books/registers is a costly affair.This can
be avoided by putting the data in the computer format that is cheaper and reliable.Since
the cost of resources for development of system satisfies the organization,the software
is economically feasible.

2.2 REQUIREMENT ANALYSIS

Requirements Analysis is the process of understanding the customer needs and expectations
from a proposed system or application and is a well-defined stage in the Software
Development Life Cycle model. Requirements are a description of how a system should
behave or a description of system properties or attributes. It can alternatively be a statement
of ‘what’ an application is expected to do.Given the multiple levels of interaction between
users, business processes and devices in global corporations today, there are simultaneous
and complex requirements from a single application, from various levels within an
organization and outside it as well.The Software Requirements Analysis Process covers the
complex task of eliciting and documenting the requirements of all these users, modeling and
analyzing these requirements and documenting them as a basis for system design. Software
Requirements Analysis and Documentation Processes are critical to software project success.
Requirements Engineering is an emerging field which deals with the systematic handling of
requirements.

2.2.1.EXISTING SYSTEM
Analysis begins when a user or manager begins a study of the program using existing
system. During analysis, data collected on the various files, decision points and
transactions handled by the present system. The commonly used tools in the system are
Data Flow Diagram, interviews, etc. training, experience and common sense are
required for collection of relevant information needed to develop the system. The
existing Maratha Seva Sangh most of the operation like checking out of members,
uploading events and photos etc done manually which includes a lot of human error,
more data redundancy and wastage of time.

2.2.2 PROBLEM RECOGNITION


For the past few years the number of educational institutions is increasing rapidly.
Thereby the number of sanghs is also increasing for the accommodation of the Userss
studying in this institution. And hence there is a lot of strain on the person who are running
the Sangh and software’s are not usually used in this context. If we are doing it manually
more human error , more strength and strain of manual labour needed, Repetition of the same
procedures, low security, Data redundancy, difficult to handle, difficult to update data, record
keeping is difficult , Backup data can be easily generated will occur.

2.2.3 PROBLEM EVALUVATION AND SYNTHESIS

The project Sangh management deals with the problems on managing a Sangh and avoids
the problems which occur when carried manually. Identification of the drawbacks of the
existing system leads to the designing of computerized system that will be compatible to the
existing system with the system which is more user friendly. We can improve the efficiency
of the system, thus overcome the following drawbacks of the existing system.

2.3 PROPOSED SYSTEM

The drawback of the existing system is that it is very difficult to retrieve data from
records. It is difficult to handle the whole system manually and it is less accurate and
to keep the data in records for future reference because it may get destroyed .
Moreover it is very difficult to retrieve data. Redundancy of data may occur and this
may lead to the inconsistency. The manual system is so time-consuming. The
proposed system is very easy to operate. Speed and accuracy are the main
advantages of proposed system. There is no redundancy of data. The data are
stored in the computer secondary memories like hard disk, etc. it can be easily
receive and used at any time. The proposed system will easily handle all the data
and the work done by the existing systems. The proposed systems eliminate the
drawbacks of the existing system to a great extent and it provides tight security to
data.
REQUIREMENT AND SPECIFICATION

3.1 SYSTEM REQUIREMENT

This project mainly aims to deal the operations of Maratha Seva Sangh …
It consist of 2 modules.
o Administrator module
o User Module

ADMINSTRATOR MODULE CONSIST OF

• Admin login
• Report of Members
• Report of requested yser who want to become Member
• Storing visitor information.
• Upload Events and News
• Search Existing and Left members details
• Send Invitation to all users for events
• Upload Photo Gallery
• Up to date with Latest information

ADMINSTRATOR MODULE CONSIST OF

• User login
• Search Existing and Left members details
• Get benifits of sangh
3.2 REQUIREMENTS

3.2.1 Software Configuration

Front end : ASP.NET with C#.NET


Backend : Microsoft SQL Server 2005
Operating
System : Windows XP
Language : C#
Frame work : Visual studio 2005 framework 2.0

3.2.2 Hardware Configuration

Processor : Pentium III,1.13GHz


RAM :128 Mb SD RAM
Monitor : SVGA, samtron 56v
Keyboard : Samsung Keyboard 105 keys
Mouse : Logitech 3-Button
CD-ROM : Samsung 52X
Floppy Drive : 1.44Mb[3 ½] sony
Hard Drive : 40GB HDD
Mother Board : Pentium 810
DESIGN

SYSTEM DESIGN

4.1 Input Design

The system design is divided in to two portions. The Administrator


section and the User section.

4.1.1 Administrator

1. The Administrator can Upload Data


2.Events & News.
3.He can control the status of memebers
4.He can edit the details of the members

A process of converting user originated inputs to a


computer-based format. Input design is an important part of development process since
inaccurate input data are the most common cause of errors in data processing. Erroneous
entries can be controlled by input design. It consists of developing specifications and
procedures for entering data into a system and must be in simple format. The goal of input
data design is to make data entrybas easy, logical and free from errors as possible. In input
data design, we design the source document that capture the data and then select the media
used to enter them into the computer. There are two major approaches for entering data in to
the computer. They are
· Menus.
· Dialog Boxes.

Menus

A menu is a selection list that simplifies computer data access


or entry. Instead of remembering what to enter, the user chooses from a list of options. A
menu limits a user choice of response but reduce the chances for error in data entry.

Dialog Box

Dialog boxes are windows and these windows are mainly


popup, which appear in response to certain conditions that occur when a program is run. It
allows the display of bitmaps and pictures. It can have various controls like buttons, text
boxes, list boxes and combo boxes. Using these controls we can make a ‘dialog’ with the
program.

4.2 OUTPUT DESIGN

Designing computer output should proceed in an organized,


well throughout manner; the right output element is designed so that people will find the
system whether or executed. When we design an output we must identify the specific output
that is needed to meet the system. The usefulness of the new system is evaluated on the basis
of their output.Once the output requirements are determined, the system designer can decide
what to include in the system and how to structure it so that the require output can be
produced. For the proposed software, it is necessary that the output reports be compatible in
format with the existing reports. The output must be concerned to the overall performance
and the system’s working, as it should. It consists of developing specifications and
procedures for data preparation, those steps necessary to put the inputs and the desired output,
ie maximum user friendly. Proper messages and appropriate directions can control errors
committed by users. The output design is the key to the success of any system. Output is the
key between the user and the sensor. The output must be concerned to the system’s working,
as it should. Output design consists of displaying specifications and procedures as data
presentation. User never left with the confusion as to what is happening without appropriate
error and acknowledges message being received.

4.3 DATABASE DESIGN


The data in the system has to be stored and retrieved
from database. Designing the database is part of system design. Data elements and data
structures to be stored have been identified at analysis stage. They are structured and put
together to design the data storage and retrieval system. A database is a collection of
interrelated data stored with minimum redundancy to serve many users quickly and
efficiently. The general objective is to make database access easy, quick, inexpensive and
flexible for the user. Relationships are established between the data items and unnecessary
data items are removed. Normalization is done to get an internal consistency of data and to
have minimum redundancy and maximum stability. This ensures minimizing data storage
required, minimizing chances of data inconsistencies and optimizing for updates.

4.4 ARCHITECTURAL DESIGN

Architectural design represents the data structure and program components that are required to
build the computer based system. It consider the structures and properties Of the components that
constitute the system and relationship that exist between all architectural components of the
system.

4.5 PROCESS DESIGN

Process design plays an important role in project development.


In order to understand the working procedure, process design is necessary. Data Flow
Diagram is the tool used for process design. Data Flow Diagram is the logical representation
of the data flow of the project. The DFD is drawn using various symbols. It has a source and
a destination. The process is represented using circlesand source and destination are
represented using squares. The data flow is represented using arrows. One reader can easily
get the idea about the project through Data Flow Diagram.

4.6 IMPLEMENTATION DESIGN


IMPLEMENTATION
SYSTEM TESTING
System testing is the stage of implementation, which is
aimed at ensuring that the system works accurately and efficiently before live operation
commences. Testing is the process of executing the program with the intent of finding errors
and missing operations and also a complete verification to determine whether the objectives
are met and the user requirements are satisfied. The ultimate aim is quality assurance. Tests
are carried out and the results are compared with the expected document. In the case of
erroneous results, debugging is done. Using detailed testing strategies a test plan is carried
out on each module. The various tests performed in “Network Backup System” are unit
testing, integration testing and user acceptance testing.

5.1 Unit Testing

The software units in a system are modules and routines that


are assembled and integrated to perform a specific function. Unit testing focuses first on
modules, independently of one another, to locate errors. This enables, to detect errors in
coding and logic that are contained within each module. This testing includes entering data
and ascertaining if the value matches to the type and size supported by java. The various
controls are tested to ensure that each performs its action as required.

5.2 Integration Testing

Data can be lost across any interface, one module can have
an adverse effect on another, sub functions when combined, may not produce the desired
major functions. Integration testing is a systematic testing to discover errors associated within
the interface. The objective is to take unit tested modules and build a program structure. All
the modules are combined and tested as a whole. Here the Server module and Client module
options are integrated and tested. This testing provides the assurance that the application is
well integrated functional unit with smooth transition of data.

5.3 User Acceptance Testing

User acceptance of a system is the key factor for the


success of any system. The system under consideration is tested for user acceptance by
constantly keeping in touch with the system users at time of developing and making changes
whenever required.

IMPLEMENTATION

Implementation is the stage in the project where


the theoretical design is turned into a working system and is giving confidence on the new
system for the users that it will work efficiently and effectively. It involves careful planning,
investigation of the current system and its constraints on implementation, design of methods
to achieve the change over, an evaluation of change over methods. Apart from planning
major task of preparing the implementation are education and training of users. The
implementation process begins with preparing a plan for the implementation of the system.
According to this plan, the activities are to be carried out, discussions made regarding the
equipment and resources and the additional equipment has to be acquired to implement the
new system. In network backup system no additional resources are needed. Implementation is
the final and the most important phase. The most critical stage in achieving a successful new
system is giving the users confidence that the new system will work and be effective. The
system can be implemented only after thorough testing is done and if it is found to be
working according to the specification. This method also offers the greatest security since the
old system can take over if the errors are found or inability to handle certain type of
transactions while using the new system.

7.1 User Training

After the system is implemented successfully, training of the user


is one of the most important subtasks of the developer. For this purpose user manuals are
prepared and handled over to the user to operate the developed system. Thus the users are
trained to operate the developed system. Both the hardware and software securities are made
to run the developed systems successfully in future. In order to put new application system
into use, the following activities were taken care of:
· Preparation of user and system documentation
. Conducting user training with demo and hands on
· Test run for some period to ensure smooth switching over the system

The users are trained to use the newly developed functions. User
manuals describing the procedures for using the functions listed on menu are circulated to all
the users. It is confirmed that the system is implemented up to users need and expectations.
7.2 Security and Maintenance

Maintenance involves the software industry captive, typing up


system resources .It means restoring something to its original condition. Maintenance follows

conversion to the extend that changes are necessary to maintain satisfactory operations
relative to changes in the user’s environment. Maintenance often includes minor
enhancements or corrections to problems that surface in the system’s operation. Maintenance
is also done based on fixing the problems reported, changing the interface with other software
or hardware enhancing the software.Any system developed should be secured and protected
against possible hazards. Security measures are provided to prevent unauthorized access of
the database at various levels. An uninterrupted power supply should be so that the power
failure or voltage fluctuations will not erase the data in the files. Password protection and
simple procedures to prevent the unauthorized access are provided to the users .The system
allows the user to enter the system only through proper user name and password.
5.1 DATA FLOW DIAGRAM(s) [D. F. D.]

The data flow diagrams are pictorial or graphical representation of the outline of the system
study. The data flow diagram covers all the processes and data storage area, which takes
place during any transaction in the system. The data flow diagrams are functionally divided
into context level, Zero level, First level and Second level data flow diagrams.

 Symbols used in DFDs:

(1) Process: Here flow of data is transformed. E.g. Forms Distribution, Preparing
Merit list, etc.

(2) External Entity: A source or destination of data, which is external to the


system. E.g. Users, Committee etc.

(3) A data flow: It is packet of data. It may be in the form of document, letter etc.
(4) Data store: Any store data but with no reference to the physical method of
storing.

CONTEXT LEVEL DIAGRAM:

Admin/User Database

Information Maratah Seva Request


Sangh Web Site

Become Member

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy