06-10-2016, 12:28 PM
1458021589-seaddonprograms1.docx (Size: 119.96 KB / Downloads: 5)
I. Aim: Draw an UML diagrams (Use case and Sequence Diagrams) for ONLINE AUCTION.
Theory: The main objective of this project ONLINE AUCTION is to make the process of auction computerized. So that seller can sell their products details on the internet and get them sold. This process introduces an online solution to the current auction process that includes the auctioneer to inform all the bidders to attend the auction and make bids for the available products personally. This causes wastage of time and burden to both the auction and bidders. Our online solution makes all the things by internet. It is just enough for the sellers to place their product in the internet and the bidders can place their bids through internet itself by sitting in his/her home. The particular bidder who won the auction will be informed and require pay off the money and collecting the product.
The main objective of the project is to develop an application which provides an ONLINE AUCTION UML: The UML is a graphical language for specifying, visualizing, constructing, and documenting. All the three major stages of Object Oriented Development such as OOA, OOD and OOP can make use of UML.
Advantages of modeling:
• Makes easy to enhance and manipulate the existing system.
• Helps in visualizing the system to be developed.
• Permits to specify the structure and behaviour of the system.
• Used as a template to construct a proposed system.
• For capturing the requirements
Software Engineering Activities
1. Requirement elicitation
2. Analysis
3. System design
4. Object design
5. Implementation
6. Testing
Actors identified in the system are:
Customer
In this system, customer plays two roles: bidder and seller. The customer has to enrol in order to login to the system.
Bidder
The bidder can browse for a list of items that are under auction and participate in the auction process by actively bidding.
Seller
The seller can sell an item by posting it on the site by setting the desired details like reserved price, duration of auction etc. He can even cancel the auction before the start date
Auction System
The main task is “Auction Tracking”, which involves keeping track of all bids dynamically, validating them and selecting the best bid among them. It also updates all accounts,i.e. it credits from the bidder’s account, debits the commission into the system account and the remaining amount into the seller’s account.
Software: STAR UML (For Designing)
UML Diagrams:
Sequence Diagram: A sequence diagram is a graphical view of a scenario that shows object interaction in a time-based sequence-what happens first, what happens next. Sequence diagrams establish the roles of objects and help provide essential information to determine class responsibilities and interfaces. A sequence diagram has two dimensions: the vertical dimension represents time; the horizontal dimension represents different objects. The vertical line is called the object’s lifeline. The lifeline represents the object’s existence during the interaction. This form was first popularized by Jacobson. An object is shown as a box at the top of a dashed vertical line. A role is a slot for an object within a collaboration that describes the type of object that may play the role and its relationships to other roles. However, a sequence diagram does not show the relationships among the roles ort eh association among the objects. An object role is shown as a vertical dashed line, the lifeline
USE CASE DIAGRAM:
Use case diagrams depict the system behaviour (use cases).These diagrams present a high level view of how the system is used as viewed from an outsider’s (actor’s) perspective. A use case diagram may depict all or some of the use cases of a system.
A use-case diagram can contain:
actors (“things” outside the system)
use case (system boundaries identifying what the system should do)
Interactions or relationships between actors and use case in the system including the associations, dependencies and generalizations.
TASK2:
II. Aim: Draw an UML diagrams (Class, State chart and Activity) for ONLINE AUCTION
Class Diagram: A class diagram is a picture for describing generic descriptions of possible systems. Class diagrams and collaboration diagrams are alternate representations of object models. Class diagrams contain classes and object diagrams contain objects, but it is possible to mix classes and objects when dealing with various kinds of metadata, so the separation is not rigid.
Class diagrams are more prevalent than object diagrams. Normally you will build class diagrams plus occasional object diagrams illustrating complicated data structures or message-passing structures.
State chart Diagram: State chart diagrams model the dynamic behavior of individual classes or any other kind of object. They show the sequences of states that an object goes through, the events that cause a transition from one state to another and the actions that result from a state change.
State chart diagrams are closely related to activity diagrams. The main difference between the two diagrams is state chart diagrams are state centric, while activity diagrams are activity centric. A state chart diagram is typically used to model the discrete stages of an object’s lifetime, whereas an activity diagram is better suited to model the sequence of activities in a process.
Each state represents a named condition during the life of an object during which it satisfies some condition or waits for some event. A state chart diagram typically contains one start state and multiple end states. Transitions connect the various states on the diagram.
Activity Diagrams:
An activity diagram is a variation or special case of a state machine, in which the states are activities representing the performance of operations and the transitions are triggered by the completion of the operations. Unlike state diagrams that focus on the events occurring to a single object as it responds to messages, an activity diagram can be used to model an entire business process. The purpose of an activity diagram is to provide a view of flows and what is going on inside a use case or among several classes. However, activity diagram can also used to represent a class’s method implementation.
An activity model is similar to a state chart diagram, where a token represents an operation. An activity is shown as a round box, containing the name of the operation. When an operation symbol appears within an activity diagram or other state diagram, it indicates the execution of the operation. Executing a particular step within the diagram represents a state within the execution of the overall method.