New Microsoft Office Word Document

TABLE OF CONTENTS
Serial no. Description Page no.

1 ACKNOWLEDGEMENTS- 6
2 OBJECTIVE 7
3 INTRODUCTION 8
4 SYSTEM ANALYSIS 10
4.1 IDENTIFICATION OF NEED 11
4.2 PRILIMINARY INVESTIGATION 12
5 FEASIBILITY STUDY 13
5.1 TECHNICAL FEASIBILITY 13
5.2 ECONOMICAL FEASIBILITY 13
5.3 OPERATIONAL FEASIBILITY 13
6 SOFTWARE PARADIGM 14
6.1 CODE AND FIX LIFE CYCLE MODEL 15
6.2 WATERFALL MODEL 16
6.3 THE PROTOTYPING MODEL 17
6.4 THE SPIRAL MODEL 19
7 S/W AND H/W REQUIREMENT SPECIFICATION 20
7.1 SOFTWARE REQUIREMENT 20
7.2 HARDWARE REQUIREMENT 20
8 SYSTEM DESIGN 21
9 TECHNOLOGY USED 23
9.1 INTRODUCTION ON .NET 24
9.2 FEATURES OF .NET 25
10 SOURCE CODE 28
11 CODE OPTIMIZATION 50
12 IMPLEMENTATION AND MAINTENANCE 51
12.1 IMPLEMENTATION 52
12.2 MAINTENANCE 52
13 TESTING 53
14 VALIDATION CHECK 57
15 PERT CHART AND GANTT CHART 60
15.1 PERT CHART 62
15.2 GANTT CHART 64
16 CONCLUSION 65
17 BIBLIOGRAPY 66
ABSTRACT
The project will manage the overall records of the Digital

Diary .In our project we eliminate all the database problems of
managing all type of records of the college.The our main objective of
our system is to improved access time, Improved reliability , Improved
Interface , Easy Access of the database.
The project will store, record of the students , record of the
faculty, records of the library, record of the management.The main
objective of the project is to manage data of the college with required
security.The security would be like Administrator level, user level.
1. ACKNOWLEDGMENT
It required great deal of patience and hard work to compile

this project report and it would not have been possible without the
guidance and support of some very important people. I would like to
express my thanks to my guide Mr. shriram sharma, Asst. Professor of
Computer Science Department, for his help. His attitude toward
excellence in research and his enthusiasm has been source of constant
inspiration. I am grateful to him for all the advice, encouragement and
support he has given us during our work with him, without which this
endeavor would not be as structured as it is now.
I would also like to thank HOD of Computer Department, Mr. rajkumar
sain in C.S. Dept. for their help and support.
Last but not the least I am also thankful to my friends without
whom my successful completion of the report would not have been
possible.
Irfan khan
2. Objectives
DIGITAL DIARY is an important tool for any person whether that

person is an employer or an employee or a secretary, or a housewife, or
even a school going kid. everybody requires a medium to store some
useful day to day information and to retrieve it on some later stage.
Providing employees with usable tools to maintain the records is

paramount task.
DIGITAL DIARY is built to deliver better record maintenance services

by maintaining a database of “clients” related information in the address
book and daily schedules in the “task scheduler” of an employee ,along
with a semi-scientific calculator meant to make calculations much
easier.
3. INTRODUCTION
The project will manage the overall records of the Digital

Diary .In our project we eliminate all the database problems of
managing all type of records of the college.The our main objective of
our system is to improved access time, Improved reliability , Improved
Interface , Easy Access of the database.
The project will store, record of the students , record of the
faculty, records of the library, record of the management.The main
objective of the project is to manage data of the college with required
security.The security would be like Administrator level, user level.
Key Features Include

 Adding New record
 Updating the record
 Searching of record
 Deleting the record
Managing The Data
The fundamental building blocks to cargo revenue maximization
begin with sufficient, reliable and accessible data. Full air waybill
capture is a good starting point. The waybill history should be stored in
an accessible format in a database that can be updated daily.
The real challenge is not just to capture the complete life cycle of a
shipment from original booking through to invoicing, but to do so in a
dynamic and timely way. With new developments in data handling and
communications, it is now possible to build a data warehouse that
receives seamless, real time updates from reservation systems and with
minimal changes to existing systems.
Unconstrained Demand
Shipment dimensions cannot be given accurately at the time the booking
request is made. Often the actual dimensions received at tender do not
anyway become part of any permanent record. Since flights will reach
their volume limitations before they hit weight limits on some sectors,
some heuristic calculation, such as a density code, is needed to forecast
likely volumes. The first step is to use historic data to gauge the total
market demand regardless of the airline’s available capacity. This
unconstrained demand is set for each product type by origin and
destination (O&D), day of week, time of day.
Most cargo customers, unlike passengers, are more concerned with
speed and reliability than with routings. That gives the cargo carrier an
opportunity to route shipments away from congested bottlenecks and
give a better spread of revenues across the network.
For example, a booking request comes through the reservation
center to ship between a hub airport and major destination. The route is
consistently oversold, so the bid rate is high. The router will evaluate
alternative feasible routes which meet both the shipper’s requirements
and the carrier’s business rules.
Removing The Politics
Effectively, the cargo revenue optimization system will allow decisions
to be taken that make optimal use of another, then the choice will not be
made. There will be times when the users override the system’s
decisions, but overall it provides the basis for objective network-wide
decision-making, taking away the guesswork and the politics.
Tools
Front End Visual Studio 2010
Back End Ms Access 2007
4.SYSTEM ANALYSIS
The systems, often prior to their automation as computer

systems, and the interactions within those systems. Identify a better
course of action and make a better decision than he might have
otherwise made.
Identification of the need:
Since the world is growing for globalization, every organization
wants to beat its competitors and want to grow. Enterprise Resourceful
Planning (ERP) is the need of today’s organization. Survival on manual
system is difficult so, that’s why organization of the corporate world
wants to computerize their departments. The modules should be
complete database driven and interactive that should provide the proper
information about the Placement and Training Organization.
Analysis is a phase in which the requirements for the new system

are identified. System analysis is a detailed study of the various
operations performed by a system and their relationship within and
outside of the system. The question is: what must be done to solve the
problem? One aspect of analysis is defining the boundaries of the system
and determining whether or not a candidate system should consider
other related system. During analysis data are collected on the available
files, decision points and transactions handled by the parent system.
Data flow diagram, interviews, onsite observations, questionnaires are
used as a logical system model and tools to perform the analysis.
Tasks, which are performed as analyst:
 Gathered all facts about the present system from the

database.
 Studied strength and weakness of the current system.
 Determined “what” must be done to solve the problem.
 Prepared a functional specifications document.
In order to reduce the time, there is a need for computerized system
that cans retrieve data, insert data, update existing data or delete
existing data. These modules are developed wit the aim of reducing
time, reducing manpower, reducing cost so that the records can be
easily maintained. The volume of work and complexity are increasing
year by year. This system reduces complexity and workload.
Preliminary Investigation:
A request to take assistance from information system can be made
for many reasons, but in each case some one in the organization
initiate the request. When the request is made, the first system activity
the preliminary investigation begins. This activity has three parts:
 Request clarification
 Feasible Study
 Request approval
Many requests from employees and users in the organization are
not clearly defined. Therefore, it becomes necessary that project
request must be examined and clarified properly before considering
systems investigation.
The feasibility study is carried out by a small group of people who are
familiar with information system techniques, understand the parts of the
business or organization that will be involved or affected by the project,
and are skilled in the system analysis and design process.
Request Approval: It is not necessary that all request projects are

desirable or feasible. Some organizations receive so many projects
request from employees that only a few of them can be purchased.
However, those projects that are feasible and desirable should be put
into a schedule. In some cases, development can start immediately,
although usually system staff members are busy on other ongoing
projects. When such situation arises, management decides which
projects are more urgent and schedule them accordingly. Later on, when
the other projects have been completed, the proposed application
development can be initiated.
Analysis is a process of studying a problem and to find the best
solution to that problem. System analysis gives us the target for the
design and the implementation. Analysis is one phase, which is
important phase for system development life cycle. System development
is a problem solving techniques. Analysis involves interviewing the
client and the user. The people and the existing documents about the
current mode of operation are the basic source of information for the
analyst.
5. Feasibility study
A feasibility study is an evaluation of a proposal designed to

determine the difficulty in carrying out a designated task. Generally, a
feasibility study precedes technical development and project
implementation.
Technology and system feasibility:
The assessment is based on an outline design of system

requirements in terms of Input, Processes, Output, Fields, Programs, and
Procedures. This can be quantified in terms of volumes of data, trends,
frequency of updating, etc. in order to estimate whether the new system
will perform adequately or not. This means that feasibility is the study of
the based in outline.
Economic feasibility:
Economic analysis is the most frequently used method for

evaluating the effectiveness of a new system. More commonly known as
cost/benefit analysis, the procedure is to determine the benefits and
savings that are expected from a candidate system and compare them
with costs. If benefits outweigh costs, then the decision is made to
design and implement the system. An entrepreneur must accurately
weigh the cost versus benefits before taking an action.
Cost Based Study: It is important to identify cost and benefit factors.
Cost and benefits can be categorized into the following categories.
Basically it is an analysis of the costs to be incurred in the system and
benefits derivable out of the system. In a broad sense the costs can be
divided into two types
1. Development costs
2. Operating costs
Time Based Study: Contrast to the manual system management can

generate any report just by single click .
Legal feasibility
Determines whether the proposed system conflicts with legal

requirements, e.g. a data processing system must comply with the local
Data Protection Acts.
Operational feasibility
Is a measure of how well a proposed system solves the problems, and

takes advantages of the opportunities identified during scope definition
and how it satisfies the requirements identified in the requirements
analysis phase of system development.
6. Software Paradigm
To solve actual problems in a software project setting, a
software engineer or a team of engineers must incorporate a
development strategy that includes methods, tools and
procedures. This strategy is referred to as a process model or a
software engineering paradigm.
There are several such paradigms available. Which

software paradigm is more suitable depends on lot of factors
such as:
1. Nature of the Project

2. Type of Applications
3. Tools proposed to be used
4. Kind of controls and documentation required
6.1 Code And Fix Life Cycle Model :
As the name suggests, this model uses an adhoc

approach for the software designing. A very casual study is
followed by coding. The issues regarding specification or
design are never addressed. Instead, the developers simply build
a product that is re-build again and again until the customer is
satisfied.
6.1.1 Limitations of code-and-fix cycle model :
This approach may work well for small systems but is very
unsatisfactory for larger systems. As the code size increases, the
understandability and maintainability of the system decreases.
6.2 The Waterfall Model/Linear Sequential Life Cycle

Model :
The simplest, oldest and most widely used process model for
software designing is the waterfall model. It was proposed by
Royce in 1970.
The essence of this software paradigm is that the process of
software designing consists of linear set of distinct phases.
These phases are:
Stage1: Feasibility Study

The goal of feasibility study is to evaluate alternative systems
and to purpose the most feasible and desirable system for
designing. Five types of feasibility are addressed in this study.
1. Technical feasibility
2. Economic Feasibility
3. Motivational Feasibility
4. Schedule Feasibility
5. Operational Feasibility
Stage2: Requirement Analysis and Specification
The goal of this phase is to understand the exact requirements of

the customers and to document them properly. This activity is
usually executed together with the customers, as the goal is to
document all functions, performance and interfacing
requirements for the software designing and management. The
requirements describe “what” of a system. This phase produces
a large document containing a description of what the system
will do without describing how it will be done. This document is
known as software requirement specification (SRS) document.
Stage3: Design
The goal of this phase is to transform the requirement

specification produced in the requirement analysis phase into a
structure that is suitable for implementation in some
programming language, Here, overall software architecture is
defined, and the product design and detailed design work is
performed. This work is documented and is known as software
design description (SDD document).
Stage4: Coding and Unit Testing
The information contained in SDD is sufficient to begin the

coding Phase. The coding Phase of software designing involves
translation of design specification into a machine readable form.
If design is performed in a detailed manner, code generation can
be accomplished easily. This phase is also known as the
implementation phase. Here, each component of the design is
implemented as a program module, and each of these program
modules is unit tested. The purpose of unit testing is to
determine the correct working of individual modules.
Stage5: Integration and System Testing:
During this phase the different program modules are integrated

in a planned way and then tested as a completed system to
ensure that the designed system functions according to its
requirements as specified in the SRS document. After testing,
the software is delivered to the customer.
Stage6: Software Maintenance
This is the last phase of software designing which includes a

broad set of activities such as error correction, enhancement of
capabilities, deletion of obsolete capabilities and optimization.
Advantages
1. Simple and easy to use

2. Easily manageable
3. The phase of the model are processed and completed one at a
time.
4. Works very well for smaller software projects.
Disadvantages
1. It is often difficult for the customer to state all the

requirements explicitly.
2. Real projects rarely follow the sequential flow that the
software model proposes.
3. The customer must have patience, as the product is delivered
very late in this software process.
4. The model is not suitable for long time software projects.
6.3 The Prototyping Model :
Prototyping is a technique that provides a reduced functionality

or limited performance version of the eventual software to be
delivered to the user in the early stages of the software
development process. If used judiciously, this approach helps to
solidify user requirements earlier, thereby making the waterfall
approach more effective.
What is done is that before proceeding with design and coding, a
throw away prototype is built to give user a feel of the system.
The development of the software prototype also involves design
and coding, but this is not done in a formal manner. The user
interacts with the prototype as he would do with the eventual
system and would therefore be in a better position to specify his
requirements in a more detailed manner. The iterations occur to
refine the prototype to satisfy the needs of the user, while at the
same time enabling the developer to better understand what
needs to be done.
Disadvantages
1. In prototyping, as the prototype has to be discarded, so

might argue that the cost involved is higher.
2. At times, while designing a prototype, the approach
adopted is “quick and dirty” with the focus on quick
development rather than quality.
3. The developer often makes implementation compromises
in order to get a prototype working quickly.
6.4 The Spiral Model :
This model proposed by Barry Bohem in 1988, attempts to combine the

strengths of various models. It incorporates the elements of the prototype
driven approach along with the classic software life cycle. Is also takes
into account the risk assessment whose outcome determines taking up
the next phase of the designing activity.
Unlike all other models which view designing as a linear process, this
model views it as a spiral process. This is done by representing iterative
designing cycles as an expanding spiral.
Typically the inner cycles represent the early phase of requirement
analysis along with prototyping to refine the requirement definition, and
the outer spirals are progressively representative of the classic software
designing life cycle.
At every spiral there is a risk assessment phase to evaluate the designing
efforts and the associated risk involved for that particular iteration. At
the end of each spiral there is a review phase so that the current spiral
can be reviewed and the next phase can be planned.
Six major activities of each designing spirals are represented by six

major tasks:
1. Customer Communication
2. Planning
3. Risk Analysis
4. Software Designing Engineering
5. Construction and Release
6. Customer Evolution
Advantages
1. It facilities high amount of risk analysis.

2. This software designing model is more suitable for designing and
managing large software projects.
3. The software is produced early in the software life cycle.
Disadvantages
1. Risk analysis requires high expertise.

2. It is costly model to use
3. Not suitable for smaller projects.
4. There is a lack of explicit process guidance in determining objectives,
constraints and alternatives..
5. This model is relatively new. It does not have many practioners unlike
the waterfall model or prototyping model.
Software and Hardware Requirements
7.1 Minimum Software requirements are:
 OPERATING SYSTEM: Windows 9X/2000/XP
 FRONT END: MS Visual studio 2010
 VB
 VS.NET
 Microsoft Access 2007
 DESIGNING TOOL: Visual Studio Tools
7.2 Minimum Hardware requirements are:
 A Computer System with Configuration:

 Pentium-IV or equivalent processor or all higher processors.
 512 RAM.
 20GB of memory.
8. System Design
System Design develops the architectural detail required to build a
system or product. The system design process encompasses the
following activities :
 Partition the analysis model into sub systems
 Identify concurrency i.e. dictated by the problem.
 Allocates subsystems to processors and task.
 Develop a design for the user interface.
 Choose a basic strategy for implementing data management.
 Identify globlal resources and the control mechanism required to
access them.
 Design an appropriate control mechanism for the system,including
task management.
 Consider how boundary conditions should be handled.
 Review and consider trade offs .
PARTIONING THE ANALYSIS MODEL

All the elements of a sub system shares some property in
common.They all may be involved in accomplishing the same function;
they may reside within the same product hardware,or they may manage
the same class of resources.
As subsystems are defined , they should confirm to the following design
criteria:
 The subsystem should have a well defined interface through which
all communication with the rest of the system occurs.
 The number of subsystems should be kept low.
 Asubsystem can be partitioned internally to help reduce
complexity.
 With the exception of a small number of communication classes.
The classes with in a subsystem should collaborate only with other
classes with in the subsystem.
CONCURRENCY AND SUBSYSTEM ALLOCATION
The dynamic aspect of the object-behavior model provides an
indication of concurrency among classes.if classes are not active at the
same time,there is no need for concurrent processing. This mean that the
classes can be implemented on the same processor hardware. When sub
system are concurrent, to allocation options accessed.
 Allocated each sub system to an independent procesors.

 Allocate the sub system to the same processor and provide
concurrentely support through operating system processors.
Concurrent task are defined by examining the state diagram for
each object. to determine which of the processor allocation option is
appropriate, the designer must consider performance requirement, cost
and the overhead imposed by the inter process communication.
THE TASK MANAGEMENT COMPOMENT
The strategy for the design of the object that manage concurrent task are
as follows:
 The characteristics of the task can be determined.

 A codinator task and associated object are define.
 The codinator and other task are integrated.
The characteristics of a task are determined by understanding how the

task is initiated event driven and clock driven task are the most
commonly encountered.
USER INTERFACE COMPOMENT
Although the user interface compoment has been implemented with

in the context of the problem domain. The interface itself represent
criticallity important subsystem foe most modern application. object
oriented analysis model contains usage scenarios and description of the
rule that user plays as they interact with the system. The command
hierarchy are refined iteratively until every use case can be implemented
by navigating the hierarchy of functions.
THE DATA MANAGEMENT COMPONENT
Data management encompasses two distinct areas of concern:

1. The management of data that are critical to the application itself
2. The criteria of an infrastructure for storage and retrieval of objects.
Within the system context, a database management system is

often used as a common data store for all subsystems.The objects
required to manipulate the database are members of reusable
classes that are identified using domain analysis or are supplied
directly by the database vendor.
The design of the data management component includes the

design of the attributes and operations required to manage
objects.the relevant attributes are appended to every object in the
problem domain and provide information that answers the
question,”How do I store myself?” coad and Yourdon suggest the
creation of an object-server class” with services to tell each object
to save itself and retrieve stored objects for use by other design
components.
THE RESOURCE MANAGEMENT COMPONENT
A variety of different resources are available to an OO system

or product; and in many instances, sub systems can be external
entities. regardless of the nature of the resource, of the software
engineer should design a control mechanism for it.
9. Technology
The Microsoft .NET Framework is a software framework that can be

installed on computers running Microsoft Windows operating systems. It
includes a large library of coded solutions to common programming
problems and a virtual machine that manages the execution of programs
written specifically for the framework. The .NET Framework is a
Microsoft offering and is intended to be used by most new applications
created for the Windows platform.
The framework's Base Class Library provides a large range of features

including user interface, data access, database connectivity,
cryptography, web application development, numeric algorithms, and
network communications. The class library is used by programmers,
who combine it with their own code to produce applications.
Programs written for the .NET Framework execute in a software

environment that manages the program's runtime requirements. Also
part of the .NET Framework, this runtime environment is known as the
Common Language Runtime (CLR). The CLR provides the appearance
of an application virtual machine so that programmers need not consider
the capabilities of the specific CPU that will execute the program.
Common Language Infrastructure (CLI)
Common Language Infrastructure:
The purpose of the Common Language Infrastructure, or CLI, is to

provide a language-neutral platform for application development and
execution, including functions for exception handling, garbage
collection, security and interoperability. By implementing the core
aspects of the .NET Framework within the scope of the CLI, this
functionality will not be tied to a single language but will be available
across the many languages supported by the framework. Microsoft's
implementation of the CLI is called the Common Language Runtime or
CLR.
Metadata
All CIL is self-describing through .NET metadata. The CLR checks the
metadata to ensure that the correct method is called. Metadata is usually
generated by language compilers but developers can create their own
metadata through custom attributes. Metadata contains information
about the assembly, and is also used to implement the reflective
programming capabilities of .NET Framework.
Security
.NET has its own security mechanism with two general features: Code
Access Security (CAS), and validation and verification.
When an assembly is loaded the CLR performs various tests. Two such
tests are validation and verification. During validation the CLR checks
that the assembly contains valid metadata and CIL, and whether the
internal tables are correct. Verification is not so exact. The verification
mechanism checks to see if the code does anything that is 'unsafe'. ..NET
Framework uses AppDomains as a mechanism for isolating code
running in a process. AppDomains can be created and code loaded into
or unloaded from them independent of other AppDomains. This helps
increase the fault tolerance of the application, as faults or crashes in one
AppDomains do not affect rest of the application
Class library
Namespaces in the BCL
System.Data.OleDB
System. CodeDom
System. Collections
System. Diagnostics
System. Globalization
System. IO
System. Resources
System. Text
System. Text.RegularExpressions
See also: Base Class Library and Framework Class Library
The .NET Framework includes a set of standard class libraries. The class
library is organized in a hierarchy of namespaces. Most of the built in
APIs are part of either System.* or Microsoft.* namespaces. These class
libraries implement a large number of common functions, such as file
reading and writing, graphic rendering, database interaction, and XML
document manipulation, among others. The .NET class libraries are
available to all .NET languages. The .NET Framework class library is
divided into two parts: the Base Class Library and the Framework Class
Library.
The Base Class Library (BCL) includes a small subset of the entire
class library and is the core set of classes that serve as the basic API of
the Common Language Runtime.[9] The classes in mscorlib.dll and some
of the classes in System.dll and System.core.dll are considered to be a
part of the BCL. The BCL classes are available in both .NET
Framework as well as its alternative implementations including .NET
Compact Framework, Microsoft Silverlight and Mono.
The Framework Class Library (FCL) is a superset of the BCL classes

and refers to the entire class library that ships with .NET Framework. It
includes an expanded set of libraries, including WinForms, ADO.NET,
ASP.NET, Language Integrated Query, Windows Presentation
Foundation, Windows Communication Foundation among others. The
FCL is much larger in scope than standard libraries for languages like
C++, and comparable in scope to the standard libraries of Java.
Memory management
The .NET Framework CLR frees the developer from the burden of
managing memory (allocating and freeing up when done); instead it
does the memory management itself. To this end, the memory allocated
to instantiations of .NET types (objects) is done contiguously[10] from
the managed heap, a pool of memory managed by the CLR. As long as
there exists a reference to an object, which might be either a direct
reference to an object or via a graph of objects, the object is considered
to be in use by the CLR. When there is no refb erence to an object, and it
cannot be reached or used, it becomes garbage. However, it still holds on
to the memory allocated to it. .NET Framework includes a garbage
collector which runs periodically, on a separate thread from the
application's thread, that enumerates all the unusable objects and
reclaims the memory allocated to them.
The .NET Garbage Collector (GC) is a non-deterministic, compacting,

mark-and-sweep garbage collector. The GC runs only when a certain
amount of memory has been used or there is enough pressure for
memory on the system. Since it is not guaranteed when the conditions to
reclaim memory are reached, the GC runs are non-deterministic. Each
.NET application has a set of roots, which are pointers to objects on the
managed heap (managed objects). These include references to static
objects and objects defined as local variables or method parameters
currently in scope, as well as objects refers.
SnapShots--
Coding----
Imports System.Data
Imports System.Data.OleDb
Public Class Form5
Dim mycn As New OleDbConnection
Dim mycm As New OleDbCommand
Dim myad As New OleDbDataAdapter
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button2.Click
Me.Close()
End Sub

mycn.ConnectionString = "provider=microsoft.jet.oledb.4.0;Data
Source=|datadirectory|avdesh.mdb"
mycn.Open()
mycm.Connection = mycn
Try
mycm.CommandText = "insert into login values('" & (TextBox1.Text) & "
',' " & (TextBox2.Text) & " ' ,' " & (TextBox4.Text) & " ' ,' " & (TextBox5.Text) &
" ' )"
myad.InsertCommand = mycm
myad.InsertCommand.ExecuteNonQuery()
Catch ex As Exception
MsgBox("Username Already Exists try with Diferent one")
End Try
mycn.Close()
' Dim reg As String

' Try
'reg = Val(InputBox("Enter the Student Registration No:"))

'TextBox1.Text = reg
' mycn.ConnectionString = "provider=microsoft.jet.oledb.4.0;Data
' mycn.Open()
' mycm.Connection = mycn
' mycm.CommandText = "Delete * from login where uname=" &
(TextBox1.Text) & ""
' myad.DeleteCommand = mycm
' myad.DeleteCommand.ExecuteNonQuery()
' MsgBox("Record deleted successfully")
End Sub
End Class
Imports System.Data
Public Class Form2
Me.Close()
End Sub

If Not TextBox2.Text = TextBox3.Text Then
MsgBox("Password not Matched")
Else
mycn.Open()
' Try
" ' )"
' Catch ex As Exception
' MsgBox("Username Already Exists try with Diferent one")
' End Try
mycn.Close()
End If
End Sub
End Class
Imports System.Data
Public Class Form1


End
End Sub
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load
'TODO: This line of code loads data into the 'AvdeshDataSet1.login' table.
You can move, or remove it, as needed.
Me.LoginTableAdapter.Fill(Me.AvdeshDataSet1.login)
'TODO: This line of code loads data into the 'AvdeshDataSet.user' table. You
can move, or remove it, as needed.
End Sub

mycn.Open()
mycm.CommandText = "select * from login where uname='" &
(ComboBox1.Text) & " ' "
myad.SelectCommand = mycm
Dim ds As New DataSet
myad.Fill(ds, "newtab")
Dim r As DataRow
If ds.Tables("newtab").Rows.Count = 0 Then
MsgBox("Username Incorrect")
Else
r = ds.Tables("newtab").Rows(0)
If TextBox1.Text = r("pass") Then
' form2.show()
Else
MsgBox("Password Incorrect")
End If
End If
mycn.Close()
' Dim reg As String

' Try

' mycn.Open()
End Sub

Form2.Show()
End Sub
End Class
Public Class Form3

' copying style 1 RichTextBox2.Rtf = RichTextBox1.Rtf
' RichTextBox1.SaveFile("avdeshyadav.txt")
OpenFileDialog1.Filter = "All Files(*.*)|*.*"

OpenFileDialog1.FilterIndex = 2
OpenFileDialog1.ShowDialog()
If (OpenFileDialog1.ShowDialog = Windows.Forms.DialogResult.OK) Then
'RichTextBox1.AppendText("New.txt")
'if(OpenFileDialog1.FileName.ToString())
Dim str As String
str = OpenFileDialog1.FileName
RichTextBox1.LoadFile(str)
OpenFileDialog1.OpenFile()
End If
End Sub
'Dim stri As String
'stri = InputBox("Enter the file name:")
RichTextBox1.SaveFile(TextBox3.Text)
End Sub

' OpenFileDialog1.Filter = "BMP Files(*.bmp)|*.bmp|GIF
Files(*.gif)|*.gif|JPEG Files(*.jpg)|*.jpg)"
' OpenFileDialog1.FilterIndex = 1
' If (OpenFileDialog1.ShowDialog <>
Windows.Forms.DialogResult.Cancel) Then
' PictureBox1.Image = Image.FromFile(OpenFileDialog1.FileName)
' End If
End Sub
' Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As

'Dim fom As Integer
' fom = Val(ComboBox1.Text)
' FontDialog1.ShowColor = True

' FontDialog1.ShowDialog()
' If RichTextBox1.TextLength <> 0 Then
' If FontDialog1.ShowDialog <> Windows.Forms.DialogResult.Cancel Then
' RichTextBox1.SelectionColor = FontDialog1.Color
' End If
' End If
' End Sub

If Not TextBox2.Text = TextBox3.Text Then
MsgBox("Password not Matched")
Else
mycn.Open()
' Try
" ' )"
' Catch ex As Exception
' MsgBox("Username Already Exists try with Diferent one")
' End Try
mycn.Close()
End If
End Sub
End Class
Imports System.Data
Public Class Form1


End
End Sub
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load
'TODO: This line of code loads data into the 'AvdeshDataSet1.login' table.
You can move, or remove it, as needed.
Me.LoginTableAdapter.Fill(Me.AvdeshDataSet1.login)
'TODO: This line of code loads data into the 'AvdeshDataSet.user' table. You
can move, or remove it, as needed.
End Sub

mycn.Open()
mycm.CommandText = "select * from login where uname='" &
(ComboBox1.Text) & " ' "
myad.SelectCommand = mycm
Dim ds As New DataSet
myad.Fill(ds, "newtab")
Dim r As DataRow
If ds.Tables("newtab").Rows.Count = 0 Then
MsgBox("Username Incorrect")
Else
r = ds.Tables("newtab").Rows(0)
If TextBox1.Text = r("pass") Then
' form2.show()
Else
MsgBox("Password Incorrect")
End If
End If
mycn.Close()
' Dim reg As String

' Try
' mycn.Open()
End Sub

Form2.Show()
End Sub
End Class
Public Class Form3

' copying style 1 RichTextBox2.Rtf = RichTextBox1.Rtf
' RichTextBox1.SaveFile("avdeshyadav.txt")
OpenFileDialog1.Filter = "All Files(*.*)|*.*"

OpenFileDialog1.FilterIndex = 2
OpenFileDialog1.ShowDialog()
If (OpenFileDialog1.ShowDialog = Windows.Forms.DialogResult.OK) Then
'RichTextBox1.AppendText("New.txt")
'if(OpenFileDialog1.FileName.ToString())
Dim str As String
str = OpenFileDialog1.FileName
RichTextBox1.LoadFile(str)
OpenFileDialog1.OpenFile()
End If
End Sub

'Dim stri As String
'stri = InputBox("Enter the file name:")
RichTextBox1.SaveFile(TextBox3.Text)
End Sub

' OpenFileDialog1.Filter = "BMP Files(*.bmp)|*.bmp|GIF
Files(*.gif)|*.gif|JPEG Files(*.jpg)|*.jpg)"
' OpenFileDialog1.FilterIndex = 1
' If (OpenFileDialog1.ShowDialog <>
Windows.Forms.DialogResult.Cancel) Then
' PictureBox1.Image = Image.FromFile(OpenFileDialog1.FileName)
' End If
End Sub
' Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As

'Dim fom As Integer
' fom = Val(ComboBox1.Text)
' FontDialog1.ShowColor = True

' FontDialog1.ShowDialog()
' If RichTextBox1.TextLength <> 0 Then
' If FontDialog1.ShowDialog <> Windows.Forms.DialogResult.Cancel Then
' RichTextBox1.SelectionColor = FontDialog1.Color
' End If
' End If
' End Sub

FontDialog1.ShowDialog()
TextBox2.Text = FontDialog1.Font.Name
TextBox1.Text = FontDialog1.Font.Size
ComboBox1.Items.Add(FontDialog1.Font.Name)
RichTextBox1.SelectionFont = FontDialog1.Font()
End Sub

If (ColorDialog1.ShowDialog <> Windows.Forms.DialogResult.Cancel)
Then
RichTextBox1.ForeColor = ColorDialog1.Color
End If
End Sub

Dim boldFont As New Font(RichTextBox1.Font, FontStyle.Bold)
If Not RichTextBox1.Font.Bold = True Then
RichTextBox1.SelectionFont = boldFont
End If
End Sub

Dim italicFont As New Font(RichTextBox1.Font, FontStyle.Italic)
RichTextBox1.SelectionFont = italicFont
End Sub

Dim underFont As New Font(RichTextBox1.Font, FontStyle.Underline)
RichTextBox1.SelectionFont = underFont
End Sub

Form4.Show()
End Sub

Form5.Show()
End Sub
End Class
Public Class Form4

Dim a, b As Double
Dim op As Integer = 0

b = Val(TextBox1.Text)
TextBox1.Text = a * b
End Sub

If Not op = 0 Then
Call perform()
Else
TextBox2.Text = TextBox1.Text
TextBox1.Text = ""
op = 1
TextBox1.Focus()
End If
End Sub
Private Sub MenuStrip1_ItemClicked(ByVal sender As System.Object, ByVal e

As System.Windows.Forms.ToolStripItemClickedEventArgs) Handles
MenuStrip1.ItemClicked
End Sub

TextBox1.AppendText("1")
End Sub

End Sub
Function perform() As Double
a = Val(TextBox1.Text)
b = Val(TextBox2.Text)
If op = 1 Then
TextBox2.Text = a * b
ElseIf op = 2 Then
TextBox2.Text = a + b
ElseIf op = 3 Then
TextBox2.Text = b - a
End If
TextBox1.Text = ""
TextBox1.Focus()
If TextBox2.Text = "" Then
op = 0
End If
Return 0
End Function

End Sub

End Sub

End Sub

End Sub

End Sub

End Sub

End Sub
End Sub

If Not op = 0 Then
Call perform()
Else
TextBox1.Text = ""
op = 2
TextBox1.Focus()
End If
End Sub

If Not op = 0 Then
Call perform()
Else
TextBox1.Text = ""
op = 3
TextBox1.Focus()
End If
End Sub

End Sub
End Class
Imports System.Data
Public Class Form5

Me.Close()
End Sub

mycn.Open()
Try
" ' )"
Catch ex As Exception
MsgBox("Username Already Exists try with Diferent one")
End Try
mycn.Close()
End Class
11. Code Optimization
Program optimization or software optimization is the process of modifying a

software system to make some aspect of it work more efficiently or use fewer
resources. In general, a computer program may be optimized so that it executes
more rapidly, or is capable of operating with less memory storage or other
resources, or draw less power.
Although the word "optimization" shares the same root as "optimal," it is rare for
the process of optimization to produce a truly optimal system. The optimized
system will typically only be optimal in one application or for one audience. One
might reduce the amount of time that a program takes to perform some task at the
price of making it consume more memory. In an application where memory space
is at a premium, one might deliberately choose a slower algorithm in order to use
less memory. Often there is no “one size fits all” design which works well in all
cases, so engineers make trade-offs to optimize the attributes of greatest interest.
Additionally, the effort required to make a piece of software completely optimal—
incapable of any further improvement— is almost always more than is reasonable
for the benefits that would be accrued; so the process of optimization may be
halted before a completely optimal solution has been reached. Fortunately, it is
often the case that the greatest improvements come early in the process.
12. Implementation and Maintenance
12.1 Implementation
A product software implementation method is a systematically structured

approach to effectively integrate a software based service or component into the
workflow of an organizational structure or an individual end-user.
A product software implementation method is a blueprint to get users and/or

organizations running with a specific software product. The method is a set of rules
and views to cope with the most common issues that occur when implementing a
software product: business alignment from the organizational view and acceptance
from the human view.
The implementation of product software, as the final link in the deployment chain
of software production, is in a financial perspective of a major issue.
Implementation complexity differences :
The complexity of implementing product software differs on several issues.

Examples are: the number of end users that will use the product software, the
effects that the implementation has on changes of tasks and responsibilities for the
end user, the culture and the integrity of the organization where the software is
going to be used and the budget available for acquiring product software.
In general, differences are identified on a scale of size (bigger, smaller, more, less).
An example of the “smaller” product software is the implementation of an office
package. However there could be a lot of end users in an organization, the impact
on the tasks and responsibilities of the end users will not be too intense, as the
daily workflow of the end user is not changing significantly. An example of
“larger” product software is the implementation of an Enterprise Resource
Planning system. The implementation requires in-depth insights on the architecture
of the organization as well as of the product itself, before it can be aligned.
Examples of other "larger" product software are:
 Enterprise resource planning software

 Customer relationship management software
 Content management system software
 Human resource management systems
 Supply chain management software
12.2 Maintenance
Software maintenance in software engineering is the modification of a

software product after delivery to correct faults, to improve performance or other
attributes, or to adapt the product to a modified environment .
This international standard describes the 6 software maintenance processes as:
1. The implementation processes contains software preparation and transition

activities, such as the conception and creation of the maintenance plan, the
preparation for handling problems identified during development, and the
follow-up on product configuration management.
2. The problem and modification analysis process, which is executed once the
application has become the responsibility of the maintenance group. The
maintenance programmer must analyze each request, confirm it (by
reproducing the situation) and check its validity, investigate it and propose a
solution, document the request and the solution proposal, and, finally, obtain
all the required authorizations to apply the modifications.
3. The process considering the implementation of the modification itself.
4. The process acceptance of the modification, by checking it with the
individual who submitted the request in order to make sure the modification
provided a solution.
5. The migration process (platform migration, for example) is exceptional, and
is not part of daily maintenance tasks. If the software must be ported to
another platform without any change in functionality, this process will be
used and a maintenance project team is likely to be assigned to this task.
6. Finally, the last maintenance process, also an event which does not occur on
a daily basis, is the retirement of a piece of software.
13.Testing Technology To Be Used
Software Testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. The increasing
visibility of software as a system element and attendant “costs” associated with a
software failure is motivating forces for well-planned, thorough testing.
TESTING OBJECTIVES
Our objective is to design tests that systematically uncover different classes
of error and to do so with minimum amount of time and effort. Data collected, as
testing is conducted provides a good indication of software reliability and quality
as a whole. A successful test is one that uncovers an as yet undiscovered error. A
good test case is one that has a high probability of finding an as yet undiscovered
error.
TESTING APPROACHES
The two strategies we used to test our software are
1. Unit Testing
2. Integration Testing
UNIT TESTING :
Unit testing focuses on verification of the efforts on the smallest unit of
software design-the module. The unit test is always White Box oriented, and the
steps can be conducted in parallel for multiple, modules. In our modules, different
testing at module level is shown above in Test Reports
14.VALIDATION CHECK
INTEGRATION TESTING :
Integration testing addresses the issues associated with the dual problems of
verification and program construction. Black Box test case design techniques are
the most prevalent during integration, although a limited amount of White Box
Testing may be used to ensure coverage of Major control paths.
15. PERT CHART & GANTT CHART
15.1 PERT CHART:
Program Evaluation and Review Technique (PERT) and Critical Path Method
(CPM) are the project scheduling techniques that can be applied to software
development. Both technique are driven by information already gathered in earlier
project planning activities:
 Estimation of effort
 A decomposition of the product function
 The solution of the appropriate model and task set
 Decomposition of tasks
Both PERT and CPM provide quantitative tools that allow the software planning to
determine critical path – the claim of task that determined the duration of the
project establish “most likely” times estimates for individual tasks by applying
statically models: and Calculation “boundary times” that define a time “window”
for a particular task.
Both PERT and CPM have been implemented in a wide verity of automated tools
that are available for the personal computer. Such tools are easy to use and make
the scheduling methods described previously available to every software project
manager.
15.2 GANTT CHART :
When creating a software project schedule, the planner begins with a set of tasks
(the work break down structure). If automated tools are used, the work break down
is input as a task network or task outline. Efforts, duration, and start date are then
input for each task. In addition, task may be assigned to specific individuals.
As a sequence of this input, a timeline chart, also called a Gantt chart, is generated.
A Gantt chart can be developed for the entire project. Alternatively, separated it
depicts a part of a software project schedule that emphasizes the concept scooping
task for a new word processing software project. All project tasks (for concept
scooping) are listed in the left hand column. The horizontal bars occur at the same
time on the calendar, task concurrency is implied. The diamonds indicate
milestones.
Once the information necessary for the generation of the Gantt chart has been
input, the major of software project scheduling tools produce project tables a
tabular listing of all project tasks, their planned and actual start and end dates, and
a verity of related information. Used in conjunction with the Gantt Chart project
tables enable the project manager to track progress.
Task name/weak-> 1 2 3 4 5 6 7 8
|
1.Initial planning
2.Concept generation
3.Project outline
4.Module design
phase1
5.Module design
phase2
6.Module design
phase3
7.Module
development
8.Module integration
9.Testing
10.Documentation
11.Product delivery
CONCLUSION & FUTURE SCOPE
CONCLUSION
The project was aimed at understanding the programming methodology
of VB.NET and it’s versatile programming environment. The report is
aimed to provide a clearer understanding of the .NET Technology,
encompassing and elaborating the various elements of the programming
language. This literature also describes the usage and implementation of
the technology with the application software, supporting distributed
systems and information transfer over the internet securely.
FUTURE SCOPE
.NET Framework is a versatile programming environment supporting numerous

languages at the same time. The learning scope in this field is enormous as
constant exploration and experimentation makes one more proficient with the
platform.
GLOSSARY
CLR Common Language Runtime
MSLR Microsoft Intermediate Language
JIT Just In Time
CLS Common Language Specification
CTS Common Type System
ADO Active Data Object
ASP Active Server Page
EXE Execute File
DLL Dynamic Link Library
GC Garbage Collection
LINQ Language Integrated Query

New Microsoft Office Word Document

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

New Microsoft Office Word Document

Hochgeladen von

Copyright:

Verfügbare Formate

TABLE OF CONTENTS

Serial no. Description Page no.

The project will manage the overall records of the Digital

It required great deal of patience and hard work to compile

DIGITAL DIARY is an important tool for any person whether that

Providing employees with usable tools to maintain the records is

DIGITAL DIARY is built to deliver better record maintenance services

The project will manage the overall records of the Digital

Key Features Include

The systems, often prior to their automation as computer

Analysis is a phase in which the requirements for the new system

Tasks, which are performed as analyst:

 Gathered all facts about the present system from the

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

A feasibility study is an evaluation of a proposal designed to

Technology and system feasibility:

The assessment is based on an outline design of system

Economic analysis is the most frequently used method for

Time Based Study: Contrast to the manual system management can

Determines whether the proposed system conflicts with legal

Is a measure of how well a proposed system solves the problems, and

There are several such paradigms available. Which

1. Nature of the Project

6.1 Code And Fix Life Cycle Model :

As the name suggests, this model uses an adhoc

6.1.1 Limitations of code-and-fix cycle model :

6.2 The Waterfall Model/Linear Sequential Life Cycle

These phases are:

Stage1: Feasibility Study

Stage2: Requirement Analysis and Specification

The goal of this phase is to understand the exact requirements of

The goal of this phase is to transform the requirement

Stage4: Coding and Unit Testing

The information contained in SDD is sufficient to begin the

During this phase the different program modules are integrated

Stage6: Software Maintenance

This is the last phase of software designing which includes a

1. Simple and easy to use

1. It is often difficult for the customer to state all the

6.3 The Prototyping Model :

Prototyping is a technique that provides a reduced functionality

1. In prototyping, as the prototype has to be discarded, so

6.4 The Spiral Model :

This model proposed by Barry Bohem in 1988, attempts to combine the

Six major activities of each designing spirals are represented by six

1. It facilities high amount of risk analysis.

1. Risk analysis requires high expertise.

7.1 Minimum Software requirements are:

 OPERATING SYSTEM: Windows 9X/2000/XP

 FRONT END: MS Visual studio 2010

 A Computer System with Configuration:

PARTIONING THE ANALYSIS MODEL

 Allocated each sub system to an independent procesors.

THE TASK MANAGEMENT COMPOMENT

 The characteristics of the task can be determined.

The characteristics of a task are determined by understanding how the

Although the user interface compoment has been implemented with

THE DATA MANAGEMENT COMPONENT

Data management encompasses two distinct areas of concern:

Within the system context, a database management system is

The design of the data management component includes the

A variety of different resources are available to an OO system

The Microsoft .NET Framework is a software framework that can be

The framework's Base Class Library provides a large range of features

OpenFileDialog1.Filter = "All Files(.)|."

OpenFileDialog1.Filter = "All Files(.)|."