scholarly journals Several Ideas on Integration of SCRUM Practices within Microsoft Solutions Framework

2017 ◽  
Vol 21 (1) ◽  
pp. 71-79
Author(s):  
Jai Vigneshwar Alavandhar ◽  
Oksana Ņikiforova

Abstract In order to develop and deliver a software project successfully, any software development organisation has to follow a well-known and recognised software engineering process for successful delivery and maintenance of the software. However, when the organisation is willing to follow a new software development process, the success rate of adopting a new software engineering process is a question mark. In the paper, we aim at studying and comparing two software engineering processes, which are based on different paradigms or models, and proposing a hybrid methodology, which integrates advantages of both compared methods. They are Microsoft Solutions Framework as a representative for an iterative methodology and SCRUM for agile software development. The comparative analysis will help a software development company to make the transition easier from Microsoft Solutions Framework to SCRUM or vice versa.

Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  

The quality in software projects is related the deliveries that are adjusted to the use, and that they take care of to the objectives. In this way, Brazilian organizations of software development, especially the small and medium ones, need to demonstrate to future customers whom an initial understand of the business problem has enough. This chapter has as objective to demonstrate methodology, strategy, main phases and procedures adopted beyond the gotten ones of a small organization of development of software in the implantation of a Customized Software Engineering Process and of a Tool of Support to the Process in the period of 2004 to 2006 on the basis of rational unified process (RUP) and in the Microsoft solutions framework (MSF).


1998 ◽  
Vol 37 (04/05) ◽  
pp. 540-550 ◽  
Author(s):  
M. A. Musen

AbstractDomain ontologies are formal descriptions of the classes of concepts and the relationships among those concepts that describe an application area. The Protege software-engineering methodology provides a clear division between domain ontologies and domain-independent problemsolvers that, when mapped to domain ontologies, can solve application tasks. The Protege approach allows domain ontologies to inform the total software-engineering process, and for ontologies to be shared among a variety of problem-solving components. We illustrate the approach by describing the development of EON, a set of middleware components that automate various aspects of protocol-directed therapy. Our work illustrates the organizing effect that domain ontologies can have on the software-development process. Ontologies, like all formal representations, have limitations in their ability to capture the semantics of application areas. Nevertheless, the capability of ontologies to encode clinical distinctions not usually captured by controlled medical terminologies provides significant advantages for developers and maintainers of clinical software applications.


Author(s):  
Sofiane Sahraoui

Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This chapter expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the chapter demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.


Author(s):  
Priyanka Kataria ◽  
Shweta Shrivas ◽  
Ishita Shukla ◽  
A. Hemlata

During the past years, new software development approaches were introduced to suit within the new trend of the software development corporations. Most Software Corporation’s today aim to provide valuable software in short period of time with marginal prices and among unstable, ever-changing environments. Agile methodology focuses on the challenges of unpredictability of the real world by relying on individuals and their creative thinking instead of method. In this paper we tend to explore about the current agile methods, strengths and weaknesses of agile strategies and numerous problems with their relevancy. We have conjointly enclosed comparison between traditional software development process and agile software development process. This paper also includes brief discussion about the benefits and problems associated with these methodologies by performing case study of two corporations.


2012 ◽  
Vol 4 (3) ◽  
pp. 52-65
Author(s):  
Sofiane Sahraoui ◽  
Noor Al-Nahas ◽  
Rania Suleiman

Open source software (OSS) development has been a trend parallel to that of agile software development, which is the highly iterative development model following conventional software engineering principles. Striking similarities exist between the two development processes as they seem to follow the same generic phases of software development. Both modes of development have less emphasis on planning and design and a more prominent role for implementation during the software engineering process. This article expounds on this connection by adopting an agile perspective on OSS development to emphasize the similarities and dissimilarities between the two models. An attempt is first made to show how OSS development fits into the generic agile development framework. Then, the article demonstrates how the development process of Mozilla and Apache as two of the most famous OSS projects can be recast within this framework. The similarity discussed and illustrated between agile and OSS development modes is rather limited to the mechanics of the development processes and do not include the philosophies and motivations behind development.


Sign in / Sign up

Export Citation Format

Share Document