Software Architecture and Database Concepts

Users with Editor access in Lotus Notes can create personal views (private to their use) but cannot create shared views - that privilege requires Designer or Manager access. This access hierarchy makes option B the correct answer.

The stated steps are essentially correct for creating a subform in Domino Designer 6. However, the statement is marked false - this is likely because the wording has minor imprecision or the question expects knowledge that subforms can be created through multiple methods. The correct label B suggests the statement as written has some flaw.

Lotus Notes has two main types of views: shared views (accessible to multiple users) and personal views (private to individual users). Since both types exist and are valid view categories, option D 'Both' correctly answers the question.

In Siebel applications (or similar database systems), user data is stored across multiple base tables rather than a single table. This normalized database design allows efficient data management and relationships. Option D 'More than one base table' correctly represents this multi-table architecture.

A view in database systems (like Lotus Notes) displays a list of documents/records from the database. It serves as a placeholder/interface for viewing data. Option D combines both the definition (list of documents) and function (viewing data), making it the most complete answer.

A form serves as both the interface placeholder for entering information AND the structural framework for storing that information in a database. Option C correctly combines both aspects - it's where you enter data (placeholder) and the system that stores it (framework).

Forms are versatile and can contain multiple types of elements: fields (for data input), actions (buttons/scripts), tables (for structured data layout), and graphics (for visual elements). Since all these component types can be part of a form, option E 'All of these' is correct.

A subform in Lotus Notes is a reusable form component - it's a horizontal section (slice) that can be used in multiple forms, it's a shared part across many forms, and it can contain the same elements as regular forms. Since all three descriptions A, B, and C are accurate, option E combining them is correct.

EIM (Enterprise Integration Management) is an integration approach that processes data in batches rather than in real-time. Batch mode integration collects data over a period and processes it collectively, which is more efficient for large volumes of data that don't require immediate processing.

According to Roger Pressman's software engineering principles, design is information-driven. This means design decisions and architectural choices are based on information about requirements, constraints, and system goals that have been gathered and analyzed during earlier phases.

Strong software design exhibits all three characteristics: modularity (breaking into independent components), high cohesion (elements within a module serve a single purpose), and low coupling (minimal dependencies between modules). These principles make systems more maintainable, testable, and scalable.

Software architecture is NOT the same as the functioning end product. Architecture is the blueprint - the high-level design of components, their relationships, and principles guiding the system. The functioning software is the implementation of that architecture. Confusing architecture with the product leads to premature optimization and architectural over-engineering.

Software architecture design has two primary levels: data design and architectural design. Data design focuses on data structures, databases, and data flow. Architectural design addresses the overall system structure, component organization, and their relationships. XP (Extreme Programming) is a methodology, not a design level. This two-level approach is standard in software engineering.

KDD stands for Knowledge Discovery in Databases. It is the overall process of discovering useful knowledge from data, encompassing data cleaning, integration, selection, transformation, mining, and interpretation. Note it is 'in' not 'of' - the preposition matters for the correct acronym. This is a foundational concept in data mining and machine learning.

In software architecture, an archetype is a generic structure or pattern - like a Node which represents a fundamental building block. Architectural Style is a pattern, not an archetype. Actors are external entities that interact with the system, used in use cases. The question tests understanding of architectural primitives vs. patterns vs. external entities.

ATAM stands for Architecture Trade-off Analysis Method. It is a structured method for evaluating software architectures by analyzing trade-offs between quality attributes like performance, security, modifiability, and reliability. The 'trade-off' in the name is essential - architectures always involve balancing competing quality requirements.

Complexity of architecture is measured using dependencies - the relationships and couplings between components. High dependency complexity makes systems harder to maintain, test, and evolve. Coupling is related but refers specifically to how closely connected components are. Beta testing and architecture testing are quality activities, not complexity measures.