共查询到20条相似文献,搜索用时 31 毫秒
1.
Requirements for choosing off-the-shelf information systems (OISR) differ from requirements for development of new information
systems in that they do not necessarily provide complete specifications, thus allowing flexibility in matching an existing
IS to the stated needs. We present a framework for OISR conceptual models that consists of four essential elements: business
processes, business rules, information objects and required system services. We formalise the definitions of these concepts
based on an ontological model. The ontology-based OISR model provides a framework to evaluate modelling languages on how appropriate
they are for OISR requirements specifications. The evaluation framework is applied to the Object-Process Methodology, and
its results are compared with a similar evaluation of ARIS. This comparison demonstrates the effectiveness of the ontological
framework for evaluating modelling tools on how well they can guide selection, implementation and integration of purchased
software packages. 相似文献
2.
Requirements Engineering-Based Conceptual Modelling 总被引:1,自引:1,他引:1
The software production process involves a set of phases where a clear relationship and smooth transitions between them should
be introduced. In this paper, a requirements engineering-based conceptual modelling approach is introduced as a way to improve
the quality of the software production process. The aim of this approach is to provide a set of techniques and methods to
capture software requirements and to provide a way to move from requirements to a conceptual schema in a traceable way. The
approach combines a framework for requirements engineering (TRADE) and a graphical object-oriented method for conceptual modelling
and code generation (OO-Method). The intended improvement of the software production process is accomplished by providing
a precise methodological guidance to go from the user requirements (represented through the use of the appropriate TRADE techniques)
to the conceptual schema that properly represents them (according to the conceptual constructs provided by the OO-Method).
Additionally, as the OO-Method provides full model-based code generation features, this combination minimises the time dedicated
to obtaining the final software product. 相似文献
3.
In many applications, especially from the business domain, the requirements specification mainly deals with use cases and
class models. Unfortunately, these models are based on different modelling techniques and aim at different levels of abstraction,
such that serious consistency and completeness problems are induced. To overcome these deficiencies, we refine activity graphs
to meet the needs for a suitable modelling element for use case behaviour. The refinement in particular supports the proper
coupling of use cases via activity graphs and the class model. The granularity and semantics of our approach allow for a seamless,
traceable transition of use cases to the class model and for the verification of the class model against the use case model.
The validation of the use case model and parts of the class model is supported as well. Experience from several applications
has shown that the investment in specification, validation and verification not only pays off during system and acceptance
testing but also significantly improves the quality of the final product. 相似文献
4.
5.
6.
Release Planning in Market-Driven Software Product Development: Provoking an Understanding 总被引:2,自引:0,他引:2
Pär Carlshamre 《Requirements Engineering》2002,7(3):139-151
7.
A Scenario Construction Process 总被引:7,自引:3,他引:4
do Prado Leite Julio Cesar Sampaio Hadad Graciela D. S. Doorn Jorge Horacio Kaplan Gladys N. 《Requirements Engineering》2000,5(1):38-61
8.
9.
Dynamic logic (DL) provides a suitable formal framework to model actions and reasoning about them. <$>\cal OASIS<$> is a language
for the specification of object-oriented conceptual models. In our model, specialisation is a relation between classes that
defines an inheritance mechanism through static and dynamic partitions. A variant of DL (including the deontic operators for
permission, prohibition and obligation) is the formalism used in <$>\cal OASIS<$> to deal with changes of state, triggers,
preconditions, protocols and operations. The animation of conceptual models in order to validate the specification is an interesting
topic. We have worked on translating <$>\cal OASIS<$> specifications automatically to concurrent environments in order to
obtain a prototype useful to validate specifications by animation. The aim of this paper is to show that it is feasible to
translate static and dynamic partitions automatically into dynamic logic formulae. Thus, using the same developed schema of
animation it is possible to execute <$>\cal OASIS<$> specifications including inheritance. 相似文献
10.
Fabio Casati Maria Grazia Fugini Isabelle Mirbel Barbara Pernici 《Requirements Engineering》2002,7(2):73-106
Workflow management systems are becoming a relevant support for a large class of business applications, and many workflow
models as well as commercial products are currently available. While the large availability of tools facilitates the development
and the fulfilment of customer requirements, workflow application development still requires methodological guidelines that
drive the developers in the complex task of rapidly producing effective applications. In fact, it is necessary to identify
and model the business processes, to design the interfaces towards existing cooperating systems, and to manage implementation
aspects in an integrated way. This paper presents the WIRES methodology for developing workflow applications under a uniform
modelling paradigm – UML modelling tools with some extensions – that covers all the life cycle of these applications: from
conceptual analysis to implementation. High-level analysis is performed under different perspectives, including a business and an organisational perspective. Distribution, interoperability and cooperation with external information systems are considered in this early
stage. A set of “workflowability” criteria is provided in order to identify which candidate processes are suited to be implemented
as workflows. Non-functional requirements receive particular emphasis in that they are among the most important criteria for
deciding whether workflow technology can be actually useful for implementing the business process at hand. The design phase
tackles aspects of concurrency and cooperation, distributed transactions and exception handling. Reuse of component workflows,
available in a repository as workflow fragments, is a distinguishing feature of the method. Implementation aspects are presented
in terms of rules that guide in the selection of a commercial workflow management system suitable for supporting the designed
processes, coupled with guidelines for mapping the designed workflows onto the model offered by the selected system. 相似文献
11.
A Representational Framework for Scenarios of System Use 总被引:1,自引:0,他引:1
Scenarios are becoming widely used in three areas of system development: software engineering, human–computer interaction
(HCI), and organisational process design. There are many reasons to use scenarios during system design. The one usually advanced
in support of the practice is to aid the processes of validating the developers’ understanding of the customers’ or users’
work practices, organisational goals and structures, and system requirements. All three areas identified above deal with these
processes, and not surprisingly this has given rise to a profusion of scenario-based practices and representations. Yet there
has been little analysis of why scenarios should be useful, let alone whether they are. Only by having such a framework for
understanding what scenarios are, and what they are for, can we begin to evaluate different scenario approaches in specific
development contexts. This paper is a contribution toward such a framework. We lay out a space of representational possibilities
for scenarios and enumerate a set of values or criteria that are important for different uses of scenarios. We then summarise
several salient representations drawn from the software engineering, HCI, and organisational process design communities to
clarify how these representational choices contribute to or detract from the goals of the respective practices. Finally, we
discuss how scenario representations from one area of design may be useful in others, and we discuss the relationship between
these representations and other significant early-design and requirements engineering practices. 相似文献
12.
This paper looks from an ethnographic viewpoint at the case of two information systems in a multinational engineering consultancy.
It proposes using the rich findings from ethnographic analysis during requirements discovery. The paper shows how context
– organisational and social – can be taken into account during an information system development process. Socio-technical
approaches are holistic in nature and provide opportunities to produce information systems utilising social science insights,
computer science technical competence and psychological approaches. These approaches provide fact-finding methods that are
appropriate to system participants’ and organisational stakeholders’ needs.
The paper recommends a method of modelling that results in a computerised information system data model that reflects the
conflicting and competing data and multiple perspectives of participants and stakeholders, and that improves interactivity
and conflict management. 相似文献
13.
A Multi-Model View of Process Modelling 总被引:4,自引:4,他引:0
14.
Variability is a central concept in software product family development. Variability empowers constructive reuse and facilitates
the derivation of different, customer specific products from the product family. If many customer specific requirements can
be realised by exploiting the product family variability, the reuse achieved is obviously high. If not, the reuse is low.
It is thus important that the variability of the product family is adequately considered when eliciting requirements from
the customer.
In this paper we sketch the challenges for requirements engineering for product family applications. More precisely we elaborate
on the need to communicate the variability of the product family to the customer. We differentiate between variability aspects
which are essential for the customer and aspects which are more related to the technical realisation and need thus not be
communicated to the customer. Motivated by the successful usage of use cases in single product development we propose use
cases as communication medium for the product family variability. We discuss and illustrate which customer relevant variability
aspects can be represented with use cases, and for which aspects use cases are not suitable. Moreover we propose extensions
to use case diagrams to support an intuitive representation of customer relevant variability aspects.
Received: 14 October 2002 / Accepted: 8 January 2003
Published online: 27 February 2003
This work was partially funded by the CAFé project “From Concept to Application in System Family Engineering”; Eureka Σ! 2023
Programme, ITEA Project ip00004 (BMBF, F?rderkennzeichen 01 IS 002 C) and the state Nord-Rhein-Westfalia. This paper is a
significant extension of the paper “Modellierung der Variabilit?t einer Produktfamilie”, [15]. 相似文献
15.
Jean-Charles Pomerol 《Requirements Engineering》1998,3(3-4):174-181
In this paper, we address the question of how flesh and blood decision makers manage the combinatorial explosion in scenario
development for decision making under uncertainty. The first assumption is that the decision makers try to undertake ‘robust’
actions. For the decision maker a robust action is an action that has sufficiently good results whatever the events are. We
examine the psychological as well as the theoretical problems raised by the notion of robustness. Finally, we address the
false feeling of decision makers who talk of ‘risk control’. We argue that ‘risk control’ results from the thinking that one
can postpone action after nature moves. This ‘action postponement’ amounts to changing look-ahead reasoning into diagnosis.
We illustrate these ideas in the framework of software development and examine some possible implications for requirements
analysis. 相似文献
16.
The elicitation or communication of user requirements comprises an early and critical but highly error-prone stage in system
development. Socially oriented methodologies provide more support for user involvement in design than the rigidity of more
traditional methods, facilitating the degree of user–designer communication and the ‘capture’ of requirements. A more emergent
and collaborative view of requirements elicitation and communication is required to encompass the user, contextual and organisational
factors. From this accompanying literature in communication issues in requirements elicitation, a four-dimensional framework
is outlined and used to appraise comparatively four different methodologies seeking to promote a closer working relationship
between users and designers. The facilitation of communication between users and designers is subject to discussion of the
ways in which communicative activities can be ‘optimised’ for successful requirements gathering, by making recommendations
based on the four dimensions to provide fruitful considerations for system designers. 相似文献
17.
Healthcare Modelling through Role Activity Diagrams for Process-Based Information Systems Development 总被引:1,自引:0,他引:1
Nandish V. Patel 《Requirements Engineering》2000,5(2):83-92
The aim of this paper is to introduce the socio-technical Role Activity Diagram modelling language to National Health Service
(NHS) information systems requirements engineering using a process approach. Most requirements engineering in the NHS is done
using data-driven methods such as data flow diagrams. Role Activity Diagrams provide not only a socio-technical method for
analysing a particular systems development problem, but they also offer a process-based approach for capturing workflows and
their associated information flows, and facilitate communication between analysts and users in an intuitive fashion. In particular,
they elicit the important roles in a process and the interaction and collaboration required to achieve the goals of the process.
The process approach has been applied in business information systems development. It is introduced here as a potential for
systems development in the NHS. 相似文献
18.
This paper presents an automated tool for scenario-driven requirements engineering where scenario analysis plays the central
role. It is shown that a scenario can be described by three views of data flow, entity relationship and state transition models
by slight extensions of classic data flow, entity relationship and state transition diagrams. The notions of consistency and
completeness of a set of scenarios are formally defined in graph theory terminology and automatically checked by the tool.
The tool supports automatic validation of requirements definitions by analysing the consistency between a set of scenarios
and requirements models. It also supports automatic synthesis of requirements models from a set of scenarios. Its utility
and usefulness are demonstrated by a non-trivial example in the paper. Case studies of the tools are also presented. 相似文献
19.
Linguistic Problems with Requirements and Knowledge Elicitation 总被引:1,自引:0,他引:1
David C. Sutton 《Requirements Engineering》2000,5(2):114-124
Human and conversational aspects of requirements and knowledge identification are employed to show that requirements ‘engineering’
is not the same as civil engineering or scientific problem solving. Not only can requirements not be made fully explicit at
the start of a project, they cannot be made fully explicit at all. A need is identified to enhance computer-based information
systems (CBIS) development methods to accommodate: plurality of incommensurable perspectives, languages and agendas; dynamic
representations of system features that can be experienced rather than abstracted and forced into an abstract paper-based
representation; recognition that CBIS development is in general a continuous process where users changing their minds is a
natural and necessary indication or organisational vitality.
It is suggested that prototyping and rapid application development go some way to addressing these requirements but that
they require further development in the light of the theoretical light thrown on the nature of the problem. 相似文献
20.
Cynthia E. Irvine Timothy Levin Jeffery D. Wilson David Shifflett Barbara Pereira 《Requirements Engineering》2002,7(4):192-206
Requirements specifications for high-assurance secure systems are rare in the open literature. This paper examines the development
of a requirements document for a multilevel secure system that must meet stringent assurance and evaluation requirements.
The system is designed to be secure, yet combines popular commercial components with specialised high-assurance ones. Functional
and non-functional requirements pertinent to security are discussed. A multidimensional threat model is presented. The threat
model accounts for the developmental and operational phases of system evolution and for each phase accounts for both physical
and non-physical threats. We describe our team-based method for developing a requirements document and relate that process
to techniques in requirements engineering. The system requirements document presented provides a calibration point for future
security requirements engineering techniques intended to meet both functional and assurance goals.
RID="*"
ID="*"The views expressed in this paper are those of the authors and should not be construed to reflect those of their employers
or the Department of Defense. This work was supported in part by the MSHN project of the DARPA/ITO Quorum programme and by
the MYSEA project of the DARPA/ATO CHATS programme.
Correspondence and offprint requests to: T. Levin, Department of Computer Science, Naval Postgraduate School, Monterey, CA 93943-5118, USA. Tel.: +1 831 656 2339;
Fax: +1 831 656 2814; Email: levin@nps.navy.mil 相似文献