E commerce online food ordering system

The disallow likewise provides the calling taking into custody that should e incorporate into message implementation guides and other user documentation as well as supporting re-use of artifacts indoors the hackneyeds development do by. 3 Audience The main audiences for this document ar the potential authors of individual Bars. These be primarily the ANNUNCIATE product line and IT experts who ar responsible for specifying the calling requirements for e-business or e-government solutions in a specific athletic field and for progressing the development of solutions as relevant standards.Authors whitethorn include other standards bodies or users and developers in developed or evolution economies. Reference Documents Knowledge and application of the following standards is crucial to the development of quality business requirements specifications. otherwise key references are shown in the appropriate part of the document. UN/CAVEAT. Techniques and Methodologies Group (TM ). ASPECTS object lessoning Methodology (MUM) MUM Meta Model Core Module. (Candidate for 2. 0). 2009-01-30. Methodology (MUM) MUM Meta Model Foundation Module. Candidate for 2. 0). Formal translations of many of the technical arouse utilise in this BARS specification whitethorn be found in the above references barely for convenience some key definitions are included in Appendix loft this document. 5 spirit of BARS 2. 0 A BARS is designed to capture the requirements that a business, government or field has for an e-commerce solution in a particular area of business (I. E. Domain) and to achieve it in such a way that it provides a basis for a subsequent standards development process within ANNUNCIATE.Version 2 of the BARS documentation sc go forth requires that the business requirements are first specified in business price and that these requirements are then expressed formally as ML diagrams or worksheets that aid standardization and provide IT practitioners with the in evitable retracts from which to develop formal specifications. By facilitating consistent documentation of business collaborations in the midst of participants, the BARS 2. 0 template supports the standardization and harmonistic of business processes and encourages re-use of the resulting artifacts in part or as a whole.This consistency, achieved by means of the systematic specification of requirements in the BARS, is vital if resulting e-business systems are to be interoperable. A constitute specification of business requirements enables traceability in the midst of requirements and supporting the quality assurance process. As the BARS provides the description of the equines processes and identifies the business reading needed to support those processes, it sack provide the necessary business understanding to enable successful data harmonistic.It also provides the business understanding that must be incorporated when developing message implementation guides and other user do cumentation. The use of a modeling tool that is designed or configured to support Version 2. 0 of the MUM willing enable the majority of the content of a BARS to be generated automatically. This document may also be considered as a resource to support capacity building in developed or developing economies. 1 Overview of BARS Development Process A BARS must(prenominal) start with a clear specification of the area of the project and where this project fits into a global context of business operations and whitethorn refer to a MUM model of the business domain. The Scope MUST be specified in terms of the telephone circuit Processes that are involved and the calling Entities about which development is to be exchanged by the participants who are involved directly in the Information Exchanges that support the related business process.It MUST also indicate stakeholders who need an interest in the processes, or may participate in elated processes, and whenever appropriate, what is out of scope of this particular project. The process and selective information flows that constitute the business process, the business rules that govern the exchanges and the details of the information that is to be exchanged during these processes, SHOULD then be elaborated.The requirements MUST first be specified in business terms and then expressed in formalized terms. The business requirements MUST be presented as a numbered list so as to facilitate a check to be made that all requirements have been met in the eventual e-commerce solutions proposed. As the process of completing a BARS progresses, new requirements may be recognized and added to the list. The resulting BARS will include text, templates (worksheets) and diagrams, and may refer to a MUM model of the domain.To serve with future re-usability, interoperability and to provide a degree of standardization in the developing a BARS, an initial throttle of preferred terms is provided in Annex 2. To minimize the work in crea ting a new BARS, mend harmonistic and encourage risibility, where ever possible, any relevant existing Bars artifacts or MUM models SHOULD be use as a basis for producing the ewe requirements. A high level BARS MAY be employ to define the context and scope of a domain that is refined by a cascade of more(prenominal) specific Bars. . 2 BARS Business Requirements 5. 2. 1 Scope of Project The Scope of the project MUST be identified in terms of the Business Processes to be covered the key types of information that are to be exchanged in the processes and the types of participants that are involved directly or indirectly in providing or using the information exchanged. The place of this project within the wider business domain SHOULD be identified. For example projects in the International SupplyChain, this SHOULD be positioned with respect to the international supply chain be made to industry or sector models and to the Business Area/Process Area classification specified in the Comm on Business Process catalogue. The Context categories , as specified in ACTS, SHOULD be used to help specify or limit the scope of the project. 5. 2. 2 Requirements List As they are discovered, the business requirements MUST be added to a numbered list .This list will cover The business transactions between participants, the participant who initiates the activity, the participant who responds and the business conditions that govern the initiation and responses. Other business rules governing the Information Exchanges. The key classes of information (Business Entities), the detailed data (attributes) about these Entities that are to be exchanged, and the relation between the Entities. 5. 2. 3 Definitions The names and definitions of each of the business terms and data items used MUST be listed and SHOULD be added as they are discovered in the process of completing the BARS. . 2. 4 MUM spielation of Business Requirements The business requirements MUST be formalized as appropriate ML artifacts, (exercising Case Diagrams, employment Diagrams, Class Diagrams and Business Entity Life Cycle Diagrams) or worksheets, by following the Insufficient Modeling Methodology (MUM). 5. 2. 5 The UN/CAVEAT Modeling Methodology MUM An dodge description of the MUM process is given below and examples of artifacts that should form part of the BARS are shown in section 7.The MUM consists of three main views The Business Requirements conniption enables the Business Information and Business Processes describe in the first part of the BARS to be more formally described. The Business Choreography View shows how the Business Processes may e created from a choreographed set of Business Transactions and the information exchanged in each transaction identified as Information Envelopes. The Business Information View identifies the content of these information envelopes based on the specific data and syntax standards and is the substance of the related RSI.Figure 1 MUM scheme MUM Business Requirements View This presents the view of the domain, the business processes, the participants and the Business Entities involved. They are detailed in the Business Domain View, Business Partner View and Business Entity View. The Business Domain View This view identifies the scope of the domain in terms of the processes it covers. The Business Area Process area classification may be used to classify the business processes that make up the domain. Each business process is represented by an Activity diagram, Use Case Diagram and Business Process Worksheet .These document the Business Partner Types that are set-aside(p) in the information governing the initiation of each Information Exchange. The state of the Business Entity resulting from each information exchange is shown in the activity diagram. Business Partner View The business partner view captures a list of business partners and stakeholders in the domain under consideration as well as the relationships between them. Busines s Entity View The range of states that a Business Entity may assume and the order in which they may occur as a result of the various information exchanges are documented in a Business Entity Life Cycle diagram.This View MAY also contain Conceptual models that present a business view of the Information and the relationships between the Classes identified. The Conceptual Model is assembled from the list of business requirements and expressed through the use of class diagrams. These describe the necessary classes of information, the relationship between the different classes and the required attributes that are to be found within each class.Each of these pieces of information should be fully described in the business definition section. It is important to stress that the class diagram for a Business Entity should reflect the information requirements expressed in business terms. Business Choreography View This shows how the Business Processes identified in the Business Requirements View may be represented as one or more Business Transactions and the necessary hieroglyph to enable the full functionality of each Business Process to be achieved.It consists of the Business Transaction View, Business collaboration View and Business Realization View Business Transaction View The business transactions between each pair of data exchange participants that are part of the full Business Process are identified and described in a Transaction Worksheet and illustrated as Use Case diagrams . Six standard transaction patterns are identified within the JIM. Two of these represent participants send and receiving information (Information distribution, Notification) and four represent artisans sending and responding (Query Response, Request Response, Request Confirm, Commercial Transaction).Each transaction is further detailed in terms of the name of the Information Envelopes sent or received the Authorized roles exercised by the sender and receiver the Activities that action the sen ding or receiving of the Information Envelope the conditions that cause the transaction to start or that exist as a result of the exchanges . Business Collaboration View The sequence or order in which the set of business transactions that make up the lull business process is specified using a Use Case Diagram and an Activity diagram in the MUM Business Collaboration View.