Work that is performed at the stage of the analysis should not only be characterized by addressing the issues directly related to the same product - a computer system. It turns out that the products produced at that stage should be skillfully managed within IT projects. Results and analytical products should merge two parallel and complex environments: - needs of the organization - customer's, the future user of the system, - the manufacturing team of the contractor and the resulting properties. Reconciling of above factors affecting the work, probably should have an overriding goal in mind, where we speak of business needs across the organization - the customer, the direction of its evolution. Analytical products on the one hand define specific and present beings, on the other, should have flexibility and allow support for future changes. This work should be characterized not only predictable effects directly affecting the fate of the implemented projects, but also the future ones related to the evolution of the organization and its business needs, where methodological - tool workshop of the analyst is extremely important. The competence of decision makers in this area is often built over many years. Indeed, exploration of this knowledge is not trivial and takes time. Certainly the training and competence, confirmed by international certificates helps to make the right decisions. But it was the defining of role the of the analyst in a real and specific workplace - provides appropriate reference point , that is needed in the implementation of relevant work for the client and contractor. The experiences of a person working as analyst in IT projects, have led to the conclusions outlined in this article, which made it clear that later it would be needed to carry out scientific work, aimed to provide a definition. It would be a definition that would accept the proportions and agreed ideas from two separate areas of expertise: software engineering and economics. Thus, there would be some legitimate points of reference and guidelines for the production teams, which would inform about the impact of analytical products - that seem to be the most important results of the work in any IT project - on the course of the project and software engineering.
The article describes an original project to implement a resource school solution, which in the case described is focused on intellectual capital. In addition to the project and the organization, what is important here is the human being – the creator of knowledge and value. The research study is concerned with the academic teaching profession and IT subjects, and as a result, the implementation of the university’s pragmatic mission understood as meeting the needs of society. For this purpose, the author uses Educational Action Research (EAR). The publication presents empirical research based on more than 8 years of experience of a research and teaching employee, documented through sites.google.com. Conclusions are drawn from the 12 edited scientific publications, 17 teaching presentations, and 2 projects popularizing software engineering practices posted in these resources. The author tries to respect the concept of network strategy – understood by the process of value creation using the resources and competencies of all its members. In doing so, the author draws on the practices of relational and network approaches, and seeks to adapt such IT solutions that allow the management of social capital. The possible and expected consequences of the publication, following the keynote of intervention research in education, is a discussion in the teacher‑research community.
PL
Artykuł opisuje oryginalny projekt implementacji systemu szkoły zasobowej. Celem publikacji jest przedstawienie wyników badań empirycznych wynikających z realizacji tego projektu w środowisku akademickim. Badania przeprowadzono w ramach projektu wykorzystującego podejście modelowe do wytwarzania oprogramowania (Model Driven Development). Autor wykorzystał w tym celu badania interwencyjne w edukacji (Educational Action Research). Publikacja przedstawia ponad ośmioletnie doświadczenia pracownika naukowo‑dydaktycznego, udokumentowane za pośrednictwem usługi sites.google.com. Wnioski wynikają z dwunastu zredagowanych publikacji naukowych, siedemnastu prezentacji dydaktycznych oraz dwóch projektów – popularyzujących praktyki inżynierii oprogramowania. Autor stara się respektować koncepcję strategii sieciowej, rozumianej jako proces tworzenia wartości z wykorzystaniem zasobów i kompetencji wszystkich jej członków. Czerpie przy tym z praktyk podejścia relacyjnego i sieciowego oraz dąży do adaptacji takich rozwiązań informatycznych, które pozwalają na zarządzanie kapitałem społecznym. Możliwymi i oczekiwanymi następstwami publikacji, w myśl badań interwencyjnych w edukacji, jest dyskusja w środowisku nauczycieli‑badaczy.
JavaScript is turned off in your web browser. Turn it on to take full advantage of this site, then refresh the page.