'Bad practice' or 'Bad methods' are software engineering and ethnographic discourses incompatible?

2003 ◽  
Author(s):  
K. Ronkko ◽  
O. Lindeberg ◽  
Y. Dittrich
Keyword(s):  
Software Engineering

Abstraction: An alternative neurocognitive account of recognition, prediction, and decision making

2020 ◽  
Vol 43 ◽  
Author(s):  
Valerie F. Reyna ◽  
David A. Broniatowski
Keyword(s):  
Decision Making ◽  
Software Engineering ◽  
Systems Engineering ◽  
Evidence Based ◽  
Extensive Literature ◽  
Trace Theory ◽  
Fuzzy Trace Theory ◽  
Abstract Representations ◽  
Technical Systems

Abstract Gilead et al. offer a thoughtful and much-needed treatment of abstraction. However, it fails to build on an extensive literature on abstraction, representational diversity, neurocognition, and psychopathology that provides important constraints and alternative evidence-based conceptions. We draw on conceptions in software engineering, socio-technical systems engineering, and a neurocognitive theory with abstract representations of gist at its core, fuzzy-trace theory.

Software Engineering for Real Time Systems

IEE Review ◽  
1992 ◽  
Vol 38 (3) ◽  
pp. 112
Author(s):  
Stuart Bennett
Keyword(s):  
Software Engineering ◽  
Real Time ◽  
Real Time Systems ◽  
Time Systems

Rationale and Design Considerations for a Semantic Mediator in Health Information Systems

1998 ◽  
Vol 37 (04/05) ◽  
pp. 518-526 ◽  
Author(s):  
D. Sauquet ◽  
M.-C. Jaulent ◽  
E. Zapletal ◽  
M. Lavril ◽  
P. Degoulet
Keyword(s):  
Information Systems ◽  
Software Engineering ◽  
Health Information ◽  
Rapid Development ◽  
Heterogeneous Systems ◽  
Health Information Systems ◽  
Semantic Interoperability ◽  
Point Of View ◽  
Current State ◽  
Engineering Environment

AbstractRapid development of community health information networks raises the issue of semantic interoperability between distributed and heterogeneous systems. Indeed, operational health information systems originate from heterogeneous teams of independent developers and have to cooperate in order to exchange data and services. A good cooperation is based on a good understanding of the messages exchanged between the systems. The main issue of semantic interoperability is to ensure that the exchange is not only possible but also meaningful. The main objective of this paper is to analyze semantic interoperability from a software engineering point of view. It describes the principles for the design of a semantic mediator (SM) in the framework of a distributed object manager (DOM). The mediator is itself a component that should allow the exchange of messages independently of languages and platforms. The functional architecture of such a SM is detailed. These principles have been partly applied in the context of the HEllOS object-oriented software engineering environment. The resulting service components are presented with their current state of achievement.

Developing Food Sensory Analysis Information System using Waterfall Software Engineering Model

2017 ◽  
Vol 4 (2) ◽  
pp. 63-81
Author(s):  
Stefanus Oliver ◽  
Abdullah Muzi Marpaung ◽  
Maulahikmah Galinium
Keyword(s):  
Software Engineering ◽  
Sensory Analysis ◽  
Acceptance Testing ◽  
Design Activity ◽  
User Requirements ◽  
Human Errors ◽  
Web Based ◽  
Entity Relationship ◽  
Entity Relationship Diagram ◽  
Analysis System

Food sensory analysis is the terms from the field of Food Technology that has a meaning which means sensory evaluation of food that is conducted by the food sensory evaluators. Currently, food sensory analysis is conductedmanually. It can caus e human errors and consume much ti me. The objective of this research is to build a web based application that is specific for food sensory analysis using PHP programming language. This research followsfour first steps of waterfall software engineering mod el which are user requirements ana lysis (user software and requirements analysis), system design (activity, use cases, architecture, and entity relationship diagram),implementation (software development), and testing (software unit, functionality, validit y, and user acceptance testing). T he software result is well built. It is also acceptable for users and all functionality features can run well after going through those four software testing. The existence of the software brings easiness to deal with the manual food sensory analysis exper iment. It is considered also for the future it has business value by having open source and premium features.

Neural Network Model to Calculate the Creep Data Using Size

2017 ◽  
Vol 7 (8) ◽  
pp. 257
Author(s):  
Seetharam .K ◽  
Sharana Basava Gowda ◽  
. Varadaraj
Keyword(s):  
Neural Network ◽  
Risk Factors ◽  
Software Engineering ◽  
Network Model ◽  
Neural Network Model ◽  
Software Metrics ◽  
Creep Data ◽  
Engineering Software ◽  
Function Points ◽  
Different Levels

In Software engineering software metrics play wide and deeper scope. Many projects fail because of risks in software engineering development[1]t. Among various risk factors creeping is also one factor. The paper discusses approximate volume of creeping requirements that occur after the completion of the nominal requirements phase. This is using software size measured in function points at four different levels. The major risk factors are depending both directly and indirectly associated with software size of development. Hence It is possible to predict risk due to creeping cause using size.

Sign in / Sign up

Export Citation Format

Share Document