The Islamia University Bahawalpur

Slides:



Advertisements
Similar presentations
New Release Announcements and Product Roadmap Chris DiPierro, Director of Software Development April 9-11, 2014
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
1 Layers Data from IBM-Rational and Craig Larman’s text integrated into these slides. These are great references… Slides from these sources have been modified.
October 23, 2001 Software Design-Layering and Packaging1 Architecture: Layers and Packages.
March R McFadyen1 Architecture Architecture involves the set of significant decisions about the organization of a software system, decisions.
© Lethbridge/Laganière 2001 Chapter 9: Architecting and designing software1 Layers Data from IBM-Rational and Craig Larman…
Basic OOP Concepts and Terms
Understanding Metamodels. Outline Understanding metamodels Applying reference models Fundamental metamodel for describing software components Content.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
CMPT 370: Information Systems Design Instructor: Curtis Cartmill, Simon Fraser University – Summer 2003 Lecture Topic: Layered Architecture Class Exercise:
1 A Student Guide to Object- Orientated Development Chapter 9 Design.
Logical Architecture and UML Package Diagrams
March R McFadyen1 Figure 30.2 Layers in NextGen They only have three layers in this architecture Each layer is shown as a UML Package No separate.
Web Application Architecture: multi-tier (2-tier, 3-tier) & mvc
UNIT-V The MVC architecture and Struts Framework.
Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.
Chapter 13 Starting Design: Logical Architecture and UML Package Diagrams.
Architecture Of ASP.NET. What is ASP?  Server-side scripting technology.  Files containing HTML and scripting code.  Access via HTTP requests.  Scripting.
Logical Architecture and UML Package Diagrams 徐迎晓 复旦大学软件学院.
Meir Botner David Ben-David. Project Goal Build a messenger that allows a customer to communicate with a service provider for a fee.
Institute of Computer and Communication Network Engineering OFC/NFOEC, 6-10 March 2011, Los Angeles, CA Lessons Learned From Implementing a Path Computation.
An Introduction to Software Architecture
BTS430 Systems Analysis and Design using UML Domain Model Part 1—Finding Conceptual Classes.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
Architecting Web Services Unit – II – PART - III.
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
Chapter 17 GRASP: Designing Objects with Responsibilities. 1CS6359 Fall 2011 John Cole.
Selected Topics in Software Engineering - Distributed Software Development.
Systems Analysis and Design in a Changing World, 3rd Edition
Chapter 13 Logical Architecture and UML Package Diagrams 1CS6359 Fall 2012 John Cole.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Architectural Patterns Support Lecture. Software Architecture l Architecture is OVERLOADED System architecture Application architecture l Architecture.
What to remember from Chap 13 (Logical architecture)
Model View Controller MVC Web Software Architecture.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 system architecture 1 after designing to meet functional requirements, design the system.
How I spend my money Software architecture course Mohan, Maxim.
UML Package Diagrams. Package Diagrams UML Package Diagrams are often used to show the contents of components, which are often packages in the Java sense.
Slide 1 What the business needs  How to build it Functional requirements  + Nonfunctional requirements Performance System environment issues Problem.
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 JSP Application Models.
TK2023 Object-Oriented Software Engineering CHAPTER 8 LOGICAL ARCHITECTURE.
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
BTS430 Systems Analysis and Design using UML
Logical Architecture and UML Package Diagrams. The logical architecture is the large-scale organization of the software classes into packages, subsystems,
Deployment Diagram.
Architecture Review 10/11/2004
Recipes for Use With Thin Clients
Deployment Diagram.
Layers Data from IBM-Rational and Craig Larman’s text integrated into these slides. These are great references… Slides from these sources have been modified.
Architecting Web Services
Architecting Web Services
OO Methodology OO Architecture.
BTS530: Major Project Planning and Design
Chapter 13 Logical Architecture.
Figure 30.2 Layers in NextGen
Layers Data from IBM-Rational and Craig Larman’s text integrated into these slides. These are great references… Slides from these sources have been modified.
ARCH-1: Application Architecture made Simple
Software Architecture
Starting Design: Logical Architecture and UML Package Diagrams
Chapter 13 Logical Architecture.
Analysis models and design models
An Introduction to Software Architecture
Package Diagram.
Basic OOP Concepts and Terms
Design Yaodong Bi.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 6: Architectural Design
Design.
Logical Architecture & UML Package Diagrams
Presentation transcript:

The Islamia University Bahawalpur

031 052 Furqan Rustam Minhas Asif Presentation : OOSE Date:14/11/2016 Group Member’s Furqan Rustam 031 Minhas Asif 052

UML Package Diagram Design with layer’s Logical architecture Design with layer’s The Model-View Separation Principle Package Diagram

Logical Architecture What is an architecture? An architecture is a set of :- Selection of the structural elements. Interfaces by which the system is composed. Behavior

In software development Noun architecture Verb architecture As a noun, the architecture includes— System behavior. Responsibilities of systems and subsystems. Collaborations As a verb, the architecture is Investigation Design Architectural investigation or Architectural design.

Logical Architecture:- which describes the system in terms of : Layers Packages Major frameworks Classes Interfaces Subsystems.

Framework ASP. NET / IIS Layers Presentation Extensions Objects/Sub System Services Language Handler XHTML, XML,C++ Windows App Custom Properties Custom Task Scheduler Task Android App view Database Data Handler Framework ASP. NET / IIS Windows Services

Deployment Architecture:- Which describes the system in terms of: The allocation of processes to processing units. The network configuration.

Design with layer’s Note:- The Layers pattern relates to the logical architecture. A layer is a large-scale element, often composed of several packages or sub- systems. Objects/Sub System Language Handler XHTML, XML,C++ Layer Data Handler Database Note:- The purpose and number of layers varies across applications and application domains (information systems, operating systems, and so forth).

Example dependency Business Infrastructure Currency Controller GUI windows HTML, XML, XSLT, JavaScript, ... Presentation (AKA Interface, UI, View) Example Handles presentation layer requests Workflow Application (Process, App Controller) Handles application layer requests Implementation of domain rules Domain services Domain(s) (Business Services, Model) dependency Business Infrastructure Currency Controller Technical Services (High-level Technical Services) Persistence, Security Data structures, threads, math, file, DB, and network I/O Technical Services (AKA Technical Infrastructure)

The Model-View Separation Principle In this context: Model is a synonym for the Domain layer of objects. View is a synonym for presentation objects. The Model-View Separation principle states that :- Model (domain) objects should not have direct knowledge of view (presentation) objects, at least as view objects.

Model-View Separation and "Upward" Communication Presentation ProcessSale Frame UIF acade Domain Register Sale

The motivation for Model-View Separation includes: To allow separate development of the model and user interface layers. To minimize the impact of requirements changes in the interface upon the domain layer. To allow execution of the model layer independent of the user interface layer, such as in a message-processing or batch-mode system.

Package Diagram Groups of “basic elements”, e.g., classes or use cases Can contain other packages, creating hierarch Represented as file folders

- - - - - - - > or - - - - - - -> Package & Relations • Dependencies • Implementations • Merges Dependencies: Package A depends on package B if A contains a class which depends on a class in B. • Graphic representation: - - - - - - - > or - - - - - - -> <<use>>

Example of Dependencies: Typical 3-tier application (sketch):

Implementations: Meaningful if multiple variants are present.

Merge: A package merge indicates that the contents of the two packages are to be combined.

All rights reserved © DrRazorX