Office Automation System For Sudharshi Institute

H.S.R.S Perera BIT Registration Number: R052100 Index Number: 0521002

Name of the supervisor: Mr. Kasun Thilina

2011/ 2012

BIT This dissertation is submitted in partial fulfilment of the requirement of the Degree of Bachelor of Information Technology (External) of the University of Colombo School of Computing

DECLARATION
I certify that this dissertation does not incorporate, without acknowledgement, any material previously submitted for a degree or diploma in any university and to the best of my knowledge and belief, it does not contain any material previously published or written by another person or myself except where due reference is made in the text. I also hereby give consent for my dissertation, if accepted, to be made available for photocopying and for interlibrary loans, and for the title and abstract to be made available to outside organizations. Signature of Candidate: . . . . . . . . . . . . . . . . . . . . . . . Name of Candidate: . . . . . . . . . . . . . . . . . . . . . . . . . . . Countersigned by: Signature of Supervisor(s)/Advisor(s): . . . . . . . . . . . . . . . . . . . . . Date:../.../.... Name(s) of Supervisor(s)/Advisor(s): . . . . . . . . . . . . . . . . . . . . . . . . . . . Date:../.../....

ABSTRACT
Sudharshi is a company which is an Institute. It was started in 1980. Sudharshi is a developing Institute in Weliveriya Town and had to manage number of transactions per day. They were managed all those works in manual file based approach. Consequently management faced problems like inaccuracy, delay of transactions, unavailability of stock details and etc. The solution collects all data and that data will be used for creating day end reports. As solution the system will generate operational and managerial reports, digitally printed bills for transactions and also facilitate for different level of users with customized functionalities. The system which manages stock and sales will create a centralized controllability. Not only that, this solution supports for tracking orders, transactions, employees, customers and suppliers too. System was developed for standalone environment. This windows based solution was developed using technologies such as Java, My SQL and i-reports mainly. Unified Modeling Language (UML) was used for analysis and design. And also solution was developed under Object Oriented Techniques. Final result of this project a standalone Inventory Control System has been design to fulfill the user and system requirements.

AKNOWLEDGEMENT
I take this opportunity to offer my gratitude to everyone who helped me and encouraged me to complete the project successfully. I would like to thank my client, Sudharshis management and staff who gave me the opportunity to develop this system for their company and for devoting their valuble time to provide me useful information. I am also thankful my supervisor Mr.Kasun Thilina for his guidance and encouragement throughout this project. I am especially thankful to Mr. Prasad Ekanayake for always caring about this project and motivating me to do it well. I am also wish to offer my gratitude to the University Of Colombo School Of Computing for giving me the priceless opportunity to apply the knowledge gained through this program. I dedicate this dissertation to my family for their great support and for being with me supply all the sources needed to complete this project.

TABLE OF CONTENTS
DECLARATION. ii ABSTRACT.iii ACKNOWLEDGEMENTS. iv TABLE OF CONTENTS.v LIST OF FIGURES vi LIST OF TABLES....vi LIST OF ACRONYMS...vii CHAPTER 1 INTRODUCTION... 1 1.1 1.2 1.3 1.4 1.5.1 1.5.2 1.6 1.7 BACKGROUND... 1 MOTIVATION.. 1 EXISTING SYSTEM 2 PROPOSED SYSTEM.. 2 SCOPE...3 OBJECTIVE.. 4 USER REQUIREMENTS.4 SYSTEM REQUREMENTS. 5

1.5 OBJECTIVES AND SCOPE.2

1.8 SRUCTURE OF THE DISSERTATION..6

CHAPTER 2 ANALYSIS...7 2.1 2.2 2.3 2.4 2.5 2.5.1 2.5.2 2.5.3 2.5.4 2.6 DESCRIPTION OF CURRENT SYSTE...7 DISADVANTAGES OF EXISTING SYSTEM................7 STUDY OF SIMILAR SYSTEM...7 REQUIREMENT GATHERIING 8 REQUIREMENT GATHERING TECHNIQUES8 INTERVIEWING..8 OBSERVATION... 8 DOCUMENT ANALYSIS 8 PROTOTYPING 8 REQUIREMENT ANALYSIS.. 8

2.7 2.8 2.9

USECASE DESCRIPTIONS 9 FUNCTIONAL REQUIREMENTS..25 NON-FUNCTIONAL REQUREMENTS. 26

CHAPTER 3- DESIGN... 28 3.1 3.2 3.2.1 3.2.2 INTRODUCTION. 29 ALTERNATIVE SOLUTIONS 29 AVAILABLE ALTERNATES. 29 SELECTING A SOLUTION. 29

3.3 PROCESS MODEL. ..29 3.4 METHODOLOGY FOR THE PROPOSED SYSTEM.........30 3.4.1USECASE DIAGRAM 30 3.4.2 CLASS DIAGRAM.. 30 3.4.3 ENTITY RELATIONSHIP DIAGRAM..31 3.5 DATABASE DESIGN..34

LIST OF FIGURE
Fig 2.1: Use case diagram of Cashier9 Fig 2.2: Use case diagram of Receptionist... 10 Fig2.3 Use case diagram of Store Manager. 11 Fig2.4 Use case diagram of General Manager.. 11 Fig 3.1 Class Diagram.. 31 Fig 3.2 ER Notation-Entity31 Fig 3.3 ER Notation-Weak Entity.32 Fig 3.4 ER Notation-Key attributes32 Fig 3.5 ER Notation-Multi valued attribute... 32 Fig 3.6 ER Notation-Derived attribute.. 32 Fig 3.7 ER Notation-Relationships.33 Fig 3.8 ER diagram 33 Fig 3.9 Database Design34

LIST OF TABLES
Table 2.1: Login Use case.. 11 Table 2.2: View Product Information Use case. 12 Table 2.3: View Transaction Details Use case12 Table 2.4: Add Transaction Details Use case.12 Table 2.5: Edit Transaction Details Use case.........13 Table 2.6: Delete Transaction Details Use case.13 Table 2.7: Produce Day End Report Use case.. 13 Table 2.8: Produce Invoice Use case..14 Table 2.9: Add Customer Details Use case....14 Table 2.10: Delete Customer Details Use case..14 Table 2.11: Edit Customer Details Use case..15 Table 2.12: View Customer Details Use case15 Table 2.13: Make Order Use case.. 15 Table 2.14: Edit Order Details Use case 16 Table 2.15: View Stock Details Use case.. 16 Table 2.16: View Order Use case.. 16 Table 2.17: Cancel Orders Use case...17 Table 2.18: View Supplier Details Use case.. 17 Table 2.19: Add Supplier Details Use case....17 Table 2.20: Edit Supplier Details Use case 18 Table 2.21: Delete Supplier Details Use case 18 Table 2.22: Add New Product Details Use case 18 Table 2.23: Delete Product Details Use case. 19 Table 2.24: Edit Product Details Use case. 19 Table 2.25: Add Stock Details Use case 19 Table 2.26: Edit Stock Details Use case 20 Table 2.27: Delete Stock Details Use case 20 Table 2.28: Produce Stock Details Report Use case...20 Table 2.29: Add Employee Details Use case. 21 Table 2.30: Edit Employee Details Use case. 21 Table 2.31: Delete Employee Details Use case. 21 Table 2.32: View Employee Details Use case... 22

Table 2.33: Add Role Details Use case.22 Table 2.34: View Role Details Use case 22 Table 2.35: Edit Role Details Use case.. 23 Table 2.36: Delete Role Details Use case.. 23 Table 2.37: Produce Order Details Report Use case..23 Table 2.38: Produce Supplier Details Report Use case. 24 Table 2.39: Produce Products Details Report Use case. 24 Table 2.40: Produce Employee Details Report Use case...24

LIST OF ACRONYMS
BIT ER IT OS SQL UML Bachelor of Information Technology Entity Relationship Information Technology Operating System Structured Query Language Unified Modeling Language

CHAPTER 1 INTRODUCTION

CHAPTER 1 INTRODUCTION
1.1 BACKGROUND
2 Sudharshi is a company which is an Institute. It was started in 1980. Sudharshi is a developing Institute in Weliveriya Town and had to manage number of transactions per day. They were managed all those works in manual file based approach. Consequently management faced problems like inaccuracy, delay of transactions, unavailability of stock details and etc. The company is moving towards business market and it has slow down because of the lack of usage of modern IT techniques. This is the company introduction in brief.

2.1 MOTIVATION
Sudharshi already dont have computer system system will Introduce easy inventory control system. With the development of industry, Most of the companies in Sri Lanka are most standardized with computerized systems. Management needs reliable management system to create excitement and to make their business unique, relative to their nearby competitors. Therefore they must interact with reliable and effective management system which facilitates customer data management, supplier data management, product details management. The system will provide the above requirements successfully and it can be developed within lower budget and higher efficiency. The system will provide user-friendly and simple interface to the user. Then it will help them to provide a reliable, quick and effective service to their customers. and suggested Computer

2.2 EXISTING SYSTEM

Sudharshi manage its information & its business process by using hand written files, forms, bills letters & etc. Sudharshi had no any computer based information system, so that its hard to maintain in traditional file based system.

2.3 PROPOSED SYSTEM

Proposed system will provide centralized controllability to the management. Management was able to check transaction details, stock details, customer details, order details & employee details. System provided information only to authorized personals. Every system user had user name & password. After logged in, they were forwarded to their working area. Bills for transactions were digitally printed. Supplier details were only available for General Manager & Store Manger. Product information was available for every user with some restrictions.

2.4 OBJECTIVES AND SCOPE

Major objective of this project was too develop an inventory control system for E-Studio to manage business process in error free way. This system increases the speed and the quality of the company service.

2.4.1

SCOPE Manage Day-To-Day Transactions

Day-To-Day transactions were handled through the system using minimum time. Available discount rates, balance of the transactions were displayed by this system. Produce Invoice An invoice was printed automatically after every transaction. Product details, amount, quantity, total value, discount & warranty periods were available on the invoice. Manage Product Details Product details were available to browse under brands. Manage Customer Details

Customer details were managed in easy way to browse. It can be done under different categories like name or city. Produce Reports Operational, Managerial and Strategic level reports were generated by this solution. Report interfaces were provided with controllers to customize them on users request. 2.4.2 OBJECTIVES Improving Security With the new system, every important detail like transaction details, company details were computerized and protected with passwords. Every user was provided with user name and password which logged them in to their user view. Improving Speed System offered an easy way to browse customer details and product details. Preparing invoice and printing them were automated and save much time than usual. Improving Simplicity Management could monitor the current situation in easy way. Product details were categorized in to an easy manner to browse. Bills were produced automatically after every transaction. Business Profit Quality and the speed increased the income. Overall business profit was increased with the system.

2.5 USER REQUIREMENTS

This system has identified four potential users. Cashier Receptionist Store Manager General Manager

Main requirement of this system was to manage stock and sales in the organization. New system provided following functionalities.

Billing System Transaction Processing System Customer Data Management System Employee Data Management System Supplier Data Management System Product Detail Management System Report Generation System Detailed description will be available under use case descriptions.

2.6 SYSTEM REQUIREMENTS

System should not only fulfill the user requirements but needed to fulfill the system requirements as well. This section will list down the system configurations and requirements. To deploy this system one needs to have windows running machine. Hardware Requirements: System configuration would be more than Pentium IV 2.6GHz or above processing power with 512MB or above RAM Screen resolution is 1366 * 768 Software Requirements: Operating system should be Windows XP, Windows 7 or Vista Microsoft Visual Studio .Net Professional Edition 2008 Database management system tool is Microsoft SQL Management Studio 2005 Crystal Reports should be installed in to each terminal for report generation

2.7 SRUCTURE OF THE DISSERTATION

CHAPTER 2 ANALYSIS This chapter describes the analysis stage of the project. The methodologies used in data gathering and their outcomes are described in this chapter. CHAPTER 3 DESIGN This chapter explains the design stage of the project. The main diagrams which were used for design are also shown in this. The chapter provides the outlines of the main user interfaces with relevant screen shots. CHAPTER 4 IMPLEMENTATION This chapter explains about the implementation of the system. All the major coding is given in this chapter. CHAPTER 5 EVALUATION This chapter describes all the testing methodologies, which were used during this project and all the test cases with the outputs. In this chapter explains problems occurred, lessons learnt during the project. CHAPTER 6 CONCLUTION This chapter contains summery of the project and the difficulties, which were faced during the project.

CHAPTER 2 ANALYSIS

CHAPTER 2 ANALYSIS
2.1 DESCRIPTION OF CURRENT SYSTEM
Sudharshi has been managed their stock and sales in traditional file based system. They manage hand written bills, letters and forms for their day-to-day business process. They maintain their records in files. They do their all transactions in manually. Sudharshi has no computer based information system.

2.2 DISADVANTAGES OF THE EXISTING SYSTEM

Transactions are done manually using calculators Hand written Customer Details, Supplier Details, Employee Details Books Browsing data is not feasible Company letters are hand written by using printed company letter heads

2.3 STUDY OF SIMILAR SYSTEM

Similar systems could provide many designing alternatives for requirements identified in analysis phase. Study of similar system was conducted before start designing phase of this project. The following similar systems were used for gather designing alternates. Those were Sales Management System at Dharani (Pvt.) Limited Inventory, Categories, Suppliers and Customers modules were designed with user friendly manner. The module was available with Add, View and Find functionalities. Also the Report structure and some of the important management reports were identified using the same solution.

2.4 REQUREMENT GATHERING

A requirement gathering is most important and fundamental part of the software development life cycle. In this project, interviewing and discussions were the main source of requirement gathering. Observing similar system was helpful to get an idea about the system.

2.5 REQUREMENT GATHERING TECHNIQUES

Following techniques were practiced when gathering requirements in the project. 2.5.1 Interviewing Interviews are a common technique used in requirement analysis. Through interviewing from the management level staff to the minor staff analyst can get basic idea about the company process.

2.5.2 Observation Observation is the study of users in their natural habitats. By observing users an analyst can identify a current process flow of the company.

2.6 REQUIREMENT ANALYSIS

This project uses use cases as main technique for requirement analysis. The behavior of the system was documented in the use case.

2.7 USE CASE DESCRIPTIONS

Identification of critical users was the first part of identifying requirements. In this system critical users were as below. Cashier Receptionist Store Manager General Manager Use cases (fig 2.1- fig 2.3) are described below.

Fig 2.1 Use case diagram for Cashier

Fig 2.3 Use case diagram for General Manager More details about the use cases could be presented in use case descriptions. They provided a better way to include conditions, and flow of events. Following tables (Table2.1 2.40) includes more details about above use case diagrams. Table 2.1 Login Use case
Use Case Name Actor Overview Registered users can log in to the system Precondition User must register with the system, user should have user name & password Flow of Events Enter user details validate user details, Login to the system Post Condition Invalid user, print error message & rejected login Login Use case All Users

Use Case Name Actor Overview

View Product Information Use case All Users

View detailed product information under categories Precondition User must log in to the system to do this event Flow of Events Select product category for detailed view Post Condition

Table 2.2 View Product Information Use case

Use Case Name Actor Overview View transaction details Precondition User must log in to the system under authorized user type Flow of Events Select transaction and view records Post Condition View Transaction Details Use case Cashier, General Manager

Table 2.3 View Transaction Details Use case

Use Case Name Actor Overview Add new transaction in to the system Precondition User must log in to the system under authorized user type Flow of Events Insert new transaction detail in to the system Post Condition Transaction data will be printed to a invoice New details will be available to the users Add Transaction Details Use case Cashier, General Manager

Table 2.4 Add Transaction Details Use case

Use Case Name Actor Overview Change existing transaction details Edit Transaction Detail Use case Cashier, General Manager

Precondition Record must be selected before edit Flow of Events Change existing data & save them to the data base Post Condition Transaction details will be printed to a invoice New details will be available to other users

Table 2.5 Edit Transaction Details Use case

Use Case Name Actor Overview Delete transaction details from the data base Precondition User must select one or more records to be deleted Flow of Events Select records, select delete command & delete record Post Condition Records will be Removed from the company database Delete Transaction Details Use case General Manager

Table 2.6 Delete Transaction Details Use case

Use Case Name Actor Overview Produce a report for daily transactions Precondition User must log in to t system & select the range of data Flow of Events Select the range of data, create the report Post Condition Produce Day End Report Use case Cashier, General Manager

Table 2.7 Produce Day End Report Use case

Use Case Name Actor Overview Produce invoice for transaction Precondition Produce Invoice Use case Cashier, General manager

User must logged in to the system Flow of Events Enter transaction details, generate the report & print it Post Condition Transaction data will be available to other users

Table 2.8 Produce Invoice Use case

Use Case Name Actor Overview Insert details about new customers Precondition User must logged in to the system under Flow of Events Insert new customer details in to data base & save it Post Condition New customer data will be updated Add Customer Details Use case Receptionist, General Manager

Table 2.9 Add Customer Details Use case

Use Case Name Actor Overview Change existing customer details Precondition Records must be selected before edit Flow of Events Edit existing records & save them to the data base Post Condition Update the data base Delete Customer Details Use case General Manager

Table 2.10 Delete Customer Details Use case

Use Case Name Actor Overview Chang existing customer details Precondition Record must be selected before edit Flow of Events Edit Customer Details Use case Receptionist, General Manager

Edit existing records & save them to the database Post Condition Update the database

Table2.11 Edit Customer Details Use case

Use Case Name Actor Overview View details about customer Precondition User must logged in to the system under authorized username Flow of Events Use one more records to be deleted from database & deleted them Use Case Name Actor Overview User can view the stock Use Case Name Precondition Actor Overview Insert order details in to the system Precondition User must logged in to the system under authorized username Flow of Events Log in to the system, add relevant detail & update database Post Condition Update the database Post Condition Record will be deleted from database Make Order Use case Receptionist, General Manager View Stock Details Use case Receptionist, Store Manager View Customer Details Use case Receptionist, General Manager

Table 2.12 View Customer Details Use case Table 2.13 Make Order Use case

UserCase Name in to the system Use must logged Flow of Events Actor Select stock & view that stock detail Overview

Edit Order Details Use case Receptionist, General Manager

Post Condition request user can change customer orders When customer Print stock details Precondition Select order to make changes Flow of Events Select the record, make changes Post Condition Update the database

2.14 Edit Order Details Use case Table 2.15 View Stock Details Use case
Use Case Name Actor Overview User can view orders Precondition User must logged in to the system under authorized username Flow of Events Select order & view that order Post Condition View Order Use case Receptionist, General Manager

Use Case Name Actor Overview User can cancel orders that customer request Precondition

Cancel Orders Use case Receptionist, General Manager

User should select the record that user want to cancel Flow of Events Select the record, verify the message & cancel record Post Condition Update the database

Table 2.16 View Orders Use case Table 2.17 Cancel Orders Use case

Use Case Name Actor Overview User can view the supplier details Precondition

View Supplier Details Use case Store Manager, General Manager

User must logged in to the system under authorized user type Flow of Events Select the supplier & view that record Post Condition

Table 2.18 View Supplier Details Use case Table 2.19 Add Supplier Details Use case
Use Case Name Actor Overview Change existing supplier details Precondition Select record to make changes Flow of Events Select the record, make changes Post Condition Update the database Edit Supplier Details Use case Store Manager, General Manager

Use Case Name Actor Overview Insert details about new supplier Precondition User must logged in to the system under Flow of Events

Add Supplier Details Use case Store Manager, General Manager

Insert new supplier details in to data base & save it Post Condition New supplier data will be updated

Table 2.20 Edit Supplier Details Use case

Use Case Name Delete Supplier Details Use case

Actor Overview Delete transaction details from the data base Precondition

General Manager

User must select one or more records to be deleted Flow of Events Select records, select delete command & delete record Post Condition Records will be Removed from the company database

Table 2.21 Delete Supplier Details Use case

Use Case Name Actor Overview Insert details about new product Precondition User must logged in to the system under Flow of Events Insert new product details in to data base & save it Post Condition New product data will be updated Add New Product Details Use case Store Manager, General Manager

Table 2.22 Add New Product Details Use case

Use Case Name Actor Overview Delete product details from the data base Precondition User must log in to the system & select one or more records to be deleted Flow of Events Select records, select delete command & delete record Post Condition Records will be Removed from the company database Delete Product Details Use case General Manager

Table 2.23 Delete Product Details Use case

Use Case Name Actor Overview Edit Product Details Use case Store Manager, General Manager

Change existing product details Precondition Select record to make changes Flow of Events Select the record, make changes Post Condition Update the database

Table 2.24 Edit Product Details Use case

Use Case Name Actor Overview Insert details about stock Precondition User must logged in to the system under Flow of Events Insert new stock details in to data base & save it Post Condition New stock data will be updated Add Stock Details Use case Store Manager

Table 2.25 Add Stock Details Use case

Use Case Name Actor Overview Change existing stock details Precondition Select record to make changes Flow of Events Select the record, make changes Post Condition Update the database Edit Stock Details Use case Store Manager

Table 2.26 Edit Stock Details Use case

Use Case Name Actor Overview Delete stock details from the data base Precondition Delete Stock Details Use case Store Manager

User must log in to the system & select one or more records to be deleted Flow of Events Select records, select delete command & delete record Post Condition Records will be Removed from the company database

Table 2.27 Delete Stock Details Use case

Use Case Name Actor Overview Generate reports for stock conditions Precondition User must log in to t system & select the range of data Flow of Events Select a product category & view details Post Condition Print report Produce Stock Details Report Use case Store Manager, General Manager

Table 2.28 Produce Stock Details Report Use case

Use Case Name Actor Overview Insert details about employee Precondition User must logged in to the system under authorized user Flow of Events Insert new employee details in to data base & save it Post Condition New employee data will be updated Add Employee Details Use case General Manager

Table 2.29 Add Employee Details Use case

Use Case Name Actor Overview Change existing employee details Precondition Select record to make changes Flow of Events Edit Employee Details Use case General Manager

Select the record, make changes Post Condition Update the database

Table 2.30 Edit Employee Details Use case

Use Case Name Actor Overview Delete employee details from the data base Precondition User must log in to the system & select one or more records to be deleted Flow of Events Select records, select delete command & delete record Post Condition Records will be Removed from the company database Delete Employee Details Use case General Manager

Table 2.31 Delete Employee Details Use case

Use Case Name Actor Overview User can view the employee details Precondition User must logged in to the system under authorized user type Flow of Events Select the employee & view that record Post Condition View Employee Details Use case General Manager

Table 2.32 View Employee Details Use case

Use Case Name Actor Overview Insert new role to the system Precondition User must logged in to the system under authorized user name Flow of Events Logged in to the system & add new role to the system Post Condition Add Role Details Use case General Manager

Update the system

Table 2.33 Add Role Details Use case

Use Case Name Actor Overview User can view the role details Precondition User must logged in to the system under authorized user type Flow of Events Select the role & view that record Post Condition View Role Details Use case General Manager

Table 2.34 View Role Details Use cas

Use Case Name Actor Overview Change existing role details Precondition Select record to make changes Flow of Events Select the record, make changes Post Condition Update the database Edit Role Details Use case General Manager

Table 2.35 Edit Role Details Use case

Use Case Name Actor Overview Delete role details from the data base Precondition User must select one or more records to be deleted Flow of Events Select records, select delete command & delete record Post Condition Records will be Removed from the company database Delete Role Details Use case General Manager

Table 2.36 Delete Role Details Use case

Use Case Name Actor Overview Generate reports for order details Precondition

Produce Order Details Report Use case General Manager

User must log in to the system & select the range of data Flow of Events Select order or orders & view details Post Condition Print report

Table 2.37 Produce Order Details Report Use case

Use Case Name Actor Overview Generate reports for supplier information Precondition User must log in to the system under authorized username & select the range of data Flow of Events Select a supplier records & view details Post Condition Print report Produce Supplier Details Report Use case General Manager

Table 2.38 Produce Supplier Details Report Use case

Use Case Name Actor Overview Generate reports for product information Precondition User must log in to the system under authorized username & select the range of data Flow of Events Select a product records & view details Post Condition Print report Produce Products Details Report Use case General Manager

Table 2.39 Produce Products Details Report Use case

2.8 FUNCTIONAL REQUIREMENTS

Manage Day-To-Day Transactions Manage Product Details Produce Invoices Maintain Customer Details Maintain Supplier Details Manage Employee Details Produce Reports

2.9 NON-FUNCTIONAL REQUREMENTS

Simple Interfaces Easy to make back ups User Friendliness Easy Configuration Password Changing Ability Security Options Ability to run on many Windows based operating systems

CHAPTER 3 DESIGN

CHAPTER 3 DESIGN
3.1 INTRODUCTION
Designing is an important part of a software development project. Clear and steadfast design is adjustment for successful software project. Main activities carried out in the design stage of the project were to determine detailed requirements, design of information, database, user interface, and hardware and software configuration.

3.2 ALTERNATIVE SOLUTIONS

AVAILABLE ALTERNATES There are two different alternatives available for above discussed problems. Those alternatives were, A Web Based System A Stand-Alone System

3.3 PROCESS MODEL

A software process model is an abstract representation of a process. It represents a description of a process from some particular perspective. [WWW2] There are many process models; 1. Waterfall Model 2. Prototype Model 3. Spiral Model 4. Incremental Development Model 5. Object Analysis and Design Model

3.4 METHODOLOGY FOR THE PROPOSED SYSTEM

Object Oriented Analysis and Design is the process of planning a system of interacting objects for the purpose of solving a software problem. It is one approach to software design [WWW3] The following object models were used for the designing process of the system. Use case diagram Class diagram 3.4.1 USE CASE DIAGRAM Use case diagrams were briefly explained above chapter two. 3.4.2 CLASS DIAGRAM

Class diagrams are most essential part of Object Oriented Analysis and Design. Class Diagram was collection of classes and interfaces, along with the collection and relationships among classes and interfaces. Following class diagram (fig 3.1) was created before implementing the solution.

Fig 3.1Class Diagram

Fig 3.8 ER diagram