No description available.

No description available.

Workflow implementations require a deep understanding of business and human cooperation. Several approaches have been proposed to address this need for understanding, but largely in a descriptive way. Attempts to use them in software development have had mixed results. The work reported here proposes that these approaches can be used in a generative way, as part of the requirement engineering process, by (a) extending requirements engineering modelling techniques with underlying cooperation properties, (b) integrating these techniques through the use of a derivation modelling approach, and (c) providing pragmatic heuristics and guidelines that support the real-world requirements engineering practitioner to ensure a high probability of success for the business workflow system to be developed. This thesis develops and evaluates a derivation modelling approach that is based on scenario modelling. It supports clear and structured views of cooperation properties, and allows the derivation of articulation protocols from business workflow models in a scenario-driven manner. This enables requirements engineering to define how the expectations of the cooperative situation are to be fulfilled by the system to be built - a statement of requirements for business workflow systems that reflects the richness of these systems, but also acts as a feasible starting point for development. The work is evaluated through a real-world case study of business workflow management. The main contribution of this work is a demonstration that the above problems in modelling requirements for business workflow systems can be addressed by scenario-based derivation modelling approach. The method transforms models through a series of properties involving cooperation, which can be addressed by using what are effectively extensions of current requirements engineering methods.

A research report submitted to the Faculty of Commerce, University of the Witwatersrand, Johannesburg, in partial fulfillment of the requirements for the degree of Master of Commerce. / User participation is widely regarded as being important in the development of systems. Research has largely focused on describing participation in the context of traditional systems environments, such as transaction processing, management information and decision support. Very little research has concentrated on the implementation of software packages. The implementation of packaged software, as an alternative to traditional software development, has 'become increasingly popular and further research into this specific area could provide valuable insights into the user participation construct. [Abbreviated Abstract. Open document to view full version] / AC2017

Fleissner, Sebastian. / Thesis (Ph.D.)--Chinese University of Hong Kong, 2009. / Includes bibliographical references (leaves 181-189). / Electronic reproduction. Hong Kong : Chinese University of Hong Kong, [2012] System requirements: Adobe Acrobat Reader. Available via World Wide Web. / Abstract also in Chinese.

<p>This research paper discusses the software development through agile approaches. In which we see that most of the time, agile approaches cannot use for all type of projects. But this paper is exploring the new ideas that how we can use the agile methodologies with the help of traditional approach and PSP/TSP/Software CMMI. So, the over all paper is giving the whole idea, that we can develop any type of software projects through the new agile methodology guidelines which we are describing here. As well as for solving this paper we adopted different ways in which we focused on literature study & also published research paper on agile methodology. In addition, we did this work on the base of hybrid ideology where we combined the best ways of different approaches and achieved our goals.. Where we proved that by the combination of these approaches, we can manage our projects as well as team personals in the organization successfully. And this concept for team management comes from PSP/TSP and Software CMMI. The benefit for management of this is also to get our projects with agility and personnel's training for project management.</p>

This research paper discusses the software development through agile approaches. In which we see that most of the time, agile approaches cannot use for all type of projects. But this paper is exploring the new ideas that how we can use the agile methodologies with the help of traditional approach and PSP/TSP/Software CMMI. So, the over all paper is giving the whole idea, that we can develop any type of software projects through the new agile methodology guidelines which we are describing here. As well as for solving this paper we adopted different ways in which we focused on literature study & also published research paper on agile methodology. In addition, we did this work on the base of hybrid ideology where we combined the best ways of different approaches and achieved our goals.. Where we proved that by the combination of these approaches, we can manage our projects as well as team personals in the organization successfully. And this concept for team management comes from PSP/TSP and Software CMMI. The benefit for management of this is also to get our projects with agility and personnel's training for project management.

Not available / text

The creation of a requirements model (explicitly representing functional, data, and timing requirements) typically involves accommodating viewpoints from multiple system stakeholders (e.g. multiple end-users and system maintainers). Viewpoint-oriented requirements analysis methods have been proposed by other researchers to ensure the capture of requirements imposed by all user perspectives. However, domain-modeling methodologies and CASE tools poorly address how to construct a single model given input from a variety of sources and how to maintain traceability through the synthesis process. Rather than making incremental changes to a single requirements model in response to new information, this work suggests the creation of independent models to capture the input from each viewpoint. This research provides a semi-automated method of resolving the differences between viewpoints and producing a single, traceable requirements model that embodies the merged viewpoints. Computer assistance includes the detection of consistency and completeness conflicts, the enactment of conflict resolutions, the maintenance of traceability information, and the gathering of statistics regarding the content and resolution of viewpoints. This data can provide previously unavailable insight into the progress of the requirements acquisition process and characteristics of the domain. A case study is presented to demonstrate the method and the usefulness of gathered data to software engineers and software development managers. / text

No description available.