How and how not to develop software

Gorza Barna Zoltán (2023) How and how not to develop software. Gazdálkodási Kar Zalaegerszeg.

[thumbnail of gorza_barna_zoltán_2023máj.pdf] PDF
gorza_barna_zoltán_2023máj.pdf
Hozzáférés joga: Csak nyilvántartásba vett egyetemi IP címekről nyitható meg

Download (567kB)

Absztrakt (kivonat)

Information Technology (IT) is a vast field with myriads of specializations that all share one commonality: they are all require software. Regardless whether they are called applications, programs or simply logic, nowadays they are all interacting with code that someone had to have designed, developed and deployed. This ‘someone’ may be multiple persons, each having a specific role during the development process. In this thesis, different aspects of software development will be discussed, focusing on the challenges that IT students and recent graduates may encounter, topics that are outside of the scope of university education, as well as giving context to how and why certain practices arose over time. Software development is rarely an individual effort. Every developer relies on existing code; compilers and interpreters are needed to run the code, and libraries provide utilities and functions that are not only “ready to go”, but most likely are better optimized than what we could create. The very existence of already existing code that developers can integrate into their own projects offer invaluable help and saves significant amounts of resources. However, having access to thousands of libraries, many of which are serving the same purpose can be overwhelming. The choice of the right alternative depends on multiple factors and should be done so that we can minimize costs, both financial and time. While writing documentation seldom feels productive, hardly any work can be done without them. Without them, upgrading and expanding old software would be almost impossible, as the lack of a quick reference either inside or outside the code leads to the necessity to study the code in detail, wasting precious time that could have been spent on actual work. This is usually not an issue for short (less than 100 lines) scripts and code that is using reasonable naming and formatting, but spending five minutes to prevent 15 minutes of headache every time it needs to be revisited is worth the trouble. Good practices and patterns arise from years of experience of many developers. They reduce time, enable greater readability and provide the foundation that we can build upon. Teaching these in a formal settings is, although not impossible, impractical to include; without basic understanding of programming and some experience, they oft appear meaningless or outright confusing. With this thesis, I aim to outline a path of how to approach software development as a whole, and to offer an alternate perspective about the art of programming.

Intézmény

Pannon Egyetem

Kar

Gazdálkodási Kar Zalaegerszeg

Tanszék

Informatikai Rendszerek és Alkalmazásai Tanszék

Szak

gazdaságinformatikus

A képzés szintje

alapképzés

Konzulens(ek)

Konzulens neve
Konzulens típusa
Beosztás, tudományos fokozat, intézmény
Email
Guzsvinecz Tibor, Dr.
Belső
adjunktus; Informatikai Rendszerek és Alkalmazásai Tanszék; GKZ
Szűcs Judit
Külső
NEM RÉSZLETEZETT
NEM RÉSZLETEZETT

Mű típusa: diplomadolgozat
Kulcsszavak: advanced techniques, comments, documentation, naming conventions, software development
SWORD Depositor: SWORD
Felhasználói azonosító szám (ID): SWORD
Dátum: 17 Jún 2023 13:16
Utolsó módosítás: 17 Jún 2023 13:16

Actions (login required)

Tétel nézet Tétel nézet