Project Report

On
“Cellucom”
Submitted in partial fulfillment of the requirement for the
Award of the degree of
Master of Computer Application
2006-2009
U.P.TECHNICALUNIVERSITY
LUCKNOW

GUIDED BY: Submitted By:

Mrs. Shailesh Pratap Singh Ravi Kumar Maurya
Reader M.C.A R.S.M.T 0510814032
(Varanasi)

Rajarshi School of Management & Technology

(U.P.AUTONOMOUS COLLEGE)
VARANASI-221002
 Project Report
On
“Cellucom”
Submitted in partial fulfillment of the requirement for the
Award of the degree of
Master of Computer Application
2006-2009
U.P.TECHNICALUNIVERSITY
LUCKNOW

GUIDED BY: Submitted By:

Mrs. Shailesh Pratap Singh Ravi Kumar Maurya
Reader M.C.A R.S.M.T 0510814032
(Varanasi)

Rajarshi School of Management & Technology

(U.P.AUTONOMOUS COLLEGE)
VARANASI-221002
________________________________________________
 Rajarshi School of Management & Technology
(Udai Pratap Autonomous College Campus Varanasi)
Varanasi-221002

website: www.rsmt.ac.in
Ph: +91-542-2281062
Fax: +91─542-2281062
________________________________________________

CERTIFICATE
This is to certify that Mr. Ravi Kumar Maurya, Roll No.0510814032 a
bonafide student of M.C.A.VI Semester of this institute has completed the
Degree Project titled “CELLUCOM” in Arrowline computer Institute of six
months duration in partial fulfillment of Master of Compurter Application
program of U.P.Technical University, Lucknow.

(MCA Co-ordinator) (Incharge RSMT)

Mrs: Shailesh Pratap Singh Mr. Aman Gupta
Reader MCA R.S.M.T(VNS) Reader MCA R.S.M.T(VNS)

Date:………………… Date: …………………

 CERTIFICATE

This is to certify that the following student with the name

Mr. Ravi Kumar Maurya bearing the H.T.No:0510814032 from Rajarshi
School of Management &Technology, Varanasi has successfully completed
the project titled “Cellucom” as part of the course
Curriculum in our organization.

He has done the project using ASP.NET 2.0 with C# and

SQL Server-2005 during the period 15-Jan-2009 to 22-Jun-2009, under the
Guidance and supervision of Mr. Shailesh Pratap Singh, Project Leader,
Arrow Line Computer Center, Varanasi.

He has completed the assigned project well with in the time frame. He is
sincere, hardworking and his conduct during period is commendable.

We wish him all the best in this endeavor.

For Arrow Line Computer Center

Anurag Singh
(Manaager-HR)

Flat No. 205, ArrowLine Computer Center, Shivpur,Varanasi-221002

Θ: +91-542-2283025

Date: 15th Jan 2009

Varanasi.
 Declaration

I here by solemnly declare that this project report entitled “Cellucom”

is bonafied work done by me during the Final year, MCA, and submitted to
the Department of Computer Science, RAJARASHI SHCHOOL OF
MANAGEMENT & TECHNOLOGY(affiliated to U.P. Technical
University Lucknow).

This report has not been submitted previously for the award of any other
degrees or diplomas by me or any others to any institute, university to the best
of my knowledge.

Ravi Kumar Maurya

 Acknowledgement

In my first major attempt to put my feet firmly on the world of practical

computing, I take this opportunity to express my gratitude to all of them who
have helped me out throughout this endeavor.

I am bound to express my gratitude to our project co-ordinator Mrs.

Shailesh Pratap Singh for her constant encouragement and guidance
throughout my project.

I am thankful to all the staff of Department of Computer Applications for

their cordial support during my project.

I thank my parents and my friends for their support and constant

encouragement during my entire work.

To one and all, I owe acknowledgements, who have directly or indirectly

aided me in completing project.

Ravi Kumar Maurya

 Contents

1. INTRODUCTION

2. SRS DOCUMENT

3. DESIGN PRINCIPLES & EXPLANATION

4. DESIGN DOCUMENT

4.1 SYSTEM DESIGN

5. FORMS & REPORTS

5.1 I/O SPECIMEN

5.2 I/O SAMPLES

6. TESTING

6.1 TEST REPORT & ANALYSIS

7. IMPLEMENTATION & USER MANUALS

8. LIMITATION

9. CONCLUSION

10. BIBLIOGRAPHY
INTRODUCTION
RSMT, Varanasi deputed a sixth months Industrial Project Training as a point
of curriculum of MCA, Computer. This college is affiliated to U.P. Technical
University, Lucknow. The student of M.C.A. are recorded to attached with
some industries in the sixth semester, where they are to be assigned some
project . The students are supposed to complete these projects and submit the
detailed project report to the concerned official in the industry.

During my stay at Varanasi, I worked on the project “Cellucom”.This is S/W

being constructed whose focus is on Cell marketing by internet Is now –a-days
very useful to Mobile, Laptop,Palmtop, are also have many brand and styles
deign various types of qualities which is shown by internet. Sometimes a new
brand is come in the market which is not know by any person if he search the
website www.Cellucom.com then the many options are present here one click
button all the information of cell are broadly described here.

Cellucom is a graphical application that makes choice a pleasant experience.

Cellucom has two types of users: 1. Admin and 2. Client.

Admin can do the following activities:

1. User Management: He makes some initial startup tasks while starting the
Cellcom server.

He can create new users and allow or disconnect the users. Admin also
close the Cell session, so that all the users will be disconnected.

2. Administrative Client: Admin can also involve in Cellucom as a client

from his admin console using this option.

3. Shut Down: He can shut down the Cellucom server.

4. Log Charts: He can create log charts which contain information of how
Cellucom has taken place.

Client can perform the following tasks:

A client can perform the following set of task related to the requirement of
the user when the user doesn’t know about a new thing in the market then
they are delayed for that particular resource which he doesn’t know get the
detailed information about that resource through this Site they get the
detailed information for the resource.
 SOFTWARE

REQUIRMENTS

SPECIFICATION
 Software requirement specification (SRS) is the starting point of
the software development activity. Little importance was given to this
phase in the early days of software development. The emphasis was
first on coding and then shifted to design.

As systems grew more complex, it became evident that the goals

of the entire system cannot be easily comprehended. Hence the need for
the requirement analysis phase arose. Now, for large software systems,
requirements analysis is perhaps the most difficult activity and also the
most error prone.

Some of the difficulty is due to the scope of this phase. The

software project is initiated by the client’s needs. In the beginning
these needs are in the minds of various people in the client
organization. The requirement analyst has to identify the requirements
by talking to these people and understanding their needs. In situations
where the software is to automate a currently manual process, most of
the needs can be understood by observing the current practice.

The SRS is a means of translating the ideas in the minds of the

clients (the input), into formal document (the output of the
requirements phase). Thus, the output of the phase is a set of formally
specified requirements, which hopefully are complete and consistent,
while the input has none of these properties.
 Software and Hardware Tools

Development Environment:

• Operating System: Windows XP

The system will be built on windows compatible environment.

The application will be web based developed using ASP.NET
technology.

• Web Server:

IIS WEB Server to serve as ASP.NET engine.The system

requires.

• Server side Application Software: ASP.NET Server Pages

(ASP.NET)

• Client Side Application Software: Java Script, HTML

• Data Base: SqlServer 2000

The system requires SqlServer 2000 as a database; however

the system will be SQL CLIENT complaint to work on any
standard database.

• Client Browsers:

Internet Explorer 6.0 or Netscape Navigator 4.7

The system requires Internet Explorer or Netscape Navigator
browser for client side.
 Hardware & Software Requirements

HARDWARE : Pentium III/IV & Above, 128 MB RAM.

SOFTWARE : c#.net 2.0 frame work,Asp.Net

RDBMS : Sql Server 2000,Sql Server2005

OPERATING SYSTEM : Windows NT or 2000 or Later

BACKUP MEDIA : Hard disk, Floppy, CD

MONITOR : VGA

Windows 2000XP/Windows 2000 NT Operating System

The main responsibility of an operating system is to manage computer’s

resources. All activities in the system scheduling application programs,

waiting files to disk, sending data across a network and so on should

function as seamlessly and transparently as possible. Windows 98

makes your computer easier to use, with new and enhanced feature.

Improved Reliability

Window 98 improves computer reliability by introducing new wizards,

utilities and resources that keep your system running smoothly.

Faster Operating System

Windows 98 includes tools that help your computer run faster than Windows 95 with

out adding new hardware. Window 98 includes a suite of programs designed to

optimized you’re web.

Integration

Windows 98 Explorer and Internet Explorer integrate local and Web-

based resources in a single viewer computer’s efficiency, especially

when used together. Window 98 makes your computer more

entertaining by new hardware. These enhancements provide you with

hours of fun.

Multitasking Concepts

Multitasking in general refers to an operating system’s capability to load

and execute several applications concurrently. A multitasking operating

system is consider a robust and reliable one if it successful shields

concurrent applications from each other, making them believe that they

system also shields application from other’s bugs.

T o a l ar g e ex tent , mul t i t ask i ng op e r at i ng sy st e m r e l ay

o n sy stem har d w ar e to i mp l e me nt t he se c ap ab il i t i e s. Ano t he r

i mp or tant asp ec t o f mul t i t ask i ng i s p ro c e ss sc he d ul i ng . As

p ro c ess ar e c ap ab l e o f ex e c ut i ng o nl y a si ng l e st r e am o f

i nstr uc tio n at any gi ve n, mul t i t ask i ng w o uld o b vio usl y no t b e

p o ssi bl e wi tho ut the t e c hni q ue o f t he c o nt ex t sw i tc hi ng . A

c o ntex t swi tc h, tr i g g er e d b y a sp e ci fi c e ve nt ( suc h as an

i nter r up t fro m a ti me r ci r c ui t or a c all by t he r unni ng

ap p l i c atio n to a sp ec i fi c func t i o n) , e sse nt i al l y c o nsi st of

savi ng the p ro c esso r c o nt e x t ( i nst r uc t io n p oi nt e r , st ac k

p oi nter , r eg i ster co nt e nt s) of o ne r unni ng pr o gr am and

l o adi ng that o f ano ther .

In a cooperative multitasking environment, the operating system relies

explicitly on applications to yield control by regularly calling a specific

set of operating system functions. Context switching takes place at

well-defined point during the execution of a program.

In a preemptive multitasking environment, the operating system can

interrupt the execution of an application at any time. This usually
happens when the operating system responds to hardware events, such
as a interrupt from a timer circuit. An application’s flow of execution
can be interrupted at any point, not only at predefined spots. This
realizes the complexity of the system.
 System Development Life Cycle
1.2.1 Initiation Phase
The initiation of a system (or project) begins when a business
need or opportunity is identified. A Project Manager should be
appointed to manage the project. This business need is documented in a
Concept Proposal. After the Concept Proposal is approved, the System
Concept Development Phase begins.

1.2.2 System Concept Development

Phase

Once a business need is approved, the approaches for

accomplishing the concept are reviewed for feasibility and
appropriateness. The Systems Boundary Document identifies the scope
of the system and requires Senior Official approval and funding before
beginning the Planning Phase.

1.2.3 Planning Phase

The concept is further developed to describe how the business will

operate once the approved system is implemented, and to assess how
the system will impact employee and customer privacy. To ensure the
products and /or services provide the required capability on-time and
within budget, project resources, activities, schedules, tools, and
reviews are defined. Additionally, security certification and
accreditation activities begin with the identification of system security
requirements and the completion of a high level vulnerability
assessment.
1.2.4 Requirements Analysis Phase

Functional user requirements are formally defined and delineate the

requirements in terms of data, system performance, security, and
maintainability requirements for the system. All requirements are
defined to a level of detail sufficient for systems design to proceed. All
requirements need to be measurable and testable and relate to the
business need or opportunity identified in the Initiation Phase.

1.2.5 Design Phase

The physical characteristics of the system are designed during this

phase. The operating environment is established, major subsystems and
their inputs and outputs are defined, and processes are allocated to
resources. Everything requiring user input or approval must be
documented and reviewed by the user. The physical characteristics of
the system are specified and a detailed design is prepared. Subsystems
identified during design are used to create a detailed structure of the
system. Each subsystem is partitioned into one or more design units or
modules. Detailed logic specifications are prepared for each software
module.

1.2.6 Development Phase

The detailed specifications produced during the design phase are

translated into hardware, communications, and executable software.
Software shall be unit tested, integrated, and retested in a systematic
manner. Hardware is assembled and tested.
1.2.7 Integration and Test Phase

The various components of the system are integrated and

systematically tested. The user tests the system to ensure that the
functional requirements, as defined in the functional requirements
document, are satisfied by the developed or modified system. Prior to
installing and operating the system in a production environment, the
system must undergo certification and accreditation activities.

1.2.8 Implementation Phase

The system or system modifications are installed and made operational

in a production environment. The phase is initiated after the system has
been tested and accepted by the user. This phase continues until the
system is operating in production in accordance with the defined user
requirements.

1.2.9 Operations and Maintenance Phase

The system operation is ongoing. The system is monitored for continued

performance in accordance with user requirements, and needed system
modifications are incorporated. The operational system is periodically
assessed through In-Process Reviews to determine how the system can
be made more efficient and effective. Operations continue as long as the
system can be effectively adapted to respond to an organization’s
needs. When modifications or changes are identified as necessary, the
system may reenter the planning phase.

1.2.10 Disposition Phase

The disposition activities ensure the orderly termination of the system

and preserve the vital information about the system so that some or all
of the
information may be reactivated in the future if necessary. Particular
emphasis is given to proper preservation of the data processed by the
system, so that the data is effectively migrated to another system or
archived in accordance with applicable records management regulations
and policies, for potential future access.

SDLC Objectives

This guide was developed to disseminate proven practices to system

developers, project managers, program/account analysts and system
owners/users throughout the DOJ. The specific objectives expected
include the following:

• To reduce the risk of project failure

• To consider system and data requirements throughout the entire
life of the system
• To identify technical and management issues early
• To disclose all life cycle costs to guide business decisions
• To foster realistic expectations of what the systems will and will
not provide
• To provide information to better balance programmatic, technical,
management, and cost aspects of proposed system development
or modification
• To encourage periodic evaluations to identify systems that are no
longer effective
• To measure progress and status for effective corrective action
• To support effective resource management and budget planning
• To consider meeting current and future business requirements

Key Principles

This guidance document refines traditional information system life cycle

management approaches to reflect the principles outlined in the
following subsections. These are the foundations for life cycle
management.
Life Cycle Management Should be used to Ensure a Structured Approach
to Information Systems Development, Maintenance, and Operation

This SDLC describes an overall structured approach to information

management. Primary emphasis is placed on the information and
systems decisions to be made and the proper timing of decisions. The
manual provides a flexible framework for approaching a variety of
systems projects. The framework enables system developers, project
managers, program/account analysts, and system owners/users to
combine activities, processes, and products, as appropriate, and to
select the tools and methodologies best suited to the unique needs of
each project.

Support the use of an Integrated Product Team

The establishment of an Integrated Product Team (IPT) can aid in the

success of a project. An IPT is a multidisciplinary group of people who
support the Project Manager in the planning, execution, delivery and
implementation of life cycle decisions for the project. The IPT is
composed of qualified empowered individuals from all appropriate
functional disciplines that have a stake in the success of the project.
Working together in a proactive, open communication, team oriented
environment can aid in building a successful project and providing
decision makers with the necessary information to make the right
decisions at the right time.

Each System Project must have a Program Sponsor

To help ensure effective planning, management, and commitment to

information systems, each project must have a clearly identified
program sponsor. The program sponsor serves in a leadership role,
providing guidance to the project team and securing, from senior
management, the required reviews and approvals at specific points in
the life cycle. An approval from senior management is required after the
completion of the first seven of the SDLC phases, annually during
Operations and Maintenance Phase and six-months after the Disposition
Phase. Senior management approval authority may be varied based on
dollar value, visibility level, congressional interests or a combination of
these.

The program sponsor is responsible for identifying who will be

responsible for formally accepting the delivered system at the end of
the Implementation Phase.

A Single Project Manager must be Selected for Each System

Project

The Project Manager has responsibility for the success of the

project and works through a project team and other supporting
organization structures, such as working groups or user groups, to
accomplish the objectives of the project. Regardless of organizational
affiliation, the Project Manager is accountable and responsible for
ensuring that project activities and decisions consider the needs of all
organizations that will be affected by the system. The Project Manager
develops a project charter to define and clearly identify the lines of
authority between and within the agency’s executive management,
program sponsor, (user/customer), and developer for purposes of
management and oversight.

A Comprehensive Project Management Plan is Required for Each System

Project

The project management plan is a pivotal element in the

successful solution of an information management requirement. The
project management plan must describe how each life cycle phase will
be accomplished to suit the specific characteristics of the project. The

project management plan is a vehicle for documenting the project

scope, tasks, schedule, allocated resources, and interrelationships with
other projects. The plan is used to provide direction to the many
activities of the life cycle and must be refined and expanded throughout
the life cycle.

Specific Individuals Must be Assigned to Perform Key Roles Throughout

the Life Cycle

Certain roles are considered vital to a successful system

project and at least one individual must be designated as

responsible for each key role. Assignments may be made on a

full- or part-time basis as appropriate. Key roles include

program/functional management, quality assurance, security,

telecommunications management, data administration, database

administration, logistics, financial, systems engineering, test and

evaluation, contracts management, and configuration

management. For most projects, more than one individual should

represent the actual or potential users of the system (that is,

program staff) and should be designated by the Program

Manager of the program and organization

1.0 SYSTEM ANALYSIS

System Requirements

Review & Validation

User Requirement Specifications

Software Requirements
Software Requirements
Review & Validation

Preliminary Design
Review & Validation
Detailed Functional Specifications

Detailed Design Global Implementation Specifications &

Review & Validation Detailed Implementation Specifications

Code and Debugging

Review & Validation Coding & Debugging

Testing
Testing
Review & Validation

Maintenance

Review & Validation Maintenance

Process Engineering of Application Software (Software Development Life

cycle)
1.1 Identification of the need

Since the world is growing for globalization, every organization wants to beat its

competitors and want to grow. Enterprise Resourceful Planning (ERP) is the need of

today’s organization. Survival on manual system is difficult so, that’s why organization

of the corporate world wants to computerize their departments. The modules should be

complete database driven and interactive that should provide the proper information

about the Placement and Training Organization.

Suc c ess o f a sy ste m d e p e nd s l ar g el y o n how ac c ur at e ly a

p ro b l em is d efi ned , t hor o ug hly inve st i g at e d and p ro p e r ly

c ar ri ed o ut to the c ho i c e o f sol ut i o n. Anal y si s is a p hase i n

w hi c h the req ui r ement s fo r t he ne w sy st e m ar e id e nt i fi e d .

Sy stem anal y si s is a d e t ai l e d st ud y o f t he var i o us o p er at i o ns

p er fo r med by a sy ste m and t he i r re l at i o nshi p w i t hi n and

o utsi d e o f the sy stem. T he q ue st i o n i s: w hat must b e d o ne to

so l ve the pr o bl em? O ne asp e c t o f anal y si s i s d e fi ni ng t he

b o und ar i es o f the sy st e m and d e t e r mi ni ng w he t he r o r no t a

c and i d ate sy stem sho ul d co nsi d e r o t he r re l at e d sy st e m.

Dur i ng anal y si s d ata ar e co ll e c t e d on t he avai l ab l e fi l e s,

d ec i si o n p oi nts and t r ansac t i o ns hand l e d by t he p ar e nt

sy stem. Data fl o w d i ag r am, i nt e r vi e w s, o nsi t e ob se r vat i o ns,

q uesti o nnai r es ar e use d as a l og i c al sy st e m mo d e l and t oo l s

to p er fo r m the anal y si s.
Tasks, which are performed as analyst:

 Gathered all facts about the present system from the

employees.

 Studied strength and weakness of the current system.

 Determined “what” must be done to solve the problem.

 Prepared a functional specifications document.

In or d er to r ed uc e t he t i me , t he r e is a ne e d fo r

c o mp uter iz ed sy stem t hat c ans r e t ri e ve d at a, i nse r t d at a,

up d ate exi sti ng d ata or d e l e t e e xi st i ng d at a. T he se mo d ul e s

ar e d evel o p ed wit the ai m of r e d uci ng t i me , re d uc i ng

manp o w er , r ed uc i ng co st so t hat t he r e co r d s c an b e e asi l y

mai ntai ned . T he vo l ume of wo rk and c o mpl e x i ty ar e

i nc r easi ng y ear b y y ear . T hi s sy st e m re d uc e s c o mpl e x i ty and

w or k lo ad

1.2 Preliminary Investigation:

A r eq uest to tak e assi st anc e fr o m i nfo r mat i o n sy st e m

c an b e mad e for many r e aso ns, b ut i n e ac h c ase so me o ne i n

the o rg ani z ati o n i ni ti at e t he re q ue st . Whe n t he r e q ue st i s

mad e , the fir st sy stem ac ti vi t y t he pr e l i mi nar y i nve st i g at i o n

b eg i ns. T hi s ac ti vi ty has t hr e e p ar t s:

 Request clarification

 Feasible Study

 Request approval
 Many r eq uests fro m e mp lo y e e s and use r s in t he

o rg ani z ati o n ar e no t c l e ar ly d e fi ne d . T he r e fo r e , it b e co me s

nec essar y that p ro jec t r e q ue st must be e x ami ne d and

c l ari fi ed p ro p erl y b efor e co nsi d e r i ng sy st e ms i nve st i g at i o n.

The feasibility study is carried out by a small group of people who are

familiar with information system techniques, understand the parts of

the business or organization

that will be involved or affected by the project, and are skilled in the

system analysis and design process.

Request Approval: It is not necessary that all request projects are

desirable or feasible. Some organizations receive so many projects

request from employees that only a few of them can be purchased.

However, those projects that are feasible and desirable should be put

into a schedule. In some cases, development can start immediately,

although usually system staff members are busy on other ongoing

projects. When such situation arises, management decides which

projects are more urgent and schedule them accordingly. After a project

request is approved, its cost, priority, completion time and personal

requirements are estimated and used to determine where to add it to

any existing project list. Later on, when the other projects have been

completed, the proposed application development can be initiated.

Analysis is a process of studying a problem and to find the best solution

to that problem. System analysis gives us the target for the design and

the implementation. Analysis is one phase, which is important phase for

system development lie cycle. System development is a problem solving

techniques. Analysis involves interviewing the client and the user. Thee

people and the existing documents about the current mode of operation

are the basic source of information for the analyst.

Analysis is the process of studying a problem to find the best solution to

that problem. System analysis gives us the target for the design and the

implementation. Analysis is one phase of the very important phase of

the system development life cycle. System development is a problem

solving techniques. Analyses involve interviewing the client and the

user. These people and the existing document about the current mode

of operation are the basic source of information for the analyst.

SOFTWARE ENGINEERING PARADIGM APPLIED

Computer Aided Software Engineering can be as simple as a single tool

that support a specific software engineering activity or as complex as a

complete “environment “ that encompasses tools, a database, people,

hardware, a network, operating system, standards, and myriad other

components. Each building block forms a foundation for the next, with

tools sitting as the top of the heap. It is interesting to note that the

foundation for effective CASE environment has relatively little to do for

software engineering tools themselves. Rather, successful

environments appropriate hardware and systems software. In addition,

the environment architecture must consider the human work patterns

that are applied during the software engineering process.

The environment composed of the hardware platform and system

support (including networking software, software management, and

object management services), the groundwork for CASE. But the CASE

environment itself demands other building blocks. A set of portability

services provides a bridge between CASE tools and their integration

framework and the environment architecture. The integration

framework is a collection of specialized programs that enables

individual’s CASE tools to communicate one another, to create a project

database, and to exhibit the same look and feel to the end user (the

software engineer). Portability services allow CASE tools and their

integration framework to migrate across different hardware platforms

and operating system with out significant adaptive maintenance.

The building blocks represent a comprehensive foundation for the

integration of CASE tools. However, most CASE tools in use today have

been: constructed using all these building blocks. In fact some CASE

tools remain “point solution:” That is, a tool is used to assist in a

particular software engineering activity (e.g. analysis modeling) but

does

not directly communicate with other tools, is not tied into a project

database, is not part of an integrated CASE environment (l-CASE).

Although this situation is not ideal, a CASE tool can be used quite

effectively, even if it is a point solution.

At the low end of the integration spectrum is the individual (point

solution) tool. When individual tools can provide tools provide facilities

for data exchange, the integration level is improved slightly. Such tools

produce output in a standard format that should be compatible with

other tools that can read the format. In some cases, the builder of
complementary CASE tools work together to form a bridge between the

tools (e.g. an analysis and design tool that is coupled with a code

generator). Using this approach, the team develops, synergy between

the tools separately. Single source integration occurs when a single

CASE tools vendor integrates a number of different tools and sells them

as a package.

Although this approach is quite effective, the closed architecture of

most single source environments precludes easy addition from other

vendors.

5.0 DESIGN

The most creative and challenging phase of the system life cycle is

system design. The term design describes a final system and the

process by which it is developed. It refers to the technical specifications

that will be applied in implementing the candidate system.

The first step is to determine how the output is to be produced

and in what format. Samples for the output (and input) are also

presented.

The second step is input data and master files (data base) have to

be designed to meet the requirements of the proposed output. The

operational (processing) phases are handled through program

construction and testing including a list of the programs needed to meet

the system’s objective and complete documentation. Finally, details

related to justification of the system on the user and the organization

are documented and evaluated by management as a step toward

implementation. To design the system we must note the following

points:

 To identify the Software Components which satisfy the System

Design.

 To design and document the Software Components and their

linkage.

In this component the software components and relevant interfaces

such as, interactions with existing internal and external systems,

network connections, standard input an output formats are to be

identified.

Identify Relevant Interfaces

 Interaction with existing internal systems.

 Interaction with external systems.

 Network Connections.

 Standard Input Formats

 Standard Output Formats.

Program Specification

Elements of Specifications required are

 How it is being accessed.

 Function called.

 Program Security.

 Field Details.

 Program Functions.
 1

From Analysis

Detailed
Cost
Output System
Justification
Design Documentation
and
Candidate
design
Input
Design Design
submitted to
management
for approval
File
Design

Processing No
Design Design Abandon project
accepted

Yes
Test
Programs

S T E PS I N S Y S T E M D E S I G N
 STEPS IN SYSTEM DESIGN

Databases and database technology are having a major impact on the growing use of

computers. It is fair to say that databases will play critical role: in almost all areas

where computers are used. Including business, engineering, medicine, law, education

and library, science to name a few. A database is a collection of related data. By data we

mean known facts that can be recorded and that have implicit meaning for example,

consider, the names, telephone numbers and addresses of the people you know. You

may have recorded this data in an indexed address, book, or you may have stored it on

a diskette. Using a personal computer and software such as DBASE IV or V,

PARADOX, MS EXCEL OR MS ACCESS. This is a collection of related data with an

implicit meaning and hence is a database.

A database is a logically coherent of with some inherent meaning.

A database represents some aspects of the real world. Sometimes called the mini-world

or the universe of discourse (UOD). Changes to the mini-world are reflected in the

database.

A database is designed, built and populated with data for the specific people. It has an

intended group of users and some preconceived applications in which the users are

interested.

A database can be of any size and of varying complexity. For example, the list of names

and addresses referred to earlier may consist of only a few hundred records, each with

simple structure. On the other hand the card catalog of a large library may contain half

a million cards stored under different categories by primary author’s last name, by

subject, by book title with each category organized in alphabetic order.

A database may be generated and maintained or by machine. The library card catalog

is an example of a database that may be created and maintained either by a group of

application programs written specially for that task or by a database management

system.

A database management system (DBMS) is a collection of programs that enables users

to create and maintained a database. The DBMS is hence a general-purpose software

system that facilities tile processed of defining, constructing and manipulating database

for various applications. Defining a database involves specifying the data types,

structures and constraints for the data to be stored in the database. Constructing the

database is the process of storing the data itself on some storage medium that is

controlled by the DBMS. Manipulating a database includes such functions as querying

the database to reflect changes in the mini-world, and generating reports form the data.

With the advent of the graphical operating system like windows, the world of imputing

went through a dramatic change. It opened up a whole new world of graphics.

Interfaces that use graphics came to known so graphical user interface (GUI). These

became very popular because the users could identify with images than words. Mention

tile word print to a person and it invokes the image of a printer. The primary

requirements for an interface are that it is easy to use. We must be able react intuitively

to an interface presented to us. This is possible if the interface presented is such that is

it emulates real life.

 . DATA FLOW DIAGRAM

Data Flow Diagramming is a means of representing a system at

any level of detail with a graphic network of symbols showing data
flows, data stores, data processes, and data sources/destination.

The data flow diagram is analogous to a road map. It is a

network model of all possibilities with different detail shown on
different hierarchical levels. This processes of representing different
details level is called “leveling” or “partitioning” by some data flow
diagram advocates. Like a road map, there is no starting point or stop
point, no time or timing, or steps to get somewhere. We just know that
the data path must exist because at some point it will be needed. A road
map shows all existing or planned roads because the road is needed.

Details that is not shown on the different levels of the data

flow diagram such as volumes, timing, frequency, etc. is shown on
supplementary diagrams or in the data dictionary. For example, data
store contents may be shown in the data dictionary.

Data Flow Diagram (DFD) uses a number of symbols to

represent the systems. Data Flow Diagram also known as ‘Bubble Chart’
is used to clarify system requirements and identifying the major
transformations that will become programs in system design. So it is
the starting point of the design phase that functionally decomposes the
requirements specifications down to the level of details.

Terms used in DFD

• Process
 A process transforms data values. The lowest level processes are
pure functions without side effects. An entire data flow graphics high
level process.

Graphical representation:

Graphical Representation:

• Data flows

A data flow connects the output of an object or process to input of

another object or process. It represents the intermediate data value
within a computation. It is represented by an arrow and labeled with a
description of data, usually its name or type.

Graphical Representation:

• Actors
An actor is active object that drives the data flow graph by
producing or consuming values.

• Data store

A data store is a passive object with in a data flow diagram that

stores data for later access.
 Graphical Representation:

• External Entity

A rectangle represents an external entity such as a librarian

,a library member.

Graphical Representation:

• OutPut Symbol This box represented data production

during human computer interaction

Graphical Representation:
 Information Flow of Data for Testing

Software
Test Results Evaluatio
Configuration
n

Testing Error
Rate Debu
Data g
Expected
Test Results
Reliabilit
Configuration y
Model
Correction

Predicted Reliability

Information Flow of Data Testing

2.0 FEASIBILITY STUDY

A feasibility study is conducted to select the best system that

meets performance requirement. This entails an identification
description, an evaluation of candidate system and the selection of best
system for he job. The system required performance is defined by a
statement of constraints, the identification of specific system objective
and a description of outputs.

The key consideration in feasibility analysis are :

1. Economic Feasibility :

2. Technical Feasibility :

3. Operational Feasibility:

Economical feasibility

It looks at the financial aspects of the project. It determines

whether the management has enough resources and budget to invest in
the proposed system and the estimated time for the recovery of cost
incurred. It also determines whether it is worth while to invest the
money in the proposed project. Economic feasibility is determines by
the means of cost benefit analysis.The proposed system is economically
feasible because the cost involved in purchasing the hardware and the
software are within approachable. The personal cost like salaries of
employees hired are also nominal, because working in this system need
not required a highly qualified professional. The operating-environment
costs are marginal. The less time involved also helped in its economical
feasibility. It was observed that the organization has already using
computers for other purpose, so that there is no additional cost to be
incurred for adding this system to its computers.
The backend required for storing other details is also the same database

that is Sql. The computers in the organization are highly sophisticated

and don’t needs extra components to load the software. Hence the

organization can implement the new system without any additional

expenditure. Hence, it is economically feasible

The result of the feasibility study is a formal proposal. This is simply

report-a formal document detailing the nature and the scope of the

proposed solution. The proposals summarize what is known and what is

going to be done. Three key considerations are involved in the

feasibility analysis: economic, technical and operational behavior.

2.3.1 Economic Feasibility:

Economic analysis is the most frequently used method for evaluating

the effectiveness of a candidate system. More determine the benefits

and the saving that are expressed from a candidate system and

compare them costs. If benefits outweigh costs. Otherwise, further

justification or alterations in the proposed system will have to be made

if it is to have a chance of being approved. This is an ongoing effort that

improves in accuracy at each phase of the system life cycle.

2.3.2 Technical Feasibility:

Technical feasibility center around the existing computer system

hardware etc. and to what extent it can support the proposed addition.

For example, if the current computer is operating at 80% capacity an

arbitrary ceiling – then running another application could over load the

system or require additional hardware. This involves financial

consideration to accommodate technical enhancements. If the budget is

a serious constraint then the project is judged not feasible.

2.3.3 Operational Feasibility:

It is common knowledge that computer installations have some thing to

do with turnover, transfers, retraining and changes in employee job

status. Therefore, it is understandable that the introduction of a

candidate system requites special efforts to educate, sell, and train the

staff on new ways of conducting business.

2.3.4 C h o i c e o f P l a t f o r m ?

In any organization a lot of data is generated as result of day-to-day

operations. In the past, all kind of data – be it business of a company.
Since the task was performed manually, it was time consuming and
error prone. With the advent of computer, the task of maintaining large
amount of data has undergoes a sea change. Today computer system
have become so user friendly that even first time users can create their
own application with the help of tools such as MS-Access, Fox-Pro and
SQL Server. These tools are very visual and hence user friendly. They
provide a point and click environment for building applications that can
interact with large amount of data
 PLATFORM (Technology/Tool Selection)

Introduction to .net

ASP.NET is a high-level, third-generation programming language

like C, FORTRAN, Perl and many others. It is a platform for distributed
computing – a development and run-time environment that contains
built-in support for the World Wide Web.

Client Side Interface:

In client side interface we are using:-

• ASP .NET – for Internet Based Application.

ASP .NET are middle-ware technologies which are used in web based
projects because they use:-

• HTTP Protocol to handle Request and Response.

• They are invoked through Browser.
• They give output in HTML format.
• They need Browser Support.

BACK-END
 SqlServer 2000

Why we are using SqlServer 2000 (RDBMS)?

Some of the merits of using SqlServer 2000 (RDBMS) are as under:

• Centralization of database.
• Client Server Technology.
• Security.
• Normalization of Data Base.
• Relationship.
• Transaction Processor.
• It gives some internet related features.

Hence because of these features we are using SqlServer 2000 as a back-

end technology.

Weather you are working on LAN projects or Distributed projects,

there are two sides of it:-

• Front End
• Back End

Front End remains on client side. Front end is made for end user
who uses our application. Basically in front end, our input-output forms
reside which takes the input from the client and gives output back to
client.

Backend remains on server side and has two components viz.

• Server side programs

• Data Base

Database is the most important thing in this universe as database

gives identity to a thing. It provides us with a repository where we can
store ample amount of data, at one place. Without a database, existence
of a thing is impossible.

While working on a project first step is to design a database.

What is a database?

Data Base is a collection of tables and table is a collection of

records in a tabular form i.e. in row and columns format.

Data Base can be divided into two parts:-

• RDBMS
• DBMS

We will be using RDBMS (Relational Database Management

System) in our project i.e. SqlServer 2000 Enterprise Edition.

ABOUT SQLSERVER 2000

SqlServer 2000 contains all the features of previous version. It

also supports some new features & enhancement to some existing
features. SqlServer 2000 servers provide deficient & effective solution
for the major features.

• Large Database & Space Management Control

SqlServer 2000 supports the largest database potential of

hundreds of Giga Bytes in size. To make efficient use of expensive
devices, it allows full control of space usage.
 • Many Concurrent Database Performances

It supports large no of concurrent users executing a variety of

database applications operation on the same data. It minimizes data
connection & guarantees data concurrency.

• High Transaction Processing Performance

SqlServer 2000 maintains the processing features with a high

degree of overall system performance. Database users don’t suffer from
slow processing performance.

• High Availability

SqlServer 2000 works 24 hours a day with no downtime or limited

database throughput. Normal system operation such as database
backup & partial system failure doesn’t interrupt database use.

• Controlled Availbility

SqlServer 2000 can selectively control the availability of data at

the database level & sub database level. E.g. an administrator can
disallow use of a specific application .Data can be reloaded without
affecting other application.

• Industry Accepted Standards

SqlServer 2000 adheres to industry accepted standards for the

data access language operating system, user interface & network
communication protocols.

• Manageable Security
 To protect against unauthorized database aspects & users,
SqlServer 2000 provides failsafe security features to limit & monitor the
data area. The system makes it easy to manage even the most
completed designs for data assets.

• Database Enforced Integrity

SqlServer 2000 enforces data integrity “Business rules”, that

dictate the standards for applicable data. As a result, the cost of coding
& managing checks in many database applications is eliminated.

• Distributed Database System

For community environment that are connected via networks,

SqlServer 2000 combines the data physically located on different
computers in one logical database that can be accessed by all the
network users. Distributed systems have same degree of user
transparency & data consistency as non-distributed systems, yet receive
the advantages of local database management.

• Portability

SqlServer 2000 software is compatible to work under different

operating system & same on all system. Applications developed on
SqlServer 2000 can be used on virtually any system with little or no
more modification.

• Compatibility

SqlServer 2000 software is compatible with industry standards,

including most industry standard operating systems. Applications
developed on SqlServer 2000 can be used on virtually any system with
little or no modification.
 • Connectivity

SqlServer 2000 software allows different types of computers &

operating system to share information in networks.

NEW FEATURES OF SQLSERVER 2000

• Improved Scalability

The maximum size of an SqlServer 2000 database has been

increased to support hundreds of terabytes depending on the operating
system on which it resides.

• Improved Security

SqlServer 2000 server now includes password management so

that a password has a limited lifetime & must meet certain complexity
such as minimum length. An account can be locked after a specified
number of failed login attempts.

• Improved Performance via Partition

A table of index can be divided into smaller pieces called

partitions, based on the value of one or more columns. A table partitions
can be individually managed so that operation in one partition does not
affect the availability of data on other partitions. Also insert, update,
delete operations against a partitioned table can be processed partially.
 In other words, the SqlServer 2000 8 server can assign a portion
of the work to execute a single DML statement to multiple processes,
which may then be allocated to multiple processes by the server
operating system. As a result, the parallel DML operations are
completed more quickly.

• Enhanced Support for Database Replication

The performance & manageability of database replication has

been significantly improved.

• Capability to handle a much larger number of concurrent

users

By pooling database connection, the SqlServer 2000 8 server is

able to service a much larger number of concurrent users, up to 3000,
depending on the server’s operating system & server hardware
resources.

• New & Improved Data Types

Some existing data types have been enhanced & new data types
have been introduced.

• Improved Select Statement

A new feature of the select statement allows a sub query to be

used in place of a table in a from clause.
Now when we are discussing Database, there is one more
thing attached to it, i.e. “Data Base Models”
Database Models
There are three kinds of database models:-

• Single tier architecture.

• Two tier architecture.
• N- Tier architecture.

Single tier Architecture:

In this kind of architecture, database and client application

remains on one machine i.e. there is no client-server technology, there
is no centralization of database, and basically it is a stand alone system.

Two tier Architecture

In this kind of architecture, database and client application is on

two different machines i.e. Database on one machine and the
application on another machine. In this type of architecture, the
implementation of client-server technology is done and centralization of
data base is there, but it has two demerits:-

• Security is not there

• Multiple Client access is not there.

N- Tier Architecture: -
In this kind of architecture, there is a middle-ware in between the
client and database. Middle ware checks the validity of the client i.e.
weather the client can access the database or not. Hence there is
security in it as well as middle-ware allows multiple clients access.

What is Middle-Ware?

Middle-ware is a concept. Middle-ware provides centralization of

business logic i.e. instead of putting logic on each and every client
machine we put logic on a centralized server. Hence middle ware is
nothing but a server side program where all your business logic and
business methods reside. It remains on server side and it has all the
logical building. Middle ware provides: -

• Multiple Client access.

• Centralized business logic in case of distributed application.

Because we are working on Distributed Application Based Project we

need platform independent Language like

.NET AND SQL SERVER IS USE MANLY FOR

CODE EFFICIENCY

Database Management
Visual Basic allows we to manage databases while directly connected to them at
design time. Depending on the feature of our database and our access
privileges, we can use Visual Basic tools to add, remove, or modify.
 Databases
 Tables or Columns
 Views and synonyms
 Relation between Tables
 Indexes
 Constraints and triggers
 Stored procedures, functions, and packages
 Queries that return sets of data, or queries that modify a database by
adding, updating, copying, or deleting records.

Managing databases is a separate task from adding database functionality to a

Web Application. Therefore to manage databases in Visual Basic, we create a
database project. To help we perform various database management tasks, a
database project in Visual Basic .net provides the following tools:

Data View Window: A window that displays the entire database objects
that we can currently Work with. From the Data View window, we can edit
objects such as tables, views, stored procedures, and triggers.

Data View window showing available database objects

 Database Designer: A tool that displays our Microsoft SQL server database as
a database diagram, which we can edit to add or modify table and column
definitions, define relationships, create indexes, and add constraints

Database diagram representing a database visually

Query Designer: A designer that, allows we to visually create SQL statements to
query or modify a database.

Query Designer being used to create a SQL statement

 View Designer A version of the Query Designer that allows

we to visually create the SQL statement that defines a view.

 Stored Procedure Editor:

A window for creating stored procedure that includes a link to the Query Designer
to construct SQL statements.

 Trigger Editor: A window for creating triggers

 Script Editor: A window for creating SQL scripts, which are SQL
statements that are independent of any particular database. We can put SQL
scripts under source control as well.

Overview of the .NET Framework

The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet. The .NET
Framework is designed to fulfill the following objectives:

• To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-
distributed, or executed remotely.
• To provide a code-execution environment that minimizes software deployment
and versioning conflicts.
• To provide a code-execution environment that guarantees safe execution of code,
including code created by an unknown or semi-trusted third party.
• To provide a code-execution environment that eliminates the performance
problems of scripted or interpreted environments.
• To make the developer experience consistent across widely varying types of
applications, such as Windows-based applications and Web-based applications.
 • To build all communication on industry standards to ensure that code based on
the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and
the .NET Framework class library. The common language runtime is the foundation of
the .NET Framework. You can think of the runtime as an agent that manages code at
execution time, providing core services such as memory management, thread
management, and remoting, while also enforcing strict type safety and other forms of
code accuracy that ensure security and robustness. In fact, the concept of code
management is a fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime is known as
unmanaged code. The class library, the other main component of the .NET Framework,
is a comprehensive, object-oriented collection of reusable types that you can use to
develop applications ranging from traditional command-line or graphical user interface
(GUI) applications to applications based on the latest innovations provided by
ASP.NET, such as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common
language runtime into their processes and initiate the execution of managed code,
thereby creating a software environment that can exploit both managed and
unmanaged features. The .NET Framework not only provides several runtime hosts,
but also supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side

environment for managed code. ASP.NET works directly with the runtime to enable
Web Forms applications and XML Web services, both of which are discussed later in
this topic.

Internet Explorer is an example of an unmanaged application that hosts the runtime (in
the form of a MIME type extension). Using Internet Explorer to host the runtime
enables you to embed managed components or Windows Forms controls in HTML
documents. Hosting the runtime in this way makes managed mobile code (similar to
Microsoft® ActiveX® controls) possible, but with significant improvements that only
managed code can offer, such as semi-trusted execution and secure isolated file storage.

The following illustration shows the relationship of the common language runtime and
the class library to your applications and to the overall system. The illustration also
shows how managed code operates within a larger architecture.

The following sections describe the main components and features of the .NET
Framework in greater detail.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution,
code safety verification, compilation, and other system services. These features are
intrinsic to the managed code that runs on the common language runtime.
With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin (such as the Internet,
enterprise network, or local computer). This means that a managed component might
or might not be able to perform file-access operations, registry-access operations, or
other sensitive functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an
executable embedded in a Web page can play an animation on screen or sing a song,
but cannot access their personal data, file system, or network. The security features of
the runtime thus enable legitimate Internet-deployed software to be exceptionally
feature rich.

The runtime also enforces code robustness by implementing a strict type- and code-
verification infrastructure called the common type system (CTS). The CTS ensures that
all managed code is self-describing. The various Microsoft and third-party language
compilers generate managed code that conforms to the CTS. This means that managed
code can consume other managed types and instances, while strictly enforcing type
fidelity and type safety.

In addition, the managed environment of the runtime eliminates many common

software issues. For example, the runtime automatically handles object layout and
manages references to objects, releasing them when they are no longer being used. This
automatic memory management resolves the two most common application errors,
memory leaks and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers can
write applications in their development language of choice, yet take full advantage of
the runtime, the class library, and components written in other languages by other
developers. Any compiler vendor who chooses to target the runtime can do so.
Language compilers that target the .NET Framework make the features of the .NET
Framework available to existing code written in that language, greatly easing the
migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software of
today and yesterday. Interoperability between managed and unmanaged code enables
developers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted.
A feature called just-in-time (JIT) compiling enables all managed code to run in the
native machine language of the system on which it is executing. Meanwhile, the memory
manager removes the possibilities of fragmented memory and increases memory
locality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, such

as Microsoft® SQL Server™ and Internet Information Services (IIS). This
infrastructure enables you to use managed code to write your business logic, while still
enjoying the superior performance of the industry's best enterprise servers that support
runtime hosting.
.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate
with the common language runtime. The class library is object oriented, providing
types from which your own managed code can derive functionality. This not only makes
the .NET Framework types easy to use, but also reduces the time associated with learning
new features of the .NET Framework. In addition, third-party components can integrate
seamlessly with classes in the .NET Framework.

.NET Framework to develop the following types of applications and services:

• Console applications.
• Scripted or hosted applications.

• Windows GUI applications (Windows Forms).

• ASP.NET applications.
• XML Web services.
• Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that
vastly simplify Windows GUI development. If you write an ASP.NET Web Form
application, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the
desktop, enabling a user to perform a task. Client applications include applications
such as word processors and spreadsheets, as well as custom business applications such
as data-entry tools, reporting tools, and so on. Client applications usually employ
windows, menus, buttons, and other GUI elements, and they likely access local
resources such as the file system and peripherals such as printers.

Server Application Development

Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
managed code to control the behavior of the server. This model provides you with all
the features of the common language runtime and class library while gaining the
performance and scalability of the host server.
The following illustration shows a basic network schema with managed code running in
different server environments. Servers such as IIS and SQL Server can perform
standard operations while your application logic executes through the managed code.

Server-side managed code

ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use
IIS and ASP.NET as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.
 INTRODUCTION OF Sql Server 2000

 Introduction to Oracle and Its Tools:

The SQL Server product is primarily divided into:

 SQL Server Server Tools

 SQL Server Client Tools

 SQL Server Server:

Microsoft the No. one company in the software that produces the most
widely used, front end and Server based Multi user RDBMS. The SQL
Server is a program installed on the Server’s hard disk driver. This program
must be loaded in RAM so that it can process user requests.

The SQL Server Server product is either called SQL Server Professional
Or SQL Server Enterprise.

The SQL Server takes care of the following:

 Updating the database.

 Retrieving information from the database.
 Accepting query language statements.
 Enforcing security specifications.
 Enforcing data integrity specifications.
 Enforcing transaction consistency.
 Managing data sharing.
 Optimizing queries.
 Managing system catalogs.

 Sql Server Client Tools:

Once the Sql Server engine is loaded into the server’s memory, users would
have to log into the engine to get work done. Microsoft has several client-based
tools that facilitate this. The client tool most commonly used for Commercial
Application Development is Visual basic.
 What is SQL Used for:

Using SQL one can create and maintain data manipulation objects such
as table, views, sequence etc. These data manipulation objects will be
created and stored on the server's hard disk drive, in a table space, to
which the user has been assigned.

Once these data manipulation objects are created, they are used
extensively in commercial applications.

 DML, DCL, DDL:

In addition to the creation of data manipulation objects, the actual

manipulation of data within these objects is done using SQL.

The SQL sentences that are used to create these objects are called DDL's or
Data Definition Language. The SQL sentences used to manipulate data within
these objects are called DML's or Data Manipulation Language. The SQL
sentences, which are used to control the behavior of these objects, are called
DCL's or Data Control Language.

Hence, once access to the SQL*Plus tool is available and SQL syntax is
known, the creation of data storage and the manipulation of data within
the storage system, required by commercial applications, is possible.

The Data type that a Cell can hold:

Data Type Description

CHAR(size) : This data type is used to store character strings

values of fixed length. The size in brackets
determines the number of characters the cell
can hold. The maximum number of characters
this data type can hold is 255 characters.

VARCHAR (size) / : This data type is used to store variable length

VARCHAR2 (size) alphanumeric data. The maximum this data type
can hold is 2000 character.

NUMBER (P,S) : The NUMBER data type is used to store numbers

(fixed or floating point). Numbers of virtually
any magnitude maybe stored up to 38 digits of
 precision.

DATE : This data type is used to represent data and

time. The standard format is DD-MON-YY as in
24-JAN-02. To enter dates other than the
standard format, use the appropriate functions.
Date Time stores date in the 24-hour format.

LONG : This data type is used to store variable length

character strings containing up to 2GB. LONG
data can be store arrays of binary data in ASCII
format.
 SYSTEM DESIGN

Introduction

System design provides the understandings and procedural details

necessary for implementing the system recommended in the system
study. Emphasis is on the translating the performance requirements
into design specifications. The design phase is a transition from a user-
oriented document (System proposal) to a document oriented to the
programmers or database personnel.

System design goes through two phases of development:

1) Logical Design

2) Physical Design

A data flow diagram shows the logical flow of the system. For a
system it describes the input (source), output (destination), database
(data stores) and procedures (data flows) all in a format that meets the
user’s requirement. When analysis prepare the logical system design,
they specify the user needs at a level of detail that virtually determines
the information flow into an out of the system and the required data
resources. The logical design also specifies input forms and screen
layouts.

The activities following logical design are the procedure followed

in the physical design e.g., producing programs, software, file and a
working system. Design specifications instruct the user about what the
system should do.
Logical and Output Design:

The logical design of an information system is analogous to an

engineering blue print of an automobile. It shows the major features
and how they are related to one another. The detailed specification for
the new system was drawn on the bases of user’s requirement data.
The outputs inputs and databases are designed in this phase.

Output design is one of the most important features of the

information system. When the outputs is not of good quality the users
will be averse to use the newly designed system and may not use the
system. There are many types of output, all of which can be either
highly useful or can be critical to the users, depending on the manner
and degree to which they are used.

Outputs from computer system are required primarily to

communicate the results of processing to users, They are also used to
provide a permanent hard copy of these results for later consultation.
Various types of outputs required can be listed as below:

• External Outputs, whose destination is outside the

organisation

• Internal outputs, whose destination is with the organisation

• Operational outputs, whose use is purely with in the computer

department e.g., program-listing etc.

• Interactive outputs, which involve the user is communicating

directly with the computer, It is particularly important to
consider human factor when designing computer outputs. End
user must find outputs easy to use and useful to their jobs,
Without quality output, user may find the entire system
unnecessary and avoid using it. The term “Output” in any
information system may apply to either printer or displayed
information. During the designing the output for this system,
it was taken into consideration, whether the information to be
presented in the form of query of report or to create
documents etc.
 Other important factors that were taken into consideration
are:

The End user, who will use the output.

• The actual usage of the planned information

• The information that is necessary for presentation

• When and how often output and their format is needed. While
designing output for project based Attendance Compilation
System, the following aspects of outputs designing were
taken into consideration.

• The outputs (i.e., well formatted table outputs in the screen

itself) designed are simple to read and interpret.

• Format of each output was another important point taken into

consideration. Output media, for each output appropriate
media is decided whether it will be displayed on screen or will
be taken to printer or both.

• Other output design related specifications, i.e., how frequently

the outputs will be generated, how many pages or sheets
approximately it will keep up, what is its planned use and
output distribution to users are also taken into account.

These were a few major designing issues, which were taken into
consideration, while deciding the output specifications for the system.
As direct beneficiary of reports is the user community, they were
consulted constantly at every level. Formats and screen design for
various reports were identified, taking into account the user
requirements. Before finalising these were given to users for any
improvement and suggestions. End users issues taken into
consideration were Readability, Relevance and Acceptability.

Once all the output reports to be generated by ACS system were

identified, they were given to users for their acceptance. For
prototyping various outputs, final outputs models were created with
dummy data, before they were finalised.
Output Sources:

Output contents originate from these sources:

• Retrieval from a data source.

• Transmission from a process or system activity.

• Directly from an input source.

The information produced in an output can be presented as

• Tabular contents

• Graphic format

• Using Icons

Output Definition:

The output should be defined in terms of:

Types of outputs

• Content-headings, numeric, alphanumeric, etc.,

• Format-hardcopy, screen, microfilm, etc.,

• Location-local, remote, transmitted, etc.,

• Frequency-daily, weekly, hourly, etc.,

• Response-immediate with in a period, etc.,

Data items

The name given to each data item should be recorded and its
characteristics described clearly in a standard form:

• Whether alphanumeric or numeric

• Legitimate and specific range of characteristics

• Number of characters

• Positions of decimal point, arithmetic design, etc.,

Input Design:

The input design is the link that ties the information system into the
user’s world. Input specifications describe the manner in which data
enters the system for processing. Input design features can ensure the
reliability of the system and produce results from accurate data, or they
can result in the production of erroneous information.

Input Design consists of

• developing specifications and procedures for data preparation

• Steps necessary to put data into a usable form for processing.

• Data entry, the activity of putting data into the computer

processing.

Objectives of Input design

Five objectives of design input focus on

• Controlling the amount of input required

• Avoid delay

• Avoiding errors in data

• Avoiding extra steps.

• Keeping the process simple.

Input stages several activities have to be carried out as part of te

overall input process. They include some or all of the following.

Data recording (i.e., collection of data)

Data encapsulation(i.e.,transfer of data)

Data conversion(i.,e.,controlling the flow of data)

Data transmission(i.e.,transporting te data)

Data validation(i.e.,checking te input data)

Data correction(i.e.,correcting the errors)

Input Performa were designed, after a careful discussion with

users. It was attempted to cover all user requirements. Designed
Performa were given to user for any suggestion and final approval.

Various data items were identified and wherever necessary were

recorded.

Input designs are aimed at reducing the chances of mistakes of

errors. As the human beings are prone to errors there is always a
possibility of occurrence of chance of errors. Adequate validation checks
are incorporated to ensure error free data storage. Some of the data
validation checks applied are as following:

• Redundancy of data is checked. It means the records of

primary key do not occur twice.

• Primary key field of any table must not be left blank.

• Wherever items are coded, input code is checked for it’s

validly with respect to several checks.

• Utmost care has been taken to incorporate the validation at

each stage of the system. E.g. when entering records into
employee information table for employee, it is checked that
whether the corresponding employee exists in the employee
information table etc.,

Enough messages and dialogue boxes are provided while design

screen, which does guide user at the time of any errors, or at time of
entry. This feature provides a user-friendly interface to native users. It
can be emphasized that input deigns of CRM is so designed that it
ensures easy and error free data entry mechanism. Once one is sure of
input data the output formatting becomes an routine work.
SOFTWARE DESIGN

The purpose of this phase is to plan a solution for the problem

specified by the requirement document. This is first step in moving from
the problem domain to solution domain. Designing activity is divided
into two parts.

a) System Design :
It aims to identify the modules that should be in the system, the
specification of these modules and how they interact with each other to
produce the desired result.

b) Detailed Design :
The internal goal of each of the modules specified in the system design
is decided

DATABASE DESIGN

A database is a collection of inter-related data stored with a

minimum of redundancy to serve many applications. It minimizes the
artificiality embedded in using separate files. The primary objectives are
fast response time to enquires, more information at low cost, control of
redundancy, clarity and ease of use, accuracy and fast recovery. The
organization of data in a database aims to achieve three major
objectives, they are data integration, data integrity and data
independence. During the design of the database at most care has been
taken to keep up the objectives of the database design.

CODE DESIGN

The process of code is to facilitate the identification and

retrieve of items of information. The code should be simple and easy to
understandable. The codes were designed in such a way that the
features such as optimum human – oriented use and machine efficiency
are unaffected.

For the code to be designed effectively, the following characteristics

were also considered while designing the code.

• Uniqueness
• Versatility
• Stability
• Simplicity
• Consciousness

The code should be adequate for present and anticipated data

processing for machine and human use. Care was taken to minimize the
clerical effort and computer time required to continue operation.

PROCESS DESIGN

The process can be conceptualized in such a way to keep the

methodology of main module process along with some auxiliary task,
which will run concurrently with the main program.

The top-down approach is maintained so as to keep track of

the process, which satisfies the maintenance reliability testing
requirements. The concurrency of the data is checked during data entry,
by means of validation check for data in each field.
 IMPLEMENTATION

Introduction

System implementation is the stage when the user has thoroughly

tested the system and approves all the features provided by the system.
The various tests are performed and the system is approved only after
all the requirements are met and the user is satisfied.

The new system may be totally new, replacing an existing

manual or automated system, or it may be a major modification to an
existing system. In either case, proper implementation is essential to
provide a reliable system to meet organizational requirements.
Successful implementation may not guarantee improvement in the
organization using the new system (that is a design question), but
improper will prevent it.

Implementation is the process of having systems personnel check out

and put new equipment into use, train users, install the new application
and construct any files of data needed to use it. This phase is less
creative than system design. Depending on the size of the organization
that will be involved in using the application and the risk involved in its
use, systems developers may choose to test the operation in only one
area of the firm with only one or two persons. Sometimes, they will run
both old and new system in parallel way to com-pare the results. In still
other situations, system developers stop using the old system one day
and start using the new one the next.
 The implementation of the web based or lan based networked
project has some extra steps at the time of implementation. We need to
configure the system according the requirement of the software.

For the project we need to install and configure Weblogic server

8.1 , database server, and the deployment directory for the project.
Aspects of Implementation

The two aspects of implementation are:

• Training Personnel
• Conversion Procedures

TRAINING

Even w el l d esi g ne d and t ec hni c al l y e l e g ant sy st e ms c an

suc c eed o r fai l b ec ause o f t he w ay t he y ar e use d . T he r e for e
the q ual i ty o f the tr ai ni ng r e c ei ve d b y t he p e r so nne l i nvo l ve d
w i th the sy stem i n var i o us w ay s he l p s o r hi nd e r s, and may
even p r event, the suc c e ssful i mpl e me nt at i o n of an
i nfo r mati o n sy stem.
Si nc e, Human Re so urc e R e cr ui t me nt P ro c e ss is web-
b ased and user fr i endl y , no t muc h e ffo r t w as r e q ui r e d i n
tr ai ni ng pr o c ess.

CONVERSION:

C o nver sio n is the p ro c e ss of c hang i ng fro m t he o ld

sy stem to the new sy st e m. T he r e ar e t wo me t ho d s of
hand l i ng sy stems co nve r si o n:
• Parallel Run
• Immediate cut-off
Parallel Run

In thi s ap p r o ac h, t he ol d sy st e m and t he ne w sy st e m ar e
used si mul taneo usl y fo r so me p er io d o f t i me so t hat t he
p er fo r manc e of the ne w sy st e m c an be mo ni t or e d and
c o mp ar ed wi th that o f t he o ld sy st e m. Al so i n c ase o f fai l ur e
o f the new sy stem, the use r c an fal l b ac k o n t he ol d sy st e m.
T he ri sk o f thi s ap p ro ac h i s t hat t he use r may ne ve r w ant to
shi ft to new sy stem.

9.2.2.1 Immediate cut-off

In t hi s me t ho d , t he use o f t he ol d sy st e m
c eases as soo n as the ne w sy st e m i s i mp l e me nt e d and bo ug ht
i n to p al ac e. T he ol d sy st e m b e c o me s re d und ant fro m t he d ay
o f i mp l ementati o n o f t he ne w sy st e m. T he r e is t he hi g h r i sk
i nvo l ved i n thi s ap p r o ac h i f t he ne w sy st e m is no t t e st e d
r ig o ro usl y . T hi s i s b ec ause o f t he fac t t hat i f t he ne w sy st e m
fai l s, then ther e w il l no t b e any t hi ng to fal l b ac k up o n. T he
ad va ntag e o f thi s ap p ro ac h i s t hat b o t h t he sy st e ms ne e d no t
b e used si mul taneo usl y .

Implementation Tools
The project was implemented using ASP.NET server pages , HTML ,
ASP.NET beans.The implementation work was carried out in Windows
XP/2000 server platform.

1) C#.Net and Asp.Net

2) SqlServer 2000
 Coding

This means program construction with procedural specifications has

finished and the coding for the program begins:

• Once the design phase was over,coding commenced

• Coding is natural consequence of design.

• Coding step translate a detailed design representation of

software into a programming languae realization.

• Main emphasis while coding was on style so that the end result
was an optimized code.

The following points were kept into cosideration while coding:

Coding Style

The structured programming method was used in all the modules the
project.It incorporated the following features

• The code has been written so that the definition and

implementation of each function is contained in one file.
• A group of related function was clubbed together in one file to
include it when needed and save us from the labour of writing it
again and again.

Naming Convention:-
 • As the project size grows,so does the com[plexity of recognizing
the purpose of the variables.Thus the variables were given
meaningful names,whihch would hellp in understanding the
context and the purposse of the variable.
• The function names are also given meaningful names that can be
easily understood by the user.

Indentation

Judicious use of indentation can make the task of reading and

understanding a program much simpler.Indentation is an essential part
of a goog program.If code id intended without thought itv will seriously
affect the readability of the program.

• The higher-level statements like he definition of the

variables,constants and the function are intended,with each
nested block intended,stating their purpose in the code.

• Blank line is also left between each function definition to make the
code look neat.

• Indentation for each source file stating he purpose of the file is

also done.

MAINTENANCE

Maintenance or enhancement can be classified as: -

• Corrective
• Adaptive
• Perfective.
 C or r ec ti ve mai nt e n anc e me ans r e p ai ri ng p ro c e ssi ng or
p er fo r manc e fai l ur es or mak i ng c hang e s b e c ause of
p r evi o usly unc or r ec ted pr o bl e ms or fal se assump t i o ns.

Ad ap ti ve mai nten anc e me an s c hang i ng t he p r og r am

func ti o n.

P er fec ti ve mai nt e n anc e me ans e nhanc i ng t he

p er fo r manc e or mo di fy i ng t he p ro g r am( s) t o r e sp o nd to t he
user ’ s ad d i tio nal o r c hang i ng ne e d s.

Mai ntena nc e i s ac t ual l y t he i mpl e me nt at i o n o f t he po st

i mp l ementati o n r evi ew pl an.

As i mp o r tant as it i s, many p ro g r amme r s and anal y st s

ar e rel uc tant to p er fo r m or id e nt i fy t he mse l ve s with t he
mai nten anc e effo r t. T he r e ar e p sy c ho l og i c al , p er so nal i t y and
p ro fessi o nal reaso ns for t hi s. I n any c ase , a fir st c l ass e ffo r t
must b e mad e to ensur e t hat so ft w ar e c hang e s ar e mad e

p ro p er ly and i n t i me t o k e e p t he sy st e m i n t une w i t h
user sp ec i fi c atio ns.

Mai nte na nc e i s co st l y. One w ay t o r e d uc e

mai nten anc e co sts i s t hro ug h mai nt e n anc e manag e me nt and
so ftw ar e mo di fi c ati o n aud i t s. So ft w ar e mo di fi c at i o n c o nsi st s
o f pr o g r am r ewr i tes sy st e m l e ve l up d at e s, and r e - aud i t s o f
l ow r ank i ng p r og r ams to ve r i fy and co rr e c t t he so ft sp o t s.

T he outc o me sho ul d b e mo r e r e li ab l e so ft w ar e , a
r ed uc ed mai ntenanc e b ac k lo g , and hi g he r sat i sf ac t i o n and
mo r al e amo ng the mai nt e na nc e st aff.
 In P RO J EC T , c ar e has b e e n t ak e n to w ar d s
mai nten anc e; Loo p Ho l e s c an b e er ad i c at e d fr o m t he sy st e m
fr o m ti me to ti me ac co r di ng to c hang i ng r e q uir e me nt s wi t h
l esser co st.

EVALUATION
The evaluation phase ranks vendor proposals and determines the one
best suited, Evaluation of the system is performed to identify its
strengths and weaknesses. The actual evaluation can occur along any of
the following dimensions:

 Operational Evaluation: Assessment of the manner in which the

system functions, including case of use, response time, overall
reliability and level of utilization.

 Organizational Impact: Identification and measurement of

benefits to the organization in such areas as financial concerns,
operational efficiency and competitive impact.

 User Manager Assessment Evaluation of the attitudes of senior

and user manager within the organization, as well as end-users.

 Development Performance: Evaluation of the development process

in accordance with such yardsticks as overall development time
and effort, conformance to budgets and standards and other
project management criteria.
OUTPUT
This is the Home Page
This page is for Registration in the cellular
This page is about the careers information in the telecom
This Page is about the site objective:
This page display the product which are available
This display the store available int the area
Database Design

CARRERS Form
DATABASE

Id Int Auto Generate

User_Name Varchar
Password Varchar
Confirm_Password Varchar
Title Varchar
First_Name Varchar
Last_Name Varchar
Age Varchar
Address Varchar
City Varchar
State Varchar
Email Varchar
Mobile_Number Varchar
Phone_Number Varchar
Current_desgination Varchar
Current_CTC Varchar
Year_Of_Experience int
Current_Employment Varchar
create_Date datetime Auto Generate

Product Form Database

Id int Auto Generate

Product varchar
Brand varchar
Model varchar
Images varchar
 Registration Form
Database

Id int Auto Generate

Title Varchar
Name Varchar
Gender Varchar
Age int
Date_Of_Birth Varchar
Occupation Varchar
Martial_Status Varchar
Address Varchar
City Varchar
State Varchar
Mobile_Number Varchar
Phone_Number Varchar
Email Varchar
Create_Date DateTime Auto Generate
LIMITATION
LIMITATIONS: -
 This project does not Edit the date of connection or store the
date of transfer in case of connection transfer.
 System date for the project is like as backbone for the
human, i.e. proposed system is depends on system date so it
must be correct.
 Cannot be connected to the Internet.

 There are some inherent problems like time, finance etc. to

elaborate further study.

BIBLIOGRAPHY
Bibliography

 ASP.NET on the Edge

Author: Rick Leinecker.

 Programming Microsoft Visual c#.Net

(Microsoft Press)
Author: Francesco Balena.

 Introducing .NET
WROX publications.

 Upgrading Microsoft Visual Basic .NET

(Microsoft Press)
Authors: Ed Robinson, Ian Oliver, Michael Bond.

 Learn to Program with Visual Basic .NET

(Osborne McGrew-Hill)
Author: John Smiley.

Websites:

 http://www.vbnetdesign.com
 http://www.google.com
 http://www.microsoft.com/vb.net
 http://www.databasejournal.com
 GLOSSARY

Analysis Breaking a problem into successively manageable parts for

individual study.

Attribute A data item that characterizes an object.

Cost/Benefit Analysis The purpose of the comparing projected savings and benefits to

projected costs to decide whether a system

changed is justified.

Database A store of integrated data capable of being directly addressed

for multiple users; it is organized so that Various files can be

accessed through a single reference Based on the relationship

among records in the file rather then the physical location.

DBMS The software that determines how data must be

structured to produce the user’s view; and maintain and update

the system.

Data flow Movement of data in a system from a point of origin to a

Specific destinations- indicated by a line and arrow.

Data security Protection of data from loss, disclosure, modification or

destruction.

Data structure A logically related set of data that can be decomposed into

lower level data elements; a group of data elements handled

as a unit.

Design Process of developing the technical and operational

specifications of a candidate system for implementation.

Feasibility Study A procedure that identifies, describes and evaluate candidate

systems and select the best system for implementation.

File Collection of related records organized for a particular purpose also called a dataset.

Flow Chart A graphic picture of the logical steps and sequence involved in

a procedure or a program.

Form A physical carrier of data of information.

Gantt Chart A static system model used for scheduling; portrays output

performance against time.

Implementation In system development – a phase that focuses on user training,

site preparation and file conversion for installing a candidate

system.

Maintenance Restoring to its original condition.

Normalization A process of replacing a given file with its logical equivalent;

the object is to derive simple files with no redundant elements.

Operating System In database – machine based software that facilitates the

availability of information or reports through the DBMS.

Password Identity authenticator a key that allow access to a program

system or procedure.

PERT (Project Evaluation & Review Technique) A flow system model used to manipulate

various values as a basis for determining the critical path to

interpret these relationship and to relate them back to the real

world as a control technique.

Record A collection of aggregates or related items of data treated as a

unit.
Source Code A Procedure or format that allow enhancements on a software

package.

System A regular or orderly arrangements of components or parts in a

connected and interrelated series or whole; a group of

components necessary to some operation.

System Design Detailed concentration on the technical and other specifications

that will make the new system operational.

SDLC (System Development Life Cycle) A structured sequence of phases for implementing

an information system

System Testing. Testing the whole system by the user after major programs and

subsystems have been tested.

Unit Testing Testing changes made in an existing or new programs