Designing information systems in social context: a goal and scenario modelling approach (original) (raw)
Related papers
Designing web-based systems in social context: a goal and scenario based approach
2006
In order to design a better web-based system, a designer would like to have notations to visualize how design experts' knowhow can be applied according to one's specific social and technology situation. We propose the combined use of a goal-oriented language GRL and a scenarios-oriented notation UCM for representing design knowledge of web-based systems and information systems in general. Goals are used to depict business objectives, functional and nonfunctional system requirements. Tasks are used in the exploration of alternative technologies and their operationalizations into system constructs. Actors are used to do role-based analysis on social relationships. Scenarios are used to describe elaborated business processes or workflow. The approach is illustrated with an example of designing a web-based training system.
Integration of Use Case Models and BPMN Using Goal- Oriented Requirements Engineering
Journal of Computers
This paper proposes a methodology that transform Use Case diagram into BPMN diagram using GORE technique. The success of software projects depends upon the stakeholder requirements satisfaction and support for organizations business process. Use Cases is one of the most commonly used notations to elicit requirements from an actor's point of view. Business process modelling notation (BPMN) is commonly used to model organizational business processes and to effectively communicate and conceptualize configuration of processes to relevant stakeholders. Hence, there is a need to be able to transform actors' goals and objectives into operational business processes and vice versa. Goal oriented requirement engineering (GORE) suggests analysing high level goals of the system to contextualize business processes. This paper argues that both Use cases and BPMN should be contextualized and should coevolve.
Business process modelling and purpose analysis for requirements analysis of information systems
Advanced Information Systems …, 2008
Although requirements analysis is acknowledged as a critical success factor of information system development for organizations, problems related to the requirements stage are frequent. Some of these problems are lack of understanding of the business by system analysts, lack of focus on the purpose of the system, and miscommunication between business people and system analysts. As a result, an information system may not fulfil organizational needs. To try to prevent these problems, this paper describes an approach based on business process modelling and purpose analysis through BPMN and the goal/strategy Map approach. The business environment is modelled in the form of business process diagrams. The diagrams are validated by end-users, and the purpose of the system is then analyzed in order to agree on the effect that the information system should have on the business processes. Finally, requirements are specified by means of the description of the business process tasks to be supported by the system.
Case-based analysis in user requirements modelling for knowledge construction
Information and Software Technology, 2010
Context: Learning can be regarded as knowledge construction in which prior knowledge and experience serve as basis for the learners to expand their knowledge base. Such a process of knowledge construction has to take place continuously in order to enhance the learners' competence in a competitive working environment. As the information consumers, the individual users demand personalised information provision which meets their own specific purposes, goals, and expectations. Objectives: The current methods in requirements engineering are capable of modelling the common user's behaviour in the domain of knowledge construction. The users' requirements can be represented as a case in the defined structure which can be reasoned to enable the requirements analysis. Such analysis needs to be enhanced so that personalised information provision can be tackled and modelled. However, there is a lack of suitable modelling methods to achieve this end. This paper presents a new ontological method for capturing individual user's requirements and transforming the requirements onto personalised information provision specifications. Hence the right information can be provided to the right user for the right purpose. Method: An experiment was conducted based on the qualitative method. A medium size of group of users participated to validate the method and its techniques, i.e. articulates, maps, configures, and learning content. The results were used as the feedback for the improvement. Result: The research work has produced an ontology model with a set of techniques which support the functions for profiling user's requirements, reasoning requirements patterns, generating workflow from norms, and formulating information provision specifications. Conclusion: The current requirements engineering approaches provide the methodical capability for developing solutions. Our research outcome, i.e. the ontology model with the techniques, can further enhance the RE approaches for modelling the individual user's needs and discovering the user's requirements.
Integrating Use Cases and Organizational Modeling
The object oriented development paradigm has attracted many supporters in the Software Engineering community. One of the most important advances was the Unified Language Modeling (UML), a standard for visual modeling. Use Case Diagrams have been used for capturing system functional requirements. However, the system development occurs in a context where organization processes are well established. Therefore, we need to capture organizational requirements to define how the system fulfils the organization's goals, why it is necessary, what are the possible alternatives, what are the implications to the involved parts, etc. Unfortunately, UML is ill equipped for modeling organizational requirements. We need other techniques, such as i*, to represent these aspects. Nevertheless, organizational requirements must be related to functional requirements represented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of Use Cases from t...
Deriving use cases from organizational modeling
Proceedings IEEE Joint International Conference on Requirements Engineering, 2002
Modeling (UML) have been used for capturing system functional requirements. However, the system development occurs in a context where organizational processes are well established. Therefore, we need to capture organizational requirements to define how the system fulfils the organization goals, why it is necessary, what are the possible alternatives, etc. Unfortunately, UML is ill equipped for modeling organizational requirements. We need other techniques, such as i*, to represent these aspects. Nevertheless, organizational requirements must be related to functional requirements represented as Use Cases. In this paper we present some guidelines to assist requirement engineers in the development of Use Cases from the i* organizational models.
Deriving Goals from a Use-Case Based Requirements Specification
Requirements Engineering, 2001
Use cases and scenarios have emerged as prominent analysis tools during requirements engineering activities due to both their richness and informality. In some instances, for example when a project's budget or schedule time is reduced at short notice, practitioners have been known to adopt a collection of use cases as a suitable substitute for a requirements specification. Given the challenges inherent in managing large collections of scenarios, this shortcut is cause for concern and deserves focused attention. We describe our experiences during a goal-driven requirements analysis effort for an electronic commerce application. In particular, we identify the specific risks incurred, focusing more on the challenges imposed due to traceability, inconsistent use of terminology, incompleteness and consistency, rather than on traditional software project management risks. We conclude by discussing the impact of the lessons learned for requirements engineering in the context of building quality systems during goal and scenario analysis
Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems, 1996
This paper presents our approach for deriving and supporting decisions about system requirements based on the teleological paradigm. In this approach requirements for a new system are seen as the fulfilment or operationalisation of organisational and business goals. In contrast to conventional goal-oriented approaches in which requirements are derived by high level goals by a (mostly) top-down goal decomposition process, we perceive goal operationalisation as the iterative process of experimenting-in-action, using scenario generation techniques to refine enterprise goals to a level at which they have an operational definition.
Use Cases and Scenarios Engineering
2007 Innovations in Information Technologies (IIT), 2007
Scenarios and use cases have been used interchangeably in several works meaning partial descriptions. In this paper, we suggest a requirement engineering process that composes (merge) use cases/scenarios and yields a formal specification of the system in form of a high-level Petri net. Use cases and scenarios are acquired in form of diagrams as defined by the Unified Modeling Language (UML). These diagrams are composed and transformed into Petri net specifications and merged to obtain a global Petri net specification capturing the behavior of the entire system. From the global specification, a system prototype can be generated and embedded in a user interface builder environment for further refinement. Based on end user feedback, the use cases and the input scenarios may be iteratively refined. The result of the overall process is a specification consisting of a global Petri net, together with the generated and refined prototype. This paper discusses some activities of this process. The need of a unified model of interaction (UMI) is also discussed at the end of this paper.
Use Case Maps: A Roadmap for Usability and Software Integrated Specification
Usability, 2002
The purpose of this paper is to explore use case maps as a medium for integrating task analysis and usability requirement into the traditional software requirement engineering process. The paper responds to major gaps in user interface specification in HCI, in software development methods for interactive software, and in the communication between usability specialists and software developers. We illustrate, via a concrete example, the usage of use case maps as an approach for specifying user interface and usability requirements. The Use Case Maps (UCMs) is a scenario-based notation for describing, in an abstract way, how the organizational structure of a complex system and the emergent behavior of the system are intertwined. It provides a first-class design model for the "how it works" aspect of both object-oriented and real time systems. Use case maps give a road-map-like view of the causeeffect paths traced through a system by scenarios or use cases .