Requirements used consistently in combination with agile development (SCRUM) and SOA

Size: px

Start display at page:

Download "Requirements used consistently in combination with agile development (SCRUM) and SOA"

Suzan Gray
10 years ago
Views:

1 Requirements used consistently in combination with agile development (SCRUM) and SOA Date: March 10th, 2009 Produced by: Heinz Ehrsam (KSXF 51), Ralf Fahney (KSDG 233)

2 Credit Suisse is the second largest Swiss bank, and is dependent on an efficient IT The Credit Suisse Group is a modern descendent from the Schweizerische Kreditanstalt founded 1856 Banking business divides into Investment Banking, Privat Banking and Asset Management 19 application domains, which subdivide into closely related applications more than 1'200 different applications 32 million lines of code PL1 11 million lines of code Java Over 20 million processed securities transactions per year Date: Slide 2

Management 19 application domains, which subdivide into closely related applications more than 1'200 different applications 32

3 Securities operations platform must be fit for the future Starting position: 30 year old application landscape, based on PL/1 Lack of documentation for current applications Lack of PL/1 knowledge in the future Objectives: more flexibility for business by changes Service Oriented Architecture (SOA) Transaction process on Java platform Trend to standard software Coexistence to the current legacy Date: Slide 3

future Objectives: more flexibility for business by changes Service Oriented Architecture (SOA)

4 New technologies require new methodological approach Business process management (BPM) Service Oriented Architecture (SOA) Business process modeling including use case descriptions Business process model transformation into process engine Centralized Business rules engine Event Driven Process Chain (EPC) Unified Modeling Language (UML) Agile project methodology (SCRUM) Date: Slide 4

process model transformation into process engine Centralized Business rules engine Event Driven

5 Key Topics "SOA Framework" 3Request / 1 Tool Chain 5 Requirement - Management Business Process Mgt: architecture, component, activity, processes IT-Service A IT-Service B IT-Service C 2 Interaction Process Orchestration Business Rules Testing 4 1. Business Process Management for executable process models by the integrated IT-transformation 2 2. Structured IT-architecture for more agility 2 and flexibility with autonomous IT-Services, central process orchestration and central managed Business Rules 3. Request- and Requirement Management for transparent release planning and view definitions per stakeholder 4. Test environment and automatic test applications for faster and continuous integration 5. Integrated SW development Tool Chain for improve efficiency and quality of STAR rollout Date: Slide 5

Structured IT-architecture for more agility 2 and flexibility with autonomous IT-Services, central process orchestration and central managed Business Rules 3.

6 BPM/SOA and RE&M: Different perspectives to system development Request - / Tool Chain Requirement - Management Business Process Mgt: architecture, component, activity, processes IT-Service A IT-Service B IT-Service C Testing Interaction Process Orchestration Business Rules Date: Slide 6

component, activity, processes IT-Service A IT-Service B IT-Service C

7 BPM/SOA perspective: Solution-oriented Meta model terms Feature Requirement Approval Acceptance Business Process Data (e.g. Business Object) Services Rules System Specification Design Specification CIM PIM PSM Date: Slide 7

8 RE&M perspective: Requirements-oriented Meta model terms Feature Requirement Approval Acceptance Business Process Data (e.g. Business Object) Services Rules System Specification Design Specification CIM PIM PSM Date: Slide 8

9 So the question is: How to bridge the gap? Date: Slide 9

10 Step 1 Align Vee-Model levels of abstraction "Trace To" User Business Request Requirements User Level Business Request Integration Level Integration 1st Business approval System CIM Specification System Level CIM Level Integration "Build To" PSM Specification "Design Level PIM To" Level Integration "Build Level PSMTo" Level Integration Implementation eg rat ion A c, Ve ce r p ta i fi c a ti o nc n, e "Design To" PIM Specification Int, t io n osi mp eco l,d va tion ppro fini A De 2nd Business approval Date: Slide 10

"Design Level PIM To" Level Integration "Build Level PSMTo" Level Integration Implementation eg rat ion A c, Ve ce r p ta i fi c a

11 Step 2 Introduce "Approval" into BPM/SOA perspective Level of Abstraction Deliverable Business Categories Processes Data Services Business Rules Business Request 1st Business approval Computation Independent Model (CIM) 2nd Business approval Platform Independent Model (PIM) Platform Specific Model (PSM) Implementation Date: Slide 11

Business approval Computation Independent Model (CIM) 2nd Business approval Platform

12 R eq uire men ts, A cce ptan ce Levels of Abstraction Step 3 Make 3D perspective out of both 2D perspectives ve i l e D C e l b ra a es i r o te g Date: Slide 12

13 R eq uire men ts, A cce ptan ce Levels of Abstraction CIM level example ve i l e D C e l b ra a es i r o te g Date: Slide 13

14 CIM level example Requirement REQ142: 'Process Registered Share Delivery Order' business process must include to create customer documents Deliverable Process Registered Share Delivery Order Date: Slide 14

must include to create customer documents Deliverable

15 R eq uire men ts, A cce ptan ce Levels of Abstraction PIM level example ve i l e D C e l b ra a es i r o te g Date: Slide 15

16 PIM level example Requirement Deliverable derived from Create customer documents (purchase) function solution design REQ235: System must create customer documents as per customer document types list determined from customer delivery instructions Date: Slide 16

System must create customer documents as per customer document

17 R eq uire men ts, A cce ptan ce Levels of Abstraction PSM level example ve i l e D C e l b ra a es i r o te g Date: Slide 17

PSM level example Requirements Deliverable Create customer documents (purchase) event-driven process chain REQ326: System must use ALBPM as process engine REQ327: Project must use XPDL to transform

18 PSM level example Requirements Deliverable Create customer documents (purchase) event-driven process chain REQ326: System must use ALBPM as process engine REQ327: Project must use XPDL to transform event-driven process chain to ALBPM internal process representation REQ328: Project must consider mismatch between ARIS and ALBPM XPDL interpretation ARIS XPDL ALBPM = A business process modeling tool = A business process model exchange standard = A business process engine Date: Slide 18

process representation REQ328: Project must consider mismatch between ARIS and ALBPM XPDL interpretation ARIS XPDL ALBPM = A

19 ... and everything's fine again almost... Date: Slide 19

20 2nd Business approval must include PIM aspects 1st Business approval CIM 'Business-View' PIM 2nd Business approval RE&M / Sol.Eng. PSM Sol.Eng. Date: Slide 20

21 2nd Business approval must include PIM aspects 1st Business approval CIM 'Business-View' PIM 2nd Business approval RE&M / Sol.Eng. PSM Sol.Eng. Date: Slide 21

22 Models are complete Requirements are documented incompletely 1st Business approval CIM % Requirement Storage = % Explicitly documented requirements 5 20 % 'Business-View' PIM 2nd Business approval RE&M / Sol.Eng. PSM Sol.Eng. Date: Slide 22

23 Models are complete Requirements are documented incompletely Undocumented Undocumented requirements requirements % Requirement Storage = % Explicitly documented requirements 5 20 % 1st Business approval % % CIM 'Business-View' PIM 2nd Business approval RE&M / Sol.Eng. PSM Sol.Eng % Date: Slide 23

models Define the policy modulation Culture Changes Daily communication with all roles (daily

24 Lessons Learned Tools are not yet mature Early prototypes of the development process and with the solution Waterfall model is not applicable Textual description requirement, compared with models Define the policy modulation Culture Changes Daily communication with all roles (daily SCRUM-Meetings) Continuous process improvement Training, Training, Training Date: Slide 24

25 Thank you for your attention. Do you have questions?

26 References CIM, PIM, PSM Joaquin Miller, Jishnu Mukerji, "MDA Guide Version 1.0.1", 2003, Vee Model Kevin Forsberg, Harold Mooz, The Relationship of System Engineering to the Project Cycle, presented at the joint conference sponsored by: National Council On Systems Engineering (NCOSE) and American Society for Engineering Management (ASEM), Chattanooga, TN, October 1991, 20to%20Proj%20Cycle.pdf Date: Slide 26

Open Source egovernment Reference Architecture Osera.modeldriven.org. Copyright 2006 Data Access Technologies, Inc. Slide 1

Open Source egovernment Reference Architecture Osera.modeldriven.org Slide 1 Caveat OsEra and the Semantic Core is work in progress, not a ready to use capability Slide 2 OsEra What we will cover OsEra