Executable Behavioral Modeling of System and Software Architecture Specifications to Inform Resourcing Decisions
MetadataShow full item record
The size, cost, and slow rate of change of DoD Information Technology (IT) systems in comparison with commercial IT makes introduction of a new DoD system or capability challenging. Making design decisions without consideration of the whole system and its environment may result in unintended behaviors that have operational and financial impacts, often not visible until later testing. The complexity of these system interactions isn’t cheap, impacting intellectual, programmatic, and organizational resources. Precise behavioral modeling offers a way to assess architectural design decisions prior to, during, and after implementation to mitigate the impacts of complexity, but in and of itself does not lead to estimates of the effort and the cost of those design decisions. This research introduces a methodology to extract Unadjusted Function Point (UFP) counts from architectural behavioral models utilizing a framework called Monterey Phoenix (MP), lightweight formal methods, and high level pseudocode for use in cost estimation models such as COCOMO II. Additionally, integration test estimates are informed by extracts of MP model event traces. These unambiguous, executable architecture models and their views can be inspected and revised, in order to facilitate communication with stakeholders, reduce the potential for software failure, and lower costs in implementation.
The article of record as published may be found at http://dx.doi.org/10.1016/j.procs.2016.09.292
Showing items related by title, author, creator and subject.
Langford, Gary; Huynh, Thomas V. (2007-09);In this work complexity is defined as the combination of the number and types of Value Transfer Functions (VTF) between stakeholders of a system. Increasing the number of stakeholders increases the complexity. The two ...
Dupont, Joseph P. (Monterey, California. Naval Postgraduate School, 2002-06);"We often misunderstand, ill define or improperly measure the complexity of software. Software complexity is represented by the degree of complication of a system determined by such factors as control flow, information ...
Cooling system design tool for rapid development and analysis of chilled water systems aboard U.S. Navy surface ships Sanfiorenzo, Amiel B. (Cambridge, Massachussetts, Massachussetts Institute of Technology, 2013-06);Over the last several decades, there has been a dramatic increase in the complexity and power requirements of radars and other combat systems equipment aboard naval combatants and this trend is expected to continue for ...