Model Based Development of Quality-Aware Software Services

Modelling languages and development frameworks give support for functional and structural description of software architectures. But quality-aware applications require languages which allow expressing QoS as a first-class concept during architecture design and service composition, and to extend existing tools and infrastructures adding support for modelling, evaluating, managing and monitoring QoS aspects. In addition to its functional behaviour and internal structure, the developer of each service must consider the fulfilment of its quality requirements. If the service is flexible, the output quality depends both on input quality and available resources (e.g., amounts of CPU execution time and memory). From the software engineering point of view, modelling of quality-aware requirements and architectures require modelling support for the description of quality concepts, support for the analysis of quality properties (e.g. model checking and consistencies of quality constraints, assembly of quality), tool support for the transition from quality requirements to quality-aware architectures, and from quality-aware architecture to service run-time infrastructures. Quality management in run-time service infrastructures must give support for handling quality concepts dynamically. QoS-aware modeling frameworks and QoS-aware runtime management infrastructures require a common evolution to get their integration

The requirements management practices: A study at UUM IT

Requirements engineering is a main process in software engineering that focusing on development and managing the user requirements. One of the requirements engineering activities is requirements management. It plays an important role when it comes to the support of product development teams. Despite this, there is a lack of practice in requirements management activity in the software project development. Malaysian software markets are still facing several problems in requirements management practices such as requirements quality, requirements inadequately, and identification of requirements; with limited studies that address it. In this study, UUM IT as computer services provider in a local universities in Malaysia is design as case study, to represent as one organization in Malaysia software markets. This study aims to investigate the current situation for the requirement management in UUM IT, and assess the relationship CMMI level 2 with the requirements management practices in UUM IT. This study adopted mixed method through used questionnaire with the UUM IT team, as well as, interviews with managers of UUM IT for more reliability. The outcome of study showed that the UUM IT are used requirements management activities but there is a need for more attention and improve. Moreover, the study proposes CMMI appraisal method to enhance the performance of software development tea

Обеспечение качества программных средств в условиях изменяющихся требований

Рассматривается проблема обеспечения качества программных средств в условиях неясных и изменяющихся требований. Предлагается новый гибкий метод разработки программных средств – метод разработки, ведомой требованиями. В основе предлагаемого метода лежат такие принципы, как создание программной архитектуры на основе требований, управление реализацией изменяющихся требований, ориентация на быструю модификацию программных средств. Предлагаемый метод отводит требованиям основополагающую роль в процессе разработки программных средств. Он предполагает декомпозицию программного средства на компоненты, каждый из которых реализует отдельное требование или группу логически связанных требований, содержит метаинформацию о реализуемых требованиях, информацию о связях с другими компонентами, а также механизмы взаимодействия с другими компонентами.This paper outlines the problem of assuring software quality when requirements to software are changing, and these requirements are uncertain. A new agile method is presented – requirement-driven development. The method is based on the following principles: defining solution architecture from requirements, managing the implementation of changing requirements, and targeting on the ability to easily and fast modify software. The method defines that software requirements are always the key, and they are always on top of the things. The presented method splits the software to a set of components each of which implements a separate requirement (or a group of requirements), contains some metadata on the requirements being implemented, contains the information on links to another components, as well as the mechanisms to interoperate with another components

Penerapan Sistem Informasi Berbasis Web Untuk Pengelolaan dan Pengarsipan Dokumen

The web-based document archiving information system is an information system that is useful for managing archive storage where the information system created will assist in the process of storing and managing documents. Dr. Hazairin in order to improve the quality of the document archiving process, a web-based document archiving information system was designed, in order to avoid damage and also reduce the storage space for archives and the process of searching for archives can be done anywhere. The document archiving information system was created using the codeinether framework while the method stages carried out in this research process started from field studies, literature studies, interviews, system design and software where at this stage the database design system was used using MySQL, then system implementation and testing and the final stage is system integration and testing. After system integration and testing, the system can be applied to universities where access rights to the system will be divided into 7 parts, namely rectorate access requirements, faculty access requirements, institutional access requirements, bureau access requirements, study program access requirements, unit access requirements, and access requirements super admi

Requirements Management Tool Elements for The Malaysian Software Industry

Developing quality software is becoming a challenge that requires the practitioners to employ appropriate techniques, methodologies and good practices in software engineering. In the Malaysian software industry, the challenges are the practitioners lack practice in software engineering especially in the requirements management practices, and the requirements management tool is not widely facilitated during software development projects. In order to encourage them to overcome these problems, this paper attempts to recommend a requirements management tool that embeds the best practices in managing requirements. In addition, this paper aims to investigate the elements of the tool to guarantee that the tool is appropriate for Malaysian software needs. Then, a comparative study is carried out to search for various available requirements management tools that have those elements. The results show that there is no specific tool that has all the elements to fit the Malaysian software needs. Therefore, it is essential to develop a requirements management tool that is able to assist the software practitioners in developing quality software

An investigation of a requirements management tool elements

Developing quality software is becoming challenges that required the practitioners to employ appropriate techniques, methodologies and good practices in software engineering.In the Malaysian software industry, the challenges are the practitioners are lack of practicing software engineering especially in the requirements management practices as well as the requirements management tool is not widely facilitated during software project development.In order to encourage them to overcome these problems, this paper attempts to recommend a requirements management tool that embeds the best practices in managing requirements.In addition, this paper aims to investigate the elements of the tool to guarantee that the tool is appropriate for the Malaysian software needs.Then, a comparative study is carried out to search for various available requirements management tools that have those elements.The result shown that, there is no specific tool that has all the elements in order to fit the Malaysian software needs.Therefore, it is essential to develop a requirements management tool that able to assist the software practitioners in developing quality software

A study of requirements engineering practices among software developers at UUM Information Technology (UUMIT)

Requirements Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, validating and managing the requirements of a system in software development project. UUM has been supported by various systems in academic, administrative, students’ affair and many others. Most of the current systems are developed and maintained by the Information Technology Department (UUMIT). The aim of this study is to review the current requirements engineering practices and proposing requirements engineering practices during software development at UUMIT. The outsourcing of software development is rapidly growing because of its allied benefits in the limited resources of the organizations. The main problem that is discussed in this research is the lack of studies that support software development activities at the Information Technology department (UUMIT). The study used quantitative methodology and systematic literature review to answer research questions. The main significance of this study is helping educational institutes to produce quality software development and saving cost and time by implementing requirements engineering practices. In addition to that, the study contributes to UUM by identifying the activity needed for software development so that the management is able to allocate budget to provide adequate and precise training as well as seminars for the software developers. The researcher investigated three variables; Requirements Description, Requirements Development (Requirements Elicitation, Requirements Analysis and Negotiation, Requirements Validation), and Requirement Management. The results from the survey showed that the current practice of requirement engineering in IT department of UUM is encouraging, but need for further development because most of RE practices associated with requirement development and requirement management are achieved on a regular basis and not frequently. The researcher recommended providing effective training programs for UUMIT staffs on RE practices and increases their understanding on system requirements using RE practices to develop better systems for the university. Further investigation is required in the future to understand the effect of other RE practices on software developmen