article · 2015
Software Engineering Process Case Study
Gary J. Nut T
Cited by 0Abstract and details only
Abstract
Recently a faction of software engineering re-searchers has focused their attention on studying the process by which software is produced, stimulating interest in models to specify, design, and implement software. A significant part of the practicing soft-ware industry must produce software that conforms to a documentation standard (military standard 2167A) for software products; it is intended to ensure that delivered software meets the documentation require-ments. This paper is a case study of how a government software contractor might use models to define a pro-cess for designing and implementing a software prod-uct that complies with the documentation require-ments. The intent of the paper is to apply business process modeling technology to the software ngineer-ing domain, thus exploring strengths and weaknesses of our evolving models of group collaboration. The case study illustrates an alternative way to design, an-alyze, and track software processes. It also attempts to illustrate how the model might "break down " as the basis of an enactment model if it were to be used to coordinate the work of a large number of software developers.
Cite this paper
T, G. J. N. (2015). Software Engineering Process Case Study.
T, Gary J. Nut. “Software Engineering Process Case Study.” 2015.
T, Gary J. Nut. 2015. “Software Engineering Process Case Study.”
T, G.J.N. (2015) ‘Software Engineering Process Case Study’.
@article{t2015software,
title = {{Software Engineering Process Case Study}},
author = {T, Gary J. Nut},
year = {2015}
}Made from the index record. Check names, capitalisation and page numbers against the paper. Need another style? AI for Research has over 10,000.