Software requirements Definitions

  • B

    burn down chart

    A burn down chart is a visual representation of the amount of work that still needs to be completed before the end of a project.

  • D

    documentation

    In computer hardware and software product development, documentation is the information that describes the product to its users. It consists of the product technical manuals and online information (including online versions of the technical manuals and help facility descriptions).

  • F

    functional specification

    A functional specification is a formal document used to describe a product's intended capabilities, appearance, and interactions with users in detail for software developers.

  • H

    HCI (human-computer interaction)

    HCI (human-computer interaction) is the study of how people interact with computers and to what extent computers are or are not developed for successful interaction with human beings.

  • I

    integrated development environment (IDE)

    An integrated development environment (IDE) is a software suite that consolidates basic tools required to write and test software.

  • P

    pattern (design pattern)

    In software development, a pattern (or design pattern) is a written document that describes a general solution to a design problem that recurs repeatedly in many projects.

  • R

    rapid mobile app development (RMAD)

    Rapid mobile application development (RMAD) uses low-code/no-code programming tools to speed the process of application creation for mobile platforms.

  • requirements analysis (requirements engineering)

    Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product.

  • S

    software requirements specification (SRS)

    A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development. The SRS fully describes what the software will do and how it will be expected to perform... (Continued)

  • story

    In agile software development, a story is a particular business need assigned to the software development team. (Continued...)

  • U

    use case

    A use case is a methodology used in system analysis to identify, clarify, and organize system requirements.

  • user acceptance testing (UAT)

    In software development, user acceptance testing (UAT)—also called application testing, and end user testing—is a phase of software development in which the software is tested in the "real world" by the intended audience.

  • user story

    A user story is a tool used in Agile development to capture a description of a software feature from an end-user perspective.

-ADS BY GOOGLE

SearchCloudComputing

SearchAppArchitecture

SearchITOperations

SearchAWS

Close