Search Results - (( Defined contribution pensions plans ) OR ((( Defined distributed cooperative plan ) OR ( Defined ((distribution erosion) OR (((distribution estimation) OR (distribution automation)))) plans ))))

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

    Software product lines : going beyond : 14th international conference, SPLC 2010, Jeju Island, South Korea, September 13-17, 2010 : proceedings by Software Product Lines Conference Cheju Island, Korea, SpringerLink (Online service)

    Published: Springer, 2010
    Description: 1 online resource (xix, 532 pages) : illustrations.
    Contents: “…Product Line Context -- Context-Dependent Product Line Practice for Constructing Reliable Embedded Systems -- Configuring Software Product Line Feature Models Based on Stakeholders' Soft and Hard Requirements -- Usage Context as Key Driver for Feature Selection -- Formal Approaches -- A Flexible Approach for Generating Product-Specific Documents in Product Lines -- Formal Definition of Syntax and Semantics for Documenting Variability in Activity Diagrams -- Delta-Oriented Programming of Software Product Lines -- Experience Papers -- Architecting Automotive Product Lines: Industrial Practice -- Developing a Software Product Line for Train Control: A Case Study of CVL -- Dealing with Cost Estimation in Software Product Lines: Experiences and Future Directions -- Variability Management -- Evolution of the Linux Kernel Variability Model -- Variability Modeling for Distributed Development -- A Comparison with Established Practice -- Variability Management in Software Product Lines: An Investigation of Contemporary Industrial Challenges -- Product Validation 1 -- Consistent Product Line Configuration across File Type and Product Line Boundaries -- Automated Incremental Pairwise Testing of Software Product Lines -- Linking Feature Models to Code Artifacts Using Executable Acceptance Tests -- Product Validation 2 -- Avoiding Redundant Testing in Application Engineering -- Improving the Testing and Testability of Software Product Lines -- Architecture-Based Unit Testing of the Flight Software Product Line -- Feature Modeling -- Sans Constraints? …”
    SpringerLink - Click here for access
    Conference Proceeding eBook
  2. 2

    Software and data technologies : Second International Conference, ICSOFT/ENASE 2007, Barcelona, Spain, July 22-25, 2007, revised selected papers by ICSOFT 2007 Barcelona, Spain, SpringerLink (Online service), ICSOFT (Conference), ENASE (Conference)

    Published: Springer, 2008
    Description: 1 online resource (xv, 428 pages) : illustrations.
    Contents: “…Invited Papers -- Benefits of Enterprise Ontology for the Development of ICT-Based Value Networks -- SOA Pragmatism -- Software and Data Technologies -- A Simple Language for Novel Visualizations of Information -- Generic Components for Static Operations at Object Level -- A Visual Dataflow Language for Image Segmentation and Registration -- A Debugger for the Interpreter Design Pattern -- Concepts for High-Performance Scientific Computing -- A Model Driven Architecture Approach to Web Development -- Reverse-Architecting Legacy Software Based on Roles: An Industrial Experiment -- A Supporting Tool for Requirements Elicitation Using a Domain Ontology -- Pattern Detection in Object-Oriented Source Code -- Testing the Effectiveness of MBIUI Life-Cycle Framework for the Development of Affective Interfaces -- Developer Stories: Improving Architecture in Agile Practice -- An Ontological SW Architecture Supporting Agile Development of Semantic Portals -- The Vcodex Platform for Data Compression -- Classification of Benchmarks for the Evaluation of Grid Resource Planning Algorithms -- A Disconnection-Aware Mechanism to Provide Anonymity in Two-Level P2P Systems -- Approximation and Scoring for XML Data Management -- Quantitative Analysis of the Top Ten Wikipedias -- A Semantic Web Approach for Ontological Instances Analysis -- Aspects Based Modeling of Web Applications to Support Co-evolution -- Recommending Trustworthy Knowledge in KMS by Using Agents -- Recent Developments in Automated Inferencing of Emotional State from Face Images -- Inconsistency-Tolerant Integrity Checking for Knowledge Assimilation -- Improving Cutting-Stock Plans with Multi-objective Genetic Algorithm -- Knowledge Purpose and Visualization -- Empirical Experimentation for Validating the Usability of Knowledge Packages in Transferring Innovations -- An Ontological Investigation in the Field of Computer Programs -- Evaluation of Novel Approaches to Software Engineering -- Formal Problem Domain Modeling within MDA -- Model Based Testing for Agent Systems -- A Metamodel for Defining Development Methodologies.…”
    SpringerLink - Click here for access
    Conference Proceeding eBook
  3. 3
  4. 4

    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