The first project to be analyzed is Design and Implementation of an Ordering system using UML, Formal specification and Java Builder. The case study is based initially on the following informal context specification: A computer store wants to acquire an automated tool for orders. The order is made on behalf of a registered customer. An order consists of a number of items in the stock. The system should keep track of the stock level of each item. The order is either pending or serviced. The first strategy is that an order is serviced only if the stock level meets the request. An invoice is made at the time of servicing the order. The second strategy is that an invoice is based on the current item prices; the time when the order is being serviced.
The second project of choice was the Real Estate Web Site, which shall provide my client (an actual realtor) the ability to showcase and manage their property listings while allowing potential clients a concise and structured way of searching properties. The web site will be set up in a way the realtor will have total administrative rights to their listings. This web site will be developed for one realtor, but will be able to accommodate the needs of any realtor in the real estate career.
The third project of choice was the Web based auction system using UML and components. The web-enabled auction system uses four UML Diagrams and three components that are reusable at the specification level. For the UML notation to be effectively applied, it must be used in conjunction with an Object-Oriented Analysis and Design method. OOAD describes a community of methodologies for producing business component based software. The methodology outlines the system development lifecycle identifying the tasks and deliverables in an object-oriented project. Using a combination of UML notation and Object-Oriented Analysis and Design process, we can reduce the system development life cycle, easily maintain the system, and improve the reusability of modules. Component-based programming also results in maintainable and reusable code.
Case Study 1:
- S_Essential: (by user)
- Place Order
- Order Change
- Open System
- Book Order
- Order Details
- Change in order
- Select payment method
- Service order
Case Study 2:
Purpose: The register function allows an agent/realtor to register with the Real Estate web site so they can list properties.
- The agent/realtor navigates to the Real Estate web site.
- The agent/realtor clicks the “Register” link on the top of the homepage.
- The agent/realtor enters the required information such as their first name, last name, password, password confirmation, E-Mail address, E-Mail address confirmation, phone numbers, address, city, state, zip code, and among others.
- The agent/realtor clicks the “Register” button
Administrator – Edit Listing:
Purpose: The administrator – edit listing function allows an administrator to make changes to the information associated with a listing.
- The agent/realtor navigates to the Real Estate web site.
- The agent/realtor enters their e-mail address and password.
- The agent/realtor clicks the “Login” button.
- The administrator navigates to the control panel page.
- The administrator clicks the “Edit Listings” in the administrator control panel.
- The administrator selects the listing to edit.
- The administrator makes changes.
- The administrator clicks the “Submit Listing” button.
- Web UI
- Give Details
- Open website
- Click register
- Enter the required information such as their first name,
- Last name,
- Password confirmation,
- E-mail address,
- E-mail address confirmation,
- Phone numbers,
- Zip code
- Clicks the “register” button
Case Study 3:
- Search good
- Select auction type
- Select bidding type
- Buy product
Analysis & Results:
S_essential = the number of user steps in the essential use case narrative
S_enacted = the number of steps needed to perform the use case with the user interface design (rules for counting the number of enacted steps has come in the reference).
- Use Case1: 3
- Use Case2: 4
- Use Case3: 7
- Use Case1: 7
- Use Case2: 13
- Use Case3: 14
Calculation of Essential Efficiency
EE = 100 × Sessential / Senacted
Step 6. Calculation of Essential Efficiency EE = 100 × Sessential / Senacted
S_essential = The number of user steps in the essential use case narrative
S_enacted = The number of steps needed to perform the use case with the user interface design (rules for counting the number of enacted steps has come in the reference)
EE = 50 % Revealed that the login interface design is not good enough. Therefore, there is need to improve the given login interface to be more user friendly by reducing the number enacted use case.
In the first case study they effectively executed the Sales requesting framework as depicted in this paper. The main lesson scholarly is that UML utilization case graphs are ended up being important for inspiring data about framework useful necessities and speaking with potential clients. They additionally served to us different in the middle of utilitarian and non-practical prerequisites. Utilization case charts were utilized amid framework confirmation stage to test that all the functionalities are executed. Class charts are utilized with the end goal of outlining and actualizing our framework in an article arranged methodology. The code for constant item was specifically produced from their individual class charts.
Formalization of the framework state has helped us to thoroughly comprehend the substances and connections that may exist in the framework. Future work identifying with this framework executed in light of UML configuration would be the examination of what are the fundamental adjustments on the off chance that the framework is changed from consecutive document based framework to how about we say’s to Oracle database framework.
The motivation behind second Software Requirements Documentation is to give abnormal state and point by point portrayals of the Real Estate Web Site. This Software Requirements Documentation will give quantifiable prerequisites of the site for utilization by the fashioner and the clients of the Real Estate Web Site. The Real Estate Web Site might give my customer (a genuine real estate agent) the capacity to showcase and deal with their property postings while permitting potential customers a compact and organized method for looking properties. The site will be set up in a manner the real estate broker will have absolute managerial rights to their postings. This site will be created for one broker, however will have the capacity to oblige the needs of any real estate agent in the land vocation.
The third paper depicted a contextual analysis highlighting the best practices in planning and building an electronic closeout framework. We outlined the sale framework utilizing UML. The Use Case Diagram, Sequence Diagram, Class Diagram and Component Diagram offered by UML were utilized effectively amid the procedure. Discerning Rose, utilized for the reason, if satisfactory backing. Our execution, with its premise in part based programming empowered us to add to an exceedingly viable framework with various reusable parts. Further, the framework utilized insightful operators that allowed reasonable help to bidders taking an interest in barters, and in the meantime, attained to most extreme benefit for the vender. Once more, the execution environment and the apparatuses utilized, gave fabulous backing to the effective improvement of the framework.
The methodology sketched out here was more powerful in executing our closeout framework than the current Data Engineering (information situated), Structured Development (capacity arranged), or Object-arranged (information situated and capacity arranged) technique. In spite of the fact that we just rolled out a couple of particular improvements to the segments, these progressions show that consequent changes to other framework parts will be clear. Thus, the reusability of the framework was encouraged and, as a direct result, we expect that the framework will be effortlessly ready to suitably develop in the quick changing Internet environment. Our arrangements for future work incorporate the execution of the bartering framework utilizing Object-Z for formal particular and scientific calculations like VCG. Object-Z is an item situated formal particular dialect that is in view of Z, and has been created at the University of Queensland, Australia. Augmentations to the semantics of Z incorporate certain backing for article personality, together with thoughts of legacy and polymorphism. Further, we plan to create extra calculations that can be utilized for investigating the other aggressive bidder’s desire cost. We then arrangement to analyze the outcomes, regarding imperfection rate and level of practicality and reusability attained to, from these two separate methodologies.