1. http://www.sigl.epita.net BEWITCHED 15/06/2006Soutenance GLAO #2 slide 1 GLAO Presentation #2 CASE Architecture Bewitched Team 15 Juin 2006

2. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 2 Outline IntroductionIntroduction CASE OverviewCASE Overview –Strategy –CASE working –Special tools CASE architectureCASE architecture –Overview –Integration (Gateways) CASE development planCASE development plan –Gateways to develop –Sequencing ConclusionConclusion

3. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 3 Introduction

4. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 4 Context and Objectives ContextContext –GLAO project for CASE integration ObjectivesObjectives –Demonstrate our CASE architecture The quality of the proposed technical and methodological integrationThe quality of the proposed technical and methodological integration Answering the specification needsAnswering the specification needs Its added valuesIts added values –Suggest a development plan for the CASE and Sygime

5. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 5 CASE Overview

6. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 6 CASE Overview Strategy BDE (Bewitched Development Environment) based on the Eclipse IDE (Integrated Development Environment)BDE (Bewitched Development Environment) based on the Eclipse IDE (Integrated Development Environment) Production of Java Web application for J2EE (JSP; Servlets)Production of Java Web application for J2EE (JSP; Servlets) A 3 axe strategy :A 3 axe strategy : –Test translations from the functional specifications –Code generation and modification –Test executions Used with the XP (eXtrem Programming) Method (spiral development cycle)Used with the XP (eXtrem Programming) Method (spiral development cycle) The source code will be generatedThe source code will be generated The tests will be generated (for the majority)The tests will be generated (for the majority)

7. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 7 CASE Overview Case Working (1/3)

8. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 8 CASE Overview Case Working (2/3) The CASE works in 11 steps:The CASE works in 11 steps: 1.Project initialization, repository creation… 2.The customer provides the functional specifications 3.Functional specifications are translated in large view tests (functional tests) 4.From those tests, functional unit tests are extracted 5.Those tests are used in order to define modules 6.The dev. team defines the classes of the project and makes the first version of the Web application 7.Tests are added (partially automated) 8.Results of tests are available into BWI 9.The developers checkout the project and correct the detected bugs 10.The Web application is generated 11.A loop goes to the statement 7 until all the tests are not passed or the project is not finished

9. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 9 CASE Overview Case Working (3/3) Key features for the use of CASE are:Key features for the use of CASE are: 1.BDE Tools –CASE Tools selected as part of the CASE –Eclipse, EclipseUML and the tests tools 2.BWI – Bewitched Web Interface –A home developed-tool providing additional features, managing the tests and the test executions 3.BBC – Bewitched Batch Control –A batch allowing to run the scripts for the gateways between the tools

10. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 10 CASE Overview Special Tools (1/3) - BWI BWI – Bewitched Web InterfaceBWI – Bewitched Web Interface –Connected with several tools through many gateways –Considered as a hub BWI has 8 major functions:BWI has 8 major functions: –Secure login to the interface –Synchronisation of the tests with the SVN repository –Adding or modifying JUnit tests –Adding or modifying JUnitScenario tests –Viewing results of JUnit tests –Viewing results of JUnitScenario tests –Modifying of the testGen4J data.xml file –Manage repository

11. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 11 CASE Overview Special Tools (2/3) - BWI

12. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 12 CASE Overview Special Tools (3/3) - BBC BBC – Bewitched Batch ControlBBC – Bewitched Batch Control Born from the idea that control of all gateways must be in only one placeBorn from the idea that control of all gateways must be in only one place BBC is a “super” batch that allows launching all scripts and batches that compose the gateways of the CASEBBC is a “super” batch that allows launching all scripts and batches that compose the gateways of the CASE BBC will be automated on the server (CRON) and may be used from BWI manuallyBBC will be automated on the server (CRON) and may be used from BWI manually And… it makes call to other scripts with good parametersAnd… it makes call to other scripts with good parameters

13. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 13 CASE Architecture

14. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 14 CASE Architecture OverviewOverview –Tool List –User Interfaces –Physical Architecture –Allocation in the physical architecture

15. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 15 Overview (1/2) User Interfaces BDE is constructed around the IDE Eclipse and the test toolsBDE is constructed around the IDE Eclipse and the test tools Run in a Java environmentRun in a Java environment Users will only use two tools (interfaces)Users will only use two tools (interfaces) –Eclipse IDE with its plug-in (EclipseUML, Subclipse, Solex) –BWI which will provide the test inputs and outputs, access to BBC

16. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 16 Overview (2/2) Physical Architecture and Allocation A distributed architecture imposed by the development with a team (XP)A distributed architecture imposed by the development with a team (XP) Repository with the sources of the projects and the tests are on a serverRepository with the sources of the projects and the tests are on a server A web server hosting the BWI toolA web server hosting the BWI tool The BDE application on the workstations of the team membersThe BDE application on the workstations of the team members

17. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 17 CASE Architecture IntegrationIntegration –Flows diagram –Identified gateways –Costs of the gateways –Examples of gateways

18. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 18 Integration (1/4) Flows Diagram

19. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 19 Integration (2/4) Identified Gateways 17 gateways have been identified17 gateways have been identified CodeType Unidir ection al Bidirec tional JUnit-Hansel JUT.HSLTech. x JUnit-JUnitScenario JUT.JUSTech. x TestGen4J-JUnit TG4.JUTTech. x Eclipse-JUnit ECP.JUTTech, Meth. x Eclipse-Solex ECP.SLXTech, Meth. x Eclipse-SVN ECP.SVNTech, Meth. x Eclipse-Javadoc ECP.JVDTech x Eclipse-HibernateSynchronizer ECP.HBSTech, Meth. x Eclipse-Tomcat ECP.TCTTech. x Eclipse-BEA Workshop ECP.JERTech, Meth. x Tomcat-JBoss TCT.JBSTech. x EclipseUML-Eclipse ECU.ECPTech, Meth. x EclipseUML-MySQL ECU.MYSTech. x HibernateSynchronizer-MySQL HBS.MYSTech, Meth. x BWI-JUnit BWI.JUTTech, Meth. x BWI-JUnitScenario BWI.JUSTech, Meth. x BWI-SVN BWI.SVNTech, Meth. x

20. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 20 Integration (3/4) Example 1 The two complicated gateways are:The two complicated gateways are: 1.Junit-JUnitScenario

21. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 21 Integration (4/4) Example 2 2.TestGen4J - JUnit

22. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 22 CASE development plan

23. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 23 CASE development plan Gateways to developGateways to develop SequencingSequencing

24. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 24 CASE Development Plan (1/2) Gateways to develop 17 gateways17 gateways Only two gateways considered as long and difficultOnly two gateways considered as long and difficult –Junit-JUnitScenario –TestGen4J - JUnit 7 out of 17 are plug-in and don’t need work for integration 7 out of 17 are plug-in and don’t need work for integration All gateways can be developed in the assigned timeAll gateways can be developed in the assigned time Cost JUnit-Hansel 7 JUnit-JUnitScenario 9 TestGen4J-JUnit 9 Eclipse-JUnit 1 Eclipse-Solex 3 Eclipse-SVN 1 Eclipse-Javadoc 1 Eclipse-HibernateSynchronizer 7 Eclipse-Tomcat 1 Eclipse-BEA Workshop 1 Tomcat-JBoss 1 EclipseUML-Eclipse 1 EclipseUML-MySQL 6 HibernateSynchronizer-MySQL 2 BWI-JUnit 6 BWI-JUnitScenario 6 BWI-SVN 5

25. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 25 CASE Development Plan (2/2) Sequencing The first tool to be developed will be BWI, which is a hub between several tools After, all the missing script for each gateways will be developed To finish, Batches and BBC will be created allowing to control all the CASE from one place Estimated time for the entire CASE development is 4 weeks with 5 people according the costs table

26. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 26 Conclusion

27. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 27 Conclusion (1/2) Value Added Strong interaction between project development team and customerStrong interaction between project development team and customer –XP method –Web interface for collaborative work Code generationCode generation –Main goal –Eclipse-Hibernate gateway will generate a maximum of source code –TestGen4J-Junit will be able to generate tests A functional CASEA functional CASE –Reducing number of interface (BWI + Eclipse) –Scripts supervising other scripts (BBC) –A logic allocation of the tools and of the repository –Answer specific needs : Sygime Technical and methodological qualityTechnical and methodological quality –A repository based on SVN and data in a DataBase

28. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 28 Conclusion (2/2) Sygime Development PlanDevelopment Plan 1.Database conception (BDE) 2.Web Interface design (BDE) 3.Define functional tests (BWI) 4.Code generation (BDE + BBC) 5.Add and correct business code (BDE) 6.Verify test validation (BBC report) 7.Back to 3 for more functionalities Web Interface will be generated Controlled Security Automated database access Low development costs Quality assurance via tests and iterative development

29. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 29 Questions ?

30. BEWITCHED 15/06/2006Soutenance GLAO #2 slide 30 CASE Development Plan (1/2) Costs of the gateways (Bonus) The costs table has been define as follow Costs tablesEstimated timeApproximate work for this cost 0-Inexistent Gateway 1ImmediateExisting gateway (generally plug-in or compatible formats) 20,5hGateway possible with configuration 31hGateway possible with existing intermediate tools 44hFiles can be formatted to helped integration 51dOne connector is needed 62dSeveral connector are needed 74dSeveral connector are needed with external tools 81weekA connector changing a file is needed 92-3weeksWrite of several connectors with multiple files manipulation 101yearPart of tools to rewrite Back