SDA short Questions

Logical View

Viewer : End-user
Considers : Functional requirements- What the system
should provide in terms of services to its
users.
This view shows the components (objects) of the system as
well as their interactions / relationships.
UML diagrams – Class, State, Object, Sequence,
Communication diagrams.

Process View
(The process decomposition)
Viewer : Integrators
Considers : Non - functional requirements (concurrency,
performance, scalability)
The process view shows the processes / workflow rules of a
system and how those processes communicate with each
other.
UML diagrams – Activity diagram

Development View
(Subsystem decomposition)
Viewer : Programmers and Software Managers
Considers : software module organization
(Hierarchy of layers, software management,
reuse, constraints of tools)
It gives a building block view of the system.
Eg: Packages Used, Execution Environments, Class
Libraries and Sub systems utilized.
UML diagrams – Component, Package diagrams

Physical Views
(Mapping the software to the Hardware)
Viewer : System Engineers
Considers : Non-functional req. regarding to underlying
hardware (Topology, Communication)
This view shows the systems execution environment
UML diagram – Deployment diagram.

Quality Atribute

Suitability: Functionality is suitable to all end users

 Compliance: Functionality is compliant with applicable regulatory
guideline
Certifiability: System is able to be certified to some standard by an
independent third party
• Conformance: Conformance to industry and operational
standards
Accessibility: The user interface can be accessed and utilized by differently
abled users
Adaptability: Ability to change the system components to meet
new business needs
Extensibility & Modifiability: Ability to easily add new features
and customizations
Replaceability: Ability to replace system in the future
Reporting: The system supports generating various reports

System Quality Attributes

Security Perspective
Security: System is secure:
confidentiality, integrity, availability, accountability and
assurance
Privacy: System does not reveal (or allow revealing) of
information to improper parties
Non-exploitability: The system, its components, and its
configurations are hardened against known and
unknown security vulnerabilities
Accountability: The system records all user interactions
and data changes
Auditability: The system makes accountability
information available to managers and operators

System Quality Attributes

Performance Perspective
Efficiency: System does not waste valuable resources
Performance: Perceived response is immediate
Scalability: Able to handle increased usage on the
appropriate amount of resources, able to add resources
quickly and easily to handle increases in demand
Responsiveness: The system responds to interactions
with minimal delay and/or latency
Capacity: The system can handle sudden peaks and
surges in demand
Throughput: The system can handle a specified number
of interactions or transactions within a specified duration
without undesirable degradation in terms of other
qualities

System Quality Attributes

Configuration Perspective
Configurability: Ease of making configuration changes
Integrity: The system, its configuration, and its data
cannot be changed by unauthorized
parties(including accidental or deliberate
misconfiguration)
• Deployability: Ease of
installation, reinstallation, and updating
Portability: System supports changes in choice of
underlying technologies and architectures (such as
database platform, operating system platform, etc.)
Interoperability & Compatibility: Functionality
interoperates with other systems easily

System Quality Attributes

Operations Perspective
Availability & Fault Tolerance: System continues operating properly in the event of failure by
one or more of its components
Isolation: System survives and gracefully handles situations in which dependent
“downstream”
systems become unavailable
Continuity: System recovers from failures in surrounding environment
Disaster Recoverability: The system, its data, and its configuration can be completely and
quickly recovered from backups and configuration management repositories, even in the event
of a catastrophic loss of a data center
Operability: System can readily be kept in a functioning and operating
condition by manual or automated means
• Maintainability: System upgrades can quickly and safely be performed with a
minimum of downtime
• Monitorability: Ability for operators to easily see how the system is operating
• Alerting: The system notifies operators of faults and exceptional conditions
• Maturity: System components are proven stable by others
• Stability and Reliability: The system exhibits infrequent failures

System Quality Attributes

Data Perspective
Durability: The system does not lose critical operational data, whether “inflight”
or “at-rest”
Reversibility: Undesirable system and data changes can be reversed quickly
and easily with minimal disruption to the business
Cacheability: The data is structured with appropriate separation of volatile
(changing) and non-volatile data to support caching
Archivability: Older data can be relocated to separate data stores
Partitionability: The system supports splitting like-kind data across
multiple databases (for scalability, risk mitigation, etc.)
Idempotency: Interactions performed twice result in same change as if
performed once
 Concurrency: The system supports a high degree of simultaneous
interactions with the database without degrading in performance or
sacrificing data integrity (ex: optimistic locking, snapshot isolation)
Backup : The database and message queues support being backed up
without the system being taken offline

System Quality Attributes

Diagnostics Perspective
Supportability: System operators can quickly and easily
identify faults and perform root cause analysis within an
environment of controlled access to information and
restricted privileges
Instrumentability: System is capable of recording various
operational metrics that can be analyzed and reported
on
Traceability: System can be configured to record its own
interactions with itself in order to aid support personnel
in diagnosing problems
• Logging: The system logs external and
interactions with configurable degrees of detail

System Quality Attributes

Enhancement Perspective
Analyzability: Ability to figure out how the
system functions
Documentability: Ability to communicate
about the system in writing
Understandability: Able to use system with little
training
Learnability: Supports learning of system functionality
with little external interfacing
• Testability: Ability to create repeatable and
specific tests of the system and potential for
some to be automated