Budapest University of Technology and Economics, Faculty of Electrical Engineering and Informatics

    Belépés
    címtáras azonosítással
    vissza a tantárgylistához   nyomtatható verzió    

    Software Project Laboratory

    A tantárgy neve magyarul / Name of the subject in Hungarian: Szoftver projekt laboratórium

    Last updated: 2024. január 24.

    Budapest University of Technology and Economics
    Faculty of Electrical Engineering and Informatics     		BSc Software engineering
    Course ID Semester Assessment Credit Tantárgyfélév
    VIIIAB11 4 0/0/2/f 4  
    3. Course coordinator and department Dr. Goldschmidt Balázs,
    Web page of the course https://www.iit.bme.hu/targyak/BMEVIIIAB02?language=en
    4. Instructors


    Dr. Katalin Balla 

    Dr. Goldschmidt Balázs

     

    5. Required knowledge

    Programming 2

    Software engineering 

    6. Pre-requisites
    Kötelező:
    (NEM TárgyTeljesítve_Képzésen("BMEVIIIAB06") )

    ÉS

    ((EgyenCsoportTagja("INFO - 2022 - MINTATANTERV HALLGATÓI") ÉS
    TárgyEredmény( "BMEVIMIAB04" , "aláírás" , _ ) = -1 )

    VAGY

    ((EgyenCsoportTagja("2014_tanterv_hallgatoi_info") VAGY
    EgyenCsoportTagja("5NAA8_2022 előtti tanterv")) ÉS


    TárgyTeljesítve("BMEVIIIAB00") ÉS
    (TárgyEredmény( "BMEVIIIAB01" , "aláírás" , _ ) = -1 ) VAGY
    TárgyEredmény( "BMEVIMIAB04" , "aláírás" , _ ) = -1 ))

    A fenti forma a Neptun sajátja, ezen technikai okokból nem változtattunk.

    A kötelező előtanulmányi rend az adott szak honlapján és képzési programjában található.

    Ajánlott:
    Programming 3
    7. Objectives, learning outcomes and obtained knowledge 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.
    8. Synopsis

    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.


    9. Method of instruction During the semester the teams prepare the documentation and software at home. At the laboratory the corrections are presented and consultation is given.
    10. Assessment
    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. 
    11. Recaps

      All documentation can be submitted by no later than 14.00 of last day of the last (14th) week
    12. Consultations During laboratory
    13. References, textbooks and resources
    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.

    14. Required learning hours and assignment
    Kontakt óra28
    Félévközi készülés órákra12
    Felkészülés zárthelyire
    Házi feladat elkészítése80
    Kijelölt írásos tananyag elsajátítása
    Vizsgafelkészülés
    Összesen120
    15. Syllabus prepared by Dr. Balazs Goldschmidt, Dr Balazs Simon
    IMSc program None
    IMSc score None