Search Results - (( Defined contribution pension plant ) OR ((( Defined distribution operations plans ) OR ( Defined distribution version plans ))))

  • Showing 1 - 5 results of 5
Refine Results
  1. 1

    Making globally distributed software development a success story : International Conference on Software Process, ICSP 2008, Leipzig, Germany, May 10-11, 2008 : proceedings by International Conference on the Software Process Leipzig, Germany, SpringerLink (Online service)

    Published: Springer, 2008
    Description: 1 online resource (xiv, 422 pages) : illustrations.
    Contents: “…-- Investigating Factors Affecting the Usability of Software Process Descriptions -- Degree of Agility in Pre-Implementation Process Phases -- Support IT Service Management with Process Modeling and Analysis -- The Secret Life of a Process Description: A Look into the Evolution of a Large Process Model -- Simulation Modeling -- Simulating Worst Case Scenarios and Analyzing Their Combined Effect in Operational Release Planning -- Using Process Simulation to Assess the Test Design Effort Reduction of a Model-Based Testing Approach -- GENSIM 2.0: A Customizable Process Simulation Model for Software Process Evaluation -- RVSim: A Simulation Approach to Predict the Impact of Requirements Volatility on Software Project Plans -- Identifying Key Success Factors for Globally Distributed Software Development Project Using Simulation: A Case Study -- Hybrid Modeling of Test-and-Fix Processes in Incremental Development -- Reflections on 10 Years of Software Process Simulation Modeling: A Systematic Review -- Experience Report -- Integrating Joint Reviews with Automotive SPICE Assessments Results -- Quantitatively Managing Defects for Iterative Projects: An Industrial Experience Report in China -- An Investigation of Software Development Productivity in China -- Optimized Software Process for Fault Handling in Global Software Development -- Measuring and Comparing the Adoption of Software Process Practices in the Software Product Industry.…”
    SpringerLink - Click here for access
    Conference Proceeding eBook
  2. 2

    Software engineering for embedded systems : methods, practical techniques, and applications First edition. by ScienceDirect (Online service)

    Published: Newnes, 2013
    Description: 1 online resource (xlix, 1150 pages).
    Contents: “…-- Certification killers -- Project planning strategies -- Strategy 1: determine the project certification scope early -- Strategy 2: determine feasibility of certification -- Strategy 3: select an independent assessor (if used) -- Strategy 4: understand your assessor's role (if used) -- Strategy 5: assessment communication is key -- Strategy 6: establish a basis of certification -- Strategy 7: establish a "fit and purpose" for your product -- Strategy 8: establish a certification block diagram -- Strategy 9: establish communication integrity objectives -- Strategy 10: identify all interfaces along the certification boundary -- Strategy 11: identify the key safety defensive strategies -- Strategy 12: define built in test (BIT) capability -- Strategy 13: define fault annunciation coverage -- Strategy 14: define reliance and expectation of the operator/user -- Strategy 15: define plan for developing software to appropriate integrity level -- Strategy 16: define artifacts to be used as evidence of compliance -- Strategy 17: plan for labor-intensive analyses -- Strategy 18: create user-level documentation -- Strategy 19: plan on residual activity -- Strategy 20: publish a well-defined certification plan -- Faults, failures, hazards, and risk analysis -- Faults, errors, and failures -- Availability and reliability -- Fault handling -- Hazard analysis -- Risk analysis -- Safety-critical architectures -- "Do-er"/"Check-er" -- Two processors -- "Voter" -- Software implementation strategies -- Strategy 1: have a well-defined, repeatable peer-review process -- Strategy 2: consider using existing safety coding standards -- Strategy 3: handle all combinations of input data -- Strategy 4: specific variable value checking -- Strategy 5: mark safety-critical code sections -- Strategy 6: timing execution checking -- Strategy 7: stale data -- Strategy 8: comparison of outputs -- Strategy 9: initialize data to least permissive state -- Strategy 10: order of execution -- Strategy 11: volatile data checking -- Strategy 12: non-volatile data checking -- Strategy 13: make sure the entire system can run -- Strategy 14: remove "dead" code -- Strategy 15: fill unused memory -- Strategy 16: static code analysis -- Background -- Is that software yours? …”
    Elsevier - Click here for access
    eBook
  3. 3
  4. 4
  5. 5