Subject » BMEVIAUMB10
Software Development in Industry
Szoftverfejlesztés az iparban
A tantárgyleírás hatályossága
Hatályosság kezdete:
2026. March 21.
Hatályosság vége:
—
| Subject name (Hungarian, English) |
Szoftverfejlesztés az iparban
Software Development in Industry
|
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Subject code | BMEVIAUMB10 | ||||||||||||
| Subject type | — | ||||||||||||
| Training Level | — | ||||||||||||
| Course types and hours (weekly/semester) |
|
||||||||||||
| Assessment type | vizsga | ||||||||||||
| Credits | 5 | ||||||||||||
| Subject coordinator |
Dr. Lengyel László
position: egyetemi tanár
contact:
lengyel.laszlo@vik.bme.hu
|
||||||||||||
| Responsible department |
Automatizálási és Alkalmazott Informatikai Tanszék
|
||||||||||||
| Faculty | Villamosmérnöki és Informatikai Kar | ||||||||||||
| Subject website | www.aut.bme.hu | ||||||||||||
| Primary curriculum type | — | ||||||||||||
| Direct prerequisites – Strong prerequisite | none | ||||||||||||
| Direct prerequisites – Weak prerequisite | none | ||||||||||||
| Direct prerequisites – Parallel prerequisite | none | ||||||||||||
| Direct prerequisites – Milestone prerequisite | none | ||||||||||||
| Direct prerequisites – Exclusion | none |
Objectives
Programme
Lectures:
1. Repetition and summary
Software development methodologies
Agile development methods
2-3-4. Software project management
Business processes, business modeling, business estimation
Software project management methods and tools, project life cycle, processes, time frames, resources, strategy and organizational forms
Aspects and methods of developing and introducing services and applications: how to build a product/service, how to bring it to market, the role of an innovation manager as a product manager, knowledge-skills-attitude matrix
5-6-7-8. Software development and IT operation, cooperation between development and IT teams
Version management, Continuous Integration/Deployment/Monitoring/Testing/Delivery/Business Planning
How to monitor software progress
Roles and tasks: product owner, process manager, process stakeholder, IT security professional, project manager, software engineer, IT engineer, release manager, software tester
Software engineer (software architect)
What does a software architect know, how does someone become an architect, what are their tasks, knowledge-skills-attitude matrix
How to estimate a software system
Clean Code
9-10. Software companies
What does a software company do: consult, design, develop, operate, optimize
How we negotiate with the customer, how we negotiate the price
Contract conclusion
Management methods of software companies, construction and organization of software companies, everyday life of software companies, exit questions
11. NoSQL databases, architectures of data-driven applications
12-13. Client-side techniques and solutions
Exercises/labs:
1. Software project management
2. Software development and IT operation
3. Software architect, estimate
4. Management of software companies 1
5. Management of software companies 2
6. (Midterm test)
7. Software and copyright, intellectual property
The subject summarizes the software development methodologies, their application possibilities and conditions, the practices and tools required and preferred by the design and development methods. Building on the competencies learned in the bachelor's degree, the subject integrates technical aspects with business approaches. It presents the management methods and tools and business processes related to software projects. Discusses the steps involved in developing software-based services and products, and the role of the product and service manager. Software development and IT operation activities, roles and tasks are presented. The subject describes what a software architect can do, how someone becomes an architect, and what their responsibilities are.
The specifics, development and operation of software companies, the organizational structure of software companies, negotiation with the customer, pricing methods, contract signing issues for software projects, and exit issues of software companies are explained.
The goal is for students to have a comprehensive insight into the operation of the software industry, the organization and management of software projects, the operation of software companies, and the details of several prominent software roles, such as the software architect and the product manager.
Learning outcomes
Ez a tantárgy a KKK rendeletben meghatározott, következő kompetenciák fejlesztését szolgálja:
Knowledge
No learning outcomes recorded.
Skills
No learning outcomes recorded.
Attitudes
No learning outcomes recorded.
Autonomy and responsibility
No learning outcomes recorded.
Oktatási módszertan
Lecture and seminar
Homework
Processing selected written material
Tanulástámogató anyagok
Online források
Written materials posted on the website of the subject.
Recommended preliminary knowledge for completing the subject
Knowledge type competencies
(azon előzetes ismeretek összessége, amelyek megléte nem kötelező, de a tantárgy eredményes teljesítését nagyban elősegíti)
Basics of Programming 1-3, Software Techniques
Skill type competencies
(azon előzetes képességek és készségek összessége, amelyek megléte nem kötelező, de a tantárgy eredményes teljesítését nagyban elősegíti)
nincs
Recommended (non-compulsory) preliminary competencies
(azon ajánlott (nem kötelező) előzetesen megszerzendő kompetenciák összessége, amelyek jelentősen hozzájárulnak a tantárgy eredményes teljesítéséhez)
Basics of Programming 1-3, Software Techniques
General rules
Requirements:
During the semester
1 midterm exam
1 homework
The condition for obtaining the signature is the successful completion of the midterm exam and the homework separately. In the case of both the midterm exam and the homework, a minimum of 40% of the maximum possible score must be achieved for successful completion.
A maximum of 25 points can be obtained with midterm exam. A maximum of 25 points can be obtained from the homework. In order to complete them, it is therefore necessary to obtain a minimum of 10-10 points. The points earned count towards the end-of-semester grade.
During exam period
Written exam
To pass the exam, a minimum of 40% of the maximum possible score must be achieved. A maximum of 50 points can be obtained on the exam, so a minimum of 20 points is required to pass the exam.
The score obtained in the subject: P = V + Z + HF, where V is the score obtained in the exam, Z is the score obtained in midterm exam, and HF is the score obtained in the homework.
Calculation of the end-of-semester ticket:
excellent (5) – if P >= 85 points
good (4) – if P >= 70 points
medium (3) – if P >= 55 points
sufficient (2) – if P >= 40 points
insufficient (1) – if P < 40 points
Additional possibilities:
The midterm exam can be repeated during the repeat period in accordance with the Code of Studies and Exams.
Assessment methods
In-term assessments
No detailed assessments provided.
Weight of in-term assessments
No weights provided.
Exam-period assessments
No detailed assessments provided.
Weight of exam elements
No weights provided.
Grade calculation
No grade thresholds provided.
Attendance requirements
No attendance requirements provided.
Rules for retake and resubmission
Not provided.
Short description
Not provided.
Detailed description
Not provided.
Recommended courses
Basics of Programming 1-3, Software Techniques
Workload to complete the subject
No workload breakdown provided.
Validity of subject requirements
Requirements valid from:
—
Requirements valid until:
—
Curriculum placement
No curriculum placements recorded for this subject version.