oslc rm 22 nd june 2009 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
OSLC RM 22 nd June 2009 PowerPoint Presentation
Download Presentation
OSLC RM 22 nd June 2009

Loading in 2 Seconds...

play fullscreen
1 / 17

OSLC RM 22 nd June 2009 - PowerPoint PPT Presentation


  • 128 Views
  • Uploaded on

OSLC RM 22 nd June 2009. Workgroup meeting http://open-services.net/bin/view/Main/RmHome. OSLC RM Workgroup. Introductions Objectives, approach, participation Proposal for V1.0 specification Activities beyond V1.0 Actions for next meeting. Introductions. Steve Abrams Andrew Berner

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'OSLC RM 22 nd June 2009' - aliya


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
oslc rm 22 nd june 2009

OSLC RM 22nd June 2009

Workgroup meeting

http://open-services.net/bin/view/Main/RmHome

oslc rm workgroup
OSLC RM Workgroup
  • Introductions
  • Objectives, approach, participation
  • Proposal for V1.0 specification
  • Activities beyond V1.0
  • Actions for next meeting
introductions
Introductions
  • Steve Abrams
  • Andrew Berner
  • Gary Dang
  • George DeCandio
  • Brenda Ellis
  • Rainer Ersch
  • Ian Green
  • Ken Jackson
  • Andreas Keis
  • Chris McGraw
  • S. Ren
  • David Ruiz
  • Pratik Shah
  • Dominic Tulley
  • Randy Vogel
  • Simon Wills
objectives approach
Objectives / Approach
  • Address business challenges integrating with Requirements Management tools
  • Scenarios express these challenges
    • Solicit, articulate, motivate, prioritize, review
    • Cross-workgroup awareness!
  • Service specifications express solutions
    • Define, review, approve
  • Implementations validate
    • Feedback on specification
  • Humans validate
    • Feedback on scenarios, specifications, implementations
focus
Focus
  • Time-boxed activities
    • Sensitive to business realities & pressures
  • Scoped
    • Pin-down scope appropriately
  • Pragmatic
    • Address business challenges
collaborating
Collaborating
  • Wiki is our focus
    • Scenarios, specifications, other assets
    • Work-in-progress
  • Bi-weekly calls
    • Perhaps tighter loops during certain phases
  • Agenda and minutes on the wiki
  • Face-to-face
    • Rational Software Conferences
  • Other workgroups
team roles
Team roles
  • Motivating and articulating topics
  • Authoring
  • Discussing
  • Reviewing
  • Implementing specifications, tests
  • Evolving practices
  • Update the wiki directly or contact Ian
reaching agreement
Reaching agreement
  • Ask workgroup to review wiki page(s)
  • Add comments to wiki page
    • Eg. http://open-services.net/bin/view/Main/RmCALMReviews
  • Discuss, propose changes
    • Perhaps outwith bi-weekly calls
  • Final review to agree
  • Time-boxed
content guidelines
Content Guidelines
  • Scenarios
    • Stories, use-cases, text, diagrams, etc.
  • Specifications
    • RESTful services
      • Resource-centric
      • Language neutral, stateless protocols
    • Emphasise “just enough” specification
      • We will fail to build a “model of everything”
      • Strive for loosely coupled, low-commitment information models
    • Adopt standard vocabularies
    • Notion of a representation is simple and powerful
  • Other content?
legalese
Legalese
  • Creative commons licence
  • Patent Non-assert
proposal for v1 0
Proposal for V1.0
  • Address C/ALM scenarios
    • Described on the Wiki
  • Complements published CM V1.0 spec.
  • From Rational perspective, implement in
    • Rational Requirements Composer
    • Rational DOORS
proposed main scenario for v1 0
Proposed main scenario for V1.0
  • Define a “requirement set”
    • Create change requests to implement
    • Create test plan to validate
      • Create test cases linked to each requirement
  • Implement (build, deliver) execute tests
  • Consume traceability
    • Test coverage
    • Implementation status
proposal for v1 01
Proposal for V1.0
  • Focus on creation of traceability
    • (Defer consuming traceability.)
  • Selection (identification)
    • requirements
    • requirement sets
  • Creation of requirements
  • Creation of links across lifecycle resources
    • Between requirements and requirement sets
    • Means of distinguishing between those links
proposal for v1 02
Proposal for V1.0
  • Proposed timetable for V1.0
    • Agree scope by 6th July
    • First draft of specification 10th July
    • Review and revise 10th July – 7th August
    • Enter stabilization 14th August
      • Convergence
    • Final Spec. 11th September
efforts towards v2 0
Efforts towards V2.0
  • Timescales
  • Scenarios
    • Tagging, glossaries
    • Reporting (data warehousing)
    • Systems
      • PDM & PLM scenarios
    • Requirements Change Management
    • Traceability reporting & consuming
      • “Suspicion” – change tracking etc.
      • Impact & trace analysis
      • Justification arguments
    • Modelling
      • Analysis of requirements & other information
      • Decomposition and refinement of requirements
      • Construction of justification arguments
    • Product-line engineering (feature models, variability)
draft actions from 22 june 2009
Draft: Actions from 22 June 2009
  • Next bi-weekly call 6th July
  • Finalise C/ALM scenarios by 6th July
    • Reviewers:
    • Intermediate call w/o 29th July?
  • Work on spec. draft
    • Contributor: Ian
  • Contribute & discuss V2.0 scenarios
  • Timescales for V2.0