Call number: LD2668 .T4 1985 M378 / Master of Science

No description available.

In modern software development, the gap between software requirements and implementation is not always conciliated. Typically, for Web services-based context-aware systems, reconciling this gap is even harder. The aim of this research is to explore how software reengineering can facilitate the reconciliation between requirements and implementation for the said systems. The underlying research in this thesis comprises the following three components. Firstly, the requirements recovery framework underpins the requirements elicitation approach on the proposed reengineering framework. This approach consists of three stages: 1) Hypothesis generation, where a list of hypothesis source code information is generated; 2) Segmentation, where the hypothesis list is grouped into segments; 3) Concept binding, where the segments turn into a list of concept bindings linking regions of source code. Secondly, the derived viewpoints-based context-aware service requirements model is proposed to fully discover constraints, and the requirements evolution model is developed to maintain and specify the requirements evolution process for supporting context-aware services evolution. Finally, inspired by context-oriented programming concepts and approaches, ContXFS is implemented as a COP-inspired conceptual library in F#, which enables developers to facilitate dynamic context adaption. This library along with context-aware requirements analyses mitigate the development of the said systems to a great extent, which in turn, achieves reconciliation between requirements and implementation.

In today’s society, IT-Companies often have a hard time estimating changed requirements. This leads to that the clients’ confidence is negatively affected and is one of the main reasons why this has to be improved. The goal with this study was to find out what the most common problems regarding this issue are in IT-companies that works with agile software development. By analyzing one IT-company through a SWOT- and pareto-analysis the most common problems have been ascertained. The SWOT analysis have been created through interviews with selected employees to get a better understanding of the problems that the IT-company is facing. Furthermore was the pareto-analysis based on a survey that was sent out to many different employees to prioritize the problems. The reason why the survey was sent to different employees was to get a more objective input. The study showed that there was many different problems that needed attention. The most important problems was that the communication towards the client regarding requirements needed to be improved, better communication internally between different departments needed to be established, a method to quickly adapt and estimate change in requirements needed to be implemented and finally a method regarding witch key employees whom need to attend the planning of the program backlog. These problems have then been studied through interviews with other IT-companies and through a literature study. The conclusions that where drawn was that the client needs to be involved and updated through the whole project. Constant monitoring and communication regarding changed requirements needs to be processed and mediated. High standards needs to be set early towards the client in order to obtain as clear an image of the requirements as possible. Many different parties need to attend to the planning process for the program backlog before the start of the project. The client needs to be aware of that changed requirements will arise and that this will lead to that the first estimation may not necessarily be absolute. As long as the client is held up to date as well as participant through the whole project and problems are detected and mediated early, change in requirements should not be a huge problem. This is after all the purpose of being agile. / I dagens läge har IT-företag svårt med att estimera förändrade krav vilket medför att förtroendet hos beställaren påverkas negativt och är en av hu-vudanledningarna till att det måste förbättras. Målet med studien har varit att försöka ta reda på de vanligaste problemområdena inom agil systemut-veckling bland IT-företag med hjälp av en SWOT- och pareto-analys. SWOT-analys konstruerades av intervjuer med anställda på ett IT-företag och an-vändes för att ta reda på problemområden. Pareto-analysen användes med hjälp av en enkät som skickades ut till anställda på samma IT-företag för att prioritera problemområdena. Enkätens svar bygger på anställda från de flesta avdelningar, vilket resulterar i en objektivare syn på resultatet. Under-sökningen har visat att det finns många områden som kan förbättras. De huvudsakliga områdena som behövde förbättras var tydligare kommunikat-ion gällande kravhantering gentemot kunden, bättre kommunikation mellan avdelningarna internt i företaget, införa en metod för att snabbt estimera samt anpassa sig till förändrade krav behövde implementeras och slutligen skapa struktur gällande vilka personer som bör delta i planeringen inför program backlog. De fyra största problemområdena har sedan undersökts med hjälp av intervjuer med andra företag och genom en litteraturstudie. Slutsatsen som drogs var att kunden behöver vara involverad och uppdate-rad genom hela projektet. Konstant uppföljning och kommunikation gäl-lande förändrade krav behöver bearbetas och förmedlas. Höga krav måste sättas på kunden i början för att få en tydlig och genomarbetad förståelse för kravspecifikationen som möjligt. Många olika parter bör vara med på planeringen inför program backlog innan projektets uppstart. Kunden bör vara medveten om att förändrade krav kommer att uppstå och att detta kommer att leda till att den första estimeringen inte nödvändigtvis kommer vara absolut. Så länge kunden är uppdaterad och delaktig genom hela pro-jektet och problem upptäcks samt förmedlas tidigt bör förändrade krav inte vara ett stort problem. Det är syftet med att vara agil.

Thesis (PhD(Agric) (Horticulture))--Stellenbosch University, 2008. / It is a common practise in the Western Cape to use micro sprinklers as the standard irrigation system for apple trees. Over the past forty years much effort has been put into the optimisation of the tree canopy. Less attention has been given to root proliferation, and the question as to whether root stimulation and proliferation, through intensive water and nutrient management, can contribute towards improved tree efficiency and more efficient water use. This is addressed in this study. ‘Brookfield Gala’ apple trees were studied in the Genadendal area near Greyton, in the Western Cape Province, South Africa. The trees were planted in Dundee soil (well aerated sandy loam soil) during winter 2003. Both horticultural aspects (tree growth, shoot growth, fruit yield and quality, trunk circumference and root growth) and gas exchange were studied from 2004/5 until 2007/8 under three different water application strategies, namely micro sprinkler irrigation, daily drip and pulsing drip irrigation and using two different rootstocks: M793 and M7. Irrigation under micro sprinkler irrigation was applied once to three times weekly, daily drip irrigation once daily/twice daily, and pulsing drip irrigation one to six times daily. Water use for bearing apple trees was calculated using long-term evaporation data (for Villiersdorp and Caledon) and existing crop factors for apples. Annual nutrient requirements were adapted from literature and divided percentage-wise into the requirements for five different phenological stages. Soil sensors were used to keep plant available soil water between 100% and 50%. A computer software program was used to incorporate all the above mentioned information and calculate the exact amounts of water and nutrients, and the application times. In general, drip irrigation systems used ±26% less water than micro sprinkler irrigation system. Significantly higher fruit yields were obtained with trees under daily or pulsing drip irrigation than those under micro irrigation during 2005/6 and 2007/8. During 2006/7 the crop load was low due to unfavourable weather conditions during flowering, resulting in poor fruit set and no differences in yield. There was a significantly higher number of thin plus medium roots (3mm and less in diameter) in the 0─400mm rooting zone and total root mass at 0─800mm rooting zone under drip irrigation systems than under micro sprinkler irrigation. Brookfield Gala’ apple trees grown under daily drip irrigation and pulsing drip irrigation performed better compared to those grown under micro sprinkler irrigation with respect to CO2 assimilation rate (A), stomatal conductance (gs), water use efficiency (WUE) and leaf water potential. None of the three irrigation systems affected the biochemical efficiency of the leaf significantly, except on a few occasions during the pre-harvest period. This implied that the changes in leaf biochemical efficiency were as a result of both stomatal and non-stomatal effects (temperature and vapour pressure deficit). The removal of fruit at harvest had a great influence on leaf photosynthetic capacity under micro irrigation but less so under drip irrigation systems. Higher chlorophyll a and chlorophyll b concentrations were observed under drip irrigation systems than under micro sprinkler irrigation, implying efficient biochemical efficiency under these systems compared to micro sprinkler irrigation during the post-harvest period. Use of daily drip irrigation and pulsing drip irrigation delayed the process of leaf ageing. This study demonstrated the benefits of more intensive water and nutrient application for apple trees. Improved root proliferation, increased fruit yield and photosynthetic efficiency have been found under drip irrigation system than under micro sprinkler irrigation.

The research presented in this thesis focuses on the development of wireless, real time performance monitoring technology within the resistance training domain using a user-centred design methodology. The functionality of current performance monitoring technology and differences in monitoring ability is investigated through comparative force platform, video and accelerometer testing and analysis. Determining the complexity of resistance training exercises and whether performance variable profiles such as acceleration, velocity and power can be used to characterise lifts is also investigated. A structured user-centred design process suitable for the sporting domain is proposed and followed throughout the research to consider the collection, analysis and communication of performance data. Identifying the user requirements and developing both hardware and software to meet the requirements also forms a major part of the research. The results indicate that as the exercise complexity increases, the requirement for sophisticated technology increases. A simple tri-axial accelerometer can be used to monitor simple linear exercises at the recreational level. Gyroscope technology is required to monitor complex exercises in which rotation of the bar occurs. Force platform technology is required at the elite level to monitor the distribution of force and resultant balance throughout a lift (bilateral difference). An integrated system consisting of an Inertial Measurement Unit (both accelerometer and gyroscope technology) and a double plate force platform is required to accurately monitor performance in the resistance training domain at the elite level.

Engineers in diverse fields are able to model their design and experiment with that design to determine how it responds to the environment and how it satisfies the requirements. Design tools for software engineering have become standardized and matured to allow for formal definition of software design. This paper tests the current state of design documentation to determine the quality of design testing available at the early stage of software design. / text

Today, software has become deeply woven into the fabric of our lives. The quality of the software we depend on needs to be ensured at every phase of the Software Development Life Cycle (SDLC). An analyst uses the requirements engineering process to gather and analyze system requirements in the early stages of the SDLC. An undetected problem at the beginning of the project can carry all the way through to the deployed product. The Requirements Traceability Matrix (RTM) serves as a tool to demonstrate how requirements are addressed by the design and implementation elements throughout the entire software development lifecycle. Creating an RTM matrix by hand is an arduous task. Manual generation of an RTM can be an error prone process as well. As the size of the requirements and design document collection grows, it becomes more challenging to ensure proper coverage of the requirements by the design elements, i.e., assure that every requirement is addressed by at least one design element. The techniques used by the existing requirements tracing tools take into account only the content of the documents to establish possible links. We expect that if we take into account the relative order of the text around the common terms within the inspected documents, we may discover candidate links with a higher accuracy. The aim of this research is to demonstrate how we can apply machine learning algorithms to software requirements engineering problems. This work addresses the problem of requirements tracing by viewing it in light of the Ant Colony Optimization (ACO) algorithm and a reinforcement learning algorithm. By treating the documents as the starting (nest) and ending points (sugar piles) of a path and the terms used in the documents as connecting nodes, a possible link can be established and strengthened by attracting more agents (ants) onto a path between the two documents by using pheromone deposits. The results of the work show that ACO and RL can successfully establish links between two sets of documents.

Architecture Design for deploying or improving a tool or application is a vital step which should be neither ignored nor avoided. The architecture will provide the framework and instructions on how the tool needs to be created in order to comply with the stakeholders’ most important requirements. Utilizing data collected from the different stakeholders involved in the use of an existing tool, an effective architecture structure will be created to improve the tool and satisfy the users’ needs to achieve the desired goals in it. Through the use of an effective architecture design, a toolkit will be created to improve an existing Management Tool to provide a desired outcome. We have learned that having an architecture established prior to starting a development project or in the early lifecycle stages will positively influence the project’s outcome, timely deliverables and financial impact associated with it. It is crucial to consider all aspects surrounding a process or software design, such as stakeholder requirements, internal and external customer feedback, and any particular feature that will guarantee a reliable structure and deployment process. / text

<p>The implementation of IFRS/IAS accounting standards in Sweden had the intension to harmonize the accounting practices within the EU and increase transparency into the firms. However since the implementation there have been reports and studies showing the lack of compliance with the disclosure requirements regarding impairment tests of Goodwill. According to IFRS 3 Goodwill should no longer be amortized but should undergo an impairment test at least once a year to evaluate its true value. The impairment test is made by the firms themselves on very subjective assumptions. These assumptions should be disclosed according to IAS 36 paragraph 134 in the annual report to enable transparency. So far the full compliance with this rule has been questionable. This study aims to elucidate possible reasons for why firms leave out the required information in IAS 36 paragraph 134 and how authorized public accountants reason around the reasons given. To fulfill the aim of the study an inductive research method was used. The data was gathered through the use of qualitative interviews with authorized public accountants some of them with special expertise in the field. The empirical findings from the interviews contained a number of reasons for why companies do not disclose the information in IAS 36 paragraph 134. Among the most common were the risk of exposure, decreased flexibility, ignorance and non adequate internal reporting procedures. The study’s analysis use institutional theories to point out additional explanations for how disclosure requirements are handled. One finding is the tendency for firms to mimic each other, a behavior called isomorphism. The conclusion of the study is a discovery of an underlying unwillingness to write-down goodwill and thereby an unwillingness to give full disclosure in connection to the impairment test. Firms feel that the information is related to their competitive edge and thus exposes them too much. The authors also raise reasonable doubt to whether the IFRS/IAS standards have fulfilled their intension with increased transparency in the case of goodwill accounting.</p>