| دانلود
مقاله ترجمه شده بررسی فرآیند یکپارچه رشنال
بررسی فرآیند یکپارچه رشنال
|
|
| دسته بندی | کامپیوتر و IT |
| فرمت فایل | |
| حجم فایل | 309 کیلو بایت |
| تعداد صفحات فایل | 15 |
|
بخشی از ترجمه فارسی: فرایند یکپارچه منطقی (RUP) یک اسلوب سیستمهای
اطلاعاتی است که امروزه در وسیع ترین حالت استفاده میشود. طراحان اصلی آن سه نفر
هستند به نامهای ایوار یاکوبس، جرادی بوچ و جیمز رامبو، که همچنین زبان نمونهسازی
یکپارچه را هم طرح کردهاند. این فرایند اساساً مبتنی بر خط مشی (روش) اریکسون،
ابجکتوری و خط مشی منطقی (عقلانی) است که در سال 1995 با فرایند ابجکتوری منطقی
ترکیب شدند. زبان مدل سازی (نمونهسازی) یکپارچه به همراه تجربهای از شرکت
Rational، فرایند یکپارچه منطقی را تشکیل داد. وضعیت مسئله: |
|
فهرست مطالب این مقاله: • مقدمه |
|
بخشی از مقاله انگلیسی: 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. Element 1: The Problem Situation The methodolgy is concered about the context. This is especially seen in the two core workflows Requirements and Analysis which are mostly important in the first to phases (Inception, Elaboration), but come all along the process, because of it’s iterative nature. As mentioned above the Unified Process is use-case driven. It means that the whole process is controlled by the way the users interact with the system. Every produced model can be traced back to a use case. That the Unified Process is architecture-centric means that also from the beginning of the process there is a strong emphasis on the architecture of the information systems. This includes hardware and frameworks used, distribution and programming languages. |
