Управление финансовым состоянием предприятия (на примере СП ОАО «Спартак»)

The purpose of this paper is to explore the characteristics of information systems (IS) maintenance within an IT and organizational setting. We discuss the characteristics of maintenance objects’ focus and content. Our results are based on qualitative case studies. In this paper a case study of a Swedish Bank is used to illustrate our discussion. Our findings show that maintenance objects can be defined by processes and/or functions or products and/or services within an organizational setting. This is done in order to increase a business perspective in maintenance management and to clarify roles of responsibility for organizational changes required from new IT capabilities. According to our findings maintenance objects can contain business solutions and IT solutions. This implies that business beneficial maintenance is supported by close cooperation between actors from the organizational setting and the IT organization. The result of the paper is a characterization of IS maintenance through definition of maintenance objects’ focus and content

Assessing the Effects of Personal Characteristics and Context on U.S. House Speakers’ Leadership Styles, 1789-2006

Research on congressional leadership has been dominated in recent decades by contextual interpretations that see leaders’ behavior as best explained by the environment in which they seek to exercise leadership—particularly, the preference homogeneity and size of their party caucus. The role of agency is thus discounted, and leaders’ personal characteristics and leadership styles are underplayed. Focusing specifically on the speakers of the U.S. House of Representatives from the first to the 110th Congress, we construct measures of each speaker’s commitment to comity and leadership assertiveness. We find the scores reliable and then test the extent to which a speaker’s style is the product of both political context and personal characteristics. Regression estimates on speakers’ personal assertiveness scores provide robust support for a context-plus-personal characteristics explanation, whereas estimates of their comity scores show that speakers’ personal backgrounds trump context

Towards Automating Source-consistent UML Refactorings

With the increased interest in refactoring, UML tool vendors seek ways to support software developers in applying a (sequence of) refactoring(s)

Software engineering services for export and small developing economies.

A number of authors and multi-national organizations have suggested that providing information services, and in particular software engineering and programming services, for export afford an important economic opportunity for poor countries. Throughout the world, developing countries have acted on this advice. This paper will argue that the opportunities for software engineering services in particular are limited, at least for small developing economies. The main argument is that software engineering and programming are labor-intensive activities and that small developing countries simply do not have the required resources to acquire or train a sufficient number of software engineers and programmers. Any development policy that blindly follows the tenet that small developing countries can improve their economic position through the provision of information services for export is therefore bound to fail. Hence, more sophisticated policies are called for. This paper will also examine a number of such policy options, including an innovative human resource development policy being developed in Jamaica

A delta‐oriented approach to support the safe reuse of black‐box code rewriters

International audienceLarge-scale corrective and perfective maintenance is often automated thanks to rewriting rules using tools such as Python2to3, Spoon or Coccinelle. Such tools consider these rules as black-boxes and compose multiple rules by chaining them: giving the output of a given rewriting rule as input to the next one. It is up to the developer to identify the right order (if it exists) among all the different rules to yield the right program. In this paper, we define a formal model compatible with the black-box assumption that reifies the modifications (∆s) made by each rule. Leveraging these ∆s, we propose a way to safely compose multiple rules when applied to the same program by (i) ensuring the isolated application of the different rules and (ii) identifying unexpected behaviors that were silently ignored before. We assess this approach on two large-scale case studies: (i) identifying conflicts in the Linux source-code automated maintenance and (ii) fixing energy anti-patterns existing in Android applications available on GitHub