Project Report on Cellular Project

8/6/2019 Project Report on Cellular Project

1/88

Project ReportOn

Cellucom Submitted in partial fulfillment of the requirement for the

Award of the degree of

Master of Computer Application2006-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


2/88

Project ReportOn

Cellucom Submitted in partial fulfillment of the requirement for the

Award of the degree of

Master of Computer Application2006-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 ________________________________________________


3/88

Rajarshi School of Management & Technology(Udai Pratap Autonomous College Campus Varanasi)

Varanasi-221002

website: www.rsmt.ac.inPh: +91-542-2281062

Fax: +91542-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 theDegree Project titled CELLUCOM in Arrowline computer Institute of sixmonths 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 GuptaReader MCA R.S.M.T(VNS) Reader MCA R.S.M.T(VNS)

Date: Date:


4/88

CERTIFICATE

This is to certify that the following student with the nameMr. Ravi Kumar Maurya bearing the H.T.No:0510814032 from RajarshiSchool of Management &Technology, Varanasi has successfully completedthe project titled Cellucom as part of the courseCurriculum in our organization.

He has done the project using ASP.NET 2.0 with C# andSQL Server-2005 during the period 15-Jan-2009 to 22-Jun-2009, under theGuidance 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 issincere, 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: 15 th Jan 2009

Varanasi.


5/88

Declaration

I here by solemnly declare that this project report entitled Cellucomis bonafied work done by me during the Final year, MCA, and submitted tothe 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


6/88

Acknowledgement

In my first major attempt to put my feet firmly on the world of practicalcomputing, I take this opportunity to express my gratitude to all of them whohave 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 guidancethroughout 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 constantencouragement during my entire work.

To one and all, I owe acknowledgements, who have directly or indirectlyaided me in completing project.

Ravi Kumar Maurya


7/88

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


8/88

INTRODUCTION


9/88

RSMT, Varanasi deputed a sixth months Industrial Project Training as a pointof curriculum of MCA, Computer. This college is affiliated to U.P. TechnicalUniversity, Lucknow. The student of M.C.A. are recorded to attached withsome industries in the sixth semester, where they are to be assigned some

project . The students are supposed to complete these projects and submit thedetailed 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-daysvery useful to Mobile, Laptop,Palmtop, are also have many brand and stylesdeign 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 thewebsite 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 alsoclose the Cell session, so that all the users will be disconnected.

2. Administrative Client: Admin can also involve in Cellucom as a clientfrom 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 howCellucom 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 doesnt know about a new thing in the market thenthey are delayed for that particular resource which he doesnt know get thedetailed information about that resource through this Site they get thedetailed information for the resource.
http://www.cellucom.com/http://www.cellucom.com/


10/88

SOFTWARE

REQUIRMENTS

SPECIFICATION


11/88

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. Thesoftware project is initiated by the clients 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.


12/88

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 systemrequires.

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.


13/88

Hardware & Software Requirements

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

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

RDBMSRDBMS :: Sql Server 2000,Sql Server2005Sql Server 2000,Sql Server2005

OPERATING SYSTEM : Windows NT or 2000 or LaterOPERATING SYSTEM : Windows NT or 2000 or Later

BACKUP MEDIA : Hard disk, Floppy, CDBACKUP MEDIA : Hard disk, Floppy, CD

MONITOR MONITOR : VGA: VGA

Windows 2000XP/Windows 2000 NT Operating System

The main responsibility of an operating system is to manage computers

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


14/88

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 youre web.

IntegrationWindows 98 Explorer and Internet Explorer integrate local and Web-

based resources in a single viewer computers 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 systems 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 others bugs.

To a l a rg e e x t e n t , m u l t i t a s k i n g o p e r a t i n g s y s t e m r e l a y

on system hardware to implement these capabi l i t ies . Another

i m po r ta n t a s pe c t o f m u lt i ta s ki n g i s p r oc e ss s c he d ul i ng . A s

p ro ce ss a r e c ap ab le o f e xe cu ti ng o nl y a s in gl e s tr e am o f

ins t ruct ion at any given, mult i tasking would obviously not be

p o ss i bl e w i th o ut t h e t e ch n iq u e o f t h e c o nt e xt s w it c hi n g. A

c o nt ex t s wi tc h, t r ig ge re d b y a s pe ci fi c e ve nt ( su ch a s a n

i nt er ru pt f ro m a t im er c ir cui t o r a c all by t he r un ni ng

a pp li ca ti on t o a s pe ci fi c f un ct io n) , e ss en ti al ly c o ns is t o f

s av in g t he p ro ce ss or c on te x t ( i ns tr u ct io n p oi nt er , s ta ck


15/88

p oi nt er , r eg is te r c on te nt s) o f o ne r un ni ng p ro gr am a nd

loading that of another.

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 caninterrupt 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 applications flow of execution

can be interrupted at any point, not only at predefined spots. This

realizes the complexity of the system.


16/88

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.


17/88

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.


18/88

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 requirementsdocument, 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 organizations

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


19/88

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.


20/88

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 informationmanagement. 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


21/88

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 theproject 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 agencys 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


22/88

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


23/88

1.0 SYSTEM ANALYSIS

System Requirements

Software Requirements

Review & Validation

Review & Validation

Review & Validation

Review & Validation

Review & Val idation

Review & Validation

Review & Validation

Preliminary Design

Detailed Design

Detailed Functional Specifications

User Requirement Specifications

Code and Debugging

Testing

Maintenance

Testing

Maintenance

Software Requirements

Global Implementation Specifications &

Detailed Implementation Specifications

Coding & Debugging

Process Engineering of Application Software (Software Development Lifecycle)


24/88

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

todays organization. Survival on manual system is difficult so, thats 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.

Success of a system depends lar gely on how accurate ly a

p ro bl em i s d ef in ed , t ho ro ug hl y i nv es ti ga te d a nd p ro pe rl y

c a r r i e d o u t t o t h e c h o i c e o f s o l u t i o n . A n a l y s i s i s a p h a s e i n

w h ic h t h e r e qu i re m en t s f o r t h e n e w s y st e m a r e i d en t if i ed .

Sys tem ana lysi s i s a de ta i l ed s tudy of the var ious opera t ions

p er f or me d b y a s ys te m a nd t he ir r el at io ns hi p w it hi n a nd

outs ide of the system. The quest ion is : what must be done to

s o lv e t he p ro bl em ? O ne a sp ec t o f a na ly si s i s d ef in in g t he

boundar ies o f the sys tem and de te rmin ing whether o r no t a

c an di da te s ys te m s ho ul d c on si de r o th er r el at ed s y st em .

D ur i ng a na ly si s d at a a r e c ol le ct ed o n t he a va il ab le f il es ,

d ec is io n p oi nt s a nd t ra ns ac ti on s h an dl ed b y t he p ar en t

sys tem. Data f low d iagram, in te rv iews , ons i t e observa t ions ,

ques t ionna i res a re used as a log ica l sys tem model and too l s

to perform the analysis .


25/88

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 order to reduce the t ime, there is a need for

c o mp u te r iz e d s y st e m t h at c a ns r e t ri e ve d a ta , i n se r t d a ta ,

upda te ex i s t ing da ta o r de le te ex i s t ing da ta . These modules

ar e developed wit the a im of r educing t ime, reducing

m a np o we r, r e du c in g c o st s o t h at t h e r e c o r ds c a n b e e a si l y

maintained. The volume of work and complex i ty are

increasing year by year. Th is sys tem reduces complex ity and

workload

.

1.2 Preliminary Investigation:

A r e qu e st t o t a ke a s si s ta n ce f r om i n fo r m at i on s y st e m

can be made fo r many reasons , bu t in each case some one in

t h e o rga n iz a t io n i n it i at e t h e r e qu e st . W h en t h e r e qu e st i s

made , the f i r s t sys tem ac t iv i ty the p re l iminary inves t iga t ion

begins . This act ivi ty has three par ts :

Request clarification

Feasible Study

Request approval


26/88

Many requests f rom employees and users in the

o rga n iz a t io n a r e n o t c l ea r ly d e fi n ed . T h er e f or e , i t b e co m es

n ec es sa ry t ha t p ro je ct r eq ue st m us t be ex am ine d a nd

clar i f ied proper ly before consider ing systems invest igat ion.

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


27/88

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, successfulenvironments 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


28/88

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

individuals 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


29/88

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 systems 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


30/88

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.


31/88

1

OutputDesign

InputDesign

FileDesign

ProcessingDesign

DetailedSystem

Documentation

TestPrograms

Design

submitted tomanagementfor approval

Designaccepted

2

Abandon project

CostJustification

andCandidate

design

From Analysis

Yes

STEPS IN SYSTEM DESIGN


32/88

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 authors last name, by

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


33/88

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.


34/88

. 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


35/88

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:

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.

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:



36/88

External Entity

A rectangle represents an external entity such as a librarian

,a library member.

OutPut Symbol This box represented data productionduring human computer interaction





37/88

Information Flow of Data for Testing

Testing

Debug

Reliability

Model

Evaluation

SoftwareConfiguration

TestConfigurat ion

ExpectedResults

Correct ion

Error RateData

Predicted Rel iabi l i ty

Information Flow of Data Testing


38/88

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 neednot 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


39/88

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 dont 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


40/88


41/88

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


42/88

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


43/88


44/88

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 dont 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 doesnt 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


45/88

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.


46/88

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.


47/88

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 servers 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


48/88

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 issecurity 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


49/88

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 ManagementVisual Basic allows we to manage databases while directly connected to them atdesign time. Depending on the feature of our database and our accessprivileges, we can use Visual Basic tools to add, remove, or modify.

DatabasesTables or ColumnsViews and synonymsRelation between TablesIndexesConstraints and triggersStored procedures, functions, and packagesQueries 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 aWeb Application. Therefore to manage databases in Visual Basic, we create adatabase 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 objectsthat we can currently Work with. From the Data View window, we can editobjects such as tables, views, stored procedures, and triggers.

Data View window showing available database objects


50/88

Database Designer: A tool that displays our Microsoft SQL server database asa database diagram, which we can edit to add or modify table and columndefinitions, 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 allowswe 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 Designerto construct SQL statements.

Trigger Editor: A window for creating triggers

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

Overview of the .NET Framework

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

To provide a consistent object-oriented programming environment whetherobject code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.

To provide a code-execution environment that minimizes software deploymentand 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 performanceproblems 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.


51/88

To build all communication on industry standards to ensure that code based onthe .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime andthe .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 atexecution time, providing core services such as memory management, threadmanagement, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of codemanagement is a fundamental principle of the runtime. Code that targets the runtime isknown as managed code, while code that does not target the runtime is known asunmanaged 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 todevelop applications ranging from traditional command-line or graphical user interface(GUI) applications to applications based on the latest innovations provided byASP.NET, such as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the commonlanguage runtime into their processes and initiate the execution of managed code,thereby creating a software environment that can exploit both managed andunmanaged 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-sideenvironment for managed code. ASP.NET works directly with the runtime to enableWeb 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 (inthe form of a MIME type extension). Using Internet Explorer to host the runtimeenables you to embed managed components or Windows Forms controls in HTMLdocuments. Hosting the runtime in this way makes managed mobile code (similar toMicrosoft ActiveX controls) possible, but with significant improvements that onlymanaged code can offer, such as semi-trusted execution and secure isolated file storage.

The following illustration shows the relationship of the common language runtime andthe 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 .NETFramework 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 areintrinsic to the managed code that runs on the common language runtime.


52/88

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 mightor might not be able to perform file-access operations, registry-access operations, orother 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 anexecutable 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 exceptionallyfeature 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 thatall managed code is self-describing. The various Microsoft and third-party languagecompilers generate managed code that conforms to the CTS. This means that managedcode can consume other managed types and instances, while strictly enforcing typefidelity and type safety.

In addition, the managed environment of the runtime eliminates many commonsoftware issues. For example, the runtime automatically handles object layout andmanages references to objects, releasing them when they are no longer being used. Thisautomatic memory management resolves the two most common application errors,memory leaks and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers canwrite applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by otherdevelopers. Any compiler vendor who chooses to target the runtime can do so.Language compilers that target the .NET Framework make the features of the .NETFramework available to existing code written in that language, greatly easing themigration 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 enablesdevelopers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common languageruntime 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 thenative machine language of the system on which it is executing. Meanwhile, the memorymanager removes the possibilities of fragmented memory and increases memorylocality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, suchas Microsoft SQL Server and Internet Information Services (IIS). Thisinfrastructure enables you to use managed code to write your business logic, while stillenjoying the superior performance of the industry's best enterprise servers that supportruntime hosting.


53/88

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integratewith the common language runtime. The class library is object oriented, providing

types from which your own managed code can derive functionality. This not only makesthe .NET Framework types easy to use, but also reduces the time associated with learningnew features of the .NET Framework. In addition, third-party components can integrateseamlessly 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 thatvastly simplify Windows GUI development. If you write an ASP.NET Web Formapplication, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-basedprogramming. These are the types of applications that display windows or forms on thedesktop, enabling a user to perform a task. Client applications include applicationssuch as word processors and spreadsheets, as well as custom business applications suchas data-entry tools, reporting tools, and so on. Client applications usually employwindows, menus, buttons, and other GUI elements, and they likely access localresources 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 custommanaged code to control the behavior of the server. This model provides you with allthe features of the common language runtime and class library while gaining theperformance and scalability of the host server.


54/88

The following illustration shows a basic network schema with managed code running indifferent server environments. Servers such as IIS and SQL Server can performstandard 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 .NETFramework to target Web-based applications. However, ASP.NET is more than just aruntime host; it is a complete architecture for developing Web sites and Internet-distributed objects using managed code. Both Web Forms and XML Web services useIIS and ASP.NET as the publishing mechanism for applications, and both have acollection of supporting classes in the .NET Framework.


55/88

INTRODUCTION OF Sql Server 2000

Introduction to Oracle and Its Tools:The SQL Server product is primarily divided into:

SQL Server Server ToolsSQL Server Client Tools

SQL Server Server:

Microsoft the No. one company in the software that produces the mostwidely used, front end and Server based Multi user RDBMS. The SQLServer is a program installed on the Servers hard disk driver. This programmust be loaded in RAM so that it can process user requests.

The SQL Server Server product is either called SQL Server ProfessionalOr 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 servers memory, users wouldhave to log into the engine to get work done. Microsoft has several client-basedtools that facilitate this. The client tool most commonly used for CommercialApplication Development is Visual basic.


56/88

What is SQL Used for:

Using SQL one can create and maintain data manipulation objects suchas table, views, sequence etc. These data manipulation objects will becreated 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 usedextensively in commercial applications.

DML, DCL, DDL:

In addition to the creation of data manipulation objects, the actualmanipulation 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 withinthese objects are called DML's or Data Manipulation Language. The SQLsentences, which are used to control the behavior of these objects, are calledDCL's or Data Control Language.

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

The Data type that a Cell can hold:

Data Typ e Description

CHAR(size) : This data type is used to store character stringsvalues of fixed length. The size in bracketsdetermines the number of characters the cellcan hold. The maximum number of charactersthis data type can hold is 255 characters.

VARCHAR (size) /VARCHAR2 (size)

: This data type is used to store variable lengthalphanumeric data. The maximum this data typecan hold is 2000 character .

NUMBER (P,S) : The NUMBER data type is used to store numbers(fixed or floating point). Numbers of virtuallyany magnitude maybe stored up to 38 digits of


57/88

precision .

DATE : This data type is used to represent data andtime. The standard format is DD-MON-YY as in24-JAN-02. To enter dates other than thestandard format, use the appropriate functions.Date Time stores date in the 24-hour format.

LONG : This data type is used to store variable lengthcharacter strings containing up to 2GB. LONGdata can be store arrays of binary data in ASCIIformat.


58/88

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

users 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.


59/88

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 users 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 systemunnecessary 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.


60/88

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 intoconsideration 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.


61/88

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.,


62/88

Input Design:

The input design is the link that ties the information system into the

users 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)


63/88


64/88

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


65/88

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 characteristicswere 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.


66/88

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 theorganization 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.


67/88

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 wel l des igned and technica l ly e legan t sys tems can

succeed or fa i l because o f the way they a re used . There fore

the qual i ty of the t ra ining received by the personnel involved

w i t h t h e s y s t e m i n v a r i o u s w a y s h e l p s o r h i n d e r s , a n d m a y

even prevent , the successful implementat ion of an

informat ion system.

S in ce , H um an R es ou rc e R ec ru it me nt P ro ce ss i s w eb -

b as ed a nd u se r f ri en dl y, n ot m uc h e ff or t w as r eq ui re d i n

tra ining process .

CONVERSION:

C on ve rs io n i s t he p ro ce ss o f c ha ng in g f ro m t he o ld

sy stem to the new system. Ther e are two methods o f

handl ing systems convers ion:

Parallel Run

Immediate cut-off


68/88

Parallel Run

In this approach, the old system and the new system are

u se d s im ul ta ne ou sl y f or s om e p er io d o f t im e s o t ha t t he

p er fo rma nc e o f t he n ew s ys te m c an b e mo ni tor ed a nd

compared wi th tha t o f the o ld sys tem. Also in case o f fa i lu re

of the new sys tem, the use r can fa l l back on the o ld sys tem.

The r i sk o f th i s approach i s tha t the use r may never want to

shif t to new system.

9.2.2.1 Immediate cut-off

In th i s method , the use o f the o ld sys tem

ceases as soon as the new system is implemented and bought

in to palace. The old system becomes redundant f rom the day

of implementa t ion o f the new sys tem. There i s the h igh r i sk

i nv ol ve d i n t hi s a pp ro ac h i f t he n ew s ys te m i s n ot t es te d

r igorous ly. Th is i s because o f the fac t tha t i f the new sys tem

f a il s , t h e n t h er e w i ll n o t b e a n yt h in g t o f a l l b a ck u p on . T h eadvantage of this approach is that both the systems need not

be used s imultaneously.

Implementation Tools

The project was implemented using ASP.NET server pages , HTML ,

ASP.NET beans.The implementation work was carried out in WindowsXP/2000 server platform.

1) C#.Net and Asp.Net

2) SqlServer 2000


69/88

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:-


70/88

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 meaningf

Project Report on Cellular Project

Documents