Foraging Time Constraints and Diet Choice

1987 ◽  
pp. 239-269 ◽  
Author(s):  
Jeffrey R. Lucas
Keyword(s):  
Time Constraints ◽  
Diet Choice ◽  
Foraging Time

Time Constraints and Diet Choice: Different Predictions from Different Constraints

1985 ◽  
Vol 126 (5) ◽  
pp. 680-705 ◽  
Author(s):  
Jeffrey R. Lucas
Keyword(s):  
Time Constraints ◽  
Diet Choice

The effects of time constraints and changes in body mass and satiation on the simultaneous expression of caching and diet-choice decisions

1993 ◽  
Vol 45 (4) ◽  
pp. 639-658 ◽  
Author(s):  
Jeffrey R. Lucas ◽  
Lynda J. Peterson ◽  
Raquel L. Boudinier
Keyword(s):  
Body Mass ◽  
Time Constraints ◽  
Diet Choice ◽  
Simultaneous Expression

Gender Differences in the Mental Rotations Test (MRT) Are Not Due to Task Complexity

2008 ◽  
Vol 29 (3) ◽  
pp. 130-133 ◽  
Author(s):  
Corinna Titze ◽  
Martin Heil ◽  
Petra Jansen
Keyword(s):  
Gender Differences ◽  
Mental Rotation ◽  
Task Complexity ◽  
Time Constraints ◽  
Medium Effects ◽  
Performance Factors ◽  
Mental Rotations ◽  
Sufficient Power ◽  
Forced Choice Tasks ◽  
Choice Tasks

Gender differences are one of the main topics in mental rotation research. This paper focuses on the influence of the performance factor task complexity by using two versions of the Mental Rotations Test (MRT). Some 300 participants completed the test without time constraints, either in the regular version or with a complexity reducing template creating successive two-alternative forced-choice tasks. Results showed that the complexity manipulation did not affect the gender differences at all. These results were supported by a sufficient power to detect medium effects. Although performance factors seem to play a role in solving mental rotation problems, we conclude that the variation of task complexity as realized in the present study did not.

Time Constraints Limit Full-Body Skin Exams

2011 ◽  
Vol 41 (2) ◽  
pp. 35
Author(s):  
MARY ANN MOON
Keyword(s):  
Time Constraints ◽  
Full Body

ARCHITECTURE OF PORTS AND ADAPTERS IN ITERATIVE DEVELOPMENT WITH LIMITATIONS ON TIME

2019 ◽  
Author(s):  
Olexandr Grebenuk ◽  
Volodymyr Pavlenko
Keyword(s):  
System Structure ◽  
Time Constraints ◽  
Iterative Development ◽  
Rest Service ◽  
Defining System ◽  
Rules And Principles ◽  
Concurrent Development ◽  
Iterative Software ◽  
The One ◽  
Mail Service

The application of ports and adapters architecture (other names bulbous, layered, hexagonal) in iterative software development is considered in accordance with the requirements that come in chronological order in the practical example. Each iteration is supported by the schema architecture, problems encountered and their solution. The expediency of using the considered architecture in the iterative development of software with time constraints is shown. The system of collecting data on the concentration of carbon dioxide of the environment and air temperature in real time from a distributed network of sensors with a predetermined geolocation for medical institutions was developed. Put sensor information (ID, commissioning date and end date) in the Google Sheets spreadsheet. The data from the sensors should be collected on the server by REST service. The process of PPP in a specific project with significant time constraints is investigated, applying the rules and principles laid down in the architecture of ports and adapters, using the basic metrics to evaluate the complexity of adding new functionality, testing, concurrent development, speed and ease of development; draw conclusions about the conditions when it is appropriate to apply the chosen software design approach, and the ability of such an approach to perceive software requirements changes. The architecture of ports and adapters is useful if the system has many external integrations (mail service, push messages, databases, reporting system, etc.). The one-way communication with adapters guarantees the integrity of the main algorithmic part of the program. A thorough knowledge of the domain allows you to immediately determine the domain layer. Building a system structure that optimally reflects the domain requires the most time, and it will be costly in the future to correct errors made during the process of defining system layers (interfaces and systems). Domain logic testing is fast due to Unit tests, other tests are easy to write due to the small connectivity between layers. This architecture is not a completely new approach, but it takes the best of OOP, SOLID, DDD and determines how to apply these principles in the best way.

Sign in / Sign up

Export Citation Format

Share Document