About: Business Process Re-engineering and Agile Software Development: Applying the Story-Card Method

Facets (new session)
Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: Business Process Re-engineering and Agile Software Development: Applying the Story-Card Method Goto Sponge NotDistinct Permalink

An Entity of Type : schema:ScholarlyArticle, within Data Space : wasabi.inria.fr associated with source document(s)

Attributes	Values
type	Academic Article research paper schema:ScholarlyArticle
isDefinedBy	Covid-on-the-Web dataset
has title	Business Process Re-engineering and Agile Software Development: Applying the Story-Card Method
Creator	De Vries, Marné Djan, Elijah
Source	PMC
abstract	Enterprise designers need to continuously re-design their enterprise, re-evaluating the technologies that are available to digitize their operations. Although light-weight agile software development approaches are favored by software development service providers, additional requirements elicitation practices should be incorporated when scaling factors apply, since design team members need to have a shared understanding of the operating context and high-level requirements. Research indicated that the organization construction diagram (OCD) could be useful to create a shared context for enterprise operation, linking detailed functional requirements to this shared context during software development. Although the OCD is concise, its associated concepts are abstract and an additional story-card method (SCM) is needed to transform existing enterprise implementations into an OCD. Since additional evaluation of the SCM was required, this study focused on a real-world demonstration of the SCM at a Fintech company where an agile software development approach is applied. The results indicate that the SCM is useful when incorporated within an agile software development approach.
has issue date	2020-03-06(xsd:dateTime)
bibo:doi	10.1007/978-3-030-44999-5_31
has license	no-cc
sha1sum (hex)	3f2e214a0b4ba8cfa2d3f4acbb41de2de9e47de2
schema:url	https://doi.org/10.1007/978-3-030-44999-5_31
resource representing a document's title	Business Process Re-engineering and Agile Software Development: Applying the Story-Card Method
has PubMed Central identifier	PMC7134287
schema:publication	Responsible Design, Implementation and Use of Information and Communication Technology
resource representing a document's body	covid:3f2e214a0b4ba8cfa2d3f4acbb41de2de9e47de2#body_text
is schema:about of	named entity 'agile software development' named entity 'linking' named entity 'operation' named entity 'abstract' named entity 'SHARED' named entity 'COULD BE' named entity 'OCD' named entity 'INDICATED' named entity 'ORGANIZATION' named entity 'functional requirements' named entity 'requirements elicitation' named entity 'Although' named entity 'enterprise' named entity 'software development' named entity 'functional requirements' named entity 'software development' named entity 'agile software development' named entity 'Fintech' named entity 'Agile Software Development' named entity 'construction' named entity 'agile software development' named entity 'agile software development' named entity 'formative evaluation' named entity 'agile software development' named entity 'Fintech' named entity 'user acceptance' named entity 'software application' named entity 'TKs' named entity 'BPMN' named entity 'Fintech' named entity 'agile software development' named entity 'software development project' named entity 'participant-observer' named entity 'software development' named entity 'requirements analysis' named entity 'participant-observer' named entity 'requirements analysis' named entity 'MS Excel' named entity 'software development approach' named entity 'software development approach' named entity 'OCD' named entity 'Positive feedback' named entity 'A1 paper' named entity '4.2' named entity 'Requirements Analysis' named entity 'user story' named entity 'sticky-note' named entity 'Microsoft Excel' named entity 'ontological' named entity 'participant-observer' named entity 'positive feedback' named entity 'agile development' named entity 'automation' named entity 'participant-observer' named entity 'Evaluation Strategy' named entity 'agile approach' named entity 'agile software development' named entity 'web app' named entity 'requirements elicitation' named entity 'agile software development' named entity 'agile software development' named entity 'user interfaces' named entity 'functional requirements' named entity 'user story' named entity 'OCD' named entity 'participant-observer' named entity 'Fintech' named entity 'Business Process Model and Notation' named entity 'participant-observer' named entity 'requirements elicitation' named entity 'user story' named entity 'acceptance tests' named entity 'participant-observer' named entity 'non-functional' named entity 'acceptance test' named entity 'participant-observer' named entity 'blockchain' named entity 'TKs' named entity 'participant-observer' named entity 'agile development' named entity 'software requirements' named entity 'software requirements'

Faceted Search & Find service v1.13.91 as of Mar 24 2020

Alternative Linked Data Documents: Sponger | ODE Content Formats:

RDF

ODATA

Microdata

About

OpenLink Virtuoso version 07.20.3229 as of Jul 10 2020, on Linux (x86_64-pc-linux-gnu), Single-Server Edition (94 GB total memory)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software