TÉCNICO SUPERIOR UNIVERSITARIO EN

TECNOLOGÍAS DE LA INFORMACIÓN Y
COMUNICACIÓN: ÁREA SISTEMAS INFORMÁTICOS

SOFTWARE ENGINEERING II

1. Competences To implement information systems quality through

advanced software development techniques to
streamline the processes of organizations.

2. Four month term Fifth

3. Theoretical hours 64
4. Practical hours 26
5. Total hours 90
6. Weekly hours 6
7. Learning objective: The student will develop an information system using
the techniques, methodologies and tools for design,
testing and release necessary to ensure the
implementation, according to customer requirements.

Hours
Learning Units
Theory Practice Total
I. Design of the User Interface 8 4 12
II. Documentation in the coding stage 12 6 18
III. Software tests 30 12 42
IV. Software release 14 4 18
Total 64 26 90

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

LEARNING UNITS

1. Learning unit I. Design of the User Interface

2. Theoretical hours 8
3. Practical hours 4
4. Total hours 12
The student will design an information system applying the
5. Learning unit
principles of usability, standards and style guides to improve ease
objective
of use.

Topics Knowledge Skills Values

Principles of Identify the principles of Designing an Analytical

Usability usability: information system Systematic
using usability Ability for teamwork
- Interaction principles. Ordered
- Consistency Ethical
- Ease of Learning Disciplined
- Feedback Leader
- Help
- Standardization
- Accessibility
To identify the types of Designing an Analytical
Standards and standards: information system Systematic
Style Guide using the jure and de Ability for teamwork
- iure facto standards and Ordered
- facto style guides. Ethical
Disciplined
To identify the style Leader
guides.

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

ASSESSMENT PROCESS

Learning outcome Learning Sequence Assessment instruments

The student will develop a 1. Understand the principles of Project
project based on a usability. Checklist
document containing:
2. Identify the standards and
• Design of the user style guides.
interface by applying
principles of usability, 3. Understand the standards
standards and style guides. and style guides.

• Justification for the use of 4. Develop strategies to

the style guide. implement the principles of
usability in the information
system.

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

LEARNING-TEACHING PROCESS

Teaching methods and techniques Teaching aids and materials

Project-based learning Blackboard
practical exercises Computer
collaborative teams Projector
Design software(programming language,
visio)

TRAINING FACILITIES

Classroom Laboratory / workshop Company

X

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

LEARNING UNIT
1. Learning unit II. Documentation in the coding stage
2. Theoretical
12
hours
3. Practical hours 6
4. Total hours 18
5. Learning unit The students will draw UML diagrams and documentation to
objective guide the coding stage in the development of software.

Topics Knowledge Skills Values

UML diagrams To identify elements of To develop component Planner

in coding component diagrams, diagrams, Analytical
implementation, implementation, Systematic
deployment and activity deployment and Ethical
activity. Coherent
Proactive
Teamwork
Able to synthesize
Skilled in verbal and
written communication
Documentatio To identify the Develop code using Planner
n in coding conventions of the own documentation Analytical
programming language conventions of Systematic
for documenting code language. Ethical
such as: Coherent
Proactive
- Naming variables, Teamwork
methods and constants Able to synthesize
- Internal documentation Skilled in verbal and
(ID of the class: name, written communication
description functionality,
creation date, version).
- Format (Indent).

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

Learning outcome Learning Sequence Assessment instruments

The students will develop 1. To identify elements of the Project
a project based on a diagrams that support the Checklist
document that includes: coding stage.

• Component Diagram 2. To understand the

• Deployment diagram conventions in documenting
• deployment diagram code.
• Activity diagram
• Documented Code 3. To analyze the use of
conventions in documenting
code.

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II
Teaching methods and techniques Teaching aids and materials
Project-based learning Blackboard
Collaborative teams Computer
Lab Practices Projector
UML tool (StarUML, Rational Rose, Umlet,
ArgoUML, Visual Paradigm)

TRAINING FACILITIES

Classroom Laboratory / workshop Company

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

1. Learning unit III. Software tests

2. Theoretical hours 30
3. Practical hours 12
4. Total hours 42
5. Learning unit Students will perform software testing using methodologies and
objective tools to detect and interpret errors

Topics Knowledge Skills Values

Types of To identify the concept Analytical

software testing of software testing and Systematic
target them. Ability for teamwork
Ordered
Disciplined
Creative
Test Cases To identify the scope of Designing software Analytical
the test procedure. test cases. Systematic
Ability for teamwork
To identify the structure Ordered
to document a test Disciplined
case. Creative
Tools for To identify the tools to Interpreting the results Analytical
software testing execute or simulate test of the execution of a Systematic
cases. test case using tools Ability for teamwork
for software testing. Ordered
Disciplined
Creative

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

ASSESSMENT PROCESS

Learning outcome Learning Sequence Assessment instruments

The student will develop a
project based on a
document that includes:
• Comparative table with
description of the types of
evidence.
• Test Cases.
• Interpretation of the results
obtained in implementing
them.
1. To identify the concept and Project
the types of evidence. Checklist
2. To understanding the
structure of a test case.
3. To analyze the tools to run
test cases.
4. To understand the process
for using a tool to run test
cases.

5. To interpret the results of the

execution of a test case.

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

LEARNING TEACHING PROCESS

Teaching methods and techniques Teaching aids and materials

Project Based Learning Whiteboard
Collaborative Teams PC
Lab practices Internet
Projector
Tool to execute software tests

TRAINING FACILITIES

Classroom Laboratory / workshop Company

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

1. Learning unit IV. Software release

2. Theoretical hours 14
3. Practical hours 4
4. Total hours 18
5. Learning unit The students will establish the technical documentation and
objective installation package for the release of the software.

Topics Knowledge Skills Values

Technical To identify elements of To develop a technical Analytical

Manual. a technical manual manual information Systematic
information system system. Ability for teamwork
Ordered
Disciplined

Installation To identify the plan and To develop the Analytical

Process. mechanism installation package. Systematic
instalación.de Ability for teamwork
installation. Ordered
Identify elements of Disciplined
Installation of an
information system.
User Manual To identify standards for To develop an user Analytical
the preparation of a manual based on a Systematic
manual. standard. Ability for teamwork
Ordered
Disciplined

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

Learning outcome Learning Sequence Assessment instruments

The student will develop a 1. To identify the structure of a Project
project based on: technical manual, installation Checklist
and user.
• User Manual
• Technical Manual 2. To understand the process to
• Installation Package create an installation package.

3. Structuring an installation
package.

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II

Teaching methods and techniques Teaching aids and materials

Project Based Learning Whiteboard
Collaborative Teams PC
Lab practices Internet
Projector
Support tools to generate installation disks

TRAINING FACILITIES

Classroom Laboratory / workshop Company

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II
CAPABILITIES DERIVED FROM THE PROFESSIONAL COMPETENCES WHICH
CONTRIBUTE TO THE SUBJECT
Capability
Encode modules collecting metrics and
using programming languages to meet
their functionality within the system.
To integrate the system modules
according to the design and set
technology, for optimal application
performance.
MADE BY:
APPROVED
C. G. U. T.
BY:
Performance Criteria
a) presents the source code of the system
modules:
- Based on the design set.
- According to the standards of the programming
language chosen.
- Compliance with good programming practices.
b) Generates code documentation specifying:
- Classes (dates, authors).
- Methods Arguments (objective) and
- Variables (data types, usability).
c) Records information for their own
development process:
- Number of defects injected and removed.
- Lines of code in time.
a) Encodes the corresponding interface that
generates the links between modules, following
the component model generated in the design.
b) Documents the generated interfaces,
specifying:
- Objective
- Relationships
- Parameters
- Date
- Author
- Etc.
CHECKED BY:
VALID SINCE: September, 2011
F-CAD-SPE-28-PE-5B-22
 Capability
To develop user manuals and technical
basis of the information generated in the
developmental stages and considering
the quality standards of the organization;
for proper operation and maintenance.
To design information systems based on
the architecture defined; to describe the
system components and how they
interact.
To release information system according
to a protocol of release and the project
plan for operation and tuning.
MADE BY: CHECKED BY:
APPROVED
C. G. U. T. VALID SINCE:
BY:
Performance Criteria
a) To generate the technical manual, integrating
and organizing documents generated:
- System Requirements.
- Analysis of complexity.
- Models and design documentation.
- Source.
- Evidence.
b) To make the manual using established
standards, drafting mode system operation and
its scope.
a) To generate models using unified modeling
language, and according to the system
requirements and documentation.
a) Establishes release protocol according to the
characteristics of the project and documents the
release of draft.
b) Generates the installation package (installers,
backups, aids, among others.)
September, 2011
F-CAD-SPE-28-PE-5B-22
 SOFTWARE ENGINEERING II
References

Author Year Document Title City Country Publisher

Committee (1998 IEEE recommended Washingto EE.UU. IEEE Computer
of the IEEE ) practice for software n Society
Computer requirements
Society. specifications (830-
1998).

Nielsen, (1993 Usability Engineering. California EE.UU. Morgan

Jakob. ) Kaufmann.
Academic Press

Pressman, (2008 Ingeniería de Madrid España McGrawHill

Roger S. ) Software

Rosson, (2002 Usability Engineering. Washingto EE.UU. Academic Press.

Mary Beth. ) n

S. Adler, (1992 Usability: Turning New York EE.UU. Oxford University

Paul. A. ) Technologies Into Press
Winograd, Tools.
Terry.

Sommerville (2005 Ingeniería de Madrid España Addison Wesley

, Ian. ) Software

Committee Enero, IEEE recommended Consultado http://ieeexplore.ieee.org/xpl/

of the IEEE 1998. practice for software : freeabs_all.jsp?
Computer requirements 25 de Junio tp=&arnumber=
Society specifications (830- 2009 720574&isnumber=15571
1998)

MADE BY: CHECKED BY:

APPROVED
C. G. U. T. VALID SINCE: September, 2011
BY:

F-CAD-SPE-28-PE-5B-22