Dec 2026· Jurnal Ilmiah Informatika dan Komputer· 0 citations· 38 references
Abstract
Micro, Small, and Medium Enterprises (MSMEs) in the Indonesian culinary sector frequently face operational bottlenecks and customer decision fatigue during peak dining hours due to manual menu selection and conventional order-taking mechanisms. Preliminary field observations at Pondok Orange Restaurant in Pontianak revealed that customer menu deliberation required 6.5 to 8.2 minutes per table, while ordering queues extended up to 25 minutes during peak meal intervals. To address these operational challenges, this study designs and implements a web-based food menu recommender system utilizing the Technique for Order Preference by Similarity to Ideal Solution (TOPSIS). The recommendation framework integrates two complementary data dimensions: Customer Preferences (incorporating menu selling price as a cost attribute and customer satisfaction ratings as a benefit attribute) and Operational Ordering Patterns (incorporating daily order frequency and real-time kitchen ingredient availability as benefit attributes). Developed using the Extreme Programming (XP) methodology on the Laravel framework, the system executes TOPSIS matrix computations with linear algorithmic complexity O(m × n) in under 5 ms without requiring extensive historical customer logs. Computational evaluation shows that Bubur Pedas achieved the highest preference score of 0.6498, securing the top recommendation ranking. Initial user acceptance testing with 30 dine-in patrons demonstrated strong alignment, yielding a Top-1 recommendation hit rate of 73.3%, a Top-3 hit rate of 90.0%, and an overall usability and relevance satisfaction score of 4.38 out of 5.00. Software verification via White-Box Testing (Statement Testing and Basis Path Testing, V(G) = 4) confirmed that all four independent algorithmic paths and mathematical boundary conditions executed successfully according to technical design specifications.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
AI agents can generate code at a scale that’s hard for humans to review line-by-line. PDD Kit helps ensure the code is doing what the developer intended by creating formal specifications and testing against them. It converts developer intent into a Verus specification, proves AI-generated code meets it for every input, and uses tests where proofs aren't practical. Developers review intent, not every line. The post Formally verifying agent-written full-stack web apps with PDD Kit appeared first o…
Is your company’s AI sovereign? A practical guide for CIOs on AI vendor lock-in, EU Data Act switching, cloud sovereignty, and testing your exit plan before you need it. The post Sovereignty Is the Option to Leave appeared first on GPT-Lab.
Microsoft Research Blog· microsoft.comOct 30, 2026
Evaluating Microsoft Copilot at enterprise scale requires test data that captures the full complexity of real organizations, yet real enterprise data contains sensitive information that cannot be used for evaluation under any circumstances. The post From synthetic enterprise data evaluations to real Microsoft Copilot AI confidence appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.