Matches in DBpedia 2015-10 for { <http://dbpedia.org/resource/4+1_architectural_view_model> ?p ?o }
Showing triples 1 to 34 of
34
with 100 triples per page.
- 4+1_architectural_view_model abstract "4+1 is a view model designed by Philippe Kruchten for "describing the architecture of software-intensive systems, based on the use of multiple, concurrent views". The views are used to describe the system from the viewpoint of different stakeholders, such as end-users, developers and project managers. The four views of the model are logical, development, process and physical view. In addition selected use cases or scenarios are used to illustrate the architecture serving as the 'plus one' view. Hence the model contains 4+1 views: Logical view : The logical view is concerned with the functionality that the system provides to end-users. UML Diagrams used to represent the logical view include Class diagram, Communication diagram, Sequence diagram. Development view : The development view illustrates a system from a programmer's perspective and is concerned with software management. This view is also known as the implementation view. It uses the UML Component diagram to describe system components. UML Diagrams used to represent the development view include the Package diagram. Process view : The process view deals with the dynamic aspects of the system, explains the system processes and how they communicate, and focuses on the runtime behavior of the system. The process view addresses concurrency, distribution, integrators, performance, and scalability, etc. UML Diagrams to represent process view include the Activity diagram. Physical view : The physical view depicts the system from a system engineer's point of view. It is concerned with the topology of software components on the physical layer, as well as the physical connections between these components. This view is also known as the deployment view. UML Diagrams used to represent physical view include the Deployment diagram. Scenarios : The description of an architecture is illustrated using a small set of use cases, or scenarios which become a fifth view. The scenarios describe sequences of interactions between objects, and between processes. They are used to identify architectural elements and to illustrate and validate the architecture design. They also serve as a starting point for tests of an architecture prototype. This view is also known as use case view.↑ 1.0 1.1 ↑ 2.0 2.1 2.2 2.3".
- 4+1_architectural_view_model thumbnail 4+1_Architectural_View_Model.jpg?width=300.
- 4+1_architectural_view_model wikiPageID "11151650".
- 4+1_architectural_view_model wikiPageLength "3088".
- 4+1_architectural_view_model wikiPageOutDegree "14".
- 4+1_architectural_view_model wikiPageRevisionID "635486760".
- 4+1_architectural_view_model wikiPageWikiLink Activity_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Category:Software_architecture.
- 4+1_architectural_view_model wikiPageWikiLink Class_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Communication_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Component_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Deployment_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Package_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Philippe_Kruchten.
- 4+1_architectural_view_model wikiPageWikiLink Sequence_diagram.
- 4+1_architectural_view_model wikiPageWikiLink Use_case.
- 4+1_architectural_view_model wikiPageWikiLink View_model.
- 4+1_architectural_view_model wikiPageWikiLink File:4+1_Architectural_View_Model.jpg.
- 4+1_architectural_view_model wikiPageWikiLinkText "4+1 architectural view model".
- 4+1_architectural_view_model hasPhotoCollection 4+1_architectural_view_model.
- 4+1_architectural_view_model wikiPageUsesTemplate Template:Reflist.
- 4+1_architectural_view_model subject Category:Software_architecture.
- 4+1_architectural_view_model hypernym Model.
- 4+1_architectural_view_model type Person.
- 4+1_architectural_view_model comment "4+1 is a view model designed by Philippe Kruchten for "describing the architecture of software-intensive systems, based on the use of multiple, concurrent views". The views are used to describe the system from the viewpoint of different stakeholders, such as end-users, developers and project managers. The four views of the model are logical, development, process and physical view. In addition selected use cases or scenarios are used to illustrate the architecture serving as the 'plus one' view.".
- 4+1_architectural_view_model label "4+1 architectural view model".
- 4+1_architectural_view_model sameAs 4+1_Sichtenmodell.
- 4+1_architectural_view_model sameAs معماری_۱+۴.
- 4+1_architectural_view_model sameAs m.02r1rlf.
- 4+1_architectural_view_model sameAs Q229824.
- 4+1_architectural_view_model sameAs Q229824.
- 4+1_architectural_view_model wasDerivedFrom 4+1_architectural_view_model?oldid=635486760.
- 4+1_architectural_view_model depiction 4+1_Architectural_View_Model.jpg.
- 4+1_architectural_view_model isPrimaryTopicOf 4+1_architectural_view_model.