Real Deadlines Research Articles

Ten news value criteria for sustainable journalism

This article argues that journalism scholars and practitioners worldwide should not view 2030, i.e. the year in which the UN Agenda sustainable development goals are to be fulfilled, as a symbolic date, but instead as a real deadline. Such a posture could spur discussion about what more the media could do in these remaining years to promote sustainable development, as well as concrete action. To normatively support such a process in this context, the purpose of this contribution is to suggest news value criteria tailored to manage the challenges of sustainable development. They presuppose a well-functioning relationship between the media’s business and planetary needs. The former concern how to finance journalism and attract audiences/users, while the latter concern what kind of journalism a sustainable world de facto requires. The proposed news value criteria could serve as a point of departure for the development of sustainability-oriented news, which could be jointly tested and configurated by scholars and practitioners.

Definition of neural network model for time series prediction

This article is devoted to solving the issue of forecasting time series in the context of the functionality of project management systems, using the computational resources of neural networks. The article contains the results of analysis of neural network models and conducted experimental studies of the quality of their work, the neural network configuration was selected and adjusted, which allows predicting project execution time with sufficient accuracy. In the process of determining the structure of the neural network for time series prediction, several variants of recurring neural networks and LTSM models with different number of layers and neurons in them were considered, with varying sets of input data. Testing of the quality of neural networks was carried out on a sample of more than 300 thousand tasks for 15 projects accumulated over 8 years. Analysis of the convergence of the data predicted by the neural networks and the real deadlines for completing the tasks made it possible to design the final architecture of the neural network to predict the time of execution of projects. The neural network was developed for further integration into the project management system. The developed neural network was trained and tested. The test results showed that the prediction error in this case was determined within 20 hours. Evaluation of the duration of the task is usually carried out in days, respectively, forecasting by the developed system is carried out up to the day, which can be considered a completely satisfactory result

National spatial data infrastructure (nsdi) of Ukraine: what are its actual, feasible and simultaneously "correct" models?

The actual, feasible and simultaneously "correct" models of digital NSDI of Ukraine are considered in the work. A model of the existed digital NSDI system of Ukraine is named “actual”. This model already differs from the model defined by the [1]. As the latter is unlikely to be implemented in the near future, the issue of the digital feasible NSDI model of Ukraine in the next five years, which would take into account the actual model, is especially acute. In addition to feasibility, such a model must also be "correct", what is proposed in the article. The correct is called a model, the truth of which can be established by inductive or deductive reasoning. To do this, the correct model must be formalized enough so that everyone can verify the authors’ reasoning independently. Understanding both actual and correct models of NSDI of Ukraine will help to properly organize and develop actual Spatial Infrastructure Activities (SpIA) in Ukraine, including the real[1] implementation of the [1]. Although the results of the article call into question its feasibility and substantiate an alternative viewpoint on the automation problem of NGDI/NSDI/SpIA. However, we are convinced that it is still possible to change the alternative viewpoint to a cooperative one, if by means of by-laws the models of NGDI (Law), NSDI (article) and, finally, SpIA are agreed upon To prove the "correctness" of the feasible NSDI model, the theory of Relational cartography and its two main methods are used: Conceptual Frameworks and Solution Frameworks. In addition, the correspondence between Relational cartography and Model-Based Engineering is used. Key words: NSDI; product model; process model; actual, feasible and «correct» model. [1] Real. 1. Which exists in reality, true. Is used with: reality, life, existence, conditions, circumstances, fact, danger, force, wages, income. 2. One that can be implemented, executed: a real plan, a real program, a real task, a real deadline. 3. Which is based on taking into account and assessing the real conditions of reality: a real approach, a real view, a real policy.- accessed 2021-feb-14, http://slovopedia.org.ua/32/53408/32016.html (Ukrainian).

Creating a Construction Schedule Specyfing Fuzzy Norms and the Number of Workers

Abstract The basic element of a project organizing construction works is a schedule. The preparation of the data necessary to specify the timings of the construction completion as indicated in the schedule involves information that is uncertain and hard to quantify. The article presents the methods of building a schedule which includes a fuzzy amount of labour, time standards and number of workers. The proposed procedure allows determining the real deadline for project completion, taking into account variable factors affecting the duration of the individual works.

Innovative Teaching of IC Design and Manufacture Using the Superchip Platform

This paper describes how an intelligent chip architecture has allowed a large cohort of undergraduate (UG) students to be given effective practical insight into integrated circuit (IC) design by designing and manufacturing their own ICs. To achieve this, an efficient chip architecture, the ?Superchip,? was developed, which allows multiple student designs to be fabricated on a single IC, and encapsulated in a standard package without excessive cost in terms of time or resources. This paper demonstrates how the practical process has been tightly coupled with theoretical aspects of the degree course and how transferable skills are incorporated into the design exercise. Furthermore, the students are introduced at an early stage to the key concepts of teamwork, exposure to real deadlines, and collaborative report writing. This paper provides details of the teaching rationale, design exercise overview, design process, chip architecture, and test regime.

Design Alternatives for a MediaWiki to Support Collaborative Writing in Higher Education Classes

Introduction Wikis can be used to facilitate collaborative writing. Through the use of a wiki for a group writing project we discovered that some mechanisms can be added to wikis to support collaborative group writing in higher education. Collaborative writing can be used for varied purposes, which we term mandatory, optional, and hybrid. Based on the success of Wikipedia, it is generally assumed that a wiki is an effective collaborative writing tool. However, Wikipedia supports an optional collaborative writing purpose. Members of the Wikipedia community are voluntarily involved in a project that does not have deadlines or specific goals that the project needs to achieve. In contrast, a mandatory purpose in this context is one in which a group must finish its project within a specific timeline. Examples of this type of collaborative writing are class projects and responses to requests for proposals. Both these purposes require a different project management style. In the mandatory case, project management must be formally applied or the deadline will not be met. In the optional case, there is no necessity for formal project management. A hybrid purpose, which has characteristics of the other two, is one where a project can be considered completed but with no real deadline. Examples of this hybrid purpose are a white paper being authored by a Community or Practice (CoP) and a set of requirements for an open source software project. We address mandatory collaborative writing in higher education in the paper. Cunningham (2006) created the concept of a wiki. He specified a number of characteristics that he envisioned as necessary for enabling collaborative knowledge sharing. In this paper, we report on the problems encountered in using MediaWiki (one of the most popular wiki engines) in a classroom-based collaborative writing project. First, we review the literature on constructivist learning. Next, we compare the needs of the mandatory and optional purposes with the goals that Cunningham specified. Then, we provide a description of the course and its processes. We show that a wiki has the potential to support mandatory purposes, but requires additional facets to do so effectively. Next, we define the objectives for a solution and propose three mechanisms for MediaWiki to provide aid for discussion, evaluation, and project management functionality, and better support mandatory collaborative writing. The significant contribution of this study is these mechanisms, which can facilitate group writing and constructivist learning processes. We describe the of these three mechanisms and explain how they support group writing and constructivist learning processes. Then, we conduct a preliminary demonstration and evaluation. The paper concludes with limitations and proposed plug-ins development and testing. Research Question Current wiki technology has several challenges in the way it supports collaborative writing, such as how group members delegate responsibilities, how they coordinate with each other, and how they evaluate the content of wiki pages. Therefore, we posed the following question: Can we mechanisms to facilitate collaborative group writing in a classroom setting? To answer this question, we used our experience from a class that used MediaWiki as a mandatory collaborative writing tool using a science methodology. Design Science Research According to Hevner, March, Park, and Ram (2004, p. 79), design science addresses research through the building and evaluation of artifacts designed to meet the identified business need. This study follows six activities of science research methodology (DSRM): 1) problem identification and motivation; 2) defining the objectives for a solution; 3) and development; 4) demonstration; 5) evaluation; 6) communication (Peffers, Tuunanen, Rothenberger, & Chatterjee, 2007). The purpose of the study is to useful mechanisms for groups who are writing wiki pages, which need tools to support discussion and collaboration and help instructors with the assessment of collaborative student work. …

(Dis)trust in Software Projects: A Thrice Told Tale: On Dynamic Relationships between Software Engineers, IT Project Managers, and Customers

Software development traditionally has been a field particularly prone to delays, exceeding budgets, and misunderstandings (May 1998; Connel, 2001; Humphrey, 2002; Goodwin, 2002; Kesteloot, 2003). Only 1/4 of IT projects is completed successfully – i.e. in time, with the assumed cost, and fulfilling the promised functionality (Smith and Keil, 2003). Although there is some improvement over the last years, software creation is still one of the most unpredictable businesses in the world. It should not be surprising then that high-tech environment often is described as stressful an demanding (Kunda, 1992; Hochschild, 1997; Perlow, 1998; Cooper, 2000; Jemielniak, 2005). It is the nest of the so-called normative control: management by indirect reign, through the means of evoking motivation and dedication of the employee, rather than physical direction and supervision (Kanter, 1977; Mintzberg, 1998). On the other hand, many things have to be taken on face value: program code is a black-box for anyone but the programmer, only the client understands the real needs for the software, only the manager realizes what the real deadlines and constraints are, etc. In this light it may be interesting to delve into the issue of actual organizational practices in IT environment. Thus, in this paper we will try to analyze how the trust in software projects is understood, perceived and exercised by the key organizational actors involved. According to our research, there are three major groups of actors in software development: managers, clients, and software engineers. These roles play an important defining function in IT reality. The stories told by our interviewees all point to trust, or rather the distrust in software development. In the proposed paper we would like to confront the three views in an ethnographical manner.