Welcome to Telelogic’s TechConnect
at
Lucent Bell-Labs
Murray Hill, NJ
March 5, 2004
Opening Remarks
• Software Industry Challenges
• Requirements Engineering: Practices & Tools
• Software Technology Center
2
Telelogic TechConnect – Lucent Technologies
Software Industry Challenges
Costs
Up
Revenues
Down
Intervals
Shrinking
Market
Expectations
Up
Complexity
Up Stockholders : ROI
Customers: Value
Users : Functionality & Quality
Solutions that are
flexible, expansible, survivable,
sustainable, affordable and secure
3
Telelogic TechConnect – Lucent Technologies
Front-End Activities: Is This Complex or
What?
V&V
V&V
Inception
Elaboration
Construction
User Needs Assessment
Vision Statement
Context Diagram
Problem Statement
Levels of Requirements Specs
User Profiles
User Req. Spec.
Use Cases
Scenarios
Detailed Scenarios
NF(Archit.)R/POTR
User Task Flows
MW Class Diagrams
Process/Data Flows
V. Prototypes
PLA
Product Arch.
Class Models
Verification
Story Boards
Analysis
H. Prototypes
Verification
State Models
Design Scenarios
Requirements
Operational Profiles
UI Design
Component Model
Architecture & Design
Verification
Implement.
Verification
Test/rev., execution Test
Implementations
Time
4
Test Case Skeletons
Test Cases
Usability Testing
Telelogic TechConnect – Lucent Technologies
Doing the Right Things Right
 Doing the right thing right
– Agreement on goals and targets
– Risk management
– Early defect prevention and reduction
– Elimination of gaps and redundancies
 Throughout software engineering lifecycle
– Start in front end
– Addressed in all phases
 With inter-related, right weight processes and tools
– Repeatable
– Measured
– Adaptive
– Iterative
5
Telelogic TechConnect – Lucent Technologies
Requirements Engineering & DOORS
•
•
•
Effectively generating High Quality Requirements:
correct
• modifiable
• non-ambiguous
consistent
• traceable
• understandable
complete
• verifiable
• annotated
Requirements Engineering
Requirements Development
Requirements Management
Elicitation
Change Control
Analysis
Version Control
Modeling & Specification
Tracing & Impact Analysis
Verification & Validation
Status Tracking
Best Practices, Methods,Tools and Processes for Requirements Engineering
6
Telelogic TechConnect – Lucent Technologies
The Best Practices Effect: Early Defect
Prevention & Reduction
Rate of Discovery
Current
Proposed
Requirements
7
Defect
Prevention
& Reduction
Design &
Build
Release
to Test
TIME
Telelogic TechConnect – Lucent Technologies
Source*: Boehm, Barry.
Software
Engineering
Economics.
Englewood Cliffs,
NJ: Prentice-Hall,
Inc. 1981.
Boehm, Basili.
“Software
Management.” IEEE
Computer, January
2001.
Release
to Field
STC Domains of Expertise
Architecture
Requirements
Integrated
Information
Solutions
Realization
Software
Configuration
Mgmt
8
Human
Factors
Testing
Telelogic TechConnect – Lucent Technologies
DOORS @ Lucent:
Experiences, Extensions, Integration Efforts
Vassilka Kirova ( kirova@lucent.com )
Darshak Kothari ( dkothari@lucent.com )
March 5, 2004
DOORS@Lucent: Overview
• Areas of application
• Key Projects
– Artifact Flow Through
– Virtual Requirements & Architecture Documents (VRAD)
– Architectures & DOORS
•
•
10
Next Step
Q&A
Telelogic TechConnect – Lucent Technologies
Areas of Application
Requirements
Capture &
Engineering
Architect
ure
Specifica
tion
Modeling
Tools
Simulation
Tools
Coding
Tools
Requirements Management & Traceability Tools
Documentation Tools
Project Management Tools
Configuration/Change Management Tools
Metrics Tools
11
Telelogic TechConnect – Lucent Technologies
Testing &
Test
Mgmt
Key Projects: Artifact Flow Through
•
Goal
– Increase product quality and team efficiency/productivity
– Decrease development cycle time
•
Constraints
–
–
–
–
•
No impact on schedules
Compliance with Mobility process
Compliance with TL 9000 requirements
Use of Mobility/Lucent standard tools
Work Model:
– Collaboration & Co-ownership between STC and PacketIN
– Continuous Improvement with Clear Targets
– Focus on Technical Excellence
12
Telelogic TechConnect – Lucent Technologies
What is Artifact Flow Through?
• A Modular, Integrated Method, Tool
and Process Environment for:
– Specification, modeling, generation and
management of software “artifacts” –
requirements, designs, and test work
items
– Process improvement supporting
collaboration, elimination of functional
smokestacks, and more iterative
development
• Leverages best software practices
– Use case –driven, scenario-based
development
– Model-based design
– Early testing paradigm
• Data-driven approach
– Metrics definition and automation
– Benchmarking data & monitoring
– Data collection, analysis and ongoingimprovement
13
PacketIN Environment
Design to Req. Traceability
Extended
Developer
Support
ROSE
Extended
System
Engineering
Support
Jumpstart Rose Model
Generate Test Cases
DOORS
Test Management
Tester
Activities
Req. to Test Traceability
APX-TMS
Example: PacketIN Targets
Success Criteria
Target
(per release)
Reduction in Effort (THCM)
13%-20%
Reduction in defects (end customer)
20%
Increase in multi-use of artifacts
10%
Increase in degree of automation
30%
Telelogic TechConnect – Lucent Technologies
AFT: Benefits
AFT Increases quality
and productivity while
reducing the cycle time
via:
– Common – scenario-based representation throughout
development cycle
– Smooth “handoffs” of
artifacts – “artifact flow” –
with no-rework
– Maximum reuse of
knowledge and artifacts
– Maximum automation –
generation of test cases,
design jumpstart, metrics
– Automated Traceability
14
PacketIN Projected Gain
Cumulative ROI
2,000,000
Cumulative
Savings
1,500,000
Cumulative $
•
1,000,000
Cumulative
Cost
Estimate
Cumulative
ROI
500,000
0
Sept '02
Sept '03
Sept '04
(500,000)
Time
Projected ROI
$200-500K in the first year
$1-2M in each subsequent year
Distribution of savings:
– Reduction in field defects accounts for
35% of the expected savings
– Effort reduction accounts for 65% of the
expected savings
Telelogic TechConnect – Lucent Technologies
AFT: Key Components & Features
Rose - based Design
CM (CCMS) for Rose Models
Design to UT Traceability
Design to Req. Traceability
SRD support in DOORS
Extended DOORS Infrastructure
XML Generation
Use Case Syntax Check
Metrics & Reports
SE Activities
Developer
Activities
XML
Representation
of
Requirements
DOORS
ROSE
Rose Model
Jumpstart
Test Case
Generation
Test Management
Requirements to Test Traceability
15
Tester
Activities
Telelogic TechConnect – Lucent Technologies
APX-TMS
End-to-End Workflow: “Flowthrough”
Create SRD
UCs, POTR
Import DXL
•Generate for review,
send notification
•Generate baselined
version, send notification
Generate
MS Doc & XML
DXL Scripts
DOORS
SE
“Hand-off”
COMPAS
XML File
Jumpstart
Rose Model
MS Word File
Generate &
Store
Test Case
Developer
Create
Design Models
INTA
Manage
Test Cases
ROSE
Rose Model
“Hand-off”
CCMS
Publ. Model
“Hand-off”
WEB
Design Document - COMPAS
16
Telelogic TechConnect – Lucent Technologies
“Hand-off”
COMPAS
Tester
TMS
Better Requirements and Product Quality
through Use Cases (UC)
•
Characteristics and Benefits
– UCs capture a contract between the
stakeholders of a system about its
behavior
Industry data:
•
Use cases improved developer
productivity by 40%
(DaimlerChrysler)
– UCs specify system’s behavior
under various conditions (success &
failure modes) in a way that is
concise and easy to understand,
track, and validate
•
35% increase in developer
productivity at Merrill Lynch
achieved through: Tool-based
Requirements Management
and Use cases
– UCs are collections of scenarios;
scenarios provide context –
traditional requirements are often
too ambiguous
– UCs are a key to the creation/
generation of quality test cases and
system verification
17
Telelogic TechConnect – Lucent Technologies
End to End Workflow: Traceability
FTF 004
Querying
TMS
Data
Generate XML:
UC, POTR, Links
Auto-Generate
DOORS-TMS
Links
DXL
DOORS
SE
Generate/
Update Surrog.
Module
XML File
TMS Data File
Populate ReqLink
Property, ReqList
Package
Developer
Models
Annotated with Req.;
Run a Report
Tester
ROSE
Models
Annotated with Tests;
Run a Report
TMS Query
Support
Traceability Report
18
Telelogic TechConnect – Lucent Technologies
TMS
Innovate the Way The Team Works
Together: Process Flow for High Quality …
Requirements written in
DOORS
Delivered to tester (and
developers) early
Early Comments
to SE
Initial run through INTA
19
Telelogic TechConnect – Lucent Technologies
High
Quality
Review
AFT Software Innovation
Integrated Best Practices, Processes & Tools
System Engineering
Design
Test
(Extending DOORS)
(Augmenting Rose)
(Augmenting TMS)
• Support for Use Cases in
DOORS
– Structured template
– Syntax Checker
• XML representation of
requirements for
downstream tools
• Test coverage reports
(traceability support)
• Metrics Reports
• Test cases generation
• Design model jumpstart
from requirements
tool – use case view and
– Optimized coverage
UML sequence diagrams
– Choice of algorithms
• Design-to-unit test
traceability support
• Tool-based requirements
traceability
• Design to requirements
– Gaps & coverage
traceability tool and
– Change notification
reports
– Impact analysis
• Guidelines for legacy code
– Test reuse
reengineering
Adds functionality to standard Mobility tools
Provides “Glue” Software
Scalable integration architecture
20
Telelogic TechConnect – Lucent Technologies
Key Projects: VRAD
•
What are VRADs?
– “Books” of project/feature/component specific requirements,
architecture and any other supporting information
•
Means for:
– Need-based content definition
– Flexible, automated, on demand document generation
• Benefits:
– Reuse of artifacts
– Avoiding information overload
– IP protection
21
Telelogic TechConnect – Lucent Technologies
VRAD Use Cases
DOORS
Prepare
Source Doc.
Source Doc. Owner
Author
Instantiate
VRAD Template
Configure
VRAD
VRAD Owner
VRAD
Tool
Generate
DOORS VRAD
Publish
Combined VRAD
Legend:
Manual
TOOL-based
Doc Controller
22
Telelogic TechConnect – Lucent Technologies
VRAD Generation Tool Workflow Illustrated
Configure VRAD
VRAD GUI
SAE VRAD
VRAD
Versions (PDF)
Publish
DOORS
VRAD
Publis
h
Combi
ned
Generate
Generate
VARD
VRAD
VRAD
Note: VRAD contains
information from DOORS
documents (SAE artifacts)
as well as other external
documents
DOORS
Tagged
Source Documents
23
DOORS VRAD
Template
Other
Source Documents
Telelogic TechConnect – Lucent Technologies
Key Projects: Architecture & DOORS
• What is an architecture specification?
 Meta-model: views, components, interfaces, constraints, etc.
• What are the current architecture specification/representation
practices in Lucent?
 Structured documents, informal diagrams …
• What are the current architecture representation practices
elsewhere? What are the best practices?
 From informal text to ADLs
• What are the current expectations/experience of architecture specs
users? What is the expected final product?
 Documents ….
• What is the evolution path?
 Structured documents & informal “block-&-line” diagrams -> structured
textual specifications based on underlying “meta-model” & rigorous
models (e.g., UML diagrams) -> formal models or partial formal models
& constraints & textual annotations
• Is DOORS a step forward?
24
Telelogic TechConnect – Lucent Technologies
DOORS: Underlying architecture and
usage model
•
DOORS is an object-based module/document-centric
management system which supports:
– Storing and viewing information objects in context
– Linking and traceability
– Tracking changes
– Editing and baselining
•
DOORS is not:
– A relational data-base
– A modeling tool
25
Telelogic TechConnect – Lucent Technologies
Benefits & Drawbacks of moving to
DOORS
•
Benefits
– Viewing the architecture information in context; easy navigation
between different architecture specs as well as between
architecture and requirements artifacts
– Traceability between information objects at selected level of
granularity, e.g., requirements to an interface
– Tracking changes and impact analysis
– Structuring/Restructuring the architecture specification artifacts
according to a common model – an opportunity for streamlining
the specs
– Step toward a “model-text” specification approach
•
Drawbacks
– A somewhat clumsy editing
– Performance issues
– Learning curve
26
Telelogic TechConnect – Lucent Technologies
Representation Model
•
Views
– Structural View
• Component, Interfaces, Connectors (and configurations)
– Behavioral View
• State models, scenarios, etc.
– Quality View
• Reliability, Performance, Maintainability, etc.
– Deployment View
• Hardware configurations, software allocation to machines,
etc.
•
27
Rational, constraints & annotations
Telelogic TechConnect – Lucent Technologies
Representation Model – The Structural
View
•
Key Structural Elements
Interface (of A)
System (e.g., A)
Connector
Component
(e. g. A2)
Component
(e. g. A1)
Component decompositions
(alternatives)
Black-box
Component
Component
Interface (ports)
White-box
Component
28
Systems (subsystemarchitectures)
Telelogic TechConnect – Lucent Technologies
Some Issues that Need Further Attention
29
•
•
Printing should allow to print line numbers
•
Export to Word sometimes does not copy certain OLE
objects and does not finish cleanly.
•
Printing in book format over runs in to margins and
looses some text if it does not fit in the margins.
Specifically for text in the attributes.
•
Need to have “diff-marking” functionality.
Saving a view does not allow to inherit access rights
from module.
Telelogic TechConnect – Lucent Technologies
Next steps
Requirements
Capture &
Engineering
Architect
ure
Specifica
tion
Modeling
Tools
Simulation
Tools
Coding
Tools
Requirements Management & Traceability Tools
Documentation Tools
Project Management Tools
Configuration/Change Management Tools
Metrics Tools
30
Telelogic TechConnect – Lucent Technologies
Testing &
Test
Mgmt
Acknowledgments
•
31
The work presented here has been done in
collaboration with Mobility SAE organization and
PacketIN SE department
Telelogic TechConnect – Lucent Technologies
32
Telelogic TechConnect – Lucent Technologies