Psweng Understanding It!

Self profiling.

Dr. Mario Kupries www.engine.swsystem-architecture.com [email protected]

Challenging.

No antiquated

analysis and practice.

Adaptation. Nothing is as constant as change is.

My type of colleague. Being both, a reliable and demanding colleague. A – Analytical C – Courageous T – Talented V- Visionary

Innovation is a team sport.

My “I” in team. • • • • •

I enable team members to show initiative. I don’t do their jobs for them. I delegate tasks. I am inclusive in planning. I use my expertise to help them become better members on their own. • I – That is me, the integral and integrating team member.

The five Ws.

Challenges for teams. • Interdisciplinary. • Highly profiled. • Multi cultural. • High fluctuation.

Between team members. Technical communication. To be employed as a Technical Writer or an Informatics Journalist?

My leadership. • As a leader, one is The Generalist. • A well informed team member is not a phantom. • Professional leadership means ability-oriented task assignment. • Creative contributions need an extensive scope of freedom and action. • Interpersonal and precise communication abilities are important key stones.

My elements of leadership. • • • • •

Positional authority. Line authority. Intellectual authority. Personal authority. Ethical authority.

Proven social core competences. • • • • • •

Independent creativity (visions). Continuous learning (methodology). Team spirit (division of labor). Trust and faith in others (laissez-faire). Goal-oriented (satisfy customer needs). Customer-oriented (achieve the goal).

Not building a bridge into the fog!

Mystery: `Software Project Management’?

+

=

Project – An example.

Precise communication – an example.

The drive.

The difference between illusion and vision is to what degree a project is realizable. Engineer highly advanced products, components and systems worldwide.

Bridging the business gaps. • Identify ethnocentric, technical & economical gaps • Overcome legacy domination • Handle dissonance in direction, orientation and motivation • Measure outcomes to promote innovative solutions • Determine strategic direction • Nimbly respond to competitor moves • Retain decision rights while delegating control processes

Being excited by constructive contributions.

Arab countries have successfully replaced children as camel racers by robots.

Moving on.

Only the thirsty hunger of a discipline determines its progress.

Engineering is not science.

The scope – A delimitation.

Software Engineering supports a systematic construction of computer-aided product requirements regarding business goals & constraints. Due to the rapidly increasing functional and non-functional complexity this Engineering discipline has become a critical success factor in today’s industrial scopes and ambitions. Therewith, it focuses on assuring the optimal realization of customer expectations and market needs.

Software engineering competencies. • • • • • • • • • •

Architectures for product lines and families. Hardware and software products. Following engineering methodologies. Building block technology. Model transformation and model scopes. Construction processes and methodologies. Abstraction levels. Pre-fabrication and reuse. De-/Composition. Knowledge management.

Some principles. From the descriptive to the operative by systematic model transformation. By abstracting market developments, derive visions & prognosis for new products. By structuring and classifying conceptual work, reuse achieved knowledge to create new products.

From the abstract to the concrete.

The meaning of communicating complexity is to think abstractly, not at the instance level.

Constructing into architectures.

An architecture model is abstracted knowledge.

This is what it is about. Fighting for the better idea that builds better products and acquires new markets.

…leaving foot prints behind.

Strategies.

Prognosis regarding the potentials of markets. Country-oriented strategy.

Constructing the future. Goal is to participate in creating the future. Not to lag behind.

Webbed non-functional aspects. WEBBED

• Security. • Mobility. • Usability. • Composition & variability. • Heterogeneity.

Product Line Engineering.

• Automation of product-specific architecture variation • Determination and maintenance of consistencies between particular products, variants and suitable alternatives • Product derivation along a variation hierarchy

Handling of complexity.

CUSTOMER – zation.

• Interview techniques. • Business process modeling. • Agile integration into all phases. • Ontology / vocabulary. •…

Challenges.

Rapidly configurable systems. Variability across customer needs. Time-To-Market costs.

Adaptability. Do not turn your back on the reality: Reflect changes in the environment.

Reliability.

Understanding the people involved as (1) users carrying the application semantics (2) an important part of the discourse (3) engineers construct the product.

Internationality.

Being internationally informed, e.g. memberships in professional organizations and their task forces, standardization committees, virtual networks.

It’s all combined now.

Avoiding the linguistic confusion. BPR, BI, WfMS, SOA, ERP, EAI, TC, PLE, …

Personal

–

At a glance.

• Graduation: • PhD: • Post Doc:

1996

(University Potsdam, GER)

2000

(University Potsdam, GER)

2007

(Aarhus University, DK)

• Areas:

Software Construction, Methodologies, Software Architectures, Process Models, Software Product Lines & Families, Knowledge Management, Project leadership

• Contact:

www.pse-ezine.com/mk_vitae.htm

Consultancy.

Cooperation scope – An example.

Professional memberships.

ycavirP

Seconq

Litfaßsäule

lanoisseforP

Quariate

… until the next time!