Asee peer logo

Enhancing The Software Verification And Validation Course Through Laboratory Sessions

Download Paper |


2008 Annual Conference & Exposition


Pittsburgh, Pennsylvania

Publication Date

June 22, 2008

Start Date

June 22, 2008

End Date

June 25, 2008



Conference Session

Software Engineering Course Content

Tagged Division

Software Engineering Constituent Committee

Page Count


Page Numbers

13.555.1 - 13.555.12



Permanent URL

Download Count


Request a correction

Paper Authors

author page

Sushil Acharya Robert Morris University

Download Paper |

NOTE: The first page of text has been automatically extracted and included below in lieu of an abstract

Enhancing the Software Verification and Validation Course through Laboratory Sessions

1. Introduction

Many engineering courses are taught through lecture-only sessions and students garner experiences through course based projects and internships. However these methods alone do not suffice to place fresh engineering graduates at a competitive advantage in the job market. In good and bad times employers look for engineers with job-related experience since such engineers require less training and provide faster results. In view of this, course enhancements and delivery with focus on real-life work experience needs to be embraced by engineering programs. Software Engineering (SE) is one such engineering discipline where curriculum enhancement through laboratory sessions will highly benefit its graduates.

Software Engineering (SE)

Prior to the 1990s SE was not an explicit engineering discipline. Computing Curricula 20051 states that during the 1990’s SE began to develop as a discipline unto itself. Since then this discipline has been playing an important role in the multibillion dollar software industry. SE is defined as the discipline of developing and maintaining software systems that behave reliably and efficiently, are affordable to develop and maintain, and satisfy all the requirements that customers have defined for them1. Figure 1 depicts the conceptual territory occupied by SE in the problem space of computing. Unlike other computing disciplines (like IS, IT, CS and CE), SE domain spans on all directions. This is because software engineers fill a wide range of needs in large-project software expertise1.

Figure 1: Software Engineering Conceptual Territory1

SE’s main goal is to develop systematic models and reliable techniques for producing high- quality software on time and within budget, and these concerns extend all the way from theory and principles to daily practice2. This goal indicates that software engineers need both theoretical

Acharya, S. (2008, June), Enhancing The Software Verification And Validation Course Through Laboratory Sessions Paper presented at 2008 Annual Conference & Exposition, Pittsburgh, Pennsylvania. 10.18260/1-2--4000

ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2008 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015