2012•International journal of advanced research in computer science and electronics engineeringRequires access

Tailoring RUP to Shataayu Project : A Case Study

Fatema Rangwala, Kirti Mathur, Taher Ali Rangwala, Ashwini Mathur

Open publisher page 1 citations

Abstract

For developing a project the framework which is widely used is Rational Unified Process (RUP). RUP is used widely due to its core principles i.e. architecture centric, uses use case model for user documentation and is an iterative and incremental process model. RUP defines many artifacts and roles which are very useful during software development. But RUP does not fit for all software’s to be developed as there are many different type of software with different requirements. Therefore RUP as defined cannot be used in some projects. Therefore it has to be tailored. In this case study we are representing a project in which how RUP is tailored is shown. Research method used in this case study is action research and for data collection postmortem analysis is done. In which all the team members evaluate the project being developed and project’s flip side is also discussed.

About this research paper

What this paper is about

For developing a project the framework which is widely used is Rational Unified Process (RUP). RUP is used widely due to its core principles i.e. architecture centric, uses use case model for user documentation and is an iterative and incremental process model. RUP defines many artifacts and roles which are very useful during software development. But RUP does not fit for all software’s to be developed as there are many different type of software with different requirements. Therefore RUP as defined cannot be used in some projects. Therefore it has to be tailored. In this case study we are representing a project in which how RUP is tailored is shown. Research method used in this case study is action research and for data collection postmortem analysis is done. In which all the team members evaluate the project being developed and project’s flip side is also discussed.

Why it matters

OpenAlex reports 1 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

For developing a project the framework which is widely used is Rational Unified Process (RUP). RUP is used widely due to its core principles i.e. architecture centric, uses use case model for user documentation and is an iterative and incremental process model. RUP defines many artifacts and roles which are very useful during software development. But RUP does not fit for all software’s to be developed as there are many different type of software with different requirements. Therefore RUP as defined cannot be used in some projects. Therefore it has to be tailored. In this case study we are representing a project in which how RUP is tailored is shown. Research method used in this case study is action research and for data collection postmortem analysis is done. In which all the team members evaluate the project being developed and project’s flip side is also discussed.

Key concepts: Rational Unified Process, Computer science, Software engineering, Project team, Documentation, Software development process, Software, Software development

Related papers

Back to paper searchBrowse research topicsOriginal source
Tailoring RUP to Shataayu Project : A Case Study — Research Paper | ScholarLens