The document discusses conceptual or domain models, which represent concepts in a problem domain using UML class diagrams. A conceptual model illustrates meaningful classes and associations between classes in the problem domain, without including software artifacts or responsibilities. It focuses on identifying domain concepts, drawing them as classes, and adding associations and attributes. The document provides guidelines for creating conceptual models, such as finding conceptual classes from requirements, identifying associations between classes, and choosing appropriate attributes. It also discusses using system sequence diagrams to illustrate the system events generated by external actors in response to use case scenarios.
The document discusses Unit II of a syllabus which covers class diagrams, including elaboration, domain modeling, finding conceptual classes and relationships. It discusses when to use class diagrams and provides examples of a class diagram for a hotel management system. It also discusses inception and elaboration phases in software development processes and provides artifacts used in elaboration. Finally, it discusses domain modeling including how to identify conceptual classes, draw associations, and avoid adding too many associations.
This document discusses mapping a domain model to a software design. It provides examples of mapping domain classes from a process sale use case to initial design classes for a cash till system. Key points are that domain classes often inspire but do not directly map to design classes, and that creating an initial design can help uncover questions about requirements.
This document discusses guidelines for creating a domain model, including:
1) The domain model represents key concepts and vocabulary in a domain to bridge the gap between the software representation and our mental model. It is bounded by current iteration requirements.
2) Conceptual classes are identified from use cases, category lists, and noun phrases. Associations between classes are included where the relationship needs to be preserved.
3) Description classes can model information that describes other entities when deleting instances would lose important data. Examples include product descriptions and flight schedules.
The document provides best practices for domain modeling through examples and guidelines on finding classes, attributes versus classes, using domain terms, and including appropriate associations.
This document provides an introduction to object-oriented analysis and design (OOA/D). It discusses the key concepts of analysis, design, and the Unified Modeling Language (UML). It also provides an example of analyzing and designing a simple dice game to illustrate the process, including defining use cases, creating a domain model, interaction diagrams, and a design class diagram. The goal is to teach students how to apply OOA/D principles and the UML notation to create robust and maintainable software designs.
This document provides an overview of use case modeling. It defines what use cases are, how they are created, and the elements that comprise them. Use cases describe the functional requirements of a system from the perspective of an actor. They are developed through user interviews and documentation analysis to understand how users interact with the system. Use cases are then written as text descriptions and organized visually in a use case diagram to show relationships between use cases and actors.
Object-Oriented Systems Analysis and Design Using UML.pptxXanGwaps
This document discusses object-oriented analysis and design using the Unified Modeling Language (UML). It describes UML as the industry standard for modeling object-oriented systems using diagrams that allow visualization of system construction. The main components of UML are things, relationships, and diagrams which are used in successive iterations to precisely define a system in UML documents. Key object-oriented concepts of objects, classes, and inheritance are also summarized.
The document provides information about object-oriented modeling and design concepts including classes, objects, inheritance, polymorphism, and the Unified Modeling Language (UML). It discusses how object-oriented modeling uses classes to define objects, relationships, and behaviors. It also describes the basic UML diagram types like use case diagrams, class diagrams, sequence diagrams, and state diagrams that can be used to design software systems using an object-oriented approach.
The document discusses Unit II of a syllabus which covers class diagrams, including elaboration, domain modeling, finding conceptual classes and relationships. It discusses when to use class diagrams and provides examples of a class diagram for a hotel management system. It also discusses inception and elaboration phases in software development processes and provides artifacts used in elaboration. Finally, it discusses domain modeling including how to identify conceptual classes, draw associations, and avoid adding too many associations.
This document discusses mapping a domain model to a software design. It provides examples of mapping domain classes from a process sale use case to initial design classes for a cash till system. Key points are that domain classes often inspire but do not directly map to design classes, and that creating an initial design can help uncover questions about requirements.
This document discusses guidelines for creating a domain model, including:
1) The domain model represents key concepts and vocabulary in a domain to bridge the gap between the software representation and our mental model. It is bounded by current iteration requirements.
2) Conceptual classes are identified from use cases, category lists, and noun phrases. Associations between classes are included where the relationship needs to be preserved.
3) Description classes can model information that describes other entities when deleting instances would lose important data. Examples include product descriptions and flight schedules.
The document provides best practices for domain modeling through examples and guidelines on finding classes, attributes versus classes, using domain terms, and including appropriate associations.
This document provides an introduction to object-oriented analysis and design (OOA/D). It discusses the key concepts of analysis, design, and the Unified Modeling Language (UML). It also provides an example of analyzing and designing a simple dice game to illustrate the process, including defining use cases, creating a domain model, interaction diagrams, and a design class diagram. The goal is to teach students how to apply OOA/D principles and the UML notation to create robust and maintainable software designs.
This document provides an overview of use case modeling. It defines what use cases are, how they are created, and the elements that comprise them. Use cases describe the functional requirements of a system from the perspective of an actor. They are developed through user interviews and documentation analysis to understand how users interact with the system. Use cases are then written as text descriptions and organized visually in a use case diagram to show relationships between use cases and actors.
Object-Oriented Systems Analysis and Design Using UML.pptxXanGwaps
This document discusses object-oriented analysis and design using the Unified Modeling Language (UML). It describes UML as the industry standard for modeling object-oriented systems using diagrams that allow visualization of system construction. The main components of UML are things, relationships, and diagrams which are used in successive iterations to precisely define a system in UML documents. Key object-oriented concepts of objects, classes, and inheritance are also summarized.
The document provides information about object-oriented modeling and design concepts including classes, objects, inheritance, polymorphism, and the Unified Modeling Language (UML). It discusses how object-oriented modeling uses classes to define objects, relationships, and behaviors. It also describes the basic UML diagram types like use case diagrams, class diagrams, sequence diagrams, and state diagrams that can be used to design software systems using an object-oriented approach.
UML (Unified Modeling Language) is a standard modeling language used to visualize, specify, construct, and document software systems. It includes graphical notation techniques to create models of object-oriented software systems. Some key UML diagram types are use case diagrams, which depict interactions between external actors and the system; class diagrams, which show system classes and their relationships; and sequence diagrams, which illustrate object interactions over time. UML aims to improve understanding between customers, developers, and other stakeholders and supports the software development lifecycle.
UML (Unified Modeling Language) is a standard modeling language used to visualize, specify, construct, and document software systems. It includes graphical notation techniques to create models of object-oriented software systems. Some key UML diagram types are use case diagrams, class diagrams, sequence diagrams, and state machine diagrams. UML is not a process but a modeling language that can be used throughout the software development lifecycle.
Requirements modeling involves creating models during requirements analysis to understand current systems or business processes being automated and how users will interact with a new system. It helps with elicitation, validation, and communication of requirements. Common tools for requirements modeling include use cases, state diagrams, UI mockups, storyboards, and prototypes.
Define requirements modeling as representing the customers' needs and the problem domain using models to facilitate understanding between stakeholders.
Explain four roles of requirements modeling as:
1) Guiding elicitation by helping determine questions to ask and uncover hidden requirements
2) Providing progress measures by ensuring model completeness indicates elicitation is complete
3) Hel
This document provides an overview of domain modeling concepts including:
- A domain model illustrates meaningful conceptual classes in a problem domain and is not focused on software components.
- Key elements of a domain model include conceptual classes, associations between classes, and attributes of classes.
- Identifying conceptual classes involves techniques like analyzing common nouns and noun phrases.
- Associations represent meaningful relationships between conceptual classes and should be identified based on information needs.
- Attributes specify logical data values of conceptual classes and should be kept simple.
- The document uses examples to demonstrate domain modeling techniques.
This document discusses conceptual data modeling using the entity-relationship (ER) model. It defines key concepts of the ER model including entities, attributes, relationships, entity sets, relationship sets, keys, and ER diagrams. It explains how the ER model is used in the early conceptual design phase of database design to capture the essential data requirements and produce a conceptual schema that can be later mapped to a logical and physical database implementation.
This document provides an introduction to object-oriented analysis and design (OOAD) and domain modeling. It discusses the key steps in OOAD, including domain modeling to understand the problem domain, and creating use case and class diagrams. It then uses an example of modeling an online bookstore to illustrate domain modeling. The document describes modeling the bookstore's requirements, classes, relationships, and key use cases. It provides explanations of UML notation for class and use case diagrams.
The document discusses the differences between software analysis and design. It provides details on:
- Analysis focuses on clarifying requirements and exploring the problem domain to identify concepts and analysis classes.
- Design starts with exploring the solution domain to formulate the system design using tools like class and object diagrams.
- Key outcomes of analysis include requirement specifications while design outcomes include low-level system design documentation.
- Analysis involves system analysts and end users while design involves system architects and developers.
Object-Oriented Systems Analysis and Design Using UML.pptxXanGwaps
This document discusses object-oriented systems analysis and design using the Unified Modeling Language (UML). It defines object-oriented analysis and design, and explains that UML uses various diagrams to visualize the construction of object-oriented systems. The main components of UML include things, relationships, and diagrams. Key object-oriented concepts like objects, classes, attributes, and methods are also described. Finally, different types of UML diagrams like class, component, deployment, use case and activity diagrams are introduced along with examples.
A domain model illustrates meaningful conceptual classes in a problem domain rather than software components or classes. It represents real-world concepts using class diagrams without operations defined. A domain model is not a description of software design artifacts but rather concepts, associations between concepts, and attributes of concepts. Creating a domain model involves identifying conceptual classes, drawing them with relationships, and adding necessary attributes.
ER diagram slides for datanase stujdy-1.pdfSadiaSharmin40
The document discusses database schema design using the entity-relationship (ER) model. It describes the database design process, which involves requirements analysis, conceptual design, and implementation including logical and physical design. The conceptual design phase develops a high-level description of the database using a technique like ER modeling. ER modeling represents entities, entity sets, attributes, relationships, and keys graphically. Relationships associate entities and define how they are related. The conceptual schema and functional requirements are then implemented through logical and physical database design.
The document describes the steps to construct a domain class model:
1. The first step is to find relevant classes by identifying nouns from the problem domain. Classes often correspond to nouns and should make sense within the application domain.
2. The next steps are to prepare a data dictionary defining each class, find associations between classes corresponding to verbs, and identify attributes and links for each class.
3. The model is then organized and simplified using techniques like inheritance and packages. The model is iteratively refined by verifying queries and reconsidering the level of abstraction.
This document provides examples of entity-relationship diagrams (ERDs) for various scenarios. The examples cover relationships between professors and classes, courses and classes, invoices and products, customers and items purchased, departments and projects, orders and parts, equipment faults, students and subjects, painters and paintings, car models and parts, university faculties and courses.
This document discusses various UML diagrams including class diagrams, domain models, associations, attributes, and sequence diagrams. It provides guidance on how to draw class diagrams from different perspectives (conceptual, specification, implementation). It also covers how to create domain models by finding conceptual classes, description classes, and relationships. Sequence diagrams and their relationship to use cases is explained, specifically how system sequence diagrams show the system events for a use case scenario.
The document discusses the process of database design and the entity-relationship (E-R) model. It covers the conceptual, logical, and physical design phases. It also explains the key concepts of the E-R model including entities, attributes, relationships, keys, and cardinality constraints. E-R diagrams provide a way to visually represent an enterprise schema using these basic E-R modeling elements and their relationships.
Object Oriented Analysis and Design with UML2 part2Haitham Raik
The document discusses object-oriented analysis and design principles. It covers object-oriented analysis, which involves identifying core concepts or domain classes from requirements. It then discusses object-oriented design principles like SOLID - single responsibility principle, open/closed principle, Liskov substitution principle, interface segregation principle, and dependency inversion principle. Design patterns are also mentioned.
Introduction to object-oriented analysis and design (OOA/D)Ahmed Farag
Object-oriented analysis involves investigating the problem domain to identify key objects, their attributes, and relationships. Object-oriented design then defines the software objects and how they will collaborate. The document provides an example of analyzing a dice game, including defining use cases, creating a domain model to identify real-world objects like Player and Die, interaction diagrams to illustrate object collaboration, and design class diagrams to define software classes and their methods.
Object-oriented programming uses objects to represent real-world entities. An object has state, which describes its characteristics, and behaviors, which are its capabilities. A class defines a blueprint for objects and multiple objects can be created from the same class. Objects encapsulate both data and functions that operate on that data.
The document discusses static UML diagrams, specifically class diagrams. It covers key concepts of classes, attributes, associations, relationships, and notations. It provides examples of class diagrams for conceptual domain models and describes best practices for identifying conceptual classes, attributes, and associations from use case scenarios to build the domain model.
Training- Slide writing and story telling-AG-PREE-19Apr12 - v3.pptEkaterinaShvaiko
This document provides training materials for project managers on slide writing. It covers topics such as structuring information in slides, choosing appropriate graphs, telling a story with slides, and principles of effective slide design. The learning objectives are to help trainees communicate project results through clear and impactful slides by developing structured communication skills. Examples of good and bad slides are provided to illustrate concepts.
UML (Unified Modeling Language) is a standard modeling language used to visualize, specify, construct, and document software systems. It includes various diagram types to show different views of a system, such as use case diagrams for requirements, class diagrams for structure, and sequence diagrams for behavior. UML aims to be independent of programming languages and development processes. It has become widely used for object-oriented analysis and design.
UML (Unified Modeling Language) is a standard modeling language used to visualize, specify, construct, and document software systems. It includes graphical notation techniques to create models of object-oriented software systems. Some key UML diagram types are use case diagrams, which depict interactions between external actors and the system; class diagrams, which show system classes and their relationships; and sequence diagrams, which illustrate object interactions over time. UML aims to improve understanding between customers, developers, and other stakeholders and supports the software development lifecycle.
UML (Unified Modeling Language) is a standard modeling language used to visualize, specify, construct, and document software systems. It includes graphical notation techniques to create models of object-oriented software systems. Some key UML diagram types are use case diagrams, class diagrams, sequence diagrams, and state machine diagrams. UML is not a process but a modeling language that can be used throughout the software development lifecycle.
Requirements modeling involves creating models during requirements analysis to understand current systems or business processes being automated and how users will interact with a new system. It helps with elicitation, validation, and communication of requirements. Common tools for requirements modeling include use cases, state diagrams, UI mockups, storyboards, and prototypes.
Define requirements modeling as representing the customers' needs and the problem domain using models to facilitate understanding between stakeholders.
Explain four roles of requirements modeling as:
1) Guiding elicitation by helping determine questions to ask and uncover hidden requirements
2) Providing progress measures by ensuring model completeness indicates elicitation is complete
3) Hel
This document provides an overview of domain modeling concepts including:
- A domain model illustrates meaningful conceptual classes in a problem domain and is not focused on software components.
- Key elements of a domain model include conceptual classes, associations between classes, and attributes of classes.
- Identifying conceptual classes involves techniques like analyzing common nouns and noun phrases.
- Associations represent meaningful relationships between conceptual classes and should be identified based on information needs.
- Attributes specify logical data values of conceptual classes and should be kept simple.
- The document uses examples to demonstrate domain modeling techniques.
This document discusses conceptual data modeling using the entity-relationship (ER) model. It defines key concepts of the ER model including entities, attributes, relationships, entity sets, relationship sets, keys, and ER diagrams. It explains how the ER model is used in the early conceptual design phase of database design to capture the essential data requirements and produce a conceptual schema that can be later mapped to a logical and physical database implementation.
This document provides an introduction to object-oriented analysis and design (OOAD) and domain modeling. It discusses the key steps in OOAD, including domain modeling to understand the problem domain, and creating use case and class diagrams. It then uses an example of modeling an online bookstore to illustrate domain modeling. The document describes modeling the bookstore's requirements, classes, relationships, and key use cases. It provides explanations of UML notation for class and use case diagrams.
The document discusses the differences between software analysis and design. It provides details on:
- Analysis focuses on clarifying requirements and exploring the problem domain to identify concepts and analysis classes.
- Design starts with exploring the solution domain to formulate the system design using tools like class and object diagrams.
- Key outcomes of analysis include requirement specifications while design outcomes include low-level system design documentation.
- Analysis involves system analysts and end users while design involves system architects and developers.
Object-Oriented Systems Analysis and Design Using UML.pptxXanGwaps
This document discusses object-oriented systems analysis and design using the Unified Modeling Language (UML). It defines object-oriented analysis and design, and explains that UML uses various diagrams to visualize the construction of object-oriented systems. The main components of UML include things, relationships, and diagrams. Key object-oriented concepts like objects, classes, attributes, and methods are also described. Finally, different types of UML diagrams like class, component, deployment, use case and activity diagrams are introduced along with examples.
A domain model illustrates meaningful conceptual classes in a problem domain rather than software components or classes. It represents real-world concepts using class diagrams without operations defined. A domain model is not a description of software design artifacts but rather concepts, associations between concepts, and attributes of concepts. Creating a domain model involves identifying conceptual classes, drawing them with relationships, and adding necessary attributes.
ER diagram slides for datanase stujdy-1.pdfSadiaSharmin40
The document discusses database schema design using the entity-relationship (ER) model. It describes the database design process, which involves requirements analysis, conceptual design, and implementation including logical and physical design. The conceptual design phase develops a high-level description of the database using a technique like ER modeling. ER modeling represents entities, entity sets, attributes, relationships, and keys graphically. Relationships associate entities and define how they are related. The conceptual schema and functional requirements are then implemented through logical and physical database design.
The document describes the steps to construct a domain class model:
1. The first step is to find relevant classes by identifying nouns from the problem domain. Classes often correspond to nouns and should make sense within the application domain.
2. The next steps are to prepare a data dictionary defining each class, find associations between classes corresponding to verbs, and identify attributes and links for each class.
3. The model is then organized and simplified using techniques like inheritance and packages. The model is iteratively refined by verifying queries and reconsidering the level of abstraction.
This document provides examples of entity-relationship diagrams (ERDs) for various scenarios. The examples cover relationships between professors and classes, courses and classes, invoices and products, customers and items purchased, departments and projects, orders and parts, equipment faults, students and subjects, painters and paintings, car models and parts, university faculties and courses.
This document discusses various UML diagrams including class diagrams, domain models, associations, attributes, and sequence diagrams. It provides guidance on how to draw class diagrams from different perspectives (conceptual, specification, implementation). It also covers how to create domain models by finding conceptual classes, description classes, and relationships. Sequence diagrams and their relationship to use cases is explained, specifically how system sequence diagrams show the system events for a use case scenario.
The document discusses the process of database design and the entity-relationship (E-R) model. It covers the conceptual, logical, and physical design phases. It also explains the key concepts of the E-R model including entities, attributes, relationships, keys, and cardinality constraints. E-R diagrams provide a way to visually represent an enterprise schema using these basic E-R modeling elements and their relationships.
Object Oriented Analysis and Design with UML2 part2Haitham Raik
The document discusses object-oriented analysis and design principles. It covers object-oriented analysis, which involves identifying core concepts or domain classes from requirements. It then discusses object-oriented design principles like SOLID - single responsibility principle, open/closed principle, Liskov substitution principle, interface segregation principle, and dependency inversion principle. Design patterns are also mentioned.
Introduction to object-oriented analysis and design (OOA/D)Ahmed Farag
Object-oriented analysis involves investigating the problem domain to identify key objects, their attributes, and relationships. Object-oriented design then defines the software objects and how they will collaborate. The document provides an example of analyzing a dice game, including defining use cases, creating a domain model to identify real-world objects like Player and Die, interaction diagrams to illustrate object collaboration, and design class diagrams to define software classes and their methods.
Object-oriented programming uses objects to represent real-world entities. An object has state, which describes its characteristics, and behaviors, which are its capabilities. A class defines a blueprint for objects and multiple objects can be created from the same class. Objects encapsulate both data and functions that operate on that data.
The document discusses static UML diagrams, specifically class diagrams. It covers key concepts of classes, attributes, associations, relationships, and notations. It provides examples of class diagrams for conceptual domain models and describes best practices for identifying conceptual classes, attributes, and associations from use case scenarios to build the domain model.
Training- Slide writing and story telling-AG-PREE-19Apr12 - v3.pptEkaterinaShvaiko
This document provides training materials for project managers on slide writing. It covers topics such as structuring information in slides, choosing appropriate graphs, telling a story with slides, and principles of effective slide design. The learning objectives are to help trainees communicate project results through clear and impactful slides by developing structured communication skills. Examples of good and bad slides are provided to illustrate concepts.
UML (Unified Modeling Language) is a standard modeling language used to visualize, specify, construct, and document software systems. It includes various diagram types to show different views of a system, such as use case diagrams for requirements, class diagrams for structure, and sequence diagrams for behavior. UML aims to be independent of programming languages and development processes. It has become widely used for object-oriented analysis and design.
Embedded machine learning-based road conditions and driving behavior monitoringIJECEIAES
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.
Applications of artificial Intelligence in Mechanical Engineering.pdfAtif Razi
Historically, mechanical engineering has relied heavily on human expertise and empirical methods to solve complex problems. With the introduction of computer-aided design (CAD) and finite element analysis (FEA), the field took its first steps towards digitization. These tools allowed engineers to simulate and analyze mechanical systems with greater accuracy and efficiency. However, the sheer volume of data generated by modern engineering systems and the increasing complexity of these systems have necessitated more advanced analytical tools, paving the way for AI.
AI offers the capability to process vast amounts of data, identify patterns, and make predictions with a level of speed and accuracy unattainable by traditional methods. This has profound implications for mechanical engineering, enabling more efficient design processes, predictive maintenance strategies, and optimized manufacturing operations. AI-driven tools can learn from historical data, adapt to new information, and continuously improve their performance, making them invaluable in tackling the multifaceted challenges of modern mechanical engineering.
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...shadow0702a
This document serves as a comprehensive step-by-step guide on how to effectively use PyCharm for remote debugging of the Windows Subsystem for Linux (WSL) on a local Windows machine. It meticulously outlines several critical steps in the process, starting with the crucial task of enabling permissions, followed by the installation and configuration of WSL.
The guide then proceeds to explain how to set up the SSH service within the WSL environment, an integral part of the process. Alongside this, it also provides detailed instructions on how to modify the inbound rules of the Windows firewall to facilitate the process, ensuring that there are no connectivity issues that could potentially hinder the debugging process.
The document further emphasizes on the importance of checking the connection between the Windows and WSL environments, providing instructions on how to ensure that the connection is optimal and ready for remote debugging.
It also offers an in-depth guide on how to configure the WSL interpreter and files within the PyCharm environment. This is essential for ensuring that the debugging process is set up correctly and that the program can be run effectively within the WSL terminal.
Additionally, the document provides guidance on how to set up breakpoints for debugging, a fundamental aspect of the debugging process which allows the developer to stop the execution of their code at certain points and inspect their program at those stages.
Finally, the document concludes by providing a link to a reference blog. This blog offers additional information and guidance on configuring the remote Python interpreter in PyCharm, providing the reader with a well-rounded understanding of the process.
Advanced control scheme of doubly fed induction generator for wind turbine us...IJECEIAES
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.
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...IJECEIAES
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
Rainfall intensity duration frequency curve statistical analysis and modeling...bijceesjournal
Using data from 41 years in Patna’ India’ the study’s goal is to analyze the trends of how often it rains on a weekly, seasonal, and annual basis (1981−2020). First, utilizing the intensity-duration-frequency (IDF) curve and the relationship by statistically analyzing rainfall’ the historical rainfall data set for Patna’ India’ during a 41 year period (1981−2020), was evaluated for its quality. Changes in the hydrologic cycle as a result of increased greenhouse gas emissions are expected to induce variations in the intensity, length, and frequency of precipitation events. One strategy to lessen vulnerability is to quantify probable changes and adapt to them. Techniques such as log-normal, normal, and Gumbel are used (EV-I). Distributions were created with durations of 1, 2, 3, 6, and 24 h and return times of 2, 5, 10, 25, and 100 years. There were also mathematical correlations discovered between rainfall and recurrence interval.
Findings: Based on findings, the Gumbel approach produced the highest intensity values, whereas the other approaches produced values that were close to each other. The data indicates that 461.9 mm of rain fell during the monsoon season’s 301st week. However, it was found that the 29th week had the greatest average rainfall, 92.6 mm. With 952.6 mm on average, the monsoon season saw the highest rainfall. Calculations revealed that the yearly rainfall averaged 1171.1 mm. Using Weibull’s method, the study was subsequently expanded to examine rainfall distribution at different recurrence intervals of 2, 5, 10, and 25 years. Rainfall and recurrence interval mathematical correlations were also developed. Further regression analysis revealed that short wave irrigation, wind direction, wind speed, pressure, relative humidity, and temperature all had a substantial influence on rainfall.
Originality and value: The results of the rainfall IDF curves can provide useful information to policymakers in making appropriate decisions in managing and minimizing floods in the study area.
Discover the latest insights on Data Driven Maintenance with our comprehensive webinar presentation. Learn about traditional maintenance challenges, the right approach to utilizing data, and the benefits of adopting a Data Driven Maintenance strategy. Explore real-world examples, industry best practices, and innovative solutions like FMECA and the D3M model. This presentation, led by expert Jules Oudmans, is essential for asset owners looking to optimize their maintenance processes and leverage digital technologies for improved efficiency and performance. Download now to stay ahead in the evolving maintenance landscape.
artificial intelligence and data science contents.pptxGauravCar
What is artificial intelligence? Artificial intelligence is the ability of a computer or computer-controlled robot to perform tasks that are commonly associated with the intellectual processes characteristic of humans, such as the ability to reason.
› ...
Artificial intelligence (AI) | Definitio
2. Building Conceptual/Domain Models
• It is a major activity in the development cycle.
• A conceptual/domain model is a representation of
concepts in a problem domain.
• In UML it is a static structure diagrams in which no
operations are defined.
• A domain model illustrates meaningful (to the modelers)
conceptual classes in a problem domain; it is the most
important artifact to create during object-oriented
analysis.
• A domain model is a representation of real-world
conceptual classes, not of software components.
• It is not a set of diagrams describing software classes or
software objects with responsibilities
3. • Using UML notation, a domain model is
illustrated with a set of class diagrams in which
no operations are defined.
• It may show:
- domain objects or conceptual classes
- associations between conceptual classes
- attributes of conceptual classes
• It must not show:
- software artifacts such as window or
database
- responsibilities or methods
4.
5. Domain Modeling
• visual representation of domain concepts in simple
UML
- Other names: conceptual models, domain object
model, analysis object model
- Bounded by a specific domain as described in use
cases
- Concepts are not software classes (these are in
domain layer )
• In object Oriented design the emphasis is on defining
logical software objects that will ultimately be
implemented in an object oriented programming
language.
6. Steps for Creating a Domain Model
i. Find the domain concepts
ii. Draw them in a UML class diagram
iii. Add associations and attributes
7.
8. • Domain concepts noteworthy abstractions,
domain vocabulary idea, thing or object
e.g Payment, Sale
• Associations relationships between concepts
e.g. Payment Pays-For Sales
• Attributes information content e.g. Sale
records date and time
9. Domain Model : Identifying
Conceptual Classes
• The domain model illustrates conceptual classes
or vocabulary in the domain.
• Informally, a conceptual class is an idea, thing, or
object. More formally, a conceptual class may be
considered in terms of its symbol, intension, and
extension
Symbol: words or images representing a
conceptual class.
Intension: the definition of a conceptual class.
Extension: the set of examples to which the
conceptual class applies.
10. Example
• Conceptual class for the event of a purchase
transaction:
• Name : Sale.
• Intension: represents the event of a purchase
transaction, and has a date and time.
• Extension: All the examples of sales; in other
words, the set of all sales.
11.
12. Example ..
• Name : Card
• Intension: represents one card in a poker deck that has a rank
(1..13) and a suit
• Extension: the set of all cards
13. Domain Models and Decomposition
• Software problems can be complex
• Decomposition: divide-and-conquer is a common
strategy to deal with this complexity by division
of the problem space into comprehensible units.
• In structured analysis, the dimension of
decomposition is by processes or functions.
• In object-oriented analysis, the dimension of
decomposition is fundamentally by things or
entities in the domain.
14. How to Create a Domain Model
• Find the conceptual classes
• Draw them as classes in a UML class diagram
• Add associations necessary to record
relationships
• Add attributes necessary for information to be
preserved
• Use existing names, the vocabulary of the
domain
14
15. How do I find Conceptual Classes?
• Reuse or modify existing models. If there are
published models, prior art, or books, use
them
• Use a category list (given behind)
• Identify noun phrases (linguistic analysis)
15
16.
17.
18. Noun Phrase Identification
• Consider the following problem description,
analyzed for Subjects, Verbs, Objects:
The ATM verifies whether the customer's card number and PIN are correct.
S V O O O
If it is, then the customer can check the account balance, deposit cash, and withdraw cash.
S V O V O V O
Checking the balance simply displays the account balance.
S O V O
Depositing asks the customer to enter the amount, then updates the account balance.
S V O V O V O
Withdraw cash asks the customer for the amount to withdraw; if the account has enough cash,
S O V O O V S V O
the account balance is updated. The ATM prints the customer’s account balance on a receipt.
O V S V O O
19. Noun Phrases
Analyze each subject and object as follows:
• Does it represent a person performing an action?
Then it’s an actor, ‘R’.
• Is it also a verb (such as ‘deposit’)? Then it may be a
method, ‘M’.
• Is it a simple value, such as ‘color’ (string) or ‘money’
(number)?
Then it is probably an attribute, ‘A’.
• Which NPs are unmarked? Make it ‘C’ for class.
Verbs can also be classes, for example:
• Deposit is a class if it retains state information
20. Where are the Terms?
• Some are in the use case
• Some come from domain experts
• Natural language is imprecise and ambiguous,
so you need to use judgment
23. POS example
You can create a list, or you can use a set of class diagrams, per the table below
Store
Register Sale
Item
Payment
Sales
LineItem
Cashier Customer Manager
Product
Catalog
Product
Specification
24. A Common Mistake in Identifying
Conceptual Classes
• Common mistake: representing something as
an attribute when it should have been a class.
• “If we do not think of some conceptual class X
as a number or text in the real world, it should
probably be a class, not an attribute.”
• Should “store” be an attribute of Sale or
should it be a class?
25. • In the real world, a store is not considered a
number or text the term suggests a legal entity,
an organization, and something occupies space.
Therefore, Store should be a concept.
• In Airline Domain, Will Destination be a concept
of or an attribute Of Flight?
or?
• Destination Airport is a massive thing that
occupies space so it is a concept not an attribute
27. When Are Description Conceptual
Classes Required?
• Add a specification or description conceptual
class (ProductDescription) when:
- There needs to be a description about an item
or service, independent of the current existence
of any examples of those items or services.
- Deleting instances of things they describe (for
example, Item) results in a loss of information
that needs to be maintained, due to the incorrect
association of information with the deleted thing.
• It reduces redundant or duplicated information
29. Domain Modeling : Adding
Associations(second step)
• Association is a relationship between
concepts that indicates some meaningful
interesting connection.
30. The UML Notation for association
• An association is represented as a line between classes with
an association name.
• The association is inherently bidirectional, meaning that from
instances of either class, logical traversal to the other is
possible.
33. High Priority Associations
• Some high-priority association categories that
are invariably useful to include in a domain
model:
A is a physical or logical part of B
A is a physically or logically contained in B
A is recorded in B
34. Association Guidelines
• Focus on those associations in which knowledge
of the relationship needs to be preserved need to
know
• It is more important to identify concepts then to
identify associations
• Too many associations tend to confuse a domain
model rather than illuminate it. Their discovery
can be time-consuming, with marginal benefit.
• Avoid showing redundant or derivable
associations.
35. Role
• Each end of an association is called a role.
Roles may optionally have:
- name
- multiplicity expression
- navigability
36. Multiplicity
• It defines how many instances of A can be associated with one
instance of a type B, at a particular moment in time.
• For example, a single instance of a Store can be associated
with "many" (zero or more, indicated by the * ) Item
instances.
38. Naming Association
• Name an association based on a TypeName-VerbPhrase-
TypeName format where the verb phrase creates a sequence
that is readable and meaningful in the model context.
• Association names should start with a capital letter, since an
association represents a classifier of links between instances;
in the UML, classifiers should start with a capital letter.
• Good: Sale PaidBy CashPayment Bad: Sale uses
CashPayment
• Good: Player IsOn Square Bad: Player has Square
• Two common and equally legal formats for a compound
association name are:
- Paid-by PaidBy
39.
40. Multiple Associations between Two
Types
• Two types may have multiple associations
between them; this is not uncommon.
44. Domain Model: Identifying
Attributes(step 3)
• Attribute: It is a logical data value of an Object
• Include the following attributes in a domain model: Those
for which the requirements (for example, use cases) suggest
or imply a need to remember information
• UML Attribute Notation
Attributes are shown in the second compartment of the class
box.
Their type may optionally be shown
45. Valid Attribute Types
• Keep Attributes Simple
• Intuitively, most simple attribute types are what are often
thought of as primitive data types, such as numbers.
• The type of an attribute should not normally be a complex
domain concept, such as a Sale or Airport.
• For example, the currentRegister attribute in the Cashier class
is undesirable because its type is meant to be a Register,
which is not a simple attribute type (such as Number or
String).
• The most useful way to express that a Cashier uses a Register
is with an association, not with an attribute.
46. • The attributes in a domain model should
preferably be simple attributes or data types.
• Very common attribute data types include:
Boolean, Date, Number, String(Text), Time
• Other common types include: Address, Color,
Geometries (Point, Rectangle),Phone
• Number, Social Security Number, Universal
Product Code (UPC), SKU,ZIP or postal codes,
enumerated types
47. Figure : Relate with associations, not attributes.
Figure : Avoid representing complex domain concepts as
attributes; use associations.
48. Data Types
• Attributes should generally be data types. This is a
UML term that implies a set of values for which
unique identity is not meaningful.
• For example, it is not meaningful to distinguish
between:
Separate instances of the Number 5.
Separate instances of the String 'cat'.
Separate instances of PhoneNumber that contain the
same number.
Separate instances of Address that contain the same
address.
49. Non-Primitive Attribute Types
• Represent what may initially be considered a primitive data type
(such as a number or string) as a non-primitive class if:
- It is composed of separate sections.
- phone number, name of person
- There are operations usually associated with it, such as parsing or
validation.
- social security number
- It has other attributes.
- promotional price could have a start (effective) date and end date
- It is a quantity with a unit.
- payment amount has a unit of currency
- It is an abstraction of one or more types with some of these qualities.
- item identifier in the sales domain is a generalization of types such
as Universal Product Code (UPC) or European Article Number (EAN)
50. Attributes in the PoS Domain Model
• The attributes chosen reflect the requirements for this
iteration—the ProcessSale scenarios of this iteration
51. • The list of attributes should primarily be
constrained to the requirements and
simplifications currently under consideration.
• Some attributes are clearly called for by reading
Requirements specification
• Current use cases under considerations
Simplifications, clarifications, and assumption
documents
• e.g. It is necessary to record the date and time of
a sale, therefore the sale concept requires a date
and a time attribute.
53. Multiplicity from SalesLineItem to
Item
• It is possible for a cashier to receive a group of like items
(for example, six tofu packages),enter the itemID once,
and then enter a quantity (for example, six).
• Consequently, individual SalesLineItem can be associated
with more than one instance of item. The quantity that is
entered by the cashier may be recorded as an attribute
of the SalesLineItem . However, the quantity can be
calculated from the actual multiplicity value of the
relationship, so it may be characterized as a derived
attribute—one that may be derived from other
information. In the UML, a derived attribute is indicated
with a "/" symbol.
54.
55. Building System Sequence Diagrams -
System Behavior
• A system sequence diagram is a fast and easily
created artifact that illustrates input and
output events related to the systems under
construction.
• The UML contains notation in the form of
sequence diagrams to illustrate events from
external actors to a system.
56. System Behavior
• It is a description of what system does, without
explaining how system does it.
• Before proceeding to a logical design of how a software
application will work, it is useful to investigate and
define its behavior as a "black box."
• System behavior is a description of what a system
does, without explaining how it does it.
i. One part of that description is a system sequence
diagram.
ii. Other parts include the use cases, and system
contracts
57. System Sequence Diagrams
• Use cases describe how external actors interact with the
software system
• During this interaction an actor generates events to a
system, usually requesting some operation in response. For
example, when a cashier enters an item's ID, the cashier is
requesting the POS system to record that item's sale.
• That request event initiates an operation upon the system.
• It is desirable to isolate and illustrate the operations that
an external actor requests of a system, because they are
an important part of understanding system behavior.
58. Contd…
• The UML includes sequence diagrams as a notation that
can illustrate actor interactions and the operations initiated
by them.
• A system sequence diagram (SSD) is a picture that shows,
for a particular scenario of a usecase, the events that
external actors generate, their order, and inter-system
events.
• All systems are treated as a black box; the emphasis of the
diagram is events that cross the system boundary from
actors to systems.
• An SSD should be done for the main success scenario of
the use case, and frequent or complex alternative
scenarios.
59.
60. Example of a sequence diagram
• An SSD shows, for a particular course of events within a
use case, the external actors that interact directly with
the system, the system (as a black box), and the system
events that the actors generate .
• Time proceeds downward, and the ordering of events
should follow their order in the use case.
• System events may include parameters.
• This example is for the main success scenario of the
Process Sale use case.
• It indicates that the cashier generates makeNewSale,
enteritem, endSale, and makePayment system
events.
63. Significance of Drawing System
Sequence Diagrams
• It is required to design software to handle events from mouse,
keyboard etc coming in to the system and execute a response
• Software system reacts to three things
- External events from actors (human or computers)
- Timer events
- Faults or exceptions
• So it becomes necessary to know the external/system events to
analyze the system behavior
• System sequence diagrams are drawn to investigate and define the
behavior of a software application as a black box before going into
detailed design of how it works
• System behavior is a description of what a system does, without
explaining how it does it and System sequence diagram is a part of
that description
64. SSDs and Use Cases
• An SSD shows system events for a scenario of
a use case, therefore it is generated from
inspection of a use case. So there can be
multiple scenarios in case of a system and
those scenarios can be further elaborated by
using individual system sequence diagrams to
depict the system events.
65.
66. System Events and the System
Boundary
• To identify system events, it is necessary to be clear on the
choice of system boundary.
• For the purposes of software development, the system
boundary is usually chosen to be the software (and possibly
hardware) system itself; in this context, a system event is an
external event that directly stimulates the software
67. • Consider the Process Sale use case to identify
system events. First, we must determine the
actors that directly interact with the software
system. The customer interacts with the
cashier, but for this simple cash-only scenario,
does not directly interact with the POS system
only the cashier does. Therefore, the
customer is not a generator of system events;
only the cashier is.
68. Giving Names to System Events and
System Operations
• System events (and their associated system operations)
should be expressed at the level of intent rather than in
terms of the physical input medium or interface widget
level.
• It also improves clarity to start the name of a system event
with a verb (add...,enter..., end...,make...)
69. • A system event is an external input event generated by an actor to
a system.
• An Event initiates a responding operation.
• A system operation is an operation of the system that executes in
response to a system events
• When the Cashier generates the enterItem system event it causes
the execution of the enterItem system operation (in this case the
event is the named stimulus and the operation is the response) So
it is better to name a system event as enterItem rather than scan
as scan is specific form of entering items into system
Recording System Operations
• The set of all required systems operations is determined by
identifying the system events, using parameters e.g.
enterItem(UPC, quantity), endSale(), makePayment(amount)