Embed Size (px)
Citation preview
CHAPTER I
INTRODUCTION
1.1 Background
In the middle of evoria business that is increasingly increases in business
to increase earnings as well as maximizing customer satisfaction that is
increasingly day increasingly increases. Data and management business
becomes very vital to fulfill above clauses. Accurate data handling and
management business matching with rules absolute order hardly in requiring
create of the business men. Green Light Distro is one of peripatetic business in
the field of effort for clothes sale, length pants, trunks, boxer, shirt and various
accessories supporting to increase impressing in the fact this company still are
using way which manual to do the business transaction. People still must
come to shop and must choose and does completely manual. In payment also
the side of company still using manual method. This hardly disturbs comfort
in having business, in the case of data handling, processed business that is
enough eating time which enough eating time.
From problems to management Green Light Distro to have an eye to
changes manual method to become online method, so that customer is not
necessarily come and does direct order. System which this is new will be
design with Unified Modeling Language (UML) diagram explaining business
process from Green Light Distro. Because with this diagram can assist in the
case of implementation system Green Light Distro. This implementation
applies ASPNET. Herewith hence will get system optimal business and
gratifies customers.
1
1.2 Problem Formulation
In this project would be handled several problem such as:
1. How analyzing study case system process in Green Light Distro?
2. How to implementation of process application Green Light Distro in the
form of ASP.NET application?
3. What specification of hardware and software required for this application?
4. How to make ordering process of clothes runs easily and quickly?
5. How to reduce mistake at the time of entering data?
1.3 Purpose
Purposes of making final project paper are:
1. To identify system process in Green Light Distro by using case study.
2. To know implementation process application Green Light Distro.
3. Gives knowledge to minimum specification people of hardware and
software which must be applied.
4. To easier data process swiftly.
5. To reduce mistake at the time of entering data.
1.4 Benefit
Benefits of making final project paper are:
1. Identify system process in Green Light Distro by using case study.
2. Give implementation process application Green Light Distro.
3. Minimum specification of hardware and software this must be applied.
2
4. Give easier data process swiftly.
5. Give reduce mistake at the time of entering data.
1.5 Problem Boundaries
In creational of this application we have some problem boundaries so its
system can be implemented correctly. These problem boundaries can also
minimize the creational of application. The problem boundaries of application
creational are:
1. In the section we just discuss design with Unified Modeling Language
(UML) diagram that consist use case, class, sequence, activity diagram.
2. These shop still a medium class, and don’t serve the services.
3. Admin is a staff that serves the client register and order. But not all staffs
can be an Admin, it’s only for staff who had given rights to be an Admin
and his/her data have been saved/exist in database.
4. For payment of member consisted of 3 choice that is coming direct to
shop, transfer of account, or by using credit card.
1.6 System Writing
In this report the systematic way that we use, are:
CHAPTER I INTRODUCTION
This chapter include about background, problem formulation, purpose,
benefits, problem boundaries, writing method, writing systematic, and
schedule to make this project.
CHAPTER II ANALYSIS
This chapter include about explain the existing system and envisioned system.
CHAPTER III DESIGN
This chapter include about explain the UML diagram in this application.
3
CHAPTER IV IMPLEMENTATION AND TESTING
This chapter consists of specific of hardware and software, operating system,
GUI, tools development, and test plan.
CHAPTER V CLOSING
This chapter include about conclusions and suggestion.
BIBLIOGRAPHY
Include about reference
1.7 Time Schedule
No. Steps
May - June 2009
1 8
1
5
2
2
2
9 5
1
2
1
9
2
6 30
1System requirement
and feasibility
2Software
requirement 3 General design 4 Detailed design 5 Code 6 Test 7 Implementation
8Operation and
maintenance
9Make a
documentation Table 1.1 Time Schedule
4
CHAPTER II
ANALYSIS
4.1 Existing System
Green Light Distro is store providing assorted of clothes, pants and
accessory. Green Light Distro can service customer in the form of order and
direct transaction. Supply product from supplier direct something in marketing
there is also in produce of returning. So, in supply product, product which
supply in the form of raw and product.
Product becomes of vital importance in this business because product is
main characterization in process of this business. Product in this case is
consisted of assorted. Product record contains about Product ID, Merk, Price,
Color, Size, and Stock.
Customer can do order of coming direct to shop. Customer can choose
product provided by Green Light Distro. Then cashier will note transaction of
purchasing done by customer to cover purchase date, OrderID, type product,
name of buyer, etc. This record-keeping applied for accurate of transaction
data in system business which will be applied by Green Light Distro.
4.2 Envisioned System
Green Light Distro difficult to arranges a real data many in manuals
which still using paper. Besides also in handling of number of member which
is increasing day by day. On that account, management Green Light Distro
wishes to change former method by using computerization method. Method
which more clearer and directional in the case of handling of report and data
which more accurate.
5
At, times based on the location of the incident, the corporate office of the
company send the details about the feedback to various regional offices. After
completing the investigation on the feedback, the investigation details are sent
to the corporate office.
In this system will contain application which can be applied by
management and customer. Application consisted of some menus:
1. This system will provide system logins for administrator as well as
customer becoming member from Green Light Distro. Interface also is
reserved for customer becoming member and also which is not.
2. This also will provide details from all product provided by Green Light
Distro management. Detail product would in accompanying with
description from product and all relating to product.
3. For customer who has not had member, can become member from
Green Light Distro easily and free.
Based on above explanations of all menu and facility in application,
reserved for all customer member and also non member. There are some menu
like Home, product, order, profile, gallery, and contact us. Home contains
welcome screen from Green Light Distro Online. Profile contains about
description from Green Light Distro Online. In this application also member
order can be direct into system by using order system which has been given to
management with all easy of order and facilities complete to facilitate
customer in ordering product.
6
CHAPTER III
DESIGN
3.1Unified Modeling Language
In order to develop the software system for Green Light Distro Online,
need to analyze the existing system and create a design for the envisioned
system, using UML. It is the following UML diagrams:
1. Use Case Diagram.
Depict a number of external actors and its relationship to Use Case given
by system. Use Case is depicted only seen from outside by actor (situation
of system environment seen by user) and how the function in system.
2. Description Use Case.
3. Analysis Class.
4. Class Diagram.
A class diagram represents a set of classes, interfaces, and their
relationships.
5. Sequence Diagram.
Sequence diagrams represent an interaction between objects in the form of
messages ordered in a sequence by time.
6. Topology Graphical User Interface.
7. Design GUI.
8. Test Plan.
7
3.1.1Use Case Diagram
Picture 3.1 Use Case Diagram
3.1.2Use Case Description
Registration
Actor: Member.
Pre Condition: Member has not registered.
Post Condition: Member has registered.
No User System
1 Actor open form registration.2. Show form registration.
3 Actor enters data to form registration.
8
4. Check the data.
a. If the data is not valid, system can display alert for Actor.
b. If the data is not complete, system can display alert for Actor.
c. If the data is valid, data save in the database. Actor can login.
5. Show the content from member menu.
6 Actor Select choice in menu.7. Show the content from member
menu.Table 3.1 Registration Description
Login
Actor: Member, Employee, Admin.
Pre Condition: Actor is outside from System.
Post Condition: Actor is inside from System.
Purpose: Actor can manage the data, like update, insert, search, view,
and delete.
No User System
1 Actor open form login.2. Show form login.
3 Actor enters name and password to form login.4. Check name and password.
a. If name and password true, show menu each actors.
b. If name and password false, system can display alert for Actor.
c. If name and password true, actor can login.
5. Show the content from each menu actor.
6 Actor Select choice in menu.
9
7. Show the content from each menu.
Table 3.2 Login description
Search
Actor: Member
Pre Condition: Product has not been show.
Post Condition: Product has been showing.
Purpose: In this form Actor can searching data of product.
No User System1. Display each product sold with
description.2. Display text filed search and the button.
3 Actor types name of product which will be searched.
4. When button in clicked and then product will be searched.
5. If product is found, product will be displayed.
6. Otherwise is found hence will be presented that product is not available.
Table 3.3 Search description
Order
Actor: Member
Pre Condition: Actor has not ordered product.
Post Condition: Actor has ordered product.
Purpose: Actor gets the product.
No
User System
1 Actor open form login.2. Show form login.
3 Actor enters name and password to form login.4. Check name and password.
a. If name and password true, show member menu.
10
b. If name and password false, system can display alert for Actor.
5 Actors enter name and password again.6. Show the content from order
menu.7 Actor Select choice in order menu.
8. Show the content from order menu.
9 Actor select choice in order menu.
a. If actors want adding data of order product, select order menu.
10. Show that selected by Actor
Table 3.4 Order description
3.1.3Analysis Class
Class CandidateKind of Class
Attribute Method
Admin Entity username, password, name -
Login Admin Boundary username, password display()
validate()
Admin Page Interface - display()
Green Light Distro Online web
Boundary - display()
Product Entity ProductID, Merk, Size, Material, Color, Price, Stock
-
viewProductForm Boundary ProductID, Merk, Size, Material, Color, Price
viewProductData()
Member Entity Username, Name, Password, Address, City, Zip, Phone, Email
-
11
Member Boundary Username, Name, Password, Address, City, Zip, Phone, Email
updateData ()
searchData()
insertData()
deleteData()
viewData()
Login Member Boundary Username, Password display()
validate()
Registration Form Boundary Username, Name, Password, Address, City, Zip, Phone, Email
inputRegistration()
Member Page Boundary - display()
Order Entity OrderID, Date, UserName, Name, ProductID, Merk, Price, Qty, Total
-
InputOrderForm Boundary OrderID, UserName, Name, ProductID, Merk, Price, Qty, Total
insertOrderData()
OrderDetails Entity ID, CustID, Nama, Jalan, Kodepos, Kota, Negara, NoKartu
-
InputOrderDetails Boundary IDOrderDetails, OrderID, ProductID, Merk, Price, QTY, SubTotal, Status
insertOrderDetails ()
Table 3.5 Analysis Class
12
3.1.4Class Diagram
Picture 3.2 Class diagram
3.1.5Sequence Diagram
Login Member
Picture 3.3 Sequence login members
13
Login Admin
Picture 3.4 Sequence login admin
Registration
Picture 3.5 Sequence Registration
14
Order
Picture 3.6 Sequence order
15
3.1.6Activity Diagram
Picture 3.7 Activity diagram
16
3.1.8Topology Graphical User Interface
HOME
ORDER DETAILS
CONTACT USPROFILEREGISTRASILOGINGALLERY
ORDERGALLERY PRODUCTINFOHOME
MEMBER
Picture 3.8 Topology Graphical User Interface for customers
HOME
MANAGE DATA
ORDERCUSTOMERSPRODUCT
MANAGE DATA MANAGE DATA
Picture 3.9 Topology Graphical User Interface for admin
3.1.9Design GUI
Home Customer
Picture 3.10 Home Customer
17
Login
Picture 3.11 Login
Registration Form
Picture 3.12 Register Form
18
Home Member
Picture 3.13 Home Member
Order Form
Picture 3.14 Order Form
19
Home Admin
Picture 3.15 Home Admin
3.1.10Test Plan
No Cases Condition Expected Result Actual Result
1 Login If the text field of username and
password is blank.
Display alert “*” -
If the username is blank.
Display alert “*” -
If the password is blank.
Display alert “*” -
Username and password is doesn’t
match.
Alert “Invalid Login!!”
-
20
2 Login Admin If the text field of username and
password is blank.
Display alert “*” -
If the username is blank.
Display alert “*” -
If the password is blank.
Display alert “*” -
Username and password is doesn’t
match.
Alert “Invalid Login!!”
-
3 View Product for customer
Customer login or no can see the details of
product.
System will display the details
of products.
-
4 Choose Product Customers see the details product.
Show details product and add to
the basket, but must be login
before.
-
5 Edit Product Input code of Product, if the code doesn’t
match.
The data not is found.
-
Input code of Product, if the code is match.
The data will be found.
-
6 Delete Product Choose the data product which want to
delete.
Data Product will be deleting.
-
7 Insert order of product
Customers have been login and add the
product which wants to purchase to the
basket.
System will display form order
and saving the data.
-
8 View Order by customer
Customer can see the order that have been
submit.
The detail of order is display.
-
21
9 Check Order Admin has been login and check the order of
customer,
0= new order,
1= has delivery.
If form order has content, the
products can be delivering.
The payment is transfer.
-
10 Insert data customer
Customer not be a member, and input
data customer.
Customers have been a member.
-
Table 3.5 Test plane
3.2 Database
At part of this studies tables which in requires by system in executing
procedure implemented, in this case is including usage of name used for every
field and data type which in requires by the field. Besides every tables must in
determining which field which in using as primary key (be field which may not
have twin data). Tables which in using is as follows:
1. Table Admin
It is functioning tables to check admin.
2. Table Product
Store the data product.
3. Table Member
It is functioning tables to save data to containing login from every
inscribed user. Member here is someone which allowed applying this
application. Which to be member must do registration beforehand.
4. Table Order
Store the data order from customers.
5. Table Order Details
Store the data order from product details.
22
3.3 Entity-Relationship (ER-Diagram)
Entity-Relationship is a scheme model of data base that is often is applied.
Entity can be interpreted as entity while Relationship as relations, both this
components in description farther through an attribute or properties. Entity is
individual representing something tangible (existence), and distinguishable from
something else. Relationship shows existence of the relation of among a number
of different entities. This is E-R Diagrams from scheme of Green Light Distro
bases on WEB:
23
Product
ID_Product Size
Merk Price
Color
MaterialStock
Status
Customer
FullName
Address
Cust_ID
Phone
Password
City
Zip
UserNameexpTahun
expBulan NoCC
TypeCCNameInCC
TypePembayaranOrderID
ID
Payment
Order DetailSubTotal
QTY
Price
Merk
ProductIDIDOrderDetails IDOrder
OrderProduct
ID
Total
NegaraKota
KodePos
Jalan
Nama
CustID
M 1
m
m
Can1 has 1
has
1
has1
Picture 3.16 E-R Diagrams
24
CHAPTER IV
IMPLEMENTATION AND TESTING
4.1 Software and Hardware Suggestion
4.1.1Database Server Software Analysis and Suggestion
Compared with Microsoft SQL Server 2000, Microsoft SQL Server
2005 is the better choice. With the new features, higher security, and
patched bugs.
Item Microsoft SQL Server 2005 Microsoft SQL Server 2000
Point Reason Point Reason
Security 70 More security is
repaired from the
previous version.
40 Some bugs which is
un-patched.
Portable 70 Can run on new
Windows based OS.
50 Have some trouble
with the new Windows
based OS.
Support 100% Today Microsoft has
full support on MS
SQL Server 2005.
10% Microsoft has stop
support for this
software.
Table 4.1 Database server software analysis and suggestion
4.1.2Operating System Analysis and Suggestion
25
Operating system Windows has been a popular operating system
used around the world which has huge hardware compatibility rather
than operating system Linux, with the better performance than Linux and
minimum hardware requirement.
Item Windows Linux
Security 70 % 89 %
Performance 88 % 50 %
Hardware compatibilities 80 % 40 %
Memory management 80 % 40 %
Table 4.2 Operating system analysis and suggestion
4.1.3Developer Utility Analysis and Suggestion
While developing this application, developer uses any software:
1. Microsoft SQL Server 2000
This database server is used both on development phase and
implementation phase. By this application, developer can simulate
database on development phase and then implement it after
development is completed.
The benefit is various examples of SQL Server in one machines,
border on operation of SQL Server 7.0, including management of
SQL Server 7.0 and SQL Server 2000 of the same format SQL
Server Enterprise Manager, input and data output at xml, integrated
mechanically OLAP, and world scale champion.
2. JUDE Community
26
In this project, writer used JUDE to make UML diagrams. JUDE is
one of software diagram modeling, rich of features and the free of
charge.
Picture 4.1 JUDE Community
3. Microsoft Visual Studio 2005
Visual of Studio .NET provides many new feature, the following is:
a. One inwrought programming models for all languages .NET, for
Windows and also the application of web.
b. Expansion of drag-and-drop for server by using Server Exporer.
c. Dynamic help.
d. Big customization model and expects stripper for IDE.
e. Supports XML.
f. Service web with integration of application between platforms
that is far easier.
4. Internet Explorer 8.0
27
For implementation in this project, because IE 8.0 or higher can
maintain stability in this application.
5. JAVA 6 Standard Edition
In this project, java is required by make class diagrams in Microsoft
Visual Studio 2005.
Picture 4.2 JAVA 6 Standard Edition
6. IIS
The IIS (Internet Information Server) is a scalable network utility
tool, which is used to publish Web sites and other Web content within
an intranet or the Internet. The server is strongly integrated with the
Windows environment, which makes it a widely used Web server. It
provides an ASP (Active Server Pages) platform for developing Web
sites and FTP (File Transfer Protocol) capabilities for publishing
Web sites.
It is available with Windows NT/2000/2002 operating systems. For
setting IIS is as follows:
a. Start Administrative Tools Internet Information Services,
28
Picture 4.3 IIS configuration 1
b. Showing Internet Information Services configuration,
Picture 4.4 IIS configuration 2
c. Right click in Default Web Site choose Properties
29
Picture 4.5 IIS configuration 3
d. Then, choose ASP.NET tab, in ASP.NET version select the last
version.
Picture 4.6 IIS configuration 4
4.1.4Hardware Specification Analysis and Suggestion
30
In this Final Project, writer using database specification as list below
including reasons. On this project, the application doesn’t needs web
server technology, so writer doesn’t use it.
No. HardwareRecommended
Specification
Minimum
specificationUnit
1 CPU Intel Core 2 Duo
Processor or higher
Intel Pentium 41
2 RAM 1GB 512MB 13 Hard Disk 50GB 20GB
1
4 Video 800 x 1280, 256 colors
Recommended: High
Color 32-bit
800 x 600, 128
colors
Recommended:
High Color 16-bit
1
5 Mouse Microsoft Mouse or
compatible pointing
device
-
1
Table 4.3 Hardware specification analysis and suggestion
4.2 Graphical User Interface
4.2.1Design GUI
Home
31
Picture 4.7 Home
Login
Picture 4.8 Login
Profile
Picture 4.9 Profile
Contact Us
Picture 4.10 Contact Us
Registration Form
32
Picture 4.11 Register Form
Gallery
Picture 4.12 Gallery
Check Out
Picture 4.13 Check Out
Choose Product
Picture 4.14 Choose Product
Member Detail
33
Picture 4.15 Member Detail
Home Member
Picture 4.16 Home Member
Order Form
Picture 4.17 Order Form
4.3 Experience Using Development Tools and Characteristic Tools
Writer uses various software to support development process. To design
user interface rapidly, writer prefer to use Microsoft Visual Studio 2005 rather
34
than the other because Microsoft Visual Studio 2005 support developing
various layout and for recent Microsoft Visual Studio 2005 version, it support
layout or free layout.
Writer has been using Microsoft Visual Studio 2005 for many years on
Windows to design some graphic vector for many purposes including web
design graphic layout. Microsoft Visual Studio 2005 is simple, flexible and
easy to use vector drawing.
MS SQL Server 2000 has better compatibility for Windows XP, because of
writer developing the application on Windows XP so writer use MS SQL
Server 2000. It is difficult to connect SQL Server 2000 with ODBC on
Windows XP.
4.4 Testing Result
No Function Testing Expected output
Existing output
Conclusion
1 Login() The text field is empty
Message thrown “Username dan Password tidak boleh kosong”
Message thrown
VALID
2 Login() Username empty
Message thrown “Username tidak boleh kosong”
Message thrown
VALID
3 Login() Password empty
Message thrown “Password tidak boleh
Message thrown
VALID
35
kosong”
4 Login() Insert wrong username and/or password
Message thrown “Username atau Password salah”
Message thrown
VALID
5 Insert() Input is incomplete
Message thrown “Gagal submit...”
Message thrown
VALID
6 Update() User input non existing data
Message thrown “Data tidak ditemukan...”
Message thrown
VALID
7 Delete() User input non existing data
Message thrown “Gagal menghapus, data tidak ditemukan...”
Message thrown
VALID
8 Search() User input non existing data
Message thrown “Data tidak ditemukan...”
Message thrown
VALID
Table 4.4 Testing Results
36
CHAPTER V
CLOSING
5.1 Conclusion
From the above explanation we can get conclusion is:
1. System design from Green Light Distro consists of some diagram like a
use case diagram, class diagram, sequence diagram, and activity diagram.
2. To make and business system design Green Light Distro by using
diagrams UML
3. With using UML design, programmer easier to make implementation of
their program
4. Identifies system process in Green Light Distro by using case study.
5. Knows implementation process application in Green Light Distro.
6. Minimum specification of hardware and software which must be applied.
7. Easier waters down data process swiftly.
8. Receives and presents report structurally good, quickly and more accurate.
5.2 Suggestion
The suggestions to this project are:
1. In making UML diagrams is very difficult and many in makings the
diagram. So, programmer has to be more check in making and makes
process business.
2. Advisable apply special software to make UML diagrams to facilitate in
diagrams making, between it is Jude, Visio and other.
3. In usage of database user must get of best of program performance which
has been made.
37
Bibliography
1) ______________.2007. Developing Enterprise Wide Applications – Part II
(.NET) -1: Student Guide. NIIT
2) ______________.2007. Developing Enterprise Wide Applications – Part II
(.NET) -1: Student Guide. NIIT
3) ______________.2007. Understanding Business Process and SDLC:
Developing Applications using XML Technologies. NIIT
4) Kusumo, Ario Suryo. ASP.NET 2.0 dengan VB 2005. Elex Media
Komputindo.Jakarta.2007
38
