Artefacts
Bringing Clarity & Simplicity to Modelling

           The Fourth KISS Workshop
           17 November 2009 @ AS...
Are use cases the only legitimate software
    requirements artefacts?




2                  Software requirements artefa...
Observations
    •   We pack non-functional requirements into supplementary
        requirements documents

    •   Domain...
Are classes and interfaces the only
    legitimate software specification artefacts?




4                   Software spec...
Observations
    •   Architecture and technology decisions are recorded in
        software design documents

    •   MDD ...
Are business objects the only legitimate
    application data artefacts?




6                         Application data ar...
Observations
    •   When the number of objects is large we translate objects
        into database rows

    •   When the...
Are we any good at managing the
    dependencies between all these artefacts?




8       Managing dependencies between ar...
Observations
    •   Commercial tools for managing artefacts are a band aid at
        best

    •   We treat artefacts di...
What is an artefact?
     •   An artefact is a container of information

     •   An artefact is instantiated by a specifi...
Candidate Artefacts
     •   Emails?

     •   Documents?

     •   Models?

     •   Files?

     •   ...




11         ...
Observations
            •   Reducing the granularity of artefacts shifts complexity to the
                dependency gra...
Models
     •   When does a model start to be too big?

     •   When does a model start to be too small?

     •   Is the...
Formal artefacts
     •   A formal artefact has all characteristics of an artefact

     •   A formal artefact is instanti...
Disqualified candidate formal artefacts
     •   Emails (contained information can’t easily be processed)

     •   Text d...
The future
     •   Tools for incrementally transforming informal artefacts into
         formal artefacts

     •   Colla...
Today
     •   Manual formalisation of artefacts

     •   Formal artefacts are used in specialised domains

     •   Tran...
Observations
     •   The problem of referential integrity was solved many years
         ago by database and CASE tool ve...
Work to be done
     •   Most database rows are much too small to qualify as
         artefacts

     •   Many artefacts a...
Summary
     •   Renaming artefacts every few years to conform to the latest
         technology jargon (service, componen...
Thank you!
   Jorn Bettin
jbe @ sofismo.ch
Skype jorn_bettin
+41 62 891 0987
Upcoming SlideShare
Loading in...5
×

Artefacts - Bringing Clarity & Simplicity to Modelling

2,657

Published on

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,657
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Artefacts - Bringing Clarity & Simplicity to Modelling

  1. 1. Artefacts Bringing Clarity & Simplicity to Modelling The Fourth KISS Workshop 17 November 2009 @ ASE Auckland, New Zealand www.industrialized-software.org/kiss-ase-2009
  2. 2. Are use cases the only legitimate software requirements artefacts? 2 Software requirements artefacts
  3. 3. Observations • We pack non-functional requirements into supplementary requirements documents • Domain experts submit arbitrary specifications in various formats • We make extensive use of emails, wikis, and other “web 2.0” artefacts • Additionally we rely on verbal communication ★ saying A (nice and short) ★ actually meaning B (the fuzzy story in the back of our head) ★ and being interpreted as having said C (the minimum design that can be passed off as meeting requirement A) 3 Software requirements artefacts
  4. 4. Are classes and interfaces the only legitimate software specification artefacts? 4 Software specification artefacts
  5. 5. Observations • Architecture and technology decisions are recorded in software design documents • MDD practitioners think it’s cool to put some decisions into models • When the decision binding time is late we invent ad-hoc configuration files • When the decision binding time is even later we stuff specifications into databases 5 Software specification artefacts
  6. 6. Are business objects the only legitimate application data artefacts? 6 Application data artefacts
  7. 7. Observations • When the number of objects is large we translate objects into database rows • When the number of objects is small we translate objects into files (XML, ...) • We reluctantly deal with spreadsheets created by domain experts • We acknowledge and deal with the existence of links between business objects 7 Application data artefacts
  8. 8. Are we any good at managing the dependencies between all these artefacts? 8 Managing dependencies between artefacts
  9. 9. Observations • Commercial tools for managing artefacts are a band aid at best • We treat artefacts differently depending on their technological format • We make naive assumptions about the way artefacts change over time ★ As if version control tools provide a satisfactory answer ★ As if artefacts can’t have different levels of completeness ★ As if the structure of an artefact does not vary over time ★ As if it is okay to manually ensure referential integrity between artefacts 9 Managing dependencies between artefacts
  10. 10. What is an artefact? • An artefact is a container of information • An artefact is instantiated by a specific actor (human or a system) • An artefact is consumed by at least one actor (human or system) • An artefact represents a natural unit of work (for the instantiating and consuming actors) • An artefact may contain links to other artefacts • An artefact has a state and a lifecycle 10 A basic definition
  11. 11. Candidate Artefacts • Emails? • Documents? • Models? • Files? • ... 11 How do we measure artefact quality?
  12. 12. Observations • Reducing the granularity of artefacts shifts complexity to the dependency graph between artefacts • Increasing the granularity of artefacts shifts complexity into the individual artefacts • The dependency graph between artefacts must be considered as an artefact as well • The granularity of artefacts must be optimised with respect to overall complexity, it must not be dictated by technology • Artefacts that are connected by a circuit of links do not qualify as a modular design • Artefact value tends towards zero if the links between artefacts are unreliable 12 Complexity and artefact modularity are closely related
  13. 13. Models • When does a model start to be too big? • When does a model start to be too small? • Is there any difference between model and code? • Should we apply version control to individual model elements, or to a larger set of related model elements, or to sets of sets of model elements? • How do we handle links between models? • A model is supposed to be a representation, especially a mathematical one of (a phenomenon or system). How many modelling languages are enough? Which ones lead to good representations? 13 Modelling or Muddling?
  14. 14. Formal artefacts • A formal artefact has all characteristics of an artefact • A formal artefact is instantiated with the help of a software tool that enforces specific instantiation semantics • The information contained in a formal artefact can be easily processed by software tools • Referential integrity between formal artefacts is preserved at all times with the help of a software tool • No circular links between formal artefacts are allowed at any time • The lifecycle of a formal artefact is described in a state machine • The events consumed and produced by the artefact state machine are available for processing in software tools 14 A practically useful definition
  15. 15. Disqualified candidate formal artefacts • Emails (contained information can’t easily be processed) • Text documents (a set of text documents may contain circular references) • UML models (referential integrity between UML models is usually not guaranteed) • Database rows (granularity is too small) • Source code files (referential integrity is not guaranteed at all times) • In-memory objects (artefact boundaries are not well defined) • ... 15 Formal artefacts are still rare!
  16. 16. The future • Tools for incrementally transforming informal artefacts into formal artefacts • Collaboration based on formal artefacts • Transformation & generation technologies used to integrate formal artefacts with legacy systems • Systems conceived from the ground up in terms of collaborating formal artefact state machines • Collaborating software tools that implement complementary partial semantics for formal artefacts 16 Formal artefacts have huge potential
  17. 17. Today • Manual formalisation of artefacts • Formal artefacts are used in specialised domains • Transformation & generation technologies are already used to integrate formal artefacts with legacy systems • Only few software tools provide repositories for formal artefacts that enforce referential integrity and that provide adequate means for artefact modularity ★ Lacking repository functionality can be built into editors ★ Artefact modularity can be achieved by adhering to the KISS principles related to formal artefact modularity • Interoperability between software tools for managing formal artefacts is largely lacking ★ But transformation technologies enable DIY solutions 17 Formal artefacts are gaining ground
  18. 18. Observations • The problem of referential integrity was solved many years ago by database and CASE tool vendors • We need to apply the lessons from data management to software specification management, but we need to apply them intelligently • The KISS principles and guidelines are a starting point • To date the role of artefacts as natural units of work has been neglected 18 Lessons to be applied
  19. 19. Work to be done • Most database rows are much too small to qualify as artefacts • Many artefacts are either too small or too large • No concensus yet in the modelling community on banning circular references between artefacts • All artefact changes need to be proper transactions • When using traditional artefacts, the deployment of a software change feels more like an earthquake than a transaction ★ Practical impossibility to stengthen QA measures to complely avoid damage ★ The larger the change the higher the likelyhood of aftershocks 19 Incrementally replacing traditional artefacts
  20. 20. Summary • Renaming artefacts every few years to conform to the latest technology jargon (service, component, object, entity, ...) makes little sense • Traditional artefacts often lack modularity and some may even have circular references • In the absence of formal artefacts, each technology binding makes its own assumption about artefact boundaries • Software users experience the use of software as the execution of a series of mysterious rituals • Software change should always be as low-risk as a database transaction 20 The business case
  21. 21. Thank you! Jorn Bettin jbe @ sofismo.ch Skype jorn_bettin +41 62 891 0987
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×