The developed system successfully performs all major functions, including managing drug, category, and supplier data; recording purchase and sales transactions; automatically updating inventory; providing notifications for minimum stock levels and medicines approaching their expiration dates; and printing transaction reports.
Abstract
Drug data management in most small and medium-sized pharmacies in Indonesia is still carried out manually through ledger books or separate electronic spreadsheets for purchasing, sales, and inventory data. This condition creates various challenges, including recording errors, delays in report preparation, difficulties in monitoring minimum stock levels, and the risk of expired medicines not being detected at an early stage. This study aims to design and implement a web-based pharmacy information system capable of integrating drug data management, purchase transactions, sales transactions, inventory monitoring, and reporting within a single platform. The system development method employed was the waterfall model, consisting of requirements analysis, system design using Unified Modeling Language (UML) and Entity Relationship Diagram (ERD), implementation using the PHP programming language with a MySQL database, and system testing using the black box testing method with the equivalence partitioning technique. The results show that the developed system successfully performs all major functions, including managing drug, category, and supplier data; recording purchase and sales transactions; automatically updating inventory; providing notifications for minimum stock levels and medicines approaching their expiration dates; and printing transaction reports. Black box testing of 15 functional scenarios showed that all scenarios operated as expected and were considered valid. The system is expected to improve data accuracy, accelerate transaction processes, and support decision-making in pharmaceutical procurement at pharmacies.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.