Modern organizations within IT-developing needs to be prepared to face challengesthat are not necessarily connected to the mere technological aspects of softwares.These challenges might lie within e. g. communication between stakeholders, userinvolvement, organizational regulations, the need for standards and maintainability ofthe products. This study is investigating the software development at one of thevarious IT-departments at Swedish bank Nordea, in order to point out the mostinteresting areas of improvement. Many different tools, standards, organizationalprocesses and methodologies are available to the developers, whereof some of themmight be inhibitory rather than enhancing the effectiveness. Nordea is also having anoffshoring-oriented strategy, having development resources located in India. Thediscussion is concerned with modern methodologies such as Scrum and other agiledevelopment concepts, and their use in a geographically dispersed context and withina non-agile organization.

Component-based software is finally taking off in a big way and component-based application generators have been championed because they can be used to shorten a system¡¦s development cycle and therefore lower its development costs. Component-based application generators are standardardized building blocks that can be used to assemble, rather that develop, information systems (IS). This paper presents a component-based application generator in the restaurant food ordering setting and a requirement modeling methodology for IS construction based on the generator presented. A prototype was assembled using the generator and methodology presented to illustrate the concepts and application. With this approach, system developers or end users can more easily build, modify and maintain their applications.

How to create, classify, store and share the external and internal knowledge effectively will be the main competitive advantages of a company in the new era of knowledge economy. It is extremely important to the software industry, an industry that is highly intensive in both knowledge and human power. Requirement Analysis is the first phase in software development process and is an important development base for the other phases. Therefore, it becomes the key success factor for a software product. This paper proposes a requirement construction procedure. First, it expresses the users' important requirements through requirement capture and requirement transformation process, with related tables and interface blueprints. Secondly, it transforms the interface blueprints into abstract templates and meta-templates based on the abstraction of the interface blueprints through the requirement structure analysis procedure. Based on these templates and meta-templates, it can create a knowledge management framework using the special features of objects and encapsulation. Then, the requirement-knowledge is able to be stored, integrated and reused effectively. Lastly, this paper uses the ERP of steel industry in a software company as an example. It applies the knowledge modeling process of requirement analysis by a case demonstrated in practice. The result of this research provides the tables and templates for a company to create a requirement analysis knowledge management system. This system may help analysts to analyze requirements, and hopefully, reduce the time in software development and enhance the quality of software products.

In recent years, it has to spend lots of time and effort to get the certification of CMMI. Therefore, everyone is looking to tools or methods for speeding up the CMMI certification. CMMI level five, causal analysis and resolution, is an important issues for all industries. In the process of software development, we have to identify the causes for defects at first. Then, it uses a systematic approach to sum up the necessary causes for software defects in order to help managers make better decisions and develop action items. With no doubt, it is a very important issue in the process of software development. This study aims to explore the subject of using the methods of causal analysis and resolution to solve the problems of software defects. Through the implementation of CAR, we can determine the root causes of defects and avoid importing defects to products. This study focus on the implementations of CAR and it proposes the methods, procedures and management forms. Moreover, this study will introduce the Mill¡¦s methods for causal reasoning used in the structure of CAR. Therefore it can help managers with a better way to sum up the causes for defects. The study uses case study method. Firstly, it connects the company for data collection of cause and effect diagram and combines the Mill¡¦s methods to inductive causal and analysis. Then it arranges interviews with the company managers to identify the necessary causes of defects. Finally, it helps the company develop action items in order to achieve the causal analysis and resolutions in the process of software development.

<p>På senare tid har agila systemutvecklingsmetoder trätt fram på marknaden, metoder som värderar flexibilitet, kundmedverkan och fokus på utvecklingsteamet och fungerande mjukvara snarare än fokus på utvecklingsverktygen och dokumentation. Vi vet dock inte vilken typ av systemutvecklingsmetod som verkligen är bättre än den andra. Den här uppsatsen består av en historisk översikt av systemutvecklingsmetoder och en undersökning kring graden av belåtenhet med olika typer av systemutvecklingsmetoder och attityden till de agila värderingarna. Genom en kvantitativ studie har svenska organisationer som utövar systemutveckling tillfrågats angående detta. Resultaten är inte helt säkra, men anspelar på att utövare av mer traditionella systemutvecklingsmetoder var något mer nöjda med sin metod än utövare av agila metoder var, men de agila utövarna var istället mer nöjda med hur deras metod hjälper dem med att tillgodose kundernas behov och önskemål än de traditionella utövarna var. Båda typerna av systemutvecklare var mer positiva till de agila värderingarna än deras motsatser, men de agila metodutövarna var positiva till en större utsträckning.</p> / <p>Recent times have seen the emergence of agile software development methods, valuing flexibility, customer collaboration, and focus on the development team and working software rather than focus on tools and documentation. What is unknown is which type of software development method is really better than the other. This thesis consists of a historical overview of software development methods and an investigation of the level of satisfaction with different types of software development methods and the attitude towards the agile values. Through a quantitative study, Swedish software development organizations have been heard regarding these issues. The results, although not fully statistically supported, indicate that practisers of more traditional software development methods were slightly more satisfied with their methods than practisers of agile methods were, but the agile method practisers were instead more satisfied with how their method helped them in satisfying their customers’ wants and needs than the traditional method practisers were. Both types of software developers were more positive towards the agile values than their counterparts, but the practisers of agile software development methods were so to a greater extent.</p>

Software forms around a requirement. Defining this requirement is often regarded as the hardest part of software engineering. The requirement however has an additional complexity as, once defined, it will change with time. This change of requirement can come either from the user, or from the rapid advances in 'computer' technology. How then can software succeed to continue to remain 'current' both in terms of requirements and technology in this forever changing environment? This thesis examines the issues surrounding 'change' as applied to software and software engineering. Changing requirements are often deemed a 'curse' placed upon software engineers. It has been suggested, however, that the problems associated with change exist only in the attitude of software engineers. This is perhaps understandable considering the training methods and tools available to supposedly 'help' them. The evidence shows that quality of management and experience of personnel involved in development contribute more significantly to the success of a development project than any technical aspect. This unfortunately means that the process is highly susceptible to staff turnover which, if uncontrolled, can lead to pending disaster for the users. This suggests a 'better' system would be developed if 'experience' was maintained at a process level, rather that at an individual level. Conventional methods of software engineering are based upon a defined set of requirements which are determined at the beginning of the software process. This thesis presents an alternative paradigm which requires only a minimal set of requirements at the outset and actively encourages changes and additional requirements, even with a mature software product. The basis of this alternative approach is the fonn of the 'requirements specification' and the capturing and re-use of the 'experience' maintained by the software process itself.

The tracking of artifacts in museums can be a cumbersome and error-prone process. A system that performs this tracking manually would help prevent mistakes and could be utilized to help attract and retain museum visitors. This thesis outlines the design and implementation of a three-part system for accomplishing this goal. By combining a powerful RFID infrastructure with a server and an intuitive mobile-device application, the project in this thesis aims to provide an automated way to keep track of artifacts, as well as to provide an application that makes the traversal of the museum intuitive and enjoyable for visitors. The application is built on Apple’s iOS platform in order to reach the multitude of users already in possession of iPhones, iPads, and iPod Touches. An initial evaluation shows the system behaves as expected and that it could be a useful tool to museums. / text

Not available / text

The proliferation of collaborative computer applications in the past decade has resulted in a corresponding increase in the need for multi-user interfaces. The current research seeks to contribute to the design of a user-centered multi-user interface for a group ranking task. User requirements were identified by observing groups perform the ranking task in a non-computer environment. A design was proposed based on these identified requirements. The user-centered design was compared to preliminary designs based on the intuitions of programmers. The conclusions indicate that an analysis of observations in the non-computer environment does yield insight beyond the initial intuition of programmers. A prototype based on the user-centered design was implemented. Informal user evaluation was performed by observing users working with the prototype and obtaining verbal feedback both on the ease of use of the system and on possible improvements. The informal user evaluation provides evidence for the usefulness of user-centered design. The evaluation also suggests that not all features identified were found useful and not all features necessary were identified.

No abstract available / 28 cm.