Académique Documents
Professionnel Documents
Culture Documents
3 STOCK MAINTAINANCE
17.08.09
PROBLEM STATEMENT:
To develop a project “STOCK MAINTENANCE SYSTEM” using the Rational
Rose Software for the UML diagrams and to implement the software in Visual Basic.
The Customer can view the products and can purchase.The Administrator can
maintain the Product details in a Database to Update the Product Details and Add New
Products in the Database.
REQUIREMENT ANALYSIS:
It is a process of analyzing the User needs and transforming into a problem
requirement. This application allows the Customer to view the product details through the
database and the database is maintained by the Administrator to enter, update and add the
new products to the Database. The requirements are
1. Customer
2. Administrator
3. Products
4. Database
DATA MODELING:
The project can be explained diagrammatically using the following diagrams:
Use Case Diagram
Class Diagram
Sequence Diagram
Collaboration Diagram
Activity Diagram
ACTORS:
An actor is a role that a user plays with respect to the System. The actors are:
Administrator
Database
USE CASE :
Description:
The Customer can login in to the system and view the stock details and purchase.
Steps:
• Enter the user ID and Password.
• Press the view Button to view the details of the products.
Description:
The Administrator can login into the system and add or remove the stock based on
minimum availability in the database.
Steps:
• Enter the admin ID of the Password.
• Maintain the Recording Level.
• Add or Remove the products by pressing the corresponding buttons.
CLASS DIAGRAM:
A Class diagram describes the types of objects in the system and the various kinds
of static relationships that exist among them.
Description:
The classes used in this project are
• Customer
• Administrator
• Database
SEQUENCE DIAGRAM:
Description:
The various scenarios of the sequence diagram used in this project are
• Customer
• Database
• Administrator
COLLABORATION DIAGRAM:
In a Collaboration diagram, object’s are shown as icons. As on a sequence
diagram, arrow indicate the message sent within the given Use Case. The sequence is
indicated by numbering the messages.
Description:
This diagram contains the group of classes created, interfaces and the elements
that work together to provide the overall behavior of the project. It also describes the
relationship between each classes and how they relate with each other.
ACTIVITY DIAGRAM:
The Activity diagram describes the sequencing of activities, with the support for
both conditional and parallel behavior. An activity diagram is a variant of state diagram.
Description:
The Activity diagram is similar to traditional flowchart. It captures the event that
happens either within an object or within a group of objects.
Steps:
• Check whether the person is Customer or Administrator.
• If Customer, view the Products by giving the Product ID.
• If Administrator, select the any one of the option Like view the detail or
update or add new.
• In Customer view, check the product quantity.
• Then Check for the minimum quantity.
• In Result Analysis, view the Product Name
• To Quit the System, click the end process.
IMPLEMENTATION:
FORM 1:(STOCK MAINTAINANCE)
FORM 2:(STOCK-INTRODUCTION)
Dim p As New passenger
Dim c As New cancel
FORM 3:(AUTHENTICATION-ADMINISTRATOR)
FORM 4:(PHARMACY)
FORM 6:(TABLETS)
FORM 7:(SYRUBS/TONICS)
FORM 12:(AUTHENTICATION-CUSTOMER)
FORM 16:(EXIT)
Option Explicit
'##ModelId=4862047500CB
ADMINISTRATOR.CLS
Option Explicit
'##ModelId=486203D303C8
Private sname As String
'##ModelId=486204090138
Private pid As Integer
'##ModelId=4862041202EE
Private pname As String
'##ModelId=4862041700CB
Private passwd As String
Dim i As Integer
'##ModelId=486204F303B9
Public NewProperty As admin
'##ModelId=48620447031C
'##ModelId=4862045201B5
DATABASE.CLS
Option Explicit
'##ModelId=4862047500CB
TESTING:
Testing is the process of executing a program with the intent of finding errors.
TEST CASE 1:
BLACKBOX TESTING:
Black box testing or behavioral testing on the functional requirements of software.
Black box testing enables the software Engineer to drive sets of input condition that will
fully exercise all functional requirements for a program.
Input:
Product Name or Product ID
Output:
View the Product Details which is purchased.
Remark:
Expected result is obtained.
TEST CASE 2:
VALIDATION TESTING:
Validation testing refers to different set of activities that ensures that the software
that has been built to traceable to customer requirements.
CUSTOMER DETAILS:
Input:
Customer Name, ID,Product Name, ID.
Output:
View and Purchase operations are carried out.
Remark:
Expected result is obtained.
ADMINISTRATOR DETAILS:
Input:
Admin Name, Admin ID, Product ID.
Output:
Add, View and Update operations are carried out.
Remark:
Expected result is obtained.
RESULT CHECKING:
Input:
Given the Product ID.
Output:
Total Purchased Products are displayed.
Remark:
Expected result is obtained.
RESULT ANALYSIS:
Input:
Products in the database act as an input.
Output:
Product information like Name, ID, Quantity and its price is displayed.
Remark:
Expected result is obtained.
CONCLUSION:
Thus the STOCK MAINTENANCE SYSTEM was developed using Rational Rose
for UML (Unified Modeling Language) diagrams and the software was implemented in
Visual Basic and the output was verified.