Fig 1 - uploaded by Arantza Irastorza
Content may be subject to copyright.
Source publication
Several guidelines have been proposed for com- ponent-based design. A key step in these meth- odologies is component partition, whereby the system's functional requirements are assigned to the components. This work compares the differ- ent partition methods proposed so far. To this end, the same case study is applied to each method, and the resulti...
Contexts in source publication
Context 1
... us consider the information system of a bank. During the requirements analysis the fol- lowing use cases have been identified (see figure 1): ...
Context 2
... to give support to the 'Loan request' use case, it will only be necessary that CParty and CAccount offer in their interfaces the corresponding services, which are IPartyL and IAccountL. This possibility is shown in figure 12, where the CLoan compo- nent only offers the ILoan interface and uses the IAccountL and IPartyL interfaces. In this exam- ple, only the Loan class will be part of the CLoan component. ...
Context 3
... the 'Loan request' use case regulates the loan granting, depending on the state of the ac- count, it would be possible to use the State design pattern [6] for this design, too (see figure 10). From this pattern a StateAccount class is defined. ...
Context 4
... the same way than the CLoan component, this new component will not include all pattern classes. Since the Account class is already inte- grated in the CAccount component, a new inter- face, IAccountSt, will be added to the component in order to provide a service to the CStateAccount component as shown in figure 12. ...
Context 5
... the other hand, the analysis of the 'Special account offer' use case provides a possibility for using the Observer behavioural pattern [6] in figure 11. The 'Special account offer' use case makes offers to those accounts that comply with certain conditions. ...
Context 6
... the partition phase, this pattern would give rise to another component, called COb- server. Since the Account class is already inte- grated in the CAccount component, the IObserved interface will be added to the CAccount compo- nent in order to provide a service to the new CObserver component (see figure 12). This new component will only include the Observer class. ...
Context 7
... new component will only include the Observer class. Figure 12 shows the resulting component dia- gram after a partition process based on design patterns. ...
Context 8
... an initial class diagram is de- scribed for each component. Figure 13 shows the class diagrams for our three domains. The method recommends to take into account the design pat- terns in order to define the class diagrams, since many problems are reoccurring. ...
Context 9
... a state diagram is defined for each class and the use cases are again analysed by means of their sequence and collaboration diagrams. Figure 14 shows the collaboration diagram of the 'Loan request' use case. ...
Context 10
... this collaboration diagram, the checkIdentifier and getSalary services in the CParty component and the getState and getAver- ageBalance services in the CAccount component are identified. These services will be added to the list of methods of the respective classes in the class diagram of figure 13. The result component diagram for the 'Loan request' use case, is shown in figure 15. ...
Context 11
... services will be added to the list of methods of the respective classes in the class diagram of figure 13. The result component diagram for the 'Loan request' use case, is shown in figure 15. The process would be completed when all use cases had been analysed. ...
Context 12
... results in grouping all those operations/attributes affected by both changes into one component. A possible outcome of this process is shown in figure 16. The CAccount component includes the operations/attributes affected by the first two changes, while CMoneyTransfer includes those affected by the other three changes. ...
Similar publications
![Table 1 . Bartle's game player types [13]](profile/Sangkyun-Kim-2/publication/310465839/figure/tbl1/AS:669209092689921@1536563289028/Bartles-game-player-types-13_Q320.jpg)
![Table 2 . Definition of PLEX factors [18]](profile/Sangkyun-Kim-2/publication/310465839/figure/tbl2/AS:669209092706304@1536563289078/Definition-of-PLEX-factors-18_Q320.jpg)
Motivation is one of the key factors for organization's success. A gamification has been emerging as a new breakthrough for motivation of organization's members. The managements and practitioners easily face with the problems that there are very few guidelines or methods that can be referred when they are trying to introduce a gamification. To prov...
In this article, the many definitions of research by design are used to build a coherent model for a research by design process. Three phases are identified, each with their own characteristics and types of activities: the pre-design, the design and the post-design phase. In combination with several practical examples of design-led research project...
This paper discusses the opportunities and challenges of Ambient Intelligence (AmI) technologies in the context of classroom education, and presents the methodology and preliminary results of the development of an augmented school desk which integrates various AmI educational applications. The overall objective is to assess how AmI technologies can...
This paper presents a methodology for designing a containerized and distributed open science infrastructure to simplify its reusability, replicability, and portability in different environments. The methodology is depicted in a step-by-step schema based on four main phases: (1) Analysis, (2) Design, (3) Definition, and (4) Managing and provisioning...
Traditional user-centered methodologies have been developed for system-level and detailed-level design and not for concept-level design. This paper discusses thinking models and user-centered practices useful in the earliest phase of product developmentóproduct concept design.
