Skip to main content Accessibility help

We use cookies to distinguish you from other users and to provide you with a better experience on our websites. Close this message to accept cookies or find out how to manage your cookie settings.

Close cookie message
×
  1. Home
  2. Browse subjects
  3. Computer Science
  4. Software Engineering and Development
  5. Content listing

Refine search

Refine search

Access:
Content type:
Publication date:
Apply   From and To filters
Subject: Show more
Journals Show more
Publishers: Show more
Societies Show more
Series: Show more
Collections: Show more

Actions for selected content:

Select all | Deselect all
  • View selected items
  • Export citations
  • Download PDF (zip)
  • Save to Kindle
  • Save to Dropbox
  • Save to Google Drive

Save Search

You can save your searches here and later view and run them again in "My saved searches".

Please provide a title, maximum of 40 characters.
Cancel
×

1810 results in Software Engineering and Development

Page 4 of 91

  • 10 - Quality Metrics

  • Ravi Sethi, University of Arizona
  • Book:
    Software Engineering
    Published online:
    09 December 2022
    Print publication:
    08 December 2022, pp 253-299

  • Summary

    For metrics to be useful, they must be consistent with our intuitions about the real world. As an example, defects can be a useful metric for product quality – the fewer severe defects, the better.

  • 7 - Architectural Patterns

  • Ravi Sethi, University of Arizona
  • Book:
    Software Engineering
    Published online:
    09 December 2022
    Print publication:
    08 December 2022, pp 172-202

  • Summary

    Rather than start each design from scratch, software architects tend to adapt earlier successful designs for similar problems. Even if they do not reuse any code, the solution approach gives them a head start with the current problem. Problems like fault tolerance have been addressed over and over again. (The idea for a solution is to have a live backup system that takes over if the primary system fails due to a hardware or software fault.)

  • 3 - User Requirements

  • Ravi Sethi, University of Arizona
  • Book:
    Software Engineering
    Published online:
    09 December 2022
    Print publication:
    08 December 2022, pp 64-99

  • Summary

    All software projects face the twin questions of what users want and what to build to address those wants. These are related, but logically distinct questions. Requirements elicitation is the process of discovering user wants and writing them down as user requirements. Requirements analysis is the process of prioritizing user requirements from various sources and defining what to build as a product. In practice, elicitation and analysis are entwined: the same user-developer conversation can touch on a user goal, its priority, and acceptance tests for it.

  • 9 - Testing

  • Ravi Sethi, University of Arizona
  • Book:
    Software Engineering
    Published online:
    09 December 2022
    Print publication:
    08 December 2022, pp 222-252

  • Summary

    Software testing is the process of running a program in a controlled environment to check whether it behaves as expected. The purpose of testing is to improve software quality. If a test fails – that is, the program does not behave as expected – there must be a fault, either in the program or in the specification of expected behavior. Either way, the test has uncovered a problem that should be resolved.

  • 4 - Requirements Analysis

  • Ravi Sethi, University of Arizona
  • Book:
    Software Engineering
    Published online:
    09 December 2022
    Print publication:
    08 December 2022, pp 100-124

  • Summary

    Once user needs and goals are recorded as user requirements, the emphasis shifts to requirements analysis. User requirements, even specific and measurable ones, correspond to wish lists from the various stakeholders. Requirements analysis prioritizes these wish lists to define precisely what to build as a product; see . To prioritize, we must answer three questions. First, what properties of the product will prioritization be based on? Examples of properties include not only cost and functionality, but usefulness, usability, and desirability. Second, how will the properties be quantified? Quantification involves classification into ranked categories; for example, must-have, should-have, could-have, won’t have. Third, how do we rank order requirements based on a combination of properties, such as benefit, cost, and perhaps risk?

  • 4 - Lists and Patterns

  • from Part I - Language Concepts
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 50-65
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 23 - Foreign Function Interface

  • from Part III - The Complier and Runtime System
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 405-423
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 3 - Variables and Functions

  • from Part I - Language Concepts
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 31-49
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 17 - Concurrent Programming with Async

  • from Part II - Tools and Techniques
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 297-324
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 25 - Understanding the Garbage Collector

  • from Part III - The Complier and Runtime System
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 435-446
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 7 - Variants

  • from Part I - Language Concepts
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 99-118
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 1 - Prologue

  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 1-6
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 9 - Imperative Programming

  • from Part I - Language Concepts
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 134-165
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 8 - Error Handling

  • from Part I - Language Concepts
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 119-133
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 2 - A Guided Tour

  • from Part I - Language Concepts
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 9-30
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 24 - Memory Representation of Values

  • from Part III - The Complier and Runtime System
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 424-434
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 20 - Parsing with OCamllex and Menhir

  • from Part II - Tools and Techniques
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 361-373
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

  • 16 - Command-Line Parsing

  • from Part II - Tools and Techniques
  • Anil Madhavapeddy, University of Cambridge, Yaron Minsky
  • Book:
    Real World OCaml: Functional Programming for the Masses
    Published online:
    22 September 2022
    Print publication:
    13 October 2022, pp 280-296
    • Chapter
      • You have access
      • Open access
    • PDF
    • Export citation

Page 4 of 91