Assignment 002

(Post-Mid Assignment)
(Software Architecture
Design)

Student Name: Maira Kamran

Roll No: 054
Class: BSSE-6B
Submitted To: Sir usman Akbar
 Superior University (Lahore)

Table of Contents
Architectural Goals 1
Architectural Significant Requirements 2
Functional Requirements 2.1

Non Functional Requirements 2.2

Decisions and Justification base on (NFRs) 3

Key Abstractions/Domain Model 4
Software Partitioning 5
Logical Component Model 5.1
Process Model 5.2
Physical Component and Layers 5.3
Development Model 5.4
Deployment Model 6
Refine the architectural significant requirements for "Careem"
App as Software Architect.
A passenger came for making an online careem app car booking service.
Passenger can easily sign up and Sign in on this site and book a car and see
information about the car and also select the car like (Bus and car).Passenger can
also cancel booking of the car. When passenger book a car he tell his/her pick up
location and drop location passenger can also select the city. When passenger
reached his/her destination he pay his/her bill by cash or by credit card.

Architectural Goals
To provide convenient, reliable, and affordable transportation services to
passenger or earn money.

Architectural Significant Requirements

2.1 Functional
2.2 Nonfunctional

Functional requirement
 Sign up
 Sign in
 Book training
 Book schedule
 Select hour
 Select Cites
 Booking
 Canceling
  Drop off
 Pick up
 Payment

Non functional requirement

Security
 This site contains security on registration process that Passenger data or
information is secure.
 Service of this application for passenger is secured passenger can ride from
one place to another safely.

Availability

 Sometime server down or software issue came and we set a goal to resolve
that problem to access data available.
 24 hour Service is available

Usability

Passenger can easily access the site or learn or use the system.

Performance

When passenger wants this service at any place they give quick response.

Reliability

Service condition is good and don’t breakdown.

Decisions and Justification base on (NFRs)
Security

The website is secure passenger can easily use this website and easily booking this
service at any place and this service is secure passenger can ride secure from one
place to other and driver is full trained and detail of the driver is checked.

Availability

Sometime server down or software issue came and we set a goal to resolve that
problem to access data available. And data or service is available and modifiable in
the fashion by authorized to do, 24 hour Service is available.

Usability

Passenger can easily access the site or learn or use the system.

Performance

When passenger wants this service at any place they give quick response.

Reliability

Vehicle breakdown should not occur if that condition occurs Mean time to fashion
recovery of vehicle is available.
Logical Component Model (Class Diagram)
Development View (Package Diagram)
Process View (Interaction Diagram)
Scenarios View (Use-case Diagram)
Specification Level Deployment Diagram

Physical component and layer

Key Abstractions/Domain Model
UML(User interface)