MSc: Analysis Software Artifacts - Revision history

R.sirgalina at 09:04, 29 August 2022

2022-08-29T09:04:17Z

M.petrishchev at 08:08, 26 April 2022

2022-04-26T08:08:29Z

← Older revision		Revision as of 08:08, 26 April 2022
Line 18:		Line 18:
	Software quality is a key aspect of any IT solution whether a few hundred lines of code for a smart phone app or a few million lines of code for Enterprise Resource Planning software. The Analysis of Software Artifacts course provides techniques to develop confidence in the quality of the software being produced or acquired regardless of its size and domain. The course adopts the view that software quality is not only the absence of defects but that it encompasses all the characteristics that bear on the ability of the software to satisfy stated and implied needs. Software quality is then defined from different perspectives: product quality, quality in use and process quality through the use of specific quality models. The course systematically explores different quality attributes and the techniques most appropriate to verify them. Specific topics include software testing, static analysis and model checking, inspections, technical debt, cost of software quality, planning for quality, quantitative models and defect classifications. The course balances traditional lectures with small projects in which students apply the ideas they are learning to real artifacts. The final project consists on the preparation of a quality plan for an industry project.		Software quality is a key aspect of any IT solution whether a few hundred lines of code for a smart phone app or a few million lines of code for Enterprise Resource Planning software. The Analysis of Software Artifacts course provides techniques to develop confidence in the quality of the software being produced or acquired regardless of its size and domain. The course adopts the view that software quality is not only the absence of defects but that it encompasses all the characteristics that bear on the ability of the software to satisfy stated and implied needs. Software quality is then defined from different perspectives: product quality, quality in use and process quality through the use of specific quality models. The course systematically explores different quality attributes and the techniques most appropriate to verify them. Specific topics include software testing, static analysis and model checking, inspections, technical debt, cost of software quality, planning for quality, quantitative models and defect classifications. The course balances traditional lectures with small projects in which students apply the ideas they are learning to real artifacts. The final project consists on the preparation of a quality plan for an industry project.

−	=== Course Objectives Based on Bloom’s Taxonomy ===	+	== Course Objectives Based on Bloom’s Taxonomy ==

	== Prerequisites ==		== Prerequisites ==
Line 37:		Line 37:
	* Any video materials on Software Quality Assurance will go.		* Any video materials on Software Quality Assurance will go.

−	=== - What should a student remember at the end of the course? ===	+	=== What should a student remember at the end of the course? ===

	By the end of the course, the students will remember:		By the end of the course, the students will remember:
Line 47:		Line 47:
	* Cost of quality.		* Cost of quality.

−	=== - What should a student be able to understand at the end of the course? ===	+	=== What should a student be able to understand at the end of the course? ===

	By the end of the course, the students should be able to describe and explain (with examples)		By the end of the course, the students should be able to describe and explain (with examples)
Line 56:		Line 56:
	* Quality planning.		* Quality planning.

−	=== - What should a student be able to apply at the end of the course? ===	+	=== What should a student be able to apply at the end of the course? ===

	By the end of the course, the students should be able to		By the end of the course, the students should be able to

M.petrishchev: /* Prerequisites */

2022-04-21T06:42:19Z

Prerequisites

← Older revision		Revision as of 06:42, 21 April 2022
Line 25:		Line 25:
	* Software testing basics		* Software testing basics
	* Notions of coverage		* Notions of coverage
		+
		+	To catch up with these topics you can use the following materials:
		+	* Naik, Kshirasagar, and Priyadarshi Tripathy. [https://www.wiley.com/en-us/Software+Testing+and+Quality+Assurance%3A+Theory+and+Practice-p-9781118211632 Software testing and quality assurance: theory and practice]. John Wiley & Sons, 2011.
		+	Whittaker, James A., Jason Arbon, and Jeff Carollo. [https://books.google.ru/books/about/How_Google_Tests_Software.html?id=vHlTOVTKHeUC&redir_esc=y How Google tests software]. Addison-Wesley, 2012.
		+	Any video materials on Software Quality Assurance will go.
		+
	== Recommendations for students on how to succeed in the course ==		== Recommendations for students on how to succeed in the course ==
	To catch up with these topics you can use the following materials:		To catch up with these topics you can use the following materials:

R.akhmetzyanov: /* Prerequisites */

2022-04-18T07:52:26Z

Prerequisites

@@ Line 25: / Line 25: @@
 * Software testing basics
 * Notions of coverage
 == Recommendations for students on how to succeed in the course ==
 To catch up with these topics you can use the following materials:

R.akhmetzyanov: /* Prerequisites */

2022-04-18T07:51:58Z

Prerequisites

← Older revision		Revision as of 07:51, 18 April 2022
Line 25:		Line 25:
	* Software testing basics		* Software testing basics
	* Notions of coverage		* Notions of coverage
		+	== Recommendations for students on how to succeed in the course ==
	To catch up with these topics you can use the following materials:		To catch up with these topics you can use the following materials:
	* Naik, Kshirasagar, and Priyadarshi Tripathy. [https://www.wiley.com/en-us/Software+Testing+and+Quality+Assurance%3A+Theory+and+Practice-p-9781118211632 Software testing and quality assurance: theory and practice]. John Wiley & Sons, 2011.		* Naik, Kshirasagar, and Priyadarshi Tripathy. [https://www.wiley.com/en-us/Software+Testing+and+Quality+Assurance%3A+Theory+and+Practice-p-9781118211632 Software testing and quality assurance: theory and practice]. John Wiley & Sons, 2011.

M.petrishchev: M.petrishchev moved page MSc:Analysis Software Artifacts to MSc: Analysis Software Artifacts

2022-04-15T08:43:57Z

M.petrishchev moved page MSc:Analysis Software Artifacts to MSc: Analysis Software Artifacts

← Older revision	Revision as of 08:43, 15 April 2022
(No difference)

M.petrishchev: /* Prerequisites */

2022-04-13T13:27:47Z

Prerequisites

← Older revision		Revision as of 13:27, 13 April 2022
Line 29:		Line 29:
	* Whittaker, James A., Jason Arbon, and Jeff Carollo. [https://books.google.ru/books/about/How_Google_Tests_Software.html?id=vHlTOVTKHeUC&redir_esc=y How Google tests software]. Addison-Wesley, 2012.		* Whittaker, James A., Jason Arbon, and Jeff Carollo. [https://books.google.ru/books/about/How_Google_Tests_Software.html?id=vHlTOVTKHeUC&redir_esc=y How Google tests software]. Addison-Wesley, 2012.
	* Any video materials on Software Quality Assurance will go.		* Any video materials on Software Quality Assurance will go.
−

	=== - What should a student remember at the end of the course? ===		=== - What should a student remember at the end of the course? ===

M.petrishchev at 08:27, 11 April 2022

2022-04-11T08:27:26Z

← Older revision		Revision as of 08:27, 11 April 2022
Line 19:		Line 19:

	=== Course Objectives Based on Bloom’s Taxonomy ===		=== Course Objectives Based on Bloom’s Taxonomy ===
		+
		+	== Prerequisites ==
		+
		+	Here are prerequisites for the ASA course:
		+	* Software testing basics
		+	* Notions of coverage
		+	To catch up with these topics you can use the following materials:
		+	* Naik, Kshirasagar, and Priyadarshi Tripathy. [https://www.wiley.com/en-us/Software+Testing+and+Quality+Assurance%3A+Theory+and+Practice-p-9781118211632 Software testing and quality assurance: theory and practice]. John Wiley & Sons, 2011.
		+	* Whittaker, James A., Jason Arbon, and Jeff Carollo. [https://books.google.ru/books/about/How_Google_Tests_Software.html?id=vHlTOVTKHeUC&redir_esc=y How Google tests software]. Addison-Wesley, 2012.
		+	* Any video materials on Software Quality Assurance will go.
		+

	=== - What should a student remember at the end of the course? ===		=== - What should a student remember at the end of the course? ===

M.petrishchev: M.petrishchev moved page MSc:AnalysisSoftwareArtifacts.S22 to MSc:Analysis Software Artifacts

2022-04-10T12:37:40Z

M.petrishchev moved page MSc:AnalysisSoftwareArtifacts.S22 to MSc:Analysis Software Artifacts

← Older revision	Revision as of 12:37, 10 April 2022
(No difference)

I.konyukhov: I.konyukhov moved page MSc:AnalysisSoftwareArtifacts to MSc:AnalysisSoftwareArtifacts.S22

2021-11-14T17:23:24Z

I.konyukhov moved page MSc:AnalysisSoftwareArtifacts to MSc:AnalysisSoftwareArtifacts.S22

← Older revision	Revision as of 17:23, 14 November 2021
(No difference)