Subject » BMEVIIIAB11
Software Project Laboratory
Szoftver projekt laboratórium
A tantárgyleírás hatályossága
Hatályosság kezdete:
2026. March 21.
Hatályosság vége:
—
| Subject name (Hungarian, English) |
Szoftver projekt laboratórium
Software Project Laboratory
|
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Subject code | BMEVIIIAB11 | ||||||||||||
| Subject type | — | ||||||||||||
| Training Level | — | ||||||||||||
| Course types and hours (weekly/semester) |
|
||||||||||||
| Assessment type | félévközi érdemjegy | ||||||||||||
| Credits | 4 | ||||||||||||
| Subject coordinator |
DR. Goldschmidt Balázs
position: egyetemi docens
contact:
goldschmidt.balazs@vik.bme.hu
|
||||||||||||
| Responsible department |
Irányítástechnika és Informatika Tanszék
|
||||||||||||
| Faculty | Villamosmérnöki és Informatikai Kar | ||||||||||||
| Subject website | https://www.iit.bme.hu/targyak/BMEVIIIAB02?language=en | ||||||||||||
| 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
The task is to solve the problem in 3 major phases.
- The goal of the skeleton is to show the soundness of the analysis model.
- The goal of the prototype is to create the final product without the GUI. It fulfills all requirements except the graphical representation.
- The graphical version adds the graphical user interface to the prototype.
The schedule of the project is as follows:
1. Teams set up, original problem announced.
Skeleton phase
2. Requirements, project, functionality
3. Analysis model, version 1, based on Object oriented principles and using UML.
4. Analysis model, version 2, correcting the errors and other problems of the previous version.
5. Design of the skeleton. The analysis model is transformed into a full design of the skeleton: all business classes with all publicc method but no business logic. Business logic decesions are asked of the user. The method calls are printed to the screen.
6. Implementing the skeleton. Software source code is to be submitted. At laboratory testing is conducted.
7. Spring break
Prototype phase.
8. Concept of the prototype. Real use-cases, input-output interface design, test cases defined.
9-10. Detailed design. All classes are designed fully, except the graphical interface. Tests are designed and described in the language specified in the previous task.
11. Implementing the prototype. Based on the detailed design. Also, tests are conducted and the protocols are to be submitted.
Graphical phase.
12 Specifying the GUI, using UML, based on MVC. Detailed as far, as the connection to earlier classes are specified.
13-14 Implementing the graphical version.
The aim of the subject is to provide on hand experience in developing a complex software from requirements to final tested product applying an incremental, iterative approach in teams of 5, using UML, C++ or Java. Each week the incremental results are documented, the documentation is submitted and corrected. At some points also runnable software is created.
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
During the semester the teams prepare the documentation and software at home. At the laboratory the corrections are presented and consultation is given.
Tanulástámogató anyagok
Online források
Sommerville, I. - Software Engineering, 6th ed. Addison-Wesley PC. Reading Massachusettes, 2001.; Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide, Addison-Wesley, 1999.; Larman C. : Applying UML and Patterns, Prentice-Hall, 1998.; Material accessible from the department’s.
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)
Programming 2
Software engineering
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)
Programming 2
Software engineering
General rules
Requirements:
During midterm:
All documentation and software is to be handed in on time.
The teams gain points for each task. The final points of each team is calculated from a weighted average. Points are calculated by considering the timeliness, the soundness, etc.
Team members’ efforts are assessed by their peers, which is supervised by the teacher.
The final mark is calculated from the team-points and the individual effort.
During exam period: None.
Additional possibilities:
All documentation can be submitted by no later than 14.00 of last day of the last (14th) week
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
IMSc program:
None
IMSc points:
None
Recommended courses
Programming 3
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.