K-INFO
HU
EN
Login
Subject » BMEVIIIAB06
Older versions Download TAD (PDF)

Software Project Lab

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 Lab
Subject code BMEVIIIAB06
Subject type —
Training Level —
Course types and hours (weekly/semester)
Course type lecture tutorial laboratory
hours (weekly) 0 0 2
type (linked/independent) — — autonomous course
Assessment type félévközi érdemjegy
Credits 3
Subject coordinator
DR. Goldschmidt Balázs
position: egyetemi docens
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

The assigned project is completed in three phases:

– Skeleton phase

Its purpose is to demonstrate that the object and dynamic models correctly represent the given task. The skeleton is a program that already contains all business objects that will appear in the final system.

– Prototype phase

The goal is to create a functioning version of the software that fulfills all required tasks. This version is complete except for its graphical interface. Architecturally it is finished: scheduling and handling of active objects are implemented. All business‑object methods contain the final algorithms except for presentation‑related parts. Behavior can be observed through a text‑based interface or via log files, allowing the system to be tested.

– Graphical phase

This step develops the graphical user interface. The final GUI version differs from the prototype only in the interface quality. Evaluation focuses more on internal design than on external appearance.

Project schedule

1. Forming teams, distributing the assignment.

Skeleton phase

2. Requirements, project plan, functionality; specifying requirements, project plan, use cases, use‑case diagrams, glossary.
3. Analysis model (version 1) according to RUP using UML.
4. Improved analysis model (version 2) according to RUP using UML.
5. Designing the skeleton: specifying the skeleton application verifying model correctness.
6. Implementing and presenting the skeleton; testing another group’s application and documenting it.

Prototype phase

6. Concept of prototype: specifying real use cases of the non‑GUI version, defining input/output interface, listing test cases broadly.
7. Detailed designs: class specifications of prototype, detailed test descriptions based on the previously defined I/O specification.
8. Implementing, testing, presenting the prototype; testing another group’s version and documenting it.

Graphical phase

9. Specifying the GUI; defining necessary changes in UML; detailing new or modified classes.
10. Implementing, testing, presenting the GUI; testing another group’s implementation and documenting it.

The aim is to make students familiar with teamwork and with applying RUP and UML in a realistic software‑development context. The main task is to produce an object‑oriented software system using UML descriptions, implemented in Java, following the phases of the RUP process. Students work in groups of four or five, producing software accompanied by documentation chapters and electronic attachments.

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

Consultation and laboratory work.

Tanulástámogató anyagok

Online források
Sommerville:; Software Engineering (Hungarian edition), Panem, 2002; Software Engineering, 6th ed., Addison‑Wesley, 2001; Kondorosi,; Szirmay‑Kalos: Object‑Oriented Software Development, 1997; Booch,; Rumbaugh, Jacobson: The UML User Guide, 1999; Larman:; Applying UML and Patterns, 1998; Additional; materials downloadable from the department webpage.

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)
Java programming UML and RUP methodologies
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)
Java programming UML and RUP methodologies
General rules
Requirements: a. During the semester Students produce unified documentation and corresponding electronic attachments. Competence elements related to knowledge and ability are assessed through continuous partial evaluations based on the project work, guided by instructor supervision. Each chapter and attachment has a maximum point value. Competence elements concerning attitude, independence, and responsibility are also checked through continuous assessment based on participation and activity in group work. Each documentation item has a scheduled submission deadline. Submissions may deviate from the schedule, but each day late reduces the attainable points of that item by 10%. Day changes occur at 15:00; Saturday and Sunday count as one combined day. Acceptance of any item requires all preceding items to have been accepted. Groups indicate the contribution of each member; the coordinator may adjust based on the logbook. Evaluation results are assigned to the group. To pass each of the Skeleton, Prototype, and Graphical phases, at least 40% of the possible points of the respective closing sections and attachments must be achieved. Additionally, in each phase, at least 40% of all achievable points must be obtained. If all conditions are met, individual grades are based on the group’s total points and individual contribution ratios. If any condition fails, no member passes the course. b. During exam period The requirements cannot be completed during the exam period. Additional possibilities: Chapters and attachments may be submitted no later than 14:00 on the last working day of the final week of the semester. Already submitted materials cannot be replaced.
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: Students in the IMSc program receive additional recommended literature and may request extra consultations outside class. IMSc points: If a chapter or attachment earns more than 80% of available points, the group receives 1.5 IMSc points. Maximum total per semester: 15 IMSc points. Students earning an excellent grade receive the group’s accumulated IMSc points.
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.