Skin Bank Management

A Project Report
Submitted in partial fulfillment of the
Requirements for the award of the
Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

By Aakash Gupta & Jagdish Dhangar

Under the esteemed

guidance of

Prof. Sandeep Kamble

DEPARTMENT OF INFORMATION TECHNOLOGY

VALIA CHHAGANLAL LALJIBHAI COLLEGE OF COMMERCE

(Affiliated to University of
Mumbai)MUMBAI, 400 053
MAHARASHTRA
2021-2022

Page 1
 VALIA CHHAGANLAL LALJIBHAI COLLEGE OF
COMMERCE
(Affiliated to University of Mumbai)
MUMBAI-MAHARASHTRA-400053

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE
This is to certify that the project entitled “Skin Bank Management”, is
bonafied work of MR. AAKASH GUPTA and JAGDISH DHANGAR
bearing Seat No: 2010979 & 2010973 submitted in period fulfillment of the
requirements for the award of degree of BACHELOR OF SCIENCE in
INFORMATION TECHNOLOGY from University of Mumbai.

Internal Guide Coordinator

External Examiner

Date: College Seal

Page 2
 Abstract

This report covers all the stages of software development, we underwent, during the process of working

on this project. It is a Step-by-Step documentation, right from initial planning and designing phase to final

implementation.

The INTRODUCTION gives the reader an intro about project, and also the problems related to the

existing system, and how useful is our website to handle and eliminate those problems.

The followving sections like OBJECTIVES and LIMITATION give the reader some knowledge regarding

the technology and tools we have used for developing this project. The chapter REQUIREMENTS AND

ANALYSIS covers the planning and scheduling, software and hardware requirements andx

the preliminary design.

The section IMPLEMENTATION AND TESTING contains the testing and coding details. I have tried to

be as brief as possible about each and every step of this project development process, and I hope that this

report gives a clear idea to the reader about each and every aspect of this project.

Suggestions for improvement will be gratefully accepted and acknowledged.

Page 3
 ACKNOWLEDGEMENT
We would like to place our sincere gratitude to whom so ever has that they have
contributed to the successful completion of this project directly or indirectly.
We take this opportunity to express my profound gratitude and deep regards to
our guide Prof. Sandeep Kamble, without whose guidance & critical appreciation,
this project would have been incomplete. Right from its inception, this project has
been shaped by his expert opinions and he has helped me improve this project in all
manners and achieve the
level that it has acquired.
Last but not the least we place a deep sense of gratitude to our family members
and our friends who have been constant source of inspiration during the preparation
of this project work.

Page 4
 DECLARATION
I hereby declare that the project entitled, “Skin Bank Management Project” done
at place where the project is done, has not been in any case duplicated to submit to
any other university for the reward of any degree. To the best of my knowledge other
than me, no one has submitted to any other university.

The project is done in partial fulfilment of the requirement for the award of degree
of BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be
submitted as finalsemester project as part of our curriculum.

AAKASH GUPTA JAGDISH DHANGAR

Name and Signature of the Student Name and Signature of the Student

Page 5
 INDEX

Sr No Topic Name Page No.

1 Introduction 7
1.1 Background 8
1.2 Objectives 9
1.3 Purpose 10
1.4 Scope 11
1.5 Applicability 12
1.6 Achievements 13
1.7 Organization of Report 14

2 Survey of Technologies 15

3 Requirements And Analysis 17

3.1 Problem Definition 17
3.2 Requirement Specification 18
3.3 Planning and Scheduling 19
3.4 Software And Hardware Requirement 23
3.5 Planning and Scheduling 24
3.6 Conceptual Models 25

4 System Design
4.1 Basic Module 39
4.2 Data Design 40
4.3 Schema Design 41
4.4 Data Integrity and Constrains 43
4.5 Procedural Diagram 46
4.6 User Interface Design 49
4.7 Security Issues 50
4.8 Test Case Design 53

5 Implementation and Approaches

6
5.1 Coding Details and Efficiency 56
5.2 Coding Details 58
5.3 Testing Approaches 73
5.4 Modifications and Improvments 77
5.5 Test Cases 78

6 Results and Discussion

6.1 Outputs 81
6.2 User Documentation 92

7 Conclusions
7.1 Significance of System 94
7.2 Limitations of the System 95
7.4 Future Scope of Project 96
7.5 References 97

7
 Chapter 1
INTRODUCTION TO PROJECT

 The National Burns Centre promoted by the Indian Burns Society is a

unique and pioneering project to provide comprehensive research and
advance training facilities in the latest burns care technology.
 Specially adapted to India’s present socio-economic profile
characterizedby low incomes, an unsanitary domestic environment and
low resistanceto infection, it has been established to focus on attention
and effort on allaspects of Burns in order to develop expertise in this
particular area of specialization.
 To create an institute, this will set standards of excellence in Research,
Training, Prevention, Treatment and Rehabilation relating to Burns.
 Primary Goals is to evolve simplified methods of management to reduce
treatment costs and to evaluate new drugs.
 Research to adapt methods , proven elsewhere to suit our condition.
 Designing and evaluation of Medical Records , Health Care Insurance
and Disaster Management are the other aspects to be included in the
scope of functioning.
 The System consists of following module
 Users can:-

 Add users
 Add Folders
 Delete Folders
 Add Files
 Delete Files
 Download Files

8
 BACKGROUND

 The Skin Bank aims to provide a ready source of clinically safe human

donor skin to treat severe burns.

 Since 1998, the Skin Bank has had an average of 7 deceased donors per

year.

 Each year the demand of donated skin to treat to massive burns patients

exceed the skin supply donated by our local skin donors.

 This is why increasing awareness and public education is important.

 An increased awareness of skin donation will hopefully increase the

number of local skin donors overtime.

9
 OBJECTIVES

 Functional objectives :- This states the new or amended functional

system requirements.
 New or changed outputs reports or displays:-The Letter and certificate
of the donor are computerized. The doctor need not write on the paper.
 Revised security and access control :-Only the Administrator is
responsible for the addition and modification of the details of the Donors
, Patients and Skin. The normal user cannot modify that database.
 Process Improvement :- This includes the rearrangements of the way a
service is provided.
 Changes to the process steps:-The entering of details and Skin
allocation and certificate is carried out computationally. Thus it saves a
lot of time and manpower.
 Changes to inputs and outputs methods:-The result and detail of the
burn surgery can be made available quickly.
 Performance standards:-As the calculations are done computationally,
data is accurate and the speed is much more than the manual system.
 Simple Registration Process:- Question database can be customized.
User friendly software.

10
 PURPOSE OF SKIN BANK

 Skin banking is a facility where the skin is collected from

eligible deceased donor and processed as per international

protocols.

 Skin can be stored in the skin bank at 4-80 Celsius upto 5 years.

 Skin bank will be helpful for patients as well as for Hospitals.

 By using skin bank there was increase in survival rate.

 Cost of treatment goes down.

11
 SCOPE OF SKIN BANK

 The scope of the project is that in a very short span it provides user with

many facilities.

 The main purpose of this project is to interconnect all the skin banks,

hospitals, donors into a single network, validation, store various data and

information of skin and health of each individual.

 Emergency issue of skin.

 Management of returned and unused skin units.

 Its build in such a way that it should suits for all type of skin bank in

future.

 So every effort is taken to implement this project in this skin bank, on

successful implementation in this skin bank, we can target other skin

banks in the city.

12
 APPLICABILITY

 The skin bank management system website for ECD ETL/RFC is for

some private/public use.

 The website will be public but it will used by some organization which is

hospital or skin bank centre.

 After the website is tested in one centre then it can used by local centers

(12 centers). The further more to step to my vision is that will be used in

centers across India.

13
 ACHIEVEMENTS

 This project will help me to achieve one more steps to my leadership as

this grows and as this project will be upgrade time to time .It can reach
to 12 centers rapidly.

14
 ORGANISATION OF REPORT

 Organisation of report means to summarize the next chapters of the project

documentation.

 The System contains the information of basic module in the system.

 In schema design, short description of the database of the system is covered.

 The next chapter is Testing methodology that describes how to do testing.

 The next chapter is Survey on Technology in which there is short summary

of thedifferent technologies which are available in the market.

 The next chapter is Requirements and Analysis. In this chapter the existing

system,their drawbacks and the requirements for modification of existing

system are covered.

 There is detailed information about the feasibility study. In feasibility study

there arefunctional and non-functional requirements of system.

 It includes software and hardware requirements required to develop this project.

 Gantt chart is used to represent the schedule and planning of the project.

 Conceptual model helps to represent the Unified Modelling Language

(UML)diagrams.

15
 Chapter 2
SURVEY OF TECHNOLOGY
 With the rapid growth and use of internet, sweeping changes in users
information search behaviour has been simulated. The project of Skin
Bank Management System can be made on various Technologies and
various languages
 SQL Server (STRUCTURED QUERY LANGUAGE)
Database ASP.NET is an open-source server-side web application
framework designed for web development to produce dynamic web
pages.
 It was developed by Microsoft to allow programmers to build dynamic
web sites, web applications and web services.
 ASP_NET is a technology which is used for both Front-end & Back-end
development in the software industry.
 Front-end: ASP_NET provide large set of controls with .NET framework
for Front-end of any Web App or Website. (like, Grid View, Repeater,
Data List, Dropdown control…etc.) Back-end: It also has lot of on back-
end side with VB and C# languages.
 SQL-Server is also one of the most secure databases with support of
Microsoft. if you want just back-end for mobile application or other Web
app.
 It has web-services too. WCF (Windows Communication Foundation) is
latest technology used for web services.

 Microsoft SQL Server is a relational database

managementsystem developed by Microsoft. As a database
server, it is a software product with the primary function of
storing and 8 retrieving data as requested by other software

16
 applications—which may run either on thesame computer or
on another computer across a network (including theInternet).
 Microsoft markets at least a dozen different editions of
Microsoft SQLServer, aimed at different audiences and for
workloads ranging from small single-machine applications to
large Internet-facing applications

The windows web server thoroughly monitors the web pages, multiple
components, and applications running over it.
 The Dot Net Framework quickly gives an alert for memory leaks,
unbounded loops, and other wrong behaviours, immediately killing them
and restart them over again.
 Asp.Net features like early binding, JIT compilation, caching services and
native optimization supports gives your application the high level of
performance.
 All the Asp.Net applications are highly monitored and managed to help
application available to handle requests.

17
 Chapter 3
REQUIREMENTS AND ANALYSIS

PROBLEM DEFINITION

 The problem Definition should be given the highest priority because

every person has different approach to his or her vision and transform it
to reality. Problem definition requires better understanding of the problem
environment.
 Currently, Users are storing the data in the Personal Computer. Data can
be required anywhere you travel or that purpose you cannot carry
Personal Computers everywhere you want. Hence the users need to carry
the data in hard drives, pen drives, etc.
 Pen drives, Hard drives, etc, are easy to carry everywhere but there is
possibility to lose these devices easily. If the data is very crucial it may
lead to a great loss to the User.
 It becomes difficult to store the data is such manner hence to overcome

from these situation “SKIN BANK MANAGEMENT SYSTEM” will

help.

18
 REQUIREMENTS SPECIFICATION

 The website for Skin Bank Management System will require a software
tool which will help to make an app.
 The app should support the Microsoft SQL Server code for the backend
because the Microsoft SQL code is better than c and c++ and for frontend
Microsoft visual studio 2010 is very easy and better by this requirement
and making an app Android studio is perfect software with have
Microsoft SQL Server .
 For building Skin Bank Management System website there will be need
of laptop or a computer with minimum 4GB of ram i3 processor and
minimum space in hard disk because android studio is very heavy
 It should be user friendly
o It should perform the basic requirements.
o The GUI should be interactive.
o The data should be secured for hospitals as well as skin bank.
o The system should not clash.
o It should be able to generate report after all the data.
o The Report generated needs to be in standard format as per hospital
and skin bank

o The system should be easy to understand and work with it.

19
 PLANNING AND SCHEDULING

 The key to a successful project is planning. Creating a project plan is

the first thing you should do when undertaking any project.
 When setting goals, it should be specific measureable, achievable,
realistic and timed.
 When it is planned and scheduled the actions that are taking a huge
step toward meeting those requirements. often project planning is
ignored in favour of getting on with he work.
 However, many people fail to realize the value of a project plan for
saving time and money and many problems.
 Meeting with the team to discuss the various elements of the project.
Starting by fixing the goal i. e to generate report of Skin Bank
Management system. It is specific to provide skin by including
validations where ever require.
 Also fulfilling all the needs of the institute for the. It should make up
report and store in database. The time require to complete the project
is of 6 months.
 Working backwards to determine the steps required to complete the
goal that is determined for the project to provide the skin report. The
work is being divided between the team member respectively to
accomplish the task. The criteria mentioned needs to be distributed for
working simultaneously and coordinate for the issues that arises

Steps for project planning:

 Identifying and meeting with stakeholders
 A stakeholders in this project are Hospitals members and skin bank
members and faculties who uses the software. This includes the
patients, donors, and admin. Making sure to identify all stakeholders

20
 and keeping their interests in mind when creating project plan.

 Meeting with the project sponsors and key stakeholders to discuss

their needs and expectations and establish baselines for project
scope, budget and timeline. Then creating scope Statement
document to finalize and record project scope details, getting
everyone on the same page andreduces the chances of costly
miscommunication.

 Set and prioritize Goals

 Once a list of stakeholders needs is created, prioritizing them and
setting specific project goals. These are outline project objectives, or
the metrics and benefits that hope to achieve.Writing the goals and the
stakeholders need they address in the project plan so its clearly
communicated and easily shareable.

 Define Deliverables:

 Identifying the deliverables and project planning steps required to meet

the projects goals. The specific outputs that are expected to produce the
output.
o Next, estimating due dates for each deliverables in the project plan
o Creating the project schedule
 Looking at each deliverables and project planning steps require to meet
the projects goals. The specific outputs that are expected to produce the
output.
o Identify Issues and Complete a Risk Assesment
 No project is risk free. There is some or the other problems that arises
while the project. That s we should be prepare for further issues and have
a backup for it solve.

21
Gantt Chart

 A Gantt chart, commonly used in project management, is one of the

most popular and useful ways of showing activities (tasks or events)
displayed against time.
 On the left of the chart is a list of the activities and along the top is a
suitable time scale. Each activity is represented by a bar; the position
and length of the bar reflects the start date, duration and end date of
the activity.
 A Gantt chart is constructed with a horizontal axis representing the
total time span of the project, broken down into increments (for
example, days, weeks, or months) and a vertical axis representing the
tasks that make up the project (for example, if the project is outfitting
your computer with new software, the major tasks involved might be:
conduct research, choose software, install software).
 Horizontal bars of varying lengths represent the sequences, timing,
and time span for each task. Using the same example, you would put
"conduct research" at the top of the vertical axis and draw a bar on the
graph that represents the amount of time you expect to spend on the
research, and then enter the other tasks below the first one and
representative bars at the points in time when you expect to undertake
them.
 The bar spans may overlap, as, for example, you may conduct research
and choose software during the same time span.
 As the project progresses, secondary bars, arrowheads, or darkened
bars may be added to indicate completed tasks, or the portions of tasks
that have been completed. A vertical line is used to represent the
report date.
 Gantt Chart was prepared with the help of the Gantt Pro website. It’s

22
free version was a boon for us as we were able to use its software tool
for free

23
SOFTWARE AND HARDWARE REQUIREMENTS

SOFTWARE REQUIREMENT
 Platform: WINDOWS 10
 FrontEnd: Microsoft visual studio
 BackEnd: Microsoft SQL server 2016

HARDWARE REQUIREMENTS:
 Processor: Intel Core i3
 RAM: 4 GB Minimum free space
 DVD R/RW

Other Software and Tools:

 MS Office for Document reading, Presentation

24
 PRELIMNERY PRODUCT DESCRIPTION

The development skin bank opens everyday from 8:00am to 8:00pm. The

patients and donor comes with their family to donate and issue for skin.The

patients will provide skin as per their need and from stock.Then family member

will put the entry into special skin bank admit card.This process goes on and on

till the patient family member get the skin.

As there was no certain software or application for ECD skin bank the need

arise.The system should be user friendly and easy to use. The objective of Skin

Bank Management System is to handle the entire activity of a library. The

software keeps track of all information and database where all information will

be stored safely

 Admin

 Patient

 Donor

25
 Conceptual Model

 Data Flow Diagram

 A data flow diagram shows the way information flows through a process
or system. It includes data inputs and outputs, data stores, and the various
sub processes the data moves through. DFDs are built using standardized
symbols and notation to describe various entities and their relationships.
 A data flow diagram (DFD) is a graphical representation of the "flow" of
data through an information system, modelling its process aspects. A
DFD is often used as a preliminary step to create an overview of the
system without going into great detail, which can later be elaborated.
DFDs can also be used for the visualization of data processing.
 Data flow diagrams are also known as bubble charts. DFD is a designing
tool used in the top-down approach to Systems Design. It does not show
information about process timing or whether processes will operate in
sequence or in parallel, unlike a traditional structured flowchart which
focuses on control flow, or a UML activity workflow diagram, which
presents both control and data flows as a unified model.
 A skin bank management system data flow diagram (DFD) shows how

the information within a skin bank system needs to flow to meet the
needs of patients as well as donor as well as skin bank administrators.

26
27
Zero Level DFD
 This is the zero level dfd of Skin Bank Management System, where we
have elaborated the high level process of Skin Bank Management. It is
a basic over view of Skin Bank Management System.

28
FIRST LEVEL DFD
 First Level DFD of Skin Bank Management System shows how the
system is divided into sub-systems, each of which deals with one or more
of data flows. It identifies internal data stores patient details and donor
details

DFD Level 1

29
SECOND LEVEL DFD

 Second Level DFD of Skin Bank Management System goes one step
deeper into parts of level 1. It may require more functionalities of skin
bank system to reach the necessary level of detail. The second level DFD
contains more details of skins and skin issue and donor details and patient
details and admin

30
ENTITY RELATIONSHIP DIAGRAM

 An Entity Relationship (ER) Diagram is a type of flowchart that

illustrates how “entities” such as people, objects or concepts
relate to each other within a system. ER Diagrams are most
often used to design or debug relational databases in the fields
of software engineering, business information systems,
education and research. Also known as ERDs or ER Models,
they use a defined set of symbols such as rectangles, diamonds,
ovals and connecting lines to depict the interconnectedness of
entities, relationships and their attributes. They mirror
grammatical structure, with entities as nouns and relationships
as verbs. ER diagrams are related to data structure diagrams
(DSDs), which focus on the relationships of elements within
entities instead of relationships between entities themselves. ER
diagrams also are often used in conjunction with data flow
diagrams (DFDs), which map out the flow of information for
processes or systems. An entity is a real-world item or concept
that exists on its own. Entities are equivalent to database tables
in a relational database, with each row of the table representing
an instance of that entity.
 An attribute of an entity is a particular property that describes
the entity. A relationship is the association that describes the
interaction between entities. Cardinality, in the context of ERD,
is the number of instances of one entity that can, or must, be
associated with each instance of another entity. In general, there
may be one-to-one, one-to-many, or many-to-many
relationships.
 Skin Bank Management System ER Diagram ..... It used
structure data and to define the relationships between structured
data groups Skin Bank Management System functionalities. The
main entities of the Skin Bank Management System are patient,
skin, Issues, admin, donor.

31
COMPONENTS OF E-R DIAGRAM

 Entities: which are represented by rectangles. An entity is an object or

concept about which you want to store information.

ENTITY

32
33
USE CASE DIAGRAM
 The use case diagram are usually referred to as behavior diagram used to
describe the actions of all user in a system all user describe in use case
are actors and the functionality as action of system. To model a system,
the most important aspect is to capture the dynamic behavior. Dynamic
behavior means the behavior of the system when it is running/operating.
 Only static behavior is not sufficient to model a system rather dynamic
behavior is more important than static behavior. In UML, there are five
diagrams available to model the dynamic nature and use case diagram is
one of them. Now as we have to discuss that the use case diagram is
dynamic in nature, there should be some internal or external factors for
making the interaction.
 These internal and external agents are known as actors. Use case
diagrams consists of actors, use cases and their relationships. The
diagram is used to model the system/subsystem of an application. A
single use case diagram captures a particular functionality of a system.
 Hence to model the entire system, a number of use case diagrams are
used. Use case diagrams are used to gather the requirements of a system
including internal and external influences. These requirements are mostly
design requirements. Hence, when a system is analyzed to gather its
functionalities, use cases are prepared and actors are identified.

34
35
Donor_Admin Usecase

Patient_Admin Usecase

36
SEQUENCE DIAGRAM
 A sequence diagram shows object interactions arranged in time sequence.
It depicts the objects and classes involved in the scenario and the
sequence of messages exchanged between the objects needed to carry out
the functionality of the scenario. Sequence diagrams are typically
associated with use case realizations in the Logical View of the system
under development. Sequence diagrams are sometimes called event
diagrams or event scenarios.
 A sequence diagram shows, as parallel vertical lines (lifelines), different
processes or objects that live simultaneously, and, as horizontal arrows,
the messages exchanged between them, in the order in which they occur.
This allows the specification of simple runtime scenarios in a graphical
manner. If the lifeline is that of an object, it demonstrates a role. Leaving
the instance name blank can represent anonymous and unnamed
instances.
 Messages, written with horizontal arrows with the message name written
above them, display interaction. Solid arrow heads represent synchronous
calls, open arrow heads represent asynchronous messages, and dashed
lines represent reply messages. If a caller sends a synchronous message, it
must wait until the message is done, such as invoking a subroutine. If a
caller sends an asynchronous message, it can continue processing and
doesn’t have to wait for a response. Asynchronous calls are present in
multithreaded applications, event-driven applications and in message-
oriented middleware. Activation boxes, or method-call boxes, are opaque
rectangles drawn on top of lifelines to represent that processes are being
performed in response to the message (Execution Specifications in UML

37
SEQUENCE DIAGRAM

38
39
 Chapter 4
SYSTEM DESIGN

Basic Modules

Admin Module

40
 Data Design

 The Database Skin bank System is intended to Automate the Skin bank
activities such as creating a new borrower, giving skin to the borrowers,
maintaining the details of all the item that were available in the skin. This
also helps the Members by providing information such as available Skin,
list of Skin, list of Donor and patient information that belong to a
particular category RFC/ETL.
 Table
 Skin Details: This is the master table for all the books that are available
in the Skin. This table contains the complete list of Skin that are available
in the Skin bank. Each Skin id provided with a unique Barcode which
serves as a primary key. The Skin details skin and age category of skin.
Columns barcode: This is unique ID given to every skin .Since there may
be a large no. of skin with same barcode, this barcode will help us to
distinguish between books of same title. Skin Title: Provides the name of
the Skin. AGE: defines age category.
 Patient Details: This table contains the details of all the patient who lent
a Skin from the Skin Bank. Each Patient will be given a unique borrower
ID. All the Skin Bank related activity for a particular person will be
captured based on the Borrower ID. This table will be used to track the
borrowing records. The borrower ID will serve as a primary key here.
Columns: Borrower ID: Unique ID given to each Patient.
 Skin ID: This column contains the skin ID which was given to the
borrower. Borrowed From Date: The date on which the book was given a
particular borrower. Borrowed To Date: The date on which that book was
supposed to be returned back or should be renewed. . Patient Details:
This table contains the details of all the Patient they are eligible for
availing Skin Bank facilities. Each Patient will be provided with a unique
Student ID and Borrower ID.

 ID will be Primary Key, whereas Borrower ID and Phone no will be

Unique. Columns: Patient id id: Unique ID given to Each Patient.
 Patient Name: The Name of the Patient.
 Sex: Gender of the Patient either Male or Female.
 Date Of Birth: The Date of Birth of the Patient.
 Borrower ID: The borrower ID assigned to each Patient.
 Contact Number: Contact number of the Patient.

41
 Schema Design

CLASS DIAGRAM
 In software engineering, a class diagram in the Unified Modeling
Language (UML) is a type of static structure diagram that describes the
structure of a system by showing the system’s classes, their attributes,
operations (or methods), and the relationships among objects.
 The class diagram is the main building block of object-oriented
modelling. It is used for general conceptual modelling of the systematic
of the application, and for detailed modelling translating the models into
programming code. Class diagrams can also be used for data 37odelling.
[1] The classes in a class diagram represent both the main elements,
interactions in the application, and the classes to be programmed.
 N the diagram, classes are represented with boxes that contain three
compartments:
 The top compartment contains the name of the class. It is printed in bold
and centered, and the first letter is capitalized.
 The middle compartment contains the attributes of the class. They are
left-aligned and the first letter is lowercase.
 The bottom compartment contains the operations the class can execute.
They are also left-aligned and the first letter is lowercase.

 A class with three compartments. In the design of a system, a number of

classes are identified and grouped together in a class diagram that helps to
determine the static relations between them. With detailed modelling, the
classes of the conceptual design are often split into a number of
subclasses.

42
43
 Data Integrity and constraints

ACTIVITY DIAGRAM
 Activity diagram is another important diagram in UML to describe the
dynamic aspects of the system.
 Activity diagram is basically a flowchart to represent the flow from one
activity to another activity. The activity can be described as an operation
of the system.
 The control flow is drawn from one operation to another. This flow can
be sequential, branched, or concurrent. Activity diagrams deal with all
type of flow control by using different elements such as fork, join, etc
 The basic usage of activity diagram is similar to other four UML
diagrams. The specific usage is to model the control flow from one
activity to another. This control flow does not include messages.
 Activity diagram is suitable for modeling the activity flow of the system.
An application can have multiple systems. Activity diagram also captures
these systems and describes the flow from one system to another. This
specific usage is not available in other diagrams. These systems can be
database, external queues, or any other system.
 We will now look into the practical applications of the activity diagram.
From the above discussion, it is clear that an activity diagram is drawn
from a very high level. So it gives high level view of a system. This high
level view is mainly for business users or any other person who is not a
technical person.
 The activity diagram used to describe flow of activity through a series of
actions. Activity diagram is an important diagram to describe the system.
The activity described as a action or operation of the system.

44
COMPONENTS OF ACTIVITY DIAGRAM.

45
46
 PROCEDURAL DIAGRAM
4.3.1 Logic Diagram

47
4.3.2 Data Structures

48
4.3.3 Algorithm Design

49
 User Interface Design

 User interface design (UI) or user interface engineering is the

design of user interfaces for machines and software, such as
computers, home appliances, mobile devices, and other
electronic devices, with the focus on maximizing usability and
the user experience.
 The goal of user interface design is to make the user's
interaction as simple and efficient as possible, in terms of
accomplishing user goals (user-centered design).
 Good user interface design facilitates finishing the task at hand
without drawing unnecessary attention to itself.
 Graphic design and typography are utilized to support its
usability, influencing how the user performs certain interactions
and improving the aesthetic appeal of the design; design
aesthetics may enhance or detract from the ability of users to use
the functions of the interface.
 The design process must balance technical functionality and
visual elements (e.g., mental model) to create a system that is
not only operational but also usable and adaptable to changing
user needs.
 Interface design is involved in a wide range of projects from
computer systems, to cars, to commercial planes; all of these
projects involve much of the same basic human interactions yet
also require some unique skills and knowledge.
 As a result, designers tend to specialize in certain types of
projects and have skills centered on their expertise, whether that
be software design, user research, web design, or industrial
design.

50
 Security Issues

 Skin Bank around the world are quickly adopting technology to better

manage their inventory and staff.

 The problem for skin bank is that they can’t afford I.T. departments to

help secure data and the like, so there are always common risks that skin

bank face.

 So, if you’re using an online master of information program to obtain an

online MLIS degree, you’ll want to learn to become a techwhiz to help

you adapt to today’s skin bank environments.

 Here are some of the security issues that skin bank face. The problem

most skin bank have is that staff members delete information on the

system by accident (or on purpose) and, if it’s not carefully backed up at

regular intervals, such information is lost forever.

 This can pose significant risk to important skin bank information and

data, so certain practices need to be implemented in terms of good backup

software to ensure this doesn’t happen.

 Skin Bank now send and retrieve data from databases to help better

manage inventory and the like, but some libraries don’t have the right

data encryption practices in place. This can often lead to lost data and

sometimes, the data easily obtainable by criminals.

 While inexperienced staff pose security risks in terms of loss of

51
 information, it’s not just staff that have access to certain Skin bank

management systems.

 Because Skin bank management doesn’t believe their skin bank is a

target, they’ll often not have the right staff authentication procedures.

 This means that anyone can come in off the streets and secure access to

skin bank management systems to undertake certain criminal activities.

 Staff members will often need to look through emails from other skin

bank professionals, and that means there is a risk when it comes to

downloading content onto the skin bank system.

 Emails can come from anywhere and, if staff members aren’t careful,

certain files can pose a risk to data and information on databases.

 Skin bank forget to implement practices so staff members can’t download

invalid content.

 Another security issue that many skin bank are faced with is that their

staff members aren’t that savvy when it comes to technology.

 Some members don’t understand how backups work, and that means

they’ll never know whether the information is securely backed up at

regular intervals.

 It’s important that staff members know how data and security work so

52
 they can better serve the Skin bank management system that’s already in

place.

 As stated above, opening emails and downloading unknown files can be

very risky to Skin Bank management systems, but isn’t just emails that

play a role.

 Sometimes, the opening of unsecured web pages and downloading files

for research purposes can often lead to third party data extraction.

 Phishing scams are a big problem when it comes to replicating data, so

security procedures need to come into play to prevent these type of

security risks from happening.

 The PAGE NO: 49 above are just some of the many security issues that

Skin banks are faced with every day. It’s great to see s implementing

different technologies to help them stay up with the digital skin banks,

but if it’s not implemented correctly, it could spell disaster for Skin bank

management

53
 Test Case Design

 The Skin bank manager system under test is rider Skin Bank management
system (hosted on source forge).
 It is very simple and effective system for management of Skin Bank
patients admin and donor and the skin.
 It has the features that you can expect from most of the competitive skin
bank systems.
 It is also free of cost to download the software. So you can download and
start testing the software manually for the bugs.
 What are the requirements of Skin Bank management system?
1. Member able to register and login.
2. Patient can search the added Skin, and check in or out.
3. User can manage the inventory of the Skin.

 These are some of the common features expected from the Skin
management system. Check if the username field accepts valid username
and password field accepts valid password.
 Testing Login of Skin bank System
 Check if the wrong username and valid password allows access to any
specific account.
 Check if the valid username and wrong password allows access to any
specific account.
 Check if the invalid username and password triggers any warning.
 Check if the invalid credentials open the random account.
 Check if the user is logged in, allows you to logout by using the link at
the bottom of the application.
 Check if the logout link function as expected.

 Testing Search system of Library

 Check if the search function allows searching of books as per title.
 Check if the search function allows searching of toy as per number.
 Check if the profile search has the results listed as table with profileinformation
containing member info

54
 CHAPTER 5

IMPLEMENTATION AND APPROACHES

Implementation Approaches

 Implementation approach
An implementation method tailored to the project is a prerequisite for successful
software implementation. This involves costing, planning, controlling and monitoring
the necessary tasks, including resources.

 Project implementation plan

The Project Implementation Plan (PIP) is a representation of the project in a
structured format provided by the Financial Mechanism Office (FMO) and
completed by the Project Promoter. ........ The completed PIP will serve as a
baseline for monitoring the performance of a project in terms of its scope,
schedule and budget.

 Role of Implementation plan

Implementation is the process that turns strategies and plans into actions in order to
accomplish strategic objectives and goals. Implementing your strategicplan is as
important, or even more important, than your strategy. Sadly, the majority of
companies who have strategic plans fail to implement them.
There are many ways of implementing a new system. The method chosen willdepend on the
organisation and the type of system being implemented.

55
 Objective Of Implementation Approaches

 Medical monitoring requires instant visibility across data sources and

access to dynamic analyses.
 However medical monitoring among patients, perform in-stream medical
advice, remains a challenging problem.
 Skin banks suffer frequent shortage of skin due to lack of skin donations,
hence skin donation requests are frequently seen on social media for
patients who urgently require skin transfusion with specific blood group.
 Recently, worldwide efforts have been undertaken to utilize social media
and smart phone applications to make the skin donation process more
convenient and provide a concrete information system that allows donors
and skin donation centers to communicate efficiently and coordinate with
each other to minimize time and effort required for skin donation process.
 This paper aims at developing a Cloud medical monitoring and Web-
Based skin Bank System which will allow skin donors and patients to
offer/request skin donation from skin banks.
 Additionally, a new method is proposed for continuous observation and
communication among doctors and patients.
 Using IOT cloud platform, simple medical devices equipped with medical
sensors can monitor health status of patients and update the electronic
medical records of patients' information.
Medical experts can remotely monitor patients dynamic status and give prompt medical
advice.

56
 5.1 CODING DETAILS AND EFFICIENCY

 Code efficiency is a broad term used to depict the reliability, speed and
programming methodology used in developing codes for an application.
 Code efficiency is directly linked with algorithmic efficiency and the
speed of runtime execution for software. It is the key element in ensuring
high performance.
 Recommendations for code efficiency include:
 To remove unnecessary code or code that goes to redundant processing
 To make use of optimal memory and non-volatile storage
 To ensure the best speed or run time for completing the algorithm
 To make use of reusable components wherever possible
 To make use of error and exception handling at all layers of software,
such as the user interface, logic and data flow
 To create programming code that ensures data integrity and consistency
 To develop programming code that's compliant with the design logic and
flow
 To make use of coding practices applicable to the related software
 To optimize the use of data access and data management practices
To use the best keywords, data types and variables, and other available
programming concepts to implement the related algorithm.

57
 5.2 CODING DETAILS
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Configuration;
using System.Data.SqlClient;
using System.Data;

namespace SkinBank
{
public partial class lg : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
Session["isAuthenticated"] = false;
}
}
protected void Login1_Authenticate(object sender, AuthenticateEventArgs e)
{
ConnectionStringSettings.ConnectionString =
ConfigurationManager.ConnectionStrings["DBConnection"];
SqlConnection DBConnection = new SqlConnection();

try
{
DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();

string loginQuery = @"SELECT COUNT(sysuserno) [COUNT]

FROM users
WHERE userid = @userid
AND password = @password";

SqlCommand DBCommand = new SqlCommand(loginQuery,

DBConnection);
DBCommand.Parameters.AddWithValue("@userid",
lglogin.UserName);
DBCommand.Parameters.AddWithValue("@password",
58
lglogin.Password);
SqlDataAdapter DBAdapter = new SqlDataAdapter(DBCommand);
DataTable DTLogin = new DataTable(); DBAdapter.Fill(DTLogin);

int count = Convert.ToInt32(DTLogin.Rows[0]["COUNT"]);

DBConnection.Close();

if (count == 1)
{
e.Authenticated = true;
Session["isAuthenticated"] = true;
Session["userid"] = lglogin.UserName;
}

}
catch (Exception ex)
{
throw ex;
}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}
}
}
}
}

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Configuration;
using System.Data.SqlClient; using
System.Web.Configuration;using
System.Data;

namespace SkinBank
{
59
 public partial class adddonor : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
GetTableWithInitialData(); GetTableWithInitialPatientData();
//btnAdd.Visible = true;
//btnupdate.Visible = false;

btnAdd.Style.Add("display", "inline");
btnupdate.Style.Add("display", "none");
}
}

protected void btnAdd_Click(object sender, EventArgs e)

{

ConnectionStringSettings connectionString =
WebConfigurationManager.ConnectionStrings["DBConnection"];

SqlConnection DBConnection = new SqlConnection();try

{

DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();

if (btnAdd.Text.ToLower() == "save")
{
String InsertQuery = @"Insert into donordetails
(name, address, dateofbirth, aadharno, contactno,
emailid, relativecontactno, skincolour, skinthickness, status, wishtoddonate,
donationstatus, hivstatus,bloodgroup, allergydetails, cancerdetails, tbdetails,
medicalhistory, deathdate, preservationdate,
skinapplieddate, patientname, createdby, createddate, lupdby, lupddate)
values (@name, @address, @dateofbirth, @aadharno,
@contactno, @emailid, @relativecontactno, @skincolour, @skinthickness,
@status, @wishtoddonate, @donationstatus,
@hivstatus, @bloodgroup, @allergydetails, @cancerdetails, @tbdetails,
@medicalhistory, @deathdate, @preservationdate,
@skinapplieddate, @patientname, @createdby, @createddate, @lupdby,
@lupddate)";

60
 SqlCommand DBCommand = new SqlCommand(InsertQuery,
DBConnection);

DBCommand.Parameters.AddWithValue("@deathdate",
(txtdeathdate.Text == "" ? DBNull.Value : (object)
DateTime.ParseExact(txtdeathdate.Text, "dd'-'MMM'-'yyyy", null)));
DBCommand.Parameters.AddWithValue("@name",
txtdonornm.Text);
DBCommand.Parameters.AddWithValue("@address",
txtaddr.Text);
DBCommand.Parameters.AddWithValue("@dateofbirth",
txtdob.Text);
DBCommand.Parameters.AddWithValue("@aadharno",
txtaadharcard.Text);
DBCommand.Parameters.AddWithValue("@contactno",
txtmobno.Text);
DBCommand.Parameters.AddWithValue("@emailid",
txtemailid.Text);
DBCommand.Parameters.AddWithValue("@relativecontactno",
txtrelativecontactno.Text);
DBCommand.Parameters.AddWithValue("@skincolour",
txtskincolour.Text);
DBCommand.Parameters.AddWithValue("@skinthickness",
txtskinthickness.Text);
DBCommand.Parameters.AddWithValue("@status",
ddlstatus.Text);
DBCommand.Parameters.AddWithValue("@wishtoddonate",
ddlwishtodonatestatus.Text);
DBCommand.Parameters.AddWithValue("@donationstatus",
ddldonationstatus.Text);
DBCommand.Parameters.AddWithValue("@hivstatus",
ddlhivstatus.Text);
DBCommand.Parameters.AddWithValue("@bloodgroup",
ddlbloodgroup.Text);
DBCommand.Parameters.AddWithValue("@allergydetails",
txtallergydetails.Text);
DBCommand.Parameters.AddWithValue("@cancerdetails",
txtcanerdetails.Text);
DBCommand.Parameters.AddWithValue("@tbdetails",
txttbdetails.Text);
DBCommand.Parameters.AddWithValue("@medicalhistory",
txtmedicalhistory.Text);
DBCommand.Parameters.AddWithValue("@preservationdate",
(txtpreservationdate.Text == "" ? DBNull.Value :
(object)DateTime.ParseExact(txtpreservationdate.Text, "dd'-'MMM'-'yyyy",null)));
DBCommand.Parameters.AddWithValue("@skinapplieddate",
61
(txtapplieddate.Text == "" ? DBNull.Value : (object)DateTime.ParseExact(txtapplieddate.Text,
"dd'-'MMM'-'yyyy", null)));
DBCommand.Parameters.AddWithValue("@patientname",
txtpatientname.Text);
DBCommand.Parameters.AddWithValue("@createdby",
Session["userid"]);
DBCommand.Parameters.AddWithValue("@createddate",
DateTime.Now);
DBCommand.Parameters.AddWithValue("@lupdby",
Session["userid"]);
DBCommand.Parameters.AddWithValue("@lupddate",
DateTime.Now);
int noOfRowsAffected =
DBCommand.ExecuteNonQuery();if (noOfRowsAffected == 1)
{
"name",ScriptManager.RegisterClientScriptBlock(this, this.GetType(),

"JavaScript: alert ('Donor details added successfully');", true);

}
DBConnection.Close();

GetTableWithInitialData();
}
}
catch (Exception ex)
{

"name",ScriptManager.RegisterClientScriptBlock(this, this.GetType(), "JavaScript: alert

('Error occurred while saving donor details.');", true);
}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}

initializeFieldsValues();
}
}
protected void btnCancel_Click(object sender, EventArgs e)
{
initializeFieldsValues();
}
private void initializeFieldsValues()
62
 {
txtaadharcard.Text = "";
txtaddr.Text = "";
txtdob.Text = "";
txtemailid.Text = "";
txtmobno.Text = "";
txtdonornm.Text = "";
txtrelativecontactno.Text = "";
txtskincolour.Text = "";
txtskinthickness.Text = "";
txtdonorno.Text = "";
txtallergydetails.Text = "";
txtapplieddate.Text = "";
txtcanerdetails.Text = "";
txtdeathdate.Text = "";
txtmedicalhistory.Text = "";
txtpatientname.Text = "";
txtpreservationdate.Text = ""; txttbdetails.Text
= ""; ddlbloodgroup.SelectedIndex = 0;
ddldonationstatus.SelectedIndex = 0;
ddlhivstatus.SelectedIndex = 0;
ddlstatus.SelectedIndex = 0;
ddlwishtodonatestatus.SelectedIndex = 0;

btnAdd.Style.Add("display", "inline");
btnupdate.Style.Add("display", "none");
}

public void GetTableWithInitialData() // this might be your sp for select

{
ConnectionStringSettings connectionString =
ConfigurationManager.ConnectionStrings["DBConnection"];
SqlConnection DBConnection = new SqlConnection();
DataTable table = new DataTable();

try
{
DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();

string loginQuery = @"SELECT *

FROM donordetails";

SqlCommand DBCommand = new SqlCommand(loginQuery,

63
DBConnection);
SqlDataAdapter DBAdapter = new SqlDataAdapter(DBCommand);

DBAdapter.Fill(table);

DBConnection.Close();
}
catch (Exception ex)
{

}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}
}

if (table.Rows.Count == 0)
{
ScriptManager.RegisterClientScriptBlock(this, this.GetType(), "alert",
"alert('No existing donors found.');", true);
}

{
gvdonordetails.DataSource = table;
gvdonordetails.DataBind();
}
}

protected void gridView_RowDeleting(object sender,

GridViewDeleteEventArgs e)
{
Label lbldonorno =
(Label)gvdonordetails.Rows[e.RowIndex].FindControl("lbldonorno");

ConnectionStringSettings connectionString =
ConfigurationManager.ConnectionStrings["DBConnection"];
SqlConnection DBConnection = new SqlConnection();
DataTable table = new DataTable();
string message = string.Empty;

try
{
64
 DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();

string loginQuery = @"DELETE FROM donordetails WHERE

donorno = @donorno";

SqlCommand DBCommand = new SqlCommand(loginQuery,

DBConnection);
DBCommand.Parameters.AddWithValue("@donorno",lbldonorno.Text);
int rowsAffected = DBCommand.ExecuteNonQuery();

DBConnection.Close();

message = "Donor details deleted succcessfully";

GetTableWithInitialData();
initializeFieldsValues();

}
catch (Exception ex)
{
message = "Error occurred while deleting the donor";
}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}
}

ScriptManager.RegisterClientScriptBlock(this, this.GetType(),
"deletealert", "javascript: alert('" + message + "');", true);
}

protected void gridView_RowEditing(object sender,

GridViewEditEventArgs e)
{
Label lbldonorno =
(Label)gvdonordetails.Rows[e.NewEditIndex].FindControl("lbldonorno");

ConnectionStringSettings connectionString =
ConfigurationManager.ConnectionStrings["DBConnection"];
SqlConnection DBConnection = new SqlConnection();
65
 DataTable table = new DataTable();
string message = string.Empty;

try
{
DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();
string loginQuery = @"SELECT * FROM donordetails WHERE
donorno = @donorno";

SqlCommand DBCommand = new SqlCommand(loginQuery,

DBConnection);
DBCommand.Parameters.AddWithValue("@donorno",
lbldonorno.Text);

SqlDataAdapter DBAdapter = new SqlDataAdapter(DBCommand);

DBAdapter.Fill(table);

DBConnection.Close();

txtdonornm.Text = table.Rows[0]["name"].ToString();
txtaddr.Text = table.Rows[0]["address"].ToString();
txtaadharcard.Text = table.Rows[0]["aadharno"].ToString();
txtmobno.Text = table.Rows[0]["contactno"].ToString();
txtemailid.Text = table.Rows[0]["emailid"].ToString();
txtrelativecontactno.Text =
table.Rows[0]["relativecontactno"].ToString();
txtskincolour.Text = table.Rows[0]["skincolour"].ToString();
txtskinthickness.Text = table.Rows[0]["skinthickness"].ToString();
txtdonorno.Text = lbldonorno.Text;
ddlstatus.Text = table.Rows[0]["status"].ToString();
txtallergydetails.Text = table.Rows[0]["allergydetails"].ToString();
txtapplieddate.Text = (table.Rows[0]["skinapplieddate"] ==
DBNull.Value ? ""
:Convert.ToDateTime(table.Rows[0]["skinapplieddate"]).ToString("dd'-
'MMM'-'yyyy"));
txtcanerdetails.Text = table.Rows[0]["cancerdetails"].ToString(); txtdeathdate.Text
= (table.Rows[0]["deathdate"] == DBNull.Value ?
"" : Convert.ToDateTime(table.Rows[0]["deathdate"]).ToString("dd'-'MMM'-
'yyyy"));
txtdob.Text = (table.Rows[0]["dateofbirth"] == DBNull.Value ? "" :
Convert.ToDateTime(table.Rows[0]["dateofbirth"]).ToString("dd'-'MMM'-
'yyyy"));
txtmedicalhistory.Text = table.Rows[0]["medicalhistory"].ToString();
66
 txtpatientname.Text = table.Rows[0]["patientname"].ToString();
txtpreservationdate.Text = (table.Rows[0]["preservationdate"] ==
DBNull.Value ? "" :
Convert.ToDateTime(table.Rows[0]["preservationdate"]).ToString("dd'-
'MMM'-'yyyy"));
txttbdetails.Text = table.Rows[0]["tbdetails"].ToString();

ddlbloodgroup.Text = table.Rows[0]["bloodgroup"].ToString();
ddldonationstatus.Text = table.Rows[0]["donationstatus"].ToString();
ddlhivstatus.Text = table.Rows[0]["hivstatus"].ToString(); ddlstatus.Text
= table.Rows[0]["status"].ToString(); ddlwishtodonatestatus.Text =
table.Rows[0]["wishtoddonate"].ToString();

btnupdate.Style.Add("display", "inline");
btnAdd.Style.Add("display", "none");
}
catch (Exception ex)
{
message = "Error occurred while retrieving the donor details";
ScriptManager.RegisterClientScriptBlock(this, this.GetType(),
"editmsg", "javascript: alert('" + message + "');", true);
}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}
}
}

protected void btnupdate_Click(object sender, EventArgs e)

{
ConnectionStringSettings connectionString =
WebConfigurationManager.ConnectionStrings["DBConnection"];
SqlConnection DBConnection = new SqlConnection();

try
{
DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();
String UpdateQuery = "";

UpdateQuery = @"UPDATE donordetails

67
 SET name = @name,
address = @address,
dateofbirth = @dateofbirth,
aadharno = @aadharno,
contactno = @contactno,
emailid = @emailid,
relativecontactno = @relativecontactno,
skincolour = @skincolour, skinthickness =
@skinthickness,
status = @status,
wishtoddonate = @wishtoddonate,
donationstatus = @donationstatus,
hivstatus = @hivstatus, bloodgroup
= @bloodgroup, allergydetails =
@allergydetails, cancerdetails =
@cancerdetails, tbdetails =
@tbdetails, medicalhistory =
@medicalhistory,deathdate =
@deathdate,
preservationdate = @preservationdate,
skinapplieddate = @skinapplieddate,
patientname = @patientname,
lupdby = @lupdby,
lupddate = @lupddate
WHERE donorno = @donorno";

SqlCommand DBCommand = new SqlCommand(UpdateQuery,

DBConnection);

DBCommand.Parameters.AddWithValue("@deathdate",
(txtdeathdate.Text == "" ? DBNull.Value :
(object)DateTime.ParseExact(txtdeathdate.Text, "dd'-'MMM'-'yyyy", null)));
DBCommand.Parameters.AddWithValue("@name",
txtdonornm.Text);
DBCommand.Parameters.AddWithValue("@address", txtaddr.Text);
DBCommand.Parameters.AddWithValue("@dateofbirth",
txtdob.Text);
DBCommand.Parameters.AddWithValue("@aadharno",
txtaadharcard.Text);
DBCommand.Parameters.AddWithValue("@contactno",
txtmobno.Text);
DBCommand.Parameters.AddWithValue("@emailid",
txtemailid.Text);
DBCommand.Parameters.AddWithValue("@relativecontactno",
txtrelativecontactno.Text);
DBCommand.Parameters.AddWithValue("@skincolour",
68
txtskincolour.Text);
DBCommand.Parameters.AddWithValue("@skinthickness",txtskinthickness.Text);
DBCommand.Parameters.AddWithValue("@status", ddlstatus.Text);
DBCommand.Parameters.AddWithValue("@wishtoddonate",
ddlwishtodonatestatus.Text);
DBCommand.Parameters.AddWithValue("@donationstatus",
ddldonationstatus.Text);
DBCommand.Parameters.AddWithValue("@hivstatus",
ddlhivstatus.Text);
DBCommand.Parameters.AddWithValue("@bloodgroup",ddlbloodgroup.Text);
DBCommand.Parameters.AddWithValue("@allergydetails",
txtallergydetails.Text);
DBCommand.Parameters.AddWithValue("@cancerdetails",
txtcanerdetails.Text);
DBCommand.Parameters.AddWithValue("@tbdetails",
txttbdetails.Text);
DBCommand.Parameters.AddWithValue("@medicalhistory",
txtmedicalhistory.Text);
DBCommand.Parameters.AddWithValue("@preservationdate",
(txtpreservationdate.Text == "" ? DBNull.Value :
(object)DateTime.ParseExact(txtpreservationdate.Text, "dd'-'MMM'-'yyyy",null)));
DBCommand.Parameters.AddWithValue("@skinapplieddate", (txtapplieddate.Text
== "" ? DBNull.Value : (object)DateTime.ParseExact(txtapplieddate.Text, "dd'-'MMM'-'yyyy",
null)));
DBCommand.Parameters.AddWithValue("@patientname",
txtpatientname.Text);
DBCommand.Parameters.AddWithValue("@createdby",
Session["userid"]);
DBCommand.Parameters.AddWithValue("@createddate",
DateTime.Now);
DBCommand.Parameters.AddWithValue("@lupdby",
Session["userid"]);
DBCommand.Parameters.AddWithValue("@lupddate",
DateTime.Now);

DBCommand.Parameters.AddWithValue("@donorno",
txtdonorno.Text);

int noOfRowsAffected = DBCommand.ExecuteNonQuery();

if (noOfRowsAffected == 1)
{
ScriptManager.RegisterClientScriptBlock(this, this.GetType(),
"name",
"JavaScript: alert ('Donor Details updated successfully');", true);
}
69
 DBConnection.Close();
}

catch (Exception ex)

{
"name",ScriptManager.RegisterClientScriptBlock(this, this.GetType(),

"JavaScript: alert ('Error occurred while updating the donor

details.');", true);
}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}

initializeFieldsValues();
GetTableWithInitialData();
}
}

protected void gridView1_RowCommand(object sender,

GridViewCommandEventArgs e)
{
if (e.CommandName == "Select")
{
GridViewRow row =
(GridViewRow)(((LinkButton)e.CommandSource).NamingContainer);

txtpatientname.Text = (row.FindControl("lblName") as Label).Text;

pnlpatientdetail_CollapsiblePanelExtender.Collapsed = true;
pnlpatientdetail_CollapsiblePanelExtender.ClientState = "true";
}
}

public void GetTableWithInitialPatientData() // this might be your sp forselect

{
ConnectionStringSettings connectionString =
ConfigurationManager.ConnectionStrings["DBConnection"];
SqlConnection DBConnection = new SqlConnection();
DataTable table = new DataTable();

try
70
 {
DBConnection.ConnectionString =
connectionString.ConnectionString;
DBConnection.Open();

string loginQuery = @"SELECT *

FROM patientdetails";

SqlCommand DBCommand = new SqlCommand(loginQuery,

DBConnection);
SqlDataAdapter DBAdapter = new SqlDataAdapter(DBCommand);

DBAdapter.Fill(table);

DBConnection.Close();
}
catch (Exception ex)
{

}
finally
{
if (DBConnection.State == System.Data.ConnectionState.Open)
{
DBConnection.Close();
}
}

if (table.Rows.Count == 0)
{
ScriptManager.RegisterClientScriptBlock(this, this.GetType(), "alert",
"alert('No existing patients found.');", true);

{
gvpatientdetails.DataSource = table;
gvpatientdetails.DataBind();
}
}

71
 5.2.1 CODE EFFICIENCY

 Code efficiency is a broad term used to depict the reliability, speed and
programming methodology used in developing codes for an application.
 Code efficiency is directly linked with algorithmic efficiency and the
speed of runtime execution for software.
 It is the key element in ensuring high performance. The goal of code
efficiency is to reduce resource consumption and completion time as much
as possible with minimum risk to the business or operating environment.
 The software product quality can be accessed and evaluated with the help
of the efficiency of the code used.

72
5.3 TESTING APPROACHES
Test Approach:
 A test approach is the test strategy implementation of a project, defines
how testing would be carried out. Test approach has two techniques:
 Proactive - An approach in which the test design process is initiated as
early as possible in order to find and fix the defects before the build is
created.
 Reactive - An approach in which the testing is not started until after
design and coding are completed.
 Different Test approaches:
 There are many strategies that a project can adopt depending on the
context and some of them are:
 Dynamic and heuristic approaches
 Consultative approaches
 Model-based approach that uses statistical information about failure
rates.
 Approaches based on risk-based testing where the entire development
takes place based on the risk
 Methodical approach, which is based on failures.
 Standard-compliant approach specified by industry-specific standards.
 Factors to be considered:
 Risks of product or risk of failure or the environment and the company.
 Expertise and experience of the people in the proposed tools and
techniques.
 Regulatory and legal aspects, such as external and internal regulations of
the development process.
 The nature of the product and the domain

73
5.3.1 UNIT TESTING

 UNIT TESTING is a level of software testing where individual units/

components of a software are tested.
 The purpose is to validate that each unit of the software performs as
designed. A unit is the smallest testable part of any software. It usually
has one or a few inputs and usually a single output.
 Unit testing, a testing technique using which individual modules are
tested to determine if there are any issues by the developer himself. It is
concerned with functional correctness of the standalone modules.
 The main aim is to isolate each unit of the system to identify, analyse and
fix the defects.
Unit Testing - Advantages:
• Reduces Defects in the Newly developed features or reduces bugs when
changing the existing functionality.

• Reduces Cost of Testing as defects are captured in very early phase

 Improves design and allows better refactoring of code.

 Unit Tests, when integrated with build gives the quality of the build as well.

Unit Testing Techniques:

Black Box Testing - Using which the user interface, input and output are tested.White
Box Testing - used to test each one of those functions’ behaviour is tested.
Gray Box Testing - Used to execute tests, risks and assessment methods.

74
5.3.2 INTEGRATION TESTING

 INTEGRATION TESTING is a level of software testing where

individual units are combined and tested as a group.
 The purpose of this level of testing is to expose faults in the interaction
between integrated units.
 Test drivers and test stubs are used to assist in Integration Testing.
 Upon completion of unit testing, the units or modules are to be integrated
which gives raise to integration testing.
 The purpose of integration testing is to verify the functional,
performance, and reliability between the modules that are integrated.
Integration Strategies:
• Big-Bang Integration

• Top Down Integration

• Bottom Up Integration
Hybrid Integration

75
5.2.1 BETA TESTING

 Beta testing also known as user testing takes place at the end users site by
the end users to validate the usability, functionality, compatibility, and
reliability testing.
 Beta testing adds value to the software development life cycle as it allows
the "real" customer an opportunity to provide inputs into the design,
functionality, and usability of a product.
 These inputs are not only critical to the success of the product but also an
investment into future products when the gathered data is managed
effectively.
 Beta Testing - In SDLC
 The following diagram explains the fitment of Beta testing in the
software development life cycle:

76
5.4 MODIFICATIONS AND IMPROVEMENTS

 An adjustment made to an existing product, usually made for greater

appeal or functionality.
 A modification may include a change to a product's shape, adding a

feature or improving its performance. Often a product modification is

accompanied by a change in packaging
 Modification of image
 Modification of text
 Adding the email to sent the mail to donor and patients
 Adding of Regular expression

77
5.5 TEST CASE

 Test case Design technique

 Following are the typical design techniques in software engineering:
 1.Deriving test cases directly from a requirement specification or black
box test design technique.
The Techniques include:
 Boundary Value Analysis
 Equivalence Partitioning
 Decision Table Testing
 State Transition Diagrams
 Use Case Testing

2. Deriving test cases directly from the structure of a component or system:

 Statement Coverage
 Branch Coverage
 Path Coverage
 LCSAJ Testing
3. Deriving test cases based on testers experience on similar systems or testers
intuition:
 Error Guessing
 Exploratory Testing

78
Test Case Chart
Test Steps to be Expected Result Actual Status
case executed Result

No

Click on Login New user user New window will

registrationwindow will open butthere is error
1 Fail
open

Click on Login The username and User entered in the

(username and passwordpage will open website
2 password) Pass

Enter username If username is more than Error will occur and

more than of 5 5 character unsuccessfulmessage
3 character willdisplay Fail

Enter Username It should display succesfull Succesfull message

of 5 characters
4 Pass

Blank field for Should ask to Enter username

Username enterusername
5 Fail

Check for Should give an error as

minimum length password should be of
6 of password 5characters Success Pass

Enter number in It should not allow the It is not allowing

username field number in in username
7 field Fail

Enter the details Should give details of Informationwill be

of patient thepatient displayed
8 Pass

Enter information The skin bank will Informationwill be

that the patient providethe detail to the display
9 wants from theSkin user Pass
Bank

79
 Enter donor The SkinBank will display Information
details the donor details will bedisplay
10 Pass

Enter information The skinbank will Informationwill be

of skin which is displayedthe detail of skin displayed
11 suffering from related issue Pass
diseases etc

Login as Admin Recognize the user as Display all the details

adminand display patients tothe admin
12 and donors record Pass

Displaying Displaying Displayingthe detail

Hospital hospital
13 Information Pass
information

Enter Skin Display the detail of Displayingthe detail

Preservation date skinpreservation
14 Pass

Enter skin Display the information Displayingthe detail

applied date ofapplied date
15 Pass

Enter email id Message should be sent Email is currently

onemail present on
16 gmail accont Pass

80
 Chapter 6

RESULTS AND DISCUSSION

6.1 OUTPUT

81
ABOUT US

82
SERVICES

83
CONTACT

84
LOGIN

85
PATIENT DETAILS

86
HOSPITALS DETAILS

87
DONORS DETAILS

88
PATIENTS REPORT

89
DONOR REPORT

90
SEARCH DONOR

91
6.2 USER DOCUMENTATION

 The Skin Bank management system is designed to reduce the manual

work in the Skin bank and implement easy to use and simple website.
 For one to run this website they should have Microsoft visual studio 2010
that’s it!
 The website supports of sql server.
 There should be a connectivity of visual studio and sql express.
 Then on any browser (google chrome recommended) type localhost/(the

name of the folder in which the contents are saved).

92
 CHAPTER 7

CONCLUSIONS

CONCLUSIONS

 The main purpose of this project was to implement and providing and
donating of skin process which is very effective in today's world.
 This project will help to keep a check on availability of donor and it is
very helpful for hospitals as well as for intended patients.
 One can remain care-free as this system updates the status donor patient
and types of skin and amount of skin on time to time basis.

93
 7.1 SIGNIFICANCE OF SYSTEM

 Skin Bank management system helps in maintaining records and track of

skin in skin bank.
 This helps patients to spot any particular Skin at any given time on the
website.
 It’s easy to use interface and immediate reporting make things easier for
the system.
 Members can keep track of different records such as:

• Preservation Date

• Applied Date

• Number of Patients enrolled for

• Number of Skin available

 The website makes sure about the speedy and flawless operation and
categorizing of the routines as per different genres.
 Such a structure, also make available an option for the admin to collect all
the basic details displayed in the database.

94
7.2 LIMITATIONS OF THE SYSTEM

 Using manual Skin Bank, we have to make the whole Donors and
patients report which contains the record of the consignments. It
requires more time & more calculation.

 In Skin Bank the rate of each color of skin is fixed. The rate of skin
is depending on the amount of the skin and type and color. So, the
calculation of rate & monthly income is not done easily.

 In Skin Bank, the payment is made in credit or cash. So, for the
billing procedure for the customer, we have to refer all the records
in donating ang providing of Skin Report. For these reasons this
task is more time consuming.

 This system is only meant for individual company.

 It cannot be used for merging multiple companies.


95


7.3 FUTURE SCOPE OF PROJECT

 One of the major future scope is making our system Live.

 Connecting Skin Bank management across Mumbai to a common data
center which will provide a success step.

 And we need to create a user side so that user can search the programmes
like on google and we need to add feature of pre-enrollment.

96
7.4 REFERENCES

Sr no Book Author Publication

Foundation of Dorothy
1 Software Graham
testing
2 Asp.net with Anne Murachs
C# Boehm

Also:

 http://www.google.com
 http://www.uml.org/
 http://www.w3schools.com
 http://lucidchart.com/
 http://asp.net-tutorials.com/
 www.studentprojectcode.com
 www.bestprojectsidea.com

97