ESPINODE for Finnish ESSI Process Improvement Experiments (Esprit projekti nro 27752) Tavoitteet

Transkriptio

1 1

2 ESPINODE for Finnish ESSI Process Improvement Experiments (Esprit projekti nro 27752) Tavoitteet Edistää ohjelmistoprosessitietämystä Suomessa Tukea suomalaisia ESSI-projekteja (European System and Software Initiative) Aktiviteetit FINESSE asiakaslehdet ja seminaarit Raportit Aikataulu 3/1998-4/2000 2

3 FINESSE aktiviteetit Aikataulu FINESSE Newsletter No 1 September 1998 Seminar No1 April 13th 1999 FINESSE Newsletter No 2 March 1999 Seminar No2 October 28th 1999 FINESSE Newsletter No 3 September 1999 Seminar No 3 February 2000 FINESSE Newsletter No 4 March 2000 Seminar No 4 April

4 Putting research at the service of the citizen IST programme (Information Society Technologies) User-friendly information society Belongs to the thematic programmes of 5th Framework 4

5 KA1: Systems and and services for for the the citizen KA2: New New methods of of work and and electronic commerce KA3: Multimedia content and and tools KA4: Essential technologies and and infrastructures Future and and emerging technologies Research networking 646 MEURO 547 MEURO 564 MEURO 1,363 MEURO 319 MEURO 161 MEURO Cross-Programme themes at least 10% of programme 5

6 Technologies and Engineering for Software, Systems and Services (KA IV.3): Includes 4 action lines lines IV.3.1 Component-based software engineering IV.3.2 Engineering of intelligent services IV.3.3 Methods and tools for intelligent & knowl. sharing IV.3.4 Information management methods 6

7 Objective: To develop and validate the innovative processes, methods and tools necessary to design, implement and manage using a component-based approach Focus: The focus is on re-use, the incorporation of new technology COTS components and Expected result: The work should result in the definition of processes, methods and their supporting technologies that enable the smooth and integration of components from multiple independent sources into complex systems and services 7

8 Component-based software engineering Defined project type: Best Practice Actions In Best Practice Actions, one or more user organisations participate. They must... Demonstrate a sound analysis of of Identify a clear for for improvement Identify clearly the Plan for for of of new practices to to achieve this 8

9 To improve the software development process small steps measurements of improvement on underlying baseline Best Practice in Software Development Software Best Practice Software development, making the best use of currently available methods and technologies, in the most appropriate way according to business needs 9

10 One or more user organizations Obligation to disseminate Time frame: 9 to 18 months EU funding from 50% up to 100% Cost categories for Take up measure Percentage of funding Personnel 100 % Durable equipment 50 % Consumables 50 % Travel and Subsistence 50 % Computing *50% Subcontracting 50 % IPR protection 0 % Other costs 100 % Overheads 0 % Co-ordination 100 % 10

11 Information from Commission available: The Work Programme Description of action lines The Proposers Guides and the forms How to structure and present a proposal The Evaluation Manual The criteria under which the proposal will be evaluated 11

12 Part A - administrative and budget information Forms A0-A4 Can be filled with the support of the ProTool (CORDIS) Part B - Description of the scientific/technical content Anonymous, relates to 1st evaluation criterion Part C - Description of the EU added value, contribution to community policies, dissemination, exploitation and management Non anonymous, relates to 2 to 5th evaluation criterion 12

13 Electronically: pre-registration to be requested for electronic signature On paper: 1 original and 5 copies to be delivered to the Commission please mark on the envelope IST Programme to what specified 13

14 Criteria Weight (1) Threshold (2) 1. Scientific/Technological Quality and innovation Community Added Value and contribution to EU policy Contribution to Comm. Social objectives 2-4. Economic Dev; S&T prospects (range of applications, exploitation, strategic impact, dissemination) Resources, Partnership, Management

15 1. Individual evaluation by at least 3 experts first criterion 1 (anonymous), then rest 2. Consensus between 3 experts on draft summary scores for 5 criteria + comments 3. Discussion in panel for calibration / ranking and final overall mark to proposals 4. Recommendations to Commission for final decision on ranking 15

16 Commission Web site: IST Helpdesk: Fax ist@cec.be IST Conference 1999 in Helsinki November TEKES 16

17 Process before technology People and Soft Issues are important Training of People shall not be forgotten 17

18 Higher project awareness in smaller SWD companies Higher competitiveness, improvement in productivity Improvement in employees attitude (in project) Cultural turning point Certifications (like ISO) Some learned what they should do, but... 18

19 Still too often: the move towards improvement remains technology driven Lack of maturity of the tools and the support for them Missing a business driver leads to an invisible ROI And the greatest of all 19

20 Todella helpot Onko hakemuslomakkeen kaikki kohdat täytetty? Ovatko kaikki tarvittavat allekirjoitukset kohdillaan? Onko konsortion koostumus oikea (tarvittava määrä, ovatko riippumattomia) ja perusteltavissa (läsnäolon syyt)? Ovatko anotut summat realistisia, onko yhteenlasku suoritettu oikein? 20

21 Helpot Onko kieli oikeaoppista? Vastaako tekstin pituus annettuja ohjeita? Vastataanko kaikkiin kysymyksiin? Onko hakemus siistin näköinen? 21

22 Muista myös Etsi avainsanat työohjelmasta käytä niitä hakemuksessasi Kaikissa hakulomakkeen kohdissa pitää antaa tarvittavasti tietoa Mainitse projektiin liittyvät uudet asiat ensimmäisenä Lueta hakemuksen teksti syntyperäisellä lukijalla Kiinnitä erityinen huomio projektikuvauksen tiivistelmään. Käytä yhteenvetoja myös antamaan hakemukselle ryhtiä sielläkin, missä niitä ei erikseen pyydetä. Käytä kaaviokuvia tarvittaessa, esim. konsortion tehtäväjako kannattaa esittää graafisesti Sovi IPR-asiat ajoissa, tee konsortiosopimus 22

23 Vaikeat Vastaako projektin sisältö työohjelman vaatimuksiin? Ovatko projektin päämäärät selvillä? Ymmärtääkö amatöörilukija ne (puoliso, sisko/veli )? Käykö projektin uutuusarvo selvästi esille? Onko partnerien tehtäväjako selkeä? Selviääkö hakemuksesta miten projektia aiotaan hallinnoida? Onko hyödyntämissuunnitelma uskottava? Onko hakemuksen laatija lukenut arviointioppaan huolellisesti? Onko hakemukseen pyydetty palautetta luotettavalta mutta suorapuheiselta kollegalta? 23

24 Seija Komi-Sirviö VTT Elektroniikka Kaitoväylä 1, PL Oulu fax: (08) puh: (08) keskus suora GSM WWW 24