Sie sind auf Seite 1von 70

CASE STUDY: STUDENT ENROLLMENT SYSTEM

1. Problem analysis and project planning:

Problem Statement:

A UNIVERSITY HAS CONTRACTED TO DEVELOP THEIR NEW STUDENT RECORDS


SYSTEM. A Student Information System (SIS)is a software application for educational
establishments to manage student data. Student Information System provide capabilities for entering a
student test and other assessment scores, building student schedules, tracking student attendance, and
managing many other student related data needs in a university.

Project Statement: The given problem is to model STUDENT ENROLLMENT SYSTEM.

Objective:

The main objective of the project is to enroll a student in the university as per the course he selected
and also check the availability of the course. The student pays the fees if he joined and should get a
transcript form university.

2. Software requirement and analysis:

Functional Requirements:

Registration:
Student should get registered in university of course.
Student should receive transcript if he enrolled properly.

Administration:
Administrator should list courses available to students.
Admin should provide login credentials for student.

Non-Functional Requirements:

Performance Requirements:
The university will get more students if every course was available.

Safety Requirements:
Student should be careful in selecting course and also login credentials should be secure.

Security Requirements:
System will use secured database
Every student can join the university as there are particular rules.
System will have different types of users and every user has access constraints.

1
Software Requirements:
Operating System : Windows 8/10
Coding Language : JAVA/J2EE
IDE : My Eclipse 8.0
Database : MYSQL

Hardware Requirements:
System : I3 and above.
Hardware : 40 GB.
Ram : 512 Mb.

2
3. Software Designing:

UML Diagrams

i. Use Case Diagram :

For Administrator:

For Student:

3
ii. Sequence Diagram:

For Validity:

For Administrator:

4
For Student:

iii. Collaboration Diagram:

For Validity:

5
For Administrator:

For Student:

6
iv. Activity Diagram:

v. Component Diagram:

7
vi. Deployment Diagram:

vii. Class Diagram:

8
4. Prototype:

importjava.awt.event.*;
importjava.awt.*;
importjavax.swing.*;
importjava.sql.*;
public class jdbcframe1 extends JFrame implements ActionListener
{
publicJLable 11,12,13,14,15;
publicJTextField t1,t2,t3,t4,t5;
publicJButton b1;
Container c;
public jdbcframe1()
{
setSize(180,400);
setTitle("STUDENT DETAILS");
setVisible(ture);
setDefaultCloseOperation(Jframe.Exit_ON_CLOSE);
c=getContentPane();
c.setLayout(new FlowLayout());
11=new JLabel("Regon");
c.add(11);
t1=new JTextField(10);
c.add(t1);
12=new JLabel("Name");
c.add(12);
t2=new JTextField(10);
c.add(t2);
13=new JLable("Dept");
c.add(13);
t3=new JTextField(10);
c.add(t3);
14=new JLable("Course");
c.add(14);
t4=new JTextField(10);
c.add(t4);
15=new JLable("Contact");
c.add(15);
t5=new JTextField(10);
c.add(t5);
b1=new JButton("SAVE");
c.add(b1);
b1.addActionListener(this);
}

9
Public void actionPerformed(ActionEventae)
{
if(ae.getSource()==b1)
{
try
{
Class.forName("sun.jdbc.odbc.jdbcOdbcDriver");
Connection con=DriverManager.getConnection("jdbc:odbc:student");
Statement st=con.createStatement();
PreparedStatement ps,ps1;
ps1=con.PrepareStatement("slecte * from student where regno="+t1.getText());
ps=con.PrepareStatement("insert into
student(regno,name,dept,course,contact)values(?,?,?,?,?)");
ps.setString(1,t1.getText());
ps.setString(2,t2.getText());
ps.setString(3,t3.getText());
ps.setString(4,t4.getText());
ps.setString(5,t5.getText());
ps.excuteUpdate();
JOptionPane.showMessageDialog(null,"RECORD SAVED");
}
catch(SQLExceptionsq)
{
System.out.println(sq);
System.out.println("\n Hai this place is error occur");
}
catch(Exception e)
{
System.out.println(e);
}
}
}
public static void main(String args[])
{
jdbcframe1 f=new jdbcframe1();
}
}

10
CASE STUDY: ONLINE BOOKSHOP
1. Problem analysis and project planning:

Problem Statement:

A MAJOR BOOK RETAILER IS PLANNING TO DEVELOP A COMPUTER SYSTEM TO


HANDLE THEIR NEW ONLINE BOOKSHOP: BOOKY.COM. You have been chosen to do the
analysis and design. The following requirements have been identified: Customers can search for
books on the Booky.com website, either by author name, or words in the title. A list of all matching
books is returned to the customer. A customer does not need to be logged-in in order to search. The
system records all the customers of the Booky.com who have ever logged in.

Project Statement: The given problem is to model ONLINE BOOKSHOP.

Objective:

The main objective of the project is to create an online book shop that allows to search and purchase a
book online based on title, author and subject. The selected books are displayed in a tabular format
and user can order books online through credit card payment. Using this website the user can purchase
a book online.

2. Software requirement and analysis:

Functional Requirements:

Registration:
Customers who wish to purchase book can register on the website.
Customer should receive an email as conformation.

Purchase:
Customer can add the selected product in the shopping cart.
The prices of the product in the shopping care are added and can be paid.

Non-Functional Requirements:

Performance Requirements:
The system shall accommodate high number of books and users without any fault.

Safety Requirements:
System use shall not cause any harm to human users.

Security Requirements:
System will use secured database
 Normal users can just read information but they can’t edit or modify anything.
System will have different types of users and every user has access constraints.

11
Software Requirements:
Operating System : Windows 8/10
Coding Language : JAVA/J2EE
IDE : My Eclipse 8.0
Database : MYSQL

Hardware Requirements:
System : I3 and above.
Hardware : 40 GB.
Ram : 512 Mb.

12
3. Software Designing
UML Diagrams
i. Use Case Diagram

13
ii. Class Diagram:

14
iii. Sequence Diagram:

15
iv. Collaboration Diagram :

16
v. Activity Diagram:

17
vi. Component Diagram:

vii. Deployment Diagram:

18
4. Prototype

java core packages

import java.io.*;

public class BookBean implements Serializable {


private static final long serialVersionUID = 672341178342776147L;
private String ISBN, title, copyright, imageFile;
privateinteditionNumber, PublisherID;
private double price;

// set ISBN number


public void setISBN( String isbn)
{
ISBN = isbn;
}

// return ISBN number


public String getISBN ()
{
return ISBN;
// set book title
public void setTitle( String bookTitle)
{
title = bookTitle;
}
// return book title
public String getTitle()
{
return title;
}
// set copyright year
public void setCopyright( String year)
{
copyright = year;
}
// return copyright year
public String getCopyright()
{
return copyright;
}
// set file name of image representing product cover
public void setImageFile( String fileName )
{
imageFile = fileName;
}
// return file name of image representing product cover
public String getImageFile()
{
returnimageFile;
}
// set edition number
public void setEditionNumber( int edition )
{

19
editionNumber = edition;
}
// return edition number
publicintgetEditionNumber()
{
returneditionNumber;
}
// set Publisher ID number
public void setpublisherID( int id )
{
PublisherID =id;
}
// return Publisher ID number
publicintgetpublisherID()
{
returnPublisherID;
}
// set price
public void setprice( double amount )
{
price = amount ;
}
// return price
public double getprice ()
{
return price;
}
}

20
CASE STUDY: COURSE MANAGEMENT SYSTEM
1. Problem Analysis and Project Planning

Problem Statement:

A course management system(CMS) is a collection of software tools providing an online environment


for course interactions. A CMS typically includes a variety of online tools and environments.

Project Statement:The given problem is to model COURSE MANAGEMENT SYSTEM.

Objective:

The main objective of course management system is to provide services between students and
faculty. They are an increasingly important part of academic systems in higher education.

2. Software requirement Analysis

Functional Reqirements:

Grade Management: The system should be capable of managing student grades.

Group Management: The system should support group management features. Such
features are especially important for courses with group projects.

Ability to create groups


Integration with homework submissions
Integration with grade management
Group maintenance

Non functional Requirements:


Performance Requirements:

The system shall accommodate high number of courses and users without any fault.

Safety requirements:

System use shall not cause any harm to human users.

Security Requirements:

System will use secured database


 Normal users can just read information but they can’t edit or modify anything.
System will have different types of users and every user has access constraints.

21
Software Requirements:

Operating System : Windows XP/7


Coding Language : JAVA/J2EE
IDE : My Eclipse 8.0
Database : MYSQL

Hardware Requirements:

System : 13 and above


Hard Disk : 40 GB
Ram : 512 Mb

22
3. Software Designing

UML Diagrams:

i. Use Case Diagram:

System

assign course to tutor

view tutor

tutor
view course calander
administrator

manage course

view course
<<include>>
student
types of courses

view student

manage topic for course

manage tutor information

manage student tutor

23
ii. Class Diagram:

course administrator student

+name +student id
+password +student name
+id +qualification
+contact no
manages
+manage course() +email id
+view course() +address
+manage topic()
+assign tutor() +view student information()
+manage tutor +delete student information()
information() +modify student information()
+manage statement() +create student()
+view student() +view all student()

prepares
view

course calander

+day
+start time
+end time
+start day
manages +end day
manages
+tutor name
assigns
+view course calander()
+modify course calander()
+delete course calander()
+create course calander()

contains

topic
tutor course
+topic name
+tutor name +topic id +course name
+tutor id +content +course id
+tutor password +view course()
+manage topic()
+view tutor information() +view topic() +modify course()
+create tutor information() +create topic() +remove course()
+rename tutor() +rename topic() +create course()
+create tutor() +view topic
information()

24
iii. Deployment Diagram:

PRO_APP_SERVER
PRO_WEB_SERVER PRO_DB_SERVER

http http
<<title>> <<executable>> model
<<APACHE TOMCAT>>
view controller
<<MY SQL>>

iv. Collaboration Diagram:

: course:course

/CmsUser : user

2 .create course
1 : manage course()

3 : topic id()
4 : create topic() /topic : topic

: courseadmin:admin 5 : topic id()

25
v. Sequence Diagram:

/CmsUser : user / : courseadmin:admin / : course:course /topic : topic / : tutor :tutor

1 : manage course()

2 : create course()

3 : course id()

4 : create topic()

5 : topic id()

6 : assign tutor to course()

vi. Component Diagram:

<<title>> <<executable>>
view
controller
userinterfaceFiles
CMSController

model

/ : course admin

<<library>>
: course:Course : topic:Topic

database access
: coursecalender:CourseCalender

: :student :Student

26
vii. Activity Diagram

manage code

[course ends]
create course
[new course]

[modify course] [remove course]


create topic

assign tutor
modify course remove course

prepare course calander

course completed

27
4. Prototype Model:

Import java.awt.*;
Import java.applet.*;
Import java.awt.event.*;
Public class student extends Frame implemrnts Action Listener
{
String msg;
Button b1=new Button(“Save”);
Lable LL1= new Lable(“student details”,Label.CENTER);
Lable l1=new Lable(“Name:”,Lable.LEFT);
Lable l2=new Lable(“age:”,Lable.LEFT);
Lable l3=new Lable(“Sex(M/F):”,Lable.LEFT);
Lable l4=new Lable(“Address:”,Lable.LEFT);
Lable l5=new Lable(“Course:”,Lable.LEFT);
Lable l6=new Lable(“Semester:”,Lable.LEFT);
Lable l7=new Lable(“ ”,Lable.RIGHT);
TextField t1 =new TextField();
Choice c1=new Choice();
CheckboxGroupcbg =new CheckboxGroup();
Checkbox ck1=new Checkbox(“Male”,false,cbg);
Checkbox ck2=new Checkbox(“Female”,false,cbg);
TextArea t2 = new TextArea(“ “,180,90,TextArea.SCROLLBARS_VERTICAL_ONLY);
Choice course=new Choice();
Choice sem=new Choice();
Choice age=new Choice();
Public student()
{
addWindowListener(new myWindowAdapter());
setBackground(Color.cyan);
setForeground(Color.black);
setLayout(null);
add(ll1);
add(l1);
add(l2);
add(t1);
add(t2);
add(ck1);
add(ck2);
add(course);
add(sem);
add(age);
add(b1);
b1.addActionlistener(this);
add(b1);
course.add(“Bscc.s”);
course.add(“Bsc maths”);
course.add(“Bsc physics”);
course.add(“BA English”);
course.add(“BCOM”);
sem.add(“1”);

28
sem.add(“2”);
sem.add(“3”);
sem.add(“14”);
sem.add(“5”);
l1.setBounds(25,65,90,20);
l2.setBounds(25,90,90,20);
l3.setBounds(25,120,90,20);
l4.setBounds(25,185,90,20);
l5.setBounds(25,260,90,20);
l6.setBounds(25,290,90,20);
l7.setBounds(25,260,90,20);
ll1.setBounds(10,40,280,20);
t1.setBounds(120,65,170,20);
t2.setBounds(120,185,170,60);
ck1.setBounds(120,120,50,20);
ck2.setBounds(170,120,60,20);
course.setBounds(120,260,100,20);
sem.setBounds(120,290,50,20);
age.setBounds(120,90,50,20);
b1.setBounds(120,350,50,30);
}
Public void paint(Graphics g)
{
rawString(msg,200,450);
}
Public void actionPerformed(ActionEventae)
{
If(ae.getActionCommand().equals(“save”))
{
Msg=”Student details saved!”;
setForegriund(Color.red);
}
}
Public static void main(String ars[])
{
Student stu=new student();
Stu.setSize(new Dimension(500,500));
Stu.setTitle(“student registration”);
Stu.setVisible(true);
}
}
Class myWindowAdapter extends WindowAdapter
{
Public void windowClosing(WindowEvent we)
{
System.exit(0);
}
}

29
CASE STUDY: ELECTRONIC CASH COUNTER
1. Problem analysis and project planning:

Problem Statement:

This project is mainly developed for the Account Division of a Banking sector to provide better
interface of the entire banking transactions. This system is aimed to give a better out look to the user
interfaces and to implement all the banking transactions like:
• Supply of Account Information • New Account Creations • Deposits • Withdraws • Cheque book
issues • Stop payments • Transfer of accounts • Report Generations.

Project Statement:The given problem is to model ELECTRONIC CASH COUNTER.

Objective:

The main objective of the project is to develop that a number of factors relating to the time the
customer spends with a bank. Without usage of technology, The banking sector cannot provide
customers with a satisfactory service. So the main objective is to develop an effective service delivery
which is new or significantly improved concept that is taken into practice.

So for this project of electronic cash counter we may consider an example of an ATM. Where we
study different case study for Atm.

2. Software requirement and analysis:

Functional Requirements:

New accounts creation


Manage the transaction of account
Security issue

Software Requirements:

Operating System : Windows 8/10


Coding Language : JAVA/J2EE
IDE : My Eclipse 8.0
Database : MYSQL

Hardware Requirements:

System : I3 and above.


Hardware : 40 GB.
Ram : 512 Mb.

30
3. Software Designing
UML Diagrams

i. Use Case Diagram For ATM :

31
ii. Class Diagram For ATM:

32
MGIT SDM LAB

iii. Sequence Diagram For ATM:

iv. Collaboration Diagram For ATM:

33
v. Activity Diagram For ATM:

34
vi. Component Diagram For ATM:

vii. Deployment Diagram For ATM:

35
4. Prototype Model

import java.util.Scanner;
public class ATM_Transaction
{
public static void main(String args[] )
{
int balance = 5000, withdraw, deposit;
Scanner s = new Scanner(System.in);
while(true)
{
System.out.println("Automated Teller Machine");
System.out.println("Choose 1 for Withdraw");
System.out.println("Choose 2 for Deposit");
System.out.println("Choose 3 for Check Balance");
System.out.println("Choose 4 for EXIT");
System.out.print("Choose the operation you want to perform:");
int n = s.nextInt();
switch(n)
{
case 1:
System.out.print("Enter money to be withdrawn:");
withdraw = s.nextInt();
if(balance >= withdraw)
{
balance = balance - withdraw;
System.out.println("Please collect your money");
}
else
{
System.out.println("Insufficient Balance");
}
System.out.println("");
break;
case 2:
System.out.print("Enter money to be deposited:");
deposit = s.nextInt();
balance = balance + deposit;
System.out.println("Your Money has been successfully depsited");
System.out.println("");
break;
case 3:
System.out.println("Balance : "+balance);
System.out.println("");
break;
case 4:
System.exit(0);
}
}
}
}

36
CASE STUDY: EXAMINATION BRANCH SYSTEM
1. Problem analysis and project planning:

Problem Statement:

The project Examination Branch System is to reduce the overhead involved in the process of
maintains the data and the transaction in the Examination branch.

Project Statement: The given problem is to model EXAMINATION BRANCH SYSTEM.

Objective:

Examination branch is an intranet application for an organization. It is software which is used to


perform all the examination activities like adding employees, search employees, delete employees
and assign examination duties.

The basic framework of the project can be developed in .NET. Making use of this application the
administrator can perform their activities through it.

Features Of Examination Branch System

The proposed examination branch system application serves the following features:

Add teaching and non teaching members


Manage the personal timetable of the faculty
View all members
Search the staff accordingly
Assign the examination duties to the staff
Features of edit update and delete.

2. Software requirement and analysis:

Software Requirements:
 Operating System : Windows 8/10
 Coding Language : MS VISUAL STUDIO.NET 2008
 Database : MYSQL

Hardware Requirements:
System : I3 and above.
Hardware : 40 GB.
Ram : 512 Mb.

37
3. Software Designing
UML Diagrams
i. Use Case Diagram

ii. Sequence Diagram

38
iii. Component Diagram

iv. Activity Diagram

39
v. Class Diagram

vi. Collaboration Diagram

40
4. Prototype

import java.awt.*;
import java.sql.*;

public class examination extends Frame


{
int stdno,i;
int qcounter;
String topi;
int count=0;
int qno;
String[] ques;
String[] op1;
String[] op2;
String[] op3;
String[] op4;
String[] ans;
String[] uans;
String[] umark;
Panel p,p1,p3;
Label l1,l2,l3;
Button pre,n,m,c;
CheckboxGroup radio;
Checkbox radioop1,radioop2,radioop3,radioop4;
int qmark;
mythread mn;
results a2;
public examination(int snum,String top)
{
qcounter=0;
stdno=snum;
topi=top
try
{
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection c=DriverManager.getConnection("jdbc:odbc:sirisha");
Statement st=c.createStatement();
ResultSet rs=st.executeQuery("Select * from question where topic='"+topi+"' order by qno");

while(rs.next())
{
count++;
}
st.close();
ques = new String[count]
op1=new String[count];
op2=new String[count];
op3=new String[count];
op4=new String[count];
ans=new String[count];
uans=new String[count];

41
umark=new String[count];
Statement st1=c.createStatement();
rs=st1.executeQuery("Select * from question where topic='"+topi+"'");
int i=0;
while(rs.next())
{
ques[i]=rs.getString(2);
op1[i]=rs.getString(4);
op2[i]=rs.getString(5);
op3[i]=rs.getString(6);
op4[i]=rs.getString(7);
ans[i]=rs.getString(8);
umark[i]="N";
i++;
}

st1.close();
System.out.println(count);
}
catch(Exception e)
{
System.out.println("inside:"+e);
e.printStackTrace();
}
p=new Panel();
p3=new Panel();
p1=new Panel();
pre=new Button("Previous");
n=new Button("Next");
m=new Button("Mark/Unmark");
c=new Button("Close");
// System.out.println("Value of ques[]"+ques[qcounter]);
l1=new Label(""+ques[qcounter]);
qno=qcounter+1;
l3=new Label("Time :00::50::00");
l2=new Label("Q.NO"+qno+"of"+count);
p.add(l1);
p3.add(l2);
p3.add(l3);
p1.add(pre);
p1.add(n);
p1.add(m);
p1.add(c);
radio=new CheckboxGroup();
radioop1=new Checkbox(op1[qcounter],radio,false);
radioop2=new Checkbox(op2[qcounter],radio,false);
radioop3=new Checkbox(op3[qcounter],radio,false);
radioop4=new Checkbox(op4[qcounter],radio,false);
p.add(radioop1);
p.add(radioop2);
p.add(radioop3);

42
p.add(radioop4);
add("Center",p);
add("South",p1);
add("North",p3);
mn=new mythread(this);
mn.start();
show();
}
public boolean handleEvent(Event e)
{
if(e.id==Event.WINDOW_DESTROY)
System.exit(0);

return super.handleEvent(e);
}
public boolean action(Event e,Object o)
{
if(e.target.equals(pre))
{
qcounter=qcounter-1;
if(qcounter<=0)
{
qcounter=0;
}
add124(qcounter);
}
else if(e.target.equals(n))
{
qcounter=qcounter+1;
if(qcounter>=(count))
{
qcounter=qcounter-1;
}
add124(qcounter);
}
else if(e.target.equals(m))
{
umark[qcounter]="M";
}
else if(e.target.equals(c))
{
//count,uans,qmark,stdno,topi
disp124();
}
if(radioop1.getState())
{
uans[qcounter]= op1[qcounter];
}
else if(radioop2.getState())
{
uans[qcounter]= op2[qcounter];

43
}
else if(radioop3.getState())
{
uans[qcounter]= op3[qcounter];
}
else if(radioop4.getState())
{
uans[qcounter]= op4[qcounter];
}
return super.action(e,o);
}
public void disp124()
{
answerlist al=new answerlist(this);
hide();
al.resize(300,300);
al.show();
}
public void dispresults()
{
if(a2==null)
{
System.out.println("Method dispresults called");
a2=new results(this);
hide();
a2.resize(300,300);
a2.show();
}
}
public void add124(int c)
{
qcounter=c;
//p.removeAll();
umark[c]="N";
//l1=new Label(ques[c]);
l1.setText(ques[c]);
//p.add(l1);
//radio=new CheckboxGroup();
//radioop1=new Checkbox(op1[c],radio,false);
//radioop2=new Checkbox(op2[c],radio,false);
//radioop3=new Checkbox(op3[c],radio,false);
//radioop4=new Checkbox(op4[c],radio,false);
radioop1.setLabel(op1[c]);
radioop2.setLabel(op2[c]);
radioop3.setLabel(op3[c]);
radioop4.setLabel(op4[c]);

//p.add(radioop1);
//p.add(radioop2);
//p.add(radioop3);
//p.add(radioop4);

44
//add("Center",p);
l2.setText("Q.NO"+(c+1)+"of"+count);
System.out.println("change="+(c+1)+" "+count);
validate();
return;
}

}
class mythread extends Thread
{
examination ex;
mythread(examination f)
{
ex=f;
}
public void run()
{
long time=ex.count*100000;
System.out.println("time:"+time);
for(long i=0;i<time;i++)
{
long sec=i/1000;
long min=sec/60;
long hr=min/60;
sec=sec%60;
String str1="Time:"+hr+"::"+min+"::"+sec;
int qno=ex.qcounter+1;
//ex.p3.removeAll();
//Panel p3=new Panel();
//Label l2=new Label("Q.NO"+qno+"of"+ex.count);
//ex.l2.setText("Q.NO"+qno+"of"+ex.count);
//p3.add(l2);
//Label l3=new Label(str1);
ex.l3.setText(str1);
//p3.add(l3);
//ex.add("North",p3);
ex.validate();
}
System.out.println("time over...");
ex.dispresults();
//System.exit(0);
}
}

45
CASE STUDY: ENTERPRISE RESOURCE PLANNING (ERP)
1. Problem analysis and project planning:
Problem Statement:

ERP is a powerful human resource tool for maintaining employee and company information. More
than a data storage program, ERP helps you manage your employees. ERP offers a wide variety of
reports that give you exactly the information you need. View payroll information by department, or
find everyone who is receiving company
Module Description:
 Payroll
 Employee
 Employee payslip
 Selection process
 Reports
 Mailing System
 Training
 Add Company Information

Project Statement: The given problem is to model ENTERPRISE RESOURCE PLANNING.

Objective:

The proposed system is designed to eliminate all the drawbacks of the existing system. The system is
part of a large HRMS Application and shall be responsible for maintaining information about
Employees, Positions, Company Benefits, Departments, New Recruit Checklists, Employee
Achievements, Warnings, Evaluation Reports, Education & Training, Administration, Work Changes
And Several Ad Hoc Reports.

Advantages of the proposed system:

The major advantage of the proposed system is :

 It's online, so that information is available anytime.


 High integrity and security.
 Ability to incorporate newly available data.
 It is user friendly
 Speed and accuracy is increased
 Fully automated.
 Security is associated with user authentication
 Duplication of information is curbed

46
2. Software requirement and analysis:

Software Requirements:
 Operating System : Windows 8/10
 Coding Language : JAVA/J2EE
 IDE : My Eclipse 8.0
 Database : MYSQL

Hardware Requirements:
 System : I3 and above.
 Hardware : 40 GB.
 Ram : 512 Mb.

47
3. Software Designing
UML Diagrams
i. Use Case Diagram:

For Admin

For Employee

48
MGIT SDM LAB

ii. Sequence Diagram

iii. Component Diagram

49
iv. Activity Diagram

50
v. Class Diagram

vi. Deployment Diagram

51
4. Prototype

import java.io.IOException;
import java.io.PrintStream;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class appreport extends HttpServlet


{
public appreport()
{}

public void init(ServletConfig servletconfig)


throws ServletException
{
super.init(servletconfig);
try
{
System.out.println("inside try");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("driver is created");
con = DriverManager.getConnection("jdbc:odbc:hrms", "hrms", "hrms");
System.out.println("Connection is created");
st = con.createStatement();
System.out.println("statement is created");
}
catch(Exception exception)
{
System.out.println(exception);
}
}

public void service(HttpServletRequest httpservletrequest, HttpServletResponse httpservletresponse)


throws ServletException, IOException
{

java.io.PrintWriter pw = httpservletresponse.getWriter();
HttpSession httpsession = httpservletrequest.getSession(true);
httpservletresponse.setContentType("text/html");
// String submit=httpservletrequest.getParameter("B1");
try
{
// if(submit.equals("APPLICATION REPORT"))
{
System.out.println("Before inserting");
pw.println("<center><h1 >LIST OF APPLICANTS</h1></center>");

rs=st.executeQuery("select a.sno,a.name,a.qualcode,permanent_address,phonenumber,emailid from


education a,address_details where junior.sno=a.sno");
if(rs.next())
{
pw.println("<CENTER><table BORDER='3' ROWSPAN='3' COLSPAN='3'>");
pw.println("<tr><td>SNO</td>");
pw.println("<td>NAME</td>");

52
pw.println("<td>ADDRESS</td>");
pw.println("<td>PHONE</td>");

pw.println("<td>EMAILID</td></tr>");
pw.println("<td>QUALCODE</td>");
pw.println("<tr><td>"+rs.getInt(1)+"</td>");
pw.println("<td>"+rs.getString(2)+"</td>");
pw.println("<td>"+rs.getString(3)+"</td>");
pw.println("<td>"+rs.getInt(4)+"</ td>");
pw.println("<td>"+rs.getString(5)+"</td>");
pw.println("<td>"+rs.getString(6)+"</ td></tr></table></CENTER>");
}
}
/*else
//if(submit.equals("SELECTION LIST FROM INTERVIEW"))
{
rs=st.executeQuery("select a.sno,sname,presentaddress,phonenumber,wmarks from address_details
a,marks where marks.sno=a.sno");
pw.println("<center><h1 >SELECTION LIST FROM INTERVIEW </h1></center>");
if(rs.next())
{
pw.println("<CENTER><table BORDER='3' ROWSPAN='3' COLSPAN='3'>");
pw.println("<tr><td>SNO</td>");
pw.println("<td>NAME</td>");
pw.println("<td>ADDRESS</td>");
pw.println("<td>PHONE</td>");
pw.println("<td>MARKS</td></tr>");
pw.println("<tr><td>"+rs.getInt(1)+"</td>");
pw.println("<td>"+rs.getString(2)+"</td>");
pw.println("<td>"+rs.getString(3)+"</td>");
pw.println("<td>"+rs.getInt(4)+"</ td>");
pw.println("<td>"+rs.getInt(5)+"</ td></tr></table></CENTER>");
}
}*/
}
catch(Exception exception)
{
exception.printStackTrace();
System.out.println(exception);
}
}

Connection con;
Statement st;
ResultSet rs;
}
import java.io.IOException;
import java.io.PrintStream;
import java.sql.*;
import javax.servlet.*;
import javax.servlet.http.*;

public class reg2 extends HttpServlet


{

53
public void init(ServletConfig servletconfig)
throws ServletException
{
super.init(servletconfig);
try
{
System.out.println("inside try");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
System.out.println("driver is created");
con = DriverManager.getConnection("jdbc:odbc:hrms", "hrms", "hrms");
System.out.println("Connection is created");
st = con.createStatement();
System.out.println("statement is created");
}
catch(Exception exception)
{
System.out.println(exception);
}
}

public void service(HttpServletRequest httpservletrequest, HttpServletResponse httpservletresponse)


throws ServletException, IOException
{

java.io.PrintWriter pw = httpservletresponse.getWriter();
HttpSession httpsession = httpservletrequest.getSession(true);
httpservletresponse.setContentType("text/html");
try
{

if(submit.equals("add"))
{
System.out.println("Before inserting");
pw.println("<h1>call letter for interview</h1>");
pw.println("<h4 align="right">TO</h4>");

ResultSet rs=st.executeQuery("select sname,address1 from address_details");


pw.println("<table><tr><td>rs.getString(2)</td></tr>");
pw.println("<tr><td>rs.getString(3)</td></tr></table>");
pw.println("<p>Dear Applicant,</p>");
pw.println("<p><center>we refer to your application for employment with us.u have been show
interview for the position Programmer. The interview will be conducted on 02-April-2004,at 2
floor,AdityaEnclave, Hyderabad</center></p>");
pw.println("<p>From</P>");
pw.println("<p>HRD</P>");

httpservletrequest.getRequestDispatcher("./experience_details.htm").forward(httpservletrequest,httpse
rvletresponse);

// httpservletresponse.sendRedirect("./elogin.htm");
}
catch(Exception exception)

54
{
exception.printStackTrace();
System.out.println(exception);
}
}

Connection con;
Statement st;
ResultSet rs;
}

55
CASE STUDY: E-BIDDING
1. Problem analysis and project planning:

Problem Statement:

E-Bidding is the process of bidding through electronic medium. E-Procurement is the buying
of goods /services or construction work through electronic medium. The e-bidding system is
a flexible solution for supporting lot-based online auctions. The system has been designed to
be highly scalable and capable of supporting large number, if bidders in an active auction. To
help business with financer’s and purchases in online auctioning system (E-bidding)

Project statement: The given problem is to model e-bidding

Objective:
An Online Auction is service in which auction users can sell or bid for antique products
through the internet.

2. Software requirement and analysis:

Functional requirements:

i. System Feature:

Login module will provide security and authentication to the seller and buyer.
This system will only allow the administrator to see the other functionality of the system,
who having a valid username and password.

ii. User Details:

User module will contain the all information about the seller and buyer who are
registered under the online auction system. All user information like name, address,
mobile number etc, is handled by the user details module.

iii. Product Details:

Product module will contains all the information about the product. All the
information about the product name, type, price, bid time, description, photos, maximum
bidder names, final bidding price etc

iv. Seller Details:

Seller module will contains the information about the seller who are registered
under the online auction system, all seller information like name, seller id, email id etc,
are handled by the seller details module.

56
Non-Functional Requirements:

Performance requirement:

The physical machine to be used in the online auction needs to have internal access in order
to connect to the database, since all the data will be stored on the server database which the
software will need to connection.

Security requirement:

The online auction system will uses the secure authentication for the online auction system
administrator, login id and password is associated with the system administrator to provide
security over the system

No detail of the competitor bidder will be shown as it can be a case of fraud.

Software Quality Attributes:

The detail of the buyers and sellers is kept secret

No case of fraud is possible

Software Requirements

Front end : ibm eclipse

Coding language : java (jdk 1.6)

Operating system : windows xp/7

Hardware Requirements:

PROCESSOR : Pentium IV 2.4 GHz

SYSTEM TYPE : 32 bit operating system

HARD DISK : 40 GB

RAM : 512 MB

57
MGIT SDM LAB

3. Software Designing :
UML Diagrams
i. Use Case Diagram :

For Administrator:

58
ii. For Bidder

59
MGIT SDM LAB

iii. For Seller

60
iv. Sequence Diagram

61
v. Class Diagram

62
vi. Activity Diagram For Bidder

63
vii. Activity diagram for admin

64
viii. Activity diagram for seller

65
ix. State chart diagram

x. Component Diagram

user details

product details

66
xi. Collaboration Diagram

67
4. Prototype:

package adt;
Import java.util.LinkedList;
Import java.util.List;
public class Auction
{
private int auctionID;
private int quantity;
private byte closingType;
private double highestBid;
private String sellerIP;
private Item item;
private List clients;
private List biddingHistory;
private int timer;
private boolean isActive;
public Auction(int auctionID, int quantity, byte closingType, double highestBid, String sellerIP,Item
item,int timer)

{
this.auctionID = auctionID;
this.quantity = quantity;
this.closingType = closingType;
this.highestBid = highestBid;
this.sellerIP = sellerIP;
this.item = item;
this.timer = timer;
clients = new LinkedList();
biddingHistory = new LinkedList();
isActive = true;
}
public boolean isIsActive()
{
return isActive;
}
public void setIsActive(boolean isActive)
{
this.isActive = isActive;
}
public int getTimer()
{
return timer;
}
public void setTimer(int timer) {
this.timer = timer;
}
public Auction()
{
this.auctionID = 0;
this.quantity = 0;
this.closingType = 0;
this.highestBid = 0;
this.sellerIP = null;

68
this.item = null;
clients = new LinkedList();
biddingHistory = new LinkedList();
}
public List getBiddingHistory()
{
return biddingHistory;
}
public void setBiddingHistory(List biddingHistory)
{
this.biddingHistory = biddingHistory;
}
public Item getItem()
{
return item;
}
public void setItem(Item item)
{
this.item = item;
}
public int getAuctionID()
{
return auctionID;
}
public void setAuctionID(int auctionID)
{
this.auctionID = auctionID;
}
public byte getClosingType()
{
return closingType;
}
public void setClosingType(byte closingType)
{
this.closingType = closingType;
}
public double getHighestBid()
{
return highestBid;
}
public void setHighestBid(double highestBid)
{
this.highestBid = highestBid;
}
public int getQuantity()
{
return quantity;
}
public void setQuantity(int quantity)
{
this.quantity = quantity;
}
public String getSellerIP()
{

69
return sellerIP;
}
public void setSellerIP(String sellerIP)
{
this.sellerIP = sellerIP;
}
public List getClients()
{
return clients;
}
public void setClients(List clients)
{
this.clients = clients;

70

Das könnte Ihnen auch gefallen