2017 ch720 final term presentatiom
•Download as PPTX, PDF•
0 likes•5 views
The document discusses system breakdown structures, which divide complex systems into simpler, manageable units through a hierarchical structure. A system breakdown structure separates a system into tasks and sub-tasks to improve communication. Examples provided breakdown aircraft systems, space transport systems, and house construction systems into levels of components and subcomponents.
Report
Share
Report
Share
Recommended
WORK BREAKDOWN STRUCTURE, JOB LAYOUT & LINE OF BALANCE
The document discusses the work breakdown structure (WBS), which is a process that breaks down a construction project into identifiable major systems, sub-systems, and discrete activities. The WBS identifies the functional elements of a project and their relationships. Breaking a project into its components using a WBS helps with preparing the project network, planning, and scheduling activities. An example of breaking down the concreting work for a roof slab into its elements is given.
Design
The document discusses process design and system architecture. It covers:
1) Process design includes both logical and physical design. Logical design models system inputs, outputs, and data flows. Physical design specifies actual system inputs, outputs, storage, processing, and control requirements.
2) Common UML diagrams used in process design are discussed, including class, use case, sequence, state, activity, and component diagrams. These diagrams model different aspects of a system from various perspectives.
3) A wireless sensor network architecture is presented involving sensor nodes communicating data via radio to a base station, which then transmits the aggregated data to other networks.
Conceptually, system concept diagrams describe the interaction of a .docx
Conceptually, system concept diagrams describe the interaction of a system with its environment. Practically, system context diagrams are recommended for the following phases of IT problem solving:
PROJECT PLANNING -- to visually describe initial project scope to system owners, system users, and the project team. This serves as a "visual contract" to manage scope through the remainder of the project.
SYSTEM ANALYSIS -- to visually describe requirements for SYSTEM INTERFACES to system users and the project team.
SYSTEM DESIGN -- to visually describe technology constraints and decisions for all system interfaces for the benefit of system users, system designers, and system builders.
SYSTEM IMPLEMENTATION -- to visually describe conversion requirements for the project team and system owners (not covered in class; and hence, not required in this assignment. This is included here only as a placeholder for course improvement).
ASSIGNMENT
- Using the UML Context Diagram Profile, develop a full SET of system context diagrams
Your system, and hence its context diagrams, must exhibit at least two of the four types of integrating interfaces described and demonstrated in class:
user interfaces (also known as human-computer interfaces (HCI) and the user experience (UX)
system interfaces (to and from legacy systems)
database interfaces (to databases that may be used or update, but whose table structures are considered out of scope)
control interfaces (to machines, appliances, or devices -- for "real time systems")
Your system must demonstrate all four types if they are applicable to your problem domain.
.
Object oriented sad-5 part ii
This document discusses component, deployment, persistent and UI models in object oriented design. It provides details on component diagrams, describing how they represent high-level reusable parts of a system and their inter-relationships. Deployment diagrams depict the physical resources in a system including nodes, components, and connections. Persistent modeling involves mapping object-oriented class diagrams to relational database schemas. User interface design should match user skills/experience and consider human factors like memory, preferences and preventing errors.
3.2 The design model & Architectural design.ppt
The document discusses the design model and architectural design process. The design model has two dimensions - the process dimension outlines the evolution of the design tasks, while the abstraction dimension represents the level of detail. The design model elements include data design, architectural design, interface design, component design, and deployment design. The architectural design process involves representing the system context, defining archetypes, refining the architecture into components, and describing system instantiations.
7.1-Midterm-review-and-examplessssssss.pdf
The document provides an overview of software architecture concepts including:
1. Definitions of software architecture and its key elements like components, connectors, and views at different levels of abstraction.
2. Common architectural styles like layered architectures, client-server, pipes and filters are described.
3. Methodologies for developing architectures including conceptual, execution, and implementation views are outlined.
New phase ii-2010
The document discusses the design phase of software development. It explains that design allows engineers to model the system or product to be built based on requirements. Good design establishes quality, is understandable, easy to implement, reliable, and allows for evolution. Poor design can result in an unstable system that is difficult to maintain and fails easily. The design process involves conceptual and technical design phases with top-level and detailed design. The output is a software design document containing modules, interfaces, data structures, and classes.
UNIT 3 SE.pptx
The document discusses software design concepts and principles including:
1. Software design is an iterative process that translates requirements into a system blueprint. Initial designs have a high level of abstraction that is refined through iterations.
2. Key design concepts include abstraction, modularity, architecture, patterns, and information hiding. Architectural styles include data-centered, data flow, call-and-return, and object-oriented.
3. The design process involves representing the system context, defining archetypes, refining the architecture into components, and describing system instantiations. Architectural mapping uses data flow diagrams to guide the design structure.
Recommended
WORK BREAKDOWN STRUCTURE, JOB LAYOUT & LINE OF BALANCE
The document discusses the work breakdown structure (WBS), which is a process that breaks down a construction project into identifiable major systems, sub-systems, and discrete activities. The WBS identifies the functional elements of a project and their relationships. Breaking a project into its components using a WBS helps with preparing the project network, planning, and scheduling activities. An example of breaking down the concreting work for a roof slab into its elements is given.
Design
The document discusses process design and system architecture. It covers:
1) Process design includes both logical and physical design. Logical design models system inputs, outputs, and data flows. Physical design specifies actual system inputs, outputs, storage, processing, and control requirements.
2) Common UML diagrams used in process design are discussed, including class, use case, sequence, state, activity, and component diagrams. These diagrams model different aspects of a system from various perspectives.
3) A wireless sensor network architecture is presented involving sensor nodes communicating data via radio to a base station, which then transmits the aggregated data to other networks.
Conceptually, system concept diagrams describe the interaction of a .docx
Conceptually, system concept diagrams describe the interaction of a system with its environment. Practically, system context diagrams are recommended for the following phases of IT problem solving:
PROJECT PLANNING -- to visually describe initial project scope to system owners, system users, and the project team. This serves as a "visual contract" to manage scope through the remainder of the project.
SYSTEM ANALYSIS -- to visually describe requirements for SYSTEM INTERFACES to system users and the project team.
SYSTEM DESIGN -- to visually describe technology constraints and decisions for all system interfaces for the benefit of system users, system designers, and system builders.
SYSTEM IMPLEMENTATION -- to visually describe conversion requirements for the project team and system owners (not covered in class; and hence, not required in this assignment. This is included here only as a placeholder for course improvement).
ASSIGNMENT
- Using the UML Context Diagram Profile, develop a full SET of system context diagrams
Your system, and hence its context diagrams, must exhibit at least two of the four types of integrating interfaces described and demonstrated in class:
user interfaces (also known as human-computer interfaces (HCI) and the user experience (UX)
system interfaces (to and from legacy systems)
database interfaces (to databases that may be used or update, but whose table structures are considered out of scope)
control interfaces (to machines, appliances, or devices -- for "real time systems")
Your system must demonstrate all four types if they are applicable to your problem domain.
.
Object oriented sad-5 part ii
This document discusses component, deployment, persistent and UI models in object oriented design. It provides details on component diagrams, describing how they represent high-level reusable parts of a system and their inter-relationships. Deployment diagrams depict the physical resources in a system including nodes, components, and connections. Persistent modeling involves mapping object-oriented class diagrams to relational database schemas. User interface design should match user skills/experience and consider human factors like memory, preferences and preventing errors.
3.2 The design model & Architectural design.ppt
The document discusses the design model and architectural design process. The design model has two dimensions - the process dimension outlines the evolution of the design tasks, while the abstraction dimension represents the level of detail. The design model elements include data design, architectural design, interface design, component design, and deployment design. The architectural design process involves representing the system context, defining archetypes, refining the architecture into components, and describing system instantiations.
7.1-Midterm-review-and-examplessssssss.pdf
The document provides an overview of software architecture concepts including:
1. Definitions of software architecture and its key elements like components, connectors, and views at different levels of abstraction.
2. Common architectural styles like layered architectures, client-server, pipes and filters are described.
3. Methodologies for developing architectures including conceptual, execution, and implementation views are outlined.
New phase ii-2010
The document discusses the design phase of software development. It explains that design allows engineers to model the system or product to be built based on requirements. Good design establishes quality, is understandable, easy to implement, reliable, and allows for evolution. Poor design can result in an unstable system that is difficult to maintain and fails easily. The design process involves conceptual and technical design phases with top-level and detailed design. The output is a software design document containing modules, interfaces, data structures, and classes.
UNIT 3 SE.pptx
The document discusses software design concepts and principles including:
1. Software design is an iterative process that translates requirements into a system blueprint. Initial designs have a high level of abstraction that is refined through iterations.
2. Key design concepts include abstraction, modularity, architecture, patterns, and information hiding. Architectural styles include data-centered, data flow, call-and-return, and object-oriented.
3. The design process involves representing the system context, defining archetypes, refining the architecture into components, and describing system instantiations. Architectural mapping uses data flow diagrams to guide the design structure.
Logical design vs physical design
The document discusses the physical and logical design aspects of system design. Physical design involves graphical representation of internal and external system entities and data flows. It includes user interface, data, and process design to specify how data is input, processed and output. Logical design provides an abstract representation of system processes and data flows using models and diagrams to describe what tasks the system performs without specifying how.
Practising EA with BSS transformations
The document outlines the phases and steps to start practising enterprise architecture. It involves first defining the as-is architecture, including business functions, processes, information systems, data, and technology. The second iteration defines the to-be architecture according to reference models and principles, including requirements, stakeholders, vision, and target architectures for business, information, and technology with gap analyses. The architecture is then implemented through change scenarios, transition architecture, projects, and governance.
DDD - 4 - Domain Driven Design_ Architectural patterns.pdf
In this fourth presentation on domain-driven design, we present the architectural patterns that are most commonly used (layered architecture, hexagonal architecture and CQRS), describing their characteristics and suggesting when and how to use them
Customer Data Integration Architecture Gudelinbes
This document provides a summary of the current MCV database architecture, outlines key issues ("pain points"), and proposes a re-architecture. The current system lacks distinct ETL processes and has data integrity issues. The proposed re-architecture includes: external source/application/ETL/outbound data layers; revisiting the data model; separating ETL functions from application code; using the Oracle data dictionary; and addressing security, scalability and potential ETL tool migration. Details of each new layer and appendixes on ETL and data integrity are provided. The intended audience is the project team to review compliance and use as a design roadmap.
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
This document outlines key concepts in software design, including:
- The three types of design activities are external, architectural, and detailed design.
- Fundamental design concepts include abstraction, information hiding, structure, modularity, concurrency, verification, and aesthetics.
- Modules should have loose coupling and high cohesion. Design notations include data flow diagrams and structure charts.
Designmethodology1
The document discusses digital design methodology at different levels of abstraction: gate level, register level, and processor level. It describes how a digital design can be represented behaviorally, structurally, and through physical implementation. The key levels in computer design are the processor level (architecture), register transfer level, and gate level. Lower levels have more detail but faster speeds, while higher levels have less detail but allow more complex functions. Computer-aided design tools like simulators and synthesizers help address complexity through iterative design processes.
Object oriented sad-5 part i
The document discusses object-oriented design and its role in software development. It describes how design builds upon analysis to provide implementation details. Key aspects of object-oriented design include defining a multilayered architecture, specifying subsystems and components, describing classes and objects, and defining communication mechanisms. The input to design comes from artifacts created in analysis like use cases and class models. The output of design serves as a blueprint to guide construction.
AGADUC Towards A More Precise Presentation Of Functional Requirement In Use ...
This document describes AGADUC, a process for systematically generating activity diagrams from use case descriptions to provide a more precise presentation of functional requirements. AGADUC addresses limitations in traditional use case modeling by generating diagrams that depict workflows embedded in use case descriptions. The process involves mapping structured use case descriptions to unified use case activity diagrams (UCADs) that integrate use case and activity diagram notations. A case study on a library system demonstrates how AGADUC overcomes ambiguities in traditional use case models by automatically generating consistent and understandable UCADs from use case descriptions.
Chapter 7 Design Architecture and Methodology1.docx
Chapter 7:
Design: Architecture and Methodology
1
Design Topics Covered
Architectural vs. detailed design
“Common” architectural styles, tactics, and reference architectures
Basic techniques for detailed design
Basic issues with user-interface design
2
Design
Starts mostly from/with requirements (evolving mostly from functionalities and other non-functional characteristics).
How is the software solution going to be structured?
What are the main components—(functional comp)?
Often directly from requirements’ functionalities
(use cases).
How are these components related?
Possibly re-organize the components (composition/decomposition).
Two main levels of design:
Architectural (high level)
Detailed design
How should we depict design—notation/language?
3
Relationship between Architecture and Design
Detailed Design
Comes from
Requirements &
Architecture
4
Software Architecture
Structure(s) of the solution, comprising:
Major software elements
Their externally visible properties
Relationships among elements
Every software system has an architecture.
May have multiple structures!
Multiple ways of organizing elements, depending on the perspective
External properties of components (and modules)
Component (module) interfaces
Component (module) interactions, rather than internals of components and modules
5
Views and Viewpoints
View – representation of a system structure
4+1 views (by Krutchen)
Logical (OO decomposition – key abstractions)
Process (run-time, concurrency/distribution of functions)
Subsystem decomposition
Physical architecture
+1: use cases
Other classification (Bass, Clements, Kazman)
Module
Run-time
Allocation (mapping to development environment)
Different views for different people
6
Architectural Styles/Patterns
Pipes and filters
Event driven
Client-server
Model-view-controller (MVC)
Layered
Database centric
Three tier
We discuss architectural styles/patterns as
“reusable” starting point for design activities.
7
Pipe-Filter Architecture Style
The high-level design solution is decomposed into two “generic” parts (filters and pipes):
Filter is a service that transforms a stream of input data into a stream of output data.
Pipe is a mechanism or conduit through which the data flows from one filter to another.
Input
time cards
Prepare for
check processing
Process checks
Problems that require batch file processing seem to fit this architecture: e.g., payroll, compilers, month-end accounting.
** Reminds one of DFD without the data store or source sink.**
8
Event Driven (Real Time)
The high-level design solution is based on an event dispatcher, which manages events and the functionalities that depend on those events. These have the following characteristics:
Events may be a simple notification or may include associated data.
Events may be prioritized or be based on constraints such as time.
Events may require synchronous or asynchronous processing.
Events may be “registered” ...
Software_Archi-1.ppt
The document discusses software architecture, including:
1. Definitions of software architecture and how it is influenced.
2. Common sections of a software architecture document such as introduction, views, goals and quality.
3. Architectural patterns and views including model-view-controller, layered patterns, and the "4+1" views of logical, process, deployment, and implementation.
4. How architecture addresses concerns like complexity, communication, and early decisions.
Design concepts and principles
The document describes key components of software design including data design, architectural design, interface design, and procedural design. It discusses the goals of the design process which are to implement requirements, create an understandable guide for code generation and testing, and address implementation from data, functional, and behavioral perspectives. The document also covers concepts like abstraction, refinement, modularity, program structure, data structures, software procedures, information hiding, and cohesion and coupling.
requirement analysis of software engineering
The document describes the system design for an engineering college student department placement system. It discusses design issues such as security, performance, availability and error handling. It then covers various design patterns that could be applied like MVC, repository pattern, and strategy pattern. It includes class and database diagrams. It decomposes the system into subsystems for user account management, placement, complaints, etc. It provides a deployment diagram and discusses the overall 3-tier system architecture with separate presentation, business logic and data layers.
Pattern oriented architecture for web based architecture
This document discusses web application architecture and design patterns. It describes a three-layer architecture with presentation, application, and data layers. For the presentation layer, forms are commonly used to structure user interfaces. The application layer focuses on business processes and components. The data access layer exposes database data. Popular design patterns like MVC, PAC, and others are explained as ways to achieve separation of concerns and improve maintainability. MVC divides the presentation layer into separate controller and view components. PAC defines a hierarchical structure of cooperating agents with presentation, abstraction, and control components.
System Design For Computer Architecture
Computer architecture is a specification describing how hardware and software technologies interact to create a computer platform or system. System design – This includes all the hardware parts, such as CPU, data processors, multiprocessors, memory controllers and direct memory access.
Cisco data center
The Cisco Unified Computing System (UCS) consolidates many separate data center elements like networking, storage, and servers into a single unified system using converged network adapters and fabric interconnects. The UCS Manager allows for unified management of physical and virtual infrastructure. Service profiles define hardware configurations that can be rapidly applied to server blades. Role-based access controls in the UCS Manager separate administrator access for networking, servers, storage and other roles.
Unit-3.doc
Software design is an iterative process through which requirements are translated into a blueprint for constructing the software.
ROCHALOPES_PAPER
IDM-CIC and IDM-View are concurrent engineering tools developed by CNES for satellite design. IDM-CIC allows users to easily build engineering models with equipment geometry, mass, and power properties to generate mass and power budgets. IDM-View provides an intuitive 3D interface to visualize and interact with models created in IDM-CIC. Features include real-time animation, shadows, and attitude control configurators. These tools are useful for both large satellite projects and CubeSat design due to their simplicity and ability to import pre-defined component catalogs.
MULTIOBJECTIVE OPTIMIZATION AND QUANTITATIVE TRADE-OFF ANALYSIS IN XEROGRAPHI...
A complex engineering system such as a xerographic marking engine is an aggregate of interacting subsystems that are coupled through a large number of constraints and design variables. The traditional way of designing these systems is to decouple the overall design into smaller subsystems and assign teams to work on these subsystems. This approach is critical to making the project manageable and enabling concurrent development. However, if the goal is to design systems that can deliver best possible performance, i.e. if the performance limits are being pushed to the extreme, characterizing the interactions becomes critical.
Multiobjective optimization is a design methodology that addresses the issue of designing large systems where the goal is to simultaneously optimize a finite number of performance criteria that come from one or more disciplines and are coupled through a set of design variables and constraints. This approach to design makes explicit and quantitative the inherent trade-offs that need to be made in doing coupled system design. It also enables the determination of the attainable limits of performance from a given system.
This paper will discuss the multiobjective optimization methodology and optimal methods of performing quantitative trade-off analysis. These design methods will be applied to problems from the xerographic design domain and results will be presented.
Software architecture
The document introduces software architecture and describes key aspects of documenting a software architecture. It defines software architecture as the structure of components and relationships in a system. It outlines the 4+1 views model for documenting architecture, including use case, logical, process, deployment, and code views. It provides examples of architectural patterns like model-view-controller and layered patterns. It describes how a software architecture document outlines architectural goals, constraints, and quality attributes.
Third AssignmentDescribe in 100 – 200 words an application with .docx
Third Assignment
Describe in 100 – 200 words an application with which you are familiar. This should be an application with which other students and the course instructor are likely to be familiar. An example would be Microsoft Word. Then, select one of the architectural design styles given in the presentation on Architectural Design. Explain why this style is appropriate for the application you described. Then apply this style to the application and explain the result in enough detail that your fellow students are likely to understand.
Organization of your submission
Third Assignment
Your name
Submission Date
Application Description
Style you have selected
Why this style is appropriate for this application
The application’s architecture using this style
Explanation of this architecture (show how some common tasks for this application might be performed using this architecture)
Grading Rubric
Criterion
Points
Application description is well-organized
5
Style choice is one of the styles described
2
Style choice is effectively justified
8
Presented architecture uses the selected style
3
Presented architecture is complete
4
Architecture is described clearly
8
Chapter 7:
Design: Architecture and Methodology
1
Design Topics Covered
Architectural vs. detailed design
“Common” architectural styles, tactics, and reference architectures
Basic techniques for detailed design
Basic issues with user-interface design
2
Design
Starts mostly from/with requirements (evolving mostly from functionalities and other non-functional characteristics).
How is the software solution going to be structured?
What are the main components—(functional comp)?
Often directly from requirements’ functionalities
(use cases).
How are these components related?
Possibly re-organize the components (composition/decomposition).
Two main levels of design:
Architectural (high level)
Detailed design
How should we depict design—notation/language?
3
Relationship between Architecture and Design
Detailed Design
Comes from
Requirements &
Architecture
4
Software Architecture
Structure(s) of the solution, comprising:
Major software elements
Their externally visible properties
Relationships among elements
Every software system has an architecture.
May have multiple structures!
Multiple ways of organizing elements, depending on the perspective
External properties of components (and modules)
Component (module) interfaces
Component (module) interactions, rather than internals of components and modules
5
Views and Viewpoints
View – representation of a system structure
4+1 views (by Krutchen)
Logical (OO decomposition – key abstractions)
Process (run-time, concurrency/distribution of functions)
Subsystem decomposition
Physical architecture
+1: use cases
Other classification (Bass, Clements, Kazman)
Module
Run-time
Allocation (mapping to development environment)
Different views for different people
6
Architectural Styles/Patterns
Pipes a.
Advanced control scheme of doubly fed induction generator for wind turbine us...
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Comparative analysis between traditional aquaponics and reconstructed aquapon...
The aquaponic system of planting is a method that does not require soil usage. It is a method that only needs water, fish, lava rocks (a substitute for soil), and plants. Aquaponic systems are sustainable and environmentally friendly. Its use not only helps to plant in small spaces but also helps reduce artificial chemical use and minimizes excess water use, as aquaponics consumes 90% less water than soil-based gardening. The study applied a descriptive and experimental design to assess and compare conventional and reconstructed aquaponic methods for reproducing tomatoes. The researchers created an observation checklist to determine the significant factors of the study. The study aims to determine the significant difference between traditional aquaponics and reconstructed aquaponics systems propagating tomatoes in terms of height, weight, girth, and number of fruits. The reconstructed aquaponics system’s higher growth yield results in a much more nourished crop than the traditional aquaponics system. It is superior in its number of fruits, height, weight, and girth measurement. Moreover, the reconstructed aquaponics system is proven to eliminate all the hindrances present in the traditional aquaponics system, which are overcrowding of fish, algae growth, pest problems, contaminated water, and dead fish.
More Related Content
Similar to 2017 ch720 final term presentatiom
Logical design vs physical design
The document discusses the physical and logical design aspects of system design. Physical design involves graphical representation of internal and external system entities and data flows. It includes user interface, data, and process design to specify how data is input, processed and output. Logical design provides an abstract representation of system processes and data flows using models and diagrams to describe what tasks the system performs without specifying how.
Practising EA with BSS transformations
The document outlines the phases and steps to start practising enterprise architecture. It involves first defining the as-is architecture, including business functions, processes, information systems, data, and technology. The second iteration defines the to-be architecture according to reference models and principles, including requirements, stakeholders, vision, and target architectures for business, information, and technology with gap analyses. The architecture is then implemented through change scenarios, transition architecture, projects, and governance.
DDD - 4 - Domain Driven Design_ Architectural patterns.pdf
In this fourth presentation on domain-driven design, we present the architectural patterns that are most commonly used (layered architecture, hexagonal architecture and CQRS), describing their characteristics and suggesting when and how to use them
Customer Data Integration Architecture Gudelinbes
This document provides a summary of the current MCV database architecture, outlines key issues ("pain points"), and proposes a re-architecture. The current system lacks distinct ETL processes and has data integrity issues. The proposed re-architecture includes: external source/application/ETL/outbound data layers; revisiting the data model; separating ETL functions from application code; using the Oracle data dictionary; and addressing security, scalability and potential ETL tool migration. Details of each new layer and appendixes on ETL and data integrity are provided. The intended audience is the project team to review compliance and use as a design roadmap.
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
This document outlines key concepts in software design, including:
- The three types of design activities are external, architectural, and detailed design.
- Fundamental design concepts include abstraction, information hiding, structure, modularity, concurrency, verification, and aesthetics.
- Modules should have loose coupling and high cohesion. Design notations include data flow diagrams and structure charts.
Designmethodology1
The document discusses digital design methodology at different levels of abstraction: gate level, register level, and processor level. It describes how a digital design can be represented behaviorally, structurally, and through physical implementation. The key levels in computer design are the processor level (architecture), register transfer level, and gate level. Lower levels have more detail but faster speeds, while higher levels have less detail but allow more complex functions. Computer-aided design tools like simulators and synthesizers help address complexity through iterative design processes.
Object oriented sad-5 part i
The document discusses object-oriented design and its role in software development. It describes how design builds upon analysis to provide implementation details. Key aspects of object-oriented design include defining a multilayered architecture, specifying subsystems and components, describing classes and objects, and defining communication mechanisms. The input to design comes from artifacts created in analysis like use cases and class models. The output of design serves as a blueprint to guide construction.
AGADUC Towards A More Precise Presentation Of Functional Requirement In Use ...
This document describes AGADUC, a process for systematically generating activity diagrams from use case descriptions to provide a more precise presentation of functional requirements. AGADUC addresses limitations in traditional use case modeling by generating diagrams that depict workflows embedded in use case descriptions. The process involves mapping structured use case descriptions to unified use case activity diagrams (UCADs) that integrate use case and activity diagram notations. A case study on a library system demonstrates how AGADUC overcomes ambiguities in traditional use case models by automatically generating consistent and understandable UCADs from use case descriptions.
Chapter 7 Design Architecture and Methodology1.docx
Chapter 7:
Design: Architecture and Methodology
1
Design Topics Covered
Architectural vs. detailed design
“Common” architectural styles, tactics, and reference architectures
Basic techniques for detailed design
Basic issues with user-interface design
2
Design
Starts mostly from/with requirements (evolving mostly from functionalities and other non-functional characteristics).
How is the software solution going to be structured?
What are the main components—(functional comp)?
Often directly from requirements’ functionalities
(use cases).
How are these components related?
Possibly re-organize the components (composition/decomposition).
Two main levels of design:
Architectural (high level)
Detailed design
How should we depict design—notation/language?
3
Relationship between Architecture and Design
Detailed Design
Comes from
Requirements &
Architecture
4
Software Architecture
Structure(s) of the solution, comprising:
Major software elements
Their externally visible properties
Relationships among elements
Every software system has an architecture.
May have multiple structures!
Multiple ways of organizing elements, depending on the perspective
External properties of components (and modules)
Component (module) interfaces
Component (module) interactions, rather than internals of components and modules
5
Views and Viewpoints
View – representation of a system structure
4+1 views (by Krutchen)
Logical (OO decomposition – key abstractions)
Process (run-time, concurrency/distribution of functions)
Subsystem decomposition
Physical architecture
+1: use cases
Other classification (Bass, Clements, Kazman)
Module
Run-time
Allocation (mapping to development environment)
Different views for different people
6
Architectural Styles/Patterns
Pipes and filters
Event driven
Client-server
Model-view-controller (MVC)
Layered
Database centric
Three tier
We discuss architectural styles/patterns as
“reusable” starting point for design activities.
7
Pipe-Filter Architecture Style
The high-level design solution is decomposed into two “generic” parts (filters and pipes):
Filter is a service that transforms a stream of input data into a stream of output data.
Pipe is a mechanism or conduit through which the data flows from one filter to another.
Input
time cards
Prepare for
check processing
Process checks
Problems that require batch file processing seem to fit this architecture: e.g., payroll, compilers, month-end accounting.
** Reminds one of DFD without the data store or source sink.**
8
Event Driven (Real Time)
The high-level design solution is based on an event dispatcher, which manages events and the functionalities that depend on those events. These have the following characteristics:
Events may be a simple notification or may include associated data.
Events may be prioritized or be based on constraints such as time.
Events may require synchronous or asynchronous processing.
Events may be “registered” ...
Software_Archi-1.ppt
The document discusses software architecture, including:
1. Definitions of software architecture and how it is influenced.
2. Common sections of a software architecture document such as introduction, views, goals and quality.
3. Architectural patterns and views including model-view-controller, layered patterns, and the "4+1" views of logical, process, deployment, and implementation.
4. How architecture addresses concerns like complexity, communication, and early decisions.
Design concepts and principles
The document describes key components of software design including data design, architectural design, interface design, and procedural design. It discusses the goals of the design process which are to implement requirements, create an understandable guide for code generation and testing, and address implementation from data, functional, and behavioral perspectives. The document also covers concepts like abstraction, refinement, modularity, program structure, data structures, software procedures, information hiding, and cohesion and coupling.
requirement analysis of software engineering
The document describes the system design for an engineering college student department placement system. It discusses design issues such as security, performance, availability and error handling. It then covers various design patterns that could be applied like MVC, repository pattern, and strategy pattern. It includes class and database diagrams. It decomposes the system into subsystems for user account management, placement, complaints, etc. It provides a deployment diagram and discusses the overall 3-tier system architecture with separate presentation, business logic and data layers.
Pattern oriented architecture for web based architecture
This document discusses web application architecture and design patterns. It describes a three-layer architecture with presentation, application, and data layers. For the presentation layer, forms are commonly used to structure user interfaces. The application layer focuses on business processes and components. The data access layer exposes database data. Popular design patterns like MVC, PAC, and others are explained as ways to achieve separation of concerns and improve maintainability. MVC divides the presentation layer into separate controller and view components. PAC defines a hierarchical structure of cooperating agents with presentation, abstraction, and control components.
System Design For Computer Architecture
Computer architecture is a specification describing how hardware and software technologies interact to create a computer platform or system. System design – This includes all the hardware parts, such as CPU, data processors, multiprocessors, memory controllers and direct memory access.
Cisco data center
The Cisco Unified Computing System (UCS) consolidates many separate data center elements like networking, storage, and servers into a single unified system using converged network adapters and fabric interconnects. The UCS Manager allows for unified management of physical and virtual infrastructure. Service profiles define hardware configurations that can be rapidly applied to server blades. Role-based access controls in the UCS Manager separate administrator access for networking, servers, storage and other roles.
Unit-3.doc
Software design is an iterative process through which requirements are translated into a blueprint for constructing the software.
ROCHALOPES_PAPER
IDM-CIC and IDM-View are concurrent engineering tools developed by CNES for satellite design. IDM-CIC allows users to easily build engineering models with equipment geometry, mass, and power properties to generate mass and power budgets. IDM-View provides an intuitive 3D interface to visualize and interact with models created in IDM-CIC. Features include real-time animation, shadows, and attitude control configurators. These tools are useful for both large satellite projects and CubeSat design due to their simplicity and ability to import pre-defined component catalogs.
MULTIOBJECTIVE OPTIMIZATION AND QUANTITATIVE TRADE-OFF ANALYSIS IN XEROGRAPHI...
A complex engineering system such as a xerographic marking engine is an aggregate of interacting subsystems that are coupled through a large number of constraints and design variables. The traditional way of designing these systems is to decouple the overall design into smaller subsystems and assign teams to work on these subsystems. This approach is critical to making the project manageable and enabling concurrent development. However, if the goal is to design systems that can deliver best possible performance, i.e. if the performance limits are being pushed to the extreme, characterizing the interactions becomes critical.
Multiobjective optimization is a design methodology that addresses the issue of designing large systems where the goal is to simultaneously optimize a finite number of performance criteria that come from one or more disciplines and are coupled through a set of design variables and constraints. This approach to design makes explicit and quantitative the inherent trade-offs that need to be made in doing coupled system design. It also enables the determination of the attainable limits of performance from a given system.
This paper will discuss the multiobjective optimization methodology and optimal methods of performing quantitative trade-off analysis. These design methods will be applied to problems from the xerographic design domain and results will be presented.
Software architecture
The document introduces software architecture and describes key aspects of documenting a software architecture. It defines software architecture as the structure of components and relationships in a system. It outlines the 4+1 views model for documenting architecture, including use case, logical, process, deployment, and code views. It provides examples of architectural patterns like model-view-controller and layered patterns. It describes how a software architecture document outlines architectural goals, constraints, and quality attributes.
Third AssignmentDescribe in 100 – 200 words an application with .docx
Third Assignment
Describe in 100 – 200 words an application with which you are familiar. This should be an application with which other students and the course instructor are likely to be familiar. An example would be Microsoft Word. Then, select one of the architectural design styles given in the presentation on Architectural Design. Explain why this style is appropriate for the application you described. Then apply this style to the application and explain the result in enough detail that your fellow students are likely to understand.
Organization of your submission
Third Assignment
Your name
Submission Date
Application Description
Style you have selected
Why this style is appropriate for this application
The application’s architecture using this style
Explanation of this architecture (show how some common tasks for this application might be performed using this architecture)
Grading Rubric
Criterion
Points
Application description is well-organized
5
Style choice is one of the styles described
2
Style choice is effectively justified
8
Presented architecture uses the selected style
3
Presented architecture is complete
4
Architecture is described clearly
8
Chapter 7:
Design: Architecture and Methodology
1
Design Topics Covered
Architectural vs. detailed design
“Common” architectural styles, tactics, and reference architectures
Basic techniques for detailed design
Basic issues with user-interface design
2
Design
Starts mostly from/with requirements (evolving mostly from functionalities and other non-functional characteristics).
How is the software solution going to be structured?
What are the main components—(functional comp)?
Often directly from requirements’ functionalities
(use cases).
How are these components related?
Possibly re-organize the components (composition/decomposition).
Two main levels of design:
Architectural (high level)
Detailed design
How should we depict design—notation/language?
3
Relationship between Architecture and Design
Detailed Design
Comes from
Requirements &
Architecture
4
Software Architecture
Structure(s) of the solution, comprising:
Major software elements
Their externally visible properties
Relationships among elements
Every software system has an architecture.
May have multiple structures!
Multiple ways of organizing elements, depending on the perspective
External properties of components (and modules)
Component (module) interfaces
Component (module) interactions, rather than internals of components and modules
5
Views and Viewpoints
View – representation of a system structure
4+1 views (by Krutchen)
Logical (OO decomposition – key abstractions)
Process (run-time, concurrency/distribution of functions)
Subsystem decomposition
Physical architecture
+1: use cases
Other classification (Bass, Clements, Kazman)
Module
Run-time
Allocation (mapping to development environment)
Different views for different people
6
Architectural Styles/Patterns
Pipes a.
Similar to 2017 ch720 final term presentatiom (20)
DDD - 4 - Domain Driven Design_ Architectural patterns.pdf
DDD - 4 - Domain Driven Design_ Architectural patterns.pdf
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
UNIT 3-DEMONSTRATING A COMPREHENSIVE UNDERSTANDING OF SOFTWARE DESIGN.pptx
AGADUC Towards A More Precise Presentation Of Functional Requirement In Use ...
AGADUC Towards A More Precise Presentation Of Functional Requirement In Use ...
Chapter 7 Design Architecture and Methodology1.docx
Chapter 7 Design Architecture and Methodology1.docx
Pattern oriented architecture for web based architecture
Pattern oriented architecture for web based architecture
MULTIOBJECTIVE OPTIMIZATION AND QUANTITATIVE TRADE-OFF ANALYSIS IN XEROGRAPHI...
MULTIOBJECTIVE OPTIMIZATION AND QUANTITATIVE TRADE-OFF ANALYSIS IN XEROGRAPHI...
Third AssignmentDescribe in 100 – 200 words an application with .docx
Third AssignmentDescribe in 100 – 200 words an application with .docx
Recently uploaded
Advanced control scheme of doubly fed induction generator for wind turbine us...
This paper describes a speed control device for generating electrical energy on an electricity network based on the doubly fed induction generator (DFIG) used for wind power conversion systems. At first, a double-fed induction generator model was constructed. A control law is formulated to govern the flow of energy between the stator of a DFIG and the energy network using three types of controllers: proportional integral (PI), sliding mode controller (SMC) and second order sliding mode controller (SOSMC). Their different results in terms of power reference tracking, reaction to unexpected speed fluctuations, sensitivity to perturbations, and resilience against machine parameter alterations are compared. MATLAB/Simulink was used to conduct the simulations for the preceding study. Multiple simulations have shown very satisfying results, and the investigations demonstrate the efficacy and power-enhancing capabilities of the suggested control system.
Comparative analysis between traditional aquaponics and reconstructed aquapon...
The aquaponic system of planting is a method that does not require soil usage. It is a method that only needs water, fish, lava rocks (a substitute for soil), and plants. Aquaponic systems are sustainable and environmentally friendly. Its use not only helps to plant in small spaces but also helps reduce artificial chemical use and minimizes excess water use, as aquaponics consumes 90% less water than soil-based gardening. The study applied a descriptive and experimental design to assess and compare conventional and reconstructed aquaponic methods for reproducing tomatoes. The researchers created an observation checklist to determine the significant factors of the study. The study aims to determine the significant difference between traditional aquaponics and reconstructed aquaponics systems propagating tomatoes in terms of height, weight, girth, and number of fruits. The reconstructed aquaponics system’s higher growth yield results in a much more nourished crop than the traditional aquaponics system. It is superior in its number of fruits, height, weight, and girth measurement. Moreover, the reconstructed aquaponics system is proven to eliminate all the hindrances present in the traditional aquaponics system, which are overcrowding of fish, algae growth, pest problems, contaminated water, and dead fish.
哪里办理(csu毕业证书)查尔斯特大学毕业证硕士学历原版一模一样
原版一模一样【微信：741003700 】【(csu毕业证书)查尔斯特大学毕业证硕士学历】【微信：741003700 】学位证，留信认证（真实可查，永久存档）offer、雅思、外壳等材料/诚信可靠,可直接看成品样本，帮您解决无法毕业带来的各种难题！外壳，原版制作，诚信可靠，可直接看成品样本。行业标杆！精益求精，诚心合作，真诚制作！多年品质 ,按需精细制作，24小时接单,全套进口原装设备。十五年致力于帮助留学生解决难题，包您满意。
本公司拥有海外各大学样板无数，能完美还原海外各大学 Bachelor Diploma degree, Master Degree Diploma
1:1完美还原海外各大学毕业材料上的工艺：水印，阴影底纹，钢印LOGO烫金烫银，LOGO烫金烫银复合重叠。文字图案浮雕、激光镭射、紫外荧光、温感、复印防伪等防伪工艺。材料咨询办理、认证咨询办理请加学历顾问Q/微741003700
留信网认证的作用:
1:该专业认证可证明留学生真实身份
2:同时对留学生所学专业登记给予评定
3:国家专业人才认证中心颁发入库证书
4:这个认证书并且可以归档倒地方
5:凡事获得留信网入网的信息将会逐步更新到个人身份内，将在公安局网内查询个人身份证信息后，同步读取人才网入库信息
6:个人职称评审加20分
7:个人信誉贷款加10分
8:在国家人才网主办的国家网络招聘大会中纳入资料，供国家高端企业选择人才
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...
Medical image analysis has witnessed significant advancements with deep learning techniques. In the domain of brain tumor segmentation, the ability to
precisely delineate tumor boundaries from magnetic resonance imaging (MRI)
scans holds profound implications for diagnosis. This study presents an ensemble convolutional neural network (CNN) with transfer learning, integrating
the state-of-the-art Deeplabv3+ architecture with the ResNet18 backbone. The
model is rigorously trained and evaluated, exhibiting remarkable performance
metrics, including an impressive global accuracy of 99.286%, a high-class accuracy of 82.191%, a mean intersection over union (IoU) of 79.900%, a weighted
IoU of 98.620%, and a Boundary F1 (BF) score of 83.303%. Notably, a detailed comparative analysis with existing methods showcases the superiority of
our proposed model. These findings underscore the model’s competence in precise brain tumor localization, underscoring its potential to revolutionize medical
image analysis and enhance healthcare outcomes. This research paves the way
for future exploration and optimization of advanced CNN models in medical
imaging, emphasizing addressing false positives and resource efficiency.
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024
Sinan from the Delivery Hero mobile infrastructure engineering team shares a deep dive into performance acceleration with Gradle build cache optimizations. Sinan shares their journey into solving complex build-cache problems that affect Gradle builds. By understanding the challenges and solutions found in our journey, we aim to demonstrate the possibilities for faster builds. The case study reveals how overlapping outputs and cache misconfigurations led to significant increases in build times, especially as the project scaled up with numerous modules using Paparazzi tests. The journey from diagnosing to defeating cache issues offers invaluable lessons on maintaining cache integrity without sacrificing functionality.
International Conference on NLP, Artificial Intelligence, Machine Learning an...
International Conference on NLP, Artificial Intelligence, Machine Learning and Applications (NLAIM 2024) offers a premier global platform for exchanging insights and findings in the theory, methodology, and applications of NLP, Artificial Intelligence, Machine Learning, and their applications. The conference seeks substantial contributions across all key domains of NLP, Artificial Intelligence, Machine Learning, and their practical applications, aiming to foster both theoretical advancements and real-world implementations. With a focus on facilitating collaboration between researchers and practitioners from academia and industry, the conference serves as a nexus for sharing the latest developments in the field.
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...
Climate change's impact on the planet forced the United Nations and governments to promote green energies and electric transportation. The deployments of photovoltaic (PV) and electric vehicle (EV) systems gained stronger momentum due to their numerous advantages over fossil fuel types. The advantages go beyond sustainability to reach financial support and stability. The work in this paper introduces the hybrid system between PV and EV to support industrial and commercial plants. This paper covers the theoretical framework of the proposed hybrid system including the required equation to complete the cost analysis when PV and EV are present. In addition, the proposed design diagram which sets the priorities and requirements of the system is presented. The proposed approach allows setup to advance their power stability, especially during power outages. The presented information supports researchers and plant owners to complete the necessary analysis while promoting the deployment of clean energy. The result of a case study that represents a dairy milk farmer supports the theoretical works and highlights its advanced benefits to existing plants. The short return on investment of the proposed approach supports the paper's novelty approach for the sustainable electrical system. In addition, the proposed system allows for an isolated power setup without the need for a transmission line which enhances the safety of the electrical network
NATURAL DEEP EUTECTIC SOLVENTS AS ANTI-FREEZING AGENT
NATURAL DEEP EUTECTIC SOLVENTS AS ANTI-FREEZING AGENT
Harnessing WebAssembly for Real-time Stateless Streaming Pipelines
Traditionally, dealing with real-time data pipelines has involved significant overhead, even for straightforward tasks like data transformation or masking. However, in this talk, we’ll venture into the dynamic realm of WebAssembly (WASM) and discover how it can revolutionize the creation of stateless streaming pipelines within a Kafka (Redpanda) broker. These pipelines are adept at managing low-latency, high-data-volume scenarios.
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
As digital technology becomes more deeply embedded in power systems, protecting the communication
networks of Smart Grids (SG) has emerged as a critical concern. Distributed Network Protocol 3 (DNP3)
represents a multi-tiered application layer protocol extensively utilized in Supervisory Control and Data
Acquisition (SCADA)-based smart grids to facilitate real-time data gathering and control functionalities.
Robust Intrusion Detection Systems (IDS) are necessary for early threat detection and mitigation because
of the interconnection of these networks, which makes them vulnerable to a variety of cyberattacks. To
solve this issue, this paper develops a hybrid Deep Learning (DL) model specifically designed for intrusion
detection in smart grids. The proposed approach is a combination of the Convolutional Neural Network
(CNN) and the Long-Short-Term Memory algorithms (LSTM). We employed a recent intrusion detection
dataset (DNP3), which focuses on unauthorized commands and Denial of Service (DoS) cyberattacks, to
train and test our model. The results of our experiments show that our CNN-LSTM method is much better
at finding smart grid intrusions than other deep learning algorithms used for classification. In addition,
our proposed approach improves accuracy, precision, recall, and F1 score, achieving a high detection
accuracy rate of 99.50%.
Embedded machine learning-based road conditions and driving behavior monitoring
Car accident rates have increased in recent years, resulting in losses in human lives, properties, and other financial costs. An embedded machine learning-based system is developed to address this critical issue. The system can monitor road conditions, detect driving patterns, and identify aggressive driving behaviors. The system is based on neural networks trained on a comprehensive dataset of driving events, driving styles, and road conditions. The system effectively detects potential risks and helps mitigate the frequency and impact of accidents. The primary goal is to ensure the safety of drivers and vehicles. Collecting data involved gathering information on three key road events: normal street and normal drive, speed bumps, circular yellow speed bumps, and three aggressive driving actions: sudden start, sudden stop, and sudden entry. The gathered data is processed and analyzed using a machine learning system designed for limited power and memory devices. The developed system resulted in 91.9% accuracy, 93.6% precision, and 92% recall. The achieved inference time on an Arduino Nano 33 BLE Sense with a 32-bit CPU running at 64 MHz is 34 ms and requires 2.6 kB peak RAM and 139.9 kB program flash memory, making it suitable for resource-constrained embedded systems.
Understanding Inductive Bias in Machine Learning
This presentation explores the concept of inductive bias in machine learning. It explains how algorithms come with built-in assumptions and preferences that guide the learning process. You'll learn about the different types of inductive bias and how they can impact the performance and generalizability of machine learning models.
The presentation also covers the positive and negative aspects of inductive bias, along with strategies for mitigating potential drawbacks. We'll explore examples of how bias manifests in algorithms like neural networks and decision trees.
By understanding inductive bias, you can gain valuable insights into how machine learning models work and make informed decisions when building and deploying them.
LLM Fine Tuning with QLoRA Cassandra Lunch 4, presented by Anant
Slides for the 4th Presentation on LLM Fine-Tuning with QLoRA Presented by Anant, featuring DataStax Astra
Recently uploaded (20)
Advanced control scheme of doubly fed induction generator for wind turbine us...
Advanced control scheme of doubly fed induction generator for wind turbine us...
Comparative analysis between traditional aquaponics and reconstructed aquapon...
Comparative analysis between traditional aquaponics and reconstructed aquapon...
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...
Redefining brain tumor segmentation: a cutting-edge convolutional neural netw...
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024
Optimizing Gradle Builds - Gradle DPE Tour Berlin 2024
Generative AI leverages algorithms to create various forms of content
Generative AI leverages algorithms to create various forms of content
International Conference on NLP, Artificial Intelligence, Machine Learning an...
International Conference on NLP, Artificial Intelligence, Machine Learning an...
Introduction to AI Safety (public presentation).pptx
Introduction to AI Safety (public presentation).pptx
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...
NATURAL DEEP EUTECTIC SOLVENTS AS ANTI-FREEZING AGENT
NATURAL DEEP EUTECTIC SOLVENTS AS ANTI-FREEZING AGENT
Harnessing WebAssembly for Real-time Stateless Streaming Pipelines
Harnessing WebAssembly for Real-time Stateless Streaming Pipelines
gray level transformation unit 3(image processing))
gray level transformation unit 3(image processing))
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
DEEP LEARNING FOR SMART GRID INTRUSION DETECTION: A HYBRID CNN-LSTM-BASED MODEL
Embedded machine learning-based road conditions and driving behavior monitoring
Embedded machine learning-based road conditions and driving behavior monitoring
LLM Fine Tuning with QLoRA Cassandra Lunch 4, presented by Anant
LLM Fine Tuning with QLoRA Cassandra Lunch 4, presented by Anant
2017 ch720 final term presentatiom
- 1. ENGINEERING MANGEMENT TOPIC:- SYSTEM BREAKDOWN STRUCTURE PRENENTED BY:- 2017-CH-720
- 2. SYSTEM BREAKDOWN STRUCTURE System breakdown structure is that how to divided a existing complex system into simple and manageable units(tasks ,sub-tasks). To Create A System Breakdown Structure, You Need Hierarchy. System breakdown structure is generally communicate through the use of graph and charts.
- 3. SYSTEM BREAKDOWN STRUCTURE Hierarchy/Hierarchical Levels: The relationship of one item of hardware/software with respect to items above and below in the relative order of things.
- 4. SYSTEM BREAKDOWN STRUCTURE Example:- Here we breakdown the complex aircraft system structure to the simple unit and subunits.
- 6. SYSTEM BREAKDOWN STRUCTURE Another example Space transport system.
- 7. SYSTEM BREAKDOWN STRUCTURE System for the construction of house
- 8. SYSTEM BREAKDOWN STRUCTURE References:- https://tensix.com/2014/11/creating-a-work-breakdown- structure-wbs-in-primavera-p6/ http://origins.sese.asu.edu/ses405/Student%20PPTs/Miller%20 405%20Solo%20Lecture.pdf https://upload.wikimedia.org/wikipedia/commons/e/eb/Work_ Breakdown_Structure_of_Aircraft_System.jpg