Scenario (computing) (original) (raw)
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).
| Property | Value |
|---|---|
| dbo: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) |
| dbo:wikiPageExternalLink | http://tomeri.org/Stories.html |
| dbo:wikiPageID | 1918289 (xsd:integer) |
| dbo:wikiPageLength | 8312 (xsd:nonNegativeInteger) |
| dbo:wikiPageRevisionID | 1118680735 (xsd:integer) |
| dbo:wikiPageWikiLink | dbr:Mockup dbr:Operational_View dbr:Requirements_analysis dbr:Department_of_Defense_Architecture_Framework dbr:Design_rationale dbr:Concept_of_operations dbr:Storyboard dbr:Computer_hardware dbr:Computing dbr:Functional_requirement dbr:Stakeholder_theory dbr:User_story dbr:Marketing dbr:Actor_(UML) dbc:Software_design dbr:Loanword dbr:Abstraction dbr:Agile_software_development dbr:Flowchart dbr:Goal_modeling dbr:Happy_path dbr:Unified_Modeling_Language dbr:Software_documentation dbr:Requirements_elicitation dbr:Prototype dbr:Reliability_engineering dbr:Scenario_analysis dbc:Software_requirements dbc:Usability dbr:Training dbr:Misuse_case dbr:Software_design dbr:Software_testing dbr:Human–computer_interaction dbr:IBM_Rational_Unified_Process dbr:Narrative dbr:Use_case dbr:Safety dbr:Security dbr:Simulation dbr:Software dbr:Non-functional_requirements dbr:Implementation dbr:Team_building dbr:Scenario_testing dbr:Operational_life dbr:Unified_Modelling_Language |
| 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 |
| dct:subject | dbc:Software_design dbc:Software_requirements dbc:Usability |
| gold:hypernym | dbr:Narrative |
| rdf:type | yago:WikicatSoftwareRequirements yago:Abstraction100002137 yago:Act100030358 yago:Duty101129920 yago:Event100029378 yago:GroupAction101080366 yago:PsychologicalFeature100023100 yago:Requirement105892651 yago:YagoPermanentlyLocatedEntity dbo:Book yago:SocialControl101123598 |
| 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) |
| rdfs:label | Scénario (informatique) (fr) Scenario (computing) (en) Cenário (software) (pt) |
| owl:sameAs | freebase:Scenario (computing) yago-res:Scenario (computing) wikidata:Scenario (computing) dbpedia-fa:Scenario (computing) dbpedia-fr:Scenario (computing) dbpedia-pt:Scenario (computing) https://global.dbpedia.org/id/4uRj6 |
| prov:wasDerivedFrom | wikipedia-en:Scenario_(computing)?oldid=1118680735&ns=0 |
| foaf:isPrimaryTopicOf | wikipedia-en:Scenario_(computing) |
| is dbo:wikiPageDisambiguates of | dbr:Scenario_(disambiguation) |
| is dbo:wikiPageRedirects of | dbr:User_scenarios dbr:User_scenario |
| is dbo:wikiPageWikiLink of | dbr:Behavior-driven_development dbr:User_scenarios dbr:Design_fiction dbr:Interaction_technique dbr:Object-oriented_design dbr:Persona_(user_experience) dbr:User_story dbr:Adaptation_(computer_science) dbr:Glossary_of_Unified_Modeling_Language_terms dbr:Goal_modeling dbr:Happy_path dbr:Requirements_elicitation dbr:International_Superstar_Soccer_2 dbr:Use_case dbr:Scenario_(disambiguation) dbr:Scenario_planning dbr:User_scenario dbr:Systems_development_life_cycle dbr:Event_partitioning dbr:Usage-centered_design dbr:Scenario_testing |
| is foaf:primaryTopic of | wikipedia-en:Scenario_(computing) |