Showing posts with label OOAD. Show all posts
Showing posts with label OOAD. Show all posts

Thursday, 2 May 2013

NOTES FOR THE 6th SEMESTER .......... INFORMATION TECHNOLOGY DEPT

NOTES FOR THE 6th SEMESTER .......... INFORMATION TECHNOLOGY DEPT

pls click the link below to download the notes.........

https://docs.google.com/file/d/0B1MEIl-F-DIQbncyM3VmekplTDA/edit?usp=sharing

BITSA wishes all its subscribers all success for the exams!!!!!!!!

further notes to be updated soon.........

Monday, 22 April 2013

OOAD - UML DIAGRAM FOR ONLINE COURSE REGISTRATION (JAVA CODE)

//Source file: E:\\OOAD\\4. Stock Maintanence System\\administration.java


public class administration
{
   private int userid = integer;
   private int password = string;
   private int coursefee = integer;
   private int feedue = string;
   private int marks = integer;
   private integer attendence;
  
   /**
    * @roseuid 5139804D0044
    */
   public administration()
   {
   
   }
  
   /**
    * @roseuid 47793A4A0167
    */
   public void login()
   {
   
   }
  
   /**
    * @roseuid 47793A4E02AF
    */
   public void logout()
   {
   
   }
  
   /**
    * @roseuid 47793A95030D
    */
   public void macoursedetails()
   {
   
   }
  
   /**
    * @roseuid 47793AA70203
    */
   public void displaycourse()
   {
   
   }
  
   /**
    * @roseuid 47793ABB0213
    */
   public void conformation()
   {
   
   }
}




//Source file: E:\\OOAD\\4. Stock Maintanence System\\student.java


public class student
{
   private int sid = integer;
   private int password = string;
   private int name = string;
   private int age = int;
   private int sex = string;
   private int course = string;
   private int attendence = integer;
  
   /**
    * @roseuid 5139804C0053
    */
   public student()
   {
   
   }
  
   /**
    * @roseuid 477939A100FA
    */
   public void login()
   {
   
   }
  
   /**
    * @roseuid 477939A7002E
    */
   public void logout()
   {
   
   }
  
   /**
    * @roseuid 477939AC0196
    */
   public void conformation()
   {
   
   }
  
   /**
    * @roseuid 477939B600CB
    */
   public void register()
   {
   
   }
  
   /**
    * @roseuid 477939BC0167
    */
   public void viewcourseDetails()
   {
   
   }
}

OOAD UML DIAGRAM FOR STOCK MANAGEMENT SYSTEM - LAB EXPERIMENT (JAVA CODE)

//Source file: E:\\OOAD\\4. Stock Maintanence System\\Dealer.java

import Database;

public class Dealer
{
   private int DealerName;
   private int DateOfItemReceived;
   private int Address;
   private int ContactNumber;
   private int Price;
   private int No.OfItemOrdered;
   private int No.OfItemSold;
  
   /**
    * @roseuid 513042800012
    */
   public Dealer()
   {
   
   }
  
   /**
    * @roseuid 51303F8E02B4
    */
   public void Purchase()
   {
   
   }
  
   /**
    * @roseuid 51303F9400E8
    */
   public void Sales()
   {
   
   }
  
   /**
    * @roseuid 51303F9901DA
    */
   public void ShowStockDetails()
   {
   
   }
}





//Source file: E:\\OOAD\\4. Stock Maintanence System\\Manufacturer.java


public class Manufacturer
{
   private int ManufacturerName;
   private int CompanyName;
   private int DateOfManufactured;
   private int Address;
   private int ContactNumber;
   private int Price;
  
   /**
    * @roseuid 5130427F0006
    */
   public Manufacturer()
   {
   
   }
  
   /**
    * @roseuid 51303F3402E8
    */
   public void Purchase()
   {
   
   }
  
   /**
    * @roseuid 51303F39008D
    */
   public void Sales()
   {
   
   }
}




//Source file: E:\\OOAD\\4. Stock Maintanence System\\ShopKeeper.java


public class ShopKeeper
{
   private int ShopkeperName;
   private int Address;
   private int ContactNumber;
   private int Price;
   private int No.OfItemsOrdered;
  
   /**
    * @roseuid 513040C802C4
    */
   public ShopKeeper()
   {
   
   }
  
   /**
    * @roseuid 5130402003AE
    */
   public void Purchase()
   {
   
   }
  
   /**
    * @roseuid 51304025028C
    */
   public void Sales()
   {
   
   }
}




OOAD UML DIAGRAM FOR LAB EXPERIMENT - EXAM REGISTRATION (JAVA CODE)

//Source file: E:\\gooad\\exp 3\\database.java


public class database
{
   private int id;
   private int name;
   private int phoneNumber;
   private int subject;
 
   /**
    * @roseuid 511DD8BC0173
    */
   public database()
   {
  
   }
 
   /**
    * @roseuid 511DD7FA0036
    */
   public void displayRegistration()
   {
  
   }
 
   /**
    * @roseuid 511DD803034C
    */
   public void displaySubject()
   {
  
   }
 
   /**
    * @roseuid 511DD80A0205
    */
   public void update()
   {
  
   }
}





//Source file: E:\\gooad\\exp 3\\examDatabase.java


public class examDatabase
{
   private int id;
   private int name;
   private int address;
   private int phoneNumber;
   private int subject;
  
   /**
    * @roseuid 511DD8BC00C6
    */
   public examDatabase()
   {
   
   }
  
   /**
    * @roseuid 511DD7B30224
    */
   public void update()
   {
   
   }
  
   /**
    * @roseuid 511DD7B80194
    */
   public void modify()
   {
   
   }
  
   /**
    * @roseuid 511DD7BC0289
    */
   public void select()
   {
   
   }
  
   /**
    * @roseuid 511DD7C0009E
    */
   public void displayId()
   {
   
   }
}


OOAD - UML DIAGRAM FOR BOOK BANK (OOAD LAB PROGRAM OUTPUT) - JAVA CODE


//Source file: E:\\OOAD\\2. BOOK BANK\\bookBankEmployee.java


public class bookBankEmployee extends admin
{
   private int semesterBookList;
   private int authenticationForm;
   private int applicationForm;
   private int payment;
  
   /**
    * @roseuid 5114A5D200A7
    */
   public bookBankEmployee()
   {
   
   }
  
   /**
    * @roseuid 5114A59F0240
    */
   public void update()
   {
   
   }
}






//Source file: E:\\OOAD\\2. BOOK BANK\\student.java

import admin;
import bookBankInformation;

public class student extends admin
{
   private int application;
   private int verification;
   private int submission;
  
   /**
    * @roseuid 5114A5D20069
    */
   public student()
   {
   
   }
  
   /**
    * @roseuid 5114A5670000
    */
   public void payment()
   {
   
   }
}

OOAD UML DIAGRAM FOR PASSPORT AUTOMATION SYSTEM (JAVA CODE)

//Source file: E:\\OOAD\\1\\adminAuthentication.java


public class adminAuthentication
{
   private string username;
   private password string password;
  
   /**
    * @roseuid 51148491038D
    */
   public adminAuthentication()
   {
   
   }
  
   /**
    * @roseuid 5113760B0301
    */
   public void login()
   {
   
   }
}



//Source file: E:\\OOAD\\1\\adminPanel.java


public class adminPanel
{
   private datagrid yetToBeProcessedAppllication;
   private datagrid dispatchedApplication;
   private number applicantId;
  
   /**
    * @roseuid 5114849103D1
    */
   public adminPanel()
   {
   
   }
  
   /**
    * @roseuid 511376B2005C
    */
   public void process()
   {
   
   }
}


//Source file: E:\\OOAD\\1\\applicationStatus.java


public class applicationStatus
{
   private number applicationId;
  
   /**
    * @roseuid 51148492001C
    */
   public applicationStatus()
   {
   
   }
  
   /**
    * @roseuid 511375D501EA
    */
   public void getStatus()
   {
   
   }
}




//Source file: E:\\OOAD\\1\\bookBankEmployee.java


public class bookBankEmployee extends admin
{
   private int semesterBookList;
   private int authenticationForm;
   private int applicationForm;
   private int payment;
  
   /**
    * @roseuid 5114A5D200A7
    */
   public bookBankEmployee()
   {
   
   }
  
   /**
    * @roseuid 5114A59F0240
    */
   public void update()
   {
   
   }
}




//Source file: E:\\OOAD\\1\\gender.java


public class gender
{
   private radiobutton male;
   private radiobutton female;
  
   /**
    * @roseuid 511484910327
    */
   public gender()
   {
   
   }
}


//Source file: E:\\OOAD\\1\\newRegistration.java


public class newRegistration
{
   private string name;
   private number age;
   private date DOB;
   private string placeOfBirth;
   private int gender;
   private string fathername;
   private string mothername;
   private string address;
  
   /**
    * @roseuid 5114849102D2
    */
   public newRegistration()
   {
   
   }
  
   /**
    * @roseuid 511374E70282
    */
   public void register()
   {
   
   }
  
   /**
    * @roseuid 5113752C03DF
    */
   public void cancel()
   {}   
   }
}

Sunday, 10 February 2013

DATE: PASSPORT AUTOMATION SYSTEM - OOAD Lab - III Year - IT Department - Anna University Chennai



EX.NO:2 c
DATE: PASSPORT AUTOMATION SYSTEM
AIM:
To analyze and design a system for Passport Automation using Rational Rose tool.
1. PROBLEM STATEMENT
To create a software system for the applicant(s), applying for the passport by
verifying the information provided by them.
2. OVERALL DESCRIPTION
The modules are for
1. Applicant
Applicant has to provide the information like Name, Gender, Age,
Qualification, Parents’ Name, Communication address, Phone no,
etc. Also, they need to provide the DD details.
2. Passport Issuing Authority
This system will verify the details provided by the applicant. And
check whether the applicant is provided with passport or not. The
details of the applicant are stored in the Database.
3. Database
This will store the details of the applicant for future reference.
2.1 SOFTWARE REQURIEMENTS
1. Rational Rose
2.2 HARDWARE REQURIMENTS
1. 128MB RAM
2. Pentium III Processor
3. DESIGN
3.1 USE CASE DIAGRAM
Issue applicant details
applying for passprot
Verify the applicant details
DB
Issue Passport
Passport issue
authority
Cancellation
Applicant
3.2 CLASS DIAGRAM
3.2 SEQUENCE DIAGRAM
3.3 COLLABORATION DIAGRAM
3.4 COMPONENET DIAGRAM
JAVA CODING:
Database.java
public class database
{
private int applicantDetails;
public database()
{ }
public void storeTheDetails()
{ }
public void issueDetailsToAuthortiy()
{ }
}
Applicant.java
public class APPLICANT
{
private int firstName;
private int surname;
private int Sex;
private int DOB;
private int placeOfBirth;
private int district;
private int qualification;
private int height;
private int weight;
private int presnetAddress;
private int permanentAddress;
private int fathersName;
private int mothersName;
private int emailId;
private int phoneNumber;
private int DDNO;
private int DDDATE;
public passportIssueAuthority thePassportIssueAuthority;
}
public APPLICANT()
{ }
PassportIssueAuthority.java
public class passportIssueAuthority
{
private int authorityName;
private int authorityId;
private int workPlace;
public APPLICANT theAPPLICANT;
public database theDatabase;
public passportIssueAuthority()
{}
public void issuePassport()
{ }
public void verify()
{ }
public void cancellation()
{ }
}
RESULT:
Thus the UML diagrams for Passport Automation System was analyzed and designed
using Rational Rose.

Gantt Chart for Passport Automation System - III Year - IT Departmetn - Anna University Chennai



Gantt Chart for Passport Automation System
Ex No : 2. b
Date:
Aim:
To develop a risk management and project plan for passport automation system
using Gantt Chart.
Introduction:
A Gantt chart is a type of bar chart that illustrates a project schedule. Gantt charts
illustrate the start and finish dates of the terminal elements and summary elements of a
project. Terminal elements and summary elements comprise the work breakdown
structure of the project. Some Gantt charts also show the dependency (i.e., precedence
network) relationships between activities. Gantt charts can be used to show current
schedule status using percent-complete shadings and a vertical "TODAY" line as shown
here.
Passport Automation System
For the project, the activities considered are:
1. Requirement Analysis
2. Literature Survey and Specification
3. Preliminary Design
4. Detailed Design
5. Testing
6. Operation and Maintenance
Result:
Thus the risk management and project plan for passport automation system was
designed using Gantt Chart.

PASSPORT AUTOMATION SYSTEM - OOAD - III Year - IT department - Anna university chennai



PASSPORT AUTOMATION SYSTEM
Ex. No: 2.a
Date:
Aim:
To Study the software requirements specification for passport automation system.
Problem Statement
Passport Automation System is used in the effective dispatch of passport to all
of the applicants. This system adopts a comprehensive approach to minimize the manual
work and schedule resources, time in a cogent manner. The core of the system is to get
the online registration form (with details such as name, address etc.,) filled by the
applicant whose testament is verified for its genuineness by the Passport Automation
System with respect to the already existing information in the database. This forms the
first and foremost step in the processing of passport application. After the first round of
verification done by the system, the information is in turn forwarded to the regional
administrator's (Ministry of External Affairs) office. The application is then processed
manually based on the report given by the system, and any forfeiting identified can make
the applicant liable to penalty as per the law. The system also provides the applicant the
list of available dates for appointment to 'document verification' in the administrator's
office, from which they can select one. The system forwards the necessary details to the
police for its separate verification whose report is then presented to the administrator. The
administrator will be provided with an option to display the current status of application
to the applicant, which they can view in their online interface. After all the necessary
criteria has been met, the original information is added to the database and the passport is
sent to the applicant.
Software Requirements Specification
1.0 Introduction
Passport Automation System is an interface between the Applicant and the Authority
responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of
Passport and reduce the complexities involved in it to the maximum possible extent.
1.1 Purpose
If the entire process of 'Issue of Passport' is done in a manual manner then it
would take several months for the passport to reach the applicant. Considering the fact
that the number of applicants for passport is increasing every year, an Automated System
becomes essential to meet the demand. So this system uses several programming and
database techniques to elucidate the work involved in this process. As this is a matter of
National Security, the system has been carefully verified and validated in order to satisfy
it.
1.2 Scope
• The System provides an online interface to the user where they can fill in their personal
details and submit the necessary documents (may be by scanning).
• The authority concerned with the issue of passport can use this system to reduce his
workload and process the application in a speedy manner.
• Provide a communication platform between the applicant and the administrator.
• Transfer of data between the Passport Issuing Authority and the Local Police for
verification of applicant's information.
• Users/Applicants will come to know their status of application and the date in which
they must subject themselves for manual document verification.
1.3 Definitions, Acronyms and the Abbreviations
• Administrator - Refers to the super user who is the Central Authority who has been
vested with the privilege to manage the entire system. It can be any higher official in the
Regional Passport Office of Ministry of External Affairs.
• Applicant - One who wishes to obtain the Passport.
• PAS - Refers to this Passport Automation System.
• HTML - Markup Language used for creating web pages.
• J2EE – Java 2 Enterprise Edition is a programming platform and it is the partof the java
platform for developing and running distributed java applications.
• HTTP - Hyper Text Transfer Protocol.
• TCP/IP – Transmission Control Protocol/Internet Protocol is the communication
protocol used to connect hosts on the Internet.
1.4 References
IEEE Software Requirement Specification format.
1.5 Technologies to be used
• HTML • JSP • Javascript
• Java • XML • AJAX
1.6 Tools to be Used
• Eclipse IDE ( Integrated Development Enivronment)
• Rational Rose tool ( for developing UML Patterns)
1.7 Overview
SRS includes two sections overall description and specific requirements - Overall
description will describe major role of the system components and inter-connections.
Specific requirements will describe roles & functions of the actors.
2.0 Overall Description
2.1 Product Perspective
The PAS acts as an interface between the 'applicant' and the 'administrator'. This
system tries to make the interface as simple as possible and at the same time not risking
the security of data stored in. This minimizes the time duration in which the user receives
the passport.
2.2 Software Interface
Front End Client - The applicant and Administrator online interface is built using JSP
and HTML. The Administrators's local interface is built using Java.
Web Server - Glassfish application server(Oracle Corporation).
Back End - Oracle database.
2.3 Hardware Interface
The server is directly connected to the client systems. The client systems have
access to the database in the server.
2.4 System Functions
• Secure Registration of information by the Applicants.
• Schedule the applicants an appointment for manual verification of original documents.
• Panel for Passport Application Status Display by the Administrator.
• SMS and Mail updates to the applicants by the administrator.
• Administrator can generate reports from the information and is the only authorized
personnel to add the eligible application information to the database.
2.5 User Characteristics
• Applicant - They are the people who desires to obtain the passport and submit the
information to the database.
• Administrator - He has the certain privileges to add the passport status and to approve
the issue of passport. He may contain a group of persons under him to verify
the documents and give suggestion whether or not to approve the dispatch of passport.
• Police - He is the person who upon receiving intimation from the PAS, perform a
personal verification of the applicant and see if he has any criminal case against him
before or at present. He has been vetoed with the power to decline an application by
suggesting it to the Administrator if he finds any discrepancy with the applicant. He
communicates via this PAS.
2.6 Constraints
• The applicants require a computer to submit their information.
• Although the security is given high importance, there is always a chance of intrusion in
the web world which requires constant monitoring.
• The user has to be careful while submitting the information. Much care is required.
2.7 Use Case Model Description
The usecase model is a representation of the interaction between the users and the
system. It captures the goals of the users and the responsibility of the system to the users.
It is a special flow of events through the system. Grouping of usecases can manages the
complexities and reduce the number of usecases in the package. The usecase model
describes the uses of the system and show the courses of events that can be performed. A
usecase is an interaction between user and system; it captures the goals of the user and
the responsibility of the system to its users. It defines what happens in the system when
the usecase is performed.
2.8 Assumptions and Dependencies
• The Applicants and Administrator must have basic knowledge of computers and
English Language.
• The applicants may be required to scan the documents and send.
Result: Thus the software requirements specification for passport automation system was
studied.
Back To Top