Scriptiestage Enterprise Architecture

Deloitte

Stage informatie

Bedrijf: Deloitte

Locatie: Amsterdam

Opleidingsniveau: WO

Periode:

Type: Afstudeerstage

Vergoeding:

Solliciteren

Functieomschrijving als scriptiestagiair bij Enterprise Architecture

Als scriptant bij Enterprise Architecture doe je onderzoek op het snijvlak van Business en IT. Consultants binnen dit team houden zich bijvoorbeeld bezig met het modelleren of (her-)ontwerpen van bedrijfsprocessen, business domein architecturen en  IT architecturen. Of verzamelen binnen een IT project de business requirements en vertalen deze naar effectieve IT oplossingen, of zijn onderdeel van een team dat adviseert over hoe een bedrijf een nieuw (ERP-) systeem kan integreren binnen het bestaande legacy – applicatie landschap.

Jouw profiel als scriptiestagiair bij Enterprise Architecture

  • In de masterfase van een universitaire studie (zoals Business & ICT, Informatiekunde, Werktuigbouwkunde, Natuurkunde, Technische Bedrijfskunde en Econometrie);
  • Sterke analytische vaardigheden;
  • Liefst kennis en ervaring met methoden en technieken als modelleren van bedrijfsprocessen, workflow management, enterprise content management en digitalisering, opstellen van IT architecturen, (enterprise) architecture frameworks zoals TOGAF en tooling zoals Aris of Casewise. Of kennis van concepten en begrippen als BPMN, UML, Enterprise Service Bus, Service georiënteerde architecturen en Cloud Computing.
  • Je hebt een bijzondere interesse in Architecture & BPM en dat is terug te zien in je studiekeuze, je stage en eventuele werkervaring;
  • Je bent communicatief vaardig en in staat om in overleg met de klant tot goede oplossingen te komen;
  • Naast je studie heb je ook tijd besteed aan nevenactiviteiten en heb je actief deelgenomen aan een studentenvereniging, bestuur, commissie of sportvereniging;
  • Je hebt een uitstekende beheersing van de Nederlandse en Engelse taal.

Scriptievoorbeelden

 

Enterprise Architecture Skills

Background

Nowadays organizations have to deal with a complex Business and IT environment. Business and IT are interrelated in many different ways. Organizations are forced to adjust continuously to changing environments and therefore to change their business processes, business models and supporting IT. Because of the inherent complexity of these changes it is hard to manage changes in an integrated and controlled way. Enterprise architecture (EA) is an indispensable instrument in controlling these complex changes with a significant IT component. This has significant implication for the skill set of architects. A foundation for the value of enterprise architecture and the priorities in architecture activities have been established in preceding internships. This internship will build on those results but will focus on the skill set.

Questions to be answered

  •   Why should an organization invest in Enterprise Architecture Skills?
  •   Which skills should an Enterprise Architect focus on?
  •   Which skills should an Enterprise Architect NOT focus on?
  •   How do these skill impact the real or perceived value from EA?
  •   Which skills are crucial in which phase of the career of an Enterprise Architect

 

Retirement of Legacy Systems

Background

Large organizations that have been investing in their IT landscape for a long time often have to deal with legacy systems. Consider for example banks, who have been early adopters of IT and have been subjected to mergers and acquisitions over many years, maybe even decades. Typically, legacy systems are hard to maintain, expensive to operate and cumbersome to change. Initiatives to migrate to modern replacements often fail or are not attempted at all due to the high amount of complexity involved. Deloitte helps organizations with such initiatives, tailoring its approach to each client. The intern is requested to collect Industry best practices and examples from companies that have successfully decommissioned (part of) their legacy systems, and to build a framework to categorize these approaches and the applicability to specific cases.

Questions to be answered  

  • How can Deloitte convince clients to use the established standardized approach, rather then a “roll your own” approach?
  • How can the system functions and data remain available during the migration, e.g. how can risks be mitigated and confidence be gained?
  • Which architecture patterns are applicable to the transition? What are typical anti-patterns, often used, but always unsuccessful and therefor to be avoided?
  • How can legacy systems be phased out in a controlled, manageable, phased way?

 

Measuring Architectural Complexity

Background

Many organizations are experiencing their IT landscape as complex and in many cases as too complex.. Simplifying such landscapes in order to increase agility and reduce operational costs is a common business wish. The  real reduction in complexity, however, is difficult to measure, because no standardized or proven method exists to measure architectural complexity of IT landscapes. In addition is difficult to draw conclusions from this information, quantifying potential savings. Deloitte wants to develop such method to help clients determining the potential benefits of complexity reduction initiatives, so that the potential value of such initiatives can be determined upfront.

Questions to be answered  

  • How can the method be validated?
  • Which scientific literature is applicable to such measurements?
  • How can architectural complexity be measured, given a set of components and their interfaces?
  • How can results be visualized to provide an easy means of communication with stakeholders?
  • How can this method be applied in a commercial context?

 

The value of standardized EA artefacts

Background

One of the corner stones of Enterprise Architecture is the concept of views and view points and the associated concepts of stakeholders and concerns. Simply put, to address the concern of a specific stakeholder a standardized viewpoint is used to create the view which answers the stakeholders concern. Or in simple terms. For every question a standardized diagram, list or matrix can be created, and this is appreciated by the stakeholder. In most organizations, Enterprise Architect tend to invent their own diagrams and diagramming styles. Deviating from the established theory. So the key question is: Are the advantages of standardizing EA artefacts real or imaginary?

Questions to be answered  

  • Do typical EA stakeholders expect standardized artefacts?
  • Are standardized artefacts superior from a information exchange perspective?
  • Is the impact of EA increased by standardizing artefacts?
  • Is there any truth in the statement that artefacts cannot be standardized but need to be tailored on a case by case and stakeholder by stakeholder basis?
  • Do artefacts exist that can be considered “best in class” and should be preferred to other ad hoc alternatives?

 

Word jij uitgedaagd door deze functie?

Neem dan vandaag nog contact met ons op voor een kennismaking. Klik op onderstaande button en vul je gegevens in.

Past de geschetste functie niet bij jou, maar ken je iemand die perfect in het geschetste profiel past? Stuur deze vacature dan door.

Voor vragen over deze vacature kun je bellen met Berdi Mannaerts op telefoonnummer +31 (0)88 2888 744.

Acquisitie op basis van deze vacature wordt niet op prijs gesteld.

Stage informatie

Bedrijf: Bedrijf: Deloitte

Locatie: Amsterdam

Opleidingsniveau: $stage.educationLevel.name}

Periode:

Type: Afstudeerstage

Vergoeding:

Solliciteren

Meer stages

Stages