Übung Flashcards
Media disruption
Media disruption: a process not watched by the company between two processes supported by the company (isolated information systems like non-electronic systems).This means no influence on the outcome, which could lead to a potential loss of the customer.
Aggregation vs. Generalization
Aggregation (disaggregation): different objects are combined into a new one (server, infrastructure, website, Application – instant ONS)
Generalization (specialization): similar objects are abstracted to become a high level object (mobile phone , Smart phone, tablet PC – mobile device)
Conceptual model, Technical model, Implementation
Meta Models – Aris
Conceptual model: describes processes independent from the implementation in the IS. (Via ERM, specialty departments)
Technical model: translation of business concepts into IS related concepts. (Via Structure charts, business informatics specialist)
Implementation: specific/detailed description of a technical IS implementation (Programming code, software engineers)
Modularisation of IS-Components
Minimization of complexity Scalability Portability Maintainability Standardization Well-defined interfaces Independence of IS components
Apples Salecircle
Devices –> Content providers –> Content –> Consumers –> Devices
Google Salecircle
Support of the Web –> experience –> awareness
+
Google Services –> User Traffic –> Data
=
Adsense + Adwords
Bus, Ring, Star topology
Bus topology: single point of failure + Easy & low cost setup / extension
Ring topology: No single point of failure, but slow, if broken
Star topology: Single point of failure (central node) + easy set up / troubleshooting
Magic triangle
Magic triangle: Quality Time costs
SMART
SMART: Specific (defined goals), Measurable (quantitative), attainable (nothing unrealistic), relevant (helps the company), time bound (time plan)
Gantt vs Network Plan
Gantt: Easy to understand, shows activity durations & time overlaps, no slack times, no dependencies, for small to medium size companies
Network plan: Detailed and dependencies
Well formed XML
Well-formed XML.
Elements are case-sensitive, no special syntax, correctly nested, 1 root element
Important Parts of XML
Use case diagrams
Use cases describe the functionality which is system has to provide
Class diagrams
Representation of the static structure of the software system
No activity or control logic
Description of logical relations between structural elements
Activity diagrams
Used to model workflow in the system
