Sign In
Content Type

All

DAU Acquipedia

 

 

Agile Software Development2885281/21/2023 11:47:55 PMSoftware practices are simply techniques, guidelines or rules that are used to develop the software All this results in refinement and completion of the overall software https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClassD7568BC5D6DB4D91A67198E3450EF123">End user(s) team with developers in order to make instant decisions on user functionality. High level requirements are initially prioritized and developed quickly by small teams in order to get a working product quickly to the customer. Multiple, rapidly executed Increments are developed and capabilities are released to the customer as soon as possible. Prototypes may be used as a starting place and utilize a modular, open-systems approach. Agile methods are typically used for small, low risk projects.</div>
Integrated Product Support (IPS) Elements - Overview2881162/2/2023 4:41:07 PMand product support, plus major systems, sub systems, components, and embedded software and support mission critical information technology systems hardware/software systems https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClass9A446CDC3837474FB421D0C084502EB1"><div class="ExternalClass53E2CD9450BD4625B2374A0947079F7C" style="padding-left&#58;10px;">Product support is scoped by the IPS Elements, which provide a structured and integrated framework for managing product support. They are considered during the development of the Product Support Strategy (PSS) and continuously assessed throughout a system's life cycle and include&#58; · Product Support Management · Design Interface · Sustaining Engineering · Supply Support · Maintenance Planning and Management · Packaging, Handling, Storage and Transportation (PHS&amp;T) · Technical Data (TD) · Support Equipment · Training and Training Support · Manpower and Personnel · Facilities and Infrastructure ·Information Technology (IT) Systems Continuous Support</div></div>
Configuration Management (CM)28880711/29/2022 3:36:37 PMManagement in Systems and Software Engineering (Fee Required) IEEE-1012-2012 - IEEE Standard for System and Software Verification https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClassE89EE4227C0F4415AF19F0C3984911A3">A management process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design and operational information throughout its life.</div>
Engineering Change Proposals (ECP)28780611/29/2022 3:34:38 PMManagement in Systems and Software Engineering (Fee Required) IEEE-1042-1987 - IEEE Guide to Software Configuration Management (Fee Required) ISO https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClassD8A8BBCAC6744054BFB1E2562092EF93">The documentation by which a proposed engineering change is submitted to the responsible authority recommending that a change to an original item of equipment be considered, and the design or engineering change be incorporated into the article to modify, add to, delete, or supersede original parts.</div>
Life Cycle Sustainment Plan (LCSP)28783911/29/2022 3:35:29 PMLife Cycle Sustainment Plan (LCSP) Outline Website DoD Product Support Guidebooks & Manuals Defense Acquisition Guidebook (Chapter 4) DoD Product Support Manager (PSM https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClassEDF3B3880AD4414A8A83AA3B2FBB2C53"><div class="ExternalClass0B4699B42F6A4C628974E85376AF7CC1"><div class="ExternalClass99455B96C0FC441F9C6C3DA4ECCBEA33" style="padding-left&#58;10px;"><p>The detailed product support plan, including sustainment metrics, risks, costs, and analyses used to deliver the performance-based best value strategy covering the Integrated Product Support (IPS) elements.</p></div></div></div>
Software Life Cycle Management1969911/29/2022 10:15:26 PMThe acquisition of software applications (other than Defense Business Systems) and embedded software should follow the Software Acquisition Pathway, which begins in the https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClass9CC8A187E7E44E97BABFDBC72EABFA54"><div><div class="ExternalClass871BEE55FDB345B098906D09CE5B5144"><div><div><div><div><div class="ExternalClass4A59AEF80B7D48D095189FD7445DAD8F"><div><div><div><div><div><div><div><div><div><div><div><div><div><br></div><br><i>software development plan</i><br><div class="ExternalClass04DFD31FC4A546639367155F5821D0CA" style="padding-left&#58;10px;">A management plan usually generated by the developer outlining the software development and integration efforts.</div></div><br><i>software engineering/development approaches</i><br><div class="ExternalClass0DB957213101462687F11C09C86A30E5" style="padding-left&#58;10px;">Also referred to as software development paradigms, these are process models for how the various tasks related to software development can be organized. Typical approaches or paradigms encountered in DoD software development include waterfall, incremental, spiral, and Agile.</div></div><br></div><br><i>software maintainability</i><br><div class="ExternalClass52B57B222CD04BF6A80216AEFC4876B4" style="padding-left&#58;10px;">The ease with which a software system, or component, can be modified to correct faults, or improve performance or other attributes.</div></div><br><i>software reliability</i><br><div class="ExternalClassD504E316E9364605B2780BAD04764957" style="padding-left&#58;10px;">The probability that software will not cause a failure of a system for a specified time under specified conditions. This probability is a function of the inputs to and use of the system as well as a function of the existence of faults in the software. The inputs to the system determine whether existing faults, if any, are encountered.</div></div><br><i>software support</i><br><div class="ExternalClass3350623F6C9443078058E42C0CF9A539" style="padding-left&#58;10px;">The sum of all activities that take place to ensure that implemented and fielded software continues to fully support the operational mission of the system.</div></div><br><i>lifecycle management</i><br><div class="ExternalClassBD80FB39767F4724A9F8E6306D718727" style="padding-left&#58;10px;">The implementation, management, and oversight, by the Program Manager (PM), of all activities associated with the acquisition, development, production, fielding, sustainment, and disposal of a DoD system.</div></div><br><i>lifecycle support requirements</i><br><div class="ExternalClassB497439FC7004128BDEBEBA63E956122" style="padding-left&#58;10px;">Lifecycle support requirements are requirements for availability, scalability, maintainability, supportability, and other requirements as appropriate for the specific initiative. ​</div></div><br><i>life cycle sustainment plan</i><br><div class="ExternalClass99455B96C0FC441F9C6C3DA4ECCBEA33" style="padding-left&#58;10px;"><p>The detailed product support plan, including sustainment metrics, risks, costs, and analyses used to deliver the performance-based best value strategy covering the Integrated Product Support (IPS) elements</p></div></div><br><i>life cycle sustainment</i><br><div class="ExternalClassC87341ECB9304E18A14AE864813597E2" style="padding-left&#58;10px;">Translates force provider capability and performance requirements into tailored product support to achieve specified and evolving life cycle product support availability, reliability, and affordability parameters. Life cycle sustainment considerations include supply, maintenance, transportation, sustaining engineering, data management, Configuration Management (CM), Human Systems Integration (HSI), environment, safety (including explosives), and occupational health, protection of critical program information and anti-tamper provisions, supportability, and interoperability. Initially begun during Materiel Solution Analysis (MSA) phase and matured during the Technology&#160;Maturation and Risk Reduction&#160;phase, life cycle sustainment planning spans a system's entire life cycle from MSA phase to disposal.</div></div><br><i>life cycle mission data plans</i><br><div class="ExternalClass5CEB54B98AB34AD7BC4DBC94AC1E45F1" style="padding-left&#58;10px;">The program manager's plan for how the program manager and other organizations will address specific program needs for Intelligence Mission Data (IMD). It contains the results of IMD planning and spans the entire lifecycle of an IMD-dependent acquisition program. The LMDP potentially influences programmatic decisions based on the availability of IMD over the life of the program.</div></div><br><i>life cycle management plan</i><br><div class="ExternalClassD9215F27FF794446AB3392353D56C7C2" style="padding-left&#58;10px;">Integrated acquisition and sustainment strategy for the life of the system. The LCMP fulfills the Federal Acquisition Regulation (FAR), Defense FAR Supplement (DFARS), and Air Force FAR Supplement (AFFARS) requirements of the acquisition plan and the DoDI 5000.02 requirements of the acquisition strategy, which includes the Life Cycle Sustainment Plan (LCSP).</div></div></div><br><i>Agile approach</i><br><div class="ExternalClassD43FD18022EC41B380403BFEB8B20F40" style="padding-left&#58;10px;">&#58; End user(s) team with developers in order to make instant decisions on user functionality. High level requirements are initially prioritized and developed quickly by small teams in order to get a working product quickly to the customer. Multiple, rapidly executed Increments are developed and capabilities are released to the customer as soon as possible. Prototypes may be used as a starting place and utilize a modular, open-systems approach. Agile methods are typically used for small, low risk projects.</div></div><br><i>Development, Security, and Operations</i><br><div class="ExternalClass4015E4738F354F22A0B014BC5F0853E1" style="padding-left&#58;10px;"><p><span style="font-family&#58;&quot;segoe ui&quot;,&quot;segoe&quot;,tahoma,helvetica,arial,sans-serif;">​An organizational software engineering culture and practice that aims at unifying software development (Dev), security (Sec) and operations (Ops).&#160; The main characteristic of DevSecOps is to automate, monitor, and apply security at all phases of the software lifecycle&#58; plan, develop, build, test, release, deliver, deploy, operate, and monitor.&#160; In DevSecOps, testing and security are shifted left through automated unit, functional, integration, and security testing this is a key DevSecOps differentiator since security and functional capabilities are tested and built simultaneously.</span></p></div></div><br><i>Minimum Viable Product</i><br><div class="ExternalClass27910EDB7F764E6E9F8C36E5DCADFD9D" style="padding-left&#58;10px;"><p>​An early version of the software to deliver or field basic capabilities to users to evaluate and provide feedback on. Insights from MVPs help shape scope, requirements, and design.</p></div></div><br></div></div><br><i>Minimum Viable Capability Release</i><br></div></div>
Post-Production Software Support (PPSS)2879151/18/2023 4:04:35 PMChapter 4-3.2.1.2.2, Software Sustainment, to the discussion of post-deployment software support and post-production software support https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClass9489EE623031412D8E4EAE4F2DFE9BB2">Those software support activities that occur after the production of the system has been completed.</div>
Interface Management 28881511/29/2022 3:36:37 PMManagement in Systems and Software Engineering (Fee Required) IEEE-1012-2012 IEEE Standard for System and Software Verification https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse
Supply Chain Risk Management (SCRM) - Overview2880211/30/2023 5:28:57 PMCDSE) – Supply Chain Risk Management Software and Supply Chain Assurance DHS US CERT Defense AT&L Magazine, March-April 2017 SCRM--Supply Chain Risk Management “Fundamentals https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse<div class="ExternalClass04B357CC2EF14B04B403649AA9EB1DCC">A systematic process for managing supply chain risk by identifying susceptibilities, vulnerabilities and threats throughout DoD's supply chain and developing mitigation strategies to combat those threats whether presented by the supplier, the supplied product and its subcomponents, or the supply chain (e.g., initial production, packaging, handling, storage, transport, mission operation, and disposal).</div>
Product Support Analysis (PSA)2880691/19/2023 9:59:31 PMTechAmerica Standard TA-STD-0017 Product Support Analysis MIL-Handbook-502A Product Support Analysis US Army Logistics Support Activity (LOGSA) PowerLOGJ Tool US Army https://www.dau.edu/acquipedia/Lists/Acquipedia Article/quick.aspxFalse

Chat with DAU Assistant
Bot Image