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 labor 4.
Software Laboratory 4.
|
||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Subject code | BMEVIIIA220 | ||||||||||||
| Subject type | — | ||||||||||||
| Training Level | — | ||||||||||||
| Course types and hours (weekly/semester) |
|
||||||||||||
| Assessment type | félévközi érdemjegy | ||||||||||||
| Credits | 2 | ||||||||||||
| 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 | — | ||||||||||||
| 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
This laboratory is the organic continuation of the course „Software technology”. The goal is creating an object oriented application with UML (Unified Modeling Language) description, Java implementation, due to RUP (Rational Unified Process) concepts. Students are working on the project in groups of 3 or 4. Groups formed by the consulent. Students are preparing the documentations due to the schedule given. Documentations must be handed in in pre-definite format. The project is to be realized in three steps: Skeleton, Prototype, Complete The goal of the Skeleton version is to verify that object and dynamic models are making up the model of the task. The Skeleton is a program containing all the business objects that are going to take part in the final system. The interfaces of objects are defined only. At the beginning every method writes its name on the screen and calls the methods he needs to fulfill his service. In case calling of methods depend on condition, a question referring to the condition ought to be asked on the screen interactively so the program goes on the way the answer defines. Skeleton must also be able to help checking different scenarios and sequence diagrams. The goal of the Prototype program is to demonstrate that the program is ready, works correctly, fulfils all tasks. Prototype version is a whole program except of the detailed interface. Prototype is well planned, timing and handling of active objects is completed. All methods of the business objects contain the final algorithms - except of those concerned with appearance. Paying attention to the logic and structure of interface, to the fact how much it reflects and makes visible the functioning of the program is very important. Complete version of program may differ from prototype only because of the quality of user interface. At evaluation, the internal structure of realization is more stressed than the exteriors.
The objective of this course is to give to the students a solid practical background of the methods presented during lectures and classroom practices of the Software Technology course.
Obtained skills and expertise:
Application of methods presented during lectures and classroom practices.
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
Not provided.
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.
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)
nincs
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)
nincs
General rules
Követelmények:
a. A szorgalmi idõszakban:
A célkitűzésben és a részletes tematika leírásában szereplõ dokumentációkat a tárgy projektdefiníciójában (letölthető a tárgy web-oldaláról) meghatározott határidõkre, általában hetente kell elkészíteni és beadni. A tárgy a féléves folyamatos munkára épül és hasonlóképp folyamatos a számonkérés és értékelés is.
b. A vizsgaidõszakban:
A követelmények vizsgaidõszakban nem teljesíthetõk.
Pótlási lehetőségek:
Minden nap késedelem az adott dokumentációért kapható maximális pontszámot 10 %-kal csökkenti. A napforduló 15:00-kor van, a szombat és a vasárnap együttesen egy napnak számít. Tekintettel a féléves folyamatos munkára, egyéb pótlási lehetőség nincs.
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
Not provided.
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.