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

Detailed topic of the subject

·        

·         Introduction, agile methodology, extreme programming, agile methods (Scrum, Kanban), roles, principles, sprint

·         Requirements analysis, user stories, backlog, estimation techniques, prioritization, standards

Role of domain expert in interpretation of requirements, planning of user interaction

·         Design

Architecture and interior interaction design

Related roles: architect, designer

Model making, modeling techniques. What makes a good model?

·         Control flow, control flow description methods

Telecommunications-specific requirements (flow ctrl, error handling, etc.)

·         Data modeling, message format design

Data flow, data structures, data serialization

·         Data specification and data serialization languages (XSD, ASN.1, XML)

·         Creating an agile development environment

·         Continuous Integration

CI frameworks, continuous build

Code integrity check

Release, iteration, design

·         Implementation, installation

Version management, version management software

Configuration management, tools

·         Refactoring, when refactoring is needed, refactoring techniques

·         Testing principles, basic concepts:

Test types, levels (conformance testing, functional and unit tests, regression tests, performance tests

Test environment

Test standards, test documentation

·         Black box testing

·         Test languages (TDL, TTCN-3)

·         Test automation

Scripts

Data Driven Testing

Test execution systems (JCAT, Titan)

Model Based Testing

Test generation goals, methods, test coverage, metrics

Design for testability

·         Test-driven development

Parallel development of test and program code, establishment of acceptance criteria

Acceptance test, behavior-driven development

Test maintenance

·         Documentation

Logging, reporting,

Metrics

Automatic documentation creation systems

2 hours of classroom lectures per week and 2 hours of practice every second weeks. Based on the knowledge presented at the lectures, the students solve a development task (homework) in the framework of agile teamwork during the exercises.

a) During the teaching period: the conditions for obtaining the signature and being admitted to the exam are: writing at least a sufficient level (2) of the mid-semester test and at least a sufficient level (2) of participation in the agile team work. An offered mark can be obtained (50% of the test mark + 50% of the team-work).

b) During the exam period: written exam (50% of the exam test mark + 50% of the team-work)

c) Pre-exam: none

The mid-semester test can be repeated once, either during the teaching period or during the repeated test week.

Participation in agile teamwork (homework) cannot be repeated.

As needed.

James Shore and Shane Warden: “The Art of Agile Development”, O’Reilly, ISBN-10: 0-596-52767-5 2008

Mike Cohn: “Succeeding with Agile – Software development with Scrum”, Addison-Wesley, ISBN-10: 0-321-57936-4 2010