PC PARTS is a well known computer items shop which is at horana. They are selling desktop computers, notebooks and hardware items. From the time they have opened their shop they have been using a invoice paying publication for customer obligations and a printed out newspaper for computer items details. Therefore the owners of the shop have a requirement of something to do those above functions easily.
. ::Background::.
As mentioned previously (inside the analysis) Computer PARTS shop offers a regular level system which has gone out of your time. Inside this system the shop needs many fixed items and so it would have an impact on to the revenue of the shop. Managing books will limit the space. The management of the stock is not been doing in an effective manner. As well as the customer details papers are not satisfying the customer. So this waste the time of both customer & personnel.
My software is an improved instance for the prevailing above system.
It will stop those negatives of the current system. By utilizing a computer structured system all those extra outcomes for many fixed items will be cut off. Customer details user interface will save the time of the clients & personnel also by giving a better information to the clients about the computer items.
OBJECTIVES
. ::Main objectives::.
Managing the sales of the shop
Managing the stock of the shop
Descriptive & effective information of the reselling what to the customers
Ensuring the security & privateness of the shop's system
Disadvantages of prevailing softwares in the market
There are numerous kinds of software pests found in common softwares & computer shop softwares. Some of them are,
Conceptual errors(code is syntactically right, however the programmer or artist intendeds it to do something else)
Co-programming bugs
Team working bugs
Logic bugs
Infinite loops (Ref :)
Off by one problem, counting one too many or too few when looping
Arithmetic bugs
Division by zero
Arithmetic overflow
Loss of arithmetic detail anticipated to rounding or numerically unstable algorithms
Syntax bugs
Resource bugs
Using uninitialized variables
Access violations
(Ref :)
Details of selling items aren't been viewed within a screen(descriptively with pictures)
How to avoid those issues with this specific system
The software which I am producing will not at all be having co-programming bugs or team working bugs as the complete software is likely to be designed and developed only by my personal.
As c#, the language which I'm developing my software offers a clever sense and a great attention through it's scope logic insects, syntax bugs, reference bugs will not affect to the machine.
And also as my system will receive a customer details interface the personnel crew can make their work easier.
METHODOLOGY
. ::Main System Flow::.
LOGIN
(Loading event)
USER CHECK
ADMINISTRATOR STAFF
MAIN MENU MAIN MENU(SOME FUNCTIONS
ARE LOCKED)
RETURNED
ITEMS SUB Consumer TRANSACTIONS CUSTOMER MAIN STOK'S
DETAILS CHECK DETAILS SUB MENU
MAIN
STOCK PAYMENTS RETURNS
MAIN MENU
EXIT TO DESKTOP SCREEN
. ::Software development methodology to be used::.
Integration and system testing
Operation and maintenance
***Category diagram of the software***
PC PARTS SHOP
STAFF MEMBER
User name
Password
Access substock
View cus:details
CUSTOMER
Name
OWNER
User name
Password
Access mainstock
Access returns
Access substock
View custo:details
COMPUTER
ITEM
Code no:
Quantity
PAYMENT
Amount
CASH
Cash tendered
CHECK
Name
Bank id
Authorized
LAPTOP
DESKTOP
COMPUTER
HARDWARE
ITEM
***Use circumstance diagram of the software***
Managing the system of your computer shop
Administrator
Customer
Staff
member
Administrator
Customer
Staff
member
. ::Implementation of the machine::.
Administrators have to be given a wide explanation about the system
One of the administrators and 1 or 2 2 staff members have to be trained for approximately a week
Administrators need to be informed about what they can do & can't inside the software
Staff members also should be educated what they can & can't do
. ::Screening & bug repairing::.
White box trials and black pack assessment should be done
Minimumly 5 data items need to be came into to a data base
Testing of pictures copied to a data bottom part & it's working have to be done in a careful manner
By going through a parallel amount of old & new systems hidden pests can be identified
. ::Resources necessary for the development::.
Required Resources
Hardware(minimum) Software
*1GB Ram *MS OFFICE
*128 MB VGA *MS VISUAL
STUDIO
*House windows 2000,
Windows XP or
Windows NT
. ::Project group work plan::.
March
April
May
June
WEEK
1 2 3 4
1 2 3 4
1 2 3 4
1 2 3 4
Requirements gathering
Requirements definition
Designing
Writing the coding
Unit testing
System testing
CONCLUSION
There are several obstacles which has to be faced while growing this software. Writing codes for the new, additional functions need to be found & discovered hardly. And merging the systems of the machine should be done with a great health care. Also completing the program before the inactive line is a concern, training the users who haven't used your personal computer centered system is a hard to be confronted.
Basically to resolve those above challenges the software needs to be developed with a great health care and commitment through out the expanding period
