BPMN 2.0 - Business Process Model and Notation

Bilder zu BPMN 2.0 - Posters
Google BPMN 2.0 - Posters

Introduction to BPMN
http://de.slideshare.net/NesmaDarwish/bpmn-10041967 

Pegasystems
http://en.wikipedia.org/wiki/Pegasystems

Free-Learning online Courses

Free-Learning online Courses
Openculture: http://www.openculture.com/freeonlinecourses

CPRE Advanced Level - Requirements Modeling with UML

Certified Professional Requirements Engineering (CPRE)
CPRE Lehrpläne: http://www.ireb.org/lehrplaene.html
CPRE Glossar: http://www.ireb.org/lehrplaene.html 
Requirements engineer
A person who – in collaboration with stakeholders – elicits, documents, validates, and manages requirements.
Requirements Engineering
A systematic and disciplined approach to the specification and management of requirements with the following goals:
(1) Knowing the relevant requirements, achieving a consensus among the stakeholders about these requirements, documenting them according to given standards, and managing them systematically,
(2) Understanding and documenting the stakeholders’ desires and needs,
(3) Specifying and managing requirements to minimize the risk of delivering a system that does not meet the stakeholders’ desires and needs.
Abbreviation: RE
Note: All three goals address important facets of RE: (1) process-orientation, (2) stakeholder focus, and (3) importance of risk and value considerations.

Data Flow Diagram
DFD - Dataflow Diagrams: http://de.slideshare.net/Cazoomi/data-flow-diagrams-for-dummies

Agile RE
Agile RE: http://heliosobjects.com/2014/02/20/requirements-management-in-agile-projects/

RE Tools

Polarion
Polarion: http://www.polarion.com/ 
Polarion Webinars & Speeches: http://www.polarion.com/company/events/index.php#recorded

Sparx Enterprise Architekt
Free Download: http://www.sparxsystems.com/products/ea/trial.html
Enterprise Architect: http://www.sparxsystems.com/
EA Demonstrations: http://www.sparxsystems.com/resources/demos/index.html
EA Webinars:  https://www.cephas.cc/  about Use Cases in EA
EA UML Modeling: http://www.sparxsystems.com/uml-tutorial.html

Business Analysis

IIAB - International Institute of Business Analysis
http://www.iiba.org/babok-guide/babok-guide-online.aspx

IIAB Glossar: http://www.iiba.org/babok-guide/babok-guide-online/appendix-a-glossary.aspx

erweiterte Ereignisgesteuerte Prozesskette eEPK: http://de.wikipedia.org/wiki/Ereignisgesteuerte_Prozesskette

Priorisation of Requirements
MoSCoW Method: http://en.wikipedia.org/wiki/MoSCoW_Method


BA Tools
Freeware BPM-Tool ARIS: http://www.ariscommunity.com/


Varia
RSS Feed: http://en.wikipedia.org/wiki/RSS

Business Analyst - Requirement Engineer - Artefacts

Business Analyst - Requirement Engineer - Artefacts

Various Types of Requirements
Requirement: http://en.wikipedia.org/wiki/Requirement
- Business Requirement: http://en.wikipedia.org/wiki/Business_requirements 
- auch Business Case: http://en.wikipedia.org/wiki/Business_case
- User Requirements: http://en.wikipedia.org/wiki/User_requirements_document (user statements)
- Functional Requirement: http://en.wikipedia.org/wiki/Functional_requirements
- * Quality (of Service) Requirement - NFR: http://en.wikipedia.org/wiki/Non-functional_requirements
- Assumptions, Dependencies and Constraints: http://chicwriter.com/2010/11/requirements-gathering-analysis-assumptions-dependencies-constraints/ 

Rahmen und Randbedingungen
- more Assumptions and Constraints: http://www.bridging-the-gap.com/ba-stories-its-not-all-requirements-assumptions-and-constraints-matter-too/
- Business Constraints: http://docs.oracle.com/cd/E19263-01/817-5759/bus_analysis.html#wp20584
- Typen von Randbedingungen: https://www.projektmagazin.de/glossarterm/randbedingungen



Characteristics of good Requirements

Characteristic	Explanation
Unitary (Cohesive)	The requirement addresses one and only one thing.
Complete	The requirement is fully stated in one place with no missing information.
Consistent	The requirement does not contradict any other requirement and is fully consistent with all authoritative external documentation.
Non-Conjugated (Atomic)	The requirement is atomic, i.e., it does not contain conjunctions. E.g., "The postal code field must validate American and Canadian postal codes" should be written as two separate requirements: (1) "The postal code field must validate American postal codes" and (2) "The postal code field must validate Canadian postal codes".
Traceable	The requirement meets all or part of a business need as stated by stakeholders and authoritatively documented.
Current	The requirement has not been made obsolete by the passage of time.
Unambiguous	The requirement is concisely stated without recourse to technical jargon, acronyms (unless defined elsewhere in the Requirements document), or other esoteric verbiage. It expresses objective facts, not subjective opinions. It is subject to one and only one interpretation. Vague subjects, adjectives, prepositions, verbs and subjective phrases are avoided. Negative statements and compound statements are avoided.
Specify Importance	Many requirements represent a stakeholder-defined characteristic the absence of which will result in a major or even fatal deficiency. Others represent features that may be implemented if time and budget permits. The requirement must specify a level of importance.
Verifiable	The implementation of the requirement can be determined through basic possible methods: inspection, demonstration, test (instrumented) or analysis (to include validated modeling & simulation).

User Stories
User Stories: http://en.wikipedia.org/wiki/User_story
"As a <role>, I want <goal/desire> so that <benefit>" 
"As a <role>, I want <goal/desire>"

Use Cases
Use Case: http://www.usability.gov/how-to-and-tools/methods/use-cases.html

UML-Diagrams

Possible * Quality Requirements
Sufficient network bandwidth may be a non-functional requirement of a system. Other examples include:

• Accessibility
• Audit and control
• Availability (see service level agreement)
• Backup
• Capacity, current and forecast
• Certification
• Compliance
• Configuration management
• Dependency on other parties
• Deployment
• Documentation
• Disaster recovery
• Efficiency (resource consumption for given load)
• Effectiveness (resulting performance in relation to effort)
• Emotional factors (like fun or absorbing)
• Environmental protection
• Escrow
• Exploitability
• Extensibility (adding features, and carry-forward of customizations at next major version upgrade)
• Failure management
• Fault tolerance (e.g. Operational System Monitoring, Measuring, and Management)
• Legal and licensing issues or patent-infringement-avoidability
• Interoperability
• Maintainability
• Modifiability
• Network topology
• Open source
• Operability
• Performance / response time (performance engineering)
• Platform compatibility
• Price
• Privacy
• Portability
• Quality (e.g. faults discovered, faults delivered, fault removal efficacy)
• Recovery / recoverability (e.g. mean time to recovery - MTTR)
• Reliability (e.g. mean time between failures - MTBF)
• Reporting
• Resilience
• Resource constraints (processor speed, memory, disk space, network bandwidth, etc.)
• Response time
• Robustness
• Safety or Factor of safety
• Scalability (horizontal, vertical)
• Security
• Software, tools, standards etc. Compatibility
• Stability
• Supportability
• Testability
• Usability by target user community

Upcoming Events

Upcoming Events
UX Schweiz, 27. Feb. 2014, ETH, 18:30-20:00 h: http://ux-schweiz.ch/

About User Experience UX and GUI Design

UX Principles
GUI Design Principles: http://en.wikibooks.org/wiki/GUI_Design_Principles
The Psychological Basis for UI Design Rules: http://www.youtube.com/watch?v=3Gw2bnwQRno 
(Design Guidelines) ... 1:15:22 .. University of Stanford Lecture
Definition of UX: http://www.nngroup.com/articles/definition-user-experience/ 
User Experience Basics: http://www.usability.gov/what-and-why/user-experience.html 


UX matters
Great User Experiences sell, see Apple.
Great UX attracts traffic and increases sales, will encourage repeat visits, reduces support request ..

UX Examples: https://www.crealogix.com/de/firmenkunden/finanzindustrie/user-experience/  
Why UX:  http://ux.crealogix.com/
UX Glossar
User Experience: http://en.wikipedia.org/wiki/User_experience  
Positive User Experience: "Goals of User and Goals of Company who created Product are met."
Negative User Experience: "Try to program your Grandma's VCR." :-)
Site Map: Example of a Sitemap: https://www.credit-suisse.com/sitemap/de/
Taxonomy: http://en.wikipedia.org/wiki/Taxonomy
Flowmap: http://www.pinterest.com/jvetrau/ux-site-maps-information-maps-page-flows/
Mindmap of User Personas: what the user is looking for as an experience
Byflow: where UX designers wants their users to go (ROI on UX)
Convertion: when actually User signs up

UX Developing Cycle - watch 58:06 excellent Minutes how it all comes together
Harvard i-lab UX Design - Scott Stevenson: http://www.youtube.com/watch?v=WkUwbPdyMIY 
Five Steps of Developing UX - Tasks and Deliverables
5. Surface: Visual Interface Layer that ties all other Layers together, images, graphics, buttons etc.
4. Sceleton: Wireframe (blueprint for pages), where buttons go, what call for actions are there etc., Low-FI Wireframes (hand sketch, static), High-FI Wireframes (HTML, clickable, interactable)
3. Structure: Develop Taxonomy, what is the flow of actions and interactions within the Site
2. Scope: Migration of Strategy into Requirements, Identify Users, User Story Matrix (different types of  Users, their personas and their tasks)
1. Strategy: Business Goals & User Goals, what is the reason for the Site, what are Goals

UX Measured
- follow user adoption
- focus groups, asking 25-30 people how they percieve the sites -> value you promised does not fit the UX on
- do Google analytics, to find out when people come on, how long they stay, when they leave etc.


UX - GUI Design Tools
GUI Design Tools: http://softwaresolution.informer.com/Tools-to-Design-GUI/ 
GUI Design Tool Demo: http://www.carettasoftware.com/guidesignstudio/gui-design-studio-demo.html 
Balsamiq - allows for HiFi Prototyping: http://balsamiq.com/products/mockups/ 
Mindjet - for Site-Maps: http://www.youtube.com/user/mindjet

UX - GUI Design Tutorials
Netbeans Tutorial - GUI Design: http://www.youtube.com/watch?v=wi5hg3onjd0