2001
DOI: 10.1007/3-540-45588-4_13
|View full text |Cite
|
Sign up to set email alerts
|

Storyboard Process to Assist in Requirements Verification and Adaptation to Capabilities Inherent in COTS

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2003
2003
2017
2017

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(9 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…The analogy to filmmaking is straightforward, especially for software with GUI: each use-case is equivalent to a storyboard; each distinct screen to an illustration; events, navigation and sequencing, business logic and constraints behind the screen to the graphical and textual annotations of an illustration. A recent example is the use of storyboard to enhance descriptive narratives of the operational scenarios in documenting operational concepts (Gregor et al, 2002). Storyboards are highly readable in making pre-visualization possible before the software is actually built.…”
Section: Storyboardsmentioning
confidence: 99%
“…The analogy to filmmaking is straightforward, especially for software with GUI: each use-case is equivalent to a storyboard; each distinct screen to an illustration; events, navigation and sequencing, business logic and constraints behind the screen to the graphical and textual annotations of an illustration. A recent example is the use of storyboard to enhance descriptive narratives of the operational scenarios in documenting operational concepts (Gregor et al, 2002). Storyboards are highly readable in making pre-visualization possible before the software is actually built.…”
Section: Storyboardsmentioning
confidence: 99%
“…Tello and Perez (2002) addressed the issue of COTS component selection among various similar COTS components and proposed BAREMO (Balanced Reuse Model) as an application of AHP to help software developers for suitable selection of COTS for the development of software. Gregor et al (2002) developed STORYBOARD approach for the COTS selection by focusing on the understanding of customer's requirements with the use of use cases and screen captures. Burgues et al (2002) proposed Combined Selection (CS), a two level (Local and Global) approach for the multiple COTS component selection.…”
Section: Literature Reviewmentioning
confidence: 99%
“…Other assessment methods include: CISD (COTS-based Integrated System Development) [4], STACE (Socio Technical Approach to COTS Evaluation) [10], CDSEM (Checklist Driven Software Evaluation Methodology) [3], CRE-COTS-Based Requirements Engineering Method [6], CEP (Comparative Evaluation Process Activities) [7], CBA Process Decision Framework [8], A Proactive Evaluation Technique [19], CAP-COTS Acquisition Process method [5], Storyboard Process [11], Combined Selection of COTS Components [12], PECA Process [13] or COTS-DSS [14].…”
Section: Related Workmentioning
confidence: 99%
“…An initial and essential part of component based software development is the assessment of available COTS components. There exist a plethora of available methods for COTS assessment [1], [2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [12], [13], [14]. An often overlooked aspect in the existing assessment techniques is the inherent uncertainty in the values of the parameters being assessed.…”
Section: Introductionmentioning
confidence: 99%