Requirement Modeling Pattern As A New Process Pattern

摘要

RUP is a Use Case Driven, Architecture Centric (4+1) and Iterative & Incremental. We believe that, RUP needs to be Requirement Driven, Architecture Centric (4R1) and Iterative, Incremental and Improving process. This paper presents a process patterns definition for RUP including pattern called "Software Requirement Modeling Pattern (RMP)" in the RUP framework. The 4+1 software architecture used in RUP is extended to support Requirement Modeling Pattern. It is shown that, to include process pattern, RUP needs to be a Requirement Driven Approach. Requirement Modeling Pattern is applied in the RUP framework according to our definition of process pattern. Our aim is the extension of requirement types. In fact, a new requirement type called "Software Process Requirement" is defined and some problems of the software development process domain are involved in it. There are three questions that must be addressed. First, "How the behavior of requirements are represented?" second, "In which repository the states of requirements are saved?" third, "Which transformation exist from model elements to real requirements?". We show that the proposed process pattern needs Requirement Driven Approach. In the proposed process pattern, UML is used as a specification, visualization, modeling, and documentation language. In Requirement Driven Approach (instead of Use Case Driven Approach in RUP), some relationships between requirement and artifact classes are highlighted by a model. Rational Rose and Rational RequisitePro are used to manage the Artifact Life Cycle and control the requirements. To use the Requirement Driven Approach (RDA) we need a modified software architecture, and inclusion of a new view called "Requirement View". By using this view, we change the name of Software Architecture from (4+1) to (4R1), where R indicates the "Requirements". In summary, the 4R1 Software Architecture is given which is a superset of the 4+1 Software Architecture. A Requirement Model is associated to Requirement View, and the proposed process pattern is defined based on the new view.