Scribd
Upload
10 views2 pages

SDD (TH)

Software Architecture and Design

Uploaded by

humzasadiq52
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views2 pages

SDD (TH)

Software Architecture and Design

Uploaded by

humzasadiq52
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

What is 4 + 1 view? Briefly define each view.

The "4+1 View Model" in software architecture, you can view the system with
different perspectives. It is called this way because it combines four primary
architectural views with an additional perspective that encompasses all of them.
Here's a brief explanation of each view:

• Logical View: Describes the software's functionality from a high-level


perspective, focusing on how many objects (features, components, and
functions) are there and their connections.
• Process View: Focuses on the runtime behavior (Activity) and organization of
the system, including concurrency and communication between functions or
objects.
• Development View: It is based on modules, it represents the source code
organization and structure, including packages, classes, and connections from
the developer’s point of view during the software's construction.
• Physical View: Describes the deployment, interaction and distribution of the
software across different hardware or network infrastructure, including servers,
databases, and network connections.
• Use-Case View: This is the "+1" view, which provides a unifying perspective by
showing a complete design by performing validation through set of scenarios or
use cases. It connects the other four views by illustrating how they work
together to support specific user interactions or system behaviors.
Compare StarUML with any other similar tool and state their significance and
limitations
draw.io is an online diagramming tool that allows users to create a wide variety of
diagrams, flowcharts, and visuals including UML diagrams. It's a web-based
application that runs directly in the browser, making it accessible to users
regardless of their operating system or device. draw.io is simple, easy to use, and
has real-time collaboration features.
StarUML is a powerful and professional software modeling tool used for designing
and documenting software systems. It supports the Unified Modeling Language
(UML). It is well-suited for software developers and system architects who require
advanced UML modeling capabilities and extensive customization options,
especially for larger projects with complex requirements.
Significance:

StarUML draw.io
• Better depth of detail as it is • Free and Open-Source.
primarily focused on UML diagrams. • It also supports a wide variety of
• It supports various UML diagrams, diagrams other than UML diagram.
including class diagrams, sequence • It has real-time collaboration
diagrams, activity diagrams, and feature.
more. • Web-based interface and offline
• Supports code generation for functionality.
various programming languages
including Java, C#, C++ and Python
via open-source extensions.
Limitations:

StarUML draw.io
• It requires a paid license for most • Cannot generate code directly from
features. UML models.
• More Complex, not beginner- • It does not have the extensive UML
friendly capabilities of StarUML. It provides
• User-Experience is not so good, as a more basic level of UML support
the UI is cluttered and outdated. compared to dedicated UML tools
• Steeper learning curve. like StarUML.
• Not the same depth of detail or
specialized as professional UML
diagramming tools.

1. Draw a Use-Case diagram for an Online Shopping System


Hint: Web Customer actor uses some web site to make purchases online. Use cases
are View Items, Make Purchase and Client Register. View Items use case could be
used by customer if he only wants to find and see some products. This use case
could also be used as a part of Make Purchase use case. Client Register use case
allows customer to register on the web site through <<Service>>Authentication
actor. Note, that Checkout use case is included use case not available by itself -
checkout is part of making purchase. View Items use case is extended by several
optional use cases - customer may search for items and browse catalog. Checkout
use case includes Customer Authentication. It could be done through user login
page (sign in), Remember me page. Actor: Service Authentication.
Checkout use case also includes Payment use case which could be done either by
using credit card and external credit payment service or with PayPal. (Actors: Credit
Payment Service, PayPal)
2. Draw an activity diagram for online shopping. Online customer can browse or
search items, view specific item, add it to shopping cart, view and update
shopping cart, checkout. User can view shopping cart at any time. Checkout is
assumed to include user registration and login.

You might also like