![]() ![]() Thus, this paper will aim at simply define the keywords from the computer science area: algorithm, automation and intelligent systems (artificial intelligence), evaluate the systems that are in use in the Brazilian Justice System, specifically indicating in which category they fall and, finally, discuss the impact of using intelligent systems without any human intervention in the context of the so called 'Law 4.0'. However, the general understanding of what algorithms, automation and intelligent systems can be or perform are very foggy and, more often than not, we can see the word 'intelligent' being used inadvertently. In the justice area, it has not been different, and, particularly, in the Brazilian Justice system, there is a strong move to have as much automation, digitalisation of the processes as possible. With this move, the 'realisation' that there are several possible ways to perform automation including the use of intelligent systems came to light and it has become a particular favourite term used in any situation to name any computational system. From health to education, we can see more and more the digitalisation and the automation taking a key part of the work involved in managing data (being it private or public) and optimising the processes in general. There is a digital revolution, called Industry 4.0, happening around the world (and therefore, in Brazil as well!) that is shifting our activities from an 'ana-logic' to a 'digital' format. For the development values and guidelines must be really clear, and they will be addressed by deductive method, from the findings on Artificial Intelligence (AI), Law and the agile method. Therefore appears the need of an integrative methodology, that allows the implementation of advanced artificial intelligence instruments for the legal area. For its unprecedented factor, all researchers must develop knowledge in a intense, while working in different thought process, language and very specific methodologies. The Victor project demands knowledge and researchers from the areas of software engineering, computer science and Law. Thanks so much - I spent days in trying to find the solution, and I am desperate for helpful advice.This paper has the goal to present the development of an instrumental solution to a necessity raised from the work plan established in a AI project between the University of Brasilia and the Brazilian Supreme Court, called "Research and development project on machine learning about judicial data on general repercussion in the Supreme Court", latter called Victor Project. Obviously the correct screen already exists in our Jira (and I don´t have to create a new one, as recommended earlier). copied the screem scheme from project A to B -> no difference compared the workflows of project A and B for differences in the validators or Post Functions, as recommended in an earlier post - no difference Project B simply transitions the issue to closed WITHOUT opening up this screen.įor us, it is important to know why an issue was closed for later follow up, and therefore we want the screen "Closed" with the options to select from displayed every time we transition an issue to closed. ![]() When I transition an issue to "Closed", project A opens up a screen titled "Closed" (see below) offering me a range of reasons why the issue was closed ("won´t do", "Duplicate", "hardware failure"etc.). I have two projects, A and B, and for some reason one of them shows a different behaviour than the other: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |