1.

System Modeling Perspectives

 Context Modeling: Focuses on understanding the system’s external environment and
dependencies, detailing connections with outside entities. Example: In a library management
system, context modeling shows relationships with users like Librarians, patrons, databases,
and Payment Processors, enabling an understanding of external dependencies.
 Interaction Modeling: Documents the steps between user actions and system responses.
Example: In an online ordering platform, interaction modeling illustrates the sequence of
actions a user takes to order a product, including actions like browsing, adding items to the
cart, and checkout.
 Structure Modeling: Defines the internal layout and organization of components, often
visualized through UML class diagrams or component diagrams. Example: In a library
system, structure modeling might show User, Book, and Transaction entities and how they
interrelate, setting a clear foundation for component organization.
 Behavior Modeling: Shows the dynamic side of the system, such as how objects transition
between states. Example: In an online food delivery service, behavior modeling can illustrate
the status of an order moving from Order Received to Preparing, Out for Delivery, and
Delivered.
2. System Architecture Perspectives
Describes the system’s structure through a component-based view, covering:
 Front-End Components: User interface and presentation layer (e.g., HTML, CSS,
JavaScript for web applications).
 Back-End Components: Application logic and server functions (e.g., API handling,
database management).
 Database Layer: Stores persistent data (e.g., MySQL or MongoDB for data storage and
retrieval).
Deployment Perspectives: Discuss cloud-based vs. on-premises deployment, considering factors
like scalability, cost, and security. Cloud deployments offer greater flexibility and scalability,
while on-premises deployments may provide enhanced security for sensitive data.
3. Architectural Patterns
 Client-Server Pattern: A common setup where a server hosts resources and a client
accesses them, ideal for applications like websites or apps.
Example: In a retail system, the client (web browser or mobile app) requests data from the
server, which hosts product details and user accounts.
 Layered Pattern: Separates functionality across layers, promoting maintainability and
scalability.
Example: In a payroll processing system, the layered architecture separates presentation (UI
layer), logic (calculations and business rules), and data storage layers, streamlining updates and
isolating issues within each layer.
4. Model-View-Controller (MVC) in Layered and Client-Server Architecture
Model-View-Controller (MVC) Pattern:
 Model: Represents the data or business logic.
 View: Displays data to the user and handles UI components.
 Controller: Handles user input, updating the model and view accordingly.
Example: In a blogging platform, MVC allows the separation of user data management (Model),
page display (View), and user interactions such as creating or editing posts (Controller). MVC is
especially effective in Layered or Client-Server architectures by maintaining a clear separation
between data handling, UI, and user interaction logic.
5. UML Diagrams
 Activity Diagram: Shows workflows and business processes. Example: An online store’s
activity diagram details steps from Browse Products to Add to Cart and Checkout, helping
visualize the overall workflow.
 Use Case Diagram: Depicts user interactions with the system. Example: In a banking app,
use cases might include Deposit Money, Withdraw Cash, and Check Balance.
 Sequence Diagram: Illustrates interactions between system components over time, often
used for complex processes.
Example: In a travel booking site, a sequence diagram could outline the steps from user login
to ticket selection and payment confirmation.
 Class Diagram: Shows object structures and relationships. Example: In a library system, a
class diagram includes entities like a Book, a Patron, and a Loan.
 State Diagram: Depicts transitions between states in response to events. Example: An order
system’s state diagram shows the Order Placed, Dispatched, Delivered, and Cancelled state
6. Behavioral Modeling
 Data-driven modeling: Represents how data influences system behavior. Example: In an
analytics system, filters and views change based on the data queried, reflecting dynamic data-
driven results.
 Event-Driven Modeling: Focuses on events that trigger state changes, ideal for systems with
user interactions.
Example: In an ATM, event-driven modeling captures user interactions like Insert Card,
Enter PIN, and Select Transaction, transitioning the system to appropriate states.
7. Generic Models of Application Systems
 Transaction Processing System: Manages user interactions requiring a series of steps, like
banking transactions at an ATM, where users insert a card, enter a PIN, and proceed with
balance checks or withdrawals.
 Language Processing System: Converts one language into another, such as compilers
converting high-level programming languages (Java, Python) into machine code for
execution.