Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
66 views

Experiment No. 1 AIM: Modeling Using XADL With Arch Studio Tool. Xadl

The document outlines 8 experiments related to software architecture. Experiment 1 involves modeling with XADL and Arch Studio. Experiment 2 is an architectural analysis of a B.E. project. Experiment 3 identifies the architectural style of an existing software application. Experiment 4 analyzes connectors in two open source applications. Experiment 5 replaces an existing connector. Experiment 6 creates a web service using SOA. Experiment 7 identifies styles imposed by middleware. Experiment 8 redesigns a B.E. project architecture to improve non-functional requirements.

Uploaded by

thisaintmyid
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
66 views

Experiment No. 1 AIM: Modeling Using XADL With Arch Studio Tool. Xadl

The document outlines 8 experiments related to software architecture. Experiment 1 involves modeling with XADL and Arch Studio. Experiment 2 is an architectural analysis of a B.E. project. Experiment 3 identifies the architectural style of an existing software application. Experiment 4 analyzes connectors in two open source applications. Experiment 5 replaces an existing connector. Experiment 6 creates a web service using SOA. Experiment 7 identifies styles imposed by middleware. Experiment 8 redesigns a B.E. project architecture to improve non-functional requirements.

Uploaded by

thisaintmyid
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 16

Experiment No.

AIM: Modeling using XADL with Arch Studio Tool.

XADL:

Architecture Studio:
Eg: - Architecture of any System

Conclusion: List of Architectural studio symbols used in modeling


Experiment No. 2

AIM: Architectural Analysis of B E Project topic.

Title of B.E Project:

Scope of the Project:

Architectural Diagram: Attached

Architectural Style used:

Component & Connectors explanation:


Conclusion: Style used & why that style is used
Experiment No. 3

AIM: Identifying the Architectural Style of any existing proprietary Software


Application.

Preparatory S/W Application:

Software Application Features:

Architectural Model:
Architectural Style Identified & Why that style:

Conclusion: Used style & list others possible Architectural style


Experiment No. 4

AIM: Case Study of any two open source application architectures, identifying their
connectors according to their types and spotting the trends in the system’s
connector usage.

Open Source Applications:


1.

2.

Software Application Features:


1.
2.

Architectural Model:
1.
2.

Conclusion: Identified Connectors types are:


Experiment No. 5

AIM: - For an open source application, replace the existing connector.

Open source application name:

Applications existing connector & its functionality:

Replaced connectors may be used in place of identified connectors:

Conclusion:
Experiment No.6

AIM: Creating a Web Service as Service Oriented Architecture

Web Service:
Name:

Function:

Language / Protocol used:

Advantages of a Web Service in Software Architecture:

Conclusion:
Experiment No 7

AIM: Identify the architectural style rules imposed by the middleware platform.
Development of an application using existing components atop middleware
such as CORBA, COM, JavaBeans etc.

Middle Were Used:

Architecture style of Middleware:

Application Developed:

Name:

Steps Followed for implementation.


Conclusion:
Experiment No. 8

AIM: Re-designing the architecture of B.E. Project, to improve on non functional


requirements (Quality Attributes)

Project Title:

List of Non-Functional Requirements:

List of Non-Functional Requirements considered in the Project & Why:


1) Old Architectural Model :
2) Old Architectural Model with NFR consideration

Conclusion:

You might also like