1. Requirements I Peter Dolog dolog [at] cs [dot] aau [dot] dk 2.2.03
Intelligent Web and Information Systems
September 14, 2009

2. This Lecture
Requirements, Organizational Requirements (cca 30min) Information flows, goals (cca 30 min) -> decomposition of the values or motivations into underlying task, information, and intentions of actors Other modelling techniques (as time allows)
Peter Dolog, Web Engineering 2010, Requirements

3. Web Applications Challenges from Requirements Perspective
WA are characterized by a document-centric hypertext interface WA focus on information publishing rather than on services, i.e., contents changes and evolves very frequently; The user's and the stakeholder's contexts are often not known in advance Even when the stakeholders are known, they do not know how the Web application is going to affect their business model.
Peter Dolog, Web Engineering 2010, Requirements

4. Requirements
What is going to be published -> Content How operations (services) fit to it? How to at least to some extent analyse possible stakeholedrs or user contexts? How to analyse the value the WA is going to bring?
Peter Dolog, Web Engineering 2010, Requirements

5. Home.dk
Peter Dolog, Web Engineering 2010, Requirements

6. Hous Detail
Peter Dolog, Web Engineering 2010, Requirements

7. Furniture
Peter Dolog, Web Engineering 2010, Requirements

8. IKEA
Peter Dolog, Web Engineering 2010, Requirements

9. Integrated Application
Peter Dolog, Web Engineering 2010, Requirements

10. Areas or Options for Focus
Peter Dolog, Web Engineering 2010, Requirements

11. Organizational

12. How does it work
Peter Dolog, Web Engineering 2010, Requirements

13. Where with web application
Peter Dolog, Web Engineering 2010, Requirements

14. Value Based Requirements Engineering
Business models are important for companies They are usually informal There is a gap between the managers and IT professionals Web applications typically add to the creation of an economic value => e3-value model
Peter Dolog, Web Engineering 2010, Requirements

15. e3-value model
Provides an ontology (concepts) Models relationships between multiple enterprises E-Business Scenarios Operations Requirements
Peter Dolog, Web Engineering 2010, Requirements

16. Requirements Viewpoints
(C) Jaap Gordijn and Hans Akkermans: Designing and Evaluating E-Business Models. IEEE INTELLIGENT SYSTEMS JULY/AUGUST 2001
Peter Dolog, Web Engineering 2010, Requirements

17. Elements
Actor: an independent entity in business value exchange which consumes or creates a business value. Value object: an object (anything such as goods, money, information) which carries on could create an economic (business) benefit or a value for any actor in the model. Value port: a port through which actors exchange values, either requesting them or providing them to other actors. Value interface: groups value ports according to the economic reciprocity that one value must be exchanged or traded for other values. Value exchange: connects two value ports and represents an instance of one or more trades. Market segment: groups actors who value economic objects equally, such as a group of consumers. Value activity: an activity which creates a profit and is performed by an actor (an actor can have activities). Dependency path: the whole path of value exchange connecting a consumer need, actors, connection elements, connectors between various value interfaces (AND, OR), and dependency boundaries.
Peter Dolog, Web Engineering 2010, Requirements

18. Value Based Requirements Engineering
© Springer
Peter Dolog, Web Engineering 2010, Requirements

19. Information Flows
Refinement from previous model From value exchange to information flows Define flow of information between system, organization and external entities
Peter Dolog, Web Engineering 2010, Requirements

20. WebML+
Actors: the roles users play in the system annotated with actions they usually perform. Supplied Information Units: persistent or transient information which is directly supplied by a system or an actor without any change. Derived Information Units: persistent or transient information which is computed and composed out of various pieces of information supplied. Processing Units: used in conjunction with derived information units. They model an abstraction of a process or procedure which computes or derives composite information structures needed by actors. Information Flows: represent how information flows from one actor to another through various processing and information units.
Peter Dolog, Web Engineering 2010, Requirements

21. Information Flows © Springer
Peter Dolog, Web Engineering 2010, Requirements

22. Goal Oriented Analysis
The goals analysis focuses on strategic incentives for particular requirements. The goals behind the values exchange (why certain things are values) Complement the e3-value model Very good at finding and resolving conflicts between requirements A Goal Model is a network of dependencies between a set of actors, goals, tasks, and resources. It models dependencies between the actors through the goals and intentions they have and considers how they can eventually be achieved.
Peter Dolog, Web Engineering 2010, Requirements

23. I*
Actors: the stakeholders involved in expressing requirements and goals, who can be represented as agents or as roles played by agents in different goal dependencies (agents and roles are special kinds of actors). Goals: intentions which should be achieved. Tasks: tasks which need to be carried out, typically to achieve a goal. Resources: entities needed to achieve a goal through a task. Soft goals: goals which do not have clearly identified explicit criteria for achievement and need to be further decomposed. Dependencies: connect instances of the above-mentioned entities into a dependency network showing how different actors relate to each other through goals, tasks, resources, and soft goals.
Peter Dolog, Web Engineering 2010, Requirements

24. Goal Oriented Requirements
© Springer
Peter Dolog, Web Engineering 2010, Requirements

25. Other techniques
Peter Dolog, Web Engineering 2010, Requirements

26. Integrated Application
Peter Dolog, Web Engineering 2010, Requirements

27. Task Models
© Springer
Peter Dolog, Web Engineering 2009, Requirements

28. Audience Modeling © Springer
Peter Dolog, Web Engineering 2009, Requirements

29. © Springer Audience Hierarchies
Peter Dolog, Web Engineering 2009, Requirements

30. © Springer Audience Transitions
Peter Dolog, Web Engineering 2009, Requirements

31. © Springer Applications Domain
Peter Dolog, Web Engineering 2009, Requirements

32. Interaction Spaces © Springer
Peter Dolog, Web Engineering 2009, Requirements