Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 1 Software Tag: Empirical Software Engineering Data for Traceability and Transparency of Software Project Katsuro Inoue Osaka University

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 2 Background Empirical Software Engineering (ESE) –Emerging topics in Software Engineering –It is very important resource for the accountability and traceability in global software engineering Data Collection Data Analysis Feedback

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 3 Who gets benefit from ESE? Product data archive (CVS format) Process data archive (XML format) Code clone detection Code clone detection Component search (SPARS) Component search (SPARS) Metrics measurement Metrics measurement Project z Project y Project x Versioning (CVS) Mailing (Mailman) Format Translator Logical Coupling Collaborative filtering Collaborative filtering Interface GUI Managers Developers... Issue tracking (GNATS) Format Translator Format Translator Format Translator Other tool data Current ESE mostly focus on the benefit of software developers

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 4 Extend the Benefit Extend the benefit of ESE to software purchasers (orderers, customers, users) Purchasers get the empirical data They can analyze and evaluate the empirical data They can understand that software development was performed under proper activities and quality of the resulting products is high

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 5 Software Tag Empirical data for software purchasers Delivered associated with software products Not raw or full empirical data  –Processed and selected data Ease to understand and evaluate –Development process –Product quality

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 6 Empirical SE Model Software purchaser Development data record Purchase order Delivery Software developer Software products Empirical data Data collection Feedback

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 7 Software Tag Model Software purchaser Development data record Purchase order Delivery Software developer Software Products Empirical data Attach Data collection Extract Tag Software Tag Feedback

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 8 Example Structure of Software Tag Development process –Requirement progress and changes –Design progress and review history –Code progress and changes –Performed test cases – … Product quality –Detected faults and their history –Results of static code analysis –Code clone distribution – …

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 9 Supporting Empirical Data Validity and interpretation of the software tag will be argued Tag data need to be endorsed by the collected raw empirical data (source code repositories, review reports, …) The raw empirical data contains a lot of development know-how and proprietary information for the developer –It cannot be delivered to the purchaser directly Neutral mediator (Software Liability Mediator) is needed. The mediator investigates both the tag and raw empirical data, and resolves liability issues In the case of controversy between purchaser and developer:

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 10 Software Liability Mediator Software purchaser Development data record Purchase order Delivery Software developer Software Products Empirical data Attach Data collection Extract Tag Software Tag Software liability mediator Investigation Feedback

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 11 Merits of Software Tag Even for Developers Provide evidence for proper development activities and quality Software developers are generally purchasers of software 発注者 元請会社 一次請け 二次請け （海外） 二次請け （海外） 発注 Product & Tag ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品 オープンタグ 可視化された エンピリカルデータ 発注者 Developer 元請会社 Principal contractor 一次請け Sub contractor 一次請け 二次請け Sub-sub contractor 二次請け （海外） ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品オープンタグ 可視化された エンピリカルデータ ソフトウェア 製品 オープンタグ 可視化された エンピリカルデータ Order Sub-sub contractor Order Sub contractor Product & Tag

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 12 Stage Project Goal Standardize software tag Disseminate the idea and the standard of software tag Develop various support tool for creating and validating tags Open Software traceability center: –Keep raw empirical data –Evaluate tag and empirical data Establish Asia-Australia research initiative which promote the idea of software tag Raise advanced software engineers and software liability mediators

Software Engineering Laboratory, Department of Computer Science, Graduate School of Information Science and Technology, Osaka University 13 Thanks for your comments!