9 th Workshop Software Engineering Education and Reverse

9 th Workshop "Software Engineering Education and Reverse Engineering" Neum, Bosnia and Herzegovina DEVELOPMENT OF SOFTWARE FOR SUPPORTING THE LEARNING PROCESS ACCORDING TO BOLOGNA AGREEMENTS LESSONS LEARNED Vedran Ljubović Faculty of Electrical Engineering Sarajevo vljubovic@etf. unsa. ba Neum, 31. 08. 2009

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Introduction – Highlights of project "Zamger": Started out as an application for personal use in teaching Becomes interesting to other colleagues Used in implementation of institutional QA policies Iterative and incremental approach used during development

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Overview of methods and techniques for software development Iterative and incremental development (IID)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Iterative and incremental approach Iteration – development in steps, gradual product improvement Increment – independent part of product that is developed separately (e. g. by a team)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Iterative and incremental approach Frequent confusion between terms "iterative" and "incremental" For successfull software development both are needed! (Cockburn, 2008; Patton, 2007)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned IID vs. Waterfall "The attraction of [waterfall] is its simplicity" (Cauwenberghe, 2002) Waterfall makes it hard to make mistakes; IID requires training, both of managers and programmers (Larman, Basili, 2003)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Feature Driven Development (FDD) Project is divided in parts (classes) by user functionalities, or features Each class has an owner (Coad et al. , 1999 *)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Open Source Software Development (OSSD) Release early. Release often. User is involved in development process Developers are involved in all aspects of the project First iteration in a project is the most important one (Raymond, 2002)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Overview of Zamger architecture Zamger modular architecture

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Overview of Zamger architecture Each module is a rounded whole Registry. php – list of modules with access rights Framework deals with security, among else Library modules – offer features for other modules Core database structure is common, individual modules may have own tables (which simply remain empty if module isn't used)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Overview of Zamger architecture Core database structure (excerpt)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Zamger development specificities Relatively low urgency In-house development Some modules are mid-term / graduate student papers Web application

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Zamger development specificities Web app advantages: Deployment is practically free Bugs fixed "on the fly" Centralized data (backup!)

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Zamger development lifecycle 1. User requirements gathering 2. Requirements analysis and planning 3. Module development 4. "Live" system installation and incremental improvements

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Zamger development lifecycle 3. Module development (e. g. by a student) a. detailed user requirements b. interface and interaction design c. functional prototype d. module development (coding) e. testing f. detailed documentation g. fixes and suggestions from project leader

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Zamger development lifecycle Average iteration lenght: 6 months Relatively long, but there are good reasons (and it wasn't a problem) De-facto ownership of modules, but developers fix bugs everywhere

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Analysis of IID approach in Zamger development Each iteration is "final" release Bugs and features arise from usage ("instability" is an aftermath) Module = feature, completed within one iteration Core features in early iterations Unexpected changes and new features happen all the time – schedule extra time!

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Analysis of IID approach in Zamger development Incremental approach Iterations within an increment Project level iterations

Vedran Ljubović, Development of Software for Supporting the Learning Process According to Bologna Agreements - Lessons Learned Conclusions and future work A new reading of literature is offered Zamger project continues. . . Iteration planning process needs to be elaborated, with emphasis on the first iteration and its importance