<--- Back to Details
First PageDocument Content
Quality / Software requirements / Software quality / Reliability engineering / Software Engineering Institute / Capability Maturity Model Integration / Capability Maturity Model / Validation / DO-178B / Software development / Carnegie Mellon University / Software development process
Date: 2012-11-27 14:36:12
Quality
Software requirements
Software quality
Reliability engineering
Software Engineering Institute
Capability Maturity Model Integration
Capability Maturity Model
Validation
DO-178B
Software development
Carnegie Mellon University
Software development process

Microsoft Word - ReliabilityFramework-2012-SR-013_final to pub

Add to Reading List

Source URL: www.sei.cmu.edu

Download Document from Source Website

File Size: 2,46 MB

Share Document on Facebook

Similar Documents

Computing / Software engineering / Software review / Program analysis / Software testing / Object-oriented programming languages / Static program analysis / Java / Android / Software quality / Computer programming / Memory leak

Program Analyses for Understanding the Behavior and Performance of Traditional and Mobile Object-Oriented Software Dissertation Presented in Partial Fulfillment of the Requirements for the Degree Doctor of Philosophy in

DocID: 1xVqM - View Document

Network architecture / Computing / Computer architecture / Information and communications technology / Emerging technologies / Internet architecture / Configuration management / Software-defined networking / Network protocols / OpenFlow / Open vSwitch / Computer network

Robust fault-recovery in Software-Defined Networks IBSDN: IGP as a Backup in SDN Master’s thesis presented in partial fulfillment of the requirements for the degree of

DocID: 1xUkw - View Document

Real-time computing / Scheduling / Technology / Computer architecture / System software / Embedded operating systems / Automotive software / OSEK / Worst-case execution time / Real-time operating system / Uppaal Model Checker / Model checking

Checking Consistency of Real-Time Requirements on Distributed Automotive Control Software Early in the Development Process using UPPAAL Jan Toennemann1 , Andreas Rausch1 , Falk Howar2 , and Benjamin Cool3 1

DocID: 1xU0r - View Document

Software Lifecycle  nLogic software engineers are highly qualified throughout the fully software life cycle including requirements, design, coding, test, and documentation. Our

DocID: 1vnBe - View Document

Product Specification Sheet: MAXit for Arbortext Editor Hardware and Software Requirements

DocID: 1vnpo - View Document