E commerce online food ordering system

The interdict excessively fork ups the telephone line beneathstanding that should e incorporated into substance implementation guides and other user documentation as well as supporting re-use of artifacts at bottom the standards development assist. 3 rockening The main audiences for this document be the potential authors of individual Bars. These ar earlier the ANNUNCIATE line of merchandise and IT experts who are responsible for specifying the business requirements for e-business or e-government solutions in a specific domain and for progressing the development of solutions as relevant standards.Authors whitethorn include other standards bodies or users and developers in developed or create economies. Reference Documents Knowledge and application of the following standards is crucial to the development of fictitious character business requirements specs. Other insinuate references are shown in the take over dower of the document. UN/CAVEAT. Techniques and Metho dologies Group (TM). ASPECTS Modeling methodological analysis ( soundless) dumb Meta Model Core Module. (Candidate for 2. 0). 2009-01-30. Methodology (MUM) MUM Meta Model Foundation Module. Candidate for 2. 0). Formal definitions of many of the adept legal injury used in this interdict condition may be gear up in the above references but for convenience some key definitions are included in Appendix loft this document. 5 single-valued function of BARS 2. 0 A BARS is designed to capture the requirements that a business, government or sector has for an e-commerce solution in a limited battleground of business (I. E. Domain) and to achieve it in such a direction that it proffers a basis for a subsequent standards development process within ANNUNCIATE.Version 2 of the BARS documentation template requires that the business requirements are commencement ceremony specified in business basis and that these requirements are then convey formally as ML diagrams or worksheets tha t aid standardization and provide IT practitioners with the required retracts from which to develop formal specifications. By facilitating consistent documentation of business collaborations between players, the BARS 2. 0 template supports the standardization and harmonistic of business processes and encourages re-use of the resulting artifacts in go away or as a whole.This consistency, achieved through the systematic specification of requirements in the BARS, is vital if resulting e-business systems are to be interoperable. A clear specification of business requirements enables traceability between requirements and supporting the quality assurance process. As the BARS provides the description of the equines processes and identifies the business data needed to support those processes, it can provide the necessity business understanding to enable successful data harmonistic.It also provides the business understanding that must be incorporated when ontogenesis message implementation guides and other user documentation. The use of a forgeing turncock that is designed or configured to support Version 2. 0 of the MUM will enable the majority of the content of a BARS to be generated automatically. This document may also be considered as a resourcefulness to support capacity building in developed or developing economies. 1 Over belief of BARS Development address A BARS moldiness start with a clear specification of the scope of the reckon and where this project fits into a global context of business operations and MAY refer to a MUM model of the business domain. The Scope must(prenominal) be specified in terms of the backing bringes that are gnarled and the barter Entities about which knowledge is to be counterchanged by the participants who are involved forthwith in the learning Exchanges that support the related business process.It MUST also indicate stakeholders who have an interest in the processes, or may participate in elated processes, and whene ver appropriate, what is out of scope of this particular project. The process and tuition flows that constitute the business process, the business rules that govern the replacements and the details of the training 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 rock so as to facilitate a check to be invite that all requirements have been met in the eventual e-commerce solutions proposed. As the process of complete a BARS progresses, new requirements may be recognized and added to the distinguish. The resulting BARS will include text, templates (worksheets) and diagrams, and may refer to a MUM model of the domain.To suffice with future re-usability, interoperability and to provide a degree of standardization in the developing a BARS, an initial set of preferred terms is provided in Annex 2. To mi nimize the work in creating a new BARS, better harmonistic and encourage risibility, where ever possible, any relevant existing Bars artifacts or MUM models SHOULD be used as a basis for producing the ewe requirements. A high level BARS MAY be used to mold the context and scope of a domain that is refined by a cascade of more specific Bars. . 2 BARS crease Requirements 5. 2. 1 Scope of Project The Scope of the project MUST be swan in terms of the dividing line 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 determine. 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 i n the Common 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 installing 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(prenominal) 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 model of Business Requirements The business requirements MUST be formalized as appropriate ML artifacts, (Use sideslip Diagrams, action mechanism Diagrams, Class Diagrams and Business Entity Life turn Diagrams) or worksheets, by following the Insufficient Modeling Methodology (MUM). 5. 2. 5 The UN/CAVEAT Modeling Methodology MUM An outline 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 assimilate enables the Business Information and Business Processes described in the first part of the BARS to be more formally described. The Business Choreography depend shows how the Business Processes may e created from a choreographed set of Business minutes and the information exchanged in each transaction identified as Information gasbags. The Business Information aspect identifies the content of these information envelopes establish on the specific data and syntax standards and is the substance of the related RSI.Figure 1 MUM Outline MUM Business Requirements soak up This presents the view of the domain, the business processes, the participants and the Business Entities involved. They are detailed in the Business Domain take care, 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 eggshell Diagram and Business Process Worksheet .These document the Business Partner Types that are engaged 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 supply view captures a list of business partners and stakeholders in the domain under consideration as well as th e relationships between them. Business Entity View The range of states that a Business Entity may assume and the secern in which they may occur as a result of the various information exchanges are documented in a Business Entity Life make pass 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 collaborationism 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 sending and receiving information (Information distribution, Notification) and four represent artisans sending and responding (Query Response, pray 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 send er and receiver the Activities that action the sending or receiving of the Information Envelope the conditions that cause the transaction to start or that exist as a result of the exchanges . Business coaction View The sequence or order in which the set of business transactions that make up the tranquillize business process is specified using a Use Case Diagram and an Activity diagram in the MUM Business Collaboration View.