Syllabus CS2357
OBJECT ORIENTED ANALYSIS AND DESIGN LAB
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
0 0 3 2
CS2357
OBJECT ORIENTED ANALYSIS AND DESIGN LAB
LTPC 0032
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 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
Suggested Software Tools ArgoUML, 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 BankDB
CustomerDetail Card Pin
Log Balance
request()
processRequest()
USE CASE DIAGRAM
Withdrawal AccNo Amount drawAmt() feasible()
Insert Card
Read Card
Validate Card ATM Server
Customer Enter Pin
Validate Pin
Enter Amount
Dispense Amount
ACTIVITY DIAGRAM
User selects withdrawal
User enters account pin
System verifies pin
Is password correct?
Invalid pin No
Yes Enter amount
Invalid amount
Is amount valid? No Yes Give amount
COLLABORATION DIAGRAM 2: Boot up
1: Switch On 4: Enter amount ATM Server
UI 3: get Cash Amount
6: Open Connection 7: Checking Account 8: Validate Amount 5: Set Cash Amount 9: Give amoubnt Bank Network
Cash Dispenser
SEQUENCE DIAGRAM UI
ATM Server
Cash Dispenser
Switch On Boot up
get Cash Amount
Enter amount Set Cash Amount Open Connection Checking Account Validate Amount Give amoubnt
Bank Network
COMPONENT DIAGRAM Server
User
ATM UI
Printer
DBMS Server
DEPLOYMENT DIAGRAM
Server
Get details
DBMS Server
Withdraw
Printer UI
STATE CHART DIAGRAM
Print receipt
OFF entry/display "Not Available"
switch turned offf/ perform shutdown
switch turned on / perform startup
card inserted/create session Serving customer include session
IDLE entry/display "Please Insert Card" 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 No Is the no valid?
Yes Enter CutOff Cut off Compare Cut off with Cutoffs of available colleges
Is cut off>=requirement of college? Yes Add to Available Coll List
Select Course
Register Student
Save
COLLABORATION DIAGRAM
2: Verify
S:Student
1: Enter ID 4: Enter desired course
Course Maintenance System
3: Request Selection 6: 5: addStudent() 7: Save() C: Courses
SEQUENCE DIAGRAM
S:Student
C: Courses
Course Maintenance System Enter ID Verify Request Selection
Enter desired course addStudent()
Save()
USE CASE DIAGRAM
Enter Registration Number
Verify ID
Enter Cut-Off
StudentReg
Show Available Courses
Registration System
Select Course
Register Student
CLASS DIAGRAM
Student_Details RegNo DOB getCutoff()
Selects
College Coll_ID name cutoff selectCourse() addStudent()
has
Course course_ID name seats_Available register()
DEPLOYMENT DIAGRAM Client Processor
COMPONENT DIAGRAM
Web Server
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 selectques choices
transfers
EQ Marks selectedchoices valuatechoices()
calculates EQ System choicevalue sum1()
ACTIVITY DIAGRAM
Start the application Enter the username and password
Verify username and password
Enter into system
Read the question
Enter personal details
Select the answers
View past records
Submit answers Save your current EQ View the result
Save settings
Log out
COLLABORATION DIAGRAM
2: verify username and password User Interface
EQ Database
5: update marks on database 6: calculate result 1: login 3: pose question 8: display EQ
4: select answer 7: give EQ result
EQ System
SEQUENCE DIAGRAM
EQ System
User Interface login
EQ Database
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 Administrator
User Answer questions
Wait for inference
View marks
Personal Details
Maintenance
COMPONENT DIAGRAM
Server
User
Expert UI
Printer
DBMS Server
DEPLOYMENT DIAGRAM
Server
Get details
DBMS Server
Get question
Printer UI
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
Librarian
Administrator
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
Software Entry
Data Entry Name Id no. Book name Author DOI DOR Card no
Issue() Return ()
Querying
Issue Querying DOI. Renewal() Issue()
Return Querying Return()
COLLABORATION DIAGRAM
Librarian Student
9: Enter author name 11: Issue the book 1: Enter Login Details
6: Grant Permission/Deny
3: Grant Permission/ Deny 4: Enter Login Details 7: Enter Book name
System USE CASE DIAGRAM
2: Verify Authentication 5: Verify Authentication 8: Search the book
Administrator
Search book name
Select book name Librarian
Student
Enter student login details
Issue the book
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 Issue the book
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
Display the book
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 No If complete
Print ticket
CLASS DIAGRAM CustomerDetails Name Address Email Age book()
Booking Booking_no Date Total Status name
Payment Date Amount
Pay()
USECASE DIAGRAM
Choose source, destination
Check availability
Customer
Booking Server
Enter details
Request booking
Make payment
Confirm booking
Bank System
SEQUENCE DIAGRAM
Customer
Server
Check availability Yes If no, reschedule Enter information
Reconfirm booking
Payment Confirm payment Get ticket
Bank
COLLABORATION DIAGRAM 2: Yes
1: Check availability 4: Enter information Customer 3: If no, reschedule 5: Reconfirm booking 8: Get ticket 7: Confirm payment 6: Payment
Bank
STATE CHART DIAGRAM
Server
Displaying availability
Request booking
Check availability
Displaying payment details
User's payment details
Print Ticket
COMPONENT DIAGRAM Bank
Online Booking Server
Customer
DEPLOYMENT DIAGRAM
Server Update
Railway Database
User PC
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
Enter details into database
Obtain basic pay as per designation
employer
Calculate net deductions
calculate deductions due to leave
net salary
SEQUENCE DIAGRAM
employee
employer
database
salary calculation
Enter employee details
obtain basic pay
obtain hra,da,ta
obtain leave details
calculate salary
store
retrieve net pay
hand over pay slip
COLLABORATION DIAGRAM
employee
1: Enter employee details
database
employer 7: retrieve net pay 5: calculate salary 6: store
2: obtain basic pay 3: obtain hra,da,ta 4: obtain leave details
8: hand over pay slip
salary calculation employee
CLASS DIAGRAM
Employee emp_ID emp_name date_of_join salary dept designation
1
1..*
getDetails()
Designation type basicpay netdeductions hra pf da calculateSalary()
Leave casualLeave earnLeave no_of_years_worked medicalLeave calculateLeave()
ACTIVITY DIAGRAM
provide employee details
get basic pay as per designation
calculate net deductions and allowance percentage
netpay=basic pay+ (hra,da,pf)
netpay=basic pay-deductions
provide salary
COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM
Node 1:Registrar
Update
Node 2:PC
STATE CHART DIAGRAM
Get employee details
Get basic pay
Calculate net deductions
basic pay+allowance
Basic pay-deductions
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
Calculate The Participant Score
Won The Game
Lose The Game
Is It High Score
CLASS DIAGRAM
Admin ID Password registration() calculation() CentralSystemManagement()
user user name ID Password
compiler namelist question answer
plays() sign up()
askquestion() keepsmark() compilers()
COLLABORATION DIAGRAM
1:Register 6:No Answer
Switch Over The Question
Participant
2:Ask Question
7:Switch To Next Question
10:Won The Game 11:Lose The Game 8:Answer The Questions
3:Answer The Question 5:Ask Question
Compiler
9:Calculate The Score
4:Keep Record Of Score
Central System
USECASE DIAGRAM
player name
player id
player password
sign up
administrator generates question
selecting options
timings player switch over sections
checking the answers
print the result
Update user information
system
ACTIVITY DIAGRAM
login
Sign Up
Check whether user is registered
NO
YES Enter The Quiz
Selecting Option
NO
If Answered YES Marks Added
Game Over
NO
Its a HighScore? YES Won The Game
Switch To Next Question
STATE CHART DIAGRAM
Log in
Enter the system
Select option
Next question
Add marks
End game
COMPONENT DIAGRAM
Server
User
Quiz UI
Printer
DBMS Server
DEPLOYMENT DIAGRAM
Server
Get details
DBMS Server
Get question
Printer UI
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 name o Appointment time o 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 Person_Details
System Reschedule
Check Availability
SEQUENCE DIAGRAM
Person
Appointment Control
Appointment
View schedule
Add appointment
Check availability If yes, create appointment
No
Reschedule Confirm appointment
CLASS DIAGRAM
Person Person_Name Person_ID Phone_No Password
makes
ViewSchedule() EditSchedule()
ACTIVITY DIAGRAM
Schedule Activity Time Location DeleteSchedule() Reschedule()
needs
Availability New_time New_location CheckAvailability()
Enter details
View Schedule
Add appointment
Yes
Available?
no Reschedule appointment
Confirm schedule
COLLABORATION DIAGRAM
1: View schedule 2: Add appointment Person
Appointment Control
5: No
4: If yes, create appointment
Appointment
STATECHART DIAGRAM
3: Check availability 6: Reschedule 7: Confirm appointment
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
3: Prepare for order Config window
4: Display order Order
Order window 6: Store order
5: Submit order 1: Open new 2: Accept config
7: Link customer Payment
Customer
CLASS
8: Link payment
DIAGRAM
Customer name address ph no email get order()
Order od num date address total status sales pname
Configuration item type item descp Invoice number date total
Payment payment method date received amt received
USE CASE DIAGRAM
Display standard computer config
Build computer config
Order configured computer
customer Request salesperson contact
Inform warehouse about order
warehouse Update order status
Print invoice
Verify and accept customer payment
Salesperson
SEQUENCE
DIAGRAM
Customer
Config window
Order
Order window
Open new Accept config
Prepare for order
Display order
Submit order Store order Link customer Link payment
Payment
ACTIVITYDIAGRAM
Display current config
Get order request
Dispaly purchase form [time out] [incomplete] Get purchase details
Store order [OK]
Email order details
STATE CHART DIAGRAM
Pending New order
Stock not
Back order
Available
Ready to ship
Stock available
stock available
[cancelled]
Future order
Cancelled
accepted
Filled
COMPONENT DIAGRAM
Customer
Online shopping
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
SELLER SITE
enter username and password login
selecting product
product has been enabled
paid through credit card
PAYMENT
COLLABORATION DIAGRAM
5: paid through credit card USER
PAYMENT
1: enter username and password 3: selecting product 2: login
4: product has been enabled PRODUCT
SELLER SITE
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
Browse Catlog
Select Item
Software Customer
Request Item
Ask for Payment & Shipping details
Issue Details
Issue Authorization
Banking Check for validity
Deliever Goods
Dealer
ONLINE PURCHASE CLASS DIAGRAM
Customer
ShoppingCard
Attributes
Attributes
private string addrtoship private string name private string addrtobill private string emailadd private int creditrating
public float subtotal public float salesmoney public 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() 1 public void setCreditCard(CreditCard val[0..*] )
Operations
mCustomer
public Customer() public string getAddrtoship() public void setAddrtoship(string val ) public string getName() 1 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()
mCustomer
1 mCreditCard
1
CreditCard
*
ItemOfPurchase Attributes
private int quantity private 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..*] )
Operations
PrefferedCustomer
public CreditCard() Attributes public int getNumber() private int discountrate public void setNumber(int val ) Operations public date getExpirydate() mPrefferedCustomer public PrefferedCustomer() public void setExpirydate(date val ) public int getDiscountrate() public boolean getIssue() public void setDiscountrate(int val ) 1 public void setIssue(boolean val ) * public Customer getCustomer() public void authorizeCharge() public void setCustomer(Customer val ) public Preffered() public Customer getCustomer1() public ItemOfPurchase getItemOfPurchase() public void setCusotmer1(Customer val ) public void setItemOfPurchase(ItemOfPurchase val ) public Customer getCustomer() public PrefferedCustomer[0..*] getPrefferredCustomer() public void setCustomer(Customer val ) public void setPrefferredCustomer(PrefferedCustomer val[0..*] ) public PrefferedCustomer[0..*] getPrefferedCustomer() public void setPrefferedCustomer(PrefferedCustomer val[0..*] )
mProduct 1
Product Attributes Operations
public Product()
ONLINE PURCHASE SEQUENCE DIAGRAM
: Shoppingcart
: creditcard
: Customer 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 getExpiryDate()
validation
public void authorize()
public void setCrediting(int val )
public void setAddrToShip()
public void deleverItem() public void rejected() public void removeOrder()
ONLINE PURCHASE COLLABORATION DIAGRAM
: Customer public void setAddrToShip() public void brow secatalog()
public void deleverItem() public void getCreditRating()
public void shipmentDetails() public void getAddrToShop()
public void displaycatalog()
public void selectItem()
public void removeOrder()
public void setCreditCard()
public void setCrediting(int val )
: Shoppingcart public void rejected()
public void authorize()
public void authorizedCharge()
: creditcard
public void getExpiryDate()
ONLINE PURCHASE ACTIVITY DIAGRAM OnlinePurchase Customer
Shoppingcart
Creditcard
Unnamed
Browse Catlog
Displaying Catlog
{ From OP_Activity }
{ From OP_Activity }
Selecting Catlog
Displaying ....
{ From OP_Activ...
{ From OP_Activity }
Selecting &
Requesting
Validating credit
{ From OP_Activit...
{ From OP_Activity }
{ From OP_Activity }
Issuing payment
Accepting delivery
{ From OP_Activity }
{ From OP_Activity }
Unnamed
Delievering Item
Authorized
{ From OP_Activity }
{ From OP_Activity }
Rejected { From OP_Activity } Unnamed
ONLINE PURCHASE STATECHART DIAGRAM
CHECKING
PROCESS
WAITING
CANCELLING
DELIVERY
DISPATCH
EXIT
CLASS CODE public class Customer() { private string name private string addtoshop private int creditrating public Customer() { } public void delieverItem() { } public void selectItem() { } public void removeItem() { } } public class ItemOfPurchase() { private int quantity private 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.
