Definition Constructed Process in Mathematics Learning

Salah satu faktor yang dapat mendukung kemampuan profesional guru adalah penguasaan guru tentang ilmu psikologi kognitif. Salah satu kajian dari ilmu kognitif adalah tentang bagaimana siswa belajar. Tulisan ini membahas tentang bagaimana pemahaman terhadap definisi berkembang dalam pikiran siswa. Seorang guru tidak hanya memfasilitasi siswa untuk memiliki konsep definisi sebaiknya sampai memiliki konsep image

A uniform definition of stochastic process calculi

We introduce a unifying framework to provide the semantics of process algebras, including their quantitative variants useful for modeling quantitative aspects of behaviors. The unifying framework is then used to describe some of the most representative stochastic process algebras. This provides a general and clear support for an understanding of their similarities and differences. The framework is based on State to Function Labeled Transition Systems, FuTSs for short, that are state-transition structures where each transition is a triple of the form (s; α;P). The first andthe second components are the source state, s, and the label, α, of the transition, while the third component is the continuation function, P, associating a value of a suitable type to each state s0. For example, in the case of stochastic process algebras the value of the continuation function on s0 represents the rate of the negative exponential distribution characterizing the duration/delay of the action performed to reach state s0 from s. We first provide the semantics of a simple formalism used to describe Continuous-Time Markov Chains, then we model a number of process algebras that permit parallel composition of models according to the two main interaction paradigms (multiparty and one-to-one synchronization). Finally, we deal with formalisms where actions and rates are kept separate and address the issues related to the coexistence of stochastic, probabilistic, and non-deterministic behaviors. For each formalism, we establish the formal correspondence between the FuTSs semantics and its original semantics

Software Project Failure Process Definition

Many researchers have attempted to identify the factors behind software project failures and their solutions from various perspectives. However, systematic and integrated process definitions of failure as process models for success are lacking. This study aims to build a process definition for software project failure as an anti-pattern by identifying the main phases and their relationships in terms of team behavior. We researched software engineering literature and case studies to gather information about critical incidents and repeating behaviors of teams in failed projects into a novel dataset. Grounded theory was employed to build a theoretical foundation for failure phase definitions from the collected data. The design structure matrix and Bayesian belief network were used for the quantitative assessment of the transitions between phases. The results revealed that common behavioral patterns occurred in approximately 89 percent of the case studies, supporting the decision to consider software project failure as a process. The proposed failure process definition has a simple structure that uses everyday concepts for phase names and reveals the critical behaviors leading a software project to failure Thus, it provides critical insights for software professionals, non-technical stakeholders, and managers to evaluate the progress of their projects and design strategies to avoid failure

Designer's Education to User's Definition Process

AbstractCorrect identification of human capabilities and limitations is essential when designing objects, activities or environments that must facilitate the accomplishment of User's activities. Such identification task is performed routinely in the disciplines of human factors, particularly Ergonomics in Design, given the relevance of that aspect in the correct definition of the characteristics that mediate between users and the system in which is immersed. Day by day numerous technologies, methods, strategies and techniques are developed, that in addition to existing ones, are intended to facilitate the approach to define who the User is, by detecting and analyzing her or his skills and limitations, ways of thinking and behaving when exposed to various stimuli and circumstances leading to an expansion of human knowledge and provides invaluable input to Designing but such tools, techniques and technologies are often quite distant from design practitioner, meaning, it requires working with other fields specialists to usefully incorporate information for design process. Design education should be transdisciplinary

NTP comparison process

The systems engineering process for the concept definition phase of the program involves requirements definition, system definition, and consistent concept definition. The requirements definition process involves obtaining a complete understanding of the system requirements based on customer needs, mission scenarios, and nuclear thermal propulsion (NTP) operating characteristics. A system functional analysis is performed to provide a comprehensive traceability and verification of top-level requirements down to detailed system specifications and provides significant insight into the measures of system effectiveness to be utilized in system evaluation. The second key element in the process is the definition of system concepts to meet the requirements. This part of the process involves engine system and reactor contractor teams to develop alternative NTP system concepts that can be evaluated against specific attributes, as well as a reference configuration against which to compare system benefits and merits. Quality function deployment (QFD), as an excellent tool within Total Quality Management (TQM) techniques, can provide the required structure and provide a link to the voice of the customer in establishing critical system qualities and their relationships. The third element of the process is the consistent performance comparison. The comparison process involves validating developed concept data and quantifying system merits through analysis, computer modeling, simulation, and rapid prototyping of the proposed high risk NTP subsystems. The maximum amount possible of quantitative data will be developed and/or validated to be utilized in the QFD evaluation matrix. If upon evaluation of a new concept or its associated subsystems determine to have substantial merit, those features will be incorporated into the reference configuration for subsequent system definition and comparison efforts

Definition of a goal elicitation process

Requirement Engineering plays an essential role at the initial stage in the software development life cycle. This discipline entails three processes: Requirements Elicitation, Specification and Validation. Elicitation has, as a primary goal, the knowledge acquisition over a problem domain. In order to do this, different techniques are applied according to the kind of information to be elicited and the time and resources available for the analyst. One of the most important techniques is Goal Analysis. It was established, once analysed the most important approaches as far as use is concerned (GBRAM, KAOS, Softgoals, Ideas, Rolland, Loucopoulos) that those approaches lack a Goal Elicitation Process, in other words, they lack a methodology that shows clearly what are to be made to obtain Goals. This Thesis proposes a process to elicit Goals based on Annie Antón's approach (GBRAM) from Scenarios applying the schema proposed by Julio Leite. To do this 12 rules were defined which, applied to Scenario elements, allow us to obtain the goal elements with GBRAM schema.Es revisión de: http://sedici.unlp.edu.ar/handle/10915/4084Dossier: Resumen de la tesis presentada por el autor para la obtención del título de Magister en Ingeniería de Software (UNLP) en al 2005.Facultad de Informátic