Autenticação

Utilizador:

Senha:

Iniciar sessão

Esqueceu-se da senha?

Software Engineering I

Code:

TINF20

Sigla:

ESI

Áreas Científicas
Classificação	Área Científica
OFICIAL	Ciências Informáticas

Ocorrência: 2022/2023 - 2S

Ativa?	Yes
Unidade Responsável:	Departamento de Sistemas e Informática
Curso/CE Responsável:	Professional Technical Higher Education Courses in Informatics Technologies (Turma do Programa BrightStart)

Ciclos de Estudo/Cursos

Sigla	Nº de Estudantes	Plano de Estudos	Anos Curriculares	Créditos UCN	Créditos ECTS	Horas de Contacto	Horas Totais
TINFT	20	Plano Estudos_2018_19	1	-	6	60	162

Língua de trabalho

Portuguese

Objetivos

C1. LEARNING OUTCOMES OF THE COURSE UNIT

This course unit aims to provide students with knowledge about:

• Modeling of business processes supported by an information system, using the BPMN (Business Process Model and Notation) language;

• Information systems modeling, using object-oriented analysis and design and the UML (Unified Modeling Language).

 

 

Resultados de aprendizagem e competências

At the end of the course unit the student should be able to:

• Explain the importance of modeling information systems, and know how to relate the concepts: model, modeling and information system;

• Explain the importance of modeling an organization's business processes in the process of developing an information system;

• Model a business process using the BPMN language;

• Identify the relationship between the modeling of an organization's business processes and the modeling of an information system;

• Identify and apply different techniques to survey, analyze and specify requirements for an information system;

• Identify and apply several techniques to analyze and model an information system, using the UML to specify the analyzed system;

• Identify and apply different techniques to design an information system, using the UML language to specify the system to be developed.

Modo de trabalho

Presencial

Programa

1. Introduction to the concepts of modeling an information system
1.1. Concept of System, Information, Models, and Modeling Language
1.2. Development Process of an Information System
2. Business Process Modeling
2.1. The business processes of organizations and their relationship with information systems.
2.2. Specification and a Business Process
2.3. BPMN as a business process modeling language.
2.4. Modeling the business processes of organizations in the process of developing an information system
3. Survey and Specification of Information System Requirements
3.1. Functional and non-functional requirements
3.2. Requirements Gathering Techniques
3.3. Analysis and Specification of Functional Requirements
3.4. Use Case and Use Case Detail Diagrams for specifying the functionalities of an information system
3.5. Activity Diagram for modeling user interaction with the system
4. Information System Analysis
4.1. Discovery of informational entities that support the system to be built
4.2. Modeling of informational entities using the UML Class and Object Diagram.
4.3. Modeling of the dynamic component of the system. Realization of Use Cases, using UML sequence diagrams, use of state machine diagrams.

 

Bibliografia Obrigatória

Fowler, M. and Scott, K. ; UML Distilled: A Brief Guide to the Standard Object Modeling Language. 3rd ed. , Addison-Wesley Professional, 2003
Borges, J., Cunha, J. and Dias, T. ; Modelação de dados em UML – uma abordagem por problemas, FCA, 2015
Nunes, M., O’Neill, H. ; Fundamental de UML, FCA, 2004

Métodos de ensino e atividades de aprendizagem

·      In Theoretical Classes (T) expository and participatory methods are used in order to promote discovery learning, through individual and group exploration. Therefore, the dynamics of these classes consist of exposing the material followed by problem solving;

·      In the Practical/Laboratory (PL) classes, the participative and work-solving method will be used, providing the development of know-how skills, for a closer approximation of theoretical-practical teaching to the demands of the labor market. Thus, and in terms of dynamics, these classes will be conducted according to the pedagogical methodology problem/project based learning, where students, in groups of 3, will develop the analysis and specification of an information system. For each laboratory class there will be a set of specific objectives to be fulfilled by each working group, whose mission is to guide students in the development of the project. The resulting practical work is submitted and evaluated weekly.

Software

Bizagi Modeler

Tipo de avaliação

Distributed evaluation without final exam

Componentes de Avaliação

Designation	Peso (%)
Participação presencial	10,00
Teste	40,00
Trabalho escrito	50,00
Total:	100,00

Componentes de Ocupação

Designation	Tempo (Horas)
Elaboração de projeto	62,00
Frequência das aulas	60,00
Trabalho escrito	40,00
Total:	162,00

Obtenção de frequência

A)          Continuous evaluation (mandatory)

The continuous evaluation (CE) grade is calculated as follows:

 

Final grade of CE = TC (40%) + PC (60%)

 Considering that: 

• Theoretical Component (TC) - The TC component, which has a weight of 40% in the calculation of the final grade, is evaluated through the elaboration of 2 theoretical tests (Test1 and Test2), both with the same weighting (50%), and each of them with a minimum score of 9.5 values. The minimum TC grade is 9.5 and is calculated as follows: 

TC = Test1 (50%) + Test2 (50%) 


• Practical Component (PC) - The PC component, which has a weight of 60% in the calculation of the final grade, is evaluated by carrying out:

a) 1 project (worth 50%) to be carried out in groups of 3 students, with a minimum grade of 9.5 points, both in the final project and in the individual discussion. This project has 2 required partial deliveries, both with no minimum grade.

b) individual exercises carried out in class (Exer) - 10%

The minimum PC Grade is 9.5 and is calculated as follows: 


PC = Project (50%) + Class exercises (10%)

 

If any of the grades is lower than the minimum values ​​described above, the student will have to take, in the evaluation exam, only the evaluation component(s) that he/she has failed. NOTE: the components will always maintain their percentage value, that is: TC (40%) + PC (60%) for the purpose of calculating the student's final grade. With regard to attendance: in this program attendance is mandatory and it is necessary to provide justification for absences. The minimum number of attendances to obtain approval is 75%.

Fórmula de cálculo da classificação final

A)          Final evaluation 

Normal and appeal seasons:

The evaluation of the regular season and the appeal season is constituted by the elaboration of an Exam with the 2 components: TC (40%) + PC (60%), both with a minimum grade of 9.5 values. To make the TC, the student will have to do a written theoretical exam. To make the CP the student:

1. a) reformulates the project if it has failed in continuous assessment;


2. b) or will develop a project whose theme will be made available in the last week of classes.

NOTE: students will only make in the exam, the component(s) that they have previously failed in the continuous evaluation.