Vishu
Vishu
A report submitted in partial fulfilment of the requirements for the Award of Diploma
in
Information Technology Engineering
By
Under Supervision of
Mr. S.D.Pandhare
Founder
(POLY) KORTI.
2024-25
1
DEPARTMENT OF INFORMATION TECHNOLOGY ENGINEERING
CERTIFICATE
This is to certify that the ―Industrial Training report submitted by Mr. Vishvajit
Eknath Magar (Enrollment No: 2215230096 ) is work done by him and submitted during
2024- 25 academic year, in partial fulfilment of the requirements for the award of DIPLOMA
in INFORMATION TECHNOLOGY ENGINEERING, at Shaurya Softech
solution,Akluj.
Date: / /
2
ACKNOWLEDGEMENT
I also would like all the people that worked along with me Shaurya Softech
solution,Akluj with their patience and openness they created an enjoyable working
environment.
It is indeed with a great sense of pleasure and immense sense of gratitude that I
acknowledge the help of these individuals.
I am highly indebted to Principal Mr. Prof. Londhe V.H, for the facilities provided to
accomplish this internship.
Primarily, I will submit our gratitude and sincere thanks to Internship Co-ordinator Mr. V. N. Baad , for their
constant motivation and support during the internship.
I am extremely great full to my department staff members and friends who helped me
in successful completion of this internship.
Last but not the least, I would like to thank all our Friends and Family members who
have always been there to support and helped us to complete this internship in time.
3
ABSTRACT
The Company:
The Institute combines pioneering research with top class education. An innovative curriculum
allows the student flexibility in selecting courses and projects. Students, even at the
undergraduate level, get to participate in on-going research and technology development - an
opportunity unprecedented in India. As a result, a vibrant undergraduate programmer co-
exists with a strong postgraduate programmer.
Methodology:
This project we can display the calendar by importing the calendar module to our
program. Import the necessary libraries. Create the main GUI window. Define functions to
navigate through months and display the calendar and implement a graphical representation of
the calendar using labels or text widgets.
4
Benefits to the company / institution through
your report:-
1. Introduction 1
2. Analysis 2
2.1 Requirement analysis 2
2.2 Interviews 3
2.2.1 Interviewees
2.3 How the interviews were conducted 4
2.4 Interview findings 4
3. System requirements specifications
3.1 System configuration 6
3.2 Software requirements 6
3.3 Hardware requirements 6
4. Technology
4.1 PYTHON 7
5. Coding 8
6. Output 11
7. Conclusion 12
8. Reference 13
1. INTRODUCTION
Creating a Graphical User Interface (GUI) Patient Ragistration Form using Tkinter can be a
rewarding project, allowing you to develop a user-friendly Patient Ragistration Form application
with Python. Tkinter is a built-in Python library for creating graphical user interfaces, making it
an excellent choice for developing desktop applications.
In this project, we'll utilize Tkinter to design the interface for our Patient Ragistration Form and
integrate functionality using Python's built-in Patient Ragistration Form module. The Patient
Ragistration Form module provides utilities for generating various types of Patient Ragistration
Form, making it suitable for our purposes.
These general objectives have been met through a series of activities that include in-depth
interviews followed by a questionnaire survey and a workshop. The specific objectives of thes e
activities are as follows:
In this project, we'll embark on a step-by-step journey to construct a GUI Patient Ragistration
Form using Tkinter. Here's an outline of our approach
1. 1. Import Tkinter: Start by importing the Tkinter module and any additional modules you
may need for the project, such as Patient Ragistration Form.
2. Create the Main Window: Initialize the main window for our Patient Ragistration Form
application using Tkinter. This windowwill serve as the container for all other GUI elements.
3. Design the Patient Ragistration Form Interface: Use Tkinter widgets like labels, buttons, and
frames to design the layout of our calendar interface. Consider how users will interact with the
Patient Ragistration Form and how the interface should look.
4. Implement Patient Ragistration Form Logic: Utilize the Patient Ragistration Form module to
implement logic for displaying dates, navigating between months, and selecting dates. We'll need
functions to update the Patient Ragistration Form display based on user actions.
6. Testing and Refinement: Thoroughly test our GUI calendar application to ensure it works
as expected. Makeany necessary refinements to improve the user experience and fix any bugs
that arise during testing.
7. Documentation and Deployment: Document our code with comments and docstrings to
make it easy for othersto understand and maintain. Once our calendar is ready, we can package it
for deployment so that others can useit.
2. ANALYSIS
Design a user-friendly Patient Ragistration Form interface that is easy to navigate and understand
adapts well to differentscreen sizes and resolutions for a consistent user experience
across devices.
Ragistration Form application that meets the needs and expectations of its users
while providing
This report is based upon interviews with individuals who are knowledgeable about and
experienced with process automation. We performed a qualitative analysis of these interviews
to arrive at the findings reported here. The material in this section closely follows
thatpresented in an earlier report [Christie 96].
Three independent organizations were involved in performing the interviews reported here:
The SEI, Nolan Norton and Company (a division of KPMG Peat Marwick), and CapGemini
Sogeti (located in Grenoble, France).
An extensive list of candidates was identified early on, including end-user organizations,
commercial and in-house developers, and researchers. Our original goal was to interview
mostly end users of process automation. However, that was not to be. Because of the
immaturity of the technology, we interacted with relatively few experienced end users of the
technology. Most of our interviews were with people who were involved in developing and
implementing process-centered environments (PCEs).
A total of 14 interviews were conducted with 12 projects.1in the large majority of these
interview sessions, two interviewers were present. The number of interviewees in each
interview ranged from one to eight. All interviews were taped to ensure that the comments
were recorded accurately. The interviews took approximately 36 hours with an average
lengthof 2.4 hours per interview. All in all, the interviews yielded 150 pages of transcripts.
In one organization, two different projects were interviewed. With two other projects,
multiple interviews were conducted.
A standard script supported each interview. This script provided a consistent framework and
ensured that we would have comparable information from each of the interviews. While the
questions were used to support the interviews and to ensure coverage, they were not followed
mechanically; areas of interest were often probed in depth. Christie provides further details of
the interview format [Christie 96].
The interviewees represented one or more automation efforts that, loosely speaking, can be
seen as pilot projects. These projects ranged in size from fewer than 10 to more than 60people.
For purposes of discussion, the numbers cited include the personnel for whom the automation
was intended, as well as the developers of the automation if they are part of the same
organization. Typical project size was toward the low end.
While we made no attempt to measure formally the process maturity level of the
organizations/projects interviewed, some had previously undergone formal process
assessments using the SEI Capability Maturity Model (CMM). These projects ranged in
maturity from level 1 (ad hoc/chaotic) to level 5 (optimizing). However, most can be
characterized as relatively immature (at or below level 2). Other projects had not been
assessed formally, but many characterized themselves as having a poorly defined set of
software development processes. Two projects were attempting software development
activities for the first time.
Of the twelve projects interviewed (seven currently active, four inactive, one experimental),
only two were far enough along for the automation to be considered institutionalized. In one
case, the automation was associated with a company that developed and distributed a
configuration management product. This product has significant process capability that is used
to support further development of the product. The other organization that effectively adopted
PCE technology did so to support software problem tracking.
Four points may be made about the interviews and the findings derived from them. First,
because of the immaturity of the technology, we interviewed few people who could be
considered experienced end users of the technology. The great majority of interviewees were
either developers of process-centered environments, developers of the process tools
fromwhich PCEs can be built, or managers of development projects. Second, the findings not
only surfaced problems but identified potential solutions to these problems. We hope that this
information will be useful to organizations intending to build and use PCEs. Third,
interviewees’ experiences were not always consistent, and these inconsistencies may at times
be reflected in the report.
Fourth, as might be expected, we found that many of the adoption issues we identified
have much in common with adoption issues associated with other technology areas.
The findings fall into three major categories
• drivers and inhibitors
• contributors to success
• technology issues
In the following discussions, we make heavy use of quotes (indicated in italics) from the
interviews.
A major reason for this is that interviewees were surprisingly frank in giving us their views
about process automation and how their organizations were dealing with it.
3. SYSTEM REQUIREMENTS SPECIFICATIONS
The software requirement specification can produce at the culmination of the analysis task.
The function and performance allocated to software as part of system engineering are refined
by established a complete information description, a detailed functional description, a
representation of system behavior, and indication of performance and design constrain,
appropriate validate criteria, and other information pertinent to requirements.
Pycharm : Python3.12.
PYTHON:
Python’s surge in popularity has been due partly to its clear and concise
syntax, which enhances readability. Python emphasizes code clarity and promotes a
sense of elegance. It is prescriptive in upholding these attributes. For example, Python
has a maximum recommended line length of 79 characters and a specific indentation
style, which encourages the use of four white spaces while prohibiting space and tab
mixing. Python’s versatility is another notable strength. Although it is primarily an
object- oriented language, Python can also be harnessed for procedural or functional
applications.
Code:-
import tkinter as tk
from tkinter import messagebox
# Title label
title_label = tk.Label(root, text="Patient Registration Form", font=("Arial", 16, "bold"),
bg="#F5F5F5")
title_label.pack(pady=20)
# Submit button
submit_button = tk.Button(root, text="Submit", font=("Arial", 12), width=30,
bg="#4CAF50", fg="white",
command=submit_form)
submit_button.pack(pady=20)
This can be a powerful tool to help healthcare organizations improve their processes
and streamline their operations. It can provide an integrated, comprehensive solution
to managing patient records, billing and scheduling, as well as provide real-time
insights into hospital performance.
References:-
https://www.jotform.com/form-templates/registration/patient-registration-form-templates
https://www.typeform.com/templates/t/patient-registration-form-template/