software_engineering_proyect.pdf

1 of 12
Course title: Software Engineering Project
Course No.: 17844
School/College: Escuela Politécnica Superior
Degree: Computer Science Engineering
Level: Graduate
Type: Compulsory
ECTS: 6
SOFTWARE ENGINEERING PROJECT LEARNING GUIDE
This learning guide is for the Software Engineering Project Course, part of the
Bologna-compliant Undergraduate Degree in Computer Science and Engineering,
approved for the 2012/2013 academic year by the School Board and published on the
Universidad Autónoma de Madrid Escuela Politécnica Superior’s web site. Approved
and published ahead of the enrolment period, the Software Engineering Project
learning guide constitutes a learning agreement with the student.

2 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
COURSE TITLE
SOFTWARE ENGINEERING PROJECT (SEPRO)
1.1. Course number
17844 of the Undergraduate Degree in Computer Science and Engineering
1.2. Content area
Software Engineering
1.3. Course type
Compulsory
1.4. Course level
Undergraduate
1.5. Year
3rd
1.6. Semester
2nd (Spring/Summer semester)
1.7. Credit allotment
6 ECTS credits (2 class attendance + 4 non-class attendance)
1.8. Prerequisites
PREVIOUS KNOWLEDGE AND SKILLS REQUIRED TO TAKE THE COURSE
For students to be able to satisfactorily acquire the knowledge, abilities and skills
taught as part of the course, they should be practised at Spanish and English reading
comprehension and critique, using the electronic subject materials available on the
Moodle platform (http://uam-virtual.es), and actively searching and selecting
literature and supplementary material on the web and bibliographical resources
available at the Universidad Autónoma de Madrid. Students also require Spanish
report writing skills and a level of English language proficiency such that they are

3 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
able to understand the compulsory reading. Additionally, students will require
personal initiative, analytic and synthetic abilities, perseverance to understand,
practise and solve problems during the course. Students shall be eager to learn and
keen to develop a habit of independent study, as well as about group work. Finally,
students shall have to be enthusiastic about and supportive of cooperative teamwork,
which is an essential part of this course.
CO-REQUISITES AND RECOMMENDATIONS
The Software Engineering Project (SEPRO) and Software Engineering courses,
taught in the second semester of the third year of the Undergraduate Degree in
Computer Science and Engineering, are part of the Software Engineering content
area. The Software Analysis and Design and Software Analysis and Design Project
courses, taught in the second semester of the second year, are part of the Software
Analysis and Design content area. The Analysis and Design and Software Engineering
content areas are part of the Software Engineering module. Specifically, this module
is divided into four complementary semester-long courses: Software Analysis and
Design, Software Analysis and Design Project, Software Engineering and Software
Engineering Project (the first two are taught in the second year and the last two in
the third year). Therefore, students are required to perform satisfactorily in all four
courses to successfully pass the module.
The Software Engineering Project course is cross-curricularly related to the
Software Engineering course, because it supplements the knowledge, abilities and
attitudes learned by students of that course. SEPRO integrates the knowledge,
abilities and attitudes learned in the second-year Software Analysis and Design and
Software Analysis and Design Project courses. These four courses make up the
software engineering discipline, which manages, develops and supports quality
software system construction based on engineering. All these courses have similar
learning outcomes, competencies and contents.
To successfully pass the Software Engineering Project course, where students learn
a software project management approach, students should be taking the Software
Engineering course, where students learn a software project development integral
and supporting approach. Students are also expected to regularly attend the
practical, group and problem-solving, tool use and software project management
sessions.
1.9. Minimum attendance requirement
There are two assessment methods: continuous assessment (with compulsory class
attendance) and non-continuous assessment (without compulsory class attendance).
Students will have to decide on one option at the start of the course (first two
weeks) and meet the different assessment requirements set for each model.
CONTINUOUS ASSESSMENT WITH COMPULSORY CLASS ATTENDANCE
Attendance of at least 85% of face-to-face classes is compulsory.

4 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
NON-CONTINUOUS ASSESSMENT WITHOUT COMPULSORY CLASS ATTENDANCE
Attendance of at least 30% of face-to-face classes is compulsory. Students must
submit each deliverable of the software project that they are managing at a session
where they will be orally assessed on that part of their practical assignment.
1.10. Faculty data
Note: add @uam.es to all the listed email addresses.
Dr. Silvia Teresita Acuña (Coordinator)
Department of Computer Science and Engineering
Office – Module: B-331 Building B – 3rd
Floor
Phone: +34 91 497 2275
Email: silvia.acunna
Website: http://arantxa.ii.uam.es/~sacuna/is1/
Office hours: By email appointment.
Dr. Miren Idoia Alarcón
Floor
Phone: +34 91 497 2232
Email: idoia.alarcon
Website: http://arantxa.ii.uam.es/~ialarcon
Dra. Ruth Cobos Pérez
Office – Module: B-427 Building B – 4th
Floor
Phone: +34 91 497 2243
Email: ruth.cobos
Website: http://arantxa.ii.uam.es/~rcobos
Dr. Jesús Sánchez Cuadrado
Floor
Phone: +34 91 497 2251
Email: jesus.sanchez.cuadrado
Website: http://sanchezcuadrado.es

5 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
1.11. Course objectives
The purpose of the Software Engineering Project course is to instruct and involve
students in the management of quality software projects. It mainly focuses on the
study, analysis and use of software systems feasibility analysis and software project
management process activities, techniques and documents.
The aim of the SEPRO course is for students to be able to participate in any software
system management activity in an enterprise. Additionally, students learn through
SEPRO to distinguish software system lifecycle activities from existing software
process models and to apply key techniques and methods during the respective
software project management process activities. The aim behind this is to bring
students closer to the profession and software system management in industry,
learning the methods, techniques, procedures and tools required to manage quality
software system development for the different project management activities that
they will have to perform during their professional career. Also they will learn the
current state of the art with regard to software projects and software project
management methods and tools.
The common computing-related competencies that students acquire through the
Software Engineering Project subject are:
 C2. Ability to plan, design, deploy and manage projects, services and software
systems in all spheres, leading project startup and continuous improvement
and assessing their economic and social impact.
 C3. Ability to understand the importance of negotiation, effective work
habits, leadership and communication skills in all software development
environments.
The software engineering-specific technological competences that students
acquire through the Software Engineering Project course are:
 SE1. Ability to manage, develop, maintain and validate software services and
systems that satisfy all user requirements and behave reliably and efficiently,
are affordable to develop and maintain, and meet the quality standards,
applying software engineering theories, principles, methods and practices.
 SE2. Ability to assess customer needs and specify software requirements to
satisfy such needs, reconciling conflicting objectives by searching for
acceptable tradeoffs against constraints dictated by cost, time, developed
systems and the organization.
 SE4. Ability to identify and analyse problems and design, develop, implement,
verify, document and manage software solutions based on a satisfactory
knowledge of current theories, models and techniques.
 SE5. Ability to identify, evaluate and manage any potential risks.
The information systems-specific technological competencies that students acquire
through the Software engineering Project course are:

6 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
 IS2. Ability to determine the information systems and communication
requirements of an organization, taking into account security issues and in
compliance with the applicable standards and legislation.
The learning outcomes that students achieve through the Software Engineering
Project course are:
 Fundaments of management and integral software lifecycle activities.
Proficient use of the notations, techniques, methods and tools for performing
such activities.
 Knowledge of professional software engineering issues.
The general and specific goals of the Software Engineering Project course are as
follows.
The general goals of SEPRO are for students to be able, by the end of the course,
to:
G.1) Write a quality professional technical report.
G.2) Distinguish between software process management, technical and
supporting viewpoints.
G.3) Explain the importance of the management, technical and supporting
activities for a successful software process.
G.4) Describe the standard software process models.
G.5) List the feasibility study activities.
G.6) Distinguish between the activities involved in the software
management and leadership processes.
G.7) Apply software project management methods.
G.8) Apply software project estimation and planning techniques.
G.9) Prepare a quality software project management plan.
G.10) Identify the key risk analysis activities for proper software project
management.
G.11) Apply software project risk analysis and management techniques.
G.12) Prepare a risk management and supervision plan.
G.13) Show an interest and initiative in searching, organizing and critically
analysing key information as a means of learning and decision making
to achieve the goals specified as a result of participatory techniques,
practical assignments and team software project.
G.14) Actively participate in team analyses and discussions prompted by
program development and cooperate with peers on the software
engineering project development.
G.15) Communicate personal ideas, individual and group considerations, and
the results of the managed project to others properly and correctly
both in writing and orally.
The specific objectives of SEPRO are for students to be able, by the end of the
course, to:

7 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
UNIT 1: SOFTWARE ENGINEERING COMMUNICATION TECHNIQUES
1.1) Explain the importance of communication and the role that interpersonal
competencies play in software engineering.
1.2) Describe the phases for writing a technical report.
1.3) Detail the software engineering information/knowledge acquisition
process.
UNIT 2: SOFTWARE PROCESS
2.1) Define and characterize the software process concept.
2.2) List the process, project and product concepts as the groundwork of the
course.
2.3) Identify and list the activities involved in the software development
process and distinguish between technical and management activities.
2.4) Identify, list and distinguish between the activities involved in the
Software Engineering Project course and the Software Engineering
course.
2.5) Select the best software process model for each software project.
2.6) Structure and prepare a feasibility document.
UNIT 3: PROJECT MANAGEMENT AND LEADERSHIP PROCESSES
3.1) List the activities involved in the project management and leadership
processes.
3.2) Describe key software project management activities.
3.3) Participate in any software project management activity in industry.
UNIT 4: SOFTWARE PROJECT ESTIMATION AND PLANNING
4.1) Distinguish between management, technical and supporting activities for
successful software project enactment.
4.2) Distinguish software project management from project management in
other disciplines.
4.3) Explain the importance of the software engineering discipline for assuring
the systematic production and maintenance of software products
developed on time and within budget.
4.4) Characterize and explain the importance of software development
project estimation and planning activities.
4.5) Describe the major software project decomposition and empirical
estimation techniques.
4.6) Apply the estimation techniques in realistic projects.
4.7) Apply software project planning techniques.
4.8) Use collaborative tools, such as Google Docs, to support teamwork.
4.9) Distinguish between software project estimation tools (e.g., CoStar) and
planning tools (e.g., Microsoft Project).
4.10) Use software project planning tools such as Microsoft Project.
4.11) Define the structure and content of the project plan.

8 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
4.12) Develop negotiating skills that are fundamental for managing software
projects and, generally, for developing a software system.
UNIT 5: SOFTWARE PROJECT RISK MANAGEMENT
5.1) Identify and write risks according to risk taxonomies.
5.2) Realistically assess risk likelihood and impact.
5.3) Prepare risk management plans.
5.4) Structure risk monitoring procedures.
1.12. Course contents
PROGRAMME OUTLINE
This course takes an engineering approach and is based on the use of software
project management procedures, methods, techniques and tools. Additionally,
active student participation is essential, as they have not only to analyse but also
to implement project planning. The aim of this course is for students to be able
to actively, effectively and efficiently participate in any software project
management activity to improve their contribution to professional projects in the
future. This course aims not only to transmit knowledge but also to develop
students’ ability to manage software projects faster and better than they had
been able to do before, encouraging the exchange of ideas through cooperative
work, motivating students to learn and promoting social interaction in order to
use project management tools and software systems development estimation,
planning, monitoring and control and risk management. Note that the course units
are not strictly sequential, and are interrelated to each other, feed back into
each other and can be arranged in a different order.
The course has been divided into the following five units:
UNIT 1. SOFTWARE ENGINEERING COMMUNICATION TECHNIQUES
UNIT 2. SOFTWARE PROCESS
UNIT 3. PROJECT MANAGEMENT AND LEADERSHIP PROCESSES
UNIT 4. SOFTWARE PROJECT ESTIMATION AND PLANNING
UNIT 5. SOFTWARE PROJECT RISK MANAGEMENT
DETAILED PROGRAMME
The topics covered by the learning process have been defined for all five units.
The Software Engineering Project course is structured as shown below.
1. SOFTWARE ENGINEERING COMMUNICATION TECHNIQUES
1.1 The software engineer as a communicator
1.2. The communication problem in software engineering
1.3. Basic communication techniques in software engineering
1.3.1. Technical reports, meetings, interviews, presentations
1.3.2. Phases for preparing technical reports

9 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
1.3.3. Requirements elicitation techniques: brainstorming,
interviewing/surveys
1.3.4. User analysis techniques: site visits, scenarios/storyboards
1.3.5. Requirements representation techniques: paper prototypes, software
prototypes, mock-ups
1.3.6. Structure of presentations
1.3.7. Documentation: technical reports
2. SOFTWARE PROCESS
2.1. Software process definition
2.2. Process, project and product
2.3. Software process roles
2.4. Software process models
2.5. Classification of software process models
2.6. Software process model: IEEE Standard 1074
2.7. Relationship between Software Engineering Project and Software Engineering
courses
2.8. Software process model: Unified Process
2.9. Feasibility study process
2.9.1. Definition and goals
2.9.2. Scope
2.9.3. Technical considerations
2.9.4. Cost/benefit analysis
2.9.5. Activities
2.9.6. Decision-making criteria
2.9.7. Final feasibility document
3. PROJECT MANAGEMENT AND LEADERSHIP PROCESSES
3.1. Definitions, scope and goals
3.2. Project manager responsibilities
3.3. Activities
3.3.1. Negotiation
3.3.2. Monitoring
3.3.3. Management
3.3.4. Work team coordination
3.3.5. Technical leadership
3.4. Key project management activities: estimation, planning and monitoring, and
control
3.5. Sources of support and help tools
4. SOFTWARE PROJECT ESTIMATION AND PLANNING
4.1. Definitions
4.2. Estimation
4.3. Estimation issues
4.4. Estimation elements
4.5. Estimation techniques
4.6. Decomposition techniques
4.6.1. Matrix Model

10 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
4.6.2. Hierarchical Model
4.7. Empirical techniques
4.7.1. Function Points
4.7.2. COCOMO
4.7.3. COCOMO II
4.8. Automated estimation tools
4.9. Costs
4.10. Planning
4.11. Resource planning
4.12. Scheduling
4.13. Automated planning tools
4.14. Development team
4.15. Planner profile
4.16. Common mistakes
4.17. Documentation: Project plan
5. SOFTWARE PROJECT RISK MANAGEMENT
5.1. Definitions
5.2. Risk analysis and management strategies
5.3. Types of risk
5.4. Common problems
5.5. Activities
5.5.1. Risk identification
5.5.2. Risk estimation
5.5.3. Risk assessment
5.5.4. Risk management
5.5.5. Risk monitoring
5.6. Documentation: Risk management and supervision plan
1.13. References
The learning resources are detailed by unit below. A distinction is made between
compulsory and recommended reading.
UNIT 1: SOFTWARE ENGINEERING COMMUNICATION TECHNIQUES
Compulsory reading:
 J.-P. Berrou, Para Escribir Bien en la Empresa. (Deusto, 1992).
 D. Cassany. La Cocina de la Escritura. (Anagrama, 2004).
 R. S. PRESSMAN. Ingeniería del Software. Un Enfoque Práctico. 6ª Edición.
(McGraw Hill, 2005). Part II “Práctica de la Ingeniería del Software”: Chapter
5.
 Slides at http://www.uam-virtual.es/ .
Recommended reading:
 Materials by the Writing Center, University of Wisconsin, Madison, available
at: http://www.wisc.edu/writing/

11 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
UNIT 2: SOFTWARE PROCESS
Compulsory reading:
(McGraw Hill, 2005). Parte I “El Proceso del Software”: Chapters 2, 3 and 4.
Part IV “Gestión de Proyectos de Software”: Chapter 23. Or:
 I. SOMMERVILLE. Ingeniería del Software. 7ª Edición. (Pearson Educación,
2005). Chapters 4 and 5.
 S. T. ACUÑA, N. JURISTO, A. M. MORENO, A. MON. A Software Process Model
Handbook for Incorporating People’s Capabilities. (Springer, 2005). Chapters
1, 2, 3, 4 and 5.
 IEEE Standard 1074-1997. IEEE Standard for Developing Software Life Cycle
Processes. 1997.
 Slides at http://www.uam-virtual.es/
 S. T. ACUÑA. Proceso Software. (EPS-UAM, 2009).
 I. JACOBSON, G. BOOCH, J. RUMBAUGH. El Proceso Unificado de Desarrollo de
Software. (Addison Wesley, 2000).
 M. PIATTINI, J. A. CALVO-MANZANO, J. CERVERA, L. FERNÁNDEZ. Análisis y
Diseño de Aplicaciones Informáticas de Gestión. (Ra-Ma, 1996).
 G. CABRERA, M. MONTOYA. Análisis y Diseño Detallado de Aplicaciones
Informáticas de Gestión. Ciclo Formativo Grado Superior. (McGraw Hill, 1999).
UNIT 3: PROJECT MANAGEMENT AND LEADERSHIP PROCESSES
Compulsory reading:
(McGraw Hill, 2005). Part IV “Gestión de Proyectos de Software”: Chapter 21.
2005). Chapter 5.
 A. ALAN, J. W. MOORE, P. BOURQUE, R. DUPUIS. SWEBOK: Guide to the
Software Engineering Body of Knowledge. 2004 Version. (IEEE-CS, 2004).
http://www.computer.org/portal/web/swebok
 E. M. BENNATAN. On Time, Within Budget. Software Project Management
Practices and Techniques. 2nd Edition. (John Wiley & Sons, 1995).
 L. L. CONSTANTINE. “Work organization: Paradigms for project management
and organization”. Communications of the ACM, Vol.36, No.10, 1993, pp. 35-
43.
 M. MANTEI. “The effect of programming team structures on programming
tasks”. Communications of the ACM, Vol.24, No.3, 1981, pp. 106-113.
 J. S. REEL. “Critical success factors in software projects”. IEEE Software,
Vol.16, No.3, May-June 1999, pp. 18-23.

12 of 12
Course No.: 17844
Level: Graduate
Type: Compulsory
ECTS: 6
UNIT 4: SOFTWARE PROJECT ESTIMATION AND PLANNING
Compulsory reading:
(McGraw Hill, 2005). Part IV “Gestión de Proyectos de Software”: Chapters 23
and 24. Or:
2005). Chapters 5, 25 and 26.
 B. W. BOEHM. Software Engineering Economics. (Prentice Hall, 1981). Or:
 F. P. BROOKS. The Mythical Man-Month. (Addison Wesley, 1995).
 Tutorial on the Microsoft Project planning tool at http://www.uam-virtual.es/
 A. J. ALBRECHT, J. E. GAFFNEY. “Software function, source lines of code, and
development effort prediction: A software science validation”. IEEE
Transactions on Software Engineering, Vol.9, No.6, November 1983.
 G. D. CARTER, C. P. CLARE, D. C. J. THOROGOOD. “Engineering project
management techniques and their application to computer projects”.
Software Engineering Journal, Vol.2, No.1, January 1987, pp.145-150.
 B. W. BOEHM. “Software engineering economics”. IEEE Transactions on
Software Engineering, Vol.10, No.1, January 1984.
 B. W. BOEHM, B. CLARK, E. HOROWITZ, R. MADACHY, R. SHELBY, C.
WESTLAND. “Cost models for future software life cycle processes: COCOMO
2.0”. Annals of Software Engineering. 1995.
UNIT 5: SOFTWARE PROJECT RISK MANAGEMENT
Compulsory reading:
(McGraw Hill, 2005). Part IV “Gestión de Proyectos de Software”: Chapter 25.
2005). Chapter 5.
 E. M. Hall. Managing Risk Methods for Software Systems Development.
(Addison-Wesley, 1998).
 T. DeMARCO, T. LISTER. Waltzing with Bears: Managing Risk on Software
Projects. (Dorset House, 2003).
 D. W. KAROLAK. Software Engineering Risk Management. (IEEE Computer
Society Press, 1996).
 J. Ropponen, K. Lyytinen. “Components of software development risk: How to
address them? A Project manager survey”. IEEE Transactions on Software
Engineering, Vol.26, No.2, February 2000, pp. 98-112.

software_engineering_proyect.pdf

Recommended

Recommended

More Related Content

Similar to software_engineering_proyect.pdf

Similar to software_engineering_proyect.pdf (20)

More from ssuser4d4e5a

More from ssuser4d4e5a (8)

Recently uploaded

Recently uploaded (20)

software_engineering_proyect.pdf