نام کالا

قیمت

تعداد

حذف

• عنصر 3، مرحله1: درك وضعيت
• عنصر3، مرحله2: انجام تشخيص
• عنصر 3، مرحله3: تعريف كردن طرح كلي تشخيص
• عنصر3، مرحله4: تعريف كردن مسائل
• عنصر3، مرحله5: استنتاج يك سيستم فكري
• عنصر3، مرحله6: انجام طراحي مصنوعي/منطقي
• عنصر3، مرحله7: انجام طراحي فيزيكي
• عنصر3، مرحله8: اجراي طرح
• عنصر4: ارزيابي
• خلاصه

nIMSAD Evaluation of the Rational Unified Process
Introduction
Element 1: The Problem Situation
Element 2: The Methodology User (Intended Problem Solver)
Element 3, Stage 1: Understanding of the Situation of Concern
Element 3, Stage 2: Performing the Diagnosis
Element 3, Stage 3: Defining the Prognosis Outline
Element 3, Stage 4: Defining Problems
Element 3, Stage 5: Deriving the Notional System
Element 3, Stage 6: Performing Conceptual/Logical Design
Element 3, Stage 7: Performing the Physical Design
Element 3, Stage 8: Implementing the Design
Element 4: Evaluation
Summary

Introduction


The Rational Unified Process is the information systems methodolgy most widely in use today. The main contributers are the three amigos Ivar Jacobson, Grady Booch and James Rumbaugh who also designed the Unified Modeling Language.
It is mainly based on the Ericsson Approach, Objectory and the Rational Approach, which were combined 1995 to the Rational Objectory Process. The Unified Modeling Language together with the expirience of from Rational Inc. acquired software tool companies formed the Rational Unified Process.
The Unified Process is a software development process, that is the set of activities needed to transform a users's requirements into a software system, but it is also seen as process framework, which can be specialised for different purposes.
The three main aspects of the Unified Process are that it is
• use-case driven
• architecture-centric
• iterative and incremental
The basic sequence of an RUP project according to [2]:
• Get the team together.
• Decide what system will be built (there is apparently no other option than to build a system).
• Build a use case model and UI prototype.
• Use the UML process extensions to build an analysis object model.
• Segue into the more conventional UML stuff to do the design - class, state, sequence diagrams and the like.
• Think hard about architecture while you assign the designed classes to modules and packages
• Test against the use case model. RUP provides some excellent guidance on testing.
• Transition to live system and do the post mortem
این مقاله کامل که در 14 صفحه ترجمه شده و به همراه متن اصلی عرضه می شود و در ضمن متن اصلی در 6صفحه می باشد.