2. Developed a strategic management information system for a virtual organization while considering the analytical requirements for management dashboards.
Tools: Salesforce Developer platform
Development of-pharmacy-management-systemJoy Sarker
It is a group presentation that was made for presenting the Pharmacy Management System for IUBAT Software Engineering Course . So if anyone need this ,or can get a clear idea about the Pharmacy Management System
This is Pharmacy Management System report for the project of Final Year Degree of Information Technology with Accounting Under State University Of Zanzibar.
This proposal presents a Pharmacy Management System to automate the manual record keeping of a pharmacy. It aims to reduce costs and risks while providing quick reports. The project will use the System Development Life Cycle methodology. Requirements were gathered through interviews and focus groups. The system will include functionalities like customer and supplier records, sales and inventory management, and reporting. It is being designed to be easy to use, reliable, and securely manage the pharmacy's data. The proposal concludes by thanking the audience.
Software requirements specification of Library Management SystemSoumili Sen
The document provides requirements for a Library Management System. It includes 3 or less sentences:
The Library Management System aims to computerize library processes like book borrowing and maintain member and book details in a database. It will allow librarians and members to search for books, view member accounts, and generate reports. The system needs to be secure, fast, and compatible with common browsers and operating systems.
Pharmaceutical store management systemTushar Dalvi
Developed online in-house Application for Pharmacy Management. Used Salesforce as CRM software to develop login Form, customer inquiry Form, and other various forms, also used HTML & CSS for Webpage Designing.
Development of-pharmacy-management-systemJoy Sarker
It is a group presentation that was made for presenting the Pharmacy Management System for IUBAT Software Engineering Course . So if anyone need this ,or can get a clear idea about the Pharmacy Management System
This is Pharmacy Management System report for the project of Final Year Degree of Information Technology with Accounting Under State University Of Zanzibar.
This proposal presents a Pharmacy Management System to automate the manual record keeping of a pharmacy. It aims to reduce costs and risks while providing quick reports. The project will use the System Development Life Cycle methodology. Requirements were gathered through interviews and focus groups. The system will include functionalities like customer and supplier records, sales and inventory management, and reporting. It is being designed to be easy to use, reliable, and securely manage the pharmacy's data. The proposal concludes by thanking the audience.
Software requirements specification of Library Management SystemSoumili Sen
The document provides requirements for a Library Management System. It includes 3 or less sentences:
The Library Management System aims to computerize library processes like book borrowing and maintain member and book details in a database. It will allow librarians and members to search for books, view member accounts, and generate reports. The system needs to be secure, fast, and compatible with common browsers and operating systems.
Pharmaceutical store management systemTushar Dalvi
Developed online in-house Application for Pharmacy Management. Used Salesforce as CRM software to develop login Form, customer inquiry Form, and other various forms, also used HTML & CSS for Webpage Designing.
This document outlines the development of a pharmacy management system. It discusses designing the project with user and admin panels and a database. It describes developing the backend with PHP, MySQL, and tools like Composer. It also covers developing the frontend, testing the project, and hosting it on a server. The document notes some problems encountered like interfaces and stock handling. It proposes further developments like adding customer access, bar code readers, and payment integration.
Medical Store Management System Software Engineering 1hani2253
This document outlines a medical store management system project created by three students. The project aims to automate the manual record keeping process of a medical store. Key features of the software include inventory management, accounting, customer management, and reporting. The document discusses the scope, objectives, drawbacks of the current system, and deliverables of the project. It also covers the system requirements, design approach, implementation details, and user documentation.
Pharmacy management system fyp documentationAbubakr Cheema
Pharmacy management system fyp documentation
complete project report
Online Pharmacy is a software which is used for small or big level organization such
as pharmacy.This software is based on online pharmacy in which customer orders a
particular medicine and get it.The main purpose of this webapp is to provide facility
to the people living in remote areas or people who uses a particular medicines
monthly but they can’t get it due to a number of reasons.So this app less their worries
and make medicines available for them.Moreover if people are unable to go to the
doctor,they also visit our website and get medicines after complete consultation of our
online doctor.It performs several other operations like adding new doctor,adding new
medicine,delete or modify a medicine approving medicine orders etc .It is made in
java so it is platform independent it can run on any platform like Windows, Unix and
MacOS etc.
Medical store management System is a software to manage the store and billing. It has a special feature like bill messaging and mailing bills to the customers. Special offer alert and warehouse management is an additional thing in Medical Store Management System.
The document discusses an existing pharmacy management system called Pharmaserv. It provides an integrated software solution for pharmacy management that combines point-of-sale, inventory management, accounts receivable, and reporting functions. The system aims to help pharmacists manage their businesses more efficiently by streamlining operations and providing comprehensive tools and services in one integrated platform. It notes that pharmacists face challenges like staffing shortages and shrinking profit margins, making an integrated pharmacy management system essential for running pharmacy operations.
This document provides a software requirements specification for a Hospital Management System. It includes sections on the introduction, intended audience, product perspective, user classes and environment, functional requirements, and other non-functional requirements. The system will allow authorized users like administrators, doctors, nurses, and patients to access modules for management of hospital activities, patient records, appointments, billing, and more. It aims to automate paper-based hospital processes for improved efficiency, accuracy, and data security.
This document contains a term paper on medical store management submitted by Amit Ranjan. The document includes an acknowledgment, index, project proposal, software development cycle, coding details, and form filling for different roles including shop owner, customer, salesman and medicines. The project aims to develop software using C++ to manage operations of a medical store through an online system for tasks such as employee transfers, form submissions and inventory management.
The document proposes a hospital management system to automate the manual paper-based system currently used. It aims to standardize data, consolidate records, ensure data integrity and reduce inconsistencies. The system would manage patient information, staff details, schedules and other facilities digitally. It faces challenges in designing and implementing the new system, and maintaining it going forward to address errors, adapt to changes and allow for enhancements. The system requirements include user interfaces, hardware and software needs, and communication protocols to allow the system to work across platforms and browsers. It is concluded that the automated system would improve efficiency, provide a friendly interface, enable easy access and updating of information, and offer security and reliability benefits over the existing manual process.
This document proposes developing a Library Management System to automate Agape Youth Library. The goals are to provide efficient, secure service and reduce personnel workload. Key functions include searching for books, borrowing/returning books, and viewing user details. Main users are borrowers, administrators, and librarians. The system will use Laravel and PHP with a MySQL database. It aims to address issues with manual tracking of book issues/returns and centralized record keeping.
App based e-medicare(online Pharmacy Management system)Jahidul Islam
This document presents an app-based e-pharmacy system that aims to improve accuracy, safety, and efficiency in pharmaceutical stores. The system allows customers to order drugs online for time savings and lower costs. It also helps patients easily manage medications. Key contributions of the system include only allowing prescribed users to access it, requiring a doctor's prescription to purchase drugs, and easing the stock replenishment process. Data flow and entity-relationship diagrams are provided, as well as screenshots of prototype activities like searching for drugs, viewing drug details, managing carts, and viewing orders. Future work may incorporate additional techniques like decision trees and neural networks to expand the system.
The document provides a software requirements specification (SRS) for a library management system. It includes sections on the purpose and scope of the system, user requirements, system functions, and design constraints. The system will allow librarians to manage the library catalog and user accounts, and allow users to search for books, view their accounts, and borrow books. It will be a web-based system compatible with major browsers that integrates with a Microsoft SQL database. Non-functional requirements like security, performance and error handling are also addressed.
The document discusses a proposed library management system that aims to improve upon the current system. It outlines the key features of the proposed system, including advantages over the current one. Entity relationship, data flow, and context diagrams are presented to illustrate the flow of data and relationships between various elements in the system. Various reports, tables, and forms are also described to showcase the reporting capabilities and interfaces of the proposed library management system.
Query Decomposition and data localization Hafiz faiz
This document discusses query processing in distributed databases. It describes query decomposition, which transforms a high-level query into an equivalent lower-level algebraic query. The main steps in query decomposition are normalization, analysis, redundancy elimination, and rewriting the query in relational algebra. Data localization then translates the algebraic query on global relations into a query on physical database fragments using fragmentation rules.
This document describes a library management system project developed by students at Cochin University of Science and Technology. It includes an introduction that outlines the project aims, objectives, background and operating environment. It also includes sections on system analysis, design, implementation, testing, and conclusions. The system analysis section specifies software requirements and compares the existing system to the proposed system. It was developed using HTML, PHP and MySQL to computerize library processes and reduce issues like file loss, damage and searching difficulties.
The document provides an overview of a project report on a Hospital Management System. It includes an introduction describing the purpose and scope of the system. It then discusses the overall description, including goals, background on existing hospital processes, project requirements, user characteristics, and constraints. Finally, it analyzes the feasibility of the system from technical, economic, operational, and schedule perspectives. The system aims to automate hospital workflows and improve accuracy, reliability, and immediate access to information.
The document provides information about an IT services company called Coalesce Technologies. It discusses Coalesce's services, commitment to client satisfaction, growing network, and customized solutions. It also describes the library management system project, including the problems with existing systems, proposed new system features, and UML diagrams for modeling the system. Key aspects of the proposed system include automating transactions, providing a simple GUI, efficient database updating, and restricting administrative access for security.
The document outlines the scope and design of a library management system. It includes sections on project purpose, scope, assumptions, functionality, specific requirements, tools/platform, resources used, design specification including entity relationship and data flow diagrams, database structure, module description, process logic, types of reports, and future scope. The system is intended to automate processes like membership registration, book issuing/returning, tracking book inventory and member records. It will leverage ASP.NET and SQL Server for development.
This document outlines a proposed library management system (LMS) that will allow a library to better manage its resources and users. The key features of the LMS include adding and removing users and books, issuing and returning books, and searching for books. It will use a database like Microsoft SQL Server to store information. The system aims to provide efficient service, reduce errors, and make all information easily accessible with a single click. It depends on technologies like ASP.NET and has requirements for performance, security, and being user-friendly. Flow charts and use cases are included to illustrate how the system would function.
This technical report explores intrapreneurship in an information systems service organization from the perspective of employees. It provides an overview of entrepreneurship theory and considers how this relates to intrapreneurship and information entrepreneurship. The report describes a survey of employees at an information systems service company to understand their perceptions of the organization's support for identifying and exploiting new opportunities. The findings show that while the company supports some entrepreneurial behaviors, employees overall feel the company does not support such behaviors. Recommendations are provided to improve the company's entrepreneurial profile.
This document provides background information on the Balanced Scorecard Information Management System (BSCIMS) project. It discusses performance management and the balanced scorecard concept. It describes the problems with SEC's current paper-based balanced scorecard implementation, including lack of integration, communication challenges, and inability to properly evaluate performance. The project aims to design and develop a web-based BSCIMS to address these issues and automate SEC's balanced scorecard processes. The document outlines the balanced scorecard architecture and perspectives of financial, customer, internal processes, and learning and growth. It also presents the problem statement and objectives of the project.
This document outlines the development of a pharmacy management system. It discusses designing the project with user and admin panels and a database. It describes developing the backend with PHP, MySQL, and tools like Composer. It also covers developing the frontend, testing the project, and hosting it on a server. The document notes some problems encountered like interfaces and stock handling. It proposes further developments like adding customer access, bar code readers, and payment integration.
Medical Store Management System Software Engineering 1hani2253
This document outlines a medical store management system project created by three students. The project aims to automate the manual record keeping process of a medical store. Key features of the software include inventory management, accounting, customer management, and reporting. The document discusses the scope, objectives, drawbacks of the current system, and deliverables of the project. It also covers the system requirements, design approach, implementation details, and user documentation.
Pharmacy management system fyp documentationAbubakr Cheema
Pharmacy management system fyp documentation
complete project report
Online Pharmacy is a software which is used for small or big level organization such
as pharmacy.This software is based on online pharmacy in which customer orders a
particular medicine and get it.The main purpose of this webapp is to provide facility
to the people living in remote areas or people who uses a particular medicines
monthly but they can’t get it due to a number of reasons.So this app less their worries
and make medicines available for them.Moreover if people are unable to go to the
doctor,they also visit our website and get medicines after complete consultation of our
online doctor.It performs several other operations like adding new doctor,adding new
medicine,delete or modify a medicine approving medicine orders etc .It is made in
java so it is platform independent it can run on any platform like Windows, Unix and
MacOS etc.
Medical store management System is a software to manage the store and billing. It has a special feature like bill messaging and mailing bills to the customers. Special offer alert and warehouse management is an additional thing in Medical Store Management System.
The document discusses an existing pharmacy management system called Pharmaserv. It provides an integrated software solution for pharmacy management that combines point-of-sale, inventory management, accounts receivable, and reporting functions. The system aims to help pharmacists manage their businesses more efficiently by streamlining operations and providing comprehensive tools and services in one integrated platform. It notes that pharmacists face challenges like staffing shortages and shrinking profit margins, making an integrated pharmacy management system essential for running pharmacy operations.
This document provides a software requirements specification for a Hospital Management System. It includes sections on the introduction, intended audience, product perspective, user classes and environment, functional requirements, and other non-functional requirements. The system will allow authorized users like administrators, doctors, nurses, and patients to access modules for management of hospital activities, patient records, appointments, billing, and more. It aims to automate paper-based hospital processes for improved efficiency, accuracy, and data security.
This document contains a term paper on medical store management submitted by Amit Ranjan. The document includes an acknowledgment, index, project proposal, software development cycle, coding details, and form filling for different roles including shop owner, customer, salesman and medicines. The project aims to develop software using C++ to manage operations of a medical store through an online system for tasks such as employee transfers, form submissions and inventory management.
The document proposes a hospital management system to automate the manual paper-based system currently used. It aims to standardize data, consolidate records, ensure data integrity and reduce inconsistencies. The system would manage patient information, staff details, schedules and other facilities digitally. It faces challenges in designing and implementing the new system, and maintaining it going forward to address errors, adapt to changes and allow for enhancements. The system requirements include user interfaces, hardware and software needs, and communication protocols to allow the system to work across platforms and browsers. It is concluded that the automated system would improve efficiency, provide a friendly interface, enable easy access and updating of information, and offer security and reliability benefits over the existing manual process.
This document proposes developing a Library Management System to automate Agape Youth Library. The goals are to provide efficient, secure service and reduce personnel workload. Key functions include searching for books, borrowing/returning books, and viewing user details. Main users are borrowers, administrators, and librarians. The system will use Laravel and PHP with a MySQL database. It aims to address issues with manual tracking of book issues/returns and centralized record keeping.
App based e-medicare(online Pharmacy Management system)Jahidul Islam
This document presents an app-based e-pharmacy system that aims to improve accuracy, safety, and efficiency in pharmaceutical stores. The system allows customers to order drugs online for time savings and lower costs. It also helps patients easily manage medications. Key contributions of the system include only allowing prescribed users to access it, requiring a doctor's prescription to purchase drugs, and easing the stock replenishment process. Data flow and entity-relationship diagrams are provided, as well as screenshots of prototype activities like searching for drugs, viewing drug details, managing carts, and viewing orders. Future work may incorporate additional techniques like decision trees and neural networks to expand the system.
The document provides a software requirements specification (SRS) for a library management system. It includes sections on the purpose and scope of the system, user requirements, system functions, and design constraints. The system will allow librarians to manage the library catalog and user accounts, and allow users to search for books, view their accounts, and borrow books. It will be a web-based system compatible with major browsers that integrates with a Microsoft SQL database. Non-functional requirements like security, performance and error handling are also addressed.
The document discusses a proposed library management system that aims to improve upon the current system. It outlines the key features of the proposed system, including advantages over the current one. Entity relationship, data flow, and context diagrams are presented to illustrate the flow of data and relationships between various elements in the system. Various reports, tables, and forms are also described to showcase the reporting capabilities and interfaces of the proposed library management system.
Query Decomposition and data localization Hafiz faiz
This document discusses query processing in distributed databases. It describes query decomposition, which transforms a high-level query into an equivalent lower-level algebraic query. The main steps in query decomposition are normalization, analysis, redundancy elimination, and rewriting the query in relational algebra. Data localization then translates the algebraic query on global relations into a query on physical database fragments using fragmentation rules.
This document describes a library management system project developed by students at Cochin University of Science and Technology. It includes an introduction that outlines the project aims, objectives, background and operating environment. It also includes sections on system analysis, design, implementation, testing, and conclusions. The system analysis section specifies software requirements and compares the existing system to the proposed system. It was developed using HTML, PHP and MySQL to computerize library processes and reduce issues like file loss, damage and searching difficulties.
The document provides an overview of a project report on a Hospital Management System. It includes an introduction describing the purpose and scope of the system. It then discusses the overall description, including goals, background on existing hospital processes, project requirements, user characteristics, and constraints. Finally, it analyzes the feasibility of the system from technical, economic, operational, and schedule perspectives. The system aims to automate hospital workflows and improve accuracy, reliability, and immediate access to information.
The document provides information about an IT services company called Coalesce Technologies. It discusses Coalesce's services, commitment to client satisfaction, growing network, and customized solutions. It also describes the library management system project, including the problems with existing systems, proposed new system features, and UML diagrams for modeling the system. Key aspects of the proposed system include automating transactions, providing a simple GUI, efficient database updating, and restricting administrative access for security.
The document outlines the scope and design of a library management system. It includes sections on project purpose, scope, assumptions, functionality, specific requirements, tools/platform, resources used, design specification including entity relationship and data flow diagrams, database structure, module description, process logic, types of reports, and future scope. The system is intended to automate processes like membership registration, book issuing/returning, tracking book inventory and member records. It will leverage ASP.NET and SQL Server for development.
This document outlines a proposed library management system (LMS) that will allow a library to better manage its resources and users. The key features of the LMS include adding and removing users and books, issuing and returning books, and searching for books. It will use a database like Microsoft SQL Server to store information. The system aims to provide efficient service, reduce errors, and make all information easily accessible with a single click. It depends on technologies like ASP.NET and has requirements for performance, security, and being user-friendly. Flow charts and use cases are included to illustrate how the system would function.
This technical report explores intrapreneurship in an information systems service organization from the perspective of employees. It provides an overview of entrepreneurship theory and considers how this relates to intrapreneurship and information entrepreneurship. The report describes a survey of employees at an information systems service company to understand their perceptions of the organization's support for identifying and exploiting new opportunities. The findings show that while the company supports some entrepreneurial behaviors, employees overall feel the company does not support such behaviors. Recommendations are provided to improve the company's entrepreneurial profile.
This document provides background information on the Balanced Scorecard Information Management System (BSCIMS) project. It discusses performance management and the balanced scorecard concept. It describes the problems with SEC's current paper-based balanced scorecard implementation, including lack of integration, communication challenges, and inability to properly evaluate performance. The project aims to design and develop a web-based BSCIMS to address these issues and automate SEC's balanced scorecard processes. The document outlines the balanced scorecard architecture and perspectives of financial, customer, internal processes, and learning and growth. It also presents the problem statement and objectives of the project.
Charity & Love is developing a customer service database and WAN system to connect its three locations. This will automate referral and assessment processes to better serve clients. The project involves implementing an online database for applications, scheduling, and generating reports. Oracle Fusion was selected as the software vendor. The project plan outlines communication methods, stakeholders, and a timeline for designing, testing, and deploying the new system over the next few months. The goal is for the database to streamline services and information sharing between Charity & Love's three offices.
This document provides an overview of management accounting concepts including definitions of management accounting, different types of management accounting systems, and management accounting reporting. It includes explanations of cost accounting, budgeting, and how management accounting can be integrated within organizational processes. The document also includes tasks to calculate costs using marginal and absorption costing to prepare an income statement, explain budgeting tools for control, and compare how organizations adapt management accounting systems to respond to financial problems. Overall, the document serves to develop an understanding of management accounting and how various tools and systems can be applied within organizations.
The document is a report on a summer practical attachment conducted at the Dangila Woreda Finance and Economic Cooperation office in Ethiopia. It discusses the background of the organization and department, their visions, missions, objectives and structures. It also analyzes the organization's strengths, weaknesses, opportunities and threats. Some problems facing the organization are identified along with suggested solutions. The report evaluates the relevance and applicability of theories learned in class to the practical work. It concludes with a summary and recommendations.
This document discusses metrics that can be used to assess the effectiveness of business analytics initiatives. It summarizes the results of a benchmark study that evaluated organizations on 8 metrics: productivity, governance, timeliness, ROI, accuracy, effectiveness, empowerment and maturity. The study found that on average organizations scored highest in governance and lowest in effectiveness. Certain industries tended to score higher or lower on different metrics. The document recommends evaluating an organization across 64 questions related to the 8 metrics in order to identify strengths and opportunities for improvement.
The document is a 2013 study on accounts payable (AP) automation sponsored by several companies and published by The Institute of Financial Operations. It includes an executive summary of key findings from a survey of over 200 AP professionals. The survey found that while paper-based processes are declining, they still remain common. Invoice approval workflow was the top priority for AP automation. Cutting costs was the main driver of automation efforts. Competition for resources was the main challenge to implementing automation projects.
HRMS domain modules with performance testing approachSiva Kota
The document provides an overview of the modules in an HRMS system including talent management, onboarding, payroll, employee self-service, manager self-service, appraisal and training, and promotion. It describes the key processes and workflows in each module such as the recruiting process in talent management, the onboarding process, payroll processing features, and functions available through the employee and manager self-service portals. The document also provides high-level architecture of the HRMS system.
This whitepaper discusses holistic data governance and provides a framework for organizations to establish effective data governance. It argues that data governance should be treated as a core business function, rather than an IT project, in order to optimize value from data assets. The framework outlines 10 facets of data governance, including vision/business case, people, tools/architecture, policies, organizational alignment, measurement, change management, dependent processes, program management and defined processes. It also defines levels of data governance maturity from initial/ad hoc to optimized/function in order to help organizations assess their current state and develop a roadmap.
Effectiveness of using Facebook on increasing the brand awareness; Tharushika Ruwangi
This document is a research report that investigates the effectiveness of using Facebook to increase brand awareness in the fashion industry in Sri Lanka. It includes a literature review on social media marketing, Facebook, brand awareness, and strategies used to increase awareness through Facebook. The methodology section describes the conceptual framework, hypotheses, data collection through surveys, and data analysis plan. The results and data analysis chapter analyzes survey data on brand exposure, customer engagement, and electronic word-of-mouth and their correlation to and impact on brand awareness. The conclusion summarizes the key findings and provides recommendations.
Whitepaper 7 steps to effective it-supportComAround
Seven steps to success with more efficient IT support thanks to self service.
Offering self service is an efficient way of creating direct economic benefits in the company by making financial savings on staffed support; but also indirectly, by enhancing the level of service offered to users. A study from HDI involving 1000 support organisations the world over shows that 72% use self service operations or are planning to do so soon. But how to get started properly? How do you persuade the organisation to go along with it? How do you gauge the benefits? Take a look at this white paper for seven concrete steps you can take, from strategy via communication and procedures to measurability.
White paper - Seven steps to success with more efficient IT support thanks to self service
Written by Per Strand ComAround and Therese Walvé ComAround
This document contains a summary of a student project to develop an e-commerce website called "Senorita Online Shopping and Web Selling System". The project report contains 8 chapters and appendices documenting the research, analysis, design, and development of the system. The first chapter introduces the project background and objectives, which are to develop functionalities for online purchasing, item management, sales, delivery, payments, and reporting. The second chapter provides a literature review on e-commerce studies, models, features, methodology, techniques and tools to be used. A feasibility study is presented in chapter 3, analyzing the economic, financial, technical and legal feasibility of the project and suitability of the DSDM methodology.
This document provides a roadmap for implementing a successful identity management project. It outlines conducting a needs analysis to identify problems with the existing user access administration. Key areas to examine include user productivity, excessive administration costs, inconsistent user data, user service issues, and security vulnerabilities. The roadmap then covers determining technology requirements, organizing the project team, selecting an identity management product, implementing the system through project management best practices, and ongoing administration and reporting after rollout.
This document describes a Deployment Excellence Framework (DEF) to effectively adopt high maturity processes. The framework includes 3 interlinked cycles: 1) Identification Cycle to target initial units and stakeholders, 2) Initial Deployment Cycle focusing on awareness and success indicators, and 3) Sustenance Cycle increasing adoption scope and self-reliance. It also includes a feedback adapter for course correction. The case study illustrates using DEF to standardize an organization's project estimation processes and templates by deploying new estimation models and tools over 6 quarters.
Writekraft Research and Publications LLP was initially formed, informally, in 2006 by a group of scholars to help fellow students. Gradually, with several dissertations, thesis and assignments receiving acclaim and a good grade, Writekraft was officially founded in 2011 Since its establishment, Writekraft Research & Publications LLP is Guiding and Mentoring PhD Scholars.
Our Mission:
To provide breakthrough research works to our clients through Perseverant efforts towards creativity and innovation”.
Vision:
Writekraft endeavours to be the leading global research and publications company that will fulfil all research needs of our clients. We will achieve this vision through:
Analyzing every customer's aims, objectives and purpose of research
Using advanced and latest tools and technique of research and analysis
Coordinating and including their own ideas and knowledge
Providing the desired inferences and results of the research
In the past decade, we have successfully assisted students from various universities in India and globally. We at Writekraft Research & Publications LLP head office in Kanpur, India are most trusted and professional Research, Writing, Guidance and Publication Service Provider for PhD. Our services meet all your PhD Admissions, Thesis Preparation and Research Paper Publication needs with highest regards for the quality you prefer.
Our Achievements:
NATIONAL AWARD FOR BEST RESEARCH PROJECT (By Hon. President APJ Abdul Kalam)
GOLD MEDAL FOR RESEARCH ON DISABILITY (By Disabled’s Club of India)
NOMINATED FOR BEST MSME AWARDS 2017
5 STAR RATING ON GOOGLE
We have PhD experts from reputed institutions/ organizations like Indian Institute of Technology (IIT), Indian Institute of Management (IIM) and many more apex education institutions in India. Our works are tailored and drafted as per your requirements and are totally unique.
From past years our core advisory members, research team assisted research scholars from various universities from all corners of world.
Subjects/Areas We Cover:
Management, Commerce, Finance, Marketing, Psychology, Education, Sociology, Mass communications, English Literature, English Language, Law, History, Computer Science & Engineering, Electronics & Communication Engineering, Mechanical Engineering, Civil Engineering, Electrical Engineering, Pharmacy & Healthcare.
This document provides an abstract for a study on the impact of quality of work life on employee job satisfaction, with a focus on the IT industry in Hyderabad, India. The abstract discusses that quality of work life (QWL) aims to provide a satisfactory work environment through rewards, career growth, job security, and other factors. QWL is related to job satisfaction, involvement, motivation, health, safety, security, development, and balance between work and personal life. Both primary and secondary data were collected through a questionnaire survey of 120 IT industry employees. The findings revealed that improving QWL factors like health, safety, skills development, and work-life balance can increase employee satisfaction and productivity.
Writekraft Research and Publications LLP was initially formed, informally, in 2006 by a group of scholars to help fellow students. Gradually, with several dissertations, thesis and assignments receiving acclaim and a good grade, Writekraft was officially founded in 2011 Since its establishment, Writekraft Research & Publications LLP is Guiding and Mentoring PhD Scholars.
Our Mission:
To provide breakthrough research works to our clients through Perseverant efforts towards creativity and innovation”.
Vision:
Writekraft endeavours to be the leading global research and publications company that will fulfil all research needs of our clients. We will achieve this vision through:
Analyzing every customer's aims, objectives and purpose of research
Using advanced and latest tools and technique of research and analysis
Coordinating and including their own ideas and knowledge
Providing the desired inferences and results of the research
In the past decade, we have successfully assisted students from various universities in India and globally. We at Writekraft Research & Publications LLP head office in Kanpur, India are most trusted and professional Research, Writing, Guidance and Publication Service Provider for PhD. Our services meet all your PhD Admissions, Thesis Preparation and Research Paper Publication needs with highest regards for the quality you prefer.
Our Achievements:
NATIONAL AWARD FOR BEST RESEARCH PROJECT (By Hon. President APJ Abdul Kalam)
GOLD MEDAL FOR RESEARCH ON DISABILITY (By Disabled’s Club of India)
NOMINATED FOR BEST MSME AWARDS 2017
5 STAR RATING ON GOOGLE
We have PhD experts from reputed institutions/ organizations like Indian Institute of Technology (IIT), Indian Institute of Management (IIM) and many more apex education institutions in India. Our works are tailored and drafted as per your requirements and are totally unique.
From past years our core advisory members, research team assisted research scholars from various universities from all corners of world.
Subjects/Areas We Cover:
Management, Commerce, Finance, Marketing, Psychology, Education, Sociology, Mass communications, English Literature, English Language, Law, History, Computer Science & Engineering, Electronics & Communication Engineering, Mechanical Engineering, Civil Engineering, Electrical Engineering, Pharmacy & Healthcare.
Writekraft Research and Publications LLP was initially formed, informally, in 2006 by a group of scholars to help fellow students. Gradually, with several dissertations, thesis and assignments receiving acclaim and a good grade, Writekraft was officially founded in 2011 Since its establishment, Writekraft Research & Publications LLP is Guiding and Mentoring PhD Scholars.
Our Mission:
To provide breakthrough research works to our clients through Perseverant efforts towards creativity and innovation”.
Vision:
Writekraft endeavours to be the leading global research and publications company that will fulfil all research needs of our clients. We will achieve this vision through:
Analyzing every customer's aims, objectives and purpose of research
Using advanced and latest tools and technique of research and analysis
Coordinating and including their own ideas and knowledge
Providing the desired inferences and results of the research
In the past decade, we have successfully assisted students from various universities in India and globally. We at Writekraft Research & Publications LLP head office in Kanpur, India are most trusted and professional Research, Writing, Guidance and Publication Service Provider for PhD. Our services meet all your PhD Admissions, Thesis Preparation and Research Paper Publication needs with highest regards for the quality you prefer.
Our Achievements:
NATIONAL AWARD FOR BEST RESEARCH PROJECT (By Hon. President APJ Abdul Kalam)
GOLD MEDAL FOR RESEARCH ON DISABILITY (By Disabled’s Club of India)
NOMINATED FOR BEST MSME AWARDS 2017
5 STAR RATING ON GOOGLE
We have PhD experts from reputed institutions/ organizations like Indian Institute of Technology (IIT), Indian Institute of Management (IIM) and many more apex education institutions in India. Our works are tailored and drafted as per your requirements and are totally unique.
From past years our core advisory members, research team assisted research scholars from various universities from all corners of world.
Subjects/Areas We Cover:
Management, Commerce, Finance, Marketing, Psychology, Education, Sociology, Mass communications, English Literature, English Language, Law, History, Computer Science & Engineering, Electronics & Communication Engineering, Mechanical Engineering, Civil Engineering, Electrical Engineering, Pharmacy & Healthcare.
Writekraft Research and Publications LLP was initially formed, informally, in 2006 by a group of scholars to help fellow students. Gradually, with several dissertations, thesis and assignments receiving acclaim and a good grade, Writekraft was officially founded in 2011 Since its establishment, Writekraft Research & Publications LLP is Guiding and Mentoring PhD Scholars.
Our Mission:
To provide breakthrough research works to our clients through Perseverant efforts towards creativity and innovation”.
Vision:
Writekraft endeavours to be the leading global research and publications company that will fulfil all research needs of our clients. We will achieve this vision through:
Analyzing every customer's aims, objectives and purpose of research
Using advanced and latest tools and technique of research and analysis
Coordinating and including their own ideas and knowledge
Providing the desired inferences and results of the research
In the past decade, we have successfully assisted students from various universities in India and globally. We at Writekraft Research & Publications LLP head office in Kanpur, India are most trusted and professional Research, Writing, Guidance and Publication Service Provider for PhD. Our services meet all your PhD Admissions, Thesis Preparation and Research Paper Publication needs with highest regards for the quality you prefer.
Our Achievements:
NATIONAL AWARD FOR BEST RESEARCH PROJECT (By Hon. President APJ Abdul Kalam)
GOLD MEDAL FOR RESEARCH ON DISABILITY (By Disabled’s Club of India)
NOMINATED FOR BEST MSME AWARDS 2017
5 STAR RATING ON GOOGLE
We have PhD experts from reputed institutions/ organizations like Indian Institute of Technology (IIT), Indian Institute of Management (IIM) and many more apex education institutions in India. Our works are tailored and drafted as per your requirements and are totally unique.
From past years our core advisory members, research team assisted research scholars from various universities from all corners of world.
Subjects/Areas We Cover:
Management, Commerce, Finance, Marketing, Psychology, Education, Sociology, Mass communications, English Literature, English Language, Law, History, Computer Science & Engineering, Electronics & Communication Engineering, Mechanical Engineering, Civil Engineering, Electrical Engineering, Pharmacy & Healthcare.
Similar to Pharmaceutical store management system (20)
Prediction of Corporate Bankruptcy using Machine Learning Techniques Shantanu Deshpande
Aim is to build a classification model to predict whether company will become bankrupt or not using financial ratios of Polish companies. Applied various machine learning models like Random Forest, KNN, AdaBoost & Decision Tree with pre-processing techniques like SMOTE-ENN (to deal with class imbalance) & feature selection (for identifying ) and trained on Polish Bankruptcy dataset with prediction accuracy of 89%.
Corporate bankruptcy prediction using Deep learning techniquesShantanu Deshpande
This document proposes using deep learning techniques like LSTM neural networks to predict corporate bankruptcy by integrating both financial ratio data and textual disclosures from annual reports. It notes that previous studies have largely relied on statistical models or used only financial data with machine learning. The researcher aims to determine if adding textual data to an LSTM model improves prediction performance over a CNN model using only financial ratios. The document outlines the research question, objectives, and provides an overview of previous bankruptcy prediction studies using statistical, machine learning and deep learning methods.
Analyzing financial behavior of a person based on financial literacyShantanu Deshpande
6. Analysed consumer behaviour and relationship using Financial literacy dataset. Identified patterns and predictor variables using logistic regression.
Methodologies & Tools: IBM SPSS, RapidMiner, PowerBI
Built a CNN based machine learning model to diagnose Pneumonia disease using chest x-rays.
Methodologies & Tools: KDD, Python, VGG19 model, Convolutional Neural Network.
4. Performed statistical analysis on a chosen data table and understood relationship amongst different data fields using IBM SPSS software.
Methodologies: Multi linear regression, Logistic linear regression
IBM SPSS
Built a data warehouse from multiple data sources and ETL methodologies and executed three non-trivial Business Intelligence queries.
Technologies/Tools: R, SQL, Visual Studio, SQL Server Management, Tableau
I have examined the performance of two databases - HBase and Cassandra in terms of their scalability, security, performance and compared the results thus obtained through different operations on the Ubuntu interface.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
TrustArc Webinar - 2024 Global Privacy SurveyTrustArc
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
1. 1
Strategic ICT & eBusiness Implementation
Pharmaceutical Store Management System
Batch January-2019 / B
Project Outline
Team Members
Member Name Student Number Contribution
Ashish Soni 18136664 25 %
Shantanu Deshpande 18125514 25 %
Tushar Dalvi 18134301 25 %
Yash Iyengar 18124739 25 %
Submitted to : Prof. Ciaran Hayden
2. 2
Table of Contents
Contents
1. Background Information on the organization:....................................................................4
1.1. Organization Background: ..........................................................................................4
2. Infrastructure: .......................................................................................................................5
2.1. Rational for Selecting Infrastructure:.........................................................................5
2.2. Benefits and Risks of Infrastructure Selected: ..........................................................5
• Benefits:......................................................................................................................................... 5
• Risks:............................................................................................................................................. 6
3. System Design .......................................................................................................................7
3.1. Integrating Customers: ...............................................................................................7
3.2. Process Diagrams: .......................................................................................................7
3.3. Data Capture Points (DCPs) ..................................................................................... 10
3.4. Management Dashboard:........................................................................................ 10
4. Database Design................................................................................................................. 12
4.1. Entity-Relationship diagrams................................................................................... 12
4.2. Data Flow Diagram:.................................................................................................. 14
4.3. Data Dictionary......................................................................................................... 16
4.4. Process Control Features ......................................................................................... 20
5. Project Architecture........................................................................................................... 21
5.1. Implementation Architecture:................................................................................. 21
5.1.1. Custom Objects: ................................................................................................................... 21
5.1.2. Custom Fields: ...................................................................................................................... 22
5.1.3. View Users within Application:.............................................................................................. 22
5.1.4. Create new Product Record: ................................................................................................. 23
5.1.5. Create New Purchase Record:............................................................................................... 24
5.1.6. Create New Sales Record:..................................................................................................... 25
5.1.7. Create New Customer Record:.............................................................................................. 25
5.1.8. Create new Vendor record:................................................................................................... 26
5.1.9. Create new Employee Registration Record:........................................................................... 27
5.2. Data Fields: ............................................................................................................... 27
5.2.1. Customer Data:..................................................................................................................... 27
5.2.2. Sales Data:............................................................................................................................ 28
5.2.3. Product Master Data:............................................................................................................ 29
5.2.4. Purchase Data:...................................................................................................................... 29
5.3. Validation and Triggers:........................................................................................... 31
4. 4
Pharmaceutical Store Management System
1. Background Information on the organization:
1.1. Organization Background:
A pharmacy is a retail shop which provides prescription drugs, among other products. At the pharmacy, a
pharmacist oversees the fulfilment of medical prescriptions and is available to give advice on their offerings of
over-the-counter drugs. A typical pharmacy would be in the commercial area of the community. Characteristic
of a good pharmacy includes processing the request quickly and having drug stock available to fill the
prescription. Enabling latest technology at a pharmacy will also enable the patients to have scheduled
prescription reminders and alerts about potential negative drug interactions, which will help in reducing medical
errors.
Medcure is a pharmaceutical store operating in the healthcare industry and is in the business of selling
prescription drugs since 2013. Their motto has always been to provide best service to their customers by having
stock of appropriate products at any given point in time. Their staff dedicatedly offers precise advice to
customers for selecting the appropriate over-the-counter products well suited to their needs. The range of
products and drugs that are offered in store is quite extensive and is well-managed by the current team however
due to the outdated IT system, it becomes difficult at times to manually keep track of inventory, Revenue,
product and day to day activity information which causes lack of efficiency in the process.
It is extremely crucial for a business to integrate IT services in today’s age in order to expand their business and
bring efficiency in the process.
5. 5
2. Infrastructure:
2.1. Rational for Selecting Infrastructure:
Existing process includes a very basic IT system which only has the capability of generating bills but
does not capture customer data and all the necessary data points pertaining to the stock inventory.
As a result of that, it is not possible to derive meaningful insights based on the available data. Additional
drawbacks of the existing process could be summarized as below-
No proper employee authentication/verification process in place:
In the existing system, employee interaction with system is tracked on trust and goodwill. No
proper hierarchical process is defined which will allow the interaction to be verified, always
acknowledged and monitored.
No visual reports:
As stated earlier, there is inconsistency in the data capture process. Due to this, it is not possible for
the management to derive meaningful insights.
Improper inventory management:
In the current system, all the necessary information related to a product is not captured, for example,
the expiry date of a batch of products is not captured by the current system. This results in improper
inventory management and thereby affects profits.
Customer information not retained:
The store currently operates in a retail environment wherein the customer walks-in with the
prescription and walks out with drugs and a bill. The store does not collect any customer details.
This information is crucial in order to become customer-centric and increase profits.
2.2. Benefits and Risks of Infrastructure Selected:
Using Salesforce developer platform to integrate proper IT management system to manage the
inventory and better capture the employee and customer data will help to get accurate insight in store
as well as proper revenue, sales, purchase reports will help in order to increase profitability, efficiency
and bring transparency in the process.
• Benefits:
6. 6
Increased Profitability:
Relying on the IT system will result in reducing manual work which helps in cost cutting and
eventually increases the profitability in the long run.
Can cater to large number of customers:
Implementing IT system helps in retaining the customer information, reach out to customers and
this in turn increases publicity by word of mouth. Also, since we are increasing our scope of
business, having online customers will also widen our customer base.
Proper Inventory management and Data Transparency:
In the proposed system, all the necessary data points pertaining to the drugs/employee/customer
would be precisely captured and updated in real-time also All the data inputs can be verified and
monitored by the supervisor. This will reduce irregular and erroneous inputs.
Efficient and robust system:
An efficient and robust IT management system serves as a backbone of any organization. The
proposed system is capable to handle the existing business in an efficient and also give the
organization a competitive edge over its competitors.
• Risks:
Considerable maintenance cost:
IT systems have a significant upkeep cost as we must deploy the complete system on a Cloud
environment, hence cost might be high or low depending upon the location and infrastructure user
wants to use.
Data Security:
As mentioned above, all the information is stored on a third-partycloud-based system. If the system
is not properly secured there might be a possibility of data breach and the crucial business-related
information can be harnessed by unauthorised users.
User-adaptability:
While designing the IT management system if users’ abilities needs and preferences are not taken
into consideration, even an amazing IT system would be a complete failure. It is extremely
important to have a proper User Acceptance Testing before deploying the IT system.
7. 7
3. System Design
3.1. Integrating Customers:
Integrating customers into our management system is very crucial for smooth functioning of the medical
shop. We have demonstrated how we have integrated customers not only in retail but also in our online format.
It is explained systematically and step by step how we integrate customers into the system with the help of
design flow diagrams, data capture points, Entity Relationship diagram and Database Design diagrams.
3.2. Process Diagrams:
Retail Shop Process:
The Retail Shop Process is different from the Online registration process. In which User will no need
to Register online. This system is totally developed for employee of shops and for owner. Employee will use
this system to sell product in Retail shop in which system will capture stock details, payment method and
customer details. Customer will get to know which medicines are out of stock, which products are near to expiry
date, or which products we will need to restock for future sell.
9. 9
Stock Update Process:
The Inventory management is very important aspect of any pharmacy. If properly managed, this can lead to increased profits and reduced overheads.
This can also reduce the burden on the Manager as system would be keeping track of the inventory. We have designed a process flow for it.
Fig3.2.2 The Cross- Functional diagrams of Stock Update Process
10. 10
3.3. Data Capture Points (DCPs)
The Data Capture Points are represented by a red circle in the process flow diagrams. Error! Reference s
ource not found. shows a list of all the DCPs:
Type Process Flow Diagram DCP Data Captured
Retail
Store
New Customer Walk-In
Process
Customer Come to purchase
medicine from Store
Name of Applicant, Medicines
Name, Quantity
Making list to purchase
of New Products
Creating Purchase order Limited Stock List, Quantity of
Medicines and other product
Name of supplier
Receiving new product Adding new product in
Inventory
Product Name, Quantity of the
products, Expiry Date of
Product, Production Date of
Product, Sellers information,
Payment Details,
Adding New Worker New Worker Details of Worker, Level of
Authentication, Job Profile,
joining Date,
3.4. Management Dashboard:
Analytics Requirement:
The management dashboard aspect for medical management system is crucial to take any decision
related to organisation. Each department or division is responsible for managing their own information,
but all that information leads back to one strategy for the organization. Simply sending out a file
occasionally, to each department isn’t going to cut it. To keep every department constantly updated
(and available for viewing in several different ways), every company need a management dashboard.
This dashboard includes graphs, pie charts, line charts, dials, and tree maps, historical trend graphs, and
leadership boards, the data which we are going to present will be captured from various processes.
User will be able to obtain the following insights: -
• Numbers of product sold within day/month/year.
• Number of products need to be purchased.
• list of products which will expire soon.
• Revenue generated from Retail Store as well as Online website.
• Weekly Analytical reports to check revenue, sales, purchases and other Activity.
The purpose of operational analytics and analytical dashboards is to optimise the business process and
tasks within the store. These reports will be highly beneficial for the store in terms of increasing the
11. 11
revenue, keeping the products in stock. Ultimately, the analysis and dashboards will allow the store
manager to provide the best service to the customers and it will boost the administrative productivity.
Another analytical need of the store is the requirement of gaining insights from the customer
information. The reports can thus be generated and reviewed customer-wise. Some of the important
questions the reporting and analysis will need to answer include:
• What type of products do the customers frequently buy?
• Who the top customers are in terms of spending?
• Which products have less price or high prices?
• Total sale of product depending on different Area?
• Total expenditure for medical shop or online application with categorisation with Monthly,
quarterly or yearly.
12. 12
4. Database Design
4.1. Entity-Relationship diagrams
In order to show the relationships among the entity sets that are stored in the database, we
generally use the Entity-Relationship Diagram, often abbreviated as ER Diagram. Entity is an object, a
component of data whereas an entity set is a collection of multiple similar entities. These entities have
attributes that delineate its properties.
An ER diagram elucidates the logical structure of databases by defining the entities, their attributes and
the relationship between them. Entities are denoted by a square shape in the ER Diagram whereas the
attributes are the facts and properties of an entity. Relationships are denoted by a diamond shape on the
lines connecting the entities together and are often nouns in the description. They depict the links that
entities have among each other.
Refer Fig. No. 4.1, we have our relationships decided, from where we can now move on to particularize
a more detailed Database diagram. The Database diagram has been built upon the ER Diagram from
below, with some added details about the more descriptive attributes of each table/member. The final
design on which the data storage system will be created is based upon this lower level design.
13. 13
Fig No. 4.1: ER Diagram of Pharmaceutical Store Management System
14. 14
4.2. Data Flow Diagram:
Proposed the diagram is Entity Relationship diagram for the database design. It consist of the tables like
User Details, Login Details, Stock Data, Medicine details, Retail Billing, Vendor Invoice, Retail Billing
and Employee Table.
Below is the description of each table:
User Details: This table will capture all the details of user when He/ She first time sign up to the Online
Portal. It basically consists of basic information about the user including Email-id, password etc. The
primary key for this table will be Email-id which will be unique for each user.
Login Details: This tables will store the email-id, password and user name which will be used to
validate the record of the user who will be trying to login to the portal. The table will be updated by the
new user when they successfully signed up to the online.
Medicine Details: This table basically consist details of the medicines. The primary key of this table is
Medicine_id which will uniquely identify each medicines. It will store details related to medicines like
its description type and Cost.
Stock Data: This table will store the data of the medicine available in the stocks. To identify the stock
we have used the primary key like storage location and Medicine Number. It also include the details
like In and Out details of the batch and with the details like Expiry date etc.
Retail Billing: The retail billing is the table which store the data of all the sales done from the store
the primary key for the table is Billing Number which will uniquely identify the sales from the retail
store. And it also consist the details of store, medicine name description etc.
Vendor Invoicing: The vendor invoicing basically consist of the data which will the medical store buy
from the other vendors to fulfil its stocks. In this the invoice number will uniquely identify the data int
the table .It also contains the information like Medicine name, Medicine Description, Batch number etc.
Employee: The employee table basically consist of the employee of the company. To uniquely identify
the table employee data we have made the Employee_id as the primary key for the table. It also Include
the details of the employee role and its description.
16. 16
4.3. Data Dictionary
“A Data Dictionary is defined as a central repository of information about data such as meaning, relationship to other data, origin, usage, and format.”(IBM
Dictionary of Computing, 1993). Our data dictionary gives a complete description of different data points their relation to the database and field description.
The Data Dictionary is created with the help of Entity Relationship Diagram and Data flow Diagram.
Our data dictionary is divided into 3 main parts Customer Table, Stock Table and Employee Table. These tables have a common flow as to what fields are
mentioned in respective tables and what proper values should be input into the table. Furthermore it gives a description of each field and tells what checks
are to be implemented on the data entered in the respective field.
Product Master Detail
Field Label Data Type Description
Product Name Varchar (50) Name of the Medicine in inventory
Manufacturer Name String Drug manufacturer’s name
Purchase Price Float Cost of the drug
Quantity Int Total no of batches of that product ordered.
Expiry Date Date (dd/mm/yyyy) Approximate date after which drugs must not be consumed.
17. 17
Purchase
Field Label Data Type Description
PO Number Varchar (12) Purchase Order
Purchase_ID Int not null Primary Key for Purchase Table
Purchase Date Date (dd/mm/yyyy) Date on which Purchase was made
Quantity Int Total no of batches of that product ordered.
Purchase Price Float Cost of the drug
Vendor Name Foreign Key It is a reference field which gives Vendor name from the Vendor
table
Product Name Foreign Key It is a reference field which gives Product name from the Product
Master table
18. 18
Sales Table
Field Label Data Type Description
Sale Order Number Varchar (12) Gives the sales order for the medicine sold
Sale_ID Int not null Primary Key to Sales table
Sale Date Date (dd/mm/yyyy) Date on which sales was made
Quantity Int Number of units of that drug purchased
Sale Rate Float Selling price of the drug
Customer Name Foreign Key It reference Customer Name from the Customer
Table
Product Name Foreign Key It is a reference field which gives Product name
from the Product Master table
Customer Table
Field Label Data Type Description
Customer_ID Int not null Primary key for Customer Table
Customer Name String Name of Customer
Mobile Number Int Contact number of the customer
19. 19
Vendor Table
Field Label Data Type Description
Vendor_ID Int not null Primary key for Customer Table
Vendor Name String Name of Vendor
Mobile Number Int Contact number of the customer
Vendor Address Varchar (50) Address of production factory.
Bank Details Varchar (12) Bank Account details of the vendor
Employee Table
Field Label Data Type Description
Employee Name String Name of the Employee
Birth Date Date (dd/mm/yyyy) Date of Birth of Employee
Contact Number Int Contact number of the customer
Employee Address Varchar (50) Address of Employee
Employee Designation String Post of the Employee
PPS Number Int Personal public service number of the Employee
Password Varchar (12) Password for employee
Employee_ID Int not null Primary Key for Employee Registration Table
20. 20
4.4. Process Control Features
• Employee details are registered into the Employee Table once the employee is hired for the job, default employee id and password are
created.
• Depending on the designation of the employee, he is given access for different levels.
• An employee with a basic access includes access to Customer, Sales, Product Master Details.
• Once a customer enquires for a medicine, the employee first checks for its availability by checking quantity of the stock in the Product
Master object. If available, he gives the medicine to the customer.
• The customer details are entered in the Customer object table by the employee.
• Invoice is generated and the details are stored in the sales object table.
• Detailed explanation of level of access to different employees is explained in the next section.
• Inventory management is handled using the two objects Product Master, Purchase and Vendor.
21. 21
5. Project Architecture
Project implementation has been done using the Salesforce platform. We have designed custom
objects like Customer, Vendor, Product Master etc.
5.1. Implementation Architecture:
The basic architecture of our Sales Force project consists of the elements like Data Structures,
Custom Objects, Workflows, Email triggering etc. In below screen shot you can see some of the
objects. The details of all the built-in objects are discussed here.
Many custom objects are created for storing the data. We have opted for creating the Custom
Object because we have to define the relationship between them and used them for calculations.it
can be more complex in future So Custom object will be more suited for our project. The Custom
Object behave like the Database which stores the values.
5.1.1. Custom Objects:
Below are the Custom Objects which are created for the project to store the data for our MedCure
Store. Many objects are related to the other objects using the Look-up field in the Object.
Fig5.1.1 Custom Objects
22. 22
5.1.2. Custom Fields:
We have also used the Contact to store some of the Customer related data. A detailed information
about the customer is added to the Contacts fields. We have added some of the Custom fields to
store detailed information about the Customer. Below screen shot consist of Custom fields added to
the Contacts.
Fig5.1.2 Contact Custom Fields & Relationships
5.1.3. View Users within Application:
The Administrator perform task like creating and Editing the Users. The users in the company are the
employee like Manager, IT specialist, Team Leads etc. The people who want to access the records for
the company. The level of the Users decides what type of access are needed to assign the Users and
what types are Access needs to be granted to the Users. Below is the screen shot which consist of
the users which we had created for our MedCure App.
23. 23
Fig5.1.3 User Access
5.1.4. Create new Product Record:
The below screen shot is the input screen for the Product Master Data. The fields highlighted in red
are the mandatory fields. We have created the many of the fields as mandatory because we don’t
want to make meaningless entry in the table. We added the validation for the fields Quantity and
Expiry Date. For Quantity if negative value inserted it will throw the error message. For expiry data
the validation is that it can be a future date and Current date but it cannot have an entry with a date
in the past. If a past date is entered it will throw the error message.
Fig5.1.4 New Product Master
24. 24
5.1.5. Create New Purchase Record:
The purchase fields consists of all the field mandatory. The Custom object Purchase consist of the
record purchase done by the company till date. Field Purchase date has a validation that any
employee cannot create a new entry in system with a purchase date in the past. Also the quantity
field should have only positive values. So the Purchase date will not accept any past dates and
quantity will not accept any negative value.
Fig5.1.5 New Purchase Record
25. 25
5.1.6. Create New Sales Record:
The Custom Object consist of the records of the Sales done by the stores. All the fields are mandatory
in the table. The Object consist of the values like Sales Date, Quantity, Sale Rate, Product Name,
Customer Name. The field Sale date has validation that it cannot be past date. This object contains
two lookup fields – one is the product name that references the product master data and the second
one customer name which references the customer object. Selection of any particular product or
customer using lookup will also create another transaction record in the respective objects.
Fig5.1.6 New Sales Record
5.1.7. Create New Customer Record:
The customer object consists of two fields – the name of customer and mobile number. Since our
system is designed for a retail store, we are able to capture only these two fields from the customer
during the purchase. This will provide an insight into the past orders of the customer and thereby
help the manager in segregating customers based on their preferences and previous orders.
26. 26
Fig5.1.7 New Customer Record
5.1.8. Create new Vendor record:
The vendor object consists of several fields like the vendor name, vendor address, number and bank
details. For the restocking of sold products we need to raise the Purchase orders. We have a vendor
database from whom we purchase our products. In order to add new vendor in system, we are
making use of this object. Through reports, the store manager can visualize the spend on each
vendor and the products being purchased, this will help the manager in key decision making.
Fig5.1.8 New Vendor Record
27. 27
5.1.9. Create new Employee Registration Record:
The Custom Object Employee Registration stores the Employee details. The Employee Registration
consist of the following fields Employee Name, Employee Designation, Birthdate etc.
The fields highlighted in red are the Mandatory fields for the Registering the employees to the Firm.
The Validation for the field Email has been done like a valid mail Id should be entered if the Mail ID is
not valid it will throw the error message to the user.
The Email and password field entered by the Employee for the first time of registering are stored
and validate every time the user try to login to the System.
Fig 5.1.9 New Employee Registration Object
5.2. Data Fields:
5.2.1. Customer Data:
The below screen shot shows the data which loaded in the Customer table. This data shows us the
existing customers of our retail store. They are present in system as a result of any past purchase
from the store.
28. 28
Fig5.2.1 Customer Data fields
5.2.2. Sales Data:
The below screen shot show the data available in the Sales Custom Table. This data shows us the
products that have been sold in the past along with the quantity, price and the customer who
purchased the product. Capturing this data is important because this will help the manager in
generating reports and understand which products have sold more and the associated revenue it has
generated.
Fig5.2.2 Sales Data Field
29. 29
5.2.3. Product Master Data:
The Product Master consist of the data as shown in the below screenshot. This data represents the
products in the store and the available quantity and associated price. This is our master database,
any changes during purchase and sale will reflect in this data. For example, if a product is being sold
multiple times and the available quantity comes down below 30, it will create a trigger and send an
automatic email to the store manager and remind to restock the product.
Fig5.2.3 New Sales Record
5.2.4. Purchase Data:
This Purchase object consists of the following data as shown in the below screenshot. Several fields
have been captured during the process which can be used eventually for analysis and decision
making by store manager.
31. 31
5.3. Validation and Triggers:
5.3.1. Sales Fields Validation:
Similar validation has been done for the Custom Object Sales. If the date is less then the current date
and quantity is negative value it will throw the Error message as shown in the below screen shot.
Fig5.3.1 Validation in Sales field.
32. 32
5.3.2 Email Trigger:
An email notification will be sent to Store Manager if any quantity in the Store is running out of
stock. The product is considered out of stock if the quantity is less than 30.
Fig5.3.2 Email notification for low stock
33. 33
5.3.2. Login:
This is our internal login page that can be accessed by the employees of the store. The email id and
password is verified with our employee registration table data and if matched correctly, provides
access to internal processes like product master, purchase, sales etc.
Fig5.3.2 Employee Login Portal
34. 34
5.3.3. Login Logs:
These logs show us data of all past login attempts in system. Any erroneous entry can be tracked and
traced down by the store manager.
Fig5.3.3 Login History
35. 35
5.3.4. Permission Sales Team:
As the roles are assigned according to the designation of the person in the Organisation. So below
screen shot show the access provided to the Sales Team. The action which a Sales Team can perform
on the System are like they can create a record, view a record and Edit the record but cannot Delete
the record.
Fig5.3.4 Employee Access
36. 36
5.3.5. Permission IT manager:
Below screenshot shows the permissions granted to the IT manager. As visible, the IT manager has
the complete ownership of the objects as well as fields; like he can read, create, edit, delete, and
modify the records.
Fig5.3.5 Manager Access
37. 37
5.3.6. Roles:
Below screenshot shows us the role hierarchy assigned in the system. As we can see the manager
controls and monitors the purchase team, sales team and the team lead.
Fig5.3.6 Designation Hierarchy
38. 38
5.4. Reports:
The reports are based on the data that has been generated through past purchases and sales. These
reports are basically useful for gaining insights into the store’s business and derive key decisions out
of it.
5.4.1. Products purchased:
This report shows us which products are purchased the most and also the frequency of purchase.
This report can be further drilled down on the basis of the spend value on each product.
Fig5.4.1 Purchased Products Dashboard
39. 39
5.4.2. Top vendors:
This report shows us the top vendors from whom the store is getting their products from. We can
also compare the price of a product with several vendors to see which vendor is selling us at lowest
price.
Fig5.4.2 Top Vendors Dashboard
40. 40
5.4.3. Customer Product Sales:
This report shows us which product is frequently bought by the customers. Based on the product
purchase history, the stock can be refilled by the store manager. This will help in avoiding the loss
generated by keeping inventory of only those products that are sold frequently. This report can be
further drilled down to see the contribution of each product to the total sales revenue generated.
Fig5.4.3 Product Sales Dashboard
41. 41
5.4.4. Top customers:
This report provides us insights into the top customers of the store and the products that they have
bought from the store. The store manager can understand from the report which customers are
valuable to the store’s business and can devise marketing strategies to improve the sales.
Fig5.4.4 Top Customers Dashboard
6. Operational Benefits
• A robust CRM solution with almost no development cost.
• The solution is user friendly and it’s very easy to understand the functionality of the
CRM.
• The solution provides various levels of accessibility to the employee depending on
the employee’s designation.
42. 42
• The solution is designed in such a way that multiple users can access it
simultaneously.
• Entire store process is automated and manual labour is reduced to minimum this
results in minimizing errors.
• Live reports and visualisations can be generated which adds the analytics aspect to it
that helps in making better business decisions.
7 Future Work
The retail business has been completely incorporated onto the salesforce platform. This will
not only reduce manual labour but will also improve the profitability of the store. For further
enhancement in the business the e-commerce side of things should be taken into
consideration. An online presence by developing a website which accepts orders and makes
sales online will increase their profitability immensely.
Furthermore, mobile application development will make it easy for the customers to place
orders. This will increase the collection of customer data in the database. This data will later
help deduce strategies to increase the business.
8 References
Hayden, C. (2019) Course Notes: Strategic ICT & eBusiness Implementation: NCI. Available
at:https://moodle.ncirl.ie/course/view.php?id=1862 (Accessed: 22 October 2019).
Salesforce Developers Forums. (2019). DeveloperForce. [online] Available at:
https://developer.salesforce.com/forums/?id=9060G000000Xb3cQAC (Accessed 20 Apr. 2019)
Help.salesforce.com. (2019). Help | Training | Salesforce. [online] Available at:
https://help.salesforce.com/articleView?id=dashboards_add_component.htm&type=5
(Accessed 20 Apr. 2019)
Ramchandani, J. and Ghias, A. (2019). US7962361B2 - Customer relationship management
system for physical locations - Google Patents. [online] Patents.google.com.
Available at: https://patents.google.com/patent/US7962361B2/en [Accessed 20 Apr.
2019].