SOA-Driven Business-Software Alignment

The alignment of business processes and their supporting application software is a major concern during the initial software design phases. This paper proposes a design approach addressing this problem of business-software alignment. The approach takes an initial business model as a basis in deriving refined models that target a service-oriented software implementation. The approach explicitly identifies a software modeling level at which software modules are represented as services in a technology-platformindependent way. This model-driven service-oriented approach has the following properties: (i) there is a forced alignment (consistency) between business processes and supporting applications; (ii) changes in the business environment can be traced to the application and vice versa, via model relationships; (iii) the software modules modeled as services have a high degree of autonomy; (iv) migration to new technology platforms can be supported through the platform independent software model

Small business preference for software package

Until late 2016, the majority of small business uses QuickBooks and Excel to do their accounting work. However, the functions of these accounting tools are insufficient, and also the demands of companies are increasing. It has become inefficient and antiquated to use the software. A small business looked for new accounting software, but found that choosing an accounting software system is not straightforward, as every software package consists of different functions for users. The aim of this research was to analyse small business’ perceptions and preferences for accounting software systems in New Zealand. This is followed by an analysis of why users might want to replace their previous accounting software systems. In addition, the requirements for selecting accounting software were analysed. The main method used was qualitative research. Three people were interviewed regarding the reason for replacing their previous accounting software system. The first interviewee had not changed their accounting software system previously, but their reason for replacing their current accounting software system was that their previous accounting software system lacked the functionality he wanted. The second interviewee said e she disliked that the system frequently crashed and that it lacked the features she wanted. The reason why the last interviewee changed her previous accounting software system was that MYOB system could not improve her work efficiency

Business Rule Mining from Spreadsheets

Business rules represent the knowledge that guides the operations of a business organization. They are implemented in software applications used by organizations, and the activity of extracting them from software is known as business rule mining. It has various purposes amongst which migration and generating documentation are the most common. However, apart from conventional software, organizations also use spreadsheets for a large part of their operations and decision-making activities. Therefore we believe that spreadsheets are also rich in business rules. We thus propose to develop an automated system for extracting business rules from spreadsheets in a human comprehensible natural language format. This position paper describes our motivation, the problem description, related work, and challenges we foresee.Comment: In Proceedings of the 2nd Workshop on Software Engineering Methods in Spreadsheets (http://spreadsheetlab.org/sems15/

Modelling the Strategic Alignment of Software Requirements using Goal Graphs

This paper builds on existing Goal Oriented Requirements Engineering (GORE) research by presenting a methodology with a supporting tool for analysing and demonstrating the alignment between software requirements and business objectives. Current GORE methodologies can be used to relate business goals to software goals through goal abstraction in goal graphs. However, we argue that unless the extent of goal-goal contribution is quantified with verifiable metrics and confidence levels, goal graphs are not sufficient for demonstrating the strategic alignment of software requirements. We introduce our methodology using an example software project from Rolls-Royce. We conclude that our methodology can improve requirements by making the relationships to business problems explicit, thereby disambiguating a requirement's underlying purpose and value.Comment: v2 minor updates: 1) bitmap images replaced with vector, 2) reworded related work ref[6] for clarit

Methodological approaches based on business rules

Business rules and business processes are essential artifacts in defining the requirements of a software system. Business processes capture business behavior, while rules connect processes and thus control processes and business behavior. Traditionally, rules are scattered inside application code. This approach makes it very difficult to change rules and shorten the life cycle of the software system. Because rules change more quickly than the application itself, it is desirable to externalize the rules and move them outside the application. This paper analyzes and evaluates three well-known business rules approaches. It also outlines some critical factors that have to be taken into account in the decision to introduce business rules facilities in a software system. Based on the concept of explicit manipulation of business rules in a software system, the need for a general approach based on business rules is discussed.methodology, business rules.

Enterprise application reuse: Semantic discovery of business grid services

Web services have emerged as a prominent paradigm for the development of distributed software systems as they provide the potential for software to be modularized in a way that functionality can be described, discovered and deployed in a platform independent manner over a network (e.g., intranets, extranets and the Internet). This paper examines an extension of this paradigm to encompass ‘Grid Services’, which enables software capabilities to be recast with an operational focus and support a heterogeneous mix of business software and data, termed a Business Grid - "the grid of semantic services". The current industrial representation of services is predominantly syntactic however, lacking the fundamental semantic underpinnings required to fulfill the goals of any semantically-oriented Grid. Consequently, the use of semantic technology in support of business software heterogeneity is investigated as a likely tool to support a diverse and distributed software inventory and user. Service discovery architecture is therefore developed that is (a) distributed in form, (2) supports distributed service knowledge and (3) automatically extends service knowledge (as greater descriptive precision is inferred from the operating application system). This discovery engine is used to execute several real-word scenarios in order to develop and test a framework for engineering such grid service knowledge. The examples presented comprise software components taken from a group of Investment Banking systems. Resulting from the research is a framework for engineering servic

EFFICIENT TEAM BUILDING FOR ON-TIME PROJECTS

When we think to software development projects we consider that a strong set of requirements is defined and team members always follow initial planning. Well, this was a specific orientation in traditional software developments methods and methodologies. In a current competitive business environment this attitude leads to fail in software development projects. This paper aims to highlight the importance of agile approach focused on meetings and team building and to give examples based on our experience in software development in industrial field for financial and energy sectors. This paper is the result of collaboration between university (business informatics, psychology, and finance) and business environment (internal software development projects).agile software development, team/group building, CMMI, project management