Library Management System

Only available on StudyMode
  • Topic: Unified Modeling Language, UML diagrams, Use case diagram
  • Pages : 10 (1906 words )
  • Download(s) : 76
  • Published : March 31, 2011
Open Document
Text Preview
E-BOOK MANAGEMENT SYSTEM

PROBLEM DOMAIN

INTRODUCTION:

This E-BOOK should contain index of the topics. When the main page is visited index of the topics is displayed. Select the required topic and double click on it. Then the page with the contents of the selected topic will be displayed. A certain option is also present in that page to go back to main page and search for other topics.

STEPS:

* Create a main page.

* Main page contains index of certain topics.

* When a particular topic is required double click on it.

* It displays a page with the contents of that topic.

* A separate option is present to go back to main page.

USE-CASE DIAGRAM:

DESCRIPTION:

Use case diagrams describe what a system does from the stand point of an external observer. The emphasis is an; “What a system does rather than how it does”

Use case diagram are helpful in 3 cases:
* Use case often generates new requirement as the system is analyzed and the system is analyzed and the design takes shape. * Communication with clients.
* Generating test cases.

ACTIVITY DIAGRAM:

DESCRIPTION:

* Activity diagram focus on the flow of activity involved in the single process.

* Activity diagram shows how the activities depend on the another.

* It is essentially a FANCY diagram.

* Activity diagram is closely related with State chart.

SEQUENCE DIAGRAM:

DESCRIPTION:

* Sequence diagram is an interaction diagram which is dynamic * Sequence diagram gives information such as:
* How operations are carried out.
* What messages are sent?
* When sequence diagrams are organized according to time.

The objects involved in the operation are listed from left to right according to when they take part in the message sequence.

COLLABORATION DIAGRAM:

DESCRIPTION:

* Collaboration diagram are interaction diagram which are dynamic.

* Collaboration diagram focuses on object role instead of times that message are sent.

* Each message in the collaboration diagram has a sequence number.

DEPLOYMENT DIAGRAM:

DESCRIPTION:

* Deployment diagram is also called as component diagram.

* The component is code module.

* Component diagram are physical analog of class diagram.

* It shows the physical configuration of hardware and software.

CODING:
MAIN PAGE:
<html>
<head>
<title>E-BOOK</title><br>
</head>
<body bgcolor="yellow">
<p>
<font face="Monotype Corsiva" size="5" color="red">
<center><h1>E-BOOK ON OBJECT ORIENTED SYSTEM DEVELOPMENT</h1></center>
</p>
<p>
This book has a unique features:<br>
*Use of unified modeling language.<br>
*Inclusion of the Popkin system architect CASE tools.<br>
*Use of a use-case-driven approach.<br>
*System life cycle using object-oriented techniques.<br>
</p>
<center><a href="page1.html"><br>GO TO INDEX PAGE</a><br></center> </body>
</html>

PAGE 1:
<html>
<head>
<title>INDEX PAGE</title>
</head>
<body bgcolor="orange">
<p>
<font face="Monotype Corsiva" size="5" color="green"> <center><p><u><font color="red"><br><br>TABLE OF CONTENTS</font></u></p></center> <br><a href="page2.html">1.OBJECT ORIENTED METHODOLOGIES</a><br><br> <a href="page3.html">2.SOFTWARE QUALITY ASSURANCE</a><br>

</p>
<center><a href="main.html"><br><br><br>BACK TO MAIN PAGE</a></center> </body>
</html>

PAGE 2:
<html>
<head>
<title>OBJECT ORIENTED METHODOLOGIES</title>
</head>
<body bgcolor="pink">...
tracking img