Sunday, March 14, 2010

RUP & Software Development

How do we use RUP to develop industry based software applications?

18 comments:

  1. we know RUP is software development process,which was introduced by IBM. this process is depend on stepwise building blocks. Mainly in this process we consider about who do the job,what is the task and how it is going to be done

    ReplyDelete
  2. But Dinidu, If you just look at other process models, most of them contains stepwise building blocks...Others main objective is also provide a end product.. Can you explain your idea further... It little bit amboguous for me to get clear understanding...
    Thanks.

    ReplyDelete
  3. My idea is that
    RUP is based on a set of building blocks,it is describing
    * what are to be produced
    * the necessary skills required
    * how specific development goals are achieved and it is describing as the step by step explanation

    ReplyDelete
  4. RUP means "Retional Unified process"I think it's a software framework,that helps to develop the constraction processes.It is like building box that use to building a process.As I know this process is use to produce Dramas & films.

    M.R.M.E.M.Rathnayaka As/07/08/094

    ReplyDelete
  5. This comment has been removed by the author.

    ReplyDelete
  6. RUP

    Stands for "Rational Unified Process." RUP is a software development process from Rational, a division of IBM. It divides the development process into four distinct phases that each involve business modeling, analysis and design, implementation, testing, and deployment. The four phases are:


    1. Inception - The idea for the project is stated. The development team determines if the project is worth pursuing and what resources will be needed.



    2. Elaboration - The project's architecture and required resources are further evaluated. Developers consider possible applications of the software and costs associated with the development.



    3. Construction - The project is developed and completed. The software is designed, written, and tested.



    4. Transition - The software is released to the public. Final adjustments or updates are made based on feedback from end users.



    The RUP development methodology provides a structured way for companies to envision create software programs. Since it provides a specific plan for each step of the development process, it helps prevent resources from being wasted and reduces unexpected development costs.

    ReplyDelete
  7. Stands for "Rational Unified Process." RUP is a software development process from Rational, a division of IBM. It divides the development process into four distinct phases that each involve business modeling, analysis and design, implementation, testing, and deployment. The four phases are:


    1. Inception - The idea for the project is stated. The development team determines if the project is worth pursuing and what resources will be needed.



    2. Elaboration - The project's architecture and required resources are further evaluated. Developers consider possible applications of the software and costs associated with the development.



    3. Construction - The project is developed and completed. The software is designed, written, and tested.



    4. Transition - The software is released to the public. Final adjustments or updates are made based on feedback from end users.



    The RUP development methodology provides a structured way for companies to envision create software programs. Since it provides a specific plan for each step of the development process, it helps prevent resources from being wasted and reduces unexpected development costs.

    ReplyDelete
  8. Rational Unified Process (RUP) is an object-oriented and Web-enabled program development methodology. According to Rational (developers of Rational Rose and the Unified Modeling Language), RUP is like an online mentor that provides guidelines, templates, and examples for all aspects and stages of program development. RUP and similar products such as Object-Oriented Software Process (OOSP), and the OPEN Process are comprehensive software engineering tools that combine the procedural aspects of development (such as defined stages, techniques, and practices) with other components of development (such as documents, models, manuals, code, and so on) within a unifying framework.
    RUP establishes four phases of development, each of which is organized into a number of separate iterations that must satisfy defined criteria before the next phase is undertaken: in the inception phase, developers define the scope of the project and its business case;
    in the elaboration phase, developers analyze the project's needs in greater detail and define its architectural foundation;
    in the construction phase, developers create the application design and source code and;
    in the transition phase, developers deliver the system to users. RUP provides a prototype at the completion of each iteration. The product also includes process support for Java 2 Enterprise Edition (J2EE) and BEA (WebLogic) development, and supplies an HTML-based description of the unified process that an organization can customize for its own use.

    ReplyDelete
  9. RUP is Rational Unified Process series.
    It is designed to provide learners with an introduction to the RUP software engineering process and framework. The series explains the software development principles behind the RUP and shows learners how to apply the RUP in their own organizations and to develop industry based software applications.
    The RUP Process captures many of the best practices in modern software development in a form that is suitable for a wide range of projects and organization

    Audience:

    ReplyDelete
  10. Rational Unified Process (RUP) is an evolutionary software development process.
    The RUP is a prescriptive, well-defined system development process, often used to develop systems based on object and component-based technologies.
    It is based on sound software engineering principles such as taking an iterative, requirements-driven, and architecture-centric approach to software development.
    It provides several mechanisms, such as relatively short-term iterations with well-defined goals.

    A.Nasmiya AS/07/08/045

    RUP establishes four phases of development, each of which is organized into a number of separate iterations that must satisfy defined criteria before the next phase is undertaken.

    ReplyDelete
  11. RUP is a software process product which provides disciplined approach within the industry based development software applications.It helps to meet the needs of the end user in a predictable schedule & budget.

    RUP increases the team productivity.Each member can share his knowledge,gain new ideas & work together for the benefits of the software development project.

    RUP fits all development teams which suit the needs of given purpose.This may increase the development software applications by achieving it's goals.

    RUP addresses the risks at every stage in the software development process which helps to identify the challenges of it's applications.This helps to reduce the risks & make suitable activities to recover from.

    End user also can contribute on the product by giving his comments & expectations.This requires the manufacturer to release new versions,correct the problems,reduce the conflicts & finish the features of the final product.These communications helps the manufacturer in their product use.

    Reacting to the end user causes a friendly environment which helps to build a strong development in the industry based software applications.

    ReplyDelete
  12. I would like to ask from charith... Do you know anything related to RUP and Project Management.. I mean how PM task is done with RUP : development?

    ReplyDelete
  13. This question is directed to Madhushanka....
    Can you further explain how RUP will help to Film Industry?

    ReplyDelete
  14. RUP is a software engineering process which enables the members of the development organization to do their tasks successfully by fulfilling client's needs along with a high quality of the product.
    When we carry on our OOP project using RUP , 1st we have to decompose the problem.It minimizes the risk.

    ReplyDelete
  15. The RUP guides software development teams how to effectively put to commercially proven approaches “best practices”to software development.
    There are 6 best practices:
    1.Develop software iteratively
    2.Manage requirements
    3.Use component-based architectures
    4.Visually model software
    5.Verify software quality
    6.Control changes to software

    ReplyDelete
  16. This question is directed to Isurika..
    can you further explain how do we minimize the Risk while we are decomposing our project scope..?

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

    ReplyDelete
  18. Advantages of RUP Software Development

    This is a complete methodology in itself with an emphasis on accurate documentation
    It is proactively able to resolve the project risks associated with the client's evolving requirements requiring careful change request management
    Less time is required for integration as the process of integration goes on throughout the software development life cycle.
    The development time required is less due to reuse of components.
    There is online training and tutorial available for this process.

    Disadvantages of RUP Software Development

    The team members need to be expert in their field to develop a software under this methodology.
    The development process is too complex and disorganized.
    On cutting edge projects which utilise new technology, the reuse of components will not be possible. Hence the time saving one could have made will be impossible to fulfill.
    Integration throughout the process of software development, in theory sounds a good thing. But on particularly big projects with multiple development streams it will only add to the confusion and cause more issues during the stages of testing

    ReplyDelete