0% found this document useful (0 votes)
14 views10 pages

Error Handling: Poor Error Message May Result in Rejecting The Product

Uploaded by

adippatil456
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
0% found this document useful (0 votes)
14 views10 pages

Error Handling: Poor Error Message May Result in Rejecting The Product

Uploaded by

adippatil456
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/ 10

User Interface Design Issues B SE 26: Component Level X

1. Response Timne: Time between request and response of the system. If the response time is too
long, then the user becomes frustrated.

2. Error Handling: Poor error message may result in rejecting the product.
3. Help Facilities: User requires help when he needs some information_and he cannot find it
then the user is in trouble.

4. Application Accessibility: It states whether the application is simple to interact with or not.
Specia>guidelines are given to user while interacting with software.

OSubscribe
iko & hare

CS & IT Tutorials by Vrushali


Good & Bad Software System Design
A A

Cohesion
1) 2
3 Coupling
C Cohesioa Coupling
8 10) 8
Coupling 7
Cqupling
B 9tohesion B
2
Cohesion
(4) Coupling 10
Coupling
6 7 6
Cohesion eohesion

Bad modularization: Good modularization:


low cohesion, high coupling high cohesion, low coupling

OSubscribe
iko & share

CS& IT Tutorials by Vrushali


Why High Cohesive & Low Coupling generate good design?
ºDue to Low Coupling
Part 1
" Readability: Modules are easy to understand not complex. Coupling
"Maintainability: Changes in one module little impact on other.sion Part 2

" Modularity: Enhance modules development. Part 3

Scalability: Adding new module remove existing one easy. Module 1


Part 1
Testability: Modules are easy to test & debug.
Coupling Cohesipn
Part 2

Due to High Cohesion


" Readability: Related functions easy to understand. Part 1
Module 2
" Reusability: Easily Reuse module in another system. Part 2

"Reliability: Generate overall improvement of system. Cohesion


Part 3
Testability: Modules are casy to test & debug. Module 3
OSubscribe
liko &share

CS& IT Tutorials by Vrushali


Importance of Software Architecture
1. Security: The system is secured against malicious users by encryption or any other security
measures due to layered sotware architecture.
2. Performance: It handle request and response of the page in minimum time.
3. Maintainability: Architectural design process uses easily modifiable and replaceable
components which is easy to changethem over time according to the new requirements.
4. Safety: Avoid critical functionalities_ in small components & improve communication of
the system.
5. Availability: Architectural design process includes corresponding components,
functionalities for handling the occurrence of anytype of errors.
OSubscribe
iko & shara

CS & IT Tutorials by Vrushali


Data Centered A

the center of this architecture and is accessed frequently by everyone.


Data store at Chent S/w

present within the store.


Chent S/w
Cent Sw

Update, add, delete or modify the data


Information System etc.
It is widely used in DBMS, Library
Data store

Client SW

ient S/

Clent SW
Cient S/w

Advantages:
1. Repository of data is independent of clients StudentDtahe.

2. It may be simple to add additional clients.


Aspty

3. Modification can be very easy. Resorta Suppher


Statt Recuest

Stuoen

Library Manag

Disadvantages: AvgiDty
1. Data replication or duplication is possible. shudents Management

2 Changes in data structure highly affect the clients.


Book Database
endent of clients Student Database

itional clients. Reply

Reports
Supplier
sy. Staff Request Sock

Students
nfo
Library Management
System

Reports
Recuest
Aviaity

ion ispossible. Students Repty


Management

ighly affect the clients.


Book
B2

Book Database
CSubscribe
Data Flow Architecture
This architecture is used when input data to be transformed into output data through a series
of computational manipulative components.
Pipe is a connector which passes the data directionally from one filter to the next.
Filter is a component reads the data from its input pipes and performs its function. Connector: Pipe

This data and places the result on all output pipes.


Filter
Filter -Filter -Filter
Filter

Advantages: Component: Filter

1. With this design, concurrent execution is supported.


Datqueries
abase Database
Requests server
Chent Web
side Query
Disadvantages: HIML fles
server
results
Page
1. Does not allow greater user engagement. HIML fles
generator
OSubscribe
iko & shara

CS& IT Tutorials by Vrushali


Object Oriented Architecture
"Objects are the foundational building blocks for all kinds of software applications.

1. Object: Object is an instance of a class. Example Student S, Person;


2. Class: It defines all attributes, methods, which represents the functionality of the object.
3. Encapsulation: It is the process of binding similar types of elements of an abstraction.
4. Abstraction: It is the removal of irrelevant essentials from users.
5. Inheritance: It derivinga new class from existing one. It increases code reusability.
6. Polymorphism: It has multiple forms, Ex: draw graphic objects circle, rectangle, triangle
7. Message Passing: Sending and receiving data among objects through function parameters.

OOP OSubscribe
liko & share

CS & IT Tutorials by Vrushali


Layered Architecture
Data moves from one level te another level for processing is called layered architecture.
" Number of different layers are defined every layer performing well-defined set of operations.
Outer layer components manage the user interface operations.
Inner layer components will perform the operating system interfacing.
Intermediate layers provide utility services and application software functions.
Example: E-commerce web applications development like Amazon.
Components User Intertace Layer

Application Layer

Logic Tier Utility Layer


Presentation Tier Data Tier

Core Layer

Client Server Database

OSubscribe
liko & share

CS & IT Tutorials by Vrushali


Architectural Views
It is generally used to represent entire architecture that is useful and meaningful to one or
more stakeholders in system.

1. Use case View: Users view to handling product as per requirement. Use case diagram used.
2. Design View: Organize design information, significant features, entities and attributes.
3. Process View:Describe communication, behavior &synchronization aspects of the design.
4. Implementation View: It address source çode integrators and developers of project.
5. Deployment View: It describes &explains environment within system runner & executed.

OSubscribe
iko & share

CS & IT Tutorials by Vrushali

You might also like