MMAIM: a software development method for Ada, part II—Example

1988 ◽  
Vol VIII (5) ◽  
pp. 47-60 ◽  
Author(s):  
J. Carter
Keyword(s):  
Software Development ◽  
Development Method

Research on MES Domain Analysis Driven by Ontology

2010 ◽  
Vol 20-23 ◽  
pp. 1084-1090 ◽  
Author(s):  
Wen Long
Keyword(s):  
Control System ◽  
Software Development ◽  
Method Development ◽  
Domain Analysis ◽  
Manufacturing Execution System ◽  
Development Method ◽  
And Performance ◽  
And Control ◽  
Plan Management ◽  
Manufacturing Execution

Manufacturing Execution System (MES) links plan management and workshop control in an enterprise, which is an integrative management and control system of workshop production oriented to manufacturing process. To overcome the difficulties of traditional software development method, development of MES based on component is adopted to prompt development efficiency and performance of MES, which can be more reconstructing, reuse, expansion and integration, and MES domain analysis driven by ontology is investigated in detail. MES domain analysis driven by ontology is feasible and efficient through developing a pharmaceutics MES which applied in a pharmaceutics manufacturing factory.

Software Evolution Rules with Condition Constrains to Support Component Type Matching Based on Bigraph

2018 ◽  
Vol 28 (10) ◽  
pp. 1429-1453 ◽  
Author(s):  
Chao-Ze Lu ◽  
Guo-Sun Zeng ◽  
Wen-Juan Liu
Keyword(s):  
Information System ◽  
Software Development ◽  
Software Architecture ◽  
Software Evolution ◽  
Type System ◽  
Reaction System ◽  
Basic Component ◽  
Development Method ◽  
Component Type ◽  
Tourism Information

With the gradual maturity of component oriented software development method, component-based software evolution technology has become hot research in academia and industry. Although many evolution rules are designed, they rarely consider component type-mismatched problem in evolution rules. This has led to evolution rules that often run error in software evolution execution. Hence, focusing on the mismatch problem of component type in software evolution, this paper addresses various evolution rules with condition constrains to support component type matching. First, we use the bigraph theory to model the software architecture and employ bigraph term language to describe the basic component evolution operations. Second, we join type system into the term language and use the type term language to express the condition constraints on position and connection for component evolution rules. These condition constraints can guarantee the type-matched among components that participate in software evolution. Furthermore, we show that the component type-matched still kept during a number of different evolution rules are used in the whole software evolution reaction system. Finally, two cases study of evolution progress of ATM system and tourism information system are presented. Two cases illustrate the effectiveness of our approach.

scholarly journals SISTEM INFORMASI DETEKSI KEHADIRAN DAN MEDIA PENYAMPAIAN PENGUMUMAN DOSEN DENGAN MENGGUNAKAN TEKNIK PENGENALAN QR CODE

2018 ◽  
Vol 3 (2) ◽  
pp. 89-99
Author(s):  
Harun Mukhtar
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Programming Language ◽  
Qr Code ◽  
Web Based ◽  
Development Method ◽  
The University

“Information Systems of Attendance Detection and Media Submission of Lecturer Announcement by Using Engineering Introduction QR Code "is an application that serves to support the process of disseminating information on the campus of Muhammadiyah University of Riau to become more effective and efficient and facilitate students in obtaining information. This application can be used by Lecturers and Students as recipient of information. The results of this study is a web-based application that can support the process of disseminating information on the campus of the University of Muhammadiyah Riau. The research was built using the Waterfall software development method, using UML to document, specify, and model the system. Implemented using PHP programming language using Laravel Framework and using MySQL database and other supporting software.

Barriers and Value Co-Destruction in a B2B Project Management Context: Agile Software Development Adoption and Rejection in Japanese Organizations

2020 ◽  
Vol 6 (2) ◽  
pp. 155-176
Author(s):  
Nobuhiko Seki ◽  
Youji Kohda
Keyword(s):  
Software Development ◽  
Diffusion Process ◽  
Service Innovation ◽  
Agile Software Development ◽  
Project Managers ◽  
Service Concept ◽  
Development Method ◽  
Management Context ◽  
Business To Consumer ◽  
Agile Software

A new service concept meets some resistance from those who face it prior to adoption. If the resistance cannot be overcome, the new service will not be diffused. There have been many studies of business-to-consumer (B2C) contexts on adoption and rejection of product and service innovation. The question remains, what barriers should be overcome in the diffusion process of new services in the business-to-business (B2B) contexts? For example, if you implement a new service concept to your organization to create new value with your customers, what barriers does your organization need to overcome? Few studies to date have revealed the issue. To identify barriers for adoption, this study focuses on the diffusion process of the Agile software development method in Japanese organizations, which is still in progress, and attempts to approach the adoption barriers for service innovation in the B2B context to understand the barriers and leverage point for overcoming them. The Agile software development method is an innovation of software development. But there is a possibility that its diffusion will be stopped due to the resistance of project managers involved in a software development. This may lead service systems to value co-destruction as well.

Management Issues in Portlet Development

2011 ◽  
pp. 564-570
Author(s):  
Tony Polgar ◽  
Jana Polgar
Keyword(s):  
Software Development ◽  
High Availability ◽  
Future Trends ◽  
Technological Properties ◽  
Development Method ◽  
Development Methodology ◽  
The Right ◽  
Managerial Experience ◽  
Development Manager ◽  
Selection Of

Software development methodology refers to a standardised, documented methodology which has been used before on similar projects or one which is used habitually within an choice of software development method, and applying the right method for the job. From this perspective, the portlet development encounters new circumstances which affect the chosen method. A portal development manager must be aware of the technological properties and constraints, because there development and deployment processes. These issues are not well defined yet; there is no proven methodology for driving portal projects. This article provides discussion of practical approaches to the resolution of development issues and risks in portal environment. The discussed topics include implementation of portals in enterprise environment, portlet applications’ high availability, portlet disaster recovery, and cost of portlet deployment. An attempt is made to forecast future trends in portlet technology at the end of the article, as well as suggest the directions for the flexible selection of methodologies and managerial experience suited to the portal development.

Tool Support for Software Artefact Traceability in DevOps Practice

2020 ◽  
pp. 130-167
Author(s):  
Iresha Rubasinghe ◽  
Dulani Meedeniya ◽  
Indika Perera
Keyword(s):  
Software Development ◽  
Impact Analysis ◽  
Software Process ◽  
Source Code ◽  
Tool Support ◽  
Management Approach ◽  
Development Method ◽  
Continuous Integration ◽  
Trace Link ◽  
F Measure

Software development in DevOps practice is a widely used approach to cope with the demand for frequent artefact changes. These changes require a well-defined method to manage artefact consistency to ease the continuous integration process. This chapter proposes a traceability management approach for the artefact types in the main phases of the software process including requirements, design, source code, testing, and configuration. This chapter addresses traceability management, including trace link creation, change detection, impact analysis, change propagation, validation, and visualisation. This chapter presents a tool named SAT-Analyser that is applicable for any software development method and designed for continuous integration, multi-user collaboration, and DevOps tool stack compatibility. The SAT-Analyser is assessed using case studies and shown an impact analysis accuracy of 0.93 of F-measure. Further, the feedback by DevOps practitioners has shown the suitability and innovativeness of the proposed approach.

Sign in / Sign up

Export Citation Format

Share Document