AMERICAN INTERNATIONAL UNIVERSITY–BANGLADESH (AIUB)

Dept. of Computer Science

Faculty of Science and Technology

CSC2210: OBJECT ORIENTED PROGRAMMING 2

Fall 2024-2025
Section: F
Group No: 0512
Project Report On
Project Name: MediTrack
Supervised By
Kazi Sadia

Submitted By:
Name ID
1. ABID RAHMAN 22-49280-3
2. MAHMUDUL MORSALIN ANTOR 22-48388-3
3. MST. NISHAT ROMMAN 22-48809-3

Obtained Marks for CO2 and CO3 (Description given in the following page)

Assessment Not Attended/ Inadequate Average Good Excellent

Criteria Incorrect (0) (1-2) (3) (4) (5)
Evaluation Criteria (CO2) Total = Evaluation Criteria (CO3) Total =
Organization of the
Requirement fulfillment
application
Representation and Integration
Validation
of Database

Verification Graphical User Interface

CO2: Display and verify the mean of a real-life Project using the concepts of C# Graphical User Interface based environment
with database integration to depict a desktop-based application.
Assessment Not Attended/ Inadequate Average Good Excellent
Criteria Incorrect (0) (1-2) (3) (4) (5)
Evaluation Criteria Evaluation Definition
Fails to Demonstrates Presents a basic Effectively Exhibits an
demonstrate any limited depiction of a demonstrates a exceptional
understanding of understanding of real-life scenario- realistic scenario- understanding of
real-life scenario- real-life scenario- based project and based project and real-life scenario-
based project based project identifies some accurately based project
development or development and functional identifies most development and
functional functional requirements. functional accurately
requirement requirement However, the requirements. identifies all
identification. identification. project lacks The project is functional
There is no The project depth or well-developed requirements.
attempt to depict depicted lacks complexity, and with appropriate The project is
Requirement
a project or coherence or some functional complexity, and meticulously
fulfillment
identify relevance to real- requirements may functional developed with
functional life scenarios, be vaguely requirements are thorough
requirements and functional defined or clearly articulated attention to
accurately. requirements are missing key with relevant detail, reflecting
inaccurately details. details. a comprehensive
identified or understanding of
insufficiently Object-Oriented
described. Programming
project
development
activities.
Fails to Demonstrates Shows a basic Effectively Exhibits an
demonstrate any limited understanding of demonstrates the exceptional
understanding or understanding of validation forms use of validation understanding
implementation validation forms and data forms and and
of validation and data validation implements data implementation
forms in their validation techniques. They validation of validation
system. There is techniques. attempt to techniques. forms and data
no attempt to deal While some implement Validation is validation
with data attempt may be validation, but mostly accurate techniques.
validation, and made to some aspects and Validation is
validation implement may be missing comprehensive, meticulously
Validation requirements are validation, it is or incorrectly ensuring the implemented
completely incomplete or implemented, proper handling with thorough
ignored or poorly executed, resulting in of data input and attention to
incorrectly leading to partial or verification in the detail, ensuring
applied. inadequate inconsistent system. robust data
handling of data handling of data validation
validation. validation. procedures and
contributing to
the overall
reliability and
integrity of the
system.
Verification Fails to Demonstrates Shows a basic Identifies and Exhibits an
demonstrate any limited understanding of verifies system exceptional
attempt to verify understanding of verification data, ensuring understanding of
the system data verification processes and proper functional verification
or functional processes and attempts to verify requirements are processes and
requirements. data flow in the system data. met. Verification meticulously
There is no system. However, efforts are mostly verifies system
evidence of Verification verification accurate and data. Verification
understanding or attempts are efforts may be thorough, with efforts are
implementation incomplete or inconsistent or attention to comprehensive
 of verification inaccurate, and lack ensuring data and precise, with
processes, and there is thoroughness, integrity and a keen focus on
data flow is not insufficient and there may be appropriate data ensuring all
considered. consideration gaps in ensuring flow within the functional
given to ensuring proper functional system. requirements are
data integrity and requirements and met and
functionality. data flow. maintaining
proper data flow
throughout the
system.

CO3: Prepare and Explain a real life desktop based application synthesizing several component of C# along with development
tools to adhere the given requirements.
Assessment Not Attended/ Inadequate Average Good Excellent
Criteria Incorrect (0) (1-2) (3) (4) (5)
Evaluation Criteria Evaluation Definition
Fails to identify Limited Lacks depth or Consider and Generalize and
any suitable real understanding relevance to OOP integrate the idea exhibits an
time application about the project project of several core exceptional
or requirements scopes and development aspects of the understanding of
for project scenarios or activities and project along project
development identification of may contain with relevance to preparation
activities related functional inaccuracies. real-life according to a to
Organization of the
to OOP. requirements. Real-life scenarios. real-life
application
scenarios are Demonstrating a scenarios. Also
mentioned, but solid contains proper
the discussion understanding of and insightful
lacks depth or the application identification of
clarity. presentation. the system which
is comprehensive
and precise.
Fails to identify Limited Lacks depth or Integrate the Exhibits an
and present any understanding of relevance to database with the exceptional
understanding or the database database forms properly understanding
implementation concepts or their integration with and implements it and
of database. Also proper way of the application. with proper implementation
failed to integrate using in a real Shows a basic validation which of database
the data with the time project. understanding but is mostly ensuring
Representation and project itself. While some some aspects accurate and attention to
Integration of Database attempt may be may be missing comprehensive, detail, and robust
made to or incorrectly ensuring the data manipulation
implement but it implemented, proper handling procedures and
is incomplete or resulting in of data input and contributing to
poorly executed, partial or verification along the overall
leading to inconsistency. with general clarity.
inadequate May lack proper normalization.
design. normalization.
Fails to present or Limited Shows a basic Effectively Exhibits an
prepare GUI understanding of understanding of identifies and exceptional work
based application graphical user creating user meet the consider design following
interfaces. There interfaces. Lack interfaces. Most the simplicity. a high standard of
is no evidence of of design of them are Design related simple and
creating or knowledge. Very interconnected works are mostly elegant work.
Graphical User
integrating such poor attempt to but maybe some accurate and Several controls
Interface
things according make such things of them lack it. taken proper and mechanism
to their which are However, most of attention to has been
usefulness. currently obsolete it can be ensuring a user- organized in a
or can’t be described as user friendly coherent preferred way
identified as friendly. system. according to the
coherent. coherent usage .
Table of Contents: Page no.

1. Chapter: 01 (Introduction)----------------------------------------------------------------------- 03
2. Chapter: 02 (User Story)------------------------------------------------------------------------- 03
3. Chapter: 03a (ER Diagram)---------------------------------------------------------------------- 05
4. Chapter: 03b (SQL Queries)--------------------------------------------------------------------- 06
5. Chapter: 04 (Screenshots)------------------------------------------------------------------------ 09
Chapter 01: Introduction

Managing inventory in a pharmacy is a challenging task that often leads to inefficiencies,

errors, and financial losses due to expired or misplaced medicines. MediTrack, a Pharmacy
Inventory Management System, aims to streamline and automate pharmacy operations by
enabling real-time stock tracking, medicine categorization, and secure user authentication.
With functionalities such as outlet management, medicine grouping, and search filters,
MediTrack enhances inventory control, prevents shortages, and improves decision-making
for pharmacy owners.

Chapter 02: User Story

MediTrack is designed for pharmacy owners who need an efficient way to manage multiple
outlets, track stock levels, and categorize medicines. Users can sign up and log in securely,
add outlets, manage inventory, remove expired or sold medicines, and track stock in real
time. The system also allows grouping medicines by manufacturer or type, viewing detailed
descriptions, and searching medicines using filters like outlet name, medicine name, or
company. These features ensure better organization and operational efficiency in pharmacy
management.

Chapter 03a: ER Diagram

Chapter 03b: SQL Queries

getUserCount

"SELECT COUNT(*) FROM Users WHERE user_name COLLATE

Latin1_General_CS_AS = @Username AND password COLLATE Latin1_General_CS_AS
= @Password";

GetFullName

"SELECT full_name FROM Users WHERE user_name = @user_name";

get_userId

"SELECT user_id FROM users WHERE user_name = @user_name";

getOutlets

"SELECT outlet_id, outlet_name, outlet_address, outlet_contact FROM outlet WHERE

user_id = @UserId";

getAllMedicine

"SELECT medicine_id, medicine_name, medicine_description, exp_date, manufacturer, grp

FROM Medicine";

getMedKeyWord

"SELECT medicine_id, medicine_name, medicine_description, exp_date, manufacturer, grp

"+
"FROM Medicine " +
"WHERE medicine_name LIKE @keyWord OR manufacturer LIKE
@keyWord OR grp LIKE @keyWord OR medicine_description LIKE @keyWord";
Chapter 04: Screenshots