تاریخ انتشار | 01 آوریل 2022 |
---|---|
فرمت فایل | ورد ـ word ـ قابل ویرایش |
تعداد صفحات | 6 صفحه |
این تحقیق مقاله دارای موضوعاتی همچون مقدمه تحلیل نتیجه گیری و … می باشد و در ۶ صفحه تنظیم شده است و دارای پسوند ورد word قابل ویرایش است
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.
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.
Furthermore there are two optional concepts in the requirements workflow which support the capturing of the business environment:
Domain Model – a UML class diagram which captures the most important types of objects in the context of the system.
Business Model – technique for understanding the business processes of an organization. It presents a business like a use-case model for a software system from the usage perspective and outlines how it provides value to its users. It also has a Business Object Model which depicts the business entities like the domain model.
But apart from that is very little said about the problem situation. It is a positivistic methodology. It assumes that one is only concerned with system specification. RUP has nothing to say about business requirements or business process modelling – exept that use cases are enough. [2]
و…
این ها فقط بخشی از متون این مقاله و تحقیق و پروژه به صورت پراکنده و ناقص می باشد ، برای دانلود تحقیق ، دانلود مقاله ، دانلود پروژه به صورت کامل لطفا آن را خریداری نمایید. ( بالای صفحه )
دیدگاهها
هیچ دیدگاهی برای این محصول نوشته نشده است.