object oriented analysis and design lab manual
DESCRIPTION
Anna University Object Oriented Analysis and DesignTRANSCRIPT
Syllabus
CS2357 OBJECT ORIENTED ANALYSIS AND DESIGN LAB 0 0 3 2
1. Passport automation system.
2. Book bank
3. Exam Registration
4. Stock maintenance system.
5. Online course reservation system
6. E-ticketing
7. Software personnel management system
8. Credit card processing
9. E-book management system
10.Recruitment system
11.Foreign trading system
12.Conference Management System
13. BPO Management System
CS2357 OBJECT ORIENTED ANALYSIS AND DESIGN LAB L T P C 0 0 3 2
OBJECTIVE:
To develop a mini-project following the 12 exercises listed below.
1. To develop a problem statement.2. Develop an IEEE standard SRS document. Also develop risk management and project plan (Gantt
chart).3. Identify Use Cases and develop the Use Case model.4. Identify the business activities and develop an UML Activity diagram.5. Identity the conceptual classes and develop a domain model with UML Class diagram.6. Using the identified scenarios find the interaction between objects and represent them using UML
Interaction diagrams.7. Draw the State Chart diagram.8. Identify the User Interface, Domain objects, and Technical services. Draw the partial layered,
logical architecture diagram with UML package diagram notation.9. Implement the Technical services layer.10. Implement the Domain objects layer.11. Implement the User Interface layer.12. Draw Component and Deployment diagrams.
TOTAL = 45 PERIODS
Suggested domains for Mini-project.
1. Passport automation system.2. Book bank3. Exam Registration4. Stock maintenance system.5. Online course reservation system6. E-ticketing7. Software personnel management system8. Credit card processing9. E-book management system10. Recruitment system11. Foreign trading system12. Conference Management System13. BPO Management System
Suggested Software ToolsArgoUML, Eclipse IDE, Visual Paradigm, Visual case, and Rational Suite
INTRODUCTION TO UML DIAGRAMS
EXNO:
DATE:
UML stands for Unified Modeling Language. This object-oriented system of notation has evolved
from the work of Grady Booch, James Rumbaugh, Ivar Jacobson, and the Rational Software Corporation.
These renowned computer scientists fused their respective technologies into a single, standardized model.
Today, UML is accepted by the Object Management Group (OMG) as the standard for modeling object
oriented programs. Each UML diagram is designed to let developers and customers view a software
system from a different perspective and in varying degrees of abstraction
Types of UML Diagrams
UML defines nine types of diagrams: class, object, use case, sequence, collaboration, statechart,
activity.
Class Diagrams
Class diagrams are the backbone of almost every object oriented method, including UML. They describe
the static structure of a system. Shows a collection of static model elements such as classes and types,
their contents, and their relationships.
Use Case Diagrams
Use case diagrams model the functionality of system using actors and use cases. Shows use cases, actors,
and their interrelationships
Sequence Diagrams
Sequence diagrams describe interactions among classes in terms of an exchange of messages over time.
Models the sequential logic, in effect the time ordering of messages between classifiers.
Collaboration Diagrams
Collaboration diagrams represent interactions between objects as a series of sequenced messages.
Collaboration diagrams describe both the static structure and the dynamic behavior of a system.
Statechart Diagrams
Statechart diagrams describe the dynamic behavior of a system in response to external stimuli. Statechart
diagrams are especially useful in modeling reactive objects whose states are triggered by specific events.
Activity Diagrams
Activity diagrams illustrate the dynamic nature of a system by modeling the flow of control from activity
to activity. An activity represents an operation on some class in the system that results in a change in the
state of the system. Typically, activity diagrams are used to model workflow or business processes and
internal operation.
Ex.No: 01
DATE:
ATM SYSTEM
MODULE 1
User inserts his card. Validate the user’s card. The pin is entered by the user The ATM system validates the pin, using a database. If the pin is invalid, an error message is printed
MODULE 2
Enter amount to be withdrawn Enter type of account to be used
MODULE 3
Validate the amount. Check if the user’s account has the required amount. If not available, print an error message.MODULE 4
Dispense the amount If user requires a receipt, print the receipt of the transaction and the account balance. Eject the card for the user to take back
CLASS DIAGRAM
CustomerDetail
CardPin
request()
Withdrawal
AccNoAmount
drawAmt()feasible()
BankDB
LogBalance
processRequest()
USE CASE DIAGRAM
Customer
Insert Card
Read Card
Validate Card
Enter Pin
Validate Pin
Enter Amount
Dispense Amount
ATM Server
ACTIVITY DIAGRAM
User selects withdrawal
User enters account pin
System verifies pin
Is password correct?
Invalid pin
Enter amount
Is amount valid? Invalid amount
Give amount
NoYes
No
Yes
COLLABORATION DIAGRAM
UI ATM Server
Cash Dispenser
Bank Network
1: Switch On
2: Boot up
3: get Cash Amount
4: Enter amount
5: Set Cash Amount
6: Open Connection7: Checking Account
8: Validate Amount
9: Give amoubnt
SEQUENCE DIAGRAM
UI ATM Server Cash Dispenser
Bank Network
Switch OnBoot up
get Cash Amount
Enter amount
Set Cash Amount
Open Connection
Checking Account
Validate Amount
Give amoubnt
COMPONENT DIAGRAM
Server
DBMS Server
User ATM UI Printer
DEPLOYMENT DIAGRAM
Server DBMS Server
Printer
UI
Get details
Withdraw
Print receipt
STATE CHART DIAGRAM
OFF entry/display "Not Available"
IDLE entry/display "Please Insert Card"
Serving customer include session
switch turned on / perform startup
switch turned offf/perform shutdown
card inserted/create session
session completed or aborted
RESULT:
The above modules for the ATM System have been designed and verified.
Ex.No: 02
DATE:
COURSE REGISTRATION SYSTEM
MODULE 1
Get the student registration number and his date of birth. The registration number should be verified with the existing database of valid registration
numbers.
MODULE 2
Get the cutoff. Compare the cutoffs and record the cutoff along with the student’s registration time.
MODULE 3
Display the colleges, whose required cutoff is less than or equal to the student’s total cutoff mark. The student must choose his preferred college. Display the available courses in the selected college.
The student must now choose his preferred course.
MODULE 4
The student must finally be informed that he has been registered successfully.
ACTIVITY DIAGRAM
Enter RegNo
Enter CutOff
Is the no valid?No
Yes
Compare Cut off with Cutoffs of available colleges
Cut off
Is cut off>=requirement of college?
Add to Available Coll List
Yes
Select Course
Register Student
Save
COLLABORATION DIAGRAM
S:Student Course Maintenance System
C: Courses
2: Verify
1: Enter ID4: Enter desired course
3: Request Selection
5: addStudent()7: Save()
6:
SEQUENCE DIAGRAM
S:Student Course Maintenance System
C: Courses
Enter ID
Verify
Request Selection
Enter desired course
addStudent()
Save()
USE CASE DIAGRAM
Enter Cut-OffStudentReg
Select Course
Register Student
Enter Registration Number
Verify ID
Show Available Courses
Registration System
CLASS DIAGRAM
Student_Details
RegNoDOB
getCutoff()
Course
course_IDnameseats_Available
register()
College
Coll_IDnamecutoff
selectCourse()addStudent()
Selects has
DEPLOYMENT DIAGRAM
Client Processor
Web Server
COMPONENT DIAGRAM
STATE CHART DIAGRAM
Get Register no
Get cut off
Compare cuttoff
Add to available college list
Enter course
Register Student
RESULT:The above modules for the Course Registration System have been designed and verified.
Ex.No: 03 EXPERT SYSTEM
DATE:
MODULE 1:
The user logs into the system with the user login id and password. The connection is made with the EQ database where a random set of 10 questions along
with their choices are selected. The questions are selected in such a way that the same set is not repeated for the same
login id.
MODULE 2:
Here, ten questions are displayed. As the user chooses an option it is stored in EQ marks format for evaluation.
MODULE 3:
The marks that are stored in EQ marks are transferred to EQ system. EQ system calculates the sum and displays it as Emotional Quotient.
MODULE 4:
The EQ value is connected to the EQ database in which the characteristic matching the EQ value is displayed.
MODULE 5:
Again, the EQ value is compared with the database for displaying the users’ drawbacks and ways of improvement.
MODULE 6:
If the user is interested then provide an interface for entering personal details with EQ for future reference.
The details are stored in the EQ database and can be accessed only through entering the correct password.
CLASS DIAGRAM
EQ Questions
selectqueschoices
EQ Marks
selectedchoices
valuatechoices()
EQ System
choicevalue
sum1()
transfers
calculates
ACTIVITY DIAGRAM
Start the application
Enter the username and password
Verify username and password
Enter into system
Enter personal details
Save your current EQ
View past records
Read the question
Select the answers
Submit answers
View the result
Save settings
Log out
COLLABORATION DIAGRAM
User Interface
EQ Database
EQ System
1: login
2: verify username and password
3: pose question4: select answer
5: update marks on database6: calculate result
7: give EQ result8: display EQ
SEQUENCE DIAGRAM
User Interface EQ DatabaseEQ System
login verify username and password
pose question
select answer
update marks on database
calculate result
give EQ result
display EQ
STATECHART DIAGRAM
Enter login details
Verify details
Enter system
Read question
Submit answer
View result
Enter user details
Look through past records
Save current EQ
Save user settings
Log out of the system
USECASE DIAGRAM
Creation
Log-in
Answer questions
Wait for inference
View marks
Personal Details
Maintenance
UserAdministrator
COMPONENT DIAGRAM
Server
DBMS Server
User Expert UI Printer
DEPLOYMENT DIAGRAM
Server DBMS Server
Printer
UI
Get details
Get question
Print result
RESULT:
The above modules for the Expert System have been designed and verified.
Ex.No: 4 LIBRARY MANAGEMENGT SYSTEM
DATE:
MODULE 1 Provide a user interface for getting the user’s login details.
Verify login ID and if correct, provide access to the library database.
MODULE 2 Provide a search mechanism to search for a particular book.
Input the book name and the author’s name.
MODULE 3 Get the book details from the database.
Display the book details on the screen.
MODULE 4 Allow the user to select the book for checking out.
Issue the book.
SEQUENCE DIAGRAM
Student library AdministratorLibrarian
Enter Login Details
Verify Authentication
Grant Permission/ Deny
Enter Login Details
Verify Authentication
Grant Permission/Deny
Enter Book name
Search the book
Enter author name
Check the book
Display results
CLASS DIAGRAM
Data Entry
NameId no.Book nameAuthorDOIDORCard no
Issue()Return ()
Software Entry
Issue Querying
DOI.
Renewal()Issue()
Querying
ReturnQuerying
Return()
COLLABORATION DIAGRAM
USE CASE DIAGRAM
SystemAdministrator
Student
Librarian
1: Enter Login Details
2: Verify Authentication
3: Grant Permission/ Deny4: Enter Login Details
5: Verify Authentication
6: Grant Permission/Deny
7: Enter Book name
8: Search the book
9: Enter author name11: Issue the book
Search book name
Select book name
Enter student login details
Issue the book
Student Librarian
ACTIVITY DIAGRAM
Enter login name
Verify
Grant permission
Enter book name
Enter author name
Display the book
Check out the book
STATECHART DIAGRAM
Enter login name
Verify Grant permission
Enter the book name
Display the book
Issue the book
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
Client Processor
Web Server
RESULT:The above modules for the Library Management System have been designed and verified.
Ex.No: 5 ONLINE TICKET RESERVATION SYSTEM
DATE:
MODULE 1
Before entering the system, users have to login
Get the username and password from existing users.
Give new users the option to sign up.
MODULE 2
Get the source and destination.
Provide a dropdown box for the date.
Check availability of tickets.
MODULE 3
If tickets are available, get the number of passengers.
Get the name and age of all passengers.
If tickets are not available, reschedule.
MODULE 4
Print the cost of the tickets.
Get the payment details from the user.
Confirm the details and the ticket.
Display confirmed ticket to the user.
ACTIVITY DIAGRAM
Display availability
Get booking request
Display payment details
Get user's payment details
If completeNo
Print ticket
CLASS DIAGRAM
CustomerDetails
NameAddressEmailAge
book()
Booking
Booking_noDateTotalStatusname
Pay()
Payment
DateAmount
USECASE DIAGRAM
Choose source, destination
Check availability
Enter detailsCustomer
Request booking
Booking Server
Make payment
Confirm booking
Bank System
SEQUENCE DIAGRAM
Customer Server Bank
Check availabilityYes
If no, reschedule
Enter information
Reconfirm booking
Payment
Confirm payment
Get ticket
COLLABORATION DIAGRAM
Customer Server
Bank
1: Check availability
2: Yes
3: If no, reschedule
4: Enter information
5: Reconfirm booking
6: Payment
7: Confirm payment8: Get ticket
STATE CHART DIAGRAM
Displaying availability
Request booking
Check availability
Displaying payment details
User's payment details
Print Ticket
COMPONENT DIAGRAM
Online Booking Server
Bank
Customer
DEPLOYMENT DIAGRAM
Server Update
User PC
Railway Database
RESULT:
The above modules for the Online Ticket Reservation System have been designed and verified.
Ex.No:6 PAYROLL SYSTEMS
DATE:
MODULE 1:
Enter the employee details name and eno.
Obtain HRA,DA,PF.
Get the basic pay as per designation.
MODULE 2:
Calculate deductions and allowance percentage.
Calculate the basic pay.
MODULE 3:
Calculate the number of days taken leave.
Calculate the deductions due to leave.
Calculate the net pay after subtracting the net deductions.
Provide salary slip.
USE CASE DIAGRAM
employer
Enter details into database
Calculate net deductions
calculate deductions due to leave
Obtain basic pay as per designation
net salary
employee
SEQUENCE DIAGRAM
employer database salary calculation
employee
Enter employee details
obtain basic pay
obtain hra,da,ta
calculate salary
obtain leave details
hand over pay slip
store
retrieve net pay
COLLABORATION DIAGRAM
employerdatabase
salary calculation
employee
1: Enter employee details
7: retrieve net pay
5: calculate salary
8: hand over pay slip 2: obtain basic pay3: obtain hra,da,ta
4: obtain leave details
6: store
CLASS DIAGRAM
Leave
casualLeaveearnLeaveno_of_years_workedmedicalLeave
calculateLeave()
Employee
emp_IDemp_namedate_of_joinsalarydeptdesignation
getDetails()
Designation
typebasicpaynetdeductionshrapfda
calculateSalary()
1 1..*
ACTIVITY DIAGRAM
provide employee details
get basic pay as per designation
netpay=basic pay-deductions
netpay=basic pay+ (hra,da,pf)
calculate net deductions and allowance percentage
provide salary
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
Node 1:Registrar
Node 2:PC
Update
STATE CHART DIAGRAM
Get employee details
Get basic pay
Calculate net deductions
Basic pay-deductions
basic pay+allowance
Salary
RESULT:The above modules for the Payroll System have been designed and verified.
Ex.No:7 QUIZ SYSTEM
DATE:
MODULE 1
Get login details of the user
If new user, create a new account
Verify password and ID
MODULE 2
Display the questions
The user selects an option for each question or skips it.
Move to next question
MODULE 3
Check if the answers for each question are right or wrong.
Sum up all scores to get the total marks
Get the total of all users.
MODULE 4
Find the winner.
If a user is a winner, print you win.
Else print, game over.
SEQUENCE DIAGRAM
partcipant Switch Over The Question
Compiler Central System
Reg For NAME
Ask Question
Answer the Questions
Keep Record Score
No Answer
Is It High Score
Calculate The Participant Score
Won The Game
Lose The Game
CLASS DIAGRAM
user
user nameIDPassword
plays()sign up()
compiler
namelistquestionanswer
askquestion()keepsmark()compilers()
Admin
IDPassword
registration()calculation()CentralSystemManagement()
COLLABORATION DIAGRAM
USECASE DIAGRAM
ParticipantSwitch Over The Question
Central System
Compiler
1:Register
6:No Answer
4:Keep Record Of Score
9:Calculate The Score
8:Answer The Questions
7:Switch To Next Question
5:Ask Question
3:Answer The Question
2:Ask Question
10:Won The Game
11:Lose The Game
selecting options
generates question
timings
checking the answers
print the result
Update user information
administrator
player name
player id
player password
sign up
systemswitch over sections
player
ACTIVITY DIAGRAM
login
Enter The Quiz
Sign Up
Marks Added
Game Over
Won The Game
Switch To Next Question
Selecting Option
Check whether user is registered
YES
NO
Its a HighScore?
If Answered
YES
NO
YES
NO
STATE CHART DIAGRAM
Log in
Enter the system
Select option
Next question
Add marks
End game
COMPONENT DIAGRAM
Server
DBMS Server
User Quiz UI Printer
DEPLOYMENT DIAGRAM
Server DBMS Server
Printer
UI
Get details
Get question
Print result
RESULT:
The above modules for the Quiz System have been designed and verified.
Ex.No:8 REAL TIME SCHEDULER
DATE:
MODULE 1-GET USER DETAILS
Get the name, ID and Phone number of the user. Get the password from the user. Give options to either view the schedule of the user or to add a new schedule.
MODULE 2-VIEW SCHEDULE
In the view schedule window, display o Appointment nameo Appointment timeo Appointment location
MODULE 3-ADD SCHEDULE
To add a schedule, the user must enter the name, time and location of the appointment. The user should be alerted if the schedule is made after 5 PM. If the user is busy at the selected time, he can reschedule. The user can also delete an appointment using the delete option.
MODULE 4-RESCHEDULE
To reschedule, the user must first check whether he is free at the specified time or not. If yes, he can proceed with the rescheduling process. Otherwise, he must again check for an alternate time.
MODULE 5
The user must finally be informed that his schedule has been successfully created.
USE CASE DIAGRAM
View Schedule
Add Schedule
Delete Schedule
Reschedule
System
Check Availability
Person_Details
SEQUENCE DIAGRAM
Person Appointment Control
Appointment
View schedule
Check availability
Reschedule
Confirm appointment
Add appointment
If yes, create appointment
No
CLASS DIAGRAM
makes needs
Availability
New_timeNew_location
CheckAvailability()
Schedule
ActivityTimeLocation
DeleteSchedule()Reschedule()
Person
Person_NamePerson_IDPhone_NoPassword
ViewSchedule()EditSchedule()
ACTIVITY DIAGRAM
Enter details
View Schedule Add appointment
Available?
Reschedule appointment
no
Confirm schedule
Yes
COLLABORATION DIAGRAM
Person Appointment Control
Appointment
1: View schedule
3: Check availability6: Reschedule
7: Confirm appointment
2: Add appointment
4: If yes, create appointment
5: No
STATECHART DIAGRAM
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
Client Processor
Web Server
RESULT:
The above modules for the Real Time Scheduler System have been designed and verified.
Ex.No:9 REMOTE PROCEDURE CALL
DATE:
MODULE 1
Create an account for each customer. Customer has to log in using user name and password.
MODULE 2
Prepare the order. Provide each customer with the shopping cart containing all the items that the customer wants to
buy. Give them access to all the details about different types of computers that is available in the store.
MODULE 3
Provide order form and let the customer to fill out payment and shipping details. Store the order in database. Review the order and check whether the items are available. Email the order details to the customers email id.
MODULE 4
Send information to the warehouse to start shipping process. Print the invoice. Accept customer payment.
COLLABORATION DIAGRAM
Config window
Order Order window
Customer Payment
3: Prepare for order 4: Display order
6: Store order
8: Link payment
1: Open new2: Accept config
5: Submit order
7: Link customer
CLASS DIAGRAM
Configuration
item typeitem descp
Customer
nameaddressph noemail
get order()
Payment
payment methoddate receivedamt received
Invoice
numberdatetotal
Order
od numdateaddresstotalstatussales pname
USE CASE DIAGRAM
warehouse
Inform warehouse about order
Display standard computer config
Build computer config
Order configured computer
Request salesperson contact
customer
Update order status
Print invoice
Salesperson
Verify and accept customer payment
SEQUENCE DIAGRAM
Customer Config window Order Order window Payment
Open new
Accept config Prepare for orderDisplay order
Submit order
Store order
Link customer
Link payment
ACTIVITYDIAGRAM
Display current config
Get order request
Dispaly purchase form
Get purchase details Store order
Email order details
[OK]
[incomplete]
[time out]
STATE CHART DIAGRAM
COMPONENT DIAGRAM
Online shopping
Customer
Order
DEPLOYMENT DIAGRAM
Client Processor
Web Server
RESULT:
The above modules for the Remote Procedure Call System have been designed and verified.
Ex.No:10
STOCK MAINTANENCE SYSTEM
DATE:
MODULE 1: (user entry for log-in)
Log-in is required in order to purchase products from the store.
The old customer enters the seller’s site by entering the username and password.
If the password or username is invalid ,then an error message is displayed.
If a new customer wants to purchase products then he needs to sign up to enter his details.
MODULE 2: (selection)
After signing in the customer can select particular product and a detailed description of it is
displayed.
The customer can also select the option compare to see the features of different available
products.
After analyzing the various features ,the best of all the products is chosen.
MODULE 3: (transaction)
The customer in order to buy the product uses his credit card by entering the necessary details.
MODULE 4: (delivery)
Once the customer enters the necessary details and when the SUBMIT button is clicked, the
acknowledgement is sent and the selected product is delivered.
CLASS DIAGRAM
USE CASE DIAGRAM
SEQUENCE DIAGRAM
USER PRODUCT PAYMENTSELLER SITE
enter username and password
login
selecting product
product has been enabled
paid through credit card
COLLABORATION DIAGRAM
USER PAYMENT
PRODUCT SELLER SITE
1: enter username and password
2: login
3: selecting product
4: product has been enabled
5: paid through credit card
ACTIVITY DIAGRAM
Enter username and password
login
Select the product
Pay through credit card
STATECHART DIAGRAM
entering login details
log in
selection of the product
payment through credit card
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
Client Processor
Web Server
RESULT:
The above modules for the Stock Maintenance System have been designed and verified.
Content Beyond Syllabus
ONLINE PURCHASE SYSTEM
1. ANALYSIS
1.1 Identifying the Actors
1.2 Identifying the Use Cases
2. REQUIREMENTS
2.1 System Requirements
2.2 Software Requirements
3. DESIGN
3.1 Use Case Diagram
3.2 Class Diagram
3.3 Sequence Diagram
3.4 Collaboration Diagram
3.5 Activity Diagram
3.6 State Diagram
ONLINE PURCHASE USE CASE DIAGRAM
OnlinePurchase
Customer
Software
Banking
Dealer
Check forvalidity
Deliever Goods
IssueAuthorization
Issue Details
Ask for Payment &Shipping details
Select Item
Browse Catlog
Request Item
ONLINE PURCHASE CLASS DIAGRAM
ShoppingCardAttributes
public float subtotalpublic float salesmoneypublic float totalmoney
Operations
public ShoppingCard()public float getSubtotal()public void setSubtotal(float val )public float getSalesmoney()public void setSalesmoney(float val )public float getTotalmoney()public void setTotalmoney(float val )public void placeOrder()public void removeOrder()public Customervoid[0..*] getCustomer()public void setCustomer(Customer val[0..*] )public CreditCardvoid[0..*] getCreditCard()public void setCreditCard(CrdeitCard val[0..*] )public Customer[0..*] getCustomer()public void setCustomer(Customer val[0..*] )public CreditCard[0..*] getCreditCard()public void setCreditCard(CreditCard val[0..*] )
CustomerAttributes
private string addrtoshipprivate string nameprivate string addrtobillprivate string emailaddprivate int creditrating
Operations
public Customer()public string getAddrtoship()public void setAddrtoship(string val )public string getName()public void setName(string val )public string getAddrtobill()public void setAddrtobill(string val )public string getEmailadd()public void setEmailadd(string val )public int getCreditrating()public void setCreditrating(int val )public void displayCategory()public void selectItem()public void delieverItem()public void removeOrder()
ItemOfPurchaseAttributes
private int quantityprivate float priceperitem
Operations
public ItemOfPurchase()public int getQuantity()public void setQuantity(int val )public float getPriceperitem()public void setPriceperitem(float val )public Customer fetCustomer()public void setCustomer(Customer val )public Product[0..*] getProduct()public void setProduct(Product val[0..*] )public Product[0..*] getProduct()public void setProduct(Product val[0..*] )
CreditCardOperations
public CreditCard()public int getNumber()public void setNumber(int val )public date getExpirydate()public void setExpirydate(date val )public boolean getIssue()public void setIssue(boolean val )public void authorizeCharge()public Preffered()public ItemOfPurchase getItemOfPurchase()public void setItemOfPurchase(ItemOfPurchase val )public PrefferedCustomer[0..*] getPrefferredCustomer()public void setPrefferredCustomer(PrefferedCustomer val[0..*] )public PrefferedCustomer[0..*] getPrefferedCustomer()public void setPrefferedCustomer(PrefferedCustomer val[0..*] )
PrefferedCustomerAttributes
private int discountrate
Operations
public PrefferedCustomer()public int getDiscountrate()public void setDiscountrate(int val )public Customer getCustomer()public void setCustomer(Customer val )public Customer getCustomer1()public void setCusotmer1(Customer val )public Customer getCustomer()public void setCustomer(Customer val )
ProductAttributes
Operations
public Product()
1
*
mProduct
1
mCustomer
1*
mCreditCard 1
1
mCustomer
mPrefferedCustomer
* 1
ONLINE PURCHASE SEQUENCE DIAGRAM
: Customer
: Shoppingcart : creditcard
public void brow secatalog()
public void displaycatalog()
public void selectItem()
public void getCreditRating()public void getAddrToShop()
public void setCreditCard()
public void shipmentDetails()
public void authorizedCharge()
public void authorize()
public void getExpiryDate()
validation
public void setCrediting(int val )
public void setAddrToShip()
public void deleverItem()
public void rejected()
public void removeOrder()
ONLINE PURCHASE COLLABORATION DIAGRAM
: Customer
: Shoppingcart
: creditcard
public void brow secatalog()
public void displaycatalog()public void selectItem()
public void getCreditRating()
public void getAddrToShop()
public void setCreditCard()
public void shipmentDetails()
public void setCrediting(int val )
public void setAddrToShip()
public void deleverItem()
public void removeOrder()
public void authorizedCharge()
public void authorize()
public void rejected()
public void getExpiryDate()
ONLINE PURCHASE ACTIVITY DIAGRAM
OnlinePurchase
Customer Shoppingcart Creditcard
BrowseCatlog
{ From OP_Activity }
SelectingCatlog
{ From OP_Activ...
Selecting &
{ From OP_Activit...
Issuingpayment
{ From OP_Activity }
DelieveringItem
{ From OP_Activity }
DisplayingCatlog
{ From OP_Activity }
Displaying ....
{ From OP_Activity }
Requesting
{ From OP_Activity }
Acceptingdelivery
{ From OP_Activity }
Authorized
{ From OP_Activity }
Rejected
{ From OP_Activity }
Validatingcredit
{ From OP_Activity }
Unnamed
Unnamed
Unnamed
ONLINE PURCHASE STATECHART DIAGRAM
CHECKING
PROCESS
DELIVERY
DISPATCH
WAITING
CANCELLING
EXIT
CLASS CODEpublic class Customer(){
private string nameprivate string addtoshopprivate int creditrating
public Customer(){}public void delieverItem(){}public void selectItem(){}public void removeItem(){}
}public class ItemOfPurchase(){
private int quantityprivate flaot priceperitem
public ItemOfPurchase(){
}public float getPriceperItem(){
}public void setPriceperItem(float val){
Item = val}
}public class Product(){public Product()
{
}}RESULT:-
Thus the UML models for the Online Purchase System have been developed and verified.
STUDENT MARKS ANALYSIS SYSTEM
1. ANALYSIS
1.1 Identifying the Actors
1.2 Identifying the Use Cases
2. REQUIREMENTS
2.1 System Requirements
2.2 Software Requirements
3. DESIGN
3.1 Use Case Diagram
3.2 Class Diagram
3.3 Sequence Diagram
3.4 Collaboration Diagram
3.5 Activity Diagram
3.6 State Diagram
USE CASE DIAGRAM
CLASS DIAGRAM
SEQUENCE DIAGRAM
COLLABORATION DIAGRAM
ACTIVITY DIAGRAM
STATECHART DIAGRAM
CLASS CODE
public class MarksRegister { private int StringRegno; private int intMaxmarks; private int intMinmarks; private int intMarksobtained; /** @roseuid 46D9020F0017 */ public MarksRegister() { } /** @roseuid 46D901BF027C */ public void checkRegno() { } /** @roseuid 46D901C501FF */ public void checkSubjectCode() { } /** @roseuid 46D901CC0395 */ public void setResults() { }}
RESULT:-Thus the UML models for the Student Marks Analysis System have been developed and verified.