About: Scenario (computing)

Facets (new session)
Description
Metadata
Settings
- Rule:
- Inverse Functional Properties:
- "Same As":

About: Scenario (computing) Goto Sponge NotDistinct Permalink

An Entity of Type : yago:SocialControl101123598, within Data Space : dbpedia.demo.openlinksw.com associated with source document(s)
QRcode icon

http://dbpedia.demo.openlinksw.com/describe/?url=http%3A%2F%2Fdbpedia.org%2Fresource%2FScenario_%28computing%29

In computing, a scenario (UK: /sɪˈnɑːrioʊ/, US: /səˈnɛərioʊ/; loaned from Italian scenario (pronounced [ʃeˈnaːrjo]), from Latin scena 'scene') is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software. Increasingly, scenarios are used directly to define the wanted behaviour of software: replacing or supplementing traditional functional requirements. Scenarios are often defined in use cases, which document alternative and overlapping ways of reaching a goal.

Attributes	Values
rdf:type	yago:WikicatSoftwareRequirements yago:Abstraction100002137 yago:Act100030358 yago:Duty101129920 yago:Event100029378 yago:GroupAction101080366 yago:PsychologicalFeature100023100 yago:Requirement105892651 yago:YagoPermanentlyLocatedEntity book yago:SocialControl101123598
rdfs:label	Scénario (informatique) (fr) Scenario (computing) (en) Cenário (software) (pt)
rdfs:comment	Un scénario en informatique est une trame narrative qui décrit un ensemble d'interactions possibles entre des utilisateurs et des systèmes (logiciels, matériels et services). (fr) In computing, a scenario (UK: /sɪˈnɑːrioʊ/, US: /səˈnɛərioʊ/; loaned from Italian scenario (pronounced [ʃeˈnaːrjo]), from Latin scena 'scene') is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software. Increasingly, scenarios are used directly to define the wanted behaviour of software: replacing or supplementing traditional functional requirements. Scenarios are often defined in use cases, which document alternative and overlapping ways of reaching a goal. (en) Cenários têm vindo a ser usados ao longo do tempo em diversas áreas, nomeadamente em interacção homem computador, engenharia de requisitos, desenho orientado a objectos, planejamento estratégico, etc, uma vez que facilitam bastante a criação e utilização de casos de uso, de uma forma simples e flexível. A utilização desta aproximação em engenharia de requisitos é baseada na hipótese de que a integração desta técnica permite melhorar o processo de especificação de requisitos através de um maior envolvimento dos utilizadores no mesmo. Esta técnica descreve os requisitos numa linguagem fácil de entender e validar para todas as pessoas relacionadas com o projecto, motivando-as a discutir e participar, obtendo assim um maior feedback sobre o que se está a fazer. (pt)
dcterms:subject	Software design Software requirements Usability
Wikipage page ID	1918289 (xsd:integer)
Wikipage revision ID	1118680735 (xsd:integer)
Link from a Wikipage to another Wikipage	Mockup Operational View Requirements analysis Department of Defense Architecture Framework Design rationale Concept of operations Storyboard Computer hardware Computing Functional requirement Stakeholder theory User story Marketing Actor (UML) Software design Loanword Abstraction Agile software development Flowchart Goal modeling Happy path Unified Modeling Language Software documentation Requirements elicitation Prototype Reliability engineering Scenario analysis Software requirements Usability Training Misuse case Software design Software testing Human–computer interaction IBM Rational Unified Process Narrative Use case Safety Security Simulation Software Non-functional requirements Implementation Team building Scenario testing Operational life Unified Modelling Language
Link from a Wikipage to an external page	http://tomeri.org/Stories.html
sameAs	Scenario (computing) Scenario (computing) Scenario (computing) Scenario (computing) Scenario (computing) Scenario (computing) Scenario (computing)
dbp:wikiPageUsesTemplate	dbt:Further dbt:IPA-it dbt:IPAc-en dbt:Otheruses dbt:Reflist dbt:Rp dbt:Short_description dbt:Ety dbt:Software_development_process
has abstract	In computing, a scenario (UK: /sɪˈnɑːrioʊ/, US: /səˈnɛərioʊ/; loaned from Italian scenario (pronounced [ʃeˈnaːrjo]), from Latin scena 'scene') is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software. A scenario has a goal, which is usually functional. A scenario describes one way that a system is used, or is envisaged to be used, in the context of an activity in a defined time-frame. The time-frame for a scenario could be (for example) a single transaction; a business operation; a day or other period; or the whole operational life of a system. Similarly the scope of a scenario could be (for example) a single system or a piece of equipment; an equipped team or a department; or an entire organization. Scenarios are frequently used as part of the system development process. They are typically produced by usability or marketing specialists, often working in concert with end users and developers. Scenarios are written in plain language, with minimal technical details, so that stakeholders (designers, usability specialists, programmers, engineers, managers, marketing specialists, etc.) can have a common ground to focus their discussions. Increasingly, scenarios are used directly to define the wanted behaviour of software: replacing or supplementing traditional functional requirements. Scenarios are often defined in use cases, which document alternative and overlapping ways of reaching a goal. (en) Un scénario en informatique est une trame narrative qui décrit un ensemble d'interactions possibles entre des utilisateurs et des systèmes (logiciels, matériels et services). (fr) Cenários têm vindo a ser usados ao longo do tempo em diversas áreas, nomeadamente em interacção homem computador, engenharia de requisitos, desenho orientado a objectos, planejamento estratégico, etc, uma vez que facilitam bastante a criação e utilização de casos de uso, de uma forma simples e flexível. A utilização desta aproximação em engenharia de requisitos é baseada na hipótese de que a integração desta técnica permite melhorar o processo de especificação de requisitos através de um maior envolvimento dos utilizadores no mesmo. Esta técnica descreve os requisitos numa linguagem fácil de entender e validar para todas as pessoas relacionadas com o projecto, motivando-as a discutir e participar, obtendo assim um maior feedback sobre o que se está a fazer. Mais recentemente, a técnica tem sido utilizada no desenho e desenvolvimento de sistemas, contudo, poucos métodos emergiram para guiar a prática de análise e validação de requisitos baseada em cenários. (pt)
gold:hypernym	Narrative
prov:wasDerivedFrom	wikipedia-en:Scenario_(computing)?oldid=1118680735&ns=0
page length (characters) of wiki page	8312 (xsd:nonNegativeInteger)
foaf:isPrimaryTopicOf	wikipedia-en:Scenario_(computing)
is Link from a Wikipage to another Wikipage of	Behavior-driven development User scenarios Design fiction Interaction technique Object-oriented design Persona (user experience) User story

Faceted Search & Find service v1.17_git139 as of Feb 29 2024

Alternative Linked Data Documents: ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 08.03.3330 as of Mar 19 2024, on Linux (x86_64-generic-linux-glibc212), Single-Server Edition (378 GB total memory, 67 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software