Search

PageRank is an algorithm that brings an order to the Internet by returning the best result to the users corresponding to a search query. The algorithm returns the result by calculating the outgoing links that a webpage has thus reflecting whether the webpage is relevant or not. However, there are still problems existing which relate to the time needed to calculate the page rank of all the webpages. The turnaround time is long as the webpages in the Internet are a lot and keep increasing. Secondly, the results returned by the algorithm are biased towards mainly old webpages resulting in newly created webpages having lower page rankings compared to old webpages even though new pages might have comparatively more relevant information. To overcome these setbacks, this research proposes an alternative hybrid algorithm based on an optimized normalization technique and content-based approach. The proposed algorithm reduces the number of iterations required to calculate the page rank hence improving efficiency by calculating the mean of all page rank values and normalising the page rank value through the use of the mean. This is complemented by calculating the valid links of web pages based on the validity of the links rather than the conventional popularity.

The potentially many software system input combinations make exhaustive testing practically impossible. To address this issue, combinatorial t-way testing (where t indicates the interaction strength, i.e. the number of interacting parameters (input)) was adopted to minimize the number of cases for testing. Complimentary to existing testing techniques (e.g. boundary value, equivalence partitioning, cause and effect graphing), combinatorial testing helps to detect faults caused by the faulty interaction between input parameters. In the last 15 years, applications of meta-heuristics as the backbone of t-way test suite generation have shown promising results (e.g. Particle Swarm Optimization, Cuckoo Search, Flower Pollination Algorithm, and Hyper-Heuristics (HHH), to name a few). Supporting the No Free Lunch theorem, as well as potentially offering new insights into the whole process of t-way generation, this article proposes a new strategy with constraint support based on the Whale Optimization Algorithm (WOA). Our work is the first attempt to adopt the WOA as part of a search-based software engineering (SBSE) initiative for t-way test suite generation with constraint support. The experimental results of the test-suite generation indicate that WOA produces competitive outcomes compared to some selected single-based and population-based meta-heuristic algorithms.

Information Security Management (ISM) is a systematic initiative in managing the organisation’s information security. ISM can also be defined as a strategic approach to addressing information security (IS) risks, breaches, and incidents that could threaten the confidentiality, integrity, and availability of information. Although organisations have complied with ISM requirements, security incidents are still afflicting numerous organisations. This issue shows that the current implementation of ISM is still ineffective. The ineffective ISM implementation illustrates the low maturity level. To achieve a higher level of maturity, organisations should always evaluate their ISM practices. Several maturity models have been developed by international organisations, consultants, and researchers to assist organisations in assessing their ISM practices. However, the current models do not evaluate ISM practices holistically. The measurement dimensions in current models are more focused on assessing certain factors only. This caused the maturity assessment to be not executed comprehensively. Therefore, this study aims to address this shortcoming by proposing a comprehensive maturity assessment model that takes into account ISM success factors to evaluate the effectiveness of the implementation. This study adopted a mixed-method approach, which comprises qualitative and quantitative studies to strengthen the research finding. The qualitative study analyses the existing literature and conducts interviews with nine industry practitioners and six experts while the quantitative study involves a questionnaire survey. The data obtained from the qualitative study were analysed using content analysis while the quantitative data employed statistics analysis. The study identified fourteen success factors and fifty-seven maturity dimensions, which each contains five maturity levels. The proposed model was evaluated through experts’ reviews to ensure its accuracy and suitability. The evaluation shows that the model can identify the ISM maturity level systematically and comprehensively. This model will ultimately help the organisations to improve the weaknesses in the implementations thus diminishing security incidents.

Software engineering (SE) research addresses not only technical issues but also human behaviour. SE is considered as an immature discipline because many technical and social issues concerning software development and management have yet to be specified. SE in general is inclined towards quantitative approaches. Nevertheless, qualitative methods are still appropriate for SE research as the methods encourage deep understanding of subject matter. Grounded Theory (GT) is regarded as one of the potential qualitative methods that is applicable to SE research. The method is able to transform less and unknown SE phenomena into cohesive theories through systematic discovery of empirical data from the ground. This paper shares some encounters of using GT in SE research based on the reflection made on several SE research projects covering various phases of software development life cycle. The encounters are then transformed into adaptations and classified as GT practices for SE research, as an effort to inspire the spirit of using GT in SE particularly among novices. The practices embrace aspects concerning formulating research questions, handling preconceptions, utilising software tools, getting access to data and presenting theory and its development process. To illustrate on how the practices were derived, a case study is presented. The proposed GT practices could act as the starting point of adopting GT in SE research. They shall be refined and improved in future to possibly become best practices when more and more experience of using GT in SE are obtained.

Information technology and communication (ICT) plays an important role as a catalyst for organisational development and innovation. However, old information systems that are known as legacy systems often expose organisations to the risk of business failure. These systems are not only impeding the advancement in technology strategy but also hindering the organisations’ business competitiveness. Nevertheless, legacy systems are essential in supporting critical functions in organisations including the public sector and could not be scrapped easily. These systems need to be given a new strength through modernisation to continue providing the best service in line with global trends. Modernisation is a complex task that involves several related aspects. In the context of the public sector, legacy systems involve a complicated information relationship, environment, and culture, while ensuring the citizens are of high priority. The implementation of a digital government represents the transformation of the public service delivery to the citizens that emphasises a citizen-centric design. This study, therefore, aims to address this concern by reviewing the factors involved and suggesting a guideline in the form of a conceptual model to assist in the modernisation of legacy systems for a citizen-centric digital government. Data from the theoretical study were analysed using content analysis. The results show that the legacy systems’ modernisation comprised four main aspects, namely human, process, product, and organisation aspects, with related factors and elements. This model contributes as a reference for the public sector and provides overall guidance in performing legacy systems modernisation.

Requirements elicitation is the most critical phase in software requirements engineering. The process is resource intensive, as it concerns with a lot of dedicated stakeholders gathering purposefully to present and stipulate software requirements. The extent of effectiveness of the process is greatly influenced by the suitability of the stakeholders in the process of gathering the requirements. Previous studies indicate that improper stakeholder selection normally lead to unsuccessful requirements elicitation process. Such phenomena would later cause serious impacts to projects such as costly rework, overrun schedule and poor quality software. This study addresses this issue by proposing a model for selecting the suitable stakeholders during requirements elicitation process. The study adopts both the quantitative data collection and analysis. The data gathering was done through survey questionnaire among 300 project managers and analysts. The study employs the Structural Equation Modelling (SEM) to analyse the quantitative data. The results indicate that selecting stakeholders with appropriate characteristics such as stakeholders role, knowledge and communication skills have significant effects on the requirements elicitation phase. The results also reveal that requirements elicitation phase has significant influence on requirements quality. This model is useful for project managers to decide on appropriate stakeholders who are going to be chosen based on their characteristics during requirements elicitation phase.

Rapid development of information technology and communication (ICT) has increased the use of information systems in organizations since a decade ago. At the same time, many organizations are still using old information systems to support their business, known as legacy systems. Even though these systems cause technical problems, but they are still used to support service delivery to the customer. These systems are also essential to organizations as they have been operated for many years and possess high business value. The operation of legacy systems cannot be stopped quickly, as it will affect daily business tasks. However, organizations with legacy systems need to think about the ability of the systems to support their future direction. Modernization of legacy systems needs to be implemented to ensure the systems are aligned with global changes as well as improving the competitiveness of the organizations. This study, therefore, reviewed the phases and factors involved in legacy systems modernization to identify gaps and their insufficiencies. There are many studies on legacy systems, but only a few have focused on the overall process of legacy systems modernization. Most studies on legacy systems are technical in nature and refer to specific aspects and phases of modernization. This study aims to provide overall guidance to the organizations in performing legacy systems modernization.

Agile methods adoption has increased in recent years because of its contribution to the success rate of project development. Nevertheless, the success rate of projects implemented using Agile methods has not completely reached its expected mark, and selecting the appropriate Agile methods is one of the reasons for such lag. Selecting the appropriate Agile methods is a challenging task because there are so many methods to select from. In addition, a lot of organizations consider the selection of Agile methods as a mammoth task. Therefore, to assist Agile team members, this study aimed to investigate how the appropriate Agile methods can be determined for different projects. Based on a Grounded Theory study, 23 Agile experts drawn from 19 teams across thirteen countries were interviewed. Hence, this study employed the Ground Theory of selecting Agile methods. Sixteen factors, grouped into five categories, have been found to affect the selection of twenty Agile methods. The nature of project (size, maturity, criticality and decomposability), development team skills (communication skills, domain knowledge, team technical skills and maturity), project constraints (cost/value/ROI, cost of change, time, scope and requirements volatility), customer involvement (collaboration, commitment and domain knowledge) and organizational culture (type of organizational culture) are the key factors that should guide Agile team members in the selection of an appropriate Agile methods based on the value these factors have for different organizations and/or different projects.

Information Security Management (ISM) concerns shielding the integrity, confidentiality, availability, authenticity, reliability and accountability of the organisation’s information from unauthorised access in order to ensure business continuity and customers’ confidence. The importance of information security (IS) in today’s situation should be given due attention. Recognising its importance, organisations nowadays have devoted wide efforts in protecting their information. They establish information security policy, processes, and procedures as well as reengineer their organisational structures to align with ISM principles. Regardless of the efforts, security incidents continue to occur in many organisations. This phenomenon shows that the current implementation of ISM is still ineffective due to unaware of the factors contributing to the success of ISM. Thus, the objective of this paper is to identify ISM success factors and their elements through a large-scale survey. The survey involves 243 practitioners from statutory bodies, public and private organisations in Malaysia. The results of the survey indicate that top management, IS coordinator team, ISM team, IS audit team, employees, third parties, IS policy, IS procedures, resource planning, competency development and awareness, risk management, business continuity management, IS audit and IT infrastructure are the factors that contribute to the success of ISM implementation. These factors shall guide practitioners in planning and refining ISM implementation in their organisations.

Requirements change has been regarded as a substantial risk in software development projects. The factors that contribute to the risk are identified through impact analysis, which later determine the planning of the change implementation. The analysis is however not straightforward as the risk factors that constitute requirements change implementation is currently not much explored. This paper identifies the risk factors by firstly collating them qualitatively through a review of related work and a focus group study. The factors are then confirmed quantitatively through a survey in which data is analysed by using Partial Least Squares Structural Equation Modelling (PLS-SEM). The survey comprise of 276 practitioners from software industry who are involved in the impact analysis. The results indicate that User, Project Team, Top Management, Third Party, Organisation, Identification of Change, Existing Product and Planning of Change Implementation are the significant risk factors in planning of requirements change implementation.

Rapid and unpredictable technology advancements cause a rise in demand for software products that can be delivered faster, adapt to volatile changes and save cost. Over the years, Agile Software Development (ASD) becomes more suitable as the software process that can cater to those demands while still maintaining the quality desired. With this Agile nature, it is apparent that the team that develops the software product need to have unique features as well. The team should also be formed correctly to gain effectiveness, strong performance and ultimately project success. Ineffective teams can be caused by, among others, conflict, inadequate skillset, unbalanced role assignment, lack of teamwork and non-competent team members. However, by far, the characteristics that need to be considered in forming effective teams are yet to be formalized. Thus, this study aims to identify the necessary characteristics in composing a competent team that is well balanced and can create coherent teamwork. The study involves a qualitative literature review which includes past studies about team formation specifically in the software development domain. The data were collected from online journal databases and analyzed using content analysis. From the analysis, six characteristics together with their attributes were identified as vital in team formation. Another two characteristics were also identified as influencing the six-team formation characteristics. These findings will need further empirical rigor before they can become a complete Agile Software Development team composition model. This model is believed to assist Agile practitioners in forming effective teams for their development projects.

Persekitaran dan proses perniagaan yang dinamik menyebab perubahan keperluan dalam perisian tidak dapat dielak. Perubahan keperluan perisian perlu diurus dengan sebaiknya melalui analisis impak yang melibatkan pengenalpastian faktor penyumbang dan penilaian kesan perubahan keperluan terhadap persekitaran semasa. Analisis impak ini perlu disempurna oleh pasukan yang khas iaitu Jawatankuasa Kawalan Perubahan (JKP). Pada dasarnya, analisis impak membantu JKP memperoleh gambaran potensi impak sesuatu perubahan terhadap organisasi sebelum melaksananya. Ini perlu kerana analisis impak yang tidak sempurna boleh menjejas projek sekali gus kemampanan organisasi. Kajian lampau mengenal pasti beberapa faktor teknikal dan bukan teknikal yang perlu diambil kira semasa analisis impak perubahan keperluan perisian. Namun faktor tersebut dikaji secara bersendiri dan berasingan menyebabkan analisis impak menyeluruh sukar dilakukan. Justeru, kajian ini bertujuan mengenal pasti dan menggabung faktor tersebut sebagai model analisis impak perubahan keperluan yang bersepadu. Kajian ini bersifat kualitatif dengan data dikumpul mengguna teknik temu bual secara kumpulan fokus. Data yang dikumpul dianalisis mengguna teknik analisis kandungan. Hasil analisis mendapati terdapat empat kategori faktor yang terlibat iaitu Manusia, Proses, Teknologi (sedia ada) dan Organisasi. Setiap kategori faktor mengandungi faktor dan elemen tertentu yang dihubungkan untuk menggambarperkaitannya. Model ini dapat diguna oleh JKP sebagai panduan menilai sesuatu permintaan bagi perubahan keperluan perisian.

Case Method (CM) is a teaching technique that uses real cases as a tool for delivering a particular subject. Software Engineering (SE) is a discipline that concerns the principles, methods and tools for developing and improving software. SE education therefore tends to be too theoretical. To impose realism where the students can be exposed to real scenarios and learn to apply those theories through discovery, CM is seen as necessary for SE education. This paper presents a survey conducted to a set of students who employed CM in learning SE. The objective of the survey was to assess the degree of acceptance among SE students on the usage of CM. The participants were Undergraduates and Masters that comprise local, international and matured students. The data were analysed quantitatively using descriptive statistics and qualitatively through content analysis. The results indicate that CM can be useful for SE education. The participants accepted CM because it improves the understanding of subject matter, enhances interpersonal skills and provides meaningful learning experience. Nonetheless, CM is seen as effective only when certain conditions are met. The results can be used by SE educators to enhance teaching and learning in future.

Usability has been increasingly recognized as a significant quality dimension to determine the success of mobile applications. Due to its importance, a number of usability guidelines have been proposed to direct the design of usable applications. The guidelines are intended particularly for desktop and web-based applications. Mobile applications on the other hand are different in many ways from those applications due to the mobility nature of mobile devices. To date, the usability guidelines for mobile applications are very limited. They in fact are isolated, which makes usability evaluation for mobile devices more difficult. This study aims to address this issue by proposing a set of usability dimensions that should be considered for designing and evaluating mobile applications. The dimensions are illustrated as a model that considers four contextual factors: user, environment, technology and task/activity. The model was proposed based on the reviews of previous related studies, which were analyzed by using content analysis approach. Twenty-five dimensions were found from the analysis. The dimensions however were synthesized and prioritized based on their importance towards designing usable mobile applications. As a result, ten most important dimensions were outlined in the model. The model can be used by practitioners and researchers as a guideline to design usable mobile applications and further research can be conducted in the near future.

Student Centered Learning Environment is a learning environment that describes thinking methods about learning and teaching that emphasizes student responsibility in learning activities such as planning, interacting with lecturers and other students, doing research and evaluating learning. This means that students play an important and active role in learning. Applying the concept to Computer Science final year project requires students to be independent in carrying out activities related to the research literature, mastering software tools or libraries, designing, developing and testing software, and writing reports. Theoretically, a supervisor plays the role of an advisor to ensure the project is successfully completed within the designated timeframe. However, most of the time, students are often given the freedom to manage their project, sometimes without adequate guidance from supervisors. This is a rather complicated problem for moderate and weak students. For students to actively participate in their own learning they must possess self-monitoring and other meta-cognitive skills which are not necessarily inherent in every individual. A survey done in our faculty shows that Computer Science students face a number of problems in the course of accomplishing their final year project which include time management, anxiety, academicachievements, and capability of managing project and strategy to complete the project (listed according to factors that most affected them). This paper will discuss the role of the Final Year Project Supervision Management System in support of student-centered learning for final year project at the School of Computer Science. Mapping between system features and principles of student centered learning is also presented. The system has been developed to monitor students’ progress both in software development and report writing, as well as managing the process of allocating supervisors and examiners to students and grading.

Problem statement: Education management is a centralized process of planning, monitoring and controlling entities involved in education affairs so that they align with educational aspirations. It normally concerns several layers of administration that requires different types of information from various operational units. Operational units in education however are scattered and managed independently. As a result, most information is isolated where it is not easily and readily available. This hinders executives from making good judgment since a holistic view about the operations cannot be obtained instantly. Approach: This issue can be resolved, for instance, by having an Executive Information System (EIS). EIS is a dedicated information system that has the capacity to not only retrieving and storing information but also performing comparative analyses through its mapping and merging feature. EIS however does not depend entirely on technology. To succeed, an EIS should be developed based on concrete underlying bases that consider both operational and business aspects. The bases are called Critical Success Factors (CSF). This study discusses the CSF that influence EIS development for education domain. The factors were identified through reviews of related work and two iterations of field work that used semi-structured interviews as the means of data collection. The study adopted qualitative approach where the data were analyzed by using content analysis. Results: The collated CSF form a framework of successful EIS development, which can be employed by education stakeholders as a guideline for developing EIS in the institution. Conclusion: The framework is seen as feasible and practical to be applied in education domain as it considers the necessary elements of education business.

Software testing outsourcing appears to be the best alternative to acquire better software quality with competent ratification by extrinsic parties who have the capability to do it. Through the effort, organizations are peeking to promising benefits constitute in it such as current testing technology, experts, an abridgment of the project’s duration and more concentration on the main organisation’s activity. Along with these benefits, one important reason that encourages the decision is optimization of cost expenditure, which the strategy is perceived as a good move for a competitive organization. However, implementing such preference eventually results in a different outcome. Organizations have to bear the higher cost and incur losses of cost deviation from the expected estimation. The conflicting between cost and benefits raises an important concern of striving better cost estimation for such projects. This paper aims to address this interest by analyzing the existing literature in order to identify the contributing factors towards better cost estimation for software testing outsourcing project-context. The analysis is done using the content analysis method. The results could be divided into two categories; which are the cost items and contributing factors. Cost items consist of direct cost and indirect cost, which refers to the expenses for the project. While the contributing factors consist of people and environment, which are needed to produce accurate cost estimation. The findings provide an insight to excogitate attentively the essentials in the endeavor of improving the exactitude of cost estimation for software testing outsourcing project.

Scrumban is a combination of practices from Kanban and Scrum practices to manage the development of software based on different project situations. Scrumban practices formation can differ based on different projects and team members. However, since each method has its own pros and cons, inappropriate formation of Scrumban practices may lead to increased waste and time of development, and decreased quality, which in turn, affect the Agile organizations and cause inefficient and ineffective development. Practitioners of Kanban and Scrum are convinced that a combination of both methods is better than the use of one and thus, practitioners should be guided in their decision making. This study aims to show how Scrumban method is formed based on a combination of Kanban and Scrum methods. Scrumban formation and the identification of the factors, which assist in the combination of Kanban and Scrum were conducted through a review of the previous work and semi-structured interviews with 7 Agile experts, after which, content analysis was conducted to analyse the gathered data. Different factors - the method prescription, roles and responsibilities, adoption time, team size, batch size, requirements prioritization, feature size, lead time, technical practices, cost and quality, assist Agile team members in the formation of Scrumban by combining appropriate Kanban and Scrum practices. In addition, Scrumban were found to be more appropriate than Scrum or Kanban in saving time, improving quality and minimizing waste.

Problem statement: Formal notations employ mathematical symbols and interpretation to illustrate system elements. The formality imposed by the notations allows the accuracy and consistency of a system model to be confirmed by verification tools. Formal notations on the other hand are difficult to understand and use by most users. As supporting instruments, verification tools are expected to be as usable as possible to overcome this limitation. Approach: This study presented a survey conducted on two instances of verification tools that support a formal method, namely B. The focus of the survey was to identify the important features that are necessary for verification tools to become usable to users. The survey assessed the tools’ usability based on the Cognitive Dimensions of Notations (CD) framework and several criteria suggested by the International Organization for Standardization (ISO). Sixty-three participants responded to the survey. The data was analyzed by using the grounded theory. Results: The analysis enabled the identification of abstract concepts and properties that formed a design guideline for usable verification tools. The guideline includes there main aspects; Interface, Utilities and Resources Management. Conclusion: The guideline acts as a roadmap for tool designers to design verification tools that promote the use of formal notations.

The modeling of computer software is complex and error prone. Modeling methods and languages must be usable which implies easy to learn. Cognitive dimensions and grounded theory were used to analyse the usability and learnabilty of the new modeling language Unified Modeling Language- B: UML-B. A systematic survey of users’ encounters and interactions with UML-B clarified its good and bad features. The results indicate that UML-B is more usable and learnable than comparative modeling languages such as ‘B’. The results of this study will improve the future development of UML-B to increase its learnability hence its usability.

Conceptual models communicate the important aspects of a problem domain to stakeholders. The quality of the models is highly dependent on the usability of the modeling method used. This paper presents a survey conducted on a method that integrates the use of a semiformal notation, namely the Unified Modeling Language (UML) and a formal notation, namely B. The survey assessed the usability of the method by using the grounded theory, the Cognitive Dimensions of Notations (CD) framework, and several criteria suggested by the International Organization for Standardization (ISO). Ten participants responded to the survey. The results suggest that the method is accessible to users when the principles and roles of each notation are obvious and well understood, and when there is strong support from the environment. Supported by the findings, a usability profile based on CD for designing a method that integrates semiformal and formal notations is proposed.

Software testing outsourcing is becoming attractive among organisations that desire to gain high quality products within reasonable cost while allowing testing experts to assure its quality. Despite these promising advantages however, organisations have yet to learn the factors that contribute to such projects’ success. The necessary planning and actions could not thus be taken towards the effort. Consequently, software testing outsourcing projects still fail. This study aimed to address this concern by collating the factors from previous research. The investigation continued by confirming the factors besides discovering other relevant factors from software testing practitioners. This study adopted qualitative approach where it employed semi-structured interviews involving five practitioners, who represented both client and vendor. The data were analysed using content analysis. The results show that there are two aspects to be considered, namely Process and People. The former contains nine factors and the latter comprises four factors. Each factor has specific elements, which delineates the characteristics or roles that it owns. The findings provide practitioners with understanding of conducting software testing outsourcing projects effectively.

Computer Programming is a core subject in Computer Science. This course requires the analysis and solving of problem critically. These skills are also required in preparing Computer Science students for the career world. Problem-based Learning is thus regarded as one of the suitable methods for Teaching and Learning programming. Although this method has been proven to hone student skills in other areas such as Medicine, its usage in Computer Programming courses has yet to bring about any impacts. This is because, to date, Problem-based Learning has been employed based on the practitioner’s intuition without specifically meeting the principles and concepts of Programming courses from the human, process, and product aspects. The human aspect involves practitioners during the process. The framework for this study is built using a qualitative method that combines theoretical and empirical studies. The theoretical study includes reviews of the implementation of previous Problem-based Learning in Computer Science as well as other fields. The empirical study involves information obtained from both the theoretical and empirical studies were analysed by utilising the Thematic Analysis method to generate the proposed framework for this study. This framework can be utilised as a guide for the management and practitioners in Computer Science education to use Problem-based Learning as an effective Teaching and Learning method for Programming courses.

Agile methods have become popular in recent years because the success rate of project development using Agile methods is better than structured design methods. Nevertheless, less than 50 percent of projects implemented using Agile methods are considered successful, and selecting the wrong Agile method is one of the reasons for project failure. Selecting the most appropriate Agile method is a challenging task because there are so many to choose from. In addition, potential adopters believe that migrating to an Agile method involves taking a drastic risk. Therefore, to assist project managers and other decision makers, this study aims to identify the key factors that should be considered when selecting an appropriate Agile method. A systematic literature review was performed to elicit these factors in an unbiased manner and then content analysis was used to analyze the resultant data. It was found that the nature of project, development team skills, project constraints, customer involvement and organizational culture are the key factors that should guide decision makers in the selection of an appropriate Agile method based on the value these factors have for different organizations and/or different projects.

Software Engineering (SE) education has been reported to fall short in producing high quality software engineers. In seeking alternative solutions, Case Method (CM) is regarded as having potential to solve the issue. CM is a teaching and learning (T&L) method that has been found to be effective in Social Science education. In principle, instructors should be guided appropriately in order to adopt CM in T&L. SE education however lacks of such guidelines. This paper addresses this concern by identifying the factors and their corresponding elements and conditions that contribute to the effective use of CM in T&L SE courses. The factors, elements and conditions were then collated as a framework in the form of a guideline. The factors, elements and conditions were gathered through a series of studies, namely a theoretical study, two surveys and two expert reviews. The theoretical study involved reviewing previous research, while the surveys were performed with five groups of students who experienced CM in learning SE courses. The students were from various education and work backgrounds. Two types of survey instruments were employed, which are questionnaire and group interviews. To form the guideline, the gathered data were analysed qualitatively using contents analysis. The guideline was then validated by two experts through expert reviews. There are four main factors that constitute the guideline of using CM in T&L SE courses: Case, Instructor, Student and Infrastructure. Each factor has its corresponding elements and conditions. The guideline is useful for SE instructors to adopt CM in T&L SE courses at their institutions.

Software systems are critical assets to organisations as they support important business processes and workflow. To maintain the value of these assets, the requirements of software systems must evolve whenever there are changes in business needs. A key problem to organisations is implementing requirements change to the existing software systems. Such initiatives need proper analyses so that their effects could be determined before resources are spent. Impact analysis is therefore an important step in requirements change management. As a project, any change implementation involves risks. It is thus necessary for impact analysis to consider risk factors for implementing requirements change. However to date, the risk factors concerning requirement change are not much explored. This paper aims to identify the risk factors for implementing requirements change. The risk factors were identified through two qualitative approaches, namely a review of related work and a focus group study. The former involved fifty published articles and the latter concerned five domain experts. The collected risk factors from both studies were analysed by using content analysis. The risk factors form a risk model for analysing impacts of implementing requirements change. The model helps practitioners to assess the viability of requirements change requests.

The Case Method (CM) has long been used effectively in Social Science education. Its potential use in Applied Science such as Software Engineering (SE) however has yet to be further explored. SE is an engineering discipline that concerns the principles, methods and tools used throughout the software development lifecycle. In CM, subjects are presented to students by means of real cases whereby students themselves either individually or in group discussions work through the problems and issues presented in the cases. The CM approach is deemed necessary for SE education in order to expose students to real scenarios that challenge them to develop the appropriate skills to deal with practical problems. As a largely theoretical subject, SE students could understand more about the practical application of SE concepts and ideas via such active learning activities. This paper presents a survey conducted on two sets of students who were exposed to CM in learning SE. Besides confirming the acceptance of CM among SE students, the surveys aimed to discover the contributing factors and elements that influence the efficacy of the method. The participants consisted of 64 undergraduates that comprised local full-time and executive students. The survey was performed in two semesters through group interviews. Data from the survey were analysed qualitatively using content analysis. The results showed that there are four factors that are important to teaching SE using CM, namely Environment, Case, Instructor, and Student. Each of these factors has certain criteria and characteristics that suggest how CM can be successfully used in teaching and learning SE. These findings can be used by SE educators to more effectively plan the use of CM as one possible teaching method in SE.

Information security management (ISM) is a continuous, structured and systematic security approach to manage and protect the organisation’s information from being compromised by irresponsible parties. To ensure the information remains secure, many organisations have implemented ISM by establishing and reviewing information security (IS) policy, processes, procedures and organisational structures. Regardless of the efforts, security threats, incidents, vulnerabilities and risks are still plaguing many organisations. Lack of awareness of ISM effectiveness due to low understanding of the success factors is one of the major factors that cause this phenomenon. This study aimed to address this subject by firstly identifying the ISM key factors from existing literature and then by confirming the factors and discovering other related factors from practitioners’ perspective. This study used qualitative method where it adopted semi-structured interviews involving nine practitioners. The data were analysed using content analysis technique. Through the analysis, the study validated several ISM factors and their elements that contribute to the success of ISM. The findings provide practitioners with the high understanding of ISM key factors and could guide practitioners in implementing proper ISM.

Agile methods such as Dynamic Systems Development Method (DSDM), Extreme Programming (XP), SCRUM, Agile Modeling (AM) and Crystal Clear enable small teams to execute assigned task at their best. However, larger organizations aim at incorporating more Agile methods owing to the fact that its application is prevalently tailored for small teams. The scope in which large firms are interested will extend the original Agile methods to include larger teams, coordination, communication among teams and customers as well as oversight. Determining particular software method is always challenging for software companies especially when considering start-up, small to medium or large enterprises. Most of large organizations develop large-scale projects by teams of teams or teams of teams of teams. Therefore, most recognized Agile methods or first-generation methods such as XP and SCRUM need to be modified before they are employed in large organizations; which is not an easy task. Accomplishing said task would necessitate large organizations to pick and select from the scaling Agile methods in accommodating a single vision for large and multiple teams. Deciding the right choice requires wholesome understanding of the method including its strengths and weaknesses as well as when and how it makes sense. Therefore, the main aim of this paper is to review the existing literature of the utilized scaling Agile methods by defining, discussing and comparing them. In-depth reviews on the literature were performed to juxtapose the methods in impartial manner. In addition, the content analysis was used to analyse the resultant data. The result indicated that the DAD, LeSS, LeSS huge, SAFe, Spotify, Nexus and RAGE are the adopted scaling Agile methods at large organizations. They seem to be similar but there are discrepancies among them that take the form of team size, training and certification, methods and practices adopted, technical practices required and organizational type.

User requirements are in high demand due to advancements of technology and business needs. Therefore it is extremely difficult to achieve user requirements at one single time. Agile methods have been introduced to mitigate such issues by implementing user requirements incrementally and iteratively. The top significant aspect in agile development is selecting a group of prominent requirements to be implemented in iteration. This could be derived from continuous requirements prioritisation (RP). To assign which requirements should be selected by practitioners is considered one of the obstacles faced in the process of implementing the inter-iteration period. This study aimed to identify the RP elements and factors that should be considered through the RP process in agile software development. The elements and factors were identified through a review of previous studies and in-depth interviews involving 18 agile practitioners from different software development organizations in different countries (i.e., Malaysia and Jordan), over a period of 2 years. To get the best result, the data is analyzed by using grounded theory techniques (Open, Axial and Selective coding). The elements and factors from the RP process will guide practitioners to an effective RP process that can produce high quality requirements, which are expected to meet the needs of the intended users.

Software engineers are provided with an enormous choice of technology for improving the quality of software. Being intangible, software products tend to be more intricate to build than any other artifacts. The selection of technology can thus become a critical factor for the success of software development. Software engineers are expected to be well-versed in various technologies to enable them to decide the best one for a particular development project. Sensible decisions however require not only understanding but also active minds, which can be achieved through meaningful learning. Being a discussion-based learning approach that encourages students to exploit knowledge and understanding of the subject matter, the Case Method seems to be a practical teaching and learning option. This method entails developing specific cases that promote exploration and critical thinking. To ensure the developed cases are useful, they should be evaluated. This paper presents a practical methodology for developing as well as evaluating industrial cases for teaching software engineering through the Case Method. It also shares some important lessons learned from the process. These lessons act as a guideline for future case developers to compose useful cases and motivate software engineering instructors to use cases in teaching.

Software maintenance, which involves making enhancements, modifications and corrections to existing software systems, consumes more than half of developer time. Specification comprehensibility plays an important role in software maintenance as it permits the understanding of the system properties more easily and quickly. The use of formal notation such as B increases a specification-s precision and consistency. However, the notation is regarded as being difficult to comprehend. Semi-formal notation such as the Unified Modelling Language (UML) is perceived as more accessible but it lacks formality. Perhaps by combining both notations could produce a specification that is not only accurate and consistent but also accessible to users. This paper presents an experiment conducted on a model that integrates the use of both UML and B notations, namely UML-B, versus a B model alone. The objective of the experiment was to evaluate the comprehensibility of a UML-B model compared to a traditional B model. The measurement used in the experiment focused on the efficiency in performing the comprehension tasks. The experiment employed a cross-over design and was conducted on forty-one subjects, including undergraduate and masters students. The results show that the notation used in the UML-B model is more comprehensible than the B model., {"references":["B. W. Boehm, J. R. Brown, and J. R. Kaspar, \"Characteristics of\nSoftware Quality\", TRW Series of Software Technology, 1978.","I. Sommerville, Software Engineering. 6th Edition, Addision-Wesley,\n2001, ISBN: 020139815.","T. M. Pigoski, Practical Software Maintenance: Best Practices for\nManaging your Software Investment. Wiley Computer Publishing, 1996,\nISBN: 0471170011.","D. Craigen, S. Gerhart, and T. Ralston, Applications of Formal Methods,\nIn M. Hinchey, J. Bowen, Eds., Prentice-Hall, Englewoodcliffs, NJ,\n1995, ISBN:0133669491","M. G. Hinchey, \"Confessions of a Formal Methodist\", In P. Lindsay,\nEd., Conferences in Research and Practice in Information Technology,\nVol.15, Australian Computer Society, 2002, pp. 17-20.","K. Finney, and A. Fedorec, \"An Empirical Study of Specification\nReadability Teaching and Learning Formal Methods\", In: N. Dean, M.\nHinchey, Eds., Teaching and Learning Formal Methods, Academic\nPress, New York, 1996, ISBN: 0123490405.","K. Finney, \"Mathematical Notation in Formal Specification: Too\ndifficult for the Masses?\", IEEE Transactions on Software Engineering,\nVol.22, No.2, pp. 158-159, 1996.","D. Carew, C. Exton, and J. Buckley, \"An Empirical Investigation of the\nComprehensibility of Requirements Specifications\", International\nSymposium on Empirical Software Engineering, 2005, pp. 256-265.","J. P. Bowen, and M. G. Hinchey, \"Ten Commandments of Formal\nMethods... Ten Years Later\", IEEE Computer, Vol.39, No.1, 2006, pp.\n40-48.\n[10] A. van Lamsweerde, \"Formal Specification: A Roadmap\", In The Future\nof Software Engineering Track (ICSE-00), ACM Press, Los Angeles\nCA, 2000, pp. 147-159.\n[11] I. Vessey, and R. Weber, \"Structured Tools and Conditional Logic: An\nEmpirical Investigation\", Communications of the ACM, Vol.29, No.1,\n1986, pp. 48-57.\n[12] D. A. Scanlan, \"Structured Flowcharts Outperform Pseudocode: An\nExperiment Comparison\", IEEE Software, Vol.6, No.5, 1989, pp. 28-36.\n[13] N. Cunniff, and R. P. Taylor, \"Graphical vs Textual Representation: An\nEmpirical Study of Novices- Program Comprehension\", In Empirical\nStudies of Programmers: 2nd Workshop, 1987, pp. 114-131.\n[14] M. Bauer, and P. Johnson-Laird, \"How Diagrams Can Improve\nReasoning\", Psychological Science, Vol.4, 1993, pp. 372-378.\n[15] K. Stenning, and J. Oberlander, \"A Cognitive Theory of Graphical and\nLinguistic Reasoning: Logic and Implementation\", Cognitive Science,\nVol.19, 1995, pp. 97-140.\n[16] M. Petre, \"Why looking isn't always seeing: Readership skills and\ngraphical programming\", Communications of the ACM, Vol.38, 1995,\npp.33-44.\n[17] M. Scaife, and Y. Rogers, \"External Cognition: How do Graphical\nRepresentations Work?\", International Journal of Human-Computer\nStudies, Vol.45, 1996, pp. 185-213.\n[18] J. R. Abrial, The B-Method - Assigning Programs to Meanings,\nCambridge University Press, 1996, ISBN: 0521496195.\n[19] Object Management Group (2006). Introduction to OMG-s Unified\nModeling Language (UML). [Online]. Available:\nhttp://www.omg.org/gettingstarted/what_is_uml.htm\n[20] C. Snook, I. Oliver, and M. Butler, \"The UML-B Profile for Formal\nSystems Modelling in UML\", In J. Mermet, , Ed., UML-B Specification\nfor Proven Embedded Systems Design, Springer, 2004, ch. 5, ISBN:\n1402028660.\n[21] C. Snook, and M. Butler, \"UML-B: Formal Modelling and Design\nAided by UML\", ACM Transactions on Software Engineering and\nMethodology, Vol.15, No.1, 2006, pp.92-122.\n[22] ClearSy, AtelierB User Manual V3.6, ClearSy System Engineering,\n2003, Aix-en-Provence, France.\n[23] B-Core (UK) Limited, Oxon, UK (1999). B-Toolkit, On-line manual,\n(Online). Available:\nhttp://www.b-core.com/ONLINEDOC/Contents.html\n[24] J. R. Abrial, and D. Cansell (2003) Click ÔÇÿn- Prove - Interactive Proofs\nwithin Set Theory B. (Online). Available: http://www.b4free.com/ and\nhttp://www.loria.fr/cansell/cnp.html\n[25] T. Pender, UML Bible, Wiley, 2003, ISBN: 0764526049.\n[26] S. Senn, Cross-over Trials in Clinical Research (Statistics in Practice),\nJohn Wiley & Sons, 2002, ISBN: 0471496537.\n[27] J. Foster, \"Program Lifetime: A Vital Statistic for Maintenance\", In\nProceedings of the IEEE Conference on Software Maintenance, 1991,\npp. 98-103.\n[28] A. Davis, S. Overmyer, K. Jordan, J. Caruso, F. Dandashi, A. Dinh, G.\nKincaid, G. Ledeboer, P. Reynolds, A. Sitaram, A. Ta, and M.\nTheofanos, \"Identifying and Measuring Quality in a Software\nRequirements Specification\", In Proceedings of the 1st. International\nSoftware Metrics Symposium, IEEE, 1993, pp. 141-152.\n[29] M. Piattini, M. Genero, G. Poels, and J. Nelson, \"Towards a Framework\nfor Conceptual Modelling Quality\", In M. Genero, M. Piattini, and C.\nCalero, Eds., Metrics for Software Conceptual Models, London :\nImperial College Press, 2005, ISBN: 1860944973.\n[30] S. L. Pfleeger, \"Experimental Design and Analysis in Software\nEngineering: Part 1-5\", ACM SIGSOFT Software Engineering\nNotes, Vol.20, No.1-5, 1995.\n[31] B. A. Kitchenham, and S. L. Pfleeger, \"Principles of Survey Research:\nPart 1-6\", ACM SIGSOFT Software Engineering Notes, Vol.27, No.1-6,\n2002.\n[32] B. Efron, and R. Tibshirani, An Introduction to the Bootstrap, Chapman\nand Hall, New York, London, 1993.\n[33] D. S. Moore, and G. P. McCabe, Introduction to the Practice of\nStatistics, 5th Edition, W. H. Freeman, New York, 2006, ISBN:\n071676282.\n[34] B. Efron, and R. Tibshirani, \"The Bootstrap Method for standard errors,\nconfidence intervals and other measures of statistical accuracy\",\nStatistical Science, Vol.1, No. 1, 1986, pp 1-35.\n[35] Insightful Corporation (2006). Available:\nhttp://www.insightful.com/products/splus/default.asp\n[36] B. Jones, and M. G. Kenward, Design and Analysis of Cross-over Trials,\n2nd Edition, Chapman and Hall, London, 2003, ISBN: 0412606402.\n[37] V. R. Basili, R. W. Selby, and D. H. Huthchens, \"Experimentation in\nSoftware Engineering\", IEEE Transactions on Software Engineering,\nVol.12, No.7, 1986, pp. 733-743.\n[38] V. R. Basili, F. Shull, and F. Lanubile, \"Building Knowledge through\nFamilies of Experiments\", IEEE Transactions on Software Engineering,\nVol.25, No.4, 1999, pp. 456-473.\n[39] R. Jeffery, and L. Scott, \"Has Twenty-five Years of Empirical Software\nEngineering Made a Difference?\", In Proceedings of the 9th Asia-Pacific\nSoftware Engineering Conference, 2002, pp. 539-546.\n[40] W. F. Tichy, \"Should Computer Scientists Experiment More?\", IEEE\nComputer, Vol.31, No.5, 1998, pp. 32-40."]}

The primary objective of software specification is to promote understanding of the system properties between stakeholders. Specification comprehensibility is essential particularly during software validation and maintenance as it permits the understanding of the system properties more easily and quickly prior to the required tasks. Formal notation such as B increases a specification's precision and consistency. However, the notation is regarded as being difficult to comprehend due to its unfamiliar symbols and rules of interpretation. Semi-formal notation such as the Unified Modelling Language (UML) is perceived as more accessible but it cannot be verified systematically to ensure a specification's accuracy. Integrating the UML and B could perhaps produce an accurate and approachable specification. This paper presents an experimental comparison of the comprehensibility of a UML-based graphical formal specification versus a purely textual formal specification. The measurement focused on the efficiency in performing the comprehension tasks. The experiment employed a cross-over design and was conducted on forty-one third-year and masters students. The results show that the integration of semi-formal and formal notations expedites the subjects' comprehension tasks with accuracy even with limited hours of training.

The popularity of mobile devices in the market is impressive, but this influx of different products has made it difficult for users to secure their infrastructures from potential data breaches. As the number of exposures and attacks increase, there has been a corresponding rise in security solutions offered by researchers. This article reviews the literature to prevent the cybercrime affecting portable devices especially smartphones running Android OS. Extant researches are analyzed and opportunities for future research are identified. Four research questions have been developed and out of 493 articles retrieved, 33 articles have been selected to be analyzed. From the analysis, we have found that Data leakage resulting from device loss or theft, unintentional disclosure of data and phishing attacks are most common between attackers. With no doubt, security investigators have stressed the grandness of protecting classified personal data residing in Android portable devices. They have suggested to use the permission-based security model and behavior-based detection method for protecting classified information. In result we found that Android OS can handle and apply the integrated protection model but still there are opportunities for us to improve the security of personal data.