Skip this Video
Download Presentation
Background: Problem Statement

Loading in 2 Seconds...

play fullscreen
1 / 1

Background: Problem Statement - PowerPoint PPT Presentation

  • Uploaded on

Net-Centric Connectivity. Net. -. Centric SoS. RT-25 Net-Centric Requirements Management. University of Southern California.

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

PowerPoint Slideshow about ' Background: Problem Statement' - gabriel-barry

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





Centric SoS


Net-Centric Requirements Management

University of



Requirements Management for Net-Centric Enterprises: An Overview Doug Bodner*, Nenad Medvidovic+, Barry Boehm+, Jo Ann Lane+, Bill Rouse*, George Edwards+, Ivo Krka+, Daniel Popescu+, and Animesh Podar**Georgia Institute of Technology +University of Southern California



Background: Problem Statement

Net-Centric Eco-System

  • Net-centric enterprises engage semi-autonomous business units, each with its own goals and methods for characterizing “requirements”
  • These units often need to collaborate using common IT systems, involving integration or merging
  • Missions and unit needs evolve over time
  • Legacy systems exist and must be addressed
  • How should capabilities and requirements be managed?

Org 1

Org 2

Org n

Capabilities and requirements selection and reconciliation










Traceability analysis


Legacy Systems

Legacy Systems

Legacy Systems

Integration architecture definition and design

How to enable?

Collaborative Interoperation / Integration / Merging

Our goal: Specify a methodological framework for requirements management, identify candidate Methods, Processes and Tools (MPTs), and use case studies to aid in solution development and value articulation

Solution Approach: Methodological Framework

Problem Framework

  • Decompose high-level capabilities into software requirements, then into architectures
  • Provide support for multiple stakeholders involved in net-centric integration (conflicting needs, compartmentalized information)
  • Provide support for traceability
  • Use a spiral decision process to incrementally involve lower levels of detail and incorporate evolution of needs

Candidate Netcentric SoS Capabilities


Candidate Netcentric SoS Requirements


Candidate Netcentric SoS Architecture

Solution Details: MPTs, Case Studies and Validation

MPT Mapping

To Problems

  • Methods, Processes and Tools (generic systems/software)
  • Win-Win – MPT for negotiating and resolving multi-stakeholder conflicts regarding IT requirements
  • System-of-systems toolkit – MPTs for going from capabilities to requirements
  • Adopt-and-Go – MPT for selecting one system from among multiple
  • CBSP – MPT for deriving architecture design decisions from IT requirements
  • COSYSMO for SoS – MPT for estimating cost of software-intensive system-of-systems given size factors and cost parameters

Next step: Use case studies to adapt MPTs and integrated solution to net-centric domain

  • Regional area crisis response
  • Mergers (HP-Compaq)
  • Back-office IT integration (ISP)
  • Health IT
  • Case Study Analogy Approach
  • ∙ Apply the methodology/MPTs:
    • Identify issues/challenges
    • Determine MPT adaptations
    • Evaluate methodology
  • ∙ Expected outputs:
    • Manual/tutorial
    • Other research problems
  • Validation Goals and Approach
  • Determine capabilities and gaps with respect to managing requirements IT integration efforts in net-centric-like environments
  • Determine extent to which our methods and tools address gaps
  • Determine specific reactions and insights
    • Enterprise systems integration
    • Health IT integration
  • Surveys and interviews
    • Developed generic instrument
  • Walk-throughs and usage



  • Methodology/MPTs
    • Specified generic solution framework
    • Indentified candidate MPTs
  • Case studies and validation
    • Case studies to adapt MPTs to net-centric domain and demonstrate solution value
    • Validation with third-party systems integrators to identify gaps and independently demonstrate solution value

Doug Bodner, Tennenbaum Institute, Georgia Institute of Technology ([email protected],

Nenad Medvidovic, Center for Systems and Software Engineering, University of Southern California ([email protected],


Bodner, D. A., N. Medvidovic, W. B. Rouse, B. W. Boehm, R. A. DeMillo, G. Edwards, D. Khan, I. Krka, J. A. Lane and A. Pradhan. “RT-25: Requirements Management for Net-Centric Enterprises,” technical report SERC-2011-TR-017, Systems Engineering Research Center, Stevens Institute of Technology, 2011.