Definisanje korisničkih zahteva pri razvoju softvera

Abstract

Cilj ovog rada je da prikaže današnje stanje u oblasti analize i definisanja korisnikovih potreba i zahteva pri razvoju softvera, oblasti koja zbog svog značaja danas predstavlja posebnu disciplinu u oblasti proizvodnje softvera - requirements engineering ('inženjerstvo korisnikovih zahteva'). Kao rezultat postupka definisanja korisnikovih zahteva dobija se specifikacija zahteva - dokument koji članovima softverskog razvojnog tima služi kao osnova prilikom dizajniranja, implementacije i testiranja sistema. Kroz čitav rad insistira se na tome da proces definisanja zahteva mora da bude okrenut pre svega prema korisnikovim realnim potrebama, jer se softver pravi za njih a ne za inženjere koji razvijaju sistem. Današnja softverska industrija ide za tim da i korisnike i proizvođače softvera stavi u partnerski odnos pri razvoju programa, a ne samo u odnos kupca i prodavca. Rad analizira karakteristike samih zahteva, a takođe i procesa njihovog definisanja, kroz postupke modeliranja radnog procesa korisnika koji program treba da automatizuje ili olakša, kao i kroz prikazivanje najznačajnijih tehnika definisanja zahteva. Takođe je opisano i nekoliko softverskih alata pomoću kojih se proces definisanja zahteva može umnogome olakšati i automatizovati.

The purpose of this paper is to analyze the state of the art in the domain of gathering and specification of user's requirements in software development. The complex of activities in that domain is of primary importance for software industry, and is a discipline in itself, commonly called requirements engineering. As the main result of the process of requirements engineering, formal requirements specification is generated - a document that is used by the members of the software production team as the basis for design, implementation and testing of the product. Throughout the paper, it is stressed that requirements engineering must be user-oriented (user-centered), because it is end-users that will work with the future system, not its developers. It is the ambition of software industry today to create the relation of partnership between the end-users and the developers of software, not only to maintain the customer-vendor relationship. The paper analyzes both the requirements themselves and the process of their specification through modeling of the user's work process that the software product should facilitate or automate, as well as through discussion of most important techniques of requirements specification. Certain software tools that facilitate the process of requirements gathering and specification are also described.