No description available.

The development process for creating J2EE web applications is complex and tedious, and is thus error prone. The quality of a J2EE web application depends on correctness of code as well as the efficiency and flexibility of its architecture. Although the J2EE specification has promised to hide the distributed nature of the application, application developers still have to be aware of this fact in both the design (architecture) and implementation (code) perspectives. In this thesis, we present the detailed design of our pattern-based J2EE development tool, RoadMapAssembler (RMA). RMA demonstrates how patterns can be used to generate efficient architectural code while also hiding the deployment logic and distributed nature of J2EE applications in the implementation perspective. Furthermore, it shows the generation of a J2EE framework as a process of assembling patterns in an incremental fashion using known inter-pattern relationships.

Object-Oriented design and development dominates both commercial and open source software projects. One of the principal goals of object-oriented design is to aid reuse, and hence, reduce future maintenance efforts of software systems. However, the on-going maintenance of large-scale software systems (both changes and faults) continues to be a significant proportion of the lifecycle of the system and the total investment cost. Understanding and thus being able to predict - or even reduce - the impact of the contributing factors of future maintenance efforts of a software system is thus highly beneficial to software practitioners. In this Thesis we empirically study a large, commercial software system with the principal aim to determine the contributing factors to the change and fault propensity over a three-year period. We consider the object-oriented design context of the software, specifically its inheritance characteristics, coupling and cohesion properties, object-oriented design pattern participation, and size. We also explore the effect of refactoring and test classes in the software. Our results show that several aspects of the design context of a class have an impact to the change and fault-proneness of the software. Specifically, we show that classes with high afferent or efferent coupling are more change and fault-prone; we also identify a number of design patterns whose participants tend to have a higher change and fault propensity than non-participants and we identify a range of inheritance characteristics (in terms of depth of inheritance and number of children) that result in an increase to change and fault-proneness. Furthermore we show that refactoring is a commonly occurring maintenance activity, although it is largely limited to simpler types of refactorings. Finally, we provide some insight into the co-evolution of production and test code during refactoring.

The development process for creating J2EE web applications is complex and tedious, and is thus error prone. The quality of a J2EE web application depends on correctness of code as well as the efficiency and flexibility of its architecture. Although the J2EE specification has promised to hide the distributed nature of the application, application developers still have to be aware of this fact in both the design (architecture) and implementation (code) perspectives. In this thesis, we present the detailed design of our pattern-based J2EE development tool, RoadMapAssembler (RMA). RMA demonstrates how patterns can be used to generate efficient architectural code while also hiding the deployment logic and distributed nature of J2EE applications in the implementation perspective. Furthermore, it shows the generation of a J2EE framework as a process of assembling patterns in an incremental fashion using known inter-pattern relationships.

Apply design pattern in software analysis and design can reduce time and cost by reuse proven and validated solution to avoid redesign. Design pattern provide general solution to specific problem domain, it is best to adopt design pattern in Platform Intendant Model (PIM). Model Driven Architecture (MDA) lack of methodology to judge problem domain from UML Diagram like sequential diagram, timing diagram or class diagram and how to apply design pattern in PIM mode. To alleviate the forgoing problem, this study proposed methodology to describe rule and step to apply design pattern, and present the difference between adopt design pattern by UML diagram. The research methodology is articulated using the design science research methodology. A usability study evaluation is performed to demonstrate its applicability with test case. With this proposed method, system analyst will improve software system flexibility and accuracy by design pattern after first phase PIM modeling, and object designed in software system will be low cohesion and high coupling .

Thesis (M.S.)--Ohio University, March, 2001. / Title from PDF t.p.

La co-construction et la réutilisation de modèles font l'objet de plusieurs travaux dans le domaine de la simulation. Cependant, dans le domaine plus spécifique de la Simulation Orientée Agent (SOA), nous pouvons constater un manque sur ces deux points malgré un besoin fort de la part des thématiciens. 
La co-construction est essentielle pour optimiser la mise en commun du savoir de différents experts, mais nous faisons souvent face à des divergences de points de vue. Les méthodologies existantes pour la co-construction en SOA ne permettent qu'un faible niveau de collaboration entre thématiciens durant la phase initiale de modélisation, ainsi qu'entre les des thématiciens avec les modélisateurs ou les modélisateurs-informaticiens... Pour faciliter cette co-construction, nous proposons de suivre une méthodologie de conception favorisant cette collaboration. 
La réutilisation de modèle octroie un gain de temps significatif, une amélioration du modèle et l'apport de nouvelle connaissance. Les méthodologies en SOA dans ce domaine existent. Cependant, dans le spectre de réutilisation, elles sont souvent limitées au niveau du modèle complet ou de l'agent avec l'impossibilité de "descendre" plus bas. 
L'expérience de EDMMAS, un cas concret d'un modèle issu de trois réutilisations successives, nous a permis de constater une nouvelle complexité qui découle de la démultiplication des comportements des agents et crée un décalage conséquent entre le modèle opérationnel et le modèle conceptuel. Notre objectif est de promouvoir la réutilisation aussi bien des modèles, que des agents et de leurs comportements.Pour répondre à ces questionnements, nous proposons dans ce manuscrit une manière de codifier et d'intégrer la connaissance provenant de disciplines différentes dans le modèle, tout en utilisant des modules "composables" qui facilitent la réutilisation. Nous proposons (i) une nouvelle architecture Agent (aMVC), appliquée dans un cadre multidynamique (DOM), avec l'appui (ii) d'une approche méthodologique (MMC) basée sur la décomposition et réutilisation des comportements. 
Cet ensemble de propositions, (i) et (ii), permet de conduire un projet pluridisciplinaire de SOA avec un grand nombre d'acteurs, facilitant la co-construction des modèles grâce à l'instauration de nouvelles synergies entre les différents acteurs participant à la modélisation. Les concepteurs pourront travailler de manière autonome sur leur dynamique et la plateforme fera l'intégration de ces dernières en assurant la cohésion et la robustesse du système. Nos contributions offrent la capacité de créer les briques élémentaires du système de manière indépendante, de les associer et de les combiner pour former des agents, selon des dynamiques conformément à l'approche DOM. Elles permettent ainsi de comparer la logique selon différentes possibilités pour une même dynamique et d'ouvrir la perspective d'étudier un grand nombre d'alternatives de modélisation d'un même système complexe, et de les analyser ensuite à une échelle très fine. / Co-building and reuse of models are at the center of several studies in the field of simulation. However, in the more specific field ofMulti-Agent Based Simulation (MABS), there is a lack of methodology to resolve these two issues, despite a strong need by experts.Model co-building is essential to optimize knowledge sharing amongst different experts, but we often face divergent viewpoints. Existing methodologies for the MABS co-building allow only a low level of collaboration among experts during the initial phase of modeling, and between domain experts with modelers or computer scientists... In order to help this co-building, we propose and follow a methodology to facilitate this collaboration. Model reuse can provide significant time savings, improve models’ quality and offer new knowledge. Some MABS methodologies in this area exist. However, in the spectrum of reuse, they are often limited to a full model’s reuse or agent’s reuse with the impossibility of reusing smaller parts such as behaviors. The EDMMAS experiment was a concrete case of three successive model reuses. It allowed us to observe new complexity arising from the increase of agents’ behaviors. This creates a gap between operational model and conceptual model.Our goal is to promote the reuse of models, agents and their behaviors.To answer these questions, we propose in this thesis a new way to codify and integrate knowledge from different disciplines in the model, while using "composable"modules that facilitate reuse.We propose (i) a new agent architecture (aMVC), applied to a multidynamical approach (DOM), with the support (ii) of a methodology (MMC) based on the decompositionand reuse of behaviors.Proposals (i) and (ii) allow us to lead a multidisciplinary MABS project with a large number of actors, helping the co-building of models through the introduction of synergies among the different actors involved in the modeling. They can work independently on their dynamics and the platformwill integrate those, ensuring cohesion and robustness of the system. Our contributions include the ability to create the building blocks of the system independently, associate and combine them to formagents. This allows us to compare possibilities for the same dynamic and open the prospect of studyingmany alternate models of the same complex system, and then analyze at a very fine scale.

Master of Science / Department of Computing and Information Sciences / Daniel A. Andresen / Keeping track of paper bills is always difficult and there is always a chance of missing bill payment dates. Online Bill Payment application is an interactive, effective and secure website designed for customers to manage all their bills. The main objective of this application is to help customers to receive, view and pay all the bills from one personalized, secure website there by eliminating the need of paper bills. Once customers register in the website, they can add various company accounts. The information is verified with the company and the accounts are added. After the customers add the company accounts they can receive notifications about new bills, payments and payment reminders. All the information dealing with sensitive data is passed through a Secure Socket Layer for the sake of security. This website follows MVC architecture. Struts is used to develop the application. Well established and well proven design patterns like Business Delegate, Data Access Object, and Transfer Object are used to simplify the maintenance of the application. For the communication between the website and companies, web services are used. Apache Axis2 serves as the web services container and Apache Rampart is used to secure the information flow between the web services. Tiles, JSP, HTML, CSS and JavaScript are used to provide a rich user interface. A part from these, Java Mail is used to send emails and concepts like one way hashing, certificates, key store’s, and encryption are implemented for the sake of security. The overall system is tested using unit testing, manual testing and performance testing techniques. Automated test cases are written whenever possible to ensure correctness of the functions. Manual testing further ensures that the application is working as expected. The system is subjected to different loads and the corresponding behavior is observed at different loads. The unit and manual testing revealed that the functionality of each module in the system is behaving as expected for both valid and invalid inputs. Performance testing revealed that the website works fine even when the server is subjected to huge loads.

No description available.

Recommender system blir allt vanligare och att kombinera recommender system med användningen av design patterns kan vara ett steg i rätt riktning för att komma närmre tekniker och program som skulle kunna öka kvaliteten hos programvaran i programvaruutveckling genom att öka utbyggbarheten och underhållbarheten hos programvaran. Syftet med arbetet i den här rapporten är att utvärdera ett design pattern recommender program. Programmet kommer att utvärderas med hjälp av intervjuer av utvecklare och fallstudier hos tre företag. Frågorna i intervjun kommer att bygga på kriterier som används för utvärdering av CASE verktyg.