Lecture

Enterprise and Service-Oriented Architecture

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

In course

CS-491: Introduction to IT consulting

This course is an introduction to the alignment of enterprise needs with the possibilities offered by Information Technology (IT). Using a simulated business case, we explore how to define the requirements for an IT service that matches stakeholders explic ...

Description

This lecture introduces Enterprise and Service-Oriented Architecture, focusing on the alignment of business and IT solutions. It emphasizes the importance of understanding what and why to build, rather than just how. The course targets EPFL engineers transitioning to business analysts, project managers, and consultants. The instructors, Gil Regev, Tatiana Porté, and Alain Wegmann, aim to provide a practical view of business needs and IT usage. The course covers topics like Business Analysis, Requirements Engineering, Enterprise Architecture, and Service Management. Students will learn to analyze stakeholder needs, define requirements, and prototype IT solutions. The lecture includes interactive activities, simulations, and group presentations to enhance learning and practical application.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Instructor

Gil Regev

Gil Regev joined EPFL in 1997 as Senior Researcher after 9 years at Logitech Switzerland and USA. Gil obtained his Ph.D. in Communication Systems in 2003. Since 2008 Gil works both at EPFL and Itecor

Official source

Ontological neighbourhood

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (32)

Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

Business requirements

Business requirements, also known as stakeholder requirements specifications (StRS), describe the characteristics of a proposed system from the viewpoint of the system's end user like a CONOPS. Products, systems, software, and processes are ways of how to deliver, satisfy, or meet business requirements. Consequently, business requirements are often discussed in the context of developing or procuring software or other systems. Three main reasons for such discussions: A common practice is to refer to objectives, or expected benefits, as 'business requirements.

Requirements engineering

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference.

Enterprise architecture

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy.

Enterprise architecture framework

An enterprise architecture framework (EA framework) defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

Related lectures (64)

An Introduction to Systems Engineering: Requirements, Architecture, and Concept Generation

Covers the 'V-Model' of Systems Engineering, emphasizing good requirements, system architecture, concept generation, and concept selection.

Systems Engineering: Introduction and Stakeholders

Introduces Systems Engineering, emphasizing stakeholder analysis and clear requirement definition for project success.

Vision-Language-Action Models: Training and Applications

Delves into training and applications of Vision-Language-Action models, emphasizing large language models' role in robotic control and the transfer of web knowledge. Results from experiments and future research directions are highlighted.

Requirements Definition

Explores the fundamentals of requirements definition in systems engineering, emphasizing the importance of clear and concise requirements for successful system design.

Learning-aided Program Reasoning