Flow—Applying Industrial Insights to Software Production

2020 ◽  
pp. 277-290
Author(s):  
Peter Middleton ◽  
James Sutton
Keyword(s):  
Software Production

scholarly journals Model-driven development platform selection: four industry case studies

2021 ◽  
Author(s):  
Siamak Farshidi ◽  
Slinger Jansen ◽  
Sven Fortuin
Keyword(s):  
Decision Making ◽  
Case Studies ◽  
Decision Makers ◽  
Development Activity ◽  
Model Driven Development ◽  
Domain Experts ◽  
Theoretical Contribution ◽  
Model Driven ◽  
Development Platform ◽  
Software Production

AbstractModel-driven development platforms shift the focus of software development activity from coding to modeling for enterprises. A significant number of such platforms are available in the market. Selecting the best fitting platform is challenging, as domain experts are not typically model-driven deployment platform experts and have limited time for acquiring the needed knowledge. We model the problem as a multi-criteria decision-making problem and capture knowledge systematically about the features and qualities of 30 alternative platforms. Through four industry case studies, we confirm that the model supports decision-makers with the selection problem by reducing the time and cost of the decision-making process and by providing a richer list of options than the enterprises considered initially. We show that having decision knowledge readily available supports decision-makers in making more rational, efficient, and effective decisions. The study’s theoretical contribution is the observation that the decision framework provides a reliable approach for creating decision models in software production.

scholarly journals Building resilient medical technology supply chains with a software bill of materials

2021 ◽  
Vol 4 (1) ◽  
Author(s):  
Seth Carmody ◽  
Andrea Coravos ◽  
Ginny Fahs ◽  
Audra Hatch ◽  
Janine Medina ◽  
...  
Keyword(s):  
Supply Chains ◽  
Food Packaging ◽  
Production Costs ◽  
Third Party ◽  
Software Components ◽  
Bill Of Materials ◽  
Software Production ◽  
Software Product ◽  
Healthcare Technologies ◽  
Affect Patient Care

AbstractAn exploited vulnerability in a single software component of healthcare technology can affect patient care. The risk of including third-party software components in healthcare technologies can be managed, in part, by leveraging a software bill of materials (SBOM). Analogous to an ingredients list on food packaging, an SBOM is a list of all included software components. SBOMs provide a transparency mechanism for securing software product supply chains by enabling faster identification and remediation of vulnerabilities, towards the goal of reducing the feasibility of attacks. SBOMs have the potential to benefit all supply chain stakeholders of medical technologies without significantly increasing software production costs. Increasing transparency unlocks and enables trustworthy, resilient, and safer healthcare technologies for all.

scholarly journals METRICS DEVELOPMENT FOR THE QUALIS OF SOFTWARE TECHNICAL PRODUCTION

2015 ◽  
Vol 42 (suppl 1) ◽  
pp. 73-75
Author(s):  
Marinho Jorge Scarpi
Keyword(s):  
Software Quality ◽  
Software Metrics ◽  
Development Process ◽  
International Organization ◽  
System Behavior ◽  
Technical Standards ◽  
Quality Perception ◽  
Software Production ◽  
Technical Production ◽  
Intellectual Production

Objective: To recommend metrics to qualify software production and to propose guidelines for the CAPES quadrennial evaluation of the Post-Graduation Programs of Medicine III about this issue. Method: Identification of the development process quality features, of the product attributes and of the software use, determined by Brazilian Association of Technical Standards (ABNT), International Organization Standardization (ISO) and International Electrotechnical (IEC), important in the perspective of the CAPES Medicine III Area correlate users, basing the creation proposal of metrics aiming to be used on four-year evaluation of Medicine III. Results: The in use software quality perception by the user results from the provided effectiveness, productivity, security and satisfaction that originate from its characteristics of functionality, reliability, usability, efficiency, maintainability and portability (in use metrics quality). This perception depends on the specific use scenario. Conclusion: The software metrics should be included in the intellectual production of the program, considering the system behavior measurements results obtained by users' performance evaluation through out the favorable responses punctuation sum for the six in use metrics quality (27 sub-items, 0 to 2 points each) and for quality perception proof (four items, 0 to 10 points each). It will be considered as very good (VG) 85 to 94 points; good (G) 75 to 84 points; regular (R) 65 to 74 points; weak (W) 55 to 64 points; poor (P) <55 points.

Sign in / Sign up

Export Citation Format

Share Document