block office project

8/12/2019 Block Office Project

1/101

Introduction

We are proposing an online software application which will be used for the

efficient management of projects as well as monitoring of the block offices works.

IBMS will consist of various modules for the Patals & Departments of Block

Office. Block office employees (General Users) will put the data in their software

modules as per the rights given to them by the System Administrator (System

Administrator will be a super user, who can create users and provides the rights of

software as per their responsibilities). General users can also check the entered

data in the form of various reports and they can take the printout of the reports

whenever required. ADOs / BDOs can monitor the progress of projects with the

help of various MIS reports and also they can approve or reject the projects from

their logins. An integrated approach of the software will provide the facility to

monitor the block office work from the CDO / DM logins. They can view the

various MIS reports of any block office. IBMS will be connected to the Integrated

Voice Response System (IVRS) & SMS gateway to connect the field level officers

and gram pradhan to get the required information related to the various projects.IBMS will be online software which will be available in English/Hindi as

requirement.

1


2/101

Problem Definition

The Existing System is Offline System ,In Block Office the all Daak Letters Entry

entered by manually,and information of apply candidate for make the new Rashan

Card data is entered in papers and Registers.Not any special type technology used

in existing system.

The many No. of letters are came in block office and many No.of candidate apply

for Rashan Card.The problem is arrise that to maintain the records is very critical

because some times papers and form can be lost or damaged so data or information

will be lost.

Some time the Bdo,Dm want to see the overview of all Information about coming

letters and send letters ,how many candidate applied for make mew Rashan Card if

The papers and Register or file has been damaged or lost is possible.

In Existing System Data keep managed and Secure data is lengthy and risky.

2


3/101

System Analysis & Feasibility Study

Study of existing systems/ Technologies

The Existing System is Offline System ,In Block Office the all Daak Letters Entry

entered by manually,and information of apply candidate for make the new Rashan

Card data is entered in papers and Registers.Not any special type technology used

in existing system.

The many No. of letters are came in block office and many No.of candidate apply

for Rashan Card.The problem is arrise that to maintain the records is very critical

because some times papers and form can be lost or damaged so data or information

will be lost.

Some time the Bdo,Dm want to see the overview of all Information about coming

letters and send letters ,how many candidate applied for make mew Rashan Card if

The papers and Register or file has been damaged or lost is possible.

In Existing System Data keep managed and Secure data is lengthy and risky.

Comparison of existing systems with proposed system

The Proposed System is online System/Application which store the data in

database and tables.This System is very fast from existing system and the maintain

and secure data is very easy.In praposed System the papers and file register have

not any type role.The proposed system is used by not all employee of Block Office

Only admin have Rights to use this System.

3


4/101

In Proposed System the report show all coming and receive letters information on

one click and also view the all applied candidate for Rashan Card by one click.

ADVANTAGE OF PROPOSED SYSTEM: Very fast and accurate.No need of any extra manual efforts. Doesnt require any hardware devices. At least very easy to find or view the Information of

individualy.

Any Type papers or file are not used in this system.

Feasibility Study

Once the problem is clearly understood, the next step is to conduct feasibility

study, which is high-level capsule version of the entered systems and design

process. The objectives is to determine whether or not the proposed system is

feasible. The three tests of feasibility have been carried out.

Operational Feasibility Technical Feasibility Economical Feasibility

4


5/101

Operational Feasibility:-It is a standard that ensures interoperability. Without stifling

competition and innovations among users, to the benefit of the public

both in terms of cost and services quality. The proposed system is

acceptable to employees. So the proposed system is operationally

feasible.

Technical FeasibilityIn Technical Feasibility study, one has to test whether the proposed

system can be developed using existing technology or not. It isplanned to implement the proposed system using ASP.NET

technology. It is evident that the necessary hardware and software are

for development and implementation of the proposed system. Hence,

the solution is technically feasible.

Economical Feasibility:-As part of this, the costs and benefits associated with the proposed

system compared and the project is economically feasible only if

tangible or intangible benefits outweigh costs. The system

development costs will be significant. So the proposed system is

economically feasible.

5


6/101

Scope of the Proposed System

The objective of this application is to present the secure graphical user

interface much friendly to the authorized user only, performing all the working of

above mentioned procedure efficiently. It is aimed at making department affairs

getting rid of all the bottlenecks that are there in the manual system and enabling

them to focus on the core activities of the administration, thus helping them

strengthen the overall quality standards and at the same time make the job of

preparing and maintaining the job of all records pleasurable and interesting job.

The project has covered almost all the requirements. Further requirements

and improvements can easily be done since the coding is mainly structured or

modular in nature. Changing the existing modules or adding new modules can

append improvements. Further enhancements can be made to the application, so

that the web site functions very attractive and useful manner than the present one.

6


7/101

System Requirements

a. Hardware Requirements

PROCESSOR : 568 MHz Pentium Processor

RAM : 64 MB RAM

HARD DISK : 80 GB HDD

b. Software Requirements

i. Front End

OPERATING SYSTEM : Windows 7

ENVIRONMENT : Visual Studio .NET 2010

.NET FRAMEWORK : Version 3.5

LANGUAGE : C#.NET

WEB TECHNOLOGY : ASP.NET

ii. Back End

BACKEND : SQL SERVER 2010R2

7


8/101

System Logical Design

Software requirement specification

Software Requirements Specification (SRS) is the starting point of the software

development activity. Little importance was given to this phases in the early days

of software development. The emphasis was first on coding and then shifted to

design.

As systems grew more complex, it become evident that the goal of the entire

system cannot be easily comprehended. Hence need for the requirements analysisphase 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 imitated by the client 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 tacking to these people and

understanding their needs. In situations where the software is to automated a

currently manuals 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 output)

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.

8


9/101

System Environment

9


10/101

System Overview

Acronyms and Abbreviations

Following is a list of the acronyms and abbreviations used in the due course of the

document:-

10


11/101

Acronyms/Abbreviations Meaning

IBMS Integrated Block Management System

BDO Block Development Office

CCL Cash credit limit

SHG Self-Help Groups

BLBC block level bankers committee

MSR Minimum Skill Requirement

MPR Monthly Progress Report

DRDA District Rural Development Agencies

11


12/101

Data Flow Diagram

The data flow diagram is one of the most improvement tools used by the system

analyst DeMacro (1978) NadGandSarson (1979) popularized the use if the data

flow diagram as modeling tools through their structured system analysis

methodologies.

A data flow diagram should be the first tool used by system analyst to model

system components. These components are the system processes; the data used by

this processes and external entities that interact with the system and the

information flows in the system.

There are four kinds of system components

ProcessProcess show what system does. Each process has one or more data inputs

and produce one or more data output, Circles in a data flow diagram represent

process. Each process has unique name and number. This name and number

appear inside the circle that represents the processes in a data flow diagram.

This process is represented as circle

12


13/101

Data Stores

File or data store is depositary of data. They contain data that is retained in the

system. Processes can enter the data into a data store or retrieve data from the data

store. Each data store is represented by thin line in the data flow diagram and each

data store has a unique name.

The data store is represented in form of a line

External EntitiesExternal entities are outside the system but they either supply input data into the

system or use the system output, they are entities which the designer has no

control. Square or rectangle may represent external entities that supply data into a

system or sometimes called sources. External entities that use the system data are

sometimes called sinks.

Data Flows Dataflow model the passage of data in the system and are represented

lines joining system components. An arrow indicates the direction of the flow and

the line labeled by the name of the data flow.

13


14/101

Module-Daak

Daak Flow Diagram

ADO/Clerk BDO

CDO/DM

14

Modify

Add

View Reports

Add

Departmrnt

Letter Send Entry

Form

Letter Receive

Entry Form

Approval

Rejection

View

Approval

Rejection

View

Block Master

GramPanchayat

Master

Villege Master


15/101

ModuleRashan Card

Rashan Card Flow Diagram

ADO/Clerk BDO

CDO/DM

15

Modify

Add

View Reports

Add Rashancard

Shop Name Master

Rashan Card Entry

Form

Approval

Rejection

View

Approval

Rejection

View

Block Master

GramPanchayat

Master

Villege Master


16/101

Data Dictionary

Table For Add Department Name

Field Name DataType Size PrimaryKey/ForeignKey

Allow Null

Department_id Int PK

Department_name Nvarchar 100 Checked

Block_id Int Checked

Created_by Varchar 50 Checked

Created_on Datetime Checked

Modify_by Varchar 50 Checked

Modify_on Datetime Checked

16


17/101

Table for Letter send EntryLetter_send_id Int PK


Letter_number Varchar 50 Checked

Letter_sender_office_id Int Checked

Letter_description Nvarchar 300 Checked

Letter_send_date Datetime Checked


Creared_on Datetime Checked



Any_other Nvarchar 300 Checked

Letter_sender_person_id Int Checked

17


18/101

Table For Letter Receive EntryLetter_receive_id Int PK


Letter_send_office_id Int Checked

Letter_number Varchar 100 Checked

Letter_receive_date Datetime Checked

Any_other Nvarchar 300 Checked





Status_type Char 1 Checked

18


19/101

Table For Letter StatusStatus_id Int PK Checked

Status_type Int Checked


Letter_sender_office_id Int Checked

Letter_receive_office_id Int Checked

Status_date Datetime Checked

Remark Nvarchar 300 Checked





Letter_receive_id Int FK Checked

Letter_sender_person_id Int FK Checked

19


20/101

Table for Rashan CardRashancardshop_id Int PK

Rashancardshop_name Nvarchar 100 Checked

Grampanchayat_id Int FK Checked





Rashancardshopregisternumber Varchar 20 Checked

20


21/101

Table For Rashan Card EntryRashancard_id Int PK Checked

Block_id Int FK Checked

Grampanchayat_id Int FK Checked

Villege_id Int FK Checked

Candidate_name Nvarchar 100 Checked

Father_name Nvarchar 100 Checked

Mother_name Nvarchar 100 Checked

Caste Char 1 Checked

Full_address Nvarchar 300 Checked

Pincode Int Checked

Mob_no Varchar 20 Checked


22/101

Unique_id Varchar 20 Checked

Voter_id Varchar 20 Checked

Electricity Nvarchar 300 Checked

Gas agency_name Nvarchar 100 Checked

Consumer_number Varchar 50 Checked

Permanent_address Nvarchar 300 Checked

Living_status Nvarchar 25 Checked

House_status Nvarchar 25 Checked

House_type Nvarchar 25 Checked

Candidate_photo Varchar 50 Checked

Letter_photo Varchar 50 Checked

22


23/101

Table For Rashancard Candidate family MemberFamily_id Int PK Checked

Candtdate_id Int FK Checked

Member_name Nvarchar 100 Checked

Mother_name Nvarchar 100 Checked

Gender Char 1 Checked

Relation Nvarchar 50 Checked

Age Int Checked

Bussiness Nvarchar 100 Checked

Monthly_income Int Checked


24/101

Office_address Nvarchar 100 Checked





24


25/101

Table for Rashancard StatusStatus_id Int PK

Status_type Char 1 Checked

Rashancard_id Int FK Checked

Status_date Datetime Checked

Remark Nvarchar 100 Checked





25


26/101

System Physical Design

Program Design

The programming process is similar in approach and creativity to writing a paper.

In composition, you are writing to express ideas; in programming you are

expressing a computation. Both the programmer and the writer must adhere to the

syntactic rules (grammar) of a particular language. In prose, the fundamental idea-

expressing unit is the sentence; in programming, two unitsstatements and

comments are available.Standing back, composition from technical prose to fiction

should be organized broadly, usually through an outline. The outline should be

expanded as the detail is elaborated, and the whole re-examined and re-organized

when structural or creative flaws arise. Once the outline settles, you begin the

actual composition process, using sentences to weave the fabric your outline

expresses. Clarity in writing occurs when your sentences, both internally and

globally, communicate the outline succinctly and clearly.We stress this approach

here, with the aim of developing a programming style that produces efficient

programs that humans can easily understand.

To a great degree, no matter which language you choose for your composition, the

idea can be expressedwith the same degree of clarity. Some subtleties can be better

expressed in one language thananother, but the fundamental reason for choosing

your language is your audience: People do not knowmany languages, and if you

want to address the American population, you had better choose Englishover

Swahili. Similar situations happen in programming languages, but they are not

nearly so complexor diverse. The number of languages is far fewer, and their

differences minor. FORTRAN is the oldest languageamong those in use today. C

26


27/101

and C++ differ from it somewhat, but there are more similaritiesthan not.

MATLABs language, written in C and FORTRAN, was created much later than

these two, and itsstructure is so similar to the others that it can be easily mastered.

The C++ language is an extension ofthe C language that places its emphasis on

object oriented programming (OOP) methods. FORTRAN addedobject oriented

capabilities with its F90 standard, and additional enhancements for parallel

machineswere issued with F95. The FORTRAN 2000 standard is planned to

contain more user-friendly constructs forpolymorphism and will, thus, enhance its

object-oriented capabilities. This creation of a new languageand its similarity to

more establish ones are this books main points: More computer programming

languageswill be created during your career, but these new languages will probably

not be much differentthan ones you already know. Why should new languages

evolve? In MATLABs case, it was the desire toexpress matrix-like expressions

easily that motivated its creation. The difference between MATLAB andFortran 90

is infinitesimally small compare to the gap between English and Swahili.

An important difference between programming and composition is that inprogramming you are writingfor two audiences: people and computers. As for the

computer audience, what you write is read byinterpreters and compilers specific

to the language you used. They are very rigid about syntactic rules,and perform

exactly the calculations you say. It is like a document you write being read by the

most detailed,picky person you know; every pronoun is questioned, and if the

antecedent is not perfectly clear,then they throw up their hands, rigidly declaring

that the entire document cannot be understood. Yourpicky friend might interpret

the sentence Pick you up at eight to mean that you will literally lift him orher off

27


28/101

the ground at precisely 8 oclock, and then demand to know whether the time is in

the morning orc2001 J.E. Akin 1afternoon and what the date is.

Humans demand even more from programs. This audience consists of two main

groups, whose goals can conflict. The larger of the two groups consists of users.

Users care about how the program presents itself, its user interface, and how

quickly the program runs, how efficient it is. To satisfy this audience, programmers

may use statements that are overly terse because they know how to make the

program more readable by the computers compiler, enabling the compiler to

produce faster, but less human-intelligible program. This approach causes the other

portion of the audience programmers to boo and hiss. The smaller audience, of

which you are also a member, must be able to read the program so that they can

enhance and/or change it. A characteristic of programs, which further distinguishes

it from prose, is that you and others will seek to modify your program in the future.

For example, in the 1960s when the first version of FORTRAN was created, useful

programs by todays standards (such as matrix inversion) were written. Back then,

the user interface possibilities were quite limited, and the use of visual displayswas limited. Thirty years later, you would (conceivably) want to take an old

program, and provide a modern user interface. If the program is structurally sound

(a good outline and organized well) and is well-written, re-using the good

portions is easy accomplished.

The three-audience situation has prompted most languages to support both

computer-oriented and human-oriented prose. The programs meaning isconveyed by statements, and is what the computer interprets. Humans read this

part, which in virtually all languages bears a strong relationship to mathematical

28


29/101

equations, and also read comments. Comments are not read by the computer at all,

but are there to help explain what might be expressed in a complicated way by

programming language syntax. The document or program you write today should

be understandable tomorrow, not only by you, but also by others. Sentences and

paragraphs should make sense after a day or so of gestation. Paragraphs and larger

conceptual units should not make assumptions or leaps that confuse the reader.

Otherwise, the document you write for yourself or others served no purpose. The

same is true with programming; the programs organization should be easy to

follow and the way you write the program, using both statements and comments,

should help you and others understand how the computation proceeds. The

existence of comments permits the writer to directly express the programs outline

in the program to help the reader comprehend the computation.

These similarities highlight the parallels between composition and

programming. Differences becomeevident because programming is, in many ways,

more demanding than prose writing. On one hand, thecomponents and structure of

programming languages are far simpler than the grammar and syntax of anyverbalor written language. When reading a document, you can figure out the misspelled

words, and notbe bothered about every little imprecision in interpreting what is

written. On the other, simple errors, akinto misspelled words or unclear

antecedents, can completely obviate a program, rendering it senseless orcausing it

to go wildly wrong during execution. For example, there is no real dictionary when

it comesto programming. You can define variable names containing virtually any

combination of letters (upperand lower case), underscores, and numbers. A

typographical error in a variables name can thereforelead to unpredictable

program behaviour. Furthermore, computer execution speeds are becoming

29


30/101

fasterand faster, meaning that increasingly complex programs can run very

quickly. For example, the program(actually groups of programs) that runs NASAs

space shuttle might be comparable in size to Hugos LesMiserables, but its

complexity and immediate importance to the user far exceeds that of the novel.

As a consequence, program design must be extremely structured, having the

ultimate intentions ofperforming a specific calculation efficiently with attractive,

understandable, efficient programs. Achievingthese general goals means breaking

the program into components, writing and testing them separately,then merging

them according to the outline. Toward this end, we stress modular programming.

Modulescan be on the scale of chapters or paragraphs, and share many of the same

features. They consist of a sequenceof statements that by themselves express a

meaningful computation. They can be merged to formlarger programs by

specifying what they do and how they interface to other packages of software.

Theanalogy in prose is agreeing on the characters names and what events are to

happen in each paragraphso that events happen to the right people in the right

sequence once the whole is formed. Modules can bere-used in two ways. As withour program from the 1960s, we would lift the matrix inversion routineand put a

different user interface around it. We can also re-use a routine within a program

several times.

For example, solving the equations of space flight involves the inversion of

many matrices. We wouldc2001 J.E. Akin 2want our program to use the matrix

inversion routine over and over, presenting it with a different matrixeach time.

30


31/101

The fundamental components of good program design are

1. Problem definition, leading to a program specification2. Modular program design, which refines the specification3. Module composition, which translates specification into executable program4. Module/program evaluation and testing, during which you refine the

program and find errors

5. Program documentation, which pervades all other phasesThe result of following these steps is an efficient, easy-to-use program that has a

users guide (how doessomeone else run your program) and internal

documentation so that other programmers can decipher thealgorithm.

Today it is common in a university education to be required to learn at least one

foreign language.Global interactions in business, engineering, and government

make such a skill valuable to ones career.So it is in programming. One often

needs to be able to read two or three programming languages evenif you compose

programs in only one language. It is common for different program modules, in

differentlanguages, to be compiled separately and then brought together by a

linker to form a single executable.

When something goes wrong in such a process it is usually helpful to have a

reading knowledge of theprogramming languages being used.

When composing to express ideas there are, at least, two different approaches

to consider: poetry andprose. Likewise, in employing programming languages to

create software there are distinctly differentapproaches available. The two most

common ones are procedural programming and object-orientedprogramming.

31


32/101

The two approaches are conceptually sketched. They differ in the way that

thesoftware development and maintenance are planned and implemented.

Procedures may use objects, andobjects usually use procedures, called methods.

Usually the object-oriented code takes more planningand is significantly larger, but

it is generally accepted to be easier to maintain. Today when one can haveliterally

millions of users active for years or decades, maintenance considerations are very

important.

Input / Output Form Design

Input design is the process of converting user-originated inputs to a computer-

based format. Input design is one of the most expensive phases of the operation of

computerized system and is often the major problem of a system.

In the project, the input design is made in various web forms with various

methods. Forexample, in the Admin form, the empty username and password is not

allowed. The username if exists in the database, the input is considered to be

invalid and is not accepted.

Output design generally refers to the results and information that are generated by

the system for many employees; output is the main reason for developing the

system and the basis on which they evaluate the usefulness of the application.

In the project, if the employee has to communicate with other employees they can

communicate through send and receive message and directly interact with HR

manager.

32


33/101

In this module, we discuss the physical design of output, input, and user

interface. Although in the textbook authors include input forms as part of interface

design, I separated them. In my view, the user interface is not just input screens but

is a communication between users and the system. It is a two-way communication.

Input data and instruction (what users want to do) go into the system in many

forms. System replies with outputs, error messages, feedback, warning, help

functions, etc. Also the interface includes how users navigate through the system.

It could be commands, menus, or links that lead users to the next screen. It is a

structure of the system from users view point (while DFDs and Flowcharts are the

structure of the system from programmers view points).

Typical Physical DFD with Input and Output Functions

Outputs are data going out from the system to the users. The users may be an

external entity, or maybe internal (boundary between computer-system and manual

system). You have to be careful when determining the output data flow. Notice that

dataflow inquiry form is a form that induces the input from the user

(Customer), that means although the dataflow goes out of the system boundary,

that form is an input form and not an output.

Output-design Objectives

Outputs present information to system users. Outputs, the most visible

component of a working information system, are the justification for the system.

During systems analysis, you defined output needs and requirements, but you

didn't design those outputs. In this section, you will learn how to design effective

outputs for system users.

33


34/101

Serve the intended purpose Deliver the right quantity of output Deliver it to the right place Provide output on time Choose the right method

Types of Outputs

Internal outputs stay inside the system to support the system's users andmanagers

External outputs leave the system to trigger actions on the part of theirrecipients or confirm actions to their recipients

Turnaround outputs are those which are typically implemented as a reporteventually re-enters the system as an input

Detailed Reports:o Present information with little or no filtering or restrictions.o Some detailed reports are historical in nature.o

Detailed reports confirm and document the successful processing oftransactions and serve as an audit trail for subsequent management

inquiry.

34


35/101

o An example detailed report is depicted in the figure above. Thisexample is a listing of all purchase orders that were generated on a

particular date. Other example detail reports would be a detailed

listing of all customer accounts, orders, or products in inventory.

Exception Reports:o Filter data before it is presented to the manager as information.o Exception reports only report exceptions to some condition or

standard.

o An example is depicted in the figure above where delinquent memberaccounts are identified for following-up. Another classic examples of

an exception report is a report that identifies items that are low in

stock (soon to run out).

Output Media

PaperAlthough the paperless office (and business) has been predicted for

several years, it has not yet become a reality. Perhaps there is an irreversible

psychological dependence on paper as a medium. In any case, paper output

will be with us for a long time.

35


36/101

ScreenTherefore, other than paper, the most common output medium is

screen (monitor).Although the screen medium provides the system user with

convenient access to information, the information is only temporary. When

the image leaves the screen, that information is lost unless it is redisplayed.

If a permanent copy of the information is required, paper and film are

superior media. Often times when system designers build systems that

include screen outputs, they also may provide the user with the ability to

obtain that output on paper.

Microfilm/MicroficheThe use of film does present its own problems - microfiche and

microfilm can only be produced and read by special equipment.

Output Formats

Tabular outputMost of the computer programs written probably generated tabular

reports.

36


37/101


38/101

User-type and the degree of user-friendliness have correlation. For example,casual users require the most user friendly interfaces. You cannot expect

them to handle command interfaces. On the other hand, dedicated users

want the performance of interfaces, meaning that minimizing key-strokes,

movement of mouth should be minimized. In such a case, user-friendliness

is not so important

Dedicated system user is one who will spend considerable time usingspecific programs. This user is likely to become more comfortable and

familiar with the terminal or PC's operation.

Casual system usermay only use a specific program on an occasional basis.This user may never become truly comfortable with the terminal or the

program.

Most of the time you design a part of the system (one report, or one inputscreen), you can see who are the users. Most probably you can tell the type

of the users. With a few exceptions, those users are either dedicated orcasual, not both. So you design that part of the system according to the

users preference of user friendliness.

Input Methods

Batch inputBatch input is the oldest and most traditional input method. Source

documents or forms are collected and then periodically forwarded to data

entry operators, who key the data using a data entry device that translates the

data into a machine-readable format.

38


39/101

The most common medium for batch input data are Key-to-disk

(KTD) and key-to-tape (KTT) workstations that transcribe data to magnetic

disks and magnetic tape, respectively.

On-line inputOn-line input is the capture of data at its point of origin in the business

and the direct inputting of that data to the computer, preferably as soon as

possible after the data originates.

The system user directly enters the data when or soon after that data

originates. No data entry clerks are needed! There is no need to record data

onto a medium (paper and such) that is later input to the computer; this input

is direct! If data is entered incorrectly, the computer's edit program detects

the error and immediately requests that the operator make a correction.

Trends in Automatic Data Collection Technology

Biometric ADCBiometric ADC technology is based on unique human characteristics

or traits. For example, it is known that every individual can be identified by

their own unique fingerprint, voice pattern, or pattern of certain veins (retina

or wrist). This technology is particularly popular for systems that require

security access.

39


40/101

Electromagnetic (radio)Electromagnetic identification technology is becoming very popular

in applications that involve tracking physical objects are out of sight and on

the move. For example, electromagnetic ADC is being used for public

transportation tracking and control, tracking manufactured products, and

tracking animals to name a few.

Magnetic (MICR)There are over one billion magnetic stripe cards in use today! They

have found their way into a number of business applications such as, credit

card transactions, building security access control, and employee attendance

tracking.

Optical (Bar coding )Point-of-sale terminals in retail and grocery stores frequently include

bar-code and optical-character readers. Bar codes eliminate the need for

keying data, either by data entry clerks or end-users.

Smart CardsSmart card applications are particularly promising in the area of health

records where a persons blood type, vaccinations, and other past medical

history can be made readily available. Other uses may include such

applications as passport, financial information for point-of-sale transactions,

pay-television, etc.

40


41/101

System User Issues for Input Design

Capture only variable data. Do not capture data that can be calculated or stored in computer programs. Use codes for appropriate attributes.

41


42/101

Input / Output Screen

User Login-

42


43/101

Figures Of Module Daak

Add Department Master Form

43


44/101

Letter Receive Entry Form

44


45/101

Letter Send Entry Form

45


46/101

Receive Letter Transaction

46


47/101

Report Of Send Letters

47


48/101

Report Of Receive Letters

48


49/101

Figures Of Module Rashan Card

Rashan card ShopOwner Entry Master

49


50/101

Rashan Card Entry Form

50


51/101

Report Of Applied Candidate for Rashan Card

51


52/101

Candidate Family Report

52


53/101

Figures Of Tables

Tables of Module Daak

Add Department Master

53


54/101

Letter Receive Table

54


55/101

Letter send Table

55


56/101

Letter Status Table

56


57/101

Tables of Module Rashan Card

Add Rashancard Shop Owner Table

57


58/101

Rashan Card Apllied Candidate Entry Table

58


59/101

Rashan card Candidate family Table

59


60/101

Rashan card Status Table

60


61/101

SYSTEM TESTING

Testing is the major control measure used during software development. Its basicfunction is to detect errors in the software. During requirement analysis and design,

the output is a document that is usually textual and no executable. After the coding

phase, computer programs are available that can be executed for testing purpose.

This implies that testing not only has to uncover errors introduced during coding,

but also errors introduced during previous phase. Thus the goal of testing is to

uncover the requirements, design and coding errors in the programs.

Objectives of testing

First of all objectives should be clear.

Testing as a process of executing a program with the intent of finding errors. To perform testing, test cases are designed. A test case is a particular made up

of artificial situation upon which a program is exposed so as to find errors. So

a good test case is one that finds undiscovered errors.

If testing is done properly, it uncovers errors and after fixing those errors wehave software that is being developed according to specifications.

The above objective implies a dramatic change in viewpoint .The move counter to

the commonly held view than a successful test is one in which no errors are found.

In fact, our objective is to design tests that a systematically uncover different

classes of errors and do so with a minimum amount of time and effort.

61


62/101

Testing principles

Before applying methods to design effective test cases, software engineer must

understand the basic principles that guide the software testing process. Some of the

most commonly followed principles are:

All test should be traceable to user requirements as the objective of testing is to

uncover errors, it follows that the most severe defects (from the users point of

view) are those that causes the program to fail to meet its requirements.

Tests should be planned long before the testing begins. Test planning can begin as

soon as the requirement model is complete. Detailed definition of test cases can

begin as soon as the design model has been solidated. Therefore, all tests can be

planned and designed before any code can be generated.

The Pareto principle applies to software testing stated simply the Pareto principle

implies that 80 percent of all errors uncovered during testing will likely be

traceable to 20 percent of all program modules. The problem of course, is to isolate

these suspects modules and to thoroughly test them.

Testing should begin in the small and progress towards testing in large. The

first tests planned and executed generally focus on individual modules. As testing

progresses, testing shifts focus in an attempt to find errors in integrated clusters of

modules and ultimately in the entire system.

62


63/101

Exhaustive testing is not possible. The number of paths permutations for

impossible to execute every combination of paths during testing. It is possible

however to adequately cover program logic and to ensure that all conditions in the

procedural design have been exercised.

To be most effective, an independent third party should conduct testing. By most

effective, we mean testing that has the highest probability of finding errors (the

primary objective of testing).

Test information flow

Testing is a complete process. For testing we need two types of inputs:

Software configurationIt includes software requirement specification, design specification and source

code of program. Software configuration is required so that testers know what is to

be expected and tested.

Test configurationIt is basically test plan and procedure. Test configuration is testing plan that is, the

way how the testing will be conducted on the system. It specifies the test cases and

their expected value. It also specifies if any tools for testing are to be used.

Test cases are required to know what specific situations need to be tested. When

tests are evaluated, test results are compared with actual results and if there is some

error, then debugging is done to correct the error. Testing is a way to know about

quality and reliability. Error rate that is the occurrence of errors is evaluated. This

data can be used to predict the occurrence of errors in future.

63


64/101

A software product can be tested in two ways:-

In first approach, only overall functioning of the product is tested. Inputs are given

and outputs are checked. This approach is called black box testing. It does not care

about the internal functioning of the product.

The other approach is called white box testing. Here the internal functioning of the

product is tested. Each procedure is tested for its accuracy. It is more intensive than

black box testing. But for the overall product both these techniques are crucial.

There should be sufficient number of tests in both categories to test the overall

product.

Basic methods of Testing

White box testing

White box testing is performed to reveal problems with the internal structure of aprogram. This requires the tester to have detailed knowledge of the internal

structure. A common goal of white box testing is to ensure a test case exercises

every path through a program. A fundamental strength that all white box strategies

share is that the entire software implementation is taken into account during

testing, which facilitates error detection even when software specification is vague

or incomplete. The effectiveness or thoroughness of white box testing is commonly

expressed in terms of test or code coverage metrics, which measure the fraction of

code exercised by test cases.

64


65/101

Basic Path Testing

It is a white box technique. It was proposed by Tom McCabe. These tests

guarantee to execute every statement in the program at least one time during

testing. Basic set is the set of all execution paths of a procedure.

Black Box Testing

Black box tests are performed to access how well a program meets its

requirements, looking for incorrect or missing functionality. Functional tests

typically exercise code with valid or nearly valid input for which the expected

output is known. This includes concepts such as boundary values.

Performance tests evaluate response time, memory usage, throughput, device

utilization and execution time. Stress tests push the system to or beyond its

specified limits to evaluate its robustness and error handling capabilities.

Reliability tests monitor system response to representative user input, counting

failures over time to measure or certify reliability.

Black box testing uncovers the following types of errors

1. Incorrect or missing functions

2. Interface errors

3. External database access

4. Performance errors

5. Initialization and termination errors

65


66/101


67/101

These testing types are again divided in two groups:

a) Testing in which user plays a role of tester

b) User is not required.

Testing method where user is not required:-

Functional Testing:-In this type of testing, the software is tested for the functional requirements. The

tests are written in order to check if the application behaves as expected.

Stress Testing:-The application is tested against heavy load such as complex numerical values,

large number of inputs, large number of queries etc. which checks for the

stress/load the applications can withstand.

Load Testing:-The application is tested against heavy loads or inputs such as testing of web sites

in order to find out at what point the web-site/application fails or at what point its

performance degrades.

Ad-hoc Testing:-This type of testing is done without any formal Test Plan or Test Case creation.

Ad-hoc testing helps in deciding the scope and duration of the various other testing

and it also helps testers in learning the application prior starting with any other

testing.

67


68/101

Exploratory Testing:-This testing is similar to the ad-hoc testing and is done in order to learn/explore the

application.

Usability Testing:-This testing is also called as Testing for User-Friendliness. This testing is done if

User Interface of the application stands an important consideration and needs to be

specific for the specific type of user.

Smoke Testing:-This type of testing is also called sanity testing and is done in order to check if the

application is ready for further major testing and is working properly without

failing up to least expected level.

Recovery Testing:-Recovery testing is basically done in order to check how fast and better the

application can recover against any type of crash or hardware failure etc. Type or

extent of recovery is specified in the requirement specifications.

Volume Testing:-Volume testing is done against the efficiency of the application. Huge amount of

data is processed through the application (which is being tested) in order to check

the extreme limitations of the system.

68


69/101

Testing where user plays a role/user is required:

User Acceptance Testing:-In this type of testing, the software is handed over to the user in order to find out if

the software meets the user expectations and works as it is expected to.

Alpha Testing:-In this type of testing, the users are invited at the development center where they

use the application and the developers note every particular input or action carried

out by the user. Any type of abnormal behavior of the system is noted and rectified

by the developers.

Beta Testing:-In this type of testing, the software is distributed as a beta version to the users and

users test the application at their sites. As the users explore the software, in case if

any exception/defect occurs that is reported to the developers.

Advantages of Black Box Testing

More effective on larger units of code than glass box testing. Tester needs no knowledge of implementation, including specific

programming languages.

Tester and programmer are independent of each other. Tests are done from a user's point of view. Will help to expose any ambiguities or inconsistencies in the specifications. Test cases can be designed as soon as the specifications are complete.

69


70/101

Disadvantages of Black Box Testing

Only a small number of possible inputs can actually be tested, to test everypossible

Input stream would take nearly forever

Without clear and concise specifications, test cases are hard to design There may be unnecessary repetition of test inputs if the tester is not

informed of test cases the programmer has already tried

May leave many program paths untested Cannot be directed toward specific segments of code which may be very

complex (and therefore more error prone)

Testing With Live Data

We know, test cases are integral part of testing. So we need to know more about

test cases and how these test cases are designed. The most desired or obvious

expectation from the test cases is that it should be able to find most errors with the

least amount of time and effort.

Testing With Dummy Data

In this phase access local server data tables and procedure to test the web forms.

70


71/101

SYSTEM IMPLEMENTATION

The following guideline is a listing of key components to be taken into

consideration when developing an implementation project that is comprehensive

and realistic.

Management Support Project Management/Leadership Decision Makers

Selection of Team Members Outside Consultants Location of Team The Project Plan Duration of Project Scope Creep On-Time, Within Budget Team Espirit de Corps Team Recognition Communication

71


72/101


73/101

estimate numbers of hours for task completion, track status, manage project funds,

and more. By selecting a leader from both the functional and technical side, the

two individuals are better equipped to effectively work together to cover all areas

which may have an impact on the project.

Decision MakersWho will be selected to be the decision-makers for your project? There will be

plenty of decisions that will need to be made, and often, these decisions may have

to be made within a 24 to 48 hour period. Will Project Managers be empowered

with the authority to make all decisions? This is probably unlikely, particularly if itinvolves changing company policies. Typically, a Steering Committee that is

comprised of key stakeholders will meet with Project Leaders on a regular basis to

assist in removing obstacles and make decisions which may have an impact not

only on implementation schedules and deliverables, but the entire organization.

Selection of Team MembersPutting together a quality team is essential. During the selection process, it is

important to try and obtain the appropriate resources from both the functional and

technical areas. The functional team members will know the organizations

processes and procedures by job function and can determine whether or not policy

or procedural changes need to take place. The Project Team members will work

directly with sub-team members as well as others to help define system

requirements; review proposed designs; and help build tables which will drive the

system.

73


74/101

Technical team members will be key in working with the functional members to

pull together and program system requirements. They will serve as valuable

resources in knowledge of the legacy system's programs and functions. They will

also be involved in overall infrastructures such as networking between locations,

setting up workstations, etc.

The blending of functional and technical resources will allow for a collaborative

approach in designing, constructing and implementing the system.

Since this will no doubt be a new role for team members selected, it is important to

understand that initially there might be a period of adjustment and settling in to

their new roles. For the most part, they are being asked not only to take on a new

job, but a job which they have never done before. This in itself can cause anxiety at

times.

Project Leaders will want to work with team members on accepting and enjoying

this new experience. The reporting relationships to the Project Leaders must be

clearly defined to prevent problems. If 100% of team members time is being to the

project, then they should probably report to Project Leaders instead of their

managers. The opportunity for one to gain and expand skill sets during a project of

this nature is often viewed as a valuable and rewarding endeavor.

74


75/101

Outside ConsultantsBefore embarking on a new system implementation, it should be established

whether or not the organization will require the assistance of outside consultants. If

the organization has never gone (or has not done so recently) through a major

software implementation, then strong consideration should be given to obtaining

outside help. If the skills sets necessary are not available in-house, then outside

consultants should be used to compliment your current team's skill sets. Again, this

decision should be made prior to commencing the implementation process, since

costs associated with utilizing outside consultants need to be included in the

project budget.

Prior to hiring an outside consultant, be sure to interview anyone who is being

considered as a member of the project team. Obtain their most recent job

assignments and details of their overall qualifications. Ask for references and

check them thoroughly. Spending the time up front to select the most appropriate

outside consultant will pay big dividends in the end. Act as if you are hiring the

consultant to be an employee of your organization. You will want someone who is

qualified, experienced and committed, and who can contribute the necessary

resources for a successful implementation. Accept no one who does not meet your

expectations.

If the decision is made to hire an outside consultant, then the company should

spend the time needed with them to ensure they have an understanding of how the

organization operates, makes decisions, handles changes, etc. It is also important

for the consultant to understand the culture of the organization. This will help them

75


76/101

gain a better understanding of what the expectations are, how they should approach

the project and how flexible they will need to be.

Location of TeamThe project may be better served if the entire project team is moved to an off-site

location. At a minimum, they should all be relocated to a common work area. By

not doing so, the company is running a risk that project team members will be

pulled back into their "old jobs". This can result in team members not having

sufficient time to work on project assignments. Providing team members with the

ability to focus solely on priorities and job assignments for the implementation

process is an absolute necessity.

The Project TeamEstablishing a comprehensive project plan which includes the objectives of the

implementation is key to meeting all required deliverables during the project.

There is usually quite a bit of time spent in the beginning stages of the project just

pulling together necessary components of the project plan. The project plan is a

living document in that it will change and get updated almost on a daily basis. The

project plan will become an everyday tool used by all team members. It will help

to clarify the who, what, when, where, and why's. Without a good project plan, the

team will not know what is expected of them and important deliverables may be

missed altogether.

76


77/101

Duration of ProjectProject size, complexity and resources available will be the beginning points for

determining a completion date for the project. Ensure the approach taken is one

that produces a manageable project. Having a project that is too long and drawn

out will have an adverse impact on everything from level of motivation amongst

team members, available funding, scope creep and more. Once you start down the

road of moving out your Go Live date, you will suffer from lack of team

motivation and sense an urgency to complete the assignment on time. Therefore,

be sure to set a realistic Go Live date and stick to that date. The only time where

you may wish to consider delaying your Go Live date is if testing results are not

favorable. Meeting a deadline is not worth the risk of an incomplete and faulty

system.

On-time, Within BudgetOne way to help ensure funding and support for future HRMS initiatives is to

deliver the implementation on time and within budget. With a project of this size

and nature, it is very easy to get side-tracked. Don't let scope creep happen to you.

The term scope creep is often used in large projects. Scope creep is typically

defined as allowing or agreeing to additional work requests that were not part of

the original project plan or objectives. Be careful - this can happen easily in any

size organization. When you recognize scope creep, be firm but fair when others

try to expand the project. Taking on additional work that was not part of the

original plan can and does cost additional time and money. Keep in mind the extra

effort needed to take on new work can quickly spiral out of control.

77


78/101

Team Espirit de CorpsUnlike other project teams, this will no doubt end up being a special team and will

espouse a need to have its own identity. You will want others who are not on the

project to know what it is you will be delivering to the organization. In order to

develop and keep alive the level of motivation and dedication required, different

ways to engage team building and comradery throughout the life of the project will

need to be thought up.

As the project begins, look into having team members' work together on designing

a team logo, team name, or work on creating a vision and/or mission statement. Be

sure to use the project logo with every communication that goes out to others

regarding the implementation.

Adequate marketing of your project will help to further identify what your key

deliverables and objectives are. Other ideas are to have t-shirts; sweatshirts, pens,

etc. made with the team logo and/or name.

Team RecognitionReward and recognize team members throughout the entire project. When major

milestones are met - celebrate! When the team has successfully overcome a

difficult assignment - recognize their efforts and contributions. Keep in mind that

recognition does not always need to be in the form of compensation. A good old

fashion pat on the back still works wonders. Get upper level management and/or

your Steering Committee to help provide recognition to the team. Sometimes it's

the little things that people appreciate like doughnuts, cookies, hats, a team picture

in a company newsletter, etc.

78


79/101

CommunicationCommunicate, communicate, communicate! Sure you and the other team members

may be fully aware of your goals and objectives, but what about all of the other

stakeholders, end users, internal and external customers? Do no underestimate the

need to know and the importance of sharing with others in the organization what

the implementation will mean for them and the company as a whole. You may

want to create a special newsletter that gets published on a regular basis letting

everyone know of the projects progress, etc. How about setting up a page on the

company's Intranet? There are many ways in which you can and should keep

constituents informed about this major project.

Communications inside the project team is another key element that can help to

facilitate a healthy team environment. With the amount of activity that occurs, it

will be important to establish early on a means for open and effective

communication between all team members.

79


80/101

Limitations & Future Scope

Once you have successfully reached your Go Live date and had an opportunity to

celebrate your implementation, your focus will begin to change from a tactical to a

more strategic effort. In order to help support and validate the value the new

system brings to the organization, it will be necessary to embark on forward

thinking. Typically an exercise in determining the lessons learned from your

implementation and sharing it with management is a valuable and rewarding task.

Perhaps you will go out and solicit feedback from your internal and external

customers who are involved and are using the new system.

Leverage the investment the organization has made by ensuring the system is used

correctly and that data integrity is validated. Expand the knowledge and skill sets

of your end users by providing on going training on the system. Developing and

implementing knowledge transfer strategy on how to effectively use the system

will be beneficial.

Take the time to develop power users of the system. Develop and maintain a

knowledge transfer between co-workers and across boundaries. Use the data

available in the system to create and produce meaningful data to others in the

organization. By providing information that can be used to help make key

decisions, you will be assisting in developing an increased Human Resources

strategic position within the organization.

As you gain more experience with the new system and gain a better understanding

of it's full potential; you will be better equipped and able to make significant

contributions to all areas of the organization.

80


81/101

Language Technology Use for ProjectFRONT END DESIGN

FEATURES OF ASP.NETASP.NET is the next version of Active Server Pages (ASP); it is a

unified Web development platform that provides the services necessary for

developers to build enterprise-class Web applications. While ASP.NET is largely

syntax compatible, it also provides a new programming model and infrastructure

for more secure, scalable, and stable applications.

ASP.NET is a compiled, NET-based environment, we can author applications in

any .NET compatible language, including Visual Basic .NET, C#, and JScript

.NET. Additionally, the entire .NET Framework is available to any ASP.NET

application. Developers can easily access the benefits of these technologies, which

include the managed common language runtime environment (CLR), type safety,

inheritance, and so on.

ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors

and other programming tools, including Microsoft Visual Studio .NET. Not only

does this make Web development easier, but it also provides all the benefits that

these tools have to offer, including a GUI that developers can use to drop server

controls onto a Web page and fully integrated debugging support.

Developers can choose from the following two features when creating an

ASP.NET application.Web Forms and Web services, or combine these in any way

they see fit. Each is supported by the same infrastructure that allows you to use

81


82/101


83/101

ASP.NET provides a simple model that enables Web developers to write logic that

runs at the application level. Developers can write this code in the global.aspx text

file or in a compiled class deployed as an assembly. This logic can include

application-level events, but developers can easily extend this model to suit the

needs of their Web application.

ASP.NET provides easy-to-use application and session-state facilities that

are familiar to ASP developers and are readily compatible with all other .NET

Framework APIs.ASP.NET offers the IHttpHandler and IHttpModule interfaces.

Implementing the IHttpHandler interface gives you a means of interacting with the

low-level request and response services of the IIS Web server and provides

functionality much like ISAPI extensions, but with a simpler programming model.

Implementing the IHttpModule interface allows you to include custom events that

participate in every request made to your application.

ASP.NET takes advantage of performance enhancements found in the .NET

Framework and common language runtime. Additionally, it has been designed to

offer significant performance improvements over ASP and other Web development

platforms. All ASP.NET code is compiled, rather than interpreted, which allows

early binding, strong typing, and just-in-time (JIT) compilation to native code, to

name only a few of its benefits. ASP.NET is also easily factorable, meaning that

developers can remove modules (a session module, for instance) that are not

relevant to the application they are developing.

83


84/101

ASP.NET provides extensive caching services (both built-in services and

caching APIs). ASP.NET also ships with performance counters that developers and

system administrators can monitor to test new applications and gather metrics on

existing applications. Writing custom debug statements to your Web page can help

immensely in troubleshooting your application's code. However, it can cause

embarrassment if it is not removed. The problem is that removing the debug

statements from your pages when your application is ready to be ported to a

production server can require significant effort.

ASP.NET offers the TraceContext class, which allows us to write custom

debug statements to our pages as we develop them. They appear only when you

have enabled tracing for a page or entire application. Enabling tracing also appends

details about a request to the page, or, if you so specify, to a custom trace viewer

that is stored in the root directory of your application. The .NET Framework and

ASP.NET provide default authorization and authentication schemes for Web

applications. We can easily remove, add to, or replace these schemes, depending

upon the needs of ourapplication.

ASP.NET configuration settings are stored in XML-based files, which are

human readable and writable. Each of our applications can have a distinct

configuration file and we can extend the configuration scheme to suit our

requirements.

84


85/101

DATA ACCESS WITH ADO.NETAs you develop applications using ADO.NET, you will have different

requirements for working with data. You might never need to directly edit an

XML file containing data - but it is very useful to understand the data architecture

in ADO.NET.

ADO.NET offers several advantages over previous versions of ADO

Interoperability

Maintainability

Programmability

Performance Scalability

Interoperability

ADO.NET applications can take advantage of the flexibility and broad

acceptance of XML. Because XML is the format for transmitting datasets across

the network, any component that can read the XML format can process data. The

receiving component need not be an ADO.NET component.

The transmitting component can simply transmit the dataset to its destination

without regard to how the receiving component is implemented. The destination

component might be a Visual Studio application or any other application

implemented with any tool whatsoever.

85


86/101

The only requirement is that the receiving component be able to read XML. SO,

XML was designed with exactly this kind of interoperability in mind.

Maintainability

In the life of a deployed system, modest changes are possible, but

substantial, Architectural changes are rarely attempted because they are so

difficult. As the performance load on a deployed application server grows, system

resources can become scarce and response time or throughput can suffer. Faced

with this problem, software architects can choose to divide the server's business-

logic processing and user-interface processing onto separate tiers on separate

machines.

In effect, the application server tier is replaced with two tiers, alleviating the

shortage of system resources. If the original application is implemented in

ADO.NET using datasets, this transformation is made easier.

ADO.NET data components in Visual Studio encapsulate data access

functionality in various ways that help you program more quickly and with fewer

mistakes.

Performance

ADO.NET datasets offer performance advantages over ADO disconnected

record sets. In ADO.NET data-type conversion is not necessary.

86


87/101

Scalability

ADO.NET accommodates scalability by encouraging programmers toconserve limited resources. Any ADO.NET application employs disconnected

access to data; it does not retain database locks or active database connections for

long durations.

VISUAL STUDIO .NETVisual Studio .NET is a complete set of development tools for building ASP

Web applications, XML Web services, desktop applications, and mobile

applications In addition to building high-performing desktop applications, you can

use Visual Studio's powerful component-based development tools and other

technologies to simplify team-based design, development, and deployment of

Enterprise solutions.

Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same

integrated development environment (IDE), which allows them to share tools and

facilitates in the creation of mixed-language solutions.

In addition, these languages leverage the functionality of the .NET

Framework and simplify the development of ASP Web applications and XML

Web services. Visual Studio supports the .NET Framework, which provides a

common language runtime and unified programming classes; ASP.NET uses these

components to create ASP Web applications and XML Web services. Also it

includes MSDN Library, which contains all the documentation for these

development tools.

87


88/101

THE .NET FRAMEWORKThe .NET Framework is a new computing platform that simplifies

application development in the highly distributed environment of the Internet.

OBJECTIVES OF. NET FRAMEWORK1.To provide a consistent object-oriented programming environment whether

object codes is stored and executed locally on Internet-distributed, or executed

remotely.

2.To provide a code-execution environment to minimizes software deployment and

guarantees safe execution of code.

3. Eliminates the performance problems

There are different types of application, such as Windows-based applications and

Web-based applications.

To make communication on distributed environment to ensure that code be

accessed by the .NET Framework can integrate with any other code.

COMPONENTS OF .NET FRAMEWORK THE COMMON LANGUAGE RUNTIME (CLR)

The common language runtime is the foundation of the .NET Framework. It

manages code at execution time, providing important services such as memory

management, thread management, and remoting and also ensures more security

and robustness. 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

88


89/101


90/101

SECURITYThe runtime enforces code access security. The security features of the

runtime thus enable legitimate Internet-deployed software to be exceptionally

feature rich. With regards to security, managed components are awarded varying

degrees of trust, depending on a number of factors that include their origin to

perform file-access operations, registry-access operations, or other sensitive

functions.

ROBUSTNESSThe 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 managed environment

of the runtime eliminates many common software issues

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

90


91/101

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

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

such as Microsoft SQL Server and Internet Information Services (IIS).

ChangeoverAs name suggest it is the process of changing the old information system.

System changeover is the process of putting the new information system online

and retiring the old system. The four system changeover approaches description,

advantages, disadvantages and the implications of using each of these

approaches at Health Centres to change from the existing manual system to the

new CHIS are as follows-:

Direct Cutover:In simple words direct cutover approach is a direct approach where old

system is cut and over write by new system. The direct cutover approach causes

the changeover from the old system to the new system to occur immediately when

the new system becomes operational.

This is a least expensive method among all four but involves high risk of data

loss. With the direct cutover method, company cannot revert to the old system as a

backup option.

91


92/101


93/101

Pilot Operation:The pilot operation changeover method involves implementing the complete

new system at a selected location of the company. The group that uses the new

system first is called the pilot site. The old system continues to operate for the

entire organization including the pilot site. After the system proves successful at

the pilot site, it is implemented in the rest of the organization, usually using direct

cutover method. Pilot operation is combination of parallel operation and direct

cutover methods.

Pilot site assure the working of new system and reduces the risk of system

failure. This is also less expensive than the parallel operation as only at one section

both system works for limited period.

This is less expensive and safer approach as its combination of both direct

cutover and parallel operation. It will save money of health centre and also keep

their data safe with smooth working.

Phased Operation -:Phased operation works in different phases or stages. Implementation of new

system in modules or stages is phased operation. This is also a combination of

direct cutover and parallel similar to pilot operation. But in this approach the entire

system is provided to some users instead a part of system to all users.

In phase operation the risk of errors or failures is limited to the implemented

module only and also phased operation is less expensive than the full parallel

operation. But in some cases, phased operation can cost more than a pilot approach

where the system involves a large number of separate phases.

93


94/101

Health centre involves various phases such as registration, measuring weight,

treatment, vaccination, diagnosis and more. Because of the involvement of so

many phases it would be difficult and costly to apply phased operation approach.

RecommendationFrom the above discussion about all four possible approaches, it is very clear

that data cutover and parallel operation approach alone is not suitable for the CHIS

because of drawbacks like high risk or high cost but the combination of both

approaches namely pilot operation and phased operation approaches is more

fruitful.

Still phased operation is not most suitable approach as we know there are

lot of phases involve in our information system and also lack of fund is there. So

conclusion is pilot operation is the most recommended approach for the CHIS

because this method is cheaper and safer method. Any one of the health centre

can implement the new system and after the system proves successful, it will be

used by other health centres by using direct cutover. In this way it will beimplemented under budget and also there will be low risk of system failure.

94


95/101

Bibliography

1.

www.w3schools.com2. http://msdn.microsoft.com/en-

us/library/system.web.httpcontext.session.aspx

3. www.dotnetspider.com4. http://www.edrawsoft.com/Flowchart-tutorial.php5. http://www.codeproject.com/KB/database/DatabaseAcessWithAdoNet1.asp

x

6. http://quickstarts.asp.net/QuickStartv20/aspnet/doc/pages/pages.aspx7. http://www.bigresource.com/MS_SQL-data-binding-d4UHaJPz.html8. http://www.sql-server-performance.com9. http://www.mis-drishtee.in

95
http://www.w3schools.com/http://www.asp.com/http://www.asp.com/http://www.asp.com/http://www.asp.com/http://www.dotnetspider.com/http://www.csharpcorner.com/http://www.microsoft.com/http://www.microsoft.com/http://www.microsoft.com/http://www.microsoft.com/http://quickstarts.asp.net/QuickStartv20/aspnet/doc/pages/pages.aspxhttp://www.bigresource.com/MS_SQL-data-binding-d4UHaJPz.htmlhttp://www.sql-server-performance.com/http://www.sql-server-performance.com/http://www.bigresource.com/MS_SQL-data-binding-d4UHaJPz.htmlhttp://quickstarts.asp.net/QuickStartv20/aspnet/doc/pages/pages.aspxhttp://www.microsoft.com/http://www.microsoft.com/http://www.csharpcorner.com/http://www.dotnetspider.com/http://www.asp.com/http://www.asp.com/http://www.w3schools.com/


96/101

List of Abbreviations

Abbreviation Description

GUI Graphical User Interface

OS Operating System

DBMS Database Management System

GB Giga Bytes

DFD Data Flow Diagram

ER Entity Relationship

96


97/101

Index

1. Introduction..............1

2. Problem Definition.......2

3. System Analysis &Feasibility Study............3

4. Scope of a proposed System.............................6

5. System Requirements........7

o Hardware Requirementso Software Requirements

Front End

Back End

6. System Logical Design..................8

o Data flow diagram12o Data Dictionary16

7. System Physical Design26

8. Input / Output Screen42

9. Testing ..61

10.Implementation..71

11. Limitations & Future Scope .80

12. Bibliography..95
http://mrdavims.org/filesserve.php?file=n4beceec2b80cb#page=1


98/101

List of Tables

Table Page no.

1. Add Department Master 53

2. Letter Receive Table 54

3. Letter Send Table 55

4.Letter Status Table 56

5.Add RashanCard ShopOwner Master 576.Rashan Card Applied Candiadate 58

7.Rashan Card Candidate Family 59

8.Rashan Card Status Table 60


99/101

List of Figures

Figure name Page no.

1.Add Department Master Form 42

2.Letter Receive Form 43

3.Letter Send Form 45

4.Receive letter Transaction 46

5.Receive letter Report 47

6.Send letter Report 48

7.Add Rashan Card Shopowner Form 49

8.Rashan Card Candidate Form 50

9.Rashan Card Applied Candidate Report 51

10.Rashan Card Candidate family Report 52


100/101

A Project ReportOn

Integrated Block Of Management Sysytem

Submitted in Partial Fulfillment of the Requirement for

the Degree of Master of Computer Applications

Gautam Buddh Technical University, Lucknow

Project Guide: Submitted By:

Mr. Mahadev SACHIN VERMA

Associate Professor Roll no.1001514038

JUNE, 2013

Invertis Institute of Management Studies, Bareilly Lucknow Highway,

NH-24, Bareilly


101/101

block office project

Documents