Technology Overview of Project

C# (SHARP), .NET and SDLC of Project

About C#:

C # (pronounced “C sharp”) is the native language for the .NET Common Language
Runtime. It has been designed to fit seamlessly into the .NET Common Language
Runtime. You can (and, at times, you should) write code in either Visual C++ or
Visual Basic, but in most cases, C# will likely fit your needs better. Because the Common
Language Runtime is central to many things in C#, “The .NET Runtime Environment,” will
introduce the important parts of it—at least, those that are important to the C# language. C#
syntax is highly expressive, yet with less than 90 keywords, it is also simple and easy to
learn.
The curly-brace syntax of C# will be instantly recognizable to anyone familiar with C,
C++ or Java. Developers who know any of these languages are typically able to begin
working productively in C# within a very short time. C# syntax simplifies many of the
complexities of C++ while providing powerful features such as nullable value types,
enumerations, delegates, anonymous methods and direct memory access, which are not found
in Java.
C# also supports generic methods and types, which provide increased type safety and
performance, and iterators, which enable implementers of collection classes to define custom
iteration behaviours that are simple to use by client code.
As an object-oriented language, C# supports the concepts of encapsulation,
inheritance and polymorphism. All variables and methods, including the Main method, the
application's entry point, are encapsulated within class definitions. A class may inherit
directly from one parent class, but it may implement any number of interfaces.
Methods that override virtual methods in a parent class require the override keyword
as a way to avoid accidental redefinition. In C#, a struct is like a lightweight class; it is a
stack-allocated type that can implement interfaces but does not support inheritance.
In addition to these basic object-oriented principles, C# facilitates the development of
software components through several innovative language constructs, including:
 Encapsulated method signatures called delegates, which enable type-safe event
notifications.
 Properties, which serve as accessors for private member variables.
 Attributes, which provide declarative metadata about types at run time.
 Inline XML documentation comments.

1
C# Design Goals:
When the C++ language first came out, it caused quite a stir. Here was a language for
creating object-oriented software that didn’t require C programmers to abandon their skills or
their investment in software. It wasn’t fully object-oriented in the way a language like Eiffel
is, but it had enough object-oriented features to offer great benefits.
C# provides a similar opportunity. In cooperation with the .NET Common Language
Runtime, it provides a language to use for component-oriented soft- ware, without forcing
programmers to abandon their investment in C, C++, or COM code.
C# is designed for building robust and durable components to handle real- world
situations.

Component Software:
The .NET Common Language Runtime is a component-based environment, and it
should come as no surprise that C# is designed to make component creation easier.
It’s a “component-centric” language, in that all objects are written as components, and
the component is the center of the action.
Component concepts, such as properties, methods, and events, are first-class citizens
of the language and of the underlying runtime environment. Declarative information (known
as attributes) can be applied to components to convey design- time and runtime information
about the component to other parts of the system. Documentation can be written inside the
component and exported to XML.
C# objects don’t require header files, IDL files, or type libraries to be created or used.
Components created by C# are fully self-describing and can be used without a registration
process.
C# is aided in the creation of components by the .NET Runtime and Frameworks,
which provide a unified type system in which everything can be treated as an object.

Robust and Durable Software:

In the component-based world, being able to create software that is robust and durable
is very important. Web servers may run for months without a scheduled reboot, and an
unscheduled reboot is undesirable and the garbage collection takes the burden of memory
management away from the programmer, problems of writing version able components are
eased by definable versioning semantics and the ability to separate the interface from the
implementation.

Numerical operations can be checked to ensure that they don’t overflow, and arrays
support bounds checking.

2
 C# also provides an environment that is simple, safe, and straightforward. Error
handling is not an afterthought, with exception handling being present throughout the
environment. The language is type-safe, and it protects against the use of variables that have
not been initialized, unsafe casts, and other common programming errors.

Real-World Software:
Software development isn’t pretty. Software is rarely designed on a clean slate; it
must have decent performance, leverage existing code, and be practical to write in terms of
time and budget. A well-designed environment is of little use if it doesn’t provide enough
power for real-world use.
C# provides the benefits of an elegant and unified environment, while still providing
access to “less reputable” features—such as pointers—when those features are needed to get
the job done.
C# protects the investment in existing code. Existing COM objects can be used as if
they were .NET objects.
The .NET Common Language Runtime will make objects in the runtime appear to be
COM objects to existing COM-based code. Native C code in DLL files can be called from C#
code.
C# provides low-level access when appropriate. Lightweight objects can be written to
be stack allocated and still participate in the unified environment. Low- level access is
provided via the unsafe mode, which allows pointers to be used in cases where performance
is very important or when pointers are required to use existing DLLs.
C# is built on a C++ heritage and should be immediately comfortable for C++
programmers. The language provides a short learning curve, increased productivity, and no
unnecessary sacrifices.
Finally, C# capitalizes on the power of the .NET Common Language Runtime, which
provides extensive library support for general programming tasks and application-specific
tasks. The .NET Runtime, Frameworks, and languages are all tied together by the Visual
Studio environment, providing one-stop-shopping for the .NET programmer.

The C# Compiler and Other Resources:

There are two ways of getting the C# compiler. The first is as part of the .NET SDK.
The SDK contains compilers for C#, VB, C++, and all of the frameworks. After you
install the SDK, you can compile C# programs using the csc command, which will generate
an .exe that you can execute. The other way of getting the compiler is as part of the Visual
Studio.NET.

3
 Summary of versions

C# 2.0 C# 3.0 C# 4.0 C# 5.0 (planned)

 Implicitly
typed variables
 Implicitly
 Dynamic
typed arrays
 binding
Generics  Anonymous
 Named and
 Partial types types  Asynchronous
optional
 Anonymous  Extension methods
arguments
methods methods  Compiler As a
 Generic co-
 Iterators  Query Service
and
 Nullable types expressions
contravarian
 Lambda
ce
expressions
 Expression
trees

4
.NET Framework:
C# programs run on the .NET Framework, an integral component of Windows that
includes a virtual execution system called the common language runtime (CLR) and a unified
set of class libraries. The CLR is Microsoft's commercial implementation of the common
language infrastructure (CLI), an international standard that is the basis for creating execution
and development environments in which languages and libraries work together seamlessly.

Source code written in C# is compiled into an intermediate language (IL) that

conforms to the CLI specification. The IL code, along with resources such as bitmaps and
strings, is stored on disk in an executable file called an assembly, typically with an extension
of .exe or .dll. An assembly contains a manifest that provides information on the assembly's
types, version, culture, and security requirements.

When the C# program is executed, the assembly is loaded into the CLR, which might
take various actions based on the information in the manifest. Then, if the security
requirements are met, the CLR performs just in time (JIT) compilation to convert the IL code
into native machine instructions. The CLR also provides other services related to automatic
garbage collection, exception handling, and resource management.

Code that is executed by the CLR is sometimes referred to as "managed code," in

contrast to "unmanaged code" which is compiled into native machine language that targets a
specific system. The following diagram illustrates the compile-time and run time
relationships of C# source code files, the base class libraries, assemblies, and the CLR.

Language interoperability is a key feature of the .NET Framework. Because the IL

code produced by the C# compiler conforms to the Common Type Specification (CTS), IL
code generated from C# can interact with code that was generated from the .NET versions of
Visual Basic, Visual C++, Visual J#, or any of more than 20 other CTS-compliant languages.

A single assembly may contain multiple modules written in different .NET languages,
and the types can reference each other just as if they were written in the same language.

In addition to the run time services, the .NET Framework also includes an extensive
library of over 4000 classes organized into namespaces that provide a wide variety of useful
functionality for everything from file input and output to string manipulation to XML
parsing, to Windows Forms controls.

5
6
.NET Framework Architecture:
There is one way of describing code (metadata), and one runtime and library (the
Common Language Runtime and Frameworks). The following diagram shows how the .NET
Runtime is arranged:

The Common Language Runtime provides the basic execution services. On top of
that, the base classes provide basic data types, collection classes, and other general classes.
Built on top of the base classes are classes for dealing with data and XML. Finally, at the top
of the architecture are classes to expose web services and to deal with the user interface. An
application may call in at any level and use classes from any level.

Principal design features:

Because computer systems commonly require interaction between new and older
applications, the .NET Framework provides means to access functionality that is
implemented in programs that execute outside the .NET environment. Access to COM
components is provided in the System.Runtime.InteropServices and
System.EnterpriseServices namespaces of the framework; access to other
functionality is provided using the P/Invoke feature.

Common Runtime Engine

The Common Language Runtime (CLR) is the execution engine of the .NET
Framework. All .NET programs execute under the supervision of the CLR,
guaranteeing certain properties and behaviors in the areas of memory management,
security, and exception handling.

7
Language Independence

The .NET Framework introduces a Common Type System, or CTS. The CTS
specification defines all possible datatypes and programming constructs supported by
the CLR and how they may or may not interact with each other conforming to the
Common Language Infrastructure (CLI) specification. Because of this feature, the
.NET Framework supports the exchange of types and object instances between
libraries and applications written using any conforming .NET language.

Base Class Library

The Base Class Library (BCL), part of the Framework Class Library (FCL), is a
library of functionality available to all languages using the .NET Framework. The
BCL provides classes which encapsulate a number of common functions, including
file reading and writing, graphic rendering, database interaction, XML document
manipulation and so on.

Simplified Deployment

The .NET Framework includes design features and tools that help manage the
installation of computer software to ensure that it does not interfere with previously
installed software, and that it conforms to security requirements.

Security

The design is meant to address some of the vulnerabilities, such as buffer overflows,
that have been exploited by malicious software. Additionally, .NET provides a
common security model for all applications.

Portability

The design of the .NET Framework allows it to theoretically be platform agnostic,

and thus cross-platform compatible. That is, a program written to use the framework
should run without change on any type of system for which the framework is
implemented.

Versions:

Microsoft started development on the .NET Framework in the late 1990s originally under the
name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions
of .NET 1.0 were released.

Version 3.0 of the .NET Framework is included with Windows Server 2008 and Windows
Vista. Version 3.5 is included with Windows 7, and can also be installed on Windows XP and
the Windows Server 2003 family of operating systems. On April 12, 2010, .NET Framework
4 was released alongside Visual Studio 2010.

8
The .NET Framework family also includes two versions for mobile or embedded device use.
A reduced version of the framework, the .NET Compact Framework, is available on
Windows CE platforms, including Windows Mobile devices such as smartphones.
Additionally, the .NET Micro Framework is targeted at severely resource-constrained
devices.

Version Release
Version Visual Studio Default in Windows
Number Date

1.0 1.0.3705.0 2002-02-13 Visual Studio .NET

Visual Studio .NET

1.1 1.1.4322.573 2003-04-24 Windows Server 2003
2003

2.0 2.0.50727.42 2005-11-07 Visual Studio 2005 Windows Server 2003 R2

Windows Vista, Windows Server

3.0 3.0.4506.30 2006-11-06
2008

Windows 7, Windows Server

3.5 3.5.21022.8 2007-11-19 Visual Studio 2008
2008 R2

4.0 4.0.30319.1 2010-04-12 Visual Studio 2010

ABOUT MS-ACCESS

Access is a relational database program .Access is used to enter, edit, and analyze lists of
data. Relational databases minimize redundant data

Advantages of Access

 Duplicate data is minimized

 Information is more accurate
 Data entry is faster and easier
 Information can be viewed and sorted in multiple ways.
 Information is more secure
 Information can be shared among several users
 Information retrieval is faster and easier

9
 System Development Methodology

Existing System

During analysis, data collected on the various files, decision points and transactions handled
by the present system. The commonly used tools in the system are Data Flow Diagram,
interviews, etc. Training, experience and common sense are required for collection of
relevant information needed to develop the system. The success of the system depends
largely on how clearly the problem is defined, thoroughly investigated and properly carried
out through the choice of solution. A good analysis model should provide not only the
mechanisms of problem understanding but also the frame work of the solution. Thus it
should be studied thoroughly by collecting data about the system. Then the proposed system
should be analyzed thoroughly in accordance with the needs.

 System analysis can be categorized into four parts.

 System planning and initial investigation
 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis.

In the current system we need to keep a number of records related to the student and want to
enter the details of the student and the marks manually. In this system only the teacher or the
school authority views the mark of the student and they want to enter the details of the
student. This is time consuming and has much cost.

 More man power.

 Time consuming.
 Consumes large volume of pare work.
 Needs manual operations.
 There is no record for whole university staff.
 There is no option of clear or backspace.

Proposed System
The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. The system provides proper
and reduces the manual work.

 Minimum time needed for the various processing.

 Greater efficiency.
 Better service.

10
  User friendliness and interactive.
 Minimum time required.
 There is an option of clear (all at a time) and backspace (one at a time).
 Symptoms, treatment and doctor consulted.
 Switching from Standard to Scientific mode.
 User friendly interface
 Fast access to database
 Less error
 More Storage Capacity
 Search facility

FEASIBILITY ANALYSIS

Whatever we think need not be feasible .It is wise to think about the feasibility of any
problem we undertake. Feasibility is the study of impact, which happens in the organization
by the development of a system. The impact can be either positive or negative. When the
positives nominate the negatives, then the system is considered feasible. Here the feasibility
study can be performed in two ways such as technical feasibility and Economical Feasibility.

Technical Feasibility

We can strongly says that it is technically feasible, since there will not be much difficulty in
getting required resources for the development and maintaining the system as well. All the
resources needed for the development of the software as well as the maintenance of the same
is available in the organization here we are utilizing the resources which are available
already.

Economical Feasibility

Development of this application is highly economically feasible .The organization needed

not spend much money for the development of t he system already available. The only thing
is to be done is making an environment for the development with an effective supervision. I f
we are doing so , we can attain the maximum usability of the corresponding resources .Even
after the development , the organization will not be in condition to invest more in t he
organization .Therefore , the system is economically feasible.

1.     Initiation Phase
The initiation of a system (or project) begins when a business need or opportunity is
identified. A Project Manager should be appointed to manage the project. This business need
is documented in a Concept Proposal. After the Concept Proposal is approved, the System
Concept Development Phase begins.

11
2.    System Concept Development Phase
Once a business need is approved, the approaches for accomplishing the concept are reviewed
for feasibility and appropriateness. The Systems Boundary Document identifies the scope of the
system and requires Senior Official approval and funding before beginning the Planning Phase.

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

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

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

6.      Development Phase
The detailed specifications produced during the design phase are translated into hardware,
communications, and executable software. Software shall be unit tested, integrated, and
retested in a systematic manner. Hardware is assembled and tested.

12
7.      Integration and Test Phase
The various components of the system are integrated and systematically tested. Is the menu
bar displayed in the appropriate contested some system related features included either in
menus or tools? Do pull –Down menu operation and Tool-bars work properly? Are all menu
function and pull down sub function properly listed ?; Is it possible to invoke each menu
function using a logical assumptions that if all parts of the system are correct, the goal will be
successfully achieved .? In adequate testing or non-testing will leads to errors that may
appear few months later.

 This create two problem

 Time delay between the cause and appearance of the problem.

The effect of the system errors on files and records within the system

The purpose of the system testing is to consider all the likely variations to which it will be
suggested and push the systems to limits.

The testing process focuses on the logical intervals of the software ensuring that all
statements have been tested and on functional interval is conducting tests to uncover errors
and ensure that defined input will produce actual results that agree with the required results.
Program level testing, modules level testing integrated and carried out.

There are two major type of testing they are

 White Box Testing.

 Black Box Testing.

White Box Testing

White box sometimes called “Glass box testing” is a test case design uses the control
structure of the procedural design to drive test case.

Using white box testing methods, the following tests were made on the system

 All independent paths within a module have been exercised once. In our system,
ensuring that case was selected and executed checked all case structures. The bugs
that were prevailing in some part of the code where fixed
 All logical decisions were checked for the truth and falsity of the values.

Black box Testing

Black box testing focuses on the functional requirements of the software. This is black box
testing enables the software engineering to derive a set of input conditions that will fully
exercise all functional requirements for a program. Black box testing is not an alternative to
white box testing rather it is complementary approach that is likely to uncover a different
class of errors that white box methods like..

13
  Interface errors
 Performance in data structure
 Performance errors
 Initializing and termination errors

8.      Implementation Phase
The system or system modifications are installed and made operational in a production
environment. The phase is initiated after the system has been tested and accepted by the .
This phase continues until the system is operating in production in accordance with the
defined user requirements.

End user Training:

The successful implementation of the new system will purely upon the involvement of the
officers working in that department. The officers will be imparted the necessary training on
the new technology

End User Education:

The education of the end user start after the implementation and testing is over. When the
system is found to be more difficult to understand and complex, more effort is put to educate
the end used to make them aware of the system, giving them lectures about the new system
and providing them necessary documents and materials about how the system can do this.

9.      Operations and Maintenance Phase

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

14
 SYSTEM REQUIREMENTS

HARDWARE REQUIREMENTS

Processor : Intel Pentium IV 2.4 GHZ or above

Clock speed : 500 MHZ

System bus : 32 bits

RAM : 256MB of RAM

HDD : 40 GB or higher

Monitor : SVGA COLOR

Keyboard : 108Keys

Mouse : 2 button mouse

SOFTWARE REQUIREMENTS

OS : All MS Windows

Environment : .Net Framework v3.5

Front end : C#

Back end : Microsoft Access 2007

15
 Tables Used

Security

Field Name Data Type Description

Username Text(10) Primary Key
Password Text(10) -

Student Record

Field Name Data Type Description

Clinic_No Number Primary Key
Surname Text(15) -
Firstname Text(15) -
Middlename Text(15) -
Sex Text(1) -
Phone Text(10) -
Email Text(30) -
Next_of_kin Text(15) -
Next_of_kin(phone) Number -
Roll_no Number Primary Key
D_O_B Date -
Blood_group Text(2) -
Eye_sight Text(3) -
course Text(10) -

Student Visit

Field Name Data Type Description

Clinic_No Number Primary Key
Surname Text(15) -

16
 Firstname Text(15) -
Middlename Text(15) -
Sex Text(1) -
Roll_no Number Primary Key
Date_of_visit Date -
Date_of_discharge Date -
Symptoms Text(50) -
Disease Text(50) -
Treatment Text(50) -
Doctor Text(20) -

Staff Record

Field Name Data Type Description

Clinic_No Number Primary Key
Surname Text(15) -
Firstname Text(15) -
Middlename Text(15) -
Sex Text(1) -
Phone Text(10) -
Email Text(30) -
Next_of_kin Text(15) -
Next_of_kin(phone) Number -
Staff_id Number Primary Key
D_O_B Date -
Blood_group Text(2) -
Eye_sight Text(3) -
Teach Text(10) -

Staff Visit

Field Name Data Type Description

Clinic_No Number Primary Key
Surname Text(15) -
Firstname Text(15) -
Middlename Text(15) -
Sex Text(1) -
Staff_id Number Primary Key

17
 Date_of_visit Date -
Date_of_discharge Date -
Symptoms Text(50) -
Disease Text(50) -
Treatment Text(50) -
Doctor Text(20) -

Clinic Staff

Field Name Data Type Description

Staff_id Number Primary Key
Surname Text(15) -
Firstname Text(15) -
Middlename Text(15) -
Sex Text(1) -
Phone Text(10) -
Email Text(30) -
Job Text(15) -

18
 UNIVERSITY HEALTH CARE

Connecting MS Access database in C#

 Create Access database (e.g.  ptuhc)

19
 Now open you notepad and click on Save As button. Name then ptuhc.udl. Change
Save as type by "All Files".

20
 Now double click on ptuhc.udl file. A wizard will start like this:

21
 Click Provider TAB, select Microsoft Jet 4.0 OLE DB (denoted by black arrow) then
click next. Now click "Select or enter a database name" and select the desire database
then click open.

22
 Now click on test connection and click OK
 Now edit this UDL file with note pad and copy link as shown below

23
Copy the selected line from the Notepad and paste this in your main program coding where
you wanted the database to be used.

Creating Crystal Reports

24
Crystal Reports is a business intelligence application used to design and generate reports
from a wide range of data sources. Several other applications, such as Microsoft Visual
Studio, bundle an OEM version of Crystal Reports as a general purpose reporting tool.
Crystal Reports became the de facto standard report writer when Microsoft released it with
Visual Studio.

History

The product was originally created by Crystal Services Inc. as Quik Reports when they
couldn't find a suitable commercial report writer for their accounting software. After
producing versions 1.0 through 3.0, the company was acquired in 1994 by Seagate
Technology. Crystal Services was combined with Holistic Systems to form the Information
Management Group of Seagate Software, which later rebranded as Crystal Decisions, and
produced versions 4.0 through 9.0. Crystal Decisions was acquired in December 2003 by
Business Objects, which has so far produced versions 10, 11 (XI) and the current version 12
(2008). Business Objects was acquired by SAP on October 8, 2007.

Features
Report designer

Crystal Reports allows users to graphically design data connections and report layout. In the
Database Expert, users can select and link tables from a wide variety of data sources,
including Microsoft Excel spreadsheets, Oracle databases, Business Objects Enterprise
business views, and local file system information. Fields from these tables can be placed on
the report design surface, and can also be used in custom formulas, using either BASIC or
Crystal's own syntax, which are then placed on the design surface. Formulas can be evaluated
at several phases during report generation as specified by the developer.

Both fields and formulae have a wide array of formatting options available, which can be
applied absolutely or conditionally. The data can be grouped into bands, each of which can be
split further and conditionally suppressed as needed. Crystal Reports also supports
subreports, graphing, and a limited amount of GIS functionality.

Supported data sources

Accessible data sources include the following:

 Databases such as PostgreSQL, Sybase, IBM DB2, Ingres, Microsoft Access,

Microsoft SQL Server, MySQL, Interbase and Oracle
 Btrieve
 Spreadsheets such as Microsoft Excel
 Text files
 HTML XML files
 Groupware applications as Lotus Notes, Microsoft Exchange and Novell GroupWise

25
  SAP: BW, Info Sets, Tables, and Business Objects Universes
 Any other data source accessible through a web service, ODBC, JDBC or OLAP.

Development

Crystal Reports comes integrated with Visual Studio. Crystal Reports allows Java developers
to build applications with Crystal Reports components.

26
The next window looks like the following and you have to select your created Dataset under
“Project Data”, and click “Insert Table”, then click next.

27
Then your report creation is done by the .NET IDE. If you want to make any changes to the
report, you can do so by using the .NET IDE.

Set the Created Report to Display in the Form

Then you have to set a “crystalReportViewer” in your form to load the report that you created
earlier.

USER INTERFACE

28
Splash Screen

Login Screen
Here Username is primary key.

After successful login following screen will be display. Click on OK button to move onto
next interface.

29
Selection Screen

Button Clicked: Student Record

30
When Add button is clicked on student record following interface will get display.

When OK button is clicked message box appear as:

31
After adding data, interface will get appear as following:

Search Surname button is clicked. Selected record will get display using yellow colour.

32
Delete button: Record to be deleted is selected and then delete button is clicked, interface
will appear as follow; when OK button is clicked data get deleted.

Report Button: Crystal report will be generated, displaying the following format. This can
be printed using the print button provided in the menu bar.

33
 .

Button Clicked: Student Medical Record

34
When Add button is clicked on student record following interface will get display.

35
When OK button is clicked message will appear as:

After adding data, interface will get appear as follow:

36
Report Button: Crystal report will be generated, displaying the following format. This can
be printed using the print button provided in the menu bar.

Button Clicked: Clinic Staff Record

37
When Add button is clicked on student record following interface will get display.

38
Report Button: Crystal report will be generated, displaying the following format. This can
be printed using the print button provided in the menu bar.

39
Button Clicked: Security

Button Clicked: About

40
Button Clicked: Exit

CONCLUSION

41
 Our project is only a humble venture to satisfy the needs in an Institution. Several
user friendly coding have also adopted. This package shall prove to be a powerful
package in satisfying all the requirements of the organization.

The objective of software planning is to provide a frame work that enables the
manger to make reasonable estimates made within a limited time frame at the beginning
of the software project and should be updated regularly as the project progresses. Last but
not least it is no the work that played the ways to success but ALMIGHTY

BIBLIOGRAPHY

42
Books

1. A Practical Introduction to .Net Framework, Narosa Publishing House, 2007

2. Dan W., Introduction To C#, Pearson Education, 2007

Websites

1. Wikipedia
2. Msdn
3. Dotnetspider

43