INDEX
S. No.
Contents
1
Introduction of Project
2
Objective and Scope of Project
System Requirement Specification (SRS)
3
-
Hardware Requirement
-
Software Requirement
Theoretical Background
4
-
Front End
-
Back End
5
Definition of Problem
6
System Analysis
7
Cost and benefit Analysis
8
System Planning (PERT Chart)
9
Life Cycle of the Project
10
Methodology Adapted
11
System Implementation
12
System Design
- Data Dictionary
-
ER Diagram
-
13
DFD
- Flow Chart
Project Code Sheet(System Coding)
14
Input and Output Screen Design
15
System Testing
16
System Maintenance
17
Conclusion
18
Limitation
19
Reference
1
Page No.
INTRODUCTION OF PROJECT
OBJECTIVE OF PROJECT
SCOPE OF PROJECT
2
INTRODUCTION OF PROJECT
The title of project is-“_________________________”.
3
OBJECTIVE AND SCOPE OF PROJECT
The main objective of developing this project is only for learning purpose. This is a web
based system to provided information worldwide when it is hosted by purchasing domain
name like “http://www.carshowroom.com” and web space for storing and processing this web
site for web server.
This project is based on client-server architecture. This web application loaded on a web
server and executed from one or more clients requested by any browser like Internet Explorer,
Mozila etc. in the form of URL like http://localhost/default.aspx.
From above client-server architecture of project it is clear that any user can access web pages
of this project from any place across the world. For this user simply need internet connection
and request for needed information in the form of URL, but user has also not need to enter
URL, only simply single click on hyperlink of required pages.
Thus this project is very beneficial when user wants to list out explorer any needful
information across the world.
The scope of project depends on storing maximum information on this web site and its
hosting. As the requirements increases, it is added into projects. In this way importance of this
4
projects are long life. When a person learns any programming languages, then he/she always
thinks about developing new software project. After learning he/she starts develop software
project. Development of projects involves all the necessary features of language and
developer’s logics. Therefore perfection of programming language, every programmer must
be developed a software project to gain all knowledge about language and new approaches
that involved in projects.
5
SYSTEM REQUIREMENTS
-
HARDWARE
SOFTWARE
6
HARDWARE REQUIREMENT
Without computer hardware we can only discuss about proposed project. So to create and
working this project following minimum requirement of hardware are need.
-
CPU: 1.0 GHz
-
RAM: 1 GB
-
Hard disk: 100 GB
-
Keyboard: Having Basic Keys
-
Mouse: Optical or any wheel Mouse
-
Modem: Internal or External of 100mbps
7
SOFTWARE REQUIREMENT
Without computer software we can only discuss about proposed project. So to create and
working this project following minimum requirement of software are need.
-
Operating System: MS-Window 7 or Higher
-
MS DOT Net Framework 2.0 or higher
-
Microsoft Visual Studio2005 with SQL-SERVER during designing
-
IIS 2.0(Internet Information Services) for web server
-
Any Browser like Internet Explorer 6.0 at client side
8
THEORETICAL BACKGROUND
(FRONTEND & FRONTEND)
9
FRONT END & BACK END
Used Front End Software: Microsoft Visual Studio’s ASP.NET 2005 with C#
Meaning of Front End: It is software through which forms are designed to provide user
interface and coding are written for processing any internal activities.
Used Back End Software:
Microsoft SQL Server Database software
Meaning of Back End: It is software through which all data of applications are stored by
creating database.
10
INTRODUCTION OF ASP.NET (FRONT END)
Introduction:
ASP.NET is a server-side Web application framework designed for Web development to
produce dynamic Web pages. It was developed by Microsoft to allow programmers to build
dynamic web sites, web applications and web services. It was first released in January 5, 2002
with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server
Pages (ASP) technology. Scott Guthrie became the product unit manager for ASP.NET, and
development continued apace, with version 1.1 being released on April 24, 2003 as a part of
Windows Server 2003.
Characteristics:
-
ASP.NET is built on the Common Language Runtime (CLR), allowing programmers
to write ASP.NET code using any supported .NET language.
-
ASP.NET Web pages, known officially as Web Forms, are the main building blocks
for application development.
-
Web forms are contained in files with a ".aspx" extension; these files typically contain
static HTML markup, as well as markup defining server-side Web Controls and User
Controls where the developers place all contents for the Web page.
-
Additionally, dynamic code which runs on the server can be placed in a page within a
block <% -- dynamic code -- %>, which is similar to other Web development
technologies such as PHP, JSP, and ASP.
-
With ASP.NET Framework 2.0, Microsoft introduced a new code-behind model
which allows static text to remain on the .aspx page, while dynamic code remains in
an .aspx.vb or .aspx.cs or .aspx.fs file (depending on the programming language used).
11
Directives:
A directive is a special instruction on how ASP.NET should process the page. The most
common directive is <%@ Page %> which can specify many attributes used by the ASP.NET
page parser and compiler.
Examples:
Inline code
<%@ Page Language="C#" %>
<!DOCTYPE html PUBLIC "---//W3C//DTD XHTML 1.0 //EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
// Assign the datetime to label control
lbl1.Text = DateTime.Now.ToLongTimeString();
}
</script>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title>Sample page</title>
</head>
<body>
<form id="form1" runat="server">
Code-behind solutions
<%@Page Language="C#" CodeFile="SampleCodeBehind.aspx.cs" Inherits=
"Website.SampleCodeBehind" AutoEventWireup="true" %>
The above tag is placed at the beginning of the ASPX file. The CodeFile property of the @
Page directive specifies the file (.cs or .vb or .fs) acting as the code-behind while the Inherits
property specifies the Class from which the Page is derived. In this example, the @ Page
directive is included in SampleCodeBehind.aspx, then SampleCodeBehind.aspx.cs acts as the
code-behind for this page:
12
Source language C#:
using System;
namespace Website
{
public partial class SampleCodeBehind : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
Response.Write("Hello, world");
}
}
}
Source language Visual Basic.NET:
Imports System
Namespace Website
Public Partial Class SampleCodeBehind
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender
EventArgs)
Response.Write("Hello, world")
End Sub
End Class
End Namespace
As
Object,
ByVal
e As
In this case, the Page_Load() method is called every time the ASPX page is requested. The
programmer can implement event handlers at several stages of the page execution process to
perform processing.
State management:
ASP.NET applications are hosted by a Web server and are accessed using the stateless HTTP
protocol. As such, if an application uses stateful interaction, it has to implement state
management on its own. ASP.NET provides various functions for state management.
Application state:
These are set and initialized when the
Application_OnStart
event fires on the loading of the
first instance of the application and are available until the last instance exits. Application state
variables are accessed using the Applications collection.
13
Session state
Server-side session state is held by a collection of user-defined session variables that are
persistent during a user session. These variables, accessed using the
Session
collection, are
unique to each session instance. The variables can be set to be automatically destroyed after a
defined time of inactivity even if the session does not end. Client-side user session is
maintained by either a cookie or by encoding the session ID in the URL itself.
View state
View state refers to the page-level state management mechanism. The main use for this is to
preserve form information across postbacks. View state is turned on by default.
Template engine:
ASP.NET 2.0 introduced the concept of "master pages", which allow for template-based page
development. A Web application can have one or more master pages, which, beginning with
ASP.NET 2.0, can be nested. Master templates have place-holder controls, called
ContentPlaceHolders to denote where the dynamic content goes. Child pages use those
ContentPlaceHolder controls, which must be mapped to the place-holder of the master page
that the content page is populating. When a request is made for a content page, ASP.NET
merges the output of the content page with the output of the master page, and sends the output
to the user. The master page remains fully accessible to the content page. This means that the
content page may still manipulate headers, change title, configure caching etc.
14
File extensions:
Some useful file extensions of ASP.NET application are:
Extension
Description
Asax
This is the global application file. You can use this file to define global variable. It is
mostly used to define the overall application event related to application & session
object. Global.asax, used for application-level logic
Aspx
An ASP.NET Web Forms page that can contain Web controls and presentation and
business logic.
Config
web.config is the only file in a specific Web application to use this extension by default
(machine.config similarly affects the entire Web server and all applications on it),
however ASP.NET provides facilities to create and consume other config files. These are
stored in XML format.
cs/vb
Code files (cs indicates C#, vb indicates Visual Basic, fs indicates F#). Code behind files
have the extension ".aspx.cs" or ".aspx.vb" for the two most common languages.
Master
master page file. Default file name is Master1.master.
Directory structure:
In general, the ASP.NET directory structure can be determined by the developer's
preferences. Apart from a few reserved directory names, the site can span any number of
directories. The special directory names (from ASP.NET 2.0 on) are:
App_Data: The App_Data ASP.NET Directory is the default directory for any database used
by the ASP.NET Website. These databases might include Access (mdb) files or SQL Server
(mdf) files.
15
App_Code : This is the "raw code" directory. The ASP.NET server automatically compiles
files in this folder of every page of the site.
Bin: Contains compiled code (.dll files) for controls, components, or other code that you want
to reference in your application. Any classes represented by code in the Bin folder are
automatically referenced in your application.
Versions of ASP.NET
Date
Version
Remarks
January 16, 2002
1.0
First version. released together with Visual Studio .NET
April 24, 2003
1.1
released together with Visual Studio .NET 2003
November 7, 2005
2.0
Codename Whidbey. released together with Visual Studio 2005
and Visual Web Developer Express and SQL Server 2005
November 21, 2006
3.0
Not Papular
November 19, 2007
3.5
Released with Visual Studio 2008 and Windows Server 2008
August 11, 2008
3.5 SP1
Released with Visual Studio 2008 Service Pack 1
April 12, 2010
4.0
Parallel extensions and other .NET Framework 4 features
August 15, 2012
4.5
Released with Visual Studio 2012 and Windows Server 2012 for
Windows 8.
16
MICROSOFT SQL SERVER (BACK END)
Introduction:
Microsoft SQL Server is a relational database management system developed by Microsoft.
As a database, it is a software product whose primary function is to store and retrieve data as
requested by other software applications, be it those on the same computer or those running
on another computer across a network (including the Internet). There are at least a dozen
different editions of Microsoft SQL Server aimed at different audiences and for workloads
ranging from small single-machine applications to large Internet-facing applications with
many concurrent users. Its primary query languages are T-SQL and ANSI SQL.
SQL Server 2005
SQL Server 2005 (formerly codenamed "Yukon") released in October 2005. It included native
support for managing XML data, in addition to relational data. SQL Server 2005 also allows a
database server to be exposed over web services using Tabular Data Stream (TDS) packets
encapsulated within SOAP (protocol) requests. When the data is accessed over web services,
results are returned as XML.
Features of SQL Server 2005
-
SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET
Framework.
-
SQL Server 2005 introduced Multi-Version Concurrency Control.
-
SQL Server 2005 introduced "MARS" (Multiple Active Results Sets), a method of
allowing usage of database connections for multiple purposes.
17
-
SQL Server 2005 introduced DMVs (Dynamic Management Views), which are
specialized views and functions that return server state information that can be used to
monitor the health of a server instance, diagnose problems, and tune performance.
Data Storage
Data storage is a database, which is a collection of tables with typed columns. SQL Server
supports different data types, including primary types such as Integer, Float, Decimal, Char
(including character strings), Varchar (variable length character strings), binary (for
unstructured blobs of data), Text (for textual data) among others.
Microsoft SQL Server also allows user-defined composite types (UDTs) to be defined and
used. In addition to tables, a database can also contain other objects including views, stored
procedures, indexes and constraints, along with a transaction log. The data in the database are
stored in primary data files with an extension
.ndf
.mdf.
Secondary data files, identified with a
extension, are used to allow the data of a single database to be spread across more than
one file, and optionally across more than one file system. Log files are identified with the .ldf
extension.
Creating Tables in Microsoft SQL Server
Step 1: Design Your Table
Sit down with a pencil and paper and sketch out the design of your database.
Step 2 : Start SQL Server Management Studio
Open Microsoft SQL Server Management Studio (SSMS) and connect to the server where
you'd like to add a new table.
Step 3 : Expand the Tables Folder for the Appropriate Database
18
Expand the Databases folder and select the database where you'd like to add a new table.
Expand that database's folder and then expand the Tables subfolder.
Step 4: Start Table Designer
Right-click on the Tables subfolder and select the New Table option. This will start SQL
Server's graphical Table Designer.
Step 5: Add Columns to Your Table
Begin by clicking in the first empty cell under the Column Name heading in Table Designer.
Once you've entered an appropriate name, select the data type from the drop-down box in the
next column. If you're using a data type that allows different lengths, you may specify the
exact length by changing the value that appears in parentheses following the data type name.
If
you'd
like
to
allow
NULL values
in
this
column, click
"Allow
Nulls".
Repeat this process until you've added all necessary columns to your SQL Server database
table.
Step 6: Select a Primary Key
Next, highlight the column(s) that you've selected for your table's primary key. Then click the
key icon in the taskbar to set the primary key.
Step 7: Save Your New Table
Don't forget to save your table! When you click the save icon for the first time, you'll be asked
to provide a unique name for your table.
19
PROBLEM DEFINITION
SYSTEM ANALYSIS
COST & BENEFIT
SYSTEM PLANNING
SDLC
20
PROBLEM DEFINITION
The definition of our problem lies in manual system and a fully automated system.
Manual system : The system is very time consuming and lazy. This system is more prone to
errors and sometimes the approach to various problems is unstructured.
Technical system : With the advent of latest technology if we do not update our system then
our business result in losses gradually with time. The technical systems contains the tools of
latest
trend i.e. computers printers, fax, Internet etc. The systems with this technology are very fast,
accurate, user-friendly and reliable.
21
SYSTEM ANALYSIS
The first one is the Analysis phase which includes detailed study of the Proposed System. The
aim of this stage is to get prepared for the development phase .The various activities that are
involved while going through Analysis Phase are:
-
Analysis the Current System
-
Getting user requirements and converting them to Requirement Specifications
-
Feasibility study of the New Proposed System
-
Cost Benefit analysis
-
Arrangement of resources required.
-
Planning for time management
As Stated above Analysis Phase is the first stone towards the building of the Proposed
System, so it needs to be efficiently and perfectly performed.
For the Analysis of the this system, various nearby existing system were
visited and a detailed Study of the current system was performed. Various Staff Personnel
were questioned about the Prevailing System and Problems related to it. Their
requirements were taken and understood for the design of the Proposed System. The
Owners of current system were also part of the analysis. They were asked about the
amount that they could spend on the Proposed System and about the scope of the Proposed
System. The software must include provisions to keep user details and login history.
22
COST AND BENEFIT ANALYSIS
Cost and benefits may be tangible or intangible, direct or indirect, fixed or variable. Cost
estimates also take into consideration H/W, personnel, facility and supply cost for final
evaluation. Identify the cost and benefit of the given system and categorized them for
analysis. Then a method of evaluation is selected and the results are interpreted for action. In
developing cost estimates for a system, we need to consider several cost elements. Among
them are H/W, personal, facilities, operating and supply cost.
1. Hardware Cost: relate to the actual purchase or lease of the computer and peripherals.
Determining the actual cost of hardware is generally more difficult when the system is
shared by various users than for a dedicated stand-alone system.
2. Personal Cost: Personal cost includes EDP staff salaries and benefits. As well as pay for
those involved in developing the system. Costs incurred during the development of a
system are one-time costs and are labeled development costs. Once the system is installed
the cost of operating and maintaining the system become recurring cost
3. Facility cost: Facility costs are expenses incurred in the preparation of the physical site
where the application or the computer will be in operation. This includes writing, flooring,
acoustics, lighting and AC.]
4. Operating Cost: operating cost includes all cost associated with the day-to-day
operation of the applications and the caliber of the operating staff. There are various
ways of covering operating cost.
23
SYSTEM PLANNING (PERT CHART)
A PERT chart is a project management tool used to schedule, organize, and coordinate tasks
within a project. PERT stands for Program Evaluation Review Technique, a methodology
developed by the U.S. Navy in the 1950s to manage the Polaris submarine missile program.
A PERT chart presents a graphic illustration of a project as a network diagram consisting of
numbered nodes (either circles or rectangles) representing events, or milestones in the
project linked by labeled vectors (directional lines) representing tasks in the project. The
direction of the arrows on the lines indicates the sequence of tasks. In the diagram, for
example, the tasks between nodes 1, 2, 4, 8, and 10 must be completed in sequence. These
are called dependent or serial tasks. The tasks between nodes 1 and 2, and nodes 1 and 3 are
not dependent on the completion of one to start the other and can be undertaken
simultaneously. These tasks are called parallel or concurrent tasks. Tasks that must be
completed in sequence but that don't require resources or completion time are considered to
have event dependency. These are represented by dotted lines with arrows and are called
dummy activities. For example, the dashed arrow linking nodes 6 and 9 indicates that the
system files must be converted before the user test can take place, but that the resources and
time required to prepare for the user test (writing the user manual and user training) are on
another path. Numbers on the opposite sides of the vectors indicate the time allotted for the
task.
24
SYSTEM DEVELOPMENT LIFE CYCLE
(SDLC)
The image below is the classic Waterfall model methodology, which is the first SDLC
method
and
it
describes
the
various
phases
involved
in
development.
Fig- System Development Life Cycle
Briefly on different Phases:
Feasibility
The feasibility study is used to determine if the project should get the go-ahead. If the project
is to proceed, the feasibility study will produce a project plan and budget estimates for the
future stages of development.
Requirement Analysis and Design
Analysis gathers the requirements for the system. This stage includes a detailed study of the
business needs of the organization. Options for changing the business process may be
considered. Design focuses on high level design like, what programs are needed and how are
they going to interact, low-level design (how the individual programs are going to work),
interface design (what are the interfaces going to look like) and data design (what data will be
25
required). During these phases, the software's overall structure is defined. Analysis and
Design are very crucial in the whole development cycle. Any glitch in the design phase could
be very expensive to solve in the later stage of the software development. Much care is taken
during this phase. The logical system of the product is developed in this phase.
Implementation
In this phase the designs are translated into code. Computer programs are written using a
conventional programming language or an application generator. Programming tools like
Compilers, Interpreters, and Debuggers are used to generate the code. Different high level
programming languages like C, C++,Java, VB.NET, C#.NET, ASP.NET are used for coding.
With respect to the type of application, the right programming language is chosen.
Testing
In this phase the system is tested. Normally programs are written as a series of individual
modules, this subject to separate and detailed test. The system is then tested as a whole. The
separate modules are brought together and tested as a complete system. The system is tested
to ensure that interfaces between modules work (integration testing), the system works on the
intended platform and with the expected volume of data (volume testing) and that the system
does what the user requires (acceptance/beta testing).
Maintenance
Inevitably the system will need maintenance. Software will definitely undergo change once it
is delivered to the customer. There are many reasons for the change. Change could happen
because of some unexpected input values into the system. In addition, the changes in the
system could directly affect the software operations. The software should be developed to
accommodate changes that could happen during the post implementation period.
26
METHODOLOGY ADAPTED
SYSTEM IMPLEMENTATION
27
METHODOLOGY ADAPTED
Developing of whole system should be in a completely phased manner, utilizing the latest
techniques of project management. We have considered various concepts of software
engineering and methodology during the development of the project. Many software
development projects have been known to incur extensive and costly design errors. The most
expensive errors are often introduced early in the development process. This underscores the
need for better requirement definition and software design methodology. Software design is
an important activity as it determines how the whole software development task would
proceed including the system maintenance. The design of software is essentially a skill, but it
usually requires a structure, which will, provides a guide or a methodology for this task.
A methodology can be defined as the underlying principles and rules that govern a system.
The project follows ‘SDLC’ phases step by step. The systematic approach the analyst takes to
the analysis and design of information system is called the system development life cycle
(SDLC). The SDLC is divided into 7 phases, although each phase presented distinctly it is
never accomplished as a separate step. The several activities can occur simultaneously and
activities may be repeated.
System Testing Methodologies

Phase in which the errors remaining in previous phases must be eliminated.

Helps in critical manner for quality assurance, ensuring the reliability of a s/w.

Represents a critical review of Specifications, Design and Coding

Destructive rather than Constructive (try to break the system)

Major objective is to find errors not to show the absence of errors (as distinct from
Verification and Validation
28
TYPES OF TESTING

White-Box Testing: Knowing the internal workings of a product, tests are conducted
to ensure that internal operations are performed according to specifications and all
internal components have been exercised.

Black-Box Testing:
1. Focus is on the functional requirements of the software
2. Uncovers errors such as
3. Incorrect or missing functions
4. Interface errors
5. Errors in data structures
6. Performance errors
7. Initialization and Termination errors
8. Unlike White Box Testing, this is performed at later stages of testing.
29
SYSTEM IMPLEMENTATION
Implementation simply means converting new systems design into operational. This involves
creating computer-compatible files, training the operating staff and installing Hardware and
Terminals.
In system implementation, user training is crucial for minimizing resistance to change and
giving the new system a chance to prove its worth.
Implementation involves several steps:
Review the project plane, test documentation and implementation plane.

Converts the files.

Conduct the parallel processing.

Log the computer run for reference.

Discontinue the old system.

Plan for post-implementation review.
This package is designed and developed to solve the existing problems in electronics. Current
System at present maintained manually and gives minimum benefit to the user.
It is a user friendly package which anybody can operate, he need not to be a computer literate.
The software actually automates the stock keeping mechanism along with the bill generation
also keeps the records customer information and supplier information.
Record keeping and maintaining are very big problem now days for every firm. The use of
computer in each field is increasing rapidly.
30
SYSTEM DESIGN
- DATA DICTIONARY
- ER DIAGRAM
- DFD
- FLOWCHART
31
SYSTEM DESIGN
In software engineering, a design pattern is a general reusable solution to a commonly
occurring problem in software design. A design pattern is not a finished design that can be
transformed directly into code. It is a description or template for how to solve a problem that
can be used in many different situations. Object-oriented design patterns typically show
relationships and interactions between classes or objects, without specifying the final
application classes or objects that are involved. Algorithms are not thought of as design
patterns, since they solve computational problems rather than design problems.
Not all software patterns are design patterns. Design patterns deal specifically with problems
at the level of software design. Other kinds of patterns, such as architectural patterns, describe
problems and solutions that have alternative scopes
Uses
Design patterns can speed up the development process by providing tested, proven
development paradigms. Effective software design requires considering issues that may not
become visible until later in the implementation. Reusing design patterns helps to prevent
subtle issues that can cause major problems, and it also improves code readability for coders
and architects who are familiar with the patterns.
Often, people only understand how to apply certain software design techniques to certain
problems. These techniques are difficult to apply to a broader range of problems. Design
patterns provide general solutions, documented in a format that doesn't require specifics tied
to a particular problem.
Design patterns are composed of several sections. Of particular interest are the Structure,
Participants, and Collaboration sections. These sections describe a design motif: a
prototypical micro-architecture that developers copy and adapt to their particular designs to
32
solve the recurrent problem described by the design pattern. A micro-architecture is a set of
program constituents (e.g., classes, methods...) and their relationships. Developers use the
design pattern by introducing in their designs this prototypical micro-architecture, which
means that micro-architectures in their designs will have structure and organization similar to
the chosen design motif.
In addition, patterns allow developers to communicate using well-known, well understood
names for software interactions. Common design patterns can be improved over time, making
them more robust than ad-hoc designs.
33
DATA DICTIONARY
A Data Dictionary is a structured repository of data about data. It is a set of rigorous
definitions of all data elements and data structures. A Data Dictionary has many advantages.
Like-
Data Dictionary helps for documentation that is a valuable reference in any
organization.
-
Data Dictionary can improve analyst or user communication by establishing consistent
definitions of various elements, terms and procedures. During implementation, it
serves
as a common base against which programmers who are working on the
system compare their data descriptions.
-
Data Dictionary also control information maintained for each data element is crossreferenced in the data dictionary.
-
Finally, a data dictionary is an important step in building a data base. Most data base
management systems have a data dictionary as a standard feature.
Through this data dictionary is, we present the backend architecture of the given project.
34
List of Tables:
35
E-R DIAGRAM
It is a data model in which information stored in the database is viewed as set of entities, set
of relationship among entity. Simply it can be depend on domain knowledge and data
properties.
E R diagram has the following:

Entity

Relationship

Attributes
Entity: An entity is an object that has its existence in the real world. It includes all those
things about which data is collected.
An Entity set : It is a set of entities of the same type that share the same properties, or
attributes. It has two type1. Weak Entity: An entity set does not have sufficient attributes to form a primary key
called weak entity.
2. Strong Entity: An entity set which have a primary key is termed as a strong entity set.
Attributes: Attributes are units that describe the characteristics or properties of entities. In a
database, entities are represented by tables and attributes are represented by columns.
Relationship: Association among two or more entities.
Relationship Set: Collection of similar relationships.
Types of Relationship: There are three relationships in database.
One to One: One entity is associated with another entity. It is implemented using single table
by establishing relationship between same type of columns in a table.
36
One to Many: One entity is associated with many other entities. It is implemented using two
tables with primary key and foreign key relationships.
Many to Many: Many entities are associated with many other entities. It is implemented using
a junction table. The keys from both the tables form composite primary key of the junction
table.
ER Diagram Notation:
We can express the overall logical structure of a database graphically with an E-R diagram.
Its components are:
-
Rectangles: representing entity sets.
-
Ellipses: representing attributes.
-
Diamonds: representing relationship sets.
-
Lines: linking attributes to entity sets and entity sets to relationship sets.
37
ER Diagram of Project:
38
DATA FLOW DIAGRAM
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be used for the
visualization of data processing (structured design). Data flow diagrams were proposed by
Larry Constantine. Data flow diagrams can be used in both Analysis and Design phase of the
SDLC.
A DFD shows what kinds of information will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not show
information about the timing of processes, or information about whether processes will
operate in sequence or in parallel (which is shown on a flowchart)
Context level: It is common practice to draw the context-level data flow diagram first, which
shows the interaction between the system and external agents which act as data sources and
data sinks. The context diagram shows the entire system as a single process, and gives no
clues as to its internal organization.
Level 1: This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the system is
divided into sub-systems (processes), each of which deals with one or more of the data flows
to or from an external agent, and which together provide all of the functionality of the system
as a whole. It also identifies internal data stores that must be present in order for the system to
do its job, and shows the flow of data between the various parts of the system.
There are different notations to draw data flow diagrams, defining different visual
representations for processes, data stores, data flow, and external entities.
39
40
41
FLOWCHART
The pictorial representation of application called Flowchart. Using flowchart we can map all
the functioning of project graphically.
42
SAMPLE CODE SHEET
43
SAMPLE CODE SHEET
1. Code for Connection string in web.config file
<configuration>
<connectionStrings>
<add name="ConStr" connectionString="Data Source=.\SQLEXPRESS;
AttachDbFilename=|DataDirectory|\Database.mdf;Integrated Security=SSPI ;
User Instance=true"/>
</connectionStrings>
</configuration>
2. Code for Database Connection and Execute Incoming Queries:
using
using
using
using
using
using
using
using
using
System;
System.Collections.Generic;
System.Text;
System.Web;
System.Data.SqlClient;
System.Data;
System.Web.UI;
System.Web.UI.WebControls;
System.Configuration;
public class DatabaseConnection
{
public SqlConnection con;
public SqlCommand cmd;
public SqlDataAdapter da;
public DataSet ds;
public SqlDataReader dr;
//-----------------------public void Connect()
{
string constr = System.Configuration.ConfigurationManager.
ConnectionStrings["DatabaseConnectionString1"].ConnectionString;
con = new SqlConnection(constr);
if (con.State != ConnectionState.Open) con.Open();
}
//-----------------------public int IUD(string sql)
{
Connect();
cmd = new SqlCommand(sql, con);
return (cmd.ExecuteNonQuery());
}
//-----------------------public Boolean SearchRecord(string sql)
{
Connect();
cmd = new SqlCommand(sql, con);
dr = cmd.ExecuteReader();
if (!dr.Read()) return false;
else return true;
}
//-----------------------public void FillDS(string sql)
{
Connect();
cmd = new SqlCommand(sql, con);
da = new SqlDataAdapter(cmd);
44
ds = new DataSet();
da.Fill(ds);
}
};//End class
3. Code for Insert New Record
String sql;
sql = "INSERT INTO Records(FieldName1,FieldName2,..., FieldName_n)VALUES
('" & Text1.Text & "','" & Text2.Text & "',......., '" & Text_n.Text &
"')";
DatabaseConnection dbc = new DatabaseConnection();
dbc.IUD(sql);
4. Code for Update any Record
String sql;
sql = "UPDATE Records SET FieldName1='" & Text1.Text & "',
FieldName2 ='" & Text2.Text & "',..., FieldName_n ='" & Text_n.Text & "'
Where id=" & TextId
DatabaseConnection dbc = new DatabaseConnection();
dbc.IUD(sql);
5. Code for Delete any Record
String sql;
sql = "Delete FROM Records Where id=" & TextId
DatabaseConnection dbc = new DatabaseConnection();
dbc.IUD(sql);
6. Code for Search Record by ID
String sql;
sql = "Select * From Records Where id=" & TextId
DatabaseConnection dbc = new DatabaseConnection();
if (dbc.SearchRecord(sql))
{
TextBox1.Text = dbc.dr[1].ToString();
TextBox2.Text = dbc.dr[2].ToString();
-----}
7. Code for Show all Record on Grid / Dropdown
String sql;
sql = "SELECT * FROM Records"
DatabaseConnection dbc = new DatabaseConnection();
dbc.FillDS(sql);
Grid1.Datasource=dbc.ds;
Grid1.DataBind();
45
INPUT / OUTPUT SCREEN
DESIGN
46
INPUT / OUTPUT SCREEN DESIGN
1. Screenshot of File Structureof project with IDE
47
2. Screenshot
48
3. Screenshot
49
4. Screenshot
50
5. Screenshot
51
6. Screenshot
52
7. Screenshot
53
8. Screenshot
54
9. Screenshot
55
10.Screenshot
56
SYSTEM TESTING
SYSTEM MAINTENANCE
57
SYSTEM TESTING
When this system has been developed and the code has been generated, we begin the Testing
Process. The Testing Process focuses on the logical interval of the s/w, insuring that all
statement have been tested & on the functional external i.e. Conducting test to uncover errors
& we ensure that our given input is producing the actual result that with required results.
To validate the requirements of transaction, we have conducted a series of acceptable test.
Testing is vital to the success of the system. Testing makes the assumption that all the parts of
the system are correct; the goal will be successfully achieved.
The Alpha Testing: The user conducts the alpha testing at the developer’s site. We record errors & usage
problems. Alpha test has been conducted in the controlled environment.
The Beta Testing: The beta testing is conducted at one or more customer sites by the end user of the software.
The beta testing is the live software test in an environment that cannot be conduct by the
developer.
58
SYSTEM MAINTENANCE
When this system has been developed then the maintenance phase focuses on change
associated with error correction, adaptation required as the software’s environment evolves,
changes due to enhancement brought about by changing customers requirement.
Maintenance can be classified as: -
Corrective Maintenance: It means repairing process or performance failures or making changes
because of previously uncorrected problems or false assumption. Corrective maintenance
changes the software to correct defects.
Adaptive Maintenance: It means changing the program function. When the original
environment for which the software is developed is likely to change. It results in modification
to software to accommodate changes to its external environment.
The Perfective Maintenance: It means enhancing the performance or modifying the software to
respond to the user’s additional or changing needs. The customer / user will recognize
additional functions that will provide benefit.
The Preventive Maintenance: Computer software deteriorates due to change and because of this
preventive maintenance often called software reengineering must be conducted to enable the
software to serve the needs of end user.
59
CONCLUSION
LIMITATION
REFERENCES
60
CONCLUSION
The basic purpose of designing application as a minor purpose are learning new era in
computer development fields. While designing application we learn that how any software or
applications are deveoped, how many times are expensis, what problems are arises during
codeing and many more things.
In this project we have learn designing forms, working with database, connecting and
accessing with database for adding new records, updating, deleting and selecting records of
given database table.
We have also understand how any softwares are developed, how many tools are required,
what are our thinking during development and power of team work.
Finaly we can say this project may be very helpful for those user who wants to migrate
manual work to computer based automized work.
61
LIMITATIONS
Not any thing is perfect in the world. Some limitations are always them. In my project has
also a number of limitations that can not be removed due some reason like we are the beginer
with .NET language and Database Software. So we have chalanging tasks for learning this
development tool as well designing dummi project.
Although we try to developing error free application but some errors may be occurs while
input data at run time. Some limitation of this projects are following.
1. In some places of forms, when non non numeric values are entered in place of
required numeric value, we face unhandled error message because numeric validation
is not set.
2. Maximum limit of input data are not set.
3. We can get unhandled exceptions if wrong type of data inputs.
4. Title of forms are missing in many places.
5. Naming convections rules are not applied on controls name like TextBox, Label etc.
This project was for learning purpose. So there may be more limitation, but we try to
minimize all limitation in future.
62
REFERENCES
While cruising through our project we now and then followed the following books. We also
thought it apt to mention the tutorials taken and websites visited during the course of project.
Books for ASP.NET:
-
ASP.NET Bible: Mridula Parihar
-
SAMS, Unleased ASP.NET 3.0: Stephen Walther
-
Wrox, Beginning ASP.NET 2.0 with C#:Chris Hart, John Kauffman, David Sussman,
and Chris Ullman
-
C# 3.0:The Complete Reference: Herbert Schildt, ,TataMcGraw Hills
Books for Database:
-
SQL/PL SQL by Ivan Bayross
-
Database System Concepts by Silberschatz, Korth
Other Books:
-
System Analysis and Design by Awad.
-
Software Engineering by Roger S. Pressman,TataMcGraw Hills.
Websites:
-
www.w3schools.com
-
http://www.codeguru.com
-
www.codeproject.com
-
https://www.youtube.com
-
msdn.microsoft.com
-
http://www.asptoday.com
-
http://www.aspfriends.com
63