Practical Experience in Customization for a Software Development Process for Small Companies Based on RUP Process and MSF

2011 ◽  
pp. 71-93 ◽  
Author(s):  
Valerio Fernandes del Maschi ◽  
Luciano S. Souza ◽  
Mauro de Mesquita Spínola ◽  
Wilson Vendramel ◽  
Ivanir Costa ◽  
...  
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Development Process ◽  
Practical Experience ◽  
Software Development Process ◽  
Small Companies ◽  
Engineering Process ◽  
Software Projects ◽  
Software Engineering Process ◽  
Unified Process

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).

Domain Ontologies in Software Engineering: Use of Protégé with the EON Architecture

1998 ◽  
Vol 37 (04/05) ◽  
pp. 540-550 ◽  
Author(s):  
M. A. Musen
Keyword(s):  
Problem Solving ◽  
Software Engineering ◽  
Development Process ◽  
Application Area ◽  
Software Development Process ◽  
Engineering Process ◽  
Software Applications ◽  
Software Engineering Process ◽  
Domain Ontologies ◽  
Domain Independent

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.

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
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Project ◽  
Software Development Process ◽  
Engineering Process ◽  
Question Mark ◽  
Development Organisation ◽  
Software Engineering Process ◽  
Agile Software ◽  
New Software Development

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.

scholarly journals Rational Unified Process Part-1

2002 ◽  
Vol 1 (1) ◽  
pp. 81-94
Author(s):  
Manoj Tharian
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Unified Modeling Language ◽  
Modeling Language ◽  
Engineering Process ◽  
Unified Modeling ◽  
Industry Standard ◽  
Development Teams ◽  
Software Engineering Process ◽  
Unified Process

This paper presents an overview of the Rational Unified Process. The Rational unified Process is a software engineering process, delivered through a web-enabled, searchable knowledge base. The process enhances team productivity and delivers software best practices via guidelines, templates and tool mentors for all critical software lifecycle activities. The knowledge base allows development teams to gain the full benefits of the industry-standard Unified Modeling Language(UML). The rational Unified Process is a software Engineering Process. It provides a disciplined approach to assigning tasks and responsibilities within development organization. Its goal is to ensure the production of high-quality software that meets the needs of its end-users, within a predictable schedule and budget.[11,13] The rational Unified Process is a process product , developed and maintained by Rational Software. The development team for the Rational Unified Process are working closely with customers, partners, Rational's that the process is continuously updated and improved upon to reflect recent experiences and evolving and proven best practices. The Rational Unified Process is a guide for how to effectively use the Unified modeling Language(UML). The UML is a industry-standard language that allows us to clearly communicate requirements, architectures and designs. The UML is a industry-standard language that allows us to clearly communicate requirements architectures and designs. the UML originally created by Rational Software, and is now maintained by the standards organization Object Management Group(OMG).[4] the Rational Unified Process captures many of the best practices in modern software development in a form that is suitable for a wide range of projects and organizations. Deploying these best practices 3/4 using the Rational Unified Process as your guide 3/4 offers development teams a number of key advantages. In next section, we describe the six fundamental best practices of the Rational Unified Process. The Rational Unified Process describes how to effectively deploy commercially proven approaches to software development for software development teams. These are called "best practices" not so much because you can precisely quantify their value, but rather, because they are observed to be commonly used in industry by successful organizations.

Boosting the Competitiveness of Organizations With the Use of Software Engineering

2021 ◽  
pp. 198-216
Author(s):  
Mirna Muñoz
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Development Process ◽  
Research Work ◽  
Software Development Process ◽  
The Core ◽  
Development Organizations ◽  
Technological Base ◽  
The One

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.

scholarly journals Incorporating Accessibility Elements to the Software Engineering Process

2018 ◽  
Vol 2018 ◽  
pp. 1-17 ◽  
Author(s):  
Wesley Tessaro Andrade ◽  
Rodrigo Gonçalves de Branco ◽  
Maria Istela Cagnin ◽  
Débora Maria Barroso Paiva
Keyword(s):  
Software Engineering ◽  
Social Welfare ◽  
Development Process ◽  
Access To Information ◽  
Engineering Process ◽  
Digital Inclusion ◽  
Software Products ◽  
Computational Support ◽  
Software Engineering Process

The expansion of web is a phenomenon that brings several challenges in different segments of the society. Accessibility is one of these challenges and it is related to the digital inclusion and social welfare of the population. Thus, making accessible software available can contribute to solution of problems that currently exist in relation to access to information and services by all citizens. The purpose of this article is to present an approach that integrates accessibility to the Software Engineering process. We also present the Acero tool, which provides computational support to the proposed approach. Results were evaluated and we concluded that the use of the proposal reached the objectives, supporting different stages of the development process and contributing to obtain accessible software products.

scholarly journals Software development: do good manners matter?

2015 ◽  
Author(s):  
Giuseppe Destefanis ◽  
Marco Ortu ◽  
Steve Counsell ◽  
Michele Marchesi ◽  
Roberto Tonelli
Keyword(s):  
Software Development ◽  
Open Source Software ◽  
Development Process ◽  
Communication Process ◽  
Software Project ◽  
Software Development Process ◽  
Key Factors ◽  
Software Projects ◽  
Complex Process ◽  
Time Required

A successful software project is the result of a complex process involving, above all, people. Developers are the key factors for the success of a software development process, not merely as executors of tasks, but as protagonists and core of the whole development process. This paper investigates social aspects among developers working on software projects developed with the support of Agile tools. We studied 22 open source software projects developed using the Agile board of the JIRA repository. All comments committed by developers involved in the projects were analyzed and we explored whether the politeness of comments affected the number of developers involved and the time required to fix any given issue. Our results showed that the level of politeness in the communication process among developers does have an effect on the time required to fix issues and, in the majority of the analysed projects, it had a positive correlation with attractiveness of the project to both active and potential developers. The more polite developers were, the less time it took to fix an issue. In the majority of the analysed cases, the more developers wanted to be part of a project, the more they were willing to continue working on the project over time.

scholarly journals Software development: do good manners matter?

2015 ◽  
Author(s):  
Giuseppe Destefanis ◽  
Marco Ortu ◽  
Steve Counsell ◽  
Michele Marchesi ◽  
Roberto Tonelli
Keyword(s):  
Software Development ◽  
Open Source Software ◽  
Development Process ◽  
Communication Process ◽  
Software Project ◽  
Software Development Process ◽  
Key Factors ◽  
Software Projects ◽  
Complex Process ◽  
Time Required

A successful software project is the result of a complex process involving, above all, people. Developers are the key factors for the success of a software development process, not merely as executors of tasks, but as protagonists and core of the whole development process. This paper investigates social aspects among developers working on software projects developed with the support of Agile tools. We studied 22 open source software projects developed using the Agile board of the JIRA repository. All comments committed by developers involved in the projects were analyzed and we explored whether the politeness of comments affected the number of developers involved and the time required to fix any given issue. Our results showed that the level of politeness in the communication process among developers does have an effect on the time required to fix issues and, in the majority of the analysed projects, it had a positive correlation with attractiveness of the project to both active and potential developers. The more polite developers were, the less time it took to fix an issue. In the majority of the analysed cases, the more developers wanted to be part of a project, the more they were willing to continue working on the project over time.

A Proposed Pragmatic Software Development Process Model

2018 ◽  
pp. 448-462
Author(s):  
Sanjay Misra ◽  
M. Omorodion ◽  
Amit Mishra ◽  
Luis Fernandez
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Rapid Growth ◽  
Process Model ◽  
Development Process ◽  
Technological Development ◽  
Software Development Process ◽  
The World ◽  
Society Today

The rapid growth in technology and the dynamism in our society today poses a lot of problems for Software Engineering practitioners. The result is a series of software development process methods that can be used to combat or meet up with the problems. What we can do is evolve, grow, and adapt to the changes that come along with development. This is the dynamism inherent in man—to adapt to change and improve ourselves and our existing systems—since the world is a far cry from what it was a few decades ago. On this basis lay the need to develop the model proposed in this chapter to meet the variations that exist as a result of technological development.

Sign in / Sign up

Export Citation Format

Share Document