Warning: include(/home/faculty/schahczenski/webSites_Common/contact.php): failed to open stream: No such file or directory in /opt/www/classes/esof411/esof411.php on line 10
Warning: include(): Failed opening '/home/faculty/schahczenski/webSites_Common/contact.php' for inclusion (include_path='.:/usr/share/php') in /opt/www/classes/esof411/esof411.php on line 10
Office Hours:
Warning: include(/home/faculty/schahczenski/webSites_Common/officeHours_spring.php): failed to open stream: No such file or directory in /opt/www/classes/esof411/esof411.php on line 16
Warning: include(): Failed opening '/home/faculty/schahczenski/webSites_Common/officeHours_spring.php' for inclusion (include_path='.:/usr/share/php') in /opt/www/classes/esof411/esof411.php on line 16
Text: None
Prerequisite: ESOF322
Meeting times and place: Mon., Wed. & Wed. 12:00 - 12:50pm, MUS 205
What is in this course?
Using industry standards, a text and other materials, this course will focus on understanding software verification and validation (V&V) concepts, processes, techniques and tools. In addition students will practice several V&V techniques in class exercises and lab assignments. Prerequisites: ESOF 322 (2nd)
Grading:
| Activity | Percentage |
|---|---|
| Attendance - Start with 100% and loose 5% for each absense after 2 absences | 20% |
Quality of:
|
75% |
| Refletion paper and Final Presentation | 5% |
Expected skills students have coming into the course:
- E1. Students have a basic understanding of the fundamental concepts of software engineering: requirements, design, testing, life-cycle management, configuration management, and software engineering ethics.
Expected outcomes from taking this course:
- R1. Critique a software verification and validation plan as defined Montana Tech and/or industry standards (EAC-a, b, g, k, 1, 2, 3)
- R2. Create either a software verification and validation plan that conforms to Montana Tech and/or industry standards; and that a peer inspection team using the MTM Program Product Inspection Process will judge to be acceptable without rework. (EAC-a, b, e, g, k, 1, 2, 3)
- R3. Perform any of the inspection team roles defined in the MTM Program Product Inspection Process to inspect a software verification and validation plan as specified in the previous objective. (EAC-k, 1, 3)
- R4. Utilize best practice software verfication and validation static analysis and performance analysis tools. (EAC-a, b, e, i, k, 1, 2, 3, 4)
- R5. Accurately describe the various forms and purposes of software testing covered in the text, stanards, and other industry and academic acceptable sources. (EAC-b, e, g, i)
- R6. Carry out and report on any of the types of test covered in the text, the referenced standards, and other industry and academic acceptable sources. (EAC-a, b, e, g, i, k, 1, 2, 3, 4)
- R7. Accurately describe the importance of problem tracking. (EAC-g,i,k,1)
- R8. Accurately describe the importance of collecting and analyzing effort, defect, and defect severity data. (EAC-g, i, k, 1)
Related student outcomes:
- EAC-a An ability to apply knowledge of mathematics, science and engineering
- EAC-b An ability to design and conduct experiments, as well as to analyze and interpret data
- EAC-e An ability to identify, formulate and solve engineering problems
- EAC-g An ability to communicate effectively
- EAC-i A recognition of the need for and an ability to engage in life-long learning
- EAC-k An ability to use the techniques, skills and modern engineering tools necessary for engineering practice
- EAC-1 the ability to analyze, design, verify, validate, implement, apply and maintain software systems
- EAC-2 the ability to appropriately apply discrete mathematics, probability and statistics, and relevant topics in computer science and supporting disciplines to complex software systems
- EAC-3 the ability to work in one or more significant application domains
- EAC-4 the ability to manage the development of software systems