Software Architecture Suggestion for GUITAR: A Multi-Developer Software Testing Tool, Quizzes of Software Engineering

The software architecture for guitar, a multi-developer software testing tool consisting of several sub-systems and test artifacts. The author suggests a possible architecture and justifies it by addressing scalability, maintainability, and test artifact management.

Typology: Quizzes

2019/2020

Uploaded on 11/25/2020

koofers-user-69r-2
koofers-user-69r-2 🇺🇸

9 documents

1 / 1

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Page 1 of 1
CMSC435; Section 0101
Mar. 2, 2006; Quiz #4
Student’s Name: ____________________________________
Question 1: Our single-machine software testing tool called GUITAR consists of several
sub-systems. Each sub-system produces, consumes, or modifies a test artifact. Examples
of sub-systems include (1) test case generator, (2) reverse engineering tool, (3) model
editor, (4) capture/replay tool that generates test cases and expected output, (5) model-
based expected output generator, (6) test adequacy evaluator, and (7) test case executor.
Examples of test artifacts include (a) test cases, (b) expected output, (c) GUI model, and
(d) test adequacy report.
GUITAR has evolved from a single-developer software to a multi-developer software.
We cannot currently predict the number of developers, sub-systems, and models that will
be added to GUITAR over the next 10 years.
Suggest a software architecture for GUITAR. Justify your answer in detail.

Partial preview of the text

Download Software Architecture Suggestion for GUITAR: A Multi-Developer Software Testing Tool and more Quizzes Software Engineering in PDF only on Docsity!

Page 1 of 1

CMSC435; Section 0101

Mar. 2, 2006; Quiz

Student’s Name: ____________________________________

Question 1: Our single-machine software testing tool called GUITAR consists of several sub-systems. Each sub-system produces, consumes, or modifies a test artifact. Examples of sub-systems include (1) test case generator, (2) reverse engineering tool, (3) model editor, (4) capture/replay tool that generates test cases and expected output, (5) model- based expected output generator, (6) test adequacy evaluator, and (7) test case executor. Examples of test artifacts include (a) test cases, (b) expected output, (c) GUI model, and (d) test adequacy report.

GUITAR has evolved from a single-developer software to a multi-developer software. We cannot currently predict the number of developers, sub-systems, and models that will be added to GUITAR over the next 10 years.

Suggest a software architecture for GUITAR. Justify your answer in detail.