Full-text resources of CEJSH and other databases are now available in the new Library of Science.
Visit https://bibliotekanauki.pl

PL EN


2013 | 128 | 57-62

Article title

Analiza biznesowa w przedsięwzięciach IT

Authors

Content

Title variants

EN
Business Analysis for IT Projects

Languages of publication

PL

Abstracts

EN
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.

Year

Volume

128

Pages

57-62

Physical description

Contributors

author

References

  • Booch G., Rambaugh J., Jacobson I.: UML Przewodnik użytkownika. Wydawnictwo WNT, Warszawa 2002.
  • Kroll P., Kruchten P.: Rational Unified Process od strony teoretycznej. Wydawnictwo WNT, Warszawa 2006.
  • Lech P.: Metodyka ekonomicznej oceny przedsięwzięć informatycznych wspomagających zarządzanie organizacją. Wydawnictwo Uniwersytetu Gdańskiego, Gdańsk 2007.
  • Wrycza S., Marcinkowski B., Wyrzykowski K.: Język UML 2.0 w modelowaniu systemów informatycznych. Wydawnictwo Helion, Gliwice 2006.
  • http://agilemanifesto.org/iso/pl/principles.html.
  • http://pl.wikipedia.org/wiki/Rational_Unified_Process.
  • http://prawo.legeo.pl/prawo/ustawa-z-dnia-29-stycznia-2004-r-prawozamowien- publicznych/.

Document Type

Publication order reference

Identifiers

ISSN
2083-8611

YADDA identifier

bwmeta1.element.desklight-e134d55c-fbd1-4bb3-8032-29151239603d
JavaScript is turned off in your web browser. Turn it on to take full advantage of this site, then refresh the page.