The document describes an online shopping cart system. It includes sections on scope, requirements, functional modeling with data flow diagrams, use case diagrams, and interaction diagrams including sequence and collaboration diagrams. The functional models show the data flows between customers, administrators, and the shopping cart system for key processes like online shopping, product listing, and administration. The use case diagram defines actors like customers and administrators and key use cases such as searching for products, purchasing items, and updating product information. Sequence and collaboration diagrams provide examples of interactions during user registration, item registration by sellers, customer ordering, and administrator functions.
This document contains an analysis of requirements for an e-retail system. It includes use cases for common customer activities like registration, login, searching for products, browsing product catalogs, sorting products, adding products to a cart, managing orders, and tracking orders. It also describes requirements for the system like supporting customer registration and login, product search and browsing, sorting products by different criteria, adding items to a cart, managing orders, applying coupon codes, selecting payment methods, and tracking orders. Use case diagrams and other UML diagrams will be developed to further analyze and design the system.
The proposed SmartOnes electronic transactional records system for Acme Rental aims to streamline operations and increase revenue through reducing customer transaction times, assisting in tracking late rentals, and simplifying employee workflows. By implementing an online system instead of the current manual paper-based process, the objectives are to reduce customer transaction times by 133%, require less employee hours through more efficient processes, increase revenue by approximately $30,000 through better tracking of overdue rentals, improve customer satisfaction and loyalty, and boost employee satisfaction through reduced manual data entry. The proposal outlines the planned system interfaces, reports, data flows, implementation approach through a phased pilot program, training plans, and change management strategy to ensure a successful rollout of the
This document proposes an electronic transactional records system for Acme Rental to address inefficiencies in their current manual system. The current system takes 8 minutes per customer transaction and has led to a 12.5% decrease in revenue. The proposed system aims to reduce transaction time by 133%, require less employee time, track overdue rentals to increase revenue by $30,000, improve customer satisfaction, and boost employee morale. It will interface with customer sign-up, checkout processes, and provide inventory, exception, and sales reports for employees. A phased implementation approach over 3 months will first deploy the checkout process at one pilot store before rolling out to additional stores.
Oracle Inventory – Types of Move OrdersBoopathy CS
Move orders allow for the transfer of inventory within the same organization and come in different types for different purposes. Requisition move orders are manually created and may require approval depending on organization parameters. Replenishment move orders are automatically generated from replenishment methods to source inventory. Pick wave move orders are pre-approved and generated to move material during order picking. WIP issue move orders are automatically created for backflush transactions in a pre-approved status.
The document describes how to determine and calculate cyclomatic complexity for a code sample that uses the Euclid's algorithm to compute the greatest common divisor (GCD) of two numbers. It provides three methods to calculate the cyclomatic complexity of the code: 1) using the number of nodes and edges in the control flow graph, 2) using the number of non-overlapping areas, and 3) using the number of decision statements and loops. The cyclomatic complexity is determined to be 3 using all three methods. The document also includes an example of creating a software requirements specification (SRS) document for a banking system application using use case diagrams, state diagrams, and activity diagrams in Star UML.
The document discusses requirements modeling and analysis modeling in software engineering. It provides information on:
1) The different types of models that can be created during requirements modeling, including requirements models, design models, scenario-based models, data models, class-based models, flow-oriented models, and behavioral models.
2) The purposes of requirements modeling, which include representing customer requirements, gaining a better understanding of the system, and providing information to help with system design and development.
3) Key principles of requirements modeling, such as representing the information, functional, and behavioral domains of the system and partitioning models in a layered/hierarchical way.
4) Specific modeling techniques like scenario-based modeling, data
Use case diagrams depict the functionality of a system from a user perspective by showing actors, use cases, and relationships between them. Actors represent roles that interact with the system, while use cases represent system functions. Relationships include association, extend, generalization, uses, and include. Each use case contains details like preconditions, postconditions, normal and alternative flows, and exceptions. Use cases are identified through actor-based and event-based methods by determining actor tasks and system responses to external events.
This document contains an analysis of requirements for an e-retail system. It includes use cases for common customer activities like registration, login, searching for products, browsing product catalogs, sorting products, adding products to a cart, managing orders, and tracking orders. It also describes requirements for the system like supporting customer registration and login, product search and browsing, sorting products by different criteria, adding items to a cart, managing orders, applying coupon codes, selecting payment methods, and tracking orders. Use case diagrams and other UML diagrams will be developed to further analyze and design the system.
The proposed SmartOnes electronic transactional records system for Acme Rental aims to streamline operations and increase revenue through reducing customer transaction times, assisting in tracking late rentals, and simplifying employee workflows. By implementing an online system instead of the current manual paper-based process, the objectives are to reduce customer transaction times by 133%, require less employee hours through more efficient processes, increase revenue by approximately $30,000 through better tracking of overdue rentals, improve customer satisfaction and loyalty, and boost employee satisfaction through reduced manual data entry. The proposal outlines the planned system interfaces, reports, data flows, implementation approach through a phased pilot program, training plans, and change management strategy to ensure a successful rollout of the
This document proposes an electronic transactional records system for Acme Rental to address inefficiencies in their current manual system. The current system takes 8 minutes per customer transaction and has led to a 12.5% decrease in revenue. The proposed system aims to reduce transaction time by 133%, require less employee time, track overdue rentals to increase revenue by $30,000, improve customer satisfaction, and boost employee morale. It will interface with customer sign-up, checkout processes, and provide inventory, exception, and sales reports for employees. A phased implementation approach over 3 months will first deploy the checkout process at one pilot store before rolling out to additional stores.
Oracle Inventory – Types of Move OrdersBoopathy CS
Move orders allow for the transfer of inventory within the same organization and come in different types for different purposes. Requisition move orders are manually created and may require approval depending on organization parameters. Replenishment move orders are automatically generated from replenishment methods to source inventory. Pick wave move orders are pre-approved and generated to move material during order picking. WIP issue move orders are automatically created for backflush transactions in a pre-approved status.
The document describes how to determine and calculate cyclomatic complexity for a code sample that uses the Euclid's algorithm to compute the greatest common divisor (GCD) of two numbers. It provides three methods to calculate the cyclomatic complexity of the code: 1) using the number of nodes and edges in the control flow graph, 2) using the number of non-overlapping areas, and 3) using the number of decision statements and loops. The cyclomatic complexity is determined to be 3 using all three methods. The document also includes an example of creating a software requirements specification (SRS) document for a banking system application using use case diagrams, state diagrams, and activity diagrams in Star UML.
The document discusses requirements modeling and analysis modeling in software engineering. It provides information on:
1) The different types of models that can be created during requirements modeling, including requirements models, design models, scenario-based models, data models, class-based models, flow-oriented models, and behavioral models.
2) The purposes of requirements modeling, which include representing customer requirements, gaining a better understanding of the system, and providing information to help with system design and development.
3) Key principles of requirements modeling, such as representing the information, functional, and behavioral domains of the system and partitioning models in a layered/hierarchical way.
4) Specific modeling techniques like scenario-based modeling, data
Use case diagrams depict the functionality of a system from a user perspective by showing actors, use cases, and relationships between them. Actors represent roles that interact with the system, while use cases represent system functions. Relationships include association, extend, generalization, uses, and include. Each use case contains details like preconditions, postconditions, normal and alternative flows, and exceptions. Use cases are identified through actor-based and event-based methods by determining actor tasks and system responses to external events.
This document outlines the phases of developing an online shopping system, including project planning, modeling requirements through UML diagrams, software configuration management, and testing. Key modules include login, viewing and adding products, and updating quantities. The system allows customers to purchase products and administrators to manage the database. Programming is done in Visual Basic using forms and scripts to implement the system functionality.
This document outlines the phases of developing an online shopping system, including project planning, modeling requirements through UML diagrams, software configuration management, and testing. Key modules include login, viewing and adding products, and updating quantities. The system allows customers to purchase products and administrators to manage the database. Programming is done in Visual Basic using forms and scripts to implement the system functionality.
Payment Routing Module using Kafka StreamsIRJET Journal
This document proposes a payment routing module that uses Kafka Streams for stream processing to improve the efficiency of online payment systems. The routing module filters transaction data, calculates the success and failure rates of different acquirer banks in time windows, and queries this data to route new transactions to acquirers that are currently more reliable based on recent performance. Implementing this routing module could help lower transaction failure rates compared to relying solely on payment gateways for routing decisions. The methodology describes how the module would work using Kafka Streams functionality like tumbling windows to aggregate metrics for each acquirer and make informed routing choices.
The document discusses use case diagrams in object oriented design and analysis. It defines use cases as descriptions of system functionality from a user perspective. Use case diagrams depict system behavior, users, and relationships between actors, use cases, and other use cases. The key components of use case diagrams are described as actors, use cases, the system boundary, and relationships. Common relationships include association, extend, generalization, uses, and include. An example use case diagram for a cellular telephone is provided to illustrate these concepts.
This document discusses nested state diagrams and interaction modeling techniques. It addresses:
1. The use of submachine states and composite states to model nested states within a state diagram.
2. Interaction modeling approaches including use cases, sequence diagrams, and activity diagrams.
3. Guidelines for developing use cases, sequence diagrams, and activity diagrams to fully capture system behavior.
The document describes developing an online spice selling system that allows customers to order spices and services online by submitting orders before a cutoff time and receiving deliveries within a given window, with payment processed after items are picked but before delivery to allow for order changes. It provides an abstract, use case diagram, activity diagram, class diagram, sequence diagram, and state diagram for the system as well as an introduction and index.
The document discusses various interaction diagrams used in modeling systems, including use case diagrams, sequence diagrams, activity diagrams, and state charts. It provides examples and definitions for each type of diagram. For use case diagrams, it explains actors, scenarios, and different notations. Sequence diagrams show the sequence and timing of messages between objects to illustrate object interactions. Activity diagrams model business processes and workflows showing the flow of activities. State chart diagrams use states and transitions to model an object's behavior in response to events. The document also includes exercises to create interaction diagrams for various example systems and processes.
IRJET - Analysis & Study of E-Procurement System in Current ScenarioIRJET Journal
This document summarizes a research paper that analyzes e-procurement systems and online auctions. It begins with an abstract that outlines the goal of analyzing current auction forms and issues like developing effective auction systems and predicting final bid prices. It then covers sections that review the introduction of online auctions, prior literature on auction mechanisms and structures, the proposed system design including modules for authentication, administration, sellers and buyers, advantages over traditional auctions, problems addressed, and conclusions. The document provides details on the technical aspects and theoretical underpinnings of online auction systems.
This document discusses function-oriented design and compares it to object-oriented design. It begins by explaining function-oriented design and how a system is decomposed into a set of interacting functions that share a centralized system state. It then covers the key aspects of function-oriented design process, including:
1. Using data flow diagrams to model how data passes through the system.
2. Developing structure charts to show how high-level functions call lower-level subfunctions.
3. Creating detailed design descriptions and interface specifications for each function in a data dictionary.
An example of an ATM system is used to illustrate the function-oriented design process. The document concludes by comparing function-oriented and
This document provides an overview of an online shopping portal project that was developed using PHP and MySQL. It includes sections on the introduction, need for an online shopping portal, problem analysis, project structure, software development life cycle, and feasibility analysis. The project aims to develop a graphical user interface based system to provide online shopping for various products like mobile phones, laptops, clothes, books and more.
This document provides an overview of an online shopping portal project that was developed using PHP and MySQL. It includes sections on the introduction, need for the online shopping portal, problem analysis, project structure, software development life cycle, hardware and software requirements, front-end details using PHP, back-end details using MySQL, and system design. The project aims to develop a graphical user interface based system to provide online shopping functionality for products like mobile phones, laptops, clothes, books and more.
The document discusses verification and validation of simulation models. Verification ensures the conceptual model is accurately represented in the operational model, while validation confirms the model is an accurate representation of the real system. The key steps are: 1) observing the real system, 2) constructing a conceptual model, 3) implementing an operational model. Verification techniques include checking model logic, output reasonableness, and documentation. Validation compares model and system input-output transformations using historical data or Turing tests. The goal is to iteratively modify the model until its behavior sufficiently matches the real system.
The document discusses the unified process and use case diagrams in software development. It introduces the unified process which is an iterative and evolutionary software development methodology consisting of inception, elaboration, construction, and transition phases. The document also covers use cases, actors, use case diagrams, and how use cases influence analysis, design, implementation, project management, and testing in object-oriented software development.
Stockzilla is a web based application that aims to predict the future value of the financial stocks of a company and helps the
traders in buying the right stock.
Rather than predicting stock price, this website also provide
various information to traders such as daily market updates, top
gainers and losers in the market, view close and open price in a
particular date, company details etc.
The document discusses the role of a business analyst in a software project. It explains that a business analyst is involved in requirements gathering and representation. This includes eliciting requirements through preliminary discussions with customers, reviewing requirements with other roles like architects and UX designers, and specifying requirements. Requirements can be represented through user stories, use cases, documents, and other methods. User stories are written from the perspective of users and define what they want to do. Use cases outline interactions between actors and a system. Together, clearly documented requirements help ensure a project delivers business value through the right software solution.
The document discusses the Unified Modeling Language (UML) and use case modeling. UML was developed to provide modeling languages for software design including use case diagrams, class diagrams, and other diagrams. It describes the typical phases of system development like requirements analysis, design, implementation, and testing. It then focuses on use case modeling, explaining what a use case is, how to identify actors and use cases, and how to describe use cases. Examples of use case diagrams are provided for different systems like an ATM machine and counseling.
The document describes the requirements for developing a mobile banking application called U-Mobile. It outlines the need for the app as people spend a lot of time visiting banks for transactions. The app will allow users to transfer money, recharge mobiles, and perform other banking activities without visiting a bank. The document includes sections on the problem statement, software requirements specification, use case diagram, activity diagrams, class diagram, sequence diagrams, communication diagram, state diagram, component diagram, and deployment diagram. The diagrams model the workflows and interactions between the user, admin, and system for various functions like transactions, recharges, and updating information.
This document provides an overview of use case diagrams and use cases. It defines what a use case is, including that it captures a user's interaction with a system to achieve a goal. It describes the key components of a use case diagram, including actors, use cases, and relationships between use cases like generalization, inclusion, and extension. An example use case diagram for a money withdrawal from an ATM is presented to illustrate these concepts. Guidelines for documenting use cases with descriptions of flows, exceptions, and other details are also provided.
Toll tax management system project report..pdfKamal Acharya
Toll Tax Management System is a web based application that can provide all the information related to toll plazas and the passenger checks in and pays the amount, then he/she will be provided by a receipt. With this receipt he/she can leave the toll booth without waiting for any verification call.
The information would also cover registration of staff, toll plaza collection, toll plaza collection entry for vehicles, date wise report entry, Vehicle passes and passes reports b/w dates.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help alleviate symptoms of mental illness and support overall brain health.
This document outlines the phases of developing an online shopping system, including project planning, modeling requirements through UML diagrams, software configuration management, and testing. Key modules include login, viewing and adding products, and updating quantities. The system allows customers to purchase products and administrators to manage the database. Programming is done in Visual Basic using forms and scripts to implement the system functionality.
This document outlines the phases of developing an online shopping system, including project planning, modeling requirements through UML diagrams, software configuration management, and testing. Key modules include login, viewing and adding products, and updating quantities. The system allows customers to purchase products and administrators to manage the database. Programming is done in Visual Basic using forms and scripts to implement the system functionality.
Payment Routing Module using Kafka StreamsIRJET Journal
This document proposes a payment routing module that uses Kafka Streams for stream processing to improve the efficiency of online payment systems. The routing module filters transaction data, calculates the success and failure rates of different acquirer banks in time windows, and queries this data to route new transactions to acquirers that are currently more reliable based on recent performance. Implementing this routing module could help lower transaction failure rates compared to relying solely on payment gateways for routing decisions. The methodology describes how the module would work using Kafka Streams functionality like tumbling windows to aggregate metrics for each acquirer and make informed routing choices.
The document discusses use case diagrams in object oriented design and analysis. It defines use cases as descriptions of system functionality from a user perspective. Use case diagrams depict system behavior, users, and relationships between actors, use cases, and other use cases. The key components of use case diagrams are described as actors, use cases, the system boundary, and relationships. Common relationships include association, extend, generalization, uses, and include. An example use case diagram for a cellular telephone is provided to illustrate these concepts.
This document discusses nested state diagrams and interaction modeling techniques. It addresses:
1. The use of submachine states and composite states to model nested states within a state diagram.
2. Interaction modeling approaches including use cases, sequence diagrams, and activity diagrams.
3. Guidelines for developing use cases, sequence diagrams, and activity diagrams to fully capture system behavior.
The document describes developing an online spice selling system that allows customers to order spices and services online by submitting orders before a cutoff time and receiving deliveries within a given window, with payment processed after items are picked but before delivery to allow for order changes. It provides an abstract, use case diagram, activity diagram, class diagram, sequence diagram, and state diagram for the system as well as an introduction and index.
The document discusses various interaction diagrams used in modeling systems, including use case diagrams, sequence diagrams, activity diagrams, and state charts. It provides examples and definitions for each type of diagram. For use case diagrams, it explains actors, scenarios, and different notations. Sequence diagrams show the sequence and timing of messages between objects to illustrate object interactions. Activity diagrams model business processes and workflows showing the flow of activities. State chart diagrams use states and transitions to model an object's behavior in response to events. The document also includes exercises to create interaction diagrams for various example systems and processes.
IRJET - Analysis & Study of E-Procurement System in Current ScenarioIRJET Journal
This document summarizes a research paper that analyzes e-procurement systems and online auctions. It begins with an abstract that outlines the goal of analyzing current auction forms and issues like developing effective auction systems and predicting final bid prices. It then covers sections that review the introduction of online auctions, prior literature on auction mechanisms and structures, the proposed system design including modules for authentication, administration, sellers and buyers, advantages over traditional auctions, problems addressed, and conclusions. The document provides details on the technical aspects and theoretical underpinnings of online auction systems.
This document discusses function-oriented design and compares it to object-oriented design. It begins by explaining function-oriented design and how a system is decomposed into a set of interacting functions that share a centralized system state. It then covers the key aspects of function-oriented design process, including:
1. Using data flow diagrams to model how data passes through the system.
2. Developing structure charts to show how high-level functions call lower-level subfunctions.
3. Creating detailed design descriptions and interface specifications for each function in a data dictionary.
An example of an ATM system is used to illustrate the function-oriented design process. The document concludes by comparing function-oriented and
This document provides an overview of an online shopping portal project that was developed using PHP and MySQL. It includes sections on the introduction, need for an online shopping portal, problem analysis, project structure, software development life cycle, and feasibility analysis. The project aims to develop a graphical user interface based system to provide online shopping for various products like mobile phones, laptops, clothes, books and more.
This document provides an overview of an online shopping portal project that was developed using PHP and MySQL. It includes sections on the introduction, need for the online shopping portal, problem analysis, project structure, software development life cycle, hardware and software requirements, front-end details using PHP, back-end details using MySQL, and system design. The project aims to develop a graphical user interface based system to provide online shopping functionality for products like mobile phones, laptops, clothes, books and more.
The document discusses verification and validation of simulation models. Verification ensures the conceptual model is accurately represented in the operational model, while validation confirms the model is an accurate representation of the real system. The key steps are: 1) observing the real system, 2) constructing a conceptual model, 3) implementing an operational model. Verification techniques include checking model logic, output reasonableness, and documentation. Validation compares model and system input-output transformations using historical data or Turing tests. The goal is to iteratively modify the model until its behavior sufficiently matches the real system.
The document discusses the unified process and use case diagrams in software development. It introduces the unified process which is an iterative and evolutionary software development methodology consisting of inception, elaboration, construction, and transition phases. The document also covers use cases, actors, use case diagrams, and how use cases influence analysis, design, implementation, project management, and testing in object-oriented software development.
Stockzilla is a web based application that aims to predict the future value of the financial stocks of a company and helps the
traders in buying the right stock.
Rather than predicting stock price, this website also provide
various information to traders such as daily market updates, top
gainers and losers in the market, view close and open price in a
particular date, company details etc.
The document discusses the role of a business analyst in a software project. It explains that a business analyst is involved in requirements gathering and representation. This includes eliciting requirements through preliminary discussions with customers, reviewing requirements with other roles like architects and UX designers, and specifying requirements. Requirements can be represented through user stories, use cases, documents, and other methods. User stories are written from the perspective of users and define what they want to do. Use cases outline interactions between actors and a system. Together, clearly documented requirements help ensure a project delivers business value through the right software solution.
The document discusses the Unified Modeling Language (UML) and use case modeling. UML was developed to provide modeling languages for software design including use case diagrams, class diagrams, and other diagrams. It describes the typical phases of system development like requirements analysis, design, implementation, and testing. It then focuses on use case modeling, explaining what a use case is, how to identify actors and use cases, and how to describe use cases. Examples of use case diagrams are provided for different systems like an ATM machine and counseling.
The document describes the requirements for developing a mobile banking application called U-Mobile. It outlines the need for the app as people spend a lot of time visiting banks for transactions. The app will allow users to transfer money, recharge mobiles, and perform other banking activities without visiting a bank. The document includes sections on the problem statement, software requirements specification, use case diagram, activity diagrams, class diagram, sequence diagrams, communication diagram, state diagram, component diagram, and deployment diagram. The diagrams model the workflows and interactions between the user, admin, and system for various functions like transactions, recharges, and updating information.
This document provides an overview of use case diagrams and use cases. It defines what a use case is, including that it captures a user's interaction with a system to achieve a goal. It describes the key components of a use case diagram, including actors, use cases, and relationships between use cases like generalization, inclusion, and extension. An example use case diagram for a money withdrawal from an ATM is presented to illustrate these concepts. Guidelines for documenting use cases with descriptions of flows, exceptions, and other details are also provided.
Toll tax management system project report..pdfKamal Acharya
Toll Tax Management System is a web based application that can provide all the information related to toll plazas and the passenger checks in and pays the amount, then he/she will be provided by a receipt. With this receipt he/she can leave the toll booth without waiting for any verification call.
The information would also cover registration of staff, toll plaza collection, toll plaza collection entry for vehicles, date wise report entry, Vehicle passes and passes reports b/w dates.
Similar to unified modeling language diagrams (20)
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help alleviate symptoms of mental illness and support overall brain health.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms for those who already suffer from conditions like anxiety and depression.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help boost feelings of calmness, happiness and focus.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise causes chemical changes in the brain that may help alleviate symptoms of mental illness and boost overall mental well-being.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms for those who already suffer from conditions like anxiety and depression.
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against developing mental illness and improve symptoms for those who already suffer from conditions like anxiety and depression.
The document discusses four topics: 1) English language is important as an international business language that opens new career opportunities through the internet and press. 2) Studying math and computer science develops analytical skills and knowledge of algorithms. 3) Current education systems put too much academic pressure on children and use obsolete assessment criteria. 4) There is a boom in software innovations and experts in computer science and software engineering can play an important role.
The document defines and compares different types of sentences:
- A sentence is a set of words that is complete in itself and typically contains a subject and predicate.
- Phrases are groups of words that do not express a complete thought.
- Clauses contain a subject and verb and can be independent or dependent.
- Simple sentences contain one independent clause. Compound sentences contain two or more independent clauses joined by coordinating conjunctions. Complex sentences contain one independent clause and at least one dependent clause. Complex-compound sentences contain at least two independent clauses and one or more dependent clauses.
Punctuation marks aid in clarity and comprehension of written language. Common punctuation includes periods, commas, question marks, exclamation points, apostrophes, quotation marks, and hyphens. Proper punctuation structures sentences and organizes writing, while lack of punctuation can make text difficult to understand. Different punctuation marks serve distinct functions, such as commas separating items in a list, semicolons joining independent clauses, and colons introducing a list or phrase.
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
How to Add Chatter in the odoo 17 ERP ModuleCeline George
In Odoo, the chatter is like a chat tool that helps you work together on records. You can leave notes and track things, making it easier to talk with your team and partners. Inside chatter, all communication history, activity, and changes will be displayed.
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
How to Manage Your Lost Opportunities in Odoo 17 CRMCeline George
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
A review of the growth of the Israel Genealogy Research Association Database Collection for the last 12 months. Our collection is now passed the 3 million mark and still growing. See which archives have contributed the most. See the different types of records we have, and which years have had records added. You can also see what we have for the future.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
This slide is special for master students (MIBS & MIFB) in UUM. Also useful for readers who are interested in the topic of contemporary Islamic banking.
Chapter 4 - Islamic Financial Institutions in Malaysia.pptx
unified modeling language diagrams
1. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
CONTENTS : Page No.
1. SCOPE 1
1.1 AUDIENCE
1.2 ORGANISATION
1.3 APPLICABLE DOCUMENTS
2. SOFTWARE REQUIREMENT SPECIFICATION 2
3. FUNCTIONAL MODEL 3
4. ACTIVITY DIAGRAM 8
5. USE CASE DIAGRAM 11
6. INTERACTION DIAGRAM
6.1.1 SEQUENCE DIAGRAM 19
6.1.2 COLLABORATION DIAGRAM 23
7. STATE CHART DIAGRAM 26
8. CLASS DIAGRAM 28
9. IMPLEMENTATION DIAGRAM
9.1 COMPONENT DIAGRAM 29
9.2 DEPLOYMENT DIAGRAM 31
RGIT, MUMBAI. Page 1 Department of MCA.
2. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
1. Scope :
The following subsections describe the scope of the fast food outlet system in
terms of its audience, organization, and applicable documents
1.1 Audience :
Customers, Administrators, Sellers.
1.2 Organization :
ONLINE SHOPPING CART SYSTEM
1.3 Applicable Documents :
The following documents provide information necessary to understand this
documentation:
RGIT, MUMBAI. Page 2 Department of MCA.
3. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
2 Software Requirement Specification:
System Abstract –
The Online Shopping Cart system facilitates the Customer to view the Items
Products, inquire about the item details, availability of seats and many more. The major
functionality of system is to allow the user to book and cancels the flights as per user
requirements. It also provides the administrator or manager to modify existing flights or
to introduce a new flight’s in the schedule.
Major features provided by the system are :
1. Customer
The system allows the user or member to perform flight qnuiry including flight
scheduling, seats availability status, fare details, etc.
2. Administrator
It allows the customer to register in order to give the services to its member .
3. Online shopping system
The system allows the member to order the product as per his/her requirements. The
customer is prompt to enter the customer details and credit card details. The member
then receives the unique cart number .
4. Product Listing
This process gives the details about the purchasing process made by the customer at
the details of the shipping and taxes involved with the cost
5. Administrator
The administrator module of the system allows the admin/manager to manage the
products item It provides the admin /manger to modify or change the existing items or to
introduce a new items. Apart from modifying the category it also allow the
admin/manager to take the taxes and include the shipping charges along with the h/w s/w
and service requirements.
RGIT, MUMBAI. Page 3 Department of MCA.
4. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
3. Functional Model.
Fig 3.1 Data Flow Diagram for Online Shopping Cart Software
RGIT, MUMBAI. Page 4 Department of MCA.
5. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Fig 3.2 Data Flow Diagram for Product Listing
RGIT, MUMBAI. Page 5 Department of MCA.
6. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Fig 2.3
Fig : 3.3Data Flow Diagram for Administrator.
RGIT, MUMBAI. Page 6 Department of MCA.
7. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Fig
Fig: Data Flow Diagram for Secure Gateway Provider.
RGIT, MUMBAI. Page 7 Department of MCA.
8. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
4. Activity Diagram.
• An Activity diagram is a visual representation of any system's activities and flows of data
or decisions between activities.
• Activity diagrams provide a very broad view of a business process.
• They represent the dynamics of a system.
• They are flow charts that are used to show the work flow of a system.
• They show the flow of control from activity to activity in the system.
• They show what activities can be done in parallel, and any alternative paths through the
flow.
• Purpose
• Model business workflows
• Model operations
• Activity diagrams commonly contain
• Activity states and action states
• Transitions
• Objects
Action States and Activity States
• Action states are atomic and cannot be decomposed
• Work of the action state is not interrupted.
• Activity states can be further decomposed
• Their activity being represented by other activity diagrams
• They may be interrupted
• Represented in UML by a rounded rectangle.
• Activity represents the performance of some behavior in the work flow.
Transitions
• Transitions are used to show the passing of the flow of control from activity to activity.
They are typically triggered by the completion of the behavior in the originating activity.
• When the action or activity of a state completes, flow of control passes immediately to
the next action or activity state
RGIT, MUMBAI. Page 8 Department of MCA.
9. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
• A flow of control has to start and end at some place
initial state -- a solid ball stop state -- a solid ball inside a circle
Branching
• When modeling the workflow of a system, it is often necessary to show where the
flow of control branches based on a decision point.
• The transition from a decision point contain a guard condition.
• The guard condition is used to determine which path from the decision point is taken.
• Decisions along with their guard conditions allow you to show alternative paths
through a work flow.
• A branch specifies alternate paths taken based on some Boolean expression
• A branch may have one incoming transition and two or more outgoing ones
Synchronization Bars
• In a workflow there are typically some activities that may be done in parallel.
• A synchronization bar allows you to specify what activities may be done
concurrently.
• A synchronization bar may have
– many incoming transition and one outgoing transition, or
– one incoming transition and many outgoing transitions.
• It is use to specify the forking and joining of parallel flows of control
• A synchronization bar is rendered as a thick horizontal or vertical line
• A fork may have one incoming transitions and two or more outgoing transitions
– each transition represents an independent flow of control
– conceptually, the activities of each of outgoing transitions are concurrent
• either truly concurrent (multiple nodes)
• or sequential yet interleaved (one node)
RGIT, MUMBAI. Page 9 Department of MCA.
10. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
• A join may have two or more incoming transitions and one outgoing transition
– above the join, the activities associated with each of these paths continues in
parallel
– at the join, the concurrent flows synchronize
– each waits until all incoming flows have reached the join, at which point one
flow of control continues on below the join
RGIT, MUMBAI. Page 10 Department of MCA.
11. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
view the
product
customer
visit faq Item not found
want to purchase?
no
yes
product avilable in india? no
yes
go through the
product details
are u member?
Login
Register
yes
no
shopping cart is
assigned to customer
item get added
to shopping cart
confirm the shopp...
generate purchase
details
payment
details
yes
payment on
delivery
getway system
activated
no
yes
paying by creditcard?
no
yes
want to purchase?
final bill
no
varification of customer?
yes
Fill feedback
yes
signout
no
want to fill feedback?
Cancel
Product
no
yes
do you want to cancel the product?
no
RGIT, MUMBAI. Page 11 Department of MCA.
Fig 4.1 Activity Diagram :
12. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
5. Use-Case Diagram.
• The use-case concept was introduced by Ivar Jacobson in the object-oriented software
engineering (OOSE) method.
• A use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary,
communication (participation) associations between the actors and the use cases, and
generalization among the cases.
• Use case diagrams show how users interact with the system.
• Use case diagrams describe what a system does from the standpoint of an external observer.
The emphasis is on what a system does rather than how.
• Use case diagrams are closely connected to scenarios. A scenario is an example of what
happens when someone interacts with the system. Here is a scenario for a medical clinic.
"A patient calls the clinic to make an appointment for a yearly checkup. The receptionist
finds the nearest empty time slot in the appointment book and schedules the appointment
for that time slot. "
• Used during requirements elicitation to represent external behavior
• Actors represent roles, that is, a type of user of the system
• Use cases represent a sequence of interaction for a type of functionality
• The use case model is the set of all use cases. It is a complete description of the functionality
of the system and its environment
Actors
• An actor models an external entity which communicates with the system:
oUser
oExternal system
oPhysical environment
• An actor has a unique name and an optional description.
• Examples:
• Passenger: A person in the train
• GPS satellite: Provides the system with GPS coordinates
Use Cases
A use case represents a class of functionality provided by the system as an event flow.
A use case consists of:
• Unique name
• Participating actors
• Pre-conditions
• Entry conditions (triggers)
• Flow of events
• Exit conditions (success ‘guarantees’)
RGIT, MUMBAI. Page 12 Department of MCA.
Customer
Item Purchased
13. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
• Special requirements
The Use Case diagram for whole system is as shown in fig 5.3
The <<extend>> Relationship
• <<extend>> relationships represent exceptional or seldom invoked cases.
• The exceptional event flows are factored out of the main event flow for clarity.
• Use cases representing exceptional flows can extend more than one use case.
• The direction of a <<extend>> relationship is to the extended use case
The <<include>> Relationship
• An <<include>> relationship represents behavior that is factored out of the use case.
• An <<include>> represents behavior that is factored out for reuse, not because it is an
exception.
• The direction of a <<include>> relationship is to the using use case (unlike <<extend>>
relationships).
Fig :5.1 Use Case Diagram
RGIT, MUMBAI. Page 13 Department of MCA.
Select shipping address
Add shipping address
Add Credit card type Add Credit card number
Add credit card
Add Expiration date
Choose shipping type
Online customer
Select credit card
<<include>>
<<include>>
<<include>
>
<<include>>
<<include>>
<<include>>
14. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
<<include>>
Pay Bill
Prepare Bill
Validate Customer
Administrator
Update Items
Register Customer
Customer
Search Item
Registered
Customer Buy Item
<<include>>
<<include>>
<<include>>
Fig 5.2 Use case Diagram
RGIT, MUMBAI. Page 14 Department of MCA.
15. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
USE CASE DESCRIPTION :
Actors:
2.1 New Customers
2.2 Registered Customer
2.3 Administrator
Use cases:
1. Search Item
2. Register Item
3. Buy Item
4. Update Item
1. Search Item
Any user can search the item. User can search the item by name or company.
2. Register Customer
To buy the item, the customer has to be a registered customer. This process is used to register
a customer.
3. Buy Item
A registered customer can buy a item using this process. This process include search item,
validate customer, prepare bill, pay bill.
RGIT, MUMBAI. Page 15 Department of MCA.
16. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Use Case Table
Use case ID 1
Use case name View shopping cart
Actor Online customer
Pre-condition Open the website
Post-condition Search for product
Flow of events open the website of online shopping cart
Use case ID 2
Use case name Search for product
Actor Online customer
Pre-condition View shopping cart
Post-condition Select the product
Flow of events Open the website, search the product from list
Use case ID 3
Use case name Create new user
Actor Online customer
Pre-condition Select the product
Post-condition Select credit card
Flow of events Open the website, search the product from list, select the product, create
new user
RGIT, MUMBAI. Page 16 Department of MCA.
17. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Use case ID 4
Use case name Purchase item
Actor Online customer
Pre-condition Select credit card
Post-condition Review order information
Flow of events Open the website, search the product from list, select the product, create
new user, select credit card, purchase the selected item
Use case ID 5
Use case name Login as registered user
Actor Online seller and online customer
Pre-condition Open the website
Post-condition Sell or purchase the product
Flow of events Open the website, Login as registered user
Use case ID 6
Use case name Item registration
Actor Online seller
Pre-condition Login into the shopping cart system
Post-condition Confirm the registration
Flow of events Open the website, Login as registered user, register the item into system
RGIT, MUMBAI. Page 17 Department of MCA.
18. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Use case ID 7
Use case name Change the information
Actor administrator
Pre-condition Login into the system as administrator
Post-condition Update the system
Flow of events Open the website, Login as administrator, make changes in the information
Use case ID 8
Use case name Block users
Actor administrator
Pre-condition Select the user
Post-condition Update the system
Flow of events Open the website, Login as administrator, select the user, block the user
Use case ID 9
Use case name Inform the deal to seller
Actor Online Seller and shopping cart system
Pre-condition Check the availability of item
Post-condition Make a deal
Flow of events Open the website, login as shopping cart system , seller sell the item to
shopping cart system, inform the deal to seller
RGIT, MUMBAI. Page 18 Department of MCA.
19. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
fig 5.3. Use case diagram for Online Shopping System
6. UML Interaction Diagram
6.1 Sequence Diagram :
RGIT, MUMBAI. Page 19 Department of MCA.
Register Item
Search for product
Choose shipping type
Select credit card
Purchase item
Review order confirmation
View shopping cart
Add item to shopping cart
Login as registered user
Online seller
Shopping Cart system
Inform the deal to seller
Block users
Administrator
Change item informationOnline Customer
Create new user
20. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
user
Shopping cart
system
Administrator
User Login
user name & password
gives the details
give access to member
Fig.6.1.1 Sequence Diagram for User registeration
: Online seller
Administrator
Item Registration
Log out();
Fig.6.1.2 Sequence Diagram for Seller registeration
RGIT, MUMBAI. Page 20 Department of MCA.
21. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Cart item
: Online
Customer
Shopping cart Process
order
Order
summary
Logout
Adds Item
Gets Item
Product Details
Taxes
Processes
Add the products
Taxes
Displays the Orderd ItemDisplays the ordered item
ConfirmsConfirms
CheckoutChecks Out
Processes
Payment Details
Shipping Charges
Fig.6.1.3 Sequence Diagram for Online Customer
RGIT, MUMBAI. Page 21 Department of MCA.
22. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
:Online Customer
Shopping
system
Cart system Ordering
system
Login
Add item
Add category
Add user
Delete user
Change password
Delete item
Delete category
Logout
Fig.6.1.4 Sequence Diagram for Online Administrator
RGIT, MUMBAI. Page 22 Department of MCA.
23. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
6.2 Collaboration diagrams:
They are also interaction diagrams. They convey the same information as sequence
diagrams, but they focus on object roles instead of the times that messages are sent. In a
sequence diagram, object roles are the vertices and messages are the connecting links.
• Collaboration diagrams show (used to model) how objects interact and their roles.
• They are very similar to sequence diagrams. Actually they are considered as a cross
between class and sequence diagram.
• Sequence Diagrams are arranged according to Time.
• Collaboration Diagrams represent the structural organization of object.
• [Both sequence and collaboration diagrams are called interaction diagrams]
• Forms a context for interactions
o May realize use cases
o May be associated with operations
o May describe the static structure of classes
• Collaboration diagrams contain the following:
o Class roles (subsystems/objects/classes/actors/ external systems) as before.
o Association roles (pathways or links over which messages flow)
o Message flows (messages sent between class roles)
user Shopping cart
system
Administrator
User Login
user name & passwordgives detail
give access to member
1:
4:
2:3:
Fig.6.2.1 Collaboration Diagram for User registration
RGIT, MUMBAI. Page 23 Department of MCA.
24. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
: Online seller
Administrator
Item registration
log out();
1:
2:
Fig.6.2.2Collaboration Diagram for Seller registeration
: Online customer
Shopping
cart
Logout
Order
summary
Process
order
Cart item
1: Adds Item
11: Checkout
2: Gets Item
9: Displays the Orderd Item
10: Confirms
3: Product Details
4: Add the products
6: Taxes
8: Processes
7: Payment Details
5: Shipping Charges
Fig.6.2.3 Collaboration Diagram for Online Customer
RGIT, MUMBAI. Page 24 Department of MCA.
25. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
:Online Customer
Shopping
system
Cart
system
Ordering
system
1: Logiin
9: Logout
2: Add item
3: Add category
7: Delete item
8:Delete category
4: Add user
5: Delete user
6:Change password
Fig.6.2.4 Collaboration Diagram for Online Administrator
RGIT, MUMBAI. Page 25 Department of MCA.
26. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
7. Statechart Diagram:
The name of the diagram itself clarifies the purpose of the diagram and other details. It
describes different states of a component in a system. The states are specific to a
component/object of a system.
A Statechart diagram describes a state machine. Now to clarify it state machine can be
defined as a machine, which defines different states of an object, and these states are
controlled by external or internal events.
transaction Processed
Member
Logging
Verifying
Re-Logging
Transaction
Performing
Printing
Ticket
Reserving
Accessing the
account
managing
account
Credit card
Processing
Cancelling
Member Login
Member Relogin
Invalid >3 times
Invalid Login
Valid login
Member Access
Perform Reservation
Perform cancellation
Process credit card details
Process credit card details
Transaction Processing
Fig.7.1 State Chart diagram for Online Shopping System
RGIT, MUMBAI. Page 26 Department of MCA.
27. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
buy the item
Searching Selecting
Buying
Pay bill
Register
registered customer
new customer
more items buy item
item selection over
Fig7.2 State diagram for customer.
RGIT, MUMBAI. Page 27 Department of MCA.
28. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
8. CLASS DIAGRAM :
Fig 8.1 Class diagram for Online Shopping System
RGIT, MUMBAI. Page 28 Department of MCA.
TRANSACTION
transid
pnrno
transdate
amt
commit()
rollback()
Payment System
custno
custid
custname
creditcardno
BillingAddress
VeiwOrder()
PaymentDetails()
ONLINE SHOPPING CART
SYSTEM
HTTP
CartAddition
Creidtno : String
Description : String
ItemId : String
Amount : Integer
Category : String
Get_to_cart()
Check_out()
CANCELLATION
cusno : Integer
Item id : Integer
amount : Integer
retrive()
update()
CREDIT CARD HOLDER
cardno
issuedate
expirydate
verifydtls()
perform_transaction()
CUSTOMER
Number of Item : Integer
cusid : Integer
Shipnname : String
Company : String
Address : String
Payment()
CartAddition()
Cancellation()
USER
Email id : String
password : String
First name : String
Last Name : String
Street Address : String
ZipCode : Integer
City : String
State : String
Country : String
Phone : String
Login()
Registration()
Logout()
SELLER
Item name : String
Item id : Integer
Discount : Integer
Categoty : Integer
29. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
9.Implementation Diagram.
9.1Component Diagram :
Component diagrams are different in terms of nature and behavior. Component diagrams
are used to model physical aspects of a system.
Physical aspects are the elements like executables, libraries, files, documents etc that
resides in a node. So component diagrams are used to visualize the organization and
relationships among components in a system. These diagrams are also used to make executable
systems.
Description of the component diagram for online shopping system is as follows :
Data base server contains all the database tables. It contains Administrator, Registered
Customer, Seller, Item and Payment.
Application server contains Access classes package and Business classes package and view
layer classes, i.e. view classes package.
Clients are the nodes having no processing capabilities. Only browser is there on this node
to send a request
RGIT, MUMBAI. Page 29 Department of MCA.
30. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
Payment
View Classes
Home Page
Login
Form
Searching
Form
Registration
Form
Updation
Form
Ordering
Form
Payment
form
Business Classes
Registered
Customer
Seller
Administrator
Access Classes
Access
Database
Component Diagram :
RGIT, MUMBAI. Page 30 Department of MCA.
31. Object Oriented Modeling and Design ONLINE SHOPPING CART
SYSTEM
9.2 Deployment Diagram :
Deployment diagrams are used to visualize the topology of the physical components
of a system where the software components are deployed.
So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.
.
Application Server.exe
Data Base
Server
Application
Server
Client
Client
Client
<<Private Network>>
<<Private Network>>
<<Private Network>>
<<LAN>>
Oracle Server
Fig 9..2 Deployment diagram for Online Shopping System.
RGIT, MUMBAI. Page 31 Department of MCA.