Catalogue Search | MBRL
هل أنت متأكد أنك تريد إزالة الكتاب من الرف؟
{{itemTitle}}
4
نتائج ل
"Computer programmers Supervision of."
صنف حسب:
A Probabilistic Approach to PLC Crash Problem
We propose in this work, a new approach based on a probability study to choose the standby Programmable Logic Controller (PLC). Indeed, the solution of standby PLC was adopted by the majority of the industrial companies faced to automated production management and scheduling. This solution proved its efficiency by guaranteeing the continuity of functioning of the equipment of production managed by PLC; the latter can be automatically replaced by another in the case of failure. Unfortunately, this solution has shown its limits. Several anomalies have been identified by the automation specialists. The most known are the not starting up of the standby PLC for various causes. The new developed approach allows not only incrementing the number of standby PLC but also choosing the best one in the replacement task. This choice is based on a new probability approach. Simulations are performed through T.I.A Portal platform.
Journal Article
COMPUTER PROGRAMS DEVELOPED BY INDEPENDENT CONTRACTORS: WHO OWNS THE COPYRIGHT?
This article discusses the question of who owns the copyright in computer programs developed by independent contractors. An important decision by the U.S. Supreme Court last year clarified the ownership issue in a way that expands the ownership rights of independent programmers.
Journal Article
What Do Software Development Managers REALLY Do?
How to measure the productivity of software development staff and how to increase their productivity remain unanswered questions in the field of information processing. Three approaches to the problem include: 1. increased interpersonal skills training, 2. increased productivity through engineering of tools and job, and 3. thorough organization management. In a recent programmer supervision survey, 266 members of the Association for Systems Management, who either currently or previously had been software development managers, were asked to read 6 descriptions of situations that often occur during software development. These situations usually cannot be solved by: 1. programming, 2. finding a bug, or 3. bringing in hardware or a manual. Responses included make-do approaches and documenting the problem, neither of which attempts to solve a problem or requires much skill. Investigating the root causes creates the opportunity for programmers to exercise their analytic skills. Although communication was the most popular response, other sources reveal that over 27% of managers had no supervisory training and, thus, are not prepared for communication activities.
Journal Article