Business-Systems Architecture
- Details
- Category: Discipline
- McGovern, James: Ambler, Scott W.; Stevens, Michael E.; Linn, James; Sharan, Vikas; Jo, Elias K.; A Practical Guide to Enterprise Architecture, Pearson Prentice Hall, 2007 Laudon, Keneth C.; Management Information Systems: Managing the Digital Firm, 15 ed. Global Edition, Pearson Prentice Hall, 2017 Steven H. Spewak, Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology, John Willey & Sons, 1992. The Zachman´s framework Sparx Systems & Stephen Maguire, Enterprise Architecture- User Guide Series, 2017
- IT Engineering
- 587
- 7345
- Business-Systems Architecture
- ISMAT587-7345
- 2
- 6
- 0
- 12
- Não
- Português
- A hybrid methodology is used to support the teaching-learning process, specifically through the use of concept maps, problem-based learning, and support for entrepreneurship.
- Mandatory
- This course aims to provide a comprehensive body of knowledge related to Enterprise Architecture, as well as to organize content relevant to a thorough understanding of the challenges associated with implementing an information system within a company. The syllabus aims to achieve the learning objectives and skills included in the bachelor's degree's general training plan in programming and systems, and its main objectives are to provide students with a set of general and specific knowledge that enables them to understand and master technologies, application components, and methodologies for developing information system architectures, as well as to characterize the essential aspects of Enterprise Information System Architectures.
- An overview of strategic management concepts and their interconnection with information systems. SWOT analysis, product life cycle, BCG matrix, value chain. Introduction to enterprise architecture. The role of information systems in today's global business environment. Information Systems, Strategy, and Organization. Types of Enterprise Architectures. Strategic Management. SWOT Analysis. Strategic Management. BCG and Porter Models What is the BCG Matrix and what is it used for? What is the BCG Matrix? Zachman Framework Analysis Business Processes for an Enterprise System. BPMN Notation Information Architecture Application Architecture Service Architecture Technology Architecture Alignment between Architectures
Descrição dos instrumentos de avaliação (individuais e de grupo) ¿ testes, trabalhos práticos, relatórios, projetos... respetivas datas de entrega/apresentação... e ponderação na nota final.
Exemplo:
Descrição
Data limite
Ponderação
Teste de avaliação
18-06-2026 50%
Atividades Práticas (as 8 melhores atividades)
Todas as Semanas
40%
Participação
10%
Componente Teórica:
- 1 teste na época normal (2 horas máximo com 10 minutos tolerância)
- Nota mínima da componente teórica é de 8 (oito) valores
- Existe depois época de recurso, que substituirá a nota apenas em caso de melhoria
Componente Trabalho:
- Grupos de 2 alunos (ou individual)
- Formados na segunda semana
- Nota mínima da componente trabalho é de 9 (nove) valores
- Presença obrigatória na apresentação e discussão final do trabalho
- Poderá mediante a demonstração de conhecimento existir avaliações distintas no mesmo grupo
Componente Participação:
- Assiduidade
- Participação
- Interesse
- Postura
- Desenvolvimento de exercícios que possam exist
- Semestral
- A computer engineer who doesn't understand enterprise architecture knows how to build components (functions, modules, isolated systems), but doesn't necessarily know where those components fit, why they exist, or what happens when the organization changes and the components have to change with it. ASE provides three capabilities that the typical technical curriculum does not cover. First, the ability to contextualize technical decisions: understanding that choosing between a monolith and microservices is not a matter of technological preference. Second, the ability to communicate with non-technical stakeholders: enterprise architects, managers, and decision-makers speak the language of processes, capabilities, and value. Third, the ability to think about second-order consequences: anticipating how a change in a system affects data, processes, and infrastructure that no one has explicitly mapped out.
