Architecture Concepts of outsytems module and application

Question

What is the benefit of a good architecture?

Reduces risk by avoiding service abstraction
Manages complexity and reduces costs, removing the need to plan
Abstracts business concepts, making unnecessary to worry with non functional requirements
Makes dependencies manageable and solutions flexible to evolve

What is the main nature of an end-user module?

Provides functionality to support user stories and must be independent of other end-user modules
Provides reusable business processes but must not be consumed by other end-user modules
Orchestrates cross-application end-user functionality
Designed by an end-user

Why is reusability so important?

Promotes cost savings by allowing the definition of a concept in multiple modules
Gives flexibility to create/update/delete entity records directly in an end-user module
It allows sharing screens between different end user modules
Promotes cost savings and avoids multiple definitions of concepts

Why is mash-up a key aspect of architecture?

Promotes cost savings by allowing the dispersion of a concept into multiple modules
Leverages the composition of information and logic on top of reusable building blocks
Advocates the merge of two concepts on the same module, if one depends on the other
Gives flexibility to create/update/delete entity records directly in an end-user module

What is a good reason for joining concepts when assembling a module?

Concepts have the same lifecycle, even if not functionally related
To reduce the number of modules and references, simplifying the release cycle
To accelerate development, by reducing the number of references
Concepts belong to the same functional area and a typical consumer exercises all the concepts

What is a good reason to split a core module in two?

To make sure that entities are isolated from business logic
To avoid upward references
To separate unrelated concepts with different lifecycles
To increase development speed

Help me to find the correct answers.

Accepted Answer

HI,What is the benefit of a good architecture?Makes dependencies manageable and solutions flexible to evolveWhat is the main nature of an end-user module?Provides functionality to support user stories and must be independent of other end-user modulesWhy is reusability so important?Promotes cost savings and avoids multiple definitions of conceptsWhy is mash-up a key aspect of architecture?Leverages the composition of information and logic on top of reusable building blocksWhat is a good reason for joining concepts when assembling a module?Concepts belong to the same functional area and a typical consumer exercises all the conceptsWhat is a good reason to split a core module in two?To separate unrelated concepts with different lifecycles &#160;Can someone correct me? and why?THANKS!