izpis_h1_title_alt

Primerjava agilnih in tradicionalnih metodologij zagotavljanja kakovosti, zanesljivosti in varnosti programske opreme
ID ŠRAMEK, MAXIMILIAN (Avtor), ID Bojkovski, Jovan (Mentor) Več o mentorju... Povezava se odpre v novem oknu

.pdfPDF - Predstavitvena datoteka, prenos (1,05 MB)
MD5: 0475B619727F35F860C64DFBA8930484

Izvleček
Naloga zajema pregled in primerjavo tradicionalnih ter agilnih pristopov zagotavljanja kakovostne in zanesljive programske opreme, ki so se razvijale skozi čas. Na koncu pa je tudi opisana izbira metodologije za namen razvoja varnostno-kritičnih krmilnih sistemov v avtonomnih vozilih po standardu ISO 26262, kar je danes aktualna in zaskrbljujoča tematika. V prvi polovici dela je pregled metod razvoja in preskušanja programske opreme, ki so značilne za metodologiji in se najpogosteje pojavljajo v praksi. Opisani so različni možni življenjski ciklusi razvoja, ker so ti ključnega pomena pri zagotavljanju kakovosti, zanesljivosti in varnosti opreme. Pomembni so tudi načini preskušanja, ki so opisani tako za tradicionalne kot tudi za agilne pristope. Na podlagi opisanih pristopov in njihovih lastnosti je v drugi polovici dela narejena podrobnejša primerjava metodologij. V središču primerjave so razlike v načrtovanju, sodelovanju, komunikaciji in načinih preskušanja programske opreme. Naloga tudi opisuje primernost uporabe metodologij za različne vrste in namene programske opreme, ter pravilno izbiro glede na velikost projekta. Poleg velikosti projekta pa na odločanje vpliva tudi namen uporabe programske opreme v različnih okoljih za različna področja. Ugotovitve naloge so, da so danes zelo razširjene agilne metodologije, kot najprimernejši pristop k razvoju izdelka na hitro spreminjajočem se trgu, katerega zahteve se spreminjajo praktično čez noč. So primernejše za izdelavo manjših projektov, ki imajo omejene časovne okvire in so tudi bolj prilagodljive ob spreminjanju zahtev sredi procesa razvoja. Poleg nižanja stroškov, pa tudi izboljšajo produktivnost ekipe z vključitvijo naročnika v proces razvoja in preskušanja programske opreme. Kljub temu, da današnji čas označujemo za obdobje agilnih metodologij, so tradicionalni pristopi še vedno nepogrešljivi. Za razvoj večjih in daljših projektov, ki zahtevajo povečano mero varnosti in zanesljivosti, agilne metodologije niso primerne, saj takšni projekti zahtevajo podrobno načrtovanje in analizo zahtev naročnika. Najbolj pa so danes v uporabi za razvoj sistemov, ki vsebujejo mnogo varnostno-kritičnih funkcij in bi napačno delovanje lahko pomenilo nastanek kritičnih, ali pa celo katastrofalnih posledic (avtomobilska, vojaška, letalska in vesoljska industrija). V zadnjih poglavjih je študija primera s področja uporabe tradicionalnega pristopa, ki se danes uporablja za razvoj varne programske opreme avtonomnih vozil. Standard ISO 26262 s področja varnosti električnih in elektronskih sistemov v avtomobilski industriji, zahteva uporabo V-modela življenjskega ciklusa pri avtonomnih sistemih, ter uporabo scenarijev pri določenih fazah razvoja. Takšen model je najbolj primeren zaradi izredno podrobnega načrtovanja ter predvidevanja in preprečevanja napak v zgodnjih fazah razvoja ter več stopenjskega preskušanja opreme.

Jezik:Slovenski jezik
Ključne besede:kakovost programske opreme, preskušanje programske opreme, agilne metodologije, tradicionalne metodologije, varnost
Vrsta gradiva:Diplomsko delo/naloga
Organizacija:FE - Fakulteta za elektrotehniko
Leto izida:2019
PID:20.500.12556/RUL-108525 Povezava se odpre v novem oknu
Datum objave v RUL:05.07.2019
Število ogledov:2408
Število prenosov:271
Metapodatki:XML DC-XML DC-RDF
:
Kopiraj citat
Objavi na:Bookmark and Share

Sekundarni jezik

Jezik:Angleški jezik
Naslov:Comparison of Agile and Traditional Methodologies for Quality Assurance, Reliability and Security of Software
Izvleček:
The thesis involves an overview and comparison between agile and traditional methodologies for developing quality and reliable software, which have deloped and evolved through time. At the end, there is also a review of a chosen method for developing safety-critical systems in autonomous vehicles, according to ISO 26262 standard, that is a concerning and modern topic today. In the first part of the thesis, there is an overview of different methods for developing and testing software, which are typical for both methodologies and are most commonly used. There is a description of different possible software development life cycles, because they are of crucial value in providing safe and reliable equipment. Of great importance are also the different approaches in testing, which are described for both traditional and agile methods. Based on the described approaches and their characteristics, the second part includes a detailed comparison of both methodologies. In the focus of the comparison are the differences in planning, cooperating, communicating and types of software testing. Thesis also describes suitability of both methodologies in different types and purposes of software, and the most suitable one according to the size of the project. Conclusion of the thesis are, that agile methodologies are most widespread today, as they represent the most approprite approach to development of a product on the fast transforming and developing market. They are most suitable for developing small and time limited projects, as they are more flexible to changes in the requirements and needs of the customer, even in the late stages of development. Besides the lower cost of the projects, they make a big improvement on the productivity with integrating the customer in the process of development and testing of the software. Even though we commonly state, that we are currently in a time period of agile methodologies, the traditional ones are still irreplaceable. For development of longer and bigger projects, agile methodologies are just not suitable enough, because these types of projects demand detailed planning and analysis of customers requirements. The most important use of traditional methods is for developing the systems, that have a lot of safety-critical functions and would cause critical, or even catastrophic consequences in the case of failure (automotive, military, aeronautic and aerospace industry). As a part of the last chapters there is a case study of traditional methods, commonly used today for development of safe software in the autonomous vehicles. The ISO 26262 standard, about the safety of electrical and electronic systems in automotive industry, demands the use of a V-model life cycle for the delepoment of such systems and the use of scenarious at various stages of the development. The model is most suitable for its detailed planning as well as good error predicting and preventing measures in the early stages of the development and various phases of software testing.

Ključne besede:software quality, software testing, agile methodologies, traditional methodologies, safety

Podobna dela

Podobna dela v RUL:
Podobna dela v drugih slovenskih zbirkah:

Nazaj