TANGO Requirements Definition in a multi-national, multi-cultural development environment

Transcription

1 TANGO Requirements Definition in a multi-national, multi-cultural development environment Alexander-Marc Merten Schenker AG, Project TANGO Essen, 27-Feb-2012

2 Requirements Based Software Development Not so good Requirements Management Looks like they misunderstood something about that latest biotech quotation 2

3 Requirements Based Software Development Not so good either Damn Higgins! I said chicken laying colored eggs. Five years of research down the drain! 3

4 Agenda What is TANGO? Requirements Definition in TANGO The Real World Summary 4

6 What is TANGO? Mission Statement To find and implement a standardized new operational software for all worldwide air and ocean freight operations. This new software should be of benefit to all country organizations worldwide. Significant business partners have to be included. The company strategy of Schenker AG (to be an Integrated Network Logistics Provider ) has to be strictly complied with. 6

7 What is TANGO? Four major projects to consolidate the IT landscape Variety of Systems in Use world-wide (as-is and to-be) Current Situation Land Transport Air & Ocean Planned Situation Land Transport Air & Ocean FASS TANGO MyMistral STAR 7

8 What is TANGO? Replace Local Systems by one Global Solution Initial Situation 2001 a team of 76 country (business) representatives created one common globally valid workflow OPS OPS OPS OPS More than 32 different IT systems for air and ocean freight By different vendors, Under national or regional control (Development, Support, ), Which implement different, evolved, local processes. Every adaptation creates multiple effort and further diversification of systems and processes. Change This workflow will be implemented by one team in one system for world-wide use 8

9 What is TANGO? Transport Application for Air and Ocean Freight Network and Global Operations is the Core Project for Air & Ocean Customer Services For all worldwide air/ocean operations with one common process > 100 countries, > concurrent users > 10,000 shipments / hour > 6 Billion Euro turnover (~20% of overall DB turnover (pre-arriva)) Rail Road Production & Network Air & Ocean Logistics Special Fairs & Exhibition s, Projects, Sport Events, Portal & Reporting Deployment in five functional increments Currently ~4,200 users in 93 countries on selected functional modules One central system, software and database instance State-of-the-art IT architecture and software Replaces >32 local/legacy systems TANGO Resources: Decision Support, Communication, Resources Management / Administration, Technology / Assets, Methods / Procedures / Services Allows global control over the entire transport chain and unlimited, realtime data transparency 9

10 What is TANGO? TANGO Main Objectives Operational Integration & Standardization Business Transparency & Governance Technical Modernization Enterprise-wide process consolidation : Harmonized Workflow Standardized, synchronized, automated execution of processes Single database concept for master and operational data Still: Consideration of event and customer process scenarios Transparency of customers, partners and authorities regarding Central System (instead of >32 installations ) Standardized Interfaces / Integration Architecture State-of-the-Art-Technology (Java, Oracle Database, Service oriented, ) 10

11 What is TANGO? Global Harmonized Workflow Preparatory work in pre-project phase (until mid 2005) Definition of workflows per traffic and region Mapping of regional workflows Creation of one globally harmonized air and ocean workflow Review of current situation (problems, gaps) 11

12 What is TANGO? Global Harmonized Workflow The global harmonized Workflow (Top-Level) Receipt of request for quotation Analysis of request and response Acceptance of quotation Selection of shipments for consolidation; Preparation of load plans; Stock Control; Carrier selection/carrier booking; Container/ULD Loading; Issuing of manifest and Master B/Ls /AWBs; Reconciliation/profit sharing; Tracking Arrival Notification; Pick up and unloading of containers/ulds; Discrepancy check; Turn over of cargo/documents to third-party brokers; Tracking Determination of shipment type; Carrier selection; Booking request; Booking confirmation; Tracking Determination of delivery method/delivery Stock control; Tracking RFQ Shipment creation Carrier Booking Pre- Carriage Consolidation Load Planning International transport De-Consolidation/ Importation Customs Clearance On- Carriage Job File creation; Credit check; Compliance check; Tracking Issuing of shipping documents; Invoicing/cost control; Tracking Determination of delivery method; Pick up order/delivery instructions /stock control Export customs clearance; Labeling; Cross docking /discrepancy handling; Tracking Processing customs entry; Invoicing/cost control; Tracking 12

13 What is TANGO? Increments and Top-Level Schedule Increment Capabilities Productive Air 1 Air Import Import Export Ocean RCM Pilot Jun a Ocean Import Import Export Air Ocean RCM Dec b Ocean Tariffs Import Export Air Ocean RCM May Ocean Export Import Export Air Ocean RCM Nov Air Export Import Export Air Ocean RCM Mid

14 What is TANGO? Parallel Development in Incremental Environment (Example Timeline) Q Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Sub-Project Requirements Definition Increment 3 (Ocean Export) Increment 4 (Air Export) Support of Sub-Projects System Spec., System Int., ACT, Rollout System Specification Capgemini System Integration Increment 3 Increment 4 Software Engineering CON REA INT CON REA INT Acceptance Test ACT Prep. ACT Exec. ACT Prep. ACT Exec. Deployment Requirements & System Definition Development & Integration Test Acceptance Test Deployment and Training 14

15 What is TANGO? Clear Interfaces and Transition of Responsibility between Partners REQDEF DESIGN CODE INT ACT OPS DEPLOY SUPPORT Requirements Analysis and Definition System Design and Specification (UML) Software Coding and Module Test Integration & System Test Acceptance Test (technical) (functional) IT Operations Deployment to target country DB-Systel Release / Incident / Problem Mgmt. Requirements Software Design & Code Test Ware Released System Java Release Mgmt. ~ 3 Mio. LOC DOORS Test Cases KM-Pool ~ 1,600 artifacts ~ 121,000 objects ~ 46,000 links ~ 23,000 pages ~ 750 Change Proposals ~ 3, Release installations (~ 3/week) 682 Configuration changes 15

17 Requirements Based Software Development Purpose of TANGO Requirements Management A textual requirement explains what the TANGO system is expected to fulfill. What we require What we get We test and verify the software against our requirements 17

18 Requirements Based Software Development Purpose of TANGO Requirements Management What is the purpose of the requirements we define? Requirements tell Software Engineers what demands their solution must fulfill Requirements tell any stakeholder of our organization what to expect of the TANGO software With requirements our testers can verify that the solution satisfies what is demanded Requirements allow the project to calculate cost and effort 18

19 Requirements Based Software Development Requirements: A common basis for the whole project Requirements are written in a technical and straight forward language to be as precise as possible We define what we require using our language in a restricted and formalized way Software Engineers build the TANGO system on the basis of our requirements Business IT Natural language Textual description of requirements Programming language 19

20 Requirements Based Software Development Requirements: A common basis for the whole project Which project stakeholders read requirements? a Business Analyst a Software Engineer a Tester a Trainer a Business Process Owner an External Auditor 20

21 Requirements Based Software Development Requirements: Two layers of requirements Business Requirements Business Flows Business Cases Describes Business Needs IsDerivedFrom System Behavior Dialog appearance Describes the System System Requirements 21

22 Requirements Based Software Development The Business Requirements Level The global harmonized Workflow (Top-Level) Receipt of request for quotation Analysis of request and response Acceptance of quotation Selection of shipments for consolidation; Preparation of load plans; Stock Control; Carrier selection/carrier booking; Container/ULD Loading; Issuing of manifest and Master B/Ls /AWBs; Reconciliation/profit sharing; Tracking Arrival Notification; Pick up and unloading of containers/ulds; Discrepancy check; Turn over of cargo/documents to third-party brokers; Tracking Determination of shipment type; Carrier selection; Booking request; Booking confirmation; Tracking Determination of delivery method/delivery Stock control; Tracking RFQ Shipment creation Carrier Booking Pre- Carriage Consolidation Load Planning International transport De-Consolidation/ Importation Customs Clearance On- Carriage Job File creation; Credit check; Compliance check; Tracking Issuing of shipping documents; Invoicing/cost control; Tracking Determination of delivery method; Pick up order/delivery instructions /stock control Export customs clearance; Labeling; Cross docking /discrepancy handling; Tracking Processing customs entry; Invoicing/cost control; Tracking 22

23 Requirements Based Software Development The System Requirements Level (Simplified Version) Outputs Triggers Business Actors execute PassesDataTo Application Functions CRUDs Dialogs Utilize Use Cases CRUDs Information Objects CRUDs Background Services Triggers / ProcessesDataOf Reference Books Interfaces Third Parties 23

24 Requirements Based Software Development The System Requirements Level A Spiderweb of Relationships 24

25 Requirements Based Software Development Artifact Types An overview List of Artifact Types we use in DOORS Business Process Use Case Application Function Output Dialog Interface Information Object Background Service Operational workflow from a business perspective User system interaction to achieve a result in operations Reusable business logic shared by many Use Cases Description of a paper document Conceptual layout and dynamic properties of a screen Data exchange between TANGO and other Applications Entity in the business with a group of attributes Scheduled batch job in the TANGO system 25

26 Requirements Based Software Development Artifact Types Reference Books Reference Books Reference Books are central Artifacts of the requirements repository Their contents are shared throughout the entire Functional Requirements Artifact Types like Use Cases and Dialogs refer to Reference Book contents 26

28 A Real World Example Interactions with the System The Use Case Requirements Definition for Maintaining Geographical Location (TANGO system against Use Case Artifact) The Use Case Artifact explains what happens in the TANGO system. In this case it is a simple update of Geographical Location Singapore 28

29 A Real World Example Entering and saving Data The Information Objects Requirements Definition for Maintaining Geographical Location (TANGO system against Information Object Artifact) The Information Object Artifact lists all attributes the TANGO system stores with a Geographical Location 29

30 A Real World Example Interactions with the System The Dialogs (1) Requirements Definition for Maintaining Geographical Location (TANGO system against Dialog Artifacts) TANGO Dialog definition has 4 Artifacts: a General Dialog Artifact (DL_LOC.MNT.01) and 3 Dialog Screen Artifacts (DL_LOC.MNT.01-S1/2/3) which correspond to the 3 tabs you see in the TANGO application (General, Sea-/Airports, Local Agents) 30

31 A Real World Example Interactions with the System The Dialogs (2) Requirements Definition for Maintaining Geographical Location (TANGO system against Dialog Artifacts) A Dialog Screen Artifact defines the fields on the TANGO User Interface 31

32 A Real World Example Interactions with the System The Dialogs (3) Requirements Definition for Maintaining Geographical Location (TANGO system against Dialog Artifacts) The Label UN Location Code is also registered in the Label Glossary 32

34 Take-Away Points Requirements Definition in globally distributed teams for multinational software Methods Processes Tools People Modelling is a good way to standardize requirements definition over many teams and locations Highly domain specific applications require in-depth requirements definition Using templates facilitates working Global harmonized workflow is the important basis for any multi-national software Req. Def. Guideline to streamline global req. def. teams On-Site Customer Workshops for requirements elicitation provide valuable customer specific requirements Professional database-oriented requirements tool essential for globally distributed teams Beware of overly complex linking schemas Bring testers in early Training in requirements definition methods not only for requirements oriented roles (e.g. deployment) 34

35 ???? Thanks!? Any questions? Alexander Merten Schenker AG Project TANGO Requirements Management Specialist Alfredstrasse Essen / Germany Phone +49 (0) 201 / Fax +49 (0) 201 / alexander.merten@dbschenker.com 35