90,866 research outputs found
An object-oriented analysis method for customer relationship management information systems
Abstract For the advances of Internet technologies in recent years, Electronic Commerce (EC) has gained many attentions as a major theme for enterprises to keep their competitiveness. Amongst all possibly desired endeavors for the EC, research has shown that effective management of customer relationships is a major source for keeping competitive differentiation. Therefore, it is commonly recognized as an important goal for an enterprise to promote its management of customer relationships through a prospect information system on the Internet to achieve the so-called Business-to-Customer EC. In this paper, we propose an object-oriented analysis method for the development of such a Customer Relationship Management Information System (CRMIS). The approach starts from the identification of prospect customers and their desired behaviors under preferable execution environments, and ends with the specification of system-internal objects/entities that collaborate to satisfy these behaviors and environments. The method is a use case driven approach with UML utilized and extended as its tool. To illustrate, the method is applied to an exemplified CRMIS for house agency
Object-oriented modelling with unified modelling language 2.0 for simple software application based on agile methodology
Unified modelling language (UML) 2.0 introduced in 2002 has been developing
and influencing object-oriented software engineering and has become a standard
and reference for information system analysis and design modelling. There are
many concepts and theories to model the information system or software
application with UML 2.0, which can make ambiguities and inconsistencies for a
novice to learn to how to model the system with UML especially with UML 2.0.
This article will discuss how to model the simple software application by using
some of the diagrams of UML 2.0 and not by using the whole diagrams as
suggested by agile methodology. Agile methodology is considered as convenient
for novices because it can deliver the information technology environment to
the end-user quickly and adaptively with minimal documentation. It also has the
ability to deliver best performance software application according to the
customer's needs. Agile methodology will make simple model with simple
documentation, simple team and simple tools.Comment: 15 pages, 30 figure
Goals/questions/metrics method and SAP implementation projects
During the last years some researchers have studied the critical success factors (CSFs) in ERP implementations.
However, until now, no one has studied how these CSFs should be put in practice to help organizations achieve success
in ERP implementations. This technical research report attempts to define the usage of Goals/Questions/Metrics (GQM)
approach in the definition of a measurement system for ERP implementation projects. GQM approach is a mechanism for
defining and interpreting operational, measurable goals. Lately, because of its intuitive nature the approach has
gained widespread appeal. We present a metrics overview and a description of GQM approach. Then we provide an example
of GQM application for monitoring sustained management support in ERP implementations. Sustained management support
is the most cited critical success factor in ERP implementation projects.Postprint (published version
A review of information flow diagrammatic models for product-service systems
A product-service system (PSS) is a combination of products and services to
create value for both customers and manufacturers. Modelling a PSS based on
function orientation offers a useful way to distinguish system inputs and
outputs with regards to how data are consumed and information is used, i.e.
information flow. This article presents a review of diagrammatic information
flow tools, which are designed to describe a system through its functions. The
origin, concept and applications of these tools are investigated, followed by an
analysis of information flow modelling with regards to key PSS properties. A
case study of selection laser melting technology implemented as PSS will then be
used to show the application of information flow modelling for PSS design. A
discussion based on the usefulness of the tools in modelling the key elements of
PSS and possible future research directions are also presented
Using Counts as Heuristics for the Analysis of Static Models
The upstream activities of software development are often viewed as both the most
important, in terms of cost, and the yet the least understood, and most problematic, particularly in terms of satisfying customer requirements. Business process modelling is
one solution that is being increasingly used in conjunction with traditional software
development, often feeding in to requirements and analysis activities. In addition,
research in Systems Engineering for Business Process Change, highlights the importance
of modelling business processes in evolving and maintaining the legacy systems that
support those processes. However, the major use of business process modelling, is to
attempt to restructure the business process, in order to improve some given aspect, e.g.,
cost or time. This restructuring may be seen either as separate activity or as a pre-cursor
to the development of systems to support the new or improved process. Hence, the
analysis of these business models is vital to the improvement of the process, and as a
consequence to the development of supporting software systems. Supporting this analysis
is the focus of this paper.
Business processes are typically described with static (diagrammatic) models. This paper
proposes the use of measures (counts) to aid analysis and comparison of these static
process descriptions. The proposition is illustrated by showing how measures can be
applied to a commonly used process-modelling notation, Role Activity Diagrams (RADs).
Heuristics for RADs are described and measures suggested which support those
heuristics. An example process is used to show how a coupling measure can be used to
highlight features in RADs useful to the process modeller.
To fully illustrate the proposition the paper describes and applies a framework for the
theoretical validation of the coupling measure. An empirical evaluation follows. This is
illustrated by two case studies; the first based on the bidding process of a large
telecommunications systems supplier, and the second a study of ten prototyping processes
across a number of organisations.
These studies found that roles of the same type exhibited similar levels of coupling across
processes. Where roles did not adhere to tentative threshold values, further investigation
revealed unusual circumstances or hidden behaviour. Notably, study of the prototyping
roles, which exhibited the greatest variation in coupling, found that coupling was highly
correlated with the size of the development team. This suggests that prototyping in large
projects had a different process to that for small projects, using more mechanisms for
communication. Hence, the empirical studies support the view that counts (measures)
may be useful in the analysis of static process models
What is Product-Service Systems (PSS)? A Review on PSS Researches and Relevant Policies
In order to achieve sustainable society, it is necessary to transform industrial structure to the one that does not reduce the Earth's resources. Under this circumstance, a business model of "not selling goods, but selling services" has been expected as a measure of co-existence of business and the environment. This idea, which is called as "Product-Service Systems: PSS" or "Servicizing" etc., has been studied in Europe, the United States and international organisations, and is now studied in Japan. However, the idea of PSS is still not effectively used for policy development.One of the major reasons is that PSS concept itself is under-developed. Under the unclear concept of PSS, researchers are working towards more scientific understanding while policy makers are trying to develop new policy measures, and there is confusion in those communities. In order to develop policy measures, it is necessary to make clear the position of PSS in socio-economic system. This paper overviews previous PSS researches and relevant policy measures conducted in Japan, the US and EU, and tries to grasp the context of researches and policy activities and to find out the agenda of the current status. The characteristics of PSS rest on the innovative relationship between producer and consumer. However, PSS researches are stuck at measurement of environmental loads, and relevant policies tend to be rest on the ones targeting producers. In order to get out of this situation, it is necessary to ask question what is PSS and to make it clear where PSS can be positioned in socio-economic system. PSS is important, because PSS has an element of creating sufficiency as well as eco-efficiency. It is recommended that PSS concept needs to be examined as a research effort, and environmentally sound product policy needs to be systematically organised
A goal-oriented requirements modelling language for enterprise architecture
Methods for enterprise architecture, such as TOGAF, acknowledge the importance of requirements engineering in the development of enterprise architectures. Modelling support is needed to specify, document, communicate and reason about goals and requirements. Current modelling techniques for enterprise architecture focus on the products, services, processes and applications of an enterprise. In addition, techniques may be provided to describe structured requirements lists and use cases. Little support is available however for modelling the underlying motivation of enterprise architectures in terms of stakeholder concerns and the high-level goals that address these concerns. This paper describes a language that supports the modelling of this motivation. The definition of the language is based on existing work on high-level goal and requirements modelling and is aligned with an existing standard for enterprise modelling: the ArchiMate language. Furthermore, the paper illustrates how enterprise architecture can benefit from analysis techniques in the requirements domain
- …