Health.Zone Web Search

Search results

  1. Results from the Health.Zone Content Network
  2. User story - Wikipedia

    en.wikipedia.org/wiki/User_story

    User stories are written by or for users or customers to influence the functionality of the system being developed. In some teams, the product manager (or product owner in Scrum), is primarily responsible for formulating user stories and organizing them into a product backlog. In other teams, anyone can write a user story.

  3. Vertical slice - Wikipedia

    en.wikipedia.org/wiki/Vertical_slice

    The term vertical slice refers to a cross-sectional slice through the layers that form the structure of the software code base. It is mostly used in Scrum terminology where the work is planned in terms of features (or stories). For example, as a very basic approach, a software project may consist of three layers (or components): In this common ...

  4. Use case - Wikipedia

    en.wikipedia.org/wiki/Use_case

    t. e. In software and systems engineering, the phrase use case is a polyseme with two senses: A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful. A potential scenario in which a system receives an external request (such as user input) and responds to it.

  5. Scrum (software development) - Wikipedia

    en.wikipedia.org/wiki/Scrum_(software_development)

    Scrum is an agile team collaboration framework commonly used in software development and other industries. Scrum prescribes for teams to break work into goals to be completed within time-boxed iterations, called sprints. Each sprint is no longer than one month and commonly lasts two weeks. The scrum team assesses progress in time-boxed, stand ...

  6. Behavior-driven development - Wikipedia

    en.wikipedia.org/wiki/Behavior-driven_development

    The example given above establishes a user story for a software system under development. This user story identifies a stakeholder, a business effect and a business value. It also describes several scenarios, each with a precondition, trigger and expected outcome.

  7. Use case diagram - Wikipedia

    en.wikipedia.org/wiki/Use_case_diagram

    A use case diagram[1] is a graphical depiction of a user's possible interactions with a system. A use case diagram shows various use cases and different types of users the system has and will often be accompanied by other types of diagrams as well. The use cases are represented by either circles or ellipses. The actors are often shown as stick ...

  8. Sequence diagram - Wikipedia

    en.wikipedia.org/wiki/Sequence_diagram

    This diagram depicts the processes and objects involved and the sequence of messages exchanged as needed to carry out the functionality. Sequence diagrams are typically associated with use case realizations in the 4+1 architectural view model of the system under development. Sequence diagrams are sometimes called event diagrams or event scenarios.

  9. User journey - Wikipedia

    en.wikipedia.org/wiki/User_journey

    A user journey is the experiences a person has when interacting with something, typically software. This idea is generally used by those involved with user experience design, web design, user-centered design, or anyone else focusing on how users interact with software experiences. It is often used as a shorthand for the overall user experience ...