Universidad de Jaén

Menú local

Syllabus 2016-17 - 13312004 - Software Quality (Calidad del software)

Caption
  • Level 1: Tutorial support sessions, materials and exams in this language
  • Level 2: Tutorial support sessions, materials, exams and seminars in this language
  • Level 3: Tutorial support sessions, materials, exams, seminars and regular lectures in this language
DEGREE: Grado en Ingeniería informática
FACULTY: SCHOOL OF ENGINEERING OF JAÉN
ACADEMIC YEAR: 2016-17
COURSE: Software Quality
SYLLABUS
1. COURSE BASIC INFORMATION
NAME: Software Quality
CODE: 13312004 ACADEMIC YEAR: 2016-17
LANGUAGE: English LEVEL: 3
ECTS CREDITS: 6.0 YEAR: 3 SEMESTER: SC
2. LECTURER BASIC INFORMATION
NAME: GÓMEZ ESPINOLA, JOSÉ IGNACIO
DEPARTMENT: U118 - INFORMÁTICA
FIELD OF STUDY: 570 - LENGUAJES Y SISTEMAS INFORMÁTICOS
OFFICE NO.: A3 - 122 E-MAIL: nacho@ujaen.es P: 953212382
WEBSITE: http://www4.ujaen.es/~nacho
ORCID: https://orcid.org/0000-0003-0230-3307
LANGUAGE: English LEVEL: 3
3. CONTENT DESCRIPTION

Part I. Quality Management

  • Quality Concepts
  • Quality Models and Standards
  • Computer Systems Quality
  • SQuaRE: the ISO 25000 standards family
  • Featured Quality Management Websites

Part II. Verification and Validation

  • Software Testing and Debugging
  • Verification and Validation Planning
  • Software Inspections
  • Automated Static Code Analysis Tools
  • Verification and Formal Methods

Part III. Software Testing

  • Software Testing Strategies
  • Unit Testing
  • Integration Testing
  • Validation Testing
  • Acceptance Testing
  • System Testing
  • The Debugging Process
  • White Box Testing
  • Black Box Testing
  • Software testing Tools

Part IV. Software Metrics

  • Fundamentals of Measurement Process
  • Size and Complexity Metrics
  • Metrics for Object-Oriented Systems
  • Software Maintenance Metrics
  • Software Metrics Tools

Practices

Students will have the chance of working with the next practice program:

  • Selecting and Documenting Projects
  • Application of Coding Standards
  • Automated Static Code Analysis
  • Applying Software Metrics
  • Quality Assurance for Web Development

4. COURSE DESCRIPTION AND TEACHING METHODOLOGY

Lectures

Next activities will be held:

  • Master classes
  • Theory and examples
  • Exercises resolution made by pupils aided by lecturer

Practical sesions

  • Practices at computer lab

Large group mentoring

Next activities will be held:

  • Doubts solving
  • Revision of works and exercises

Students with special educational needs should contact the Student Attention Service (Servicio de Atención y Ayudas al Estudiante) in order to receive the appropriate academic support

5. ASSESSMENT METHODOLOGY

Competencies for Assessment System:

  • S1 (attendance and participation): CIS1, CIS4
  • S2 (theory assessment): CIS1, CIS4
  • S3 (exercises and work): CIS1, CIS4
  • S4 (practice assessment): CIS1, CIS4

Results for Assessment System:

  • S1 (attendance and participation): 1,2,3,4,5,6,7,9
  • S2 (theory assessment): 1,2,3,4,5,6,10
  • S3 (exercises and work): 1,2,3,4,5,6,7,9
  • S4 (practice assessment): 1,2,5,6,7,8

Detailed description:

A global assessment of the subject will be held, dividing the score in the following sections:

-Theory (up to 4 points): writting test. You have to reach at least 2 points to have a chance to add other scores

- Practices (up to 3 points): practices development at computer lab. You have to reach at least 1.5 points to have a chance to add other scores

- Lectures attendance: up to 0.5 points

- Practices attendance: up to 0.5 points

- Participation on exercises solving and publication on the wiki of this course: up to 2 points. The number of exercises needed to get this maximum score will be decided by the professor during the first eight weeks of the course, depending on the number of students participating on this part of the course evaluation. Furthermore, the student that is able to solve and upload to the wiki this number of exercises, and additionally is able to solve and upload to the wiki an extra number of exercises equivalent at least to the 50% of the number of exercises needed to get the maximum score (2 points), will receive 1 extra point. The extra point reached can be used in two alternative ways: (1) It can be exchanged for 2 points in the written exam and then the student won't need to solve the exam. (2) The student decides to solve the exam and then the extra point will be added to the final score in the course (until a maximum score of 10 points). In this case, it's important to take into account that the condition of getting at least 2 points in the exam keeps active to pass the course.

In order to pass you have to reach at least 2 points at theory, 1.5 at practises and at least 5 points in the sum of the all evaluable sections.

In order to pass the extraordinary call, it is mandatory to pass the practical part during the ordinary call.

In the extraordinary call, only section Theory (written exam) will be evaluated, giving option to obtain up to 4 points. To ensure the option to obtain the maximum possible score in this call (according to the Academic System and Regulations of Student Assessment at the University of Jaen, approved by the Council of Government No. 33, of 21.11.2013), the score obtained in the remaining evaluable sections (attendance, practices and participation) during the last ordinary call will be added to the score obtained in the written exam for this extraordinary call

6. BOOKLIST
MAIN BOOKLIST:
  • Software Engineering: A Practitioner's Approach. Edition: 8th Edition. Author: Pressman, Roger S. Publisher: McGraw-Hill  (Library)
  • Software Engineering. Edition: 9th Edition. Author: Sommerville, Ian. Publisher: Pearson  (Library)