Be Smart! What they don t teach you. Ivar Jacobson. with Ian Spence, Pan Wei Ng and Kurt Bittner

Size: px

Start display at page:

Download "Be Smart! What they don t teach you. Ivar Jacobson. with Ian Spence, Pan Wei Ng and Kurt Bittner"

Kerry Kelley
5 years ago
Views:

1 Be Smart! or What they don t teach you about software at school Ivar Jacobson with Ian Spence, Pan Wei Ng and Kurt Bittner ivar@ivarjacobson.com

2 Our goal is the same as always! Good Software Good Software, Quickly and at Low Cost! 2008 Ivar Jacobson International 2

3 What it takes Quickly Competent & Motivated People Low Cost Large Scale Reuse of Components Good Software Useful Extensible Reliable 2008 Ivar Jacobson International 3

4 How good are we at software development? Usable: Low High Extensible: Low High Reliable: Low High Reuse of Components: Low High Competency: Low High Motivation: Low High 2008 Ivar Jacobson International 4

5 Some people feel we are this good How a Software Company would design a Treeswing 2008 Ivar Jacobson International 5

6 Let s look at our press 2008 Ivar Jacobson International 6

7 It certainly seems like Usable: Low High Extensible: Low High Reliable: Low High Reuse of Components: Low High Competency: Low High Motivation: Low High we need to get better! 2008 Ivar Jacobson International 7

One major obstacle we are a fashion industry Software Development is driven by fashions and fads Fifteen years ago it was all about OO Ten years ago it was about components, UML, Unified Process Five

8 One major obstacle we are a fashion industry Software Development is driven by fashions and fads Fifteen years ago it was all about OO Ten years ago it was about components, UML, Unified Process Five years ago it was about RUP and CMMI Two years ago it was about XP Today it is about Scrum All good, but none is all you need This is unsmart! The software industry keeps looking for a silver bullet 2008 Ivar Jacobson International 8

9 One major obstacle we are a fashion industry Yes, Software Development is driven by fashions and fads Fifteen years ago it was all about OO Ten years ago it was about components, UML, Unified Process Five years ago it was about RUP and CMMI Two years ago it was about XP Today it is about Scrum All good, but none is all you need This is unsmart! The software industry keeps looking for silver bullets 2008 Ivar Jacobson International 9

10 One major obstacle we are a fashion industry Yes, Software Development is driven by fashions and fads Fifteen years ago it was all about OO Ten years ago it was about components, UML, Unified Process Five years ago it was about RUP and CMMI Two years ago it was about XP Today it is about Scrum All good, but none is all you need This is unsmart! The software industry keeps looking for silver bullets 2008 Ivar Jacobson International 10

11 Agenda 1. What does Smart mean? 2. Smart Cases Recognize it when you see it 3. How do you become Smart 4. What does Smart really mean? 2008 Ivar Jacobson International 11

12 What does Smart mean? Things should be done as simple as possible but no simpler - Albert Einstein E= mc 2 This is smart! 2008 Ivar Jacobson International 12

13 What does being Smart mean? Being Smart is not the same thing as being intelligent You can be intelligent without being smart - and you can be very smart without being very intelligent Smart is more than having common sense You can have common sense without being smart, but if you are smart you must have common sense. Being Smart is being agile, but more Agile means being flexible and adaptable to different situations. Being Smart = Being Agile ++ Mr Smart 2008 Ivar Jacobson International 13

14 Agenda 1. What does Smart mean? 2. Smart Cases Recognize it when you see it 1. People 2. Teams 3. Projects 4. Requirements 5. Architecture 6. Modeling 7. Test 8. Documentation 9. Process 10.Knowledge 3. How do you become Smart 4. What does Smart really mean? What they don t teach you about software at school Ivar Jacobson International 14

15 Unsmart with People Some companies view process and tools as more important than people They think they can use process to make people interchangeable They think that tools will make people with poor skills as effective as people with excellent skills This is unsmart! A fool with a tool is still a fool but a dangerous fool 2008 Ivar Jacobson International 15

16 Smart with People Have you ever seen any software being developed by process and tools? Case study: Ericsson AXE the largest commercial success story ever in Sweden We had no tools and no defined process Despite this, we developed components, use cases, and a modeling language now part of UML This could only have been done with people good people Software is developed by people! By competent and motivated people Using consumable practices and tools Balancing tasks with competencies This is smart! 2008 Ivar Jacobson International 16

17 Unsmart with Teams Many software projects involve 20+ people Often organized into stove-pipe groups: Requirements, Analysis, Design, Coding, Testing, etc. This is unsmart! Requirements Implementation Test 2008 Ivar Jacobson International 17

18 Smart with Teams Software development is a team sport Teams are cross-functional Including analysts, developers, testers etc Ideal size of the team is less than 10 people Bigger projects should be organized as team of teams This is smart! 2008 Ivar Jacobson International 18

19 Unsmart with Projects Most companies still follow the waterfall approach Requirements High-Level Design This is unsmart! Detailed-Level Design Coding Testing Crash! 2008 Ivar Jacobson International 19

20 Smart with Projects Build a skinny system to demonstrate that you have eliminated all critical risks Add more capabilities on top of that skinny system Skinny System This is smart! Full Fledged System Think big, build in small steps 2008 Ivar Jacobson International 20

21 Unsmart with Requirements A constant in software development is that requirements always change Still many managers believe you can detail all the requirements upfront......and based on these can accurately predict the cost of the solution Thou shalt work with fixed requirements for fixed prices This is unsmart! 2008 Ivar Jacobson International 21

22 Smart with Requirements Base early decisions on lightweight requirements and detail as and when it is needed Use case outlines, feature lists or user stories Design your project for requirement changes Remember requirements are negotiable and priorities will change I understand your needs, let s work together to make sure we develop the right system for the right price. This is smart! 2008 Ivar Jacobson International 22

23 Unsmart with Architecture Two extremes: Mr Enterprise Architect on Ivory Tower No architecture Just Code Refactor later This is unsmart! I ll design everything up front Mr Supposedly Agile The single most important determinant of a software system s quality is the quality of its architecture 2008 Ivar Jacobson International 23

24 Smart with Architecture Focus on the skinny system But an architecture without executable code is a hallucination Refactor over releases, but large refactoring is very costly This is smart! Architectural Blue Print Skinny System Full Fledged System 2008 Ivar Jacobson International 24

25 1: Doc view request ( L ) Window95 ¹ ¼- ü Å óàì¾ðæ.exe Windows NT Windows NT ¹ ¼- ü Áø.EXE Windows95 IBM Mainframe µ ÀÌÅ º ÀÌ½º¼-¹ö Solaris ÀÀ ë¼-¹ö.exe Windows95 ¹ ¼- ü ¾ÖÇ Ã Alpha UNIX Æ Á ¹ ¼- ëçñ º ±â»ç ëàú äã»ç Ñ Ù. È-ÀÏ ü ÀÚ Â ÀÐ¾î Â ¹ ¼-ÀÇ Á º ÇØ ç ¹ ¼- Ã¼ ¼³Á À» äã»ç Ñ Ù. È- é Ã¼ Â ÀÐ¾îµéÀÎ Ã¼µé ëçø ÀÌ º Î Á ÄÀ» ½ÃÄÑ È- é º ÁØ Ù. 1: Doc view request ( ) Openning 2: fetchdoc( ) 9: sortbyname ( ) Reading add file [ numberoffile==max ] / flag OFF 3: create ( ) 6: filldocument ( ) close file 4: create ( ) 8: fillfile ( ) 5: readdoc ( ) 7: readfile ( ) Closing close file add file Writing Unsmart with Modeling We have always had programming languages. Now we also have modeling languages Mr Analysis and Design Standards FileMgr fetchdoc( ) sortbyname( ) DocumentList add( ) delete( ) Document name : int docid : int numfield : int Actor A Use Case 1 Actor B FileList add( ) delete( ) flist 1 get( ) open( ) close( ) read( ) sortfilelist( ) create( ) filldocument( ) read() fill the code.. Use Case 2 rep Repository File Use Case 3 (from Persistence) name : char * = 0 readdoc( ) readfile( ) read( ) GrpFile read( ) open( ) create( ) fillfile( ) Repository DocumentList 9: sortbyname ( ) mainwnd : MainWnd This is unsmart! 2: fetchdoc( ) 4: create ( ) gfile : GrpFile 8: fillfile ( ) user : Clerk filemgr : FileMgr 3: create ( ) 6: filldocument ( ) FileManager Document GraphicFile File FileList 7: readfile ( ) 5: readdoc ( ) repository : Repository document : Document user mainwndfilemgr : document : repository FileMgr Document gfile Mr Hacker Model Nothing Just Code Model everything 2008 Ivar Jacobson International 25

26 Smart with Modeling If the modeling language isn t executable, focus on the essentials only the skinny system Don t duplicate the effort by modeling everything, Full Fledged System This is smart! 2008 Ivar Jacobson International 26

27 Unsmart with Test We have two classes of people: Developers and Testers Developers are the creators it is OK to create bugs as well Testers are the cleaners in the software world Testing is done as an after thought too late and too expensive This is unsmart! 2008 Ivar Jacobson International 27

28 Smart with Test Our mantra: Whatever you do you are not done until you have verified that you did what you wanted to do. We are all testers! This is smart! 2008 Ivar Jacobson International 28

29 Unsmart with Documentation There has been an over-emphasis on teams producing documentation Thou shalt follow the document template I give you to document every part of the system. This is unsmart! 2008 Ivar Jacobson International 29

30 Smart with Documentation Myth: The idea that you document software so people later can read what you did. Law of nature: People don t read documents Focus on the essentials, the placeholders for conversations, people figure out the rest themselves Emphasize the essentials This is smart! making sure the documents add value Ivar Jacobson International 30

31 Unsmart with Process/Methodology/Approach Agile CMMI Unified Process CMMI Existing Way of Working Project Lead 2008 Ivar Jacobson International 31

32 Unsmart with Process/Methodology/Approach Agile CMMI Unified Process CMMI Existing Way of Working Project Lead 2008 Ivar Jacobson International 32

33 Unsmart with Process/Methodology/Approach Agile CMMI I want a new way of working Unified Process CMMI New Way of Working Project Lead 2008 Ivar Jacobson International 33

34 Unsmart with Process/Methodology/Approach We have got enough of process Agile I like to have Let me start I some want of to have with Agile, some unified of CMMI maybe process Unified Process CMMI New Way of Working Does I cannot not get it work together This is unsmart! Project Lead 2008 Ivar Jacobson International 34

35 Smart with Process/Methodology/Approach Existing Way of Working 1. Use a practice-based approach (such as EssWork) 2. Practices are separate but composable 3. Practices come from any source in the world 4. Improve in small steps 2008 Ivar Jacobson International 35

36 Smart with Process/Methodology/Approach And the Law of Nature: People don t read process books So focus on the essentials, people figure out the rest themselves New Way of Working This is smart! 1. Use a practice-based approach (such as EssWork) 2. Practices are separate but composable 3. Practices come from any source in the world 4. Improve in small steps 2008 Ivar Jacobson International 36

37 Unsmart with Knowledge People have unlimited access to information: Wikipedia Google Lot s of books But it doesn t make them smarter: People don t read Information competes and conflicts It s never put into context I ve got all this guidance but it doesn t help me This is unsmart! Just collecting information on your internet is pointless now people can access the world-wide web Ivar Jacobson International 37

Smart with Knowledge Individuals just need enough to get the

for the specific point in time Context sensitive to the

instructions they want help Add active guidance, review,

tools I help with Iterative planning I help with use cases I

38 Smart with Knowledge Individuals just need enough to get the job done Not the whole composed process Just the bits needed for the specific point in time Context sensitive to the problem at hand Focused on the essentials They don t want instructions they want help Add active guidance, review, checking and help by automation Intelligent agents and smart tools I help with Iterative planning I help with use cases I help with architecture This is smart! 2008 Ivar Jacobson International 38

39 Agenda 1. What does Smart mean? 2. Smart Cases Recognize it when you see it 3. How do you become Smart 4. What does Smart really mean? 2008 Ivar Jacobson International 39

40 How do you become Smart? You need knowledge in good (maybe best) practices There are 100 s of practices, some of them are good Business Modeling Test-Driven Development Scrum Product-Line Engineering Risk-Driven Iterative Development Systems Engineering Aspect Orientation Robustness Analysis Retrospectives Business Process Re-Engineering Use-Case Driven Development Pair Programming PSP User Stories SOA Prince2 Use-Case Modeling Program Management And you need experience in using them 2008 Ivar Jacobson International 40

41 How do you become Smart? You need knowledge in good (maybe best) practices There are 100 s of practices, some of them are good Business Modeling Test-Driven Development Scrum Product-Line Engineering Risk-Driven Iterative Development Systems Engineering Aspect Orientation Robustness Analysis Retrospectives Business Process Re-Engineering Use-Case Driven Development Pair Programming PSP User Stories SOA Prince2 Use-Case Modeling Program Management And you need experience in using them 2008 Ivar Jacobson International 41

42 How do you become Smart? You need knowledge in good (maybe best) practices There are 100 s of practices, some of them are good Business Modeling Test-Driven Development Scrum Product-Line Engineering Risk-Driven Iterative Development Systems Engineering Aspect Orientation Robustness Analysis Retrospectives Business Process Re-Engineering Use-Case Driven Development Pair Programming PSP User Stories SOA Prince2 Use-Case Modeling Program Management And you need experience in using them 2008 Ivar Jacobson International 42

43 Agenda 1. What does Smart mean? 2. Smart Cases Recognize it when you see it 3. How do you become Smart 4. What does Smart really mean? 2008 Ivar Jacobson International 43

44 What does Smart really mean? If you didn t get what smart is so far let me summarize it to you 2008 Ivar Jacobson International 44

45 Of course, eventually it comes back to you, but We can all become smarter Ivar Jacobson International 45

46 Thank You 2008 Ivar Jacobson International 46

Be Smart! or What they don t teach you about software at school

Be Smart! or What they don t teach you about software at school Ivar Jacobson with Ian Spence, Pan Wei Ng and Kurt Bittner Our goal Good Software Better, Faster, Cheaper and Happier What it takes Happier