Subject: Modeling and Rapid Software Development
Scientific area:
Computer Science
Contact hours:
56 Hours
Number of ECTS:
4,5 ECTS
Language:
Portuguese
General Objectives:
1 - Learn to model, both generically and as applied to information systems, particularly from the perspectives of the company, business, user, software, and hardware.
2 - Model the most important components of a software system, namely interface, business logic, and data, tracing their relationship with the business and enterprise architecture.
3 - Apply different modeling methods and notations, understanding common and recurring concepts, the possible relationships between them, and distinguishing between functional and non-functional requirements.
4 - Develop information systems using rapid development tools, namely no-code and low-code.
2 - Model the most important components of a software system, namely interface, business logic, and data, tracing their relationship with the business and enterprise architecture.
3 - Apply different modeling methods and notations, understanding common and recurring concepts, the possible relationships between them, and distinguishing between functional and non-functional requirements.
4 - Develop information systems using rapid development tools, namely no-code and low-code.
Contents / Syllabus:
1 - Object-Oriented Modeling
1.1 - Unified Modeling Language (UML)
1.2 - Concepts of objects, classes, stereotypes, methods, attributes
1.3 - Concepts of association, dependency, aggregation, inheritance, and information flow
1.4 - Class, activity, and sequence diagrams
1.5 - Modeling Practice
2 - Information Systems Modeling
2.1 - Functional and Non-Functional Requirements
2.2 - Business Modeling
2.3 - Business Process and User Modeling (Profiling, Persona)
2.4 - User Task and User Interface Modeling
2.5 - Business Logic and Data Modeling
2.6 - Software Architecture Modeling
3 - Business Structure Modeling
3.1 - Hardware Modeling
3.2 - Network Modeling
3.3 - Internal and External Systems Modeling
4 - Modeling Methods and Notations
4.1 - Archimate
4.2 - Business Process Model and Notation (BPMN)
4.3 - Design and Engineering Methodology for Organizations (DEMO)
4.4 - The Goals Approach
5 - Modeling with CASE Tools
5.1 - Application of modeling to low-code tools
5.2 - Application of modeling to no-code tools
5.3 - Practical Modeling of a Company Information System
5.4 - Development of a Company Information System
1.1 - Unified Modeling Language (UML)
1.2 - Concepts of objects, classes, stereotypes, methods, attributes
1.3 - Concepts of association, dependency, aggregation, inheritance, and information flow
1.4 - Class, activity, and sequence diagrams
1.5 - Modeling Practice
2 - Information Systems Modeling
2.1 - Functional and Non-Functional Requirements
2.2 - Business Modeling
2.3 - Business Process and User Modeling (Profiling, Persona)
2.4 - User Task and User Interface Modeling
2.5 - Business Logic and Data Modeling
2.6 - Software Architecture Modeling
3 - Business Structure Modeling
3.1 - Hardware Modeling
3.2 - Network Modeling
3.3 - Internal and External Systems Modeling
4 - Modeling Methods and Notations
4.1 - Archimate
4.2 - Business Process Model and Notation (BPMN)
4.3 - Design and Engineering Methodology for Organizations (DEMO)
4.4 - The Goals Approach
5 - Modeling with CASE Tools
5.1 - Application of modeling to low-code tools
5.2 - Application of modeling to no-code tools
5.3 - Practical Modeling of a Company Information System
5.4 - Development of a Company Information System
Bibliography / Information Sources:
Dietz J. L. G. , 2006 , Enterprise Ontology: Theory and Methodology , Springer
Alberto Manuel Rodrigues da Silva, Carlos Alberto Escaleira Videira , UML, metodologias e ferramentas CASE : linguagem de modelação UML, metodologias e ferramentas CASE na concepção e desenvolvimento de software ,
Geoffrey Sparks , Enterprise Architect User Guide , Sparx Systems
Alistair Cockburn , Writing effective use cases ,
Hans-Erik Eriksson, Magnus Penker , Business modeling with UML : business patterns at work ,
The Open Group , ArchiMate® 3.2 Specification , The Open Group
Object Management Group (OMG) , Business Process Model and Notation (BPMN) Version 2.0 , Object Management Group (OMG)
Pedro Valente , Business and software modeling traceability : enterprise (business + software) development process, method and language ,
Alberto Manuel Rodrigues da Silva, Carlos Alberto Escaleira Videira , UML, metodologias e ferramentas CASE : linguagem de modelação UML, metodologias e ferramentas CASE na concepção e desenvolvimento de software ,
Geoffrey Sparks , Enterprise Architect User Guide , Sparx Systems
Alistair Cockburn , Writing effective use cases ,
Hans-Erik Eriksson, Magnus Penker , Business modeling with UML : business patterns at work ,
The Open Group , ArchiMate® 3.2 Specification , The Open Group
Object Management Group (OMG) , Business Process Model and Notation (BPMN) Version 2.0 , Object Management Group (OMG)
Pedro Valente , Business and software modeling traceability : enterprise (business + software) development process, method and language ,
Assessment Methods and Criteria:
Classification Type: Quantitativa (0-20)
Evaluation Methodology:
This course combines theoretical and laboratory classes, using the presentation of concepts and the development of models applied to real-world cases. Activities include process modeling, requirements, architecture, and information systems, as well as the use of CASE tools and low-code and no-code platforms for rapid development. Assessment integrates a practical project (50%), focused on the modeling and implementation of an information system, and a written exam (50%), designed to evaluate the understanding of concepts and methodologies.
Evaluation Methodology:
This course combines theoretical and laboratory classes, using the presentation of concepts and the development of models applied to real-world cases. Activities include process modeling, requirements, architecture, and information systems, as well as the use of CASE tools and low-code and no-code platforms for rapid development. Assessment integrates a practical project (50%), focused on the modeling and implementation of an information system, and a written exam (50%), designed to evaluate the understanding of concepts and methodologies.


