recent trends and activities around software process improvement

Click here to load reader

Download Recent trends and activities around Software Process Improvement

Post on 17-Jan-2016

28 views

Category:

Documents

0 download

Embed Size (px)

DESCRIPTION

Recent trends and activities around Software Process Improvement. Reidar Conradi Dept. of Computer and Information Science Norwegian University of Science and Technology Trondheim www.idi.ntnu.no/~conradi, [email protected] Tel +47 73.593444, Fax +47 73.594466. 1. My recent background - PowerPoint PPT Presentation

TRANSCRIPT

  • Recent trends and activities around Software Process ImprovementReidar ConradiDept. of Computer and Information ScienceNorwegian University of Science and TechnologyTrondheim

    www.idi.ntnu.no/~conradi, [email protected] +47 73.593444, Fax +47 73.594466

  • Overview1. My recent background2. Some current SPI projects and activities3. Three promising new technologies: 3.1 Incremental/COTS-based development3.2 Internet/mobile technologies3.3 Inspections (for UML)4. Knowledge management and experience bases5. SPI frameworks and strategies6. SFF-Fornebu7. Empirical software engineering8. Future SPI challenges

  • 1. My recent backgroundESPRIT sw.eng. projects in 1990-1999: reuse, configurations, reengineering, process modeling, ...Natl SPI projects: SPIQ 1997-99, PROFIT 2000-02.Sabbatical stay at Univ. Maryland and Politecnico di Milano, 1999-2000.Visits and contact with IESE, Kaiserslautern.Workshops in 2000: EWSPT, PROFES, Learning Software Organizations and FEAST.Discussions at ISERN research network meeting (Basili/Rombach et Co.), Oct. 2000, Hawaii.Some contact with Q-labs, Univ. Lund, and VTT.

  • 2a. PITAC: Presidents IT Advisory CommitteeFinal recommendation Feb. 1999, www.hpcc.gov:Software -- no surprise software, empirical workScalable Software Infrastructure -- too fragileHigh End ResearchHigh End ApplicationsSocioeconomic FactorsDouble funds for basic research in IT, to 2 bill. $.NSF has initiated first ITR projects, 100 mill. $, 50 projects accepted out of 1500 applications!First projects started Sept. 2000, including CeBASE.

  • 2b. Univ. Maryland / prof. BasiliWorld famous for its SPI work with the NASA-SEL in 1976-2000: Quality Improvement Paradigm (QIP)Experience Factory / Experience Bases Goal Question Metrics method (GQM) Inspection techniques (perspective-based reading)Empirical methods (contextual factors)Some COTS workProjects with NASA, Motorola, DaimlerChrysler, Telcordia, Lucent, consortium of local SMEs etc.Univ. Maryland and its new FC-MD Fraunhofer institute: 20 researchers/PhD students.I worked on experience bases, OO reading, COTS.

  • 2c. NASA Software Engineering LaboratoryGoddard Space Flight Center, 270 software developers, 9000 people. Unmanned spacecrafts, geophysical data. Project size: 30 person-years over two years. Technology: FORTRAN, later Ada and C++.NASA-SEL: coop. by NASA, CSC, U. Maryland. Tracked 150 projects, testing different technologies.Results in 1976-96: reduced defects in operation to 1/4, 2X productivity, more complex projects.Most important technology: software reuse by domain-specific frameworks -- from 25% to 80% reuse.Egoless approach: measuring/learning in the culture.

  • 2d. CeBASE projectNew CeBASE (Center of Empiricism) NSF-PITAC project from 15. Sept. 2000, www.cebase.org.V.Basili, B.Boehm (USC), U. Nebraska, U. Tennessee.1.2 mill. $ per year for two years + three more years:Inspections (Maryland)COTS (USC)Empircial methods (all)Experience Bases, with contents (U. Nebraska)Software Engineering Education (U. Tennessee)Slogan: FAD-based => empirically-based => science-based => engineering-based.Manifest of Understanding:U.Maryland & NTNU/UiO.

  • 2e. IESE, Kaiserslautern, prof. RombachIESE: Fraunhofer Institute, Germany, applied researchArea: Experimental Software Engineering.Established in 1995, made permanent in 1998. Close to 100 persons, ca. 40% government funded.SPI and software qualitySoftware product lines and reuseInspectionsExperience bases using Case-Based ReasoningSoftware Engineering Education: SW AcademySister institute in Maryland from 1998.NTNU PhD student Dingsyr: at IESE, Spring 2001

  • 2f. ISERN, Intl Sw.Eng. Research NetworkClub around Basili/Rombach from1992, 20 members.NTNU a member since 1997, UiO will apply.Meetings:Oct. 2000 on Hawaii, Aug. 2001 in Glasgow.Topics:Inspections, e.g. for OO (Maryland, Vienna, NTNU)Technology transferEmpirical methods, practical experiencesRepeatable experiments: planned for OO designShared repository for experiments (Conradi ed.)ESERNET: network of excellence proposal in EU, Nov. 2000 (NTNU participates).

  • 3.1a Incremental and component-based developmentLead-times shrinking: one Internet-year a dog-year (7 years) in other businesses.Strict waterfall model is not functioning anymore:Incremental/iterative approaches, having continuous dialog with customer, reduce risk. Ex. RUP, Genova.Component-based approaches, reusing parts of existing solutions or ready-made components (COTS).(Re)negotiating requirements, if needed component is not yet available, but increased dependency on other actors (higher risk).Different work style: need models to reason about and balance e.g. time/quality trade-offs, market-value models.

  • 3.1b Barry Boehms COCOMO-IIIncremental development using COTS. Initial, iterative steps e.g. to scale and refocus project.

    Traditional situation:

    Current trends:

    Clear separation between

    requirements and design

    Everything connected

    Stable requirements

    Rapid requirements change

    (50% change per 3 year)

    Technical solutions are separate

    COTS influence requirements

    Mostly in-house and controllable parts

    No control over COTS evolution

    >2 year projects

    Ever-decreasing lead times

    Repeatable, mature models

    Adaptable process models

  • 3.1c INCO project: Incremental and Component-Based DevelopmentNewly accepted NFR basic R&D project, 2001-2004. UiO and NTNU. 2 PhDs and one postdoc.Need a revolution in project models -- waterfall is dead, internet time, extend RUP and similar models. Rqmts design: a negotiation!Component-based development, using Components-Off-The-Shelf (COTS) -- but how to manage the risks?Reuse through mature product lines?Empirical studies towards Norwegian IT industry.Proposers: Dag Sjberg, Univ. Oslo (coord.) and Reidar Conradi, NTNU.

  • 3.2a New network technologies: revolution in sw.eng. applications and solutions!Application side: 300 mill. mobile phones in Jan. 2000, 3 bill. in 2005 and 10% with powerful PCs/PDAs? Entry ticket to become a global (virtual?) company: reduced by factor 100 in recent years.Enormous dynamics: 3C convergence, liberalizationNew work modes: RAD, nomadic, 100% on-line.Technology side:Deluge: www, IP, Java, CORBA, XML, applets / servets / displets, agents = active html pages?, E.g. XML used for sending phone bills to bank, XML/Java tools to make graphical editors.

  • 3.2b MOWAHS project: Mobile Work Across Heterogeneous SystemsNewly accepted NFR basic R&D project, 2001-2004. IDI SU and DB group. 2 PhDs and one postdoc.Software infrastructure for mobile agents that can move across fixed and portable PCs, PDAs etc. Novel transaction models to regulate access and updates to partly shared data.Try out for software engineering and teachingInternationalization, Telenor and other cooperation?Proposers: Reidar Conradi (coord.) and Mads Nygrd, NTNU.

  • 3.3a InspectionsBy Michael Fagan at IBM, 1976; refined by Tom Gilb.Established gains, finds 2/3 of defects at 1/3 of price, saves 15-20% of total effort.Still challenges:Perspective-based reading: different checklists for different readers (customer, designer, tester) to find complementary defects.Inspections vs. testing: which defects by which technique; cf. Cleanroom.Longitudinal studies: find defect-prone modules?Root-Cause-Analysis: follow-up, prevention?OO reading techniques: for UML, for architecture?

  • 3.3b Ericsson data, 95-97Study 1: Cost-effectiveness of inspections and testing

    Activity

    Defects [#]

    Effort [h]

    Of total [%]

    Effort spent to find one defect

    [h:m]

    Estimated saved effort by early defect removal [h]

    Inspection reading (design)

    928

    786.8

    61.78

    00:51

    8200

    Inspection meeting (design)

    29

    375.7

    1.92

    12:57

    Desk check

    404

    1257.0

    26.91

    03:07

    -

    Function test

    89

    7000.0

    5.92

    78:39

    -

    System test

    17

    -

    1.13

    -

    -

    Field use

    35

    -

    2.33

    -

    -

  • 3.3c Ericsson data, 95-97 Study 1- number of defects in field-use versus states in a module

    The number of system failures increases with increasing number of states (complexity).Defects found in field-useNo. of states

  • 3.3d OO Reading of UML Documents Software Artifacts, with seven new OO Reading Techniques (OORTs) indicated:RequirementsDescriptionsUse-CasesRequirementsSpecification/AnalysisHigh LevelDesignClassDiagramsClassDescriptionsState DiagramsSequenceDiagramsOORT-1Vertical readingHorizontal readingOORT-6OORT-7OORT-5OORT-3OORT-2OORT-4

  • 3.3e OO Reading of UML (contd)How to read graphical diagrams, not linear text?Horizontal reading (OORT1-4) within a phase captures mainly inconsistencies.Vertical reading (OORT5-7) across phases captures mainly omissions and wrong facts.Easy to spot simple defects,what about deeper comments wrt. architecture and maintenance?Tried at Maryland and NTNU.Now emphasis on simple defects. Need to refine and extend before industrial use.

  • 4a. Knowledge Management, Experience BasesSystematize own experiences as reusable knowledge.Problems:Few, representative observationsFew hard data, mix of quantitative/qualitative dataReference point/baseline often missingVulnerable to short-time project pressure, even cancellations -- as in SPI and reuseLearning organization: apply methods from Knowledge Engineering and/or Social Sciences?Novel investment models, reward systems?

  • 4b. NASA Experience Factory

  • 4c. The Knowledge Spiral

  • 4d. Extern

View more