Web-based distributed EJB BugsTracker: an integration of struts framework at web server, EJBs at application server, and a relational database

This Web-based Distributed EJB BugsTracker is an integration effort of the 4-tier Enterprise Java Bean -- EJB component architecture where it uses a web browser, a web server, an application sever, and a relational database server. The application is designed and built for software managers, engineers and quality assurance staffs that keep track of the software defects which are produced during the software development life cycle. It allows independent user login in multi-project environments. This project makes use of all the benefits of the J2EE technologies: maintainability, portability, and scalability. In addition, Container Managed Persistence (CMP 2.0) greatly simplifies the connection between the application and the database tiers which results in developing a portable application that is database-independent

Process modeling using ProSLCSE on web-enabled platform

Process modeling is a relatively complex task that needs to be addressed from a different point of view. The classical approach would be to design the model, to send it for evaluation, then to return feedback to the developing team, and to reevaluate the model with the feedback received from the parties involved. However, it is our understanding that the steps taken during the process modeling could benefit from the advantages that the Internet offers. To demonstrate the usefulness of Internet in process modeling, I have taken an existing tool, ProSLCSE, and implemented it with Java so that it can run on a web-enabled environment. This Web-enabled version of ProSLCSE, also called ProWEB, will not only facilitate the implementation, controlling or standardization of the models, but also accelerate the task of modeling in an efficient and effective way. The developing team of the models would benefit from the tool in a real-time environment. Other parties, like the monitoring agencies, or controlling bodies would add their modification to the application in a sequential form. The implementation of this Web-enabled process modeling will bring a new level of abstraction to the modeling and will minimize the difficulties due to geographical differences for \u27time-depending\u27 projects

Real world evaluation of aspect-oriented software development : a thesis submitted in partial fulfilment of the requirements for the degree of Master of Science in Computer Science at Massey University, Palmerston North, New Zealand

Software development has improved over the past decade with the rise in the popularity of the Object-Oriented (OO) development approach. However, software projects continue to grow in complexity and continue to have alarmingly low rates of success. Aspect-Oriented Programming (AOP) is touted to be one solution to this software development problem. It shows promise of reducing programming complexity, making software more flexible and more amenable to change. The central concept introduced by AOP is the aspect. An aspect is used to modularise crosscutting concerns in a similar fashion to the way classes modularise business concerns. A crosscutting concern cannot be modularised in approaches such as OO because the code to realise the concern must be spread throughout the module (e.g. a tracing concent is implemented by adding code to every method in a system). AOP also introduces join points, pointcuts, and advice which are used with aspects to capture crosscutting concerns so they can be localised in a modular unit. OO took approximately 20 years to become a mainstream development approach. AOP was only invented in 1997. This project considers whether AOP is ready for commercial adoption. This requires analysis of the AOP implementations available, tool support, design processes, testing tools, standards, and support infrastructure. Only when AOP is evaluated across all these criteria can it be established whether it is ready to be used in commercial projects. Moreover, if companies are to invest time and money into adopting AOP, they must be aware of the benefits and risks associated with its adoption. This project attempts to quantify the potential benefits in adopting AOP, as well as identifying areas of risk. SolNet Solutions Ltd, an Information Technology (IT) company in Wellington, New Zealand, is used in this study as a target environment for integration of aspects into a commercial development process. SolNet is in the business of delivering large scale enterprise Java applications. To assist in this process they have developed a Common Services Architecture (CSA) containing components that can be reused to reduce risk and cost to clients. However, the CSA is complicated and SolNet have identified aspects as a potential solution to decrease the complexity. Aspects were found to bring substantial improvement to the Service Layer of SolNet. applications, including substantial reductions in complexity and size. This reduces the cost and time of development, as well as the risk associated with the projects. Moreover, the CSA was used in a more consistent fashion making the system easier to understand and maintain, and several crosscutting concerns were modularised as part of a reusable aspect library which could eventually form part of their CSA. It was found that AOP is approaching commercial readiness. However, more work is needed on defining standards for aspect languages and modelling of design elements. The current solutions in this area are commercially viable, but would greatly benefit from a standardised approach. Aspect systems can be difficult to test and the effect of the weaving process on Java serialisation requires further investigation

Development Of A Personal Diet Plan Database Application For Persons With Severe Food Allergies

This project will research, analyze, design, and implement a computerized system that will assist patients in creating a personal diet plan based upon a rotation diet. This diet, specifically designed for patients with severe food allergies, requires that a patient may only eat a particular food every n days (where n is any number), and foods from the same biological food family every n days. Currently, patients use either pen-and-paper or a computerized spreadsheet to create weekly or monthly food meal plans for the diet plan. The meal plans are usually transferred by hand to their daily or weekly shopping lists. There are three main problems with the current system. First, many patients complain that in order to make their meal plans simple enough to follow easily, they tend to eat the same foods in the same order each week, so their diets have become very plain and uninteresting. Second, patients frequently make mistakes on their meal plans relating to which foods belong to a given food family, which defeats the purpose of the rotation diet plan. Finally, hand transferring the meal plans to shopping lists is time consuming and often inaccurate. The ultimate goal of this project is to create a computerized system that will assist patients to make up a personalized diet plan that allows them to enjoy a broader range of meals, and also to quickly and accurately make up shopping lists for the meals

Implementing a map based simulator for the location API for J2ME

The Java Location API for J2METM integrates generic positioning and orientation data with persistent storage of landmark objects. It can be used to develop location based service applications for small mobile devices, and these applications can be tested using simulation environments. Currently the only simulation tools in the public domain are proprietary mobile device simulators that are driven by GPS data log files, but it is sometimes useful to be able to test location based services using interactive map-based tools. In addition, we may need to experiment with extensions and changes to the standard API to support additional services, requiring an open source environment. In this paper we describe the implementation of an open source map-based simulation tool compatible with other commonly used development and deployment tools

Teaching Web Development Technologies: Past, Present, and (Near) Future

The advent of the World Wide Web not only fundamentally changes the way we do things, it also greatly changes how computer software are built. While this profound evolution of software development has caused many in the software industry to change their way of developing software, it has not caused many in the academics to change their way of teaching computing. This paper describes the evolution of a course that teaches web development technologies. The contents of the course in three different iterations, the observations made, the available educational resources employed, and the challenges ahead for the course are presented

Using a Class-Wide, Semester-Long Project to Teach Software Engineering Principles

A senior-level, project-based Software Engineeringcourse taught at the University of Central Arkansas serves asthe capstone course for the Computer Science Program andintroduces students to the theory, tools, and techniques used tobuild large-scale software systems in a project-driven setting.Foundational to the course is the use of a class-wide, semesterlongcourse project to emphasize the theoretical aspects of thesoftware process and the system used for scoring studentperformance on the project. One project is selected for theentire class with students divided into teams of four to sixstudents to support different functional requirement areas. Amilestone-driven approach is used following a modifiedversion of the Unified Process for project development.Student scores on the project are divided into a group score,assignable via a rubric-like grade sheet, and an individualscore which is determined by the individual’s effort asassigned using the task-management tool, Issue-Tracker.Experiences gained and lessons learned in teaching the courseare provided as a guide for those wishing to follow a similarapproach to teaching Software Engineering in the future

Upstream database and digital asset management in variable data printing

This study outlines the upstream database and digital asset management issues for variable data printing. The goal is to clarify what work environment and processes are needed during digital asset and data preparation. A literature review was conducted and complemented with the experiential experience of establishing and using a variable data preparation and testing platform