SOFTWARE FEATURES

VISUAL BASIC.NET

Visual Baic.Net has revolutionized windows programming windows

programming and with an object based, event driven approach to software
designs. Visual basic.Net applications act as a front end to the database.
Visual basic.Net application provides the interface between the user and the
database. Sophisticated features that make the language truly object oriented
and interfaces it with the latest in the database technology.

.NET provides a new, object-oriented API as a set of classes that will be

accessible from any programming language. This book describes this
framework of classes and provides a reference to what is available and how
you can use this framework to write Windows applications in the brave new
world of .NET.

Microsoft .NET Framework is a computing platform for developing

distributed applications for the Internet. Following are the design goals of
Microsoft .NET Framework:

1. To provide a very high degree of language interoperability

2. To provide a runtime environment that completely manages code
execution
3. To provide a very simple software deployment and versioning model
4. To provide high-level code security through code access security and
strong type checking
5. To provide a consistent object-oriented programming model
 6. To facilitate application communication by using industry standards
such as SOAP and XML.
7. To simplify Web application development

Visual basic.net lets the user to add menus, text boxes, command
buttons, option buttons, check boxes, list boxes, scroll bars, and file
directory boxes to blank windows. Visual basic.net has many different tools.

The Common Language Runtime

The CLR is the mechanism through which .NET code is executed. It

is built upon a single, common language—IL—into which source languages
are compiled and includes mechanisms for executing the compiled code.
This includes code verification and just-in-time (JIT) compilation, garbage
collection and enforcement of security policies, and the provision of
profiling and debugging services.

The CLR provides a lot of added value to the programs it supports.

Because it controls how a .NET program executes and sits between the
program and the operating system, it can implement security, versioning
support, automatic memory management through garbage collection, and
provide transparent access to system services

IMPORTANT FEATURES

 The application is a graphical user interface.

  Client-Server architecture benefits picture and image box
can be easily handled using bit mapped files and icons.
 Bit mapped files and icons are used as simple debugging
tools.
 With the advent of .NET, Microsoft has introduced many
new technologies that make writing component-based
distributed systems easier, more flexible, and more
powerful than ever before.
 It is now easier than it has ever been to write components
in any programming language that can interoperate with
components on other machines, which may not be
Windows-based at all.

SQL SERVER

The purpose of this document is to help you migrate your applications

when you are migrating the underlying database from Microsoft SQL Server
to Some other Database. Most of the issues encountered when migrating
applications to use a Sql Server Database are related to database
incompatibility. This paper presents these incompatibilities and provides
solutions for many issues.

You should familiarize yourself with this document prior to migrating

your databases. The choices made about how to migrate your application
affect how you migrate the underlying database from Microsoft SQL Server
to some other Database.
 If the application uses the Microsoft OLE DB Provider for SQL
Server or a third-party OLE DB Provider to connect the Microsoft SQL
Server database, use the Sql Server Provider for OLE DB (SQLOLEDB) to
connect to the migrated Database.

SQL Server Security

Login Authentication.
Windows NT Authentication
SQL Server Authentication

Permissions validation on user database.

 T-SQL statements sent to SQL Server.
SQL server checks user permissions on receipt of T-SQL
statements

FEATURES

 Created by Microsoft and Sybase in the 80s.

 Is SQL Compliant - Uses ANSI SQL
 Supports SQL – 92 standards - Uses T-SQL
 Stores data in a central location and delivers it to clients on request
 New Server Architecture
 Graphic Administration Tools
 Maintains ANSI standards and 6.x Compatibility
  Data integrity means reliability and accuracy of data.
 Integrity rules keep data consistent.
 Supports Client/Server model.
 Request response dialog.
 Workload is split between the client and the server.
 Operating System compatibility.
 Runs on Win 95/98 NT, Netware, UNIX, OS/2, AppleTalk, Banyan
VINES.
 SQL Server must have Service Pack 4 (SP4) to run on Windows NT
4.0.
 Multiple protocol compatibility.
 SQL Server supports these protocols - AppleTalk, TCP/IP.
 SMP Compatibility and Scalability
 Supports multiple processors. SMP leads to scalability.

INPUT DESIGN

Input design is the process of converting the user-oriented. Input to a

computer based format. The goal of the input design is to make the data
entry easier, logical and free error. Errors in the input data are controlled by
the input design. The quality of the input determines the quality of the
system output.

The entire data entry screen is interactive in nature, so that the user
can directly enter into data according to the prompted messages. The user is
also can directly enter into data according to the prompted messages. The
users are also provided with option of selecting an appropriate input from a
list of values. This will reduce the number of error, which are otherwise
likely to arise if they were to be entered by the user itself.

Input design is one of the most important phases of the system design.
Input design is the process where the input received in the system are
planned and designed, so as to get necessary information from the user,
eliminating the information that is not required. The aim of the input design
is to ensure the maximum possible levels of accuracy and also ensures that
the input is accessible that understood by the user.

The input design is the part of overall system design, which requires
very careful attention. If the data going into the system is incorrect then the
processing and output will magnify the errors.

The objectives considered during input design are:

 Nature of input processing.

 Flexibility and thoroughness of validation rules.
 Handling of properties within the input documents.
 Screen design to ensure accuracy and efficiency of the
input relationship with files.
 Careful design of the input also involves attention to
error handling, controls, batching and validation
procedures.
Input design features can ensure the reliability of the system and produce
result from accurate data or they can result in the production of erroneous
information.
Data Flow Diagram (DFD)

The first step is to draw a data flow diagram (DFD). The DFD was
first developed by Larry Constantine as a way of expressing system
requirements in graphical form.

A DFD also known as a “bubble chart” has the purpose of clarifying

system requirements and identifying 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
lowest level of detail. A DFD consists of series of bubbles join by the data
flows in the system.

The purpose of data flow diagrams is to provide a semantic bridge

between users and systems developers. The diagrams are:

• Graphical, eliminating thousands of words;

• Logical representations, modeling WHAT a system does, rather than

physical models showing HOW it does it;

• Hierarchical, showing systems at any level of detail; and

• jargon less, allowing user understanding and reviewing.

The goal of data flow diagramming is to have a commonly understood

model of a system. The diagrams are the basis of structured systems
analysis. Data flow diagrams are supported by other techniques of structured
systems analysis such as data structure diagrams, data dictionaries, and
procedure-representing techniques such as decision tables, decision trees,
and structured English.
External Entity

An external entity is a source or destination of a data flow, which is

outside the area of study. Only those entities, which originate or receive
data, are represented on a business process diagram. The symbol used is an
oval containing a meaningful and unique identifier.

Process

A process shows a transformation or manipulation of data flows

within the system. The symbol used is a rectangular box, which contains 3
descriptive elements: Firstly an identification number appears in the upper
left hand corner. This is allocated arbitrarily at the top level and serves as a
unique reference. Secondly, a location appears to the right of the identifier
and describes where in the system the process takes place.

Data Flow

A data flow shows the flow of information from its source to its
destination. A data flow is represented by a line, with arrowheads showing
the direction of flow. Information always flows to or from a process and
may be written, verbal or electronic. Each data flow may be referenced by
the processes or data stores at its head and tail, or by a description of its
contents.

Data Store

A data store is a holding place for information within the system: It is

represented by an open ended narrow rectangle. Data stores may be long-
term files such as sales ledgers, or may be short-term accumulations: for
example batches of documents that are waiting to be processed. Each data
store should be given a reference followed by an arbitrary number.

Resource Flow

A resource flow shows the flow of any physical material from its
source to its destination. For this reason they are sometimes referred to as
physical flows. The physical material in question should be given a
meaningful name. Resource flows are usually restricted to early, high-level
diagrams and are used when a description of the physical flow of materials is
considered to be important to help the analysis.

OUTPUT DESIGN

Output design is very important concept in the computerized system,

without reliable output the user may feel the entire system is unnecessary
and avoids using it. The proper output design is important in any system and
facilitates effective decision-making. The output design of this system
includes various reports.

Computer output is the most important and direct source of

information the user. Efficient, intelligible output design should improve the
system’s relationships with the user and help in decision making. A major
form of output is the hardcopy from the printer.

Output requirements are designed during system analysis. A good

starting point for the output design is the data flow diagram. Human factors
reduce issues for design involved addressing internal controls to ensure
readability.
 An application is successful only when it can provide efficient and
effective reports. Reports are actually presentable form of the data. The
report generation should be useful to the management for future reference.
The report is the main source of information for user’s operators and
management. Report generated are a permanent record of the transaction
occurred. After any valid transactions; have commenced the report of the
same is generation and: filed for future reference. Great care has been taken
when designation the report as it plays an important role in decision-
marking.

DATABASE DESIGN

A well database is essential for the good performance of the system

.several tables are referenced or manipulated at various instance. The table
also knows as relation; provide information pertaining to a specified entity.
Normalization of table is carried out to extent possible, while the
normalizing tables, care should be taken to make sure that the number of
tables do not exceed the optimum level, so that table maintenance. Is
convenient and effective

The process of doing database design generally consists of a number of steps

which will be carried out by the database designer. Not all of these steps will
be necessary in all cases. Usually, the designer must:

Determine the data to be stored in the database

Determine the relationships between the different data elements

Superimpose a logical structure upon the data on the basis of these
relationships. Within the relational model the final step can generally be
broken down into two further steps that of determining the grouping of
information within the system, generally determining what are the basic
objects about which information is being stored, and then determining the
relationships between these groups of information, or objects. This step is
not necessary with an Object database.

In a majority of cases, the person who is doing the design of a

database is a person with expertise in the area of database design, rather than
expertise in the domain from which the data to be stored is drawn e.g.
financial information, biological information etc. Therefore the data to be
stored in the database must be determined in cooperation with a person who
does have expertise in that domain, and who is aware of what data must be
stored within the system.

CODE DESIGN

Code is an order collection of symbols designed to provide unique

identification of an entry or attribute. Sometimes used in the place of name
of the item they can be specified all object’s physical or performances
characteristics or operational instructions. They can also show inter
relationship and may sometime be used to achieve secrecy or
confidentiality.

Most computer systems are stable from the compiler down to the
execution of binary instructions. Therefore, it's natural to think of "product"
as the artifact just above that base. That's language source code. The system
that produces that artifact is still quite unpredictable, so it's not likely we'll
shift our orientation. Artifacts more abstract, be they whatever, will
constitute a nebulous range of "designs" or "specifications". I think it's the
lack of a direct and strictly repeatable translation of these artifacts that
characterizes them.

TESTING AND IMPLEMENTATION

SYSTEM TESTING

It is the stage of implementation, which ensures that system works

accurately and effectively before the live operation Commences. It is a
confirmation that all are correct and opportunity to show the users that the
system must be tested with text data and show that the system will operate
successfully and produce expected results under expected conditions.

Before implementation, the proposed system must be tested with raw

data to ensure that the modules of the system work correctly and
satisfactorily. The system must be tested with valid data to achieve its
objective.

The purpose of system testing is to identify and correct errors in the

candidate system. As important as this phase is, it is one that is frequently
compromised. Typically, the project the schedule or the user is eager to go
directly to conversion. Actually, testing is done to achieve the system goal.
Testing is vital to the parts of the system are correct; the goal will be
successfully achieved. Inadequate testing or non-testing leads to errors that
may not appear until months later Appearance of the problem.
SYSTEM IMPLEMENTATION

The purpose of System Implementation can be summarized as

follows:

It making the new system available to a prepared set of users (the

deployment), and positioning on-going support and maintenance of the
system within the Performing Organization (the transition). At a finer level
of detail, deploying the system consists of executing all steps necessary to
educate the Consumers on the use of the new system, placing the newly
developed system into production, confirming that all data required at the
start of operations is available and accurate, and validating that business
functions that interact with the system are functioning properly.
Transitioning the system support responsibilities involves changing from a
system development to a system support and maintenance mode of
operation, with ownership of the new system moving from the Project Team
to the Performing Organization.

List ofSystem implementation is the important stage of project when the

theoretical design is tuned into practical system. The main stages in the
implementation are as follows:

 Planning
 Training
 System testing and
 Changeover Planning
 Planning is the first task in the system implementation. Planning means
deciding on the method and the time scale to be adopted. At the time of
implementation of any system people from different departments and system
analysis involve. They are confirmed to practical problem of controlling
various activities of people outside their own data processing departments.
The line managers controlled through an implementation coordinating
committee. The committee considers ideas, problems and complaints of user
department, it must also consider;

 The implication of system environment

 Self selection and allocation form implementation tasks
 Consultation with unions and resources available
 Standby facilities and channels of communication
The following roles are involved in carrying out the processes of this
phase. Detailed descriptions of these roles can be found in the Introductions
to Sections I and III.

_ Project Manager

_ Project Sponsor

_ Business Analyst

_ Data/Process Modeler

_ Technical Lead/Architect

_ Application Developers

_ Software Quality Assurance (SQA) Lead

_ Technical Services (HW/SW, LAN/WAN, TelCom)

 _ Information Security Officer (ISO)

_ Technical Support (Help Desk, Documentation, Trainers)

_ Customer Decision-Maker

_ Customer Representative

_ Consumer

The purpose of Prepare for System Implementation is to take all

possible steps to ensure that the upcoming system deployment and transition
occurs smoothly, efficiently, and flawlessly. In the implementation of any
new system, it is necessary to ensure that the Consumer community is best
positioned to utilize the system once deployment efforts have been validated.
Therefore, all necessary training activities must be scheduled and
coordinated. As this training is often the first exposure to the system for
many individuals, it should be conducted as professionally and competently
as possible. A positive training experience is a great first step towards
Customer acceptance of the system.

During System Implementation it is essential that everyone involved

be absolutely synchronized with the deployment plan and with each other.
Often the performance of deployment efforts impacts many of the
Performing Organization’s normal business operations. Examples of these
impacts include:

_ Consumers may experience a period of time in which the systems that they
depend on to perform their jobs are temporarily unavailable to them. They
may be asked to maintain detailed manual records or logs of business
functions that they perform to be entered into the new system once it is
operational.

_ Technical Services personnel may be required to assume significant

implementation responsibilities while at the same time having to continue
current levels of service on other critical business systems.

_ Technical Support personnel may experience unusually high

volumes of support requests due to the possible disruption of day-to-day
processing.

Because of these and other impacts, the communication of planned

deployment activities to all parties involved in the project is critical. A
smooth deployment requires strong leadership, planning, and
communications. By this point in the project lifecycle, the team will have
spent countless hours devising and refining the steps to be followed. During
this preparation process the Project Manager must verify that all conditions
that must be met prior to initiating deployment activities have been met, and
that the final ‘green light’ is on for the team to proceed. The final process
within the System Development Lifecycle is to transition ownership of the
system support responsibilities to the Performing Organization. In order for
there to be an efficient and effective transition, the Project Manager should
make sure that all involved parties are aware of the transition plan, the
timing of the various transition activities, and their role in its execution.

Due to the number of project participants in this phase of the SDLC,

many of the necessary conditions and activities may be beyond the direct
control of the Project Manager. Consequently, all Project Team members
with roles in the implementation efforts must understand the plan,
acknowledge their responsibilities, recognize the extent to which other
implementation efforts are dependent upon them, and confirm their
commitment.

SYSTEM TESTING

System testing of software is testing conducted on a complete,

integrated system to evaluate the system's compliance with its specified
requirements. System testing falls within the scope of black box testing, and
as such, should require no knowledge of the inner design of the code or
logic.

As a rule, system testing takes, as its input, all of the "integrated"

software components that have successfully passed integration testing and
also the software system itself integrated with any applicable hardware
system(s). The purpose of integration testing is to detect any inconsistencies
between the software units that are integrated together (called assemblages)
or between any of the assemblages and the hardware. System testing is a
more limiting type of testing; it seeks to detect defects both within the "inter-
assemblages" and also within the system as a whole.

UNIT TEST

The first test in the development process is the unit test. The source
code is normally divided into modules, which in turn are divided into
smaller units called units. These units have specific behavior. The test done
on these units of code is called unit test. Unit test depends upon the language
on which the project is developed. Unit tests ensure that each unique path of
the project performs accurately to the documented specifications and
contains clearly defined inputs and expected results.

SYSTEM TEST

Several modules constitute a project. If the project is long-term

project, several developers write the modules. Once all the modules are
integrated, several errors may arise. The testing done at this stage is called
system test.

System testing ensures that the entire integrated software system

meets requirements. It tests a configuration to ensure known and predictable
results. System testing is based on process descriptions and flows,
emphasizing pre-driven process links and integration points.

FUNCTIONAL TEST

Functional test can be defined as testing two or more modules

together with the intent of finding defects, demonstrating that defects are not
present, verifying that the module performs its intended functions as stated
in the specification and establishing confidence that a program does what it
is supposed to do.
ACCEPTANCE TESTING

Testing the system with the intent of confirming readiness of the

product and customer acceptance.

VALIDATION TESTING

Software validation is achieved through a serious of testes that

demonstrate conformity with requirements. Thus the proposed system under
consideration has been tested by validation & found to be working
satisfactory.

INTEGRATED TESTING

Integrated testing is a systematic technique for constructing tests to

uncover errors associated with interface.

Objective is to take unit tested modules and build a program structure

that has been dictated by design.

SYSTEM MAINTENANCE

All system is dynamic and subjects to constantly changing

requirements. Effort must be devoted to adapting them and design must be
flexible specified so that such changes can be easily implemented. This
activity is called system maintains. It includes improvement of system
functions and correction of errors.
 Back up for the entire database files are taken and stored in secondary
storage devices like magnetic tapes and disks so that is possible to restore
the system at the earliest. If there is a breakdown or collapse, then the
system gives provision to restore database files. Storing data in a separate
secondary device leads to an effective and efficient maintains of the system.

The master file has flags for maintains. After the mentioned period,
the rejection suppliers, unused data in the files will be deleted in the master
file. This method is the increasing the memory to store the data.

SCOPE OF FUTURE ENHANCEMENTS

Nothing will be useful until it is update & enhanced timely just like IT
field. In such a way that this software can have more future enhancement
such as

 Authentication on administrator side can be moved over to

biometrics for more secure access
 Database used has limited storage, Which can be switched
to SQL etc
 Virtual auction can be enabled through web cams.
 Virtual reality for the products can be achieved with the
development of technology
 It can be enhanced according to the client user friendliness
  Can be enhanced with blogs in future for tie up with
different organization.
 Further the remote monitoring can be done for this project.

CONCLUSION

The “” has been developed to satisfy all proposed requirements. The

system is highly scalable and user friendly. Almost all the system objectives
have been met. The system has been tested under all criteria. The system
minimizes the problem arising in the existing manual system and it
eliminates the human errors to zero level. The design of the database is
flexible ensuring that the system can be implemented. It is implemented and
gone through all validation.

All phases of development were conceived using methodologies. User

with little training can get the required report. The software executes
successfully by fulfilling the objectives of the project. Further extensions to
this system can be made required with minor modifications.

BIBLIOGRAPHY
1.Elias Awath, “SYSTEM ANALYSIS AND DESIGN”,Tata Mc Graw
Hill Publication, Sixth Edition,2003

2.S.Ramachandran,”COMPUTER AIDED DESIGN”, Air Walk

Publication, Third Edition,2003
3.Richard Fairley,”SOFTWARE ENGINEERING CONCEPTS”,Tata Mc
Graw Hill Publication, Second Edition,1997

4.Alan Elisaon Ray Halarkey,”VISUAL BASIC 6.0 ENVIRONMENT,

PROGRAMMING AND APPLICATION”.

5.PKMC Bride ,”PROGRAMMING IN VISUAL BASIC”,RBP

Publication 1999.

6.Roger s. Pressman,” SOFTWARE ENGINEERING” Fifth Edition,Mc

Graw-Hill Publications.

7.Bipin Desai C,”INTRODUCTION TO DATABASE SYSTEM”, Third

Edition,Wert Publication Company,1996s