Chapter 1 debut
In the debut subdivision of the writers study he will province the chief aims of the undertaking, which has been conducted by me the writer.
1.1 jobs to be solved
Mr Patel has merely late established his intoxicant wholesales concern, as the concern has late been established they are seeking to happen a method to pull more clients to make the concern with every bit good as to be known in the market.
So to work out the company ‘s job I have decided to utilize E-commerce to plan and construct the company a web page, which will hold a log in subdivision for his clients and let them to put orders for cargos on-line. There will be a database linked to the web page which holds information of his intoxicant stock lists, client information, purchase orders, purchase position and bills, for Patel ‘s Cash & A ; Carry Ltd and the clients.
1.2 undertaking donees
Mr Patel & A ; Patel ‘s Wholesalers ( client ) – This will profit my client when he gets new stock in because he can advise his clients. Besides he can merely merely upload the new list onto his web page via his database package. This allows his clients to hold entree to the members log in subdivision ; besides he can demo the list and monetary values of his stock on the non members subdivision. This information will profit the company to pull new clients to the concern.
Mr Patel ‘s Clients ( consumers ) – The company web page will profit clients as they will be given an option to travel online to put their order with Patel ‘s Cash & A ; Carry Ltd. Besides there can look at new stock and offers. Therefore this will give them an chance to reach the company straight ; the clients will be able to see their recent and outstanding purchases, besides leting clients to hold entree to other assorted good modules.
The Author ( Jayraj Sangha ) – This gives me the chance to profit and larn new accomplishments during this undertaking, every bit good as doing usage of my current accomplishments to help me to finish the undertaking, in add-on I will larn how to intercede with the clients and larn undertaking direction accomplishments.
1.3 undertaking aims
Primary Objective
The aim for this undertaking will be making a database that will be integrated within a web site for Patel ‘s Cash & A ; Carry Ltd. The web page will hold an online login system for all the clients and decision makers, where they can hold entree to several installations runing from stock list, particular offers, doing payments either online or on bringing, every bit good as reaching the company.
All the information inputs and end products will be managed by the integrated database system, which will incorporate client information, general stock, recent purchases placed. Whenever an update is applied to the web site or the database these alterations will be in consequence instantly leting up to day of the month information to be displayed on both the web site and the database system.
Secondary aims
- Meeting up with Patel ‘s Cash & A ; Carry Ltd to obtain demands the client wishes to see from the undertaking result.
- Making and develop the web site and database system paradigm.
- Present paradigm to Mr Patel to acquire input and feedback with the undertaking.
- Better the paradigm to develop the concluding version of a to the full functional web page meeting all the demands for the company.
1.1 work program
The undertaking will get down off by run intoing up with the client and discoursing the demands he wishes to see implemented with the terminal merchandise, so travel onto research of web page development layout and design, and so followed up with package proving of the paradigm so will acquire feedback and input from my client.
Once the paradigm has been assessed by the client I will so follow up from the client ‘s feedback and input, so correct any errors by redesigning and reconstructing the concluding system from the footing of the paradigm layout. The concluding web page will so be up and running for Mr Patel.
1.2 project study construction
In this subdivision of the study the writer will be saying the layout of the construction of his undertaking study, how it will look and how it will be ladled consequently.
Chapter 2 end product sum-up
This subdivision will incorporate the description and information of the undertaking outputs, which will be used by the client Prakash Patel. Chapter 2 will include the overview of the description, the nature of the end product and who the terminal user will be and how they plan to utilize it.
Chapter 3 literature reappraisal
This subdivision contains the information incorporating all the books that the writer read, these books helped him transport out my undertaking successfully. In add-on these books he read will give anyone reading my study a small spot of cognition of the techniques I used during the class of the undertaking.
Chapter 4 method
This subdivision contains the method he used to help me in developing my undertaking. It will discourse into deepness the work the writer did during the assorted stages of the undertaking, runing from demands garnering up to the rating phase.
Chapter 5 consequences
This subdivision will show all the consequences the writer obtained throughout the development of the undertaking. This will include the consequences from requirement assemblage. Systems analysis, design, execution, proving and rating.
Chapter 6 decision and treatment
This subdivision revolves around on sum uping undertaking consequences by revising the undertakings aims and ends. In add-on it provides the audience with an penetration into what he may or hold gained during the class of the undertaking. Besides improvements that can be made to the system will be briefly discussed.
Chapter 8 glossary
This chapter focuses on specifying specializer footings.
Chapter 9 mentions
This subdivision presents to the audience the list of mentions used in the undertaking development and this study.
Chapter 2 end product sum-up
2.1 end product demands certification
My first end product affecting my undertaking revolves around the system certification ; the system certification consists of the specifications and designs based on the system I will be constructing for the client.
The description for the system certification is where the system undertaking certification will dwell of all the critical and necessary information, this will help the writer in constructing the system for the client Prakash Patel. The certification will include these critical phases which are system demands specification, design and proving the system. All these can be found in the appendix.
The system demands specification fundamentally focal points on all the demands given to me by my client utilizing interview and experimental techniques for informations assemblage, all the demands and information I obtain will so be documented in the usage instance diagrams, usage instance specifications, functional and non functional demands. Can be found in appendix C.
2.2 end product specification certification
My secondary end product is based on the specification papers ; this papers fundamentally involves me making my usage instance diagrams, usage instance specifications and functional and non functional tabular arraies, with the assistance of the demands certification information that I collected from my interview with Prakash Patel.
How the demands certification will assist me construct the all my usage instance diagrams and functional and non functional tabular arraies is, I will carefully dissect and pull out the of import characteristics from the demands Prakash has stated to me in the interview and so use them to the diagrams and other specification theoretical account. Can be found in appendix C
2.3 end product Design certification
My 3rd end product is based on me really pulling up and making designs on how the system will look like aesthetically and functionality wise, this will subsequently on assist me plan the paradigm of the system and subsequently on assistance me constructing the concluding system.
The design phase will be based on assorted types of diagrams which will help me in planing the system. This will dwell of assorted properties such as category, province chart and sequence diagrams along with entity relationship diagram, relational database scheme ( DBS ) . In add-on assorted screenshots of GUI ‘s will be included in the design phase. Can be found in appendix E2.4 end product proving certification
My 4th end product will be based on the testing of my systems traveling through what does work and what does non work in the functionality section, this will assist me better on the system so when I build the concluding system all the characteristics that were non working in the paradigm system will later on be working and rectified in the concluding system.
The testing phase involves in documented trials which will be conducted to do certain the system meets wholly coveted demands. Can be found in appendix D
How I intend to utilize the undertaking certifications, is it will be able to assist me supply penetration in the whole of my undertaking and the system, if any job may happen it will be easy identified with the aid of the certification. In add-on the papers will assist me better the system in the close hereafter, which will profit Prakash Patel.
Chapter 3 literature reappraisal
3.1 Introduction
This chapter will discourse how I used assorted literature stuffs that aided me in my design phases for my system runing from:
- making my usage instance diagrams
- Use instance specifications
- Sequence diagrams
- State chart diagrams
- Class diagrams
- Using Dreamweaver to make the web site
- Using my SQL
By utilizing these literature stuffs this helped me into making my mark and end of making the web site and engagement system for my client Prakash Patel and his concern. In add-on this literature reappraisal fundamentally summarises for me, Prakash Patel, Chris Smart and the moderators what stuffs I used to make the system and assist them derive an apprehension of the system and any proficient slang.
3.2 understanding Electronic Commerce, David Kosiur, 1997
For some clip now, big concern endeavor has used electronic commercialism to carry on business-to-business minutess. The cyberspace is already altering the manner many companies conduct their concern. ( David Kosiur, 1997, P.1 )
Many sellers are looking to utilize the cyberspace as another gross revenues channel. This gross revenues channel can mime that of the shops and promenades that consumers are used to, what have been called practical promenades. ( David Kosiur, 1997, P.117 )
Tiing databases to online catalogues, AMP has successfully met the demands of many of its clients by exchanging to a merchandise catalogue that ‘s accessible via the web. By keeping the catalogue on line, AMP connect serves as a cardinal depository of utile information that remains at the clients fingertips, 24 hours a twenty-four hours, 7 yearss a hebdomad. ( David Kosiur, 1997, P.181 )
Not merely is the database used to dynamically bring forth the HTML pages that users see as portion of the online catalogue, but it besides serves as printing smaller, printed catalogues. The database supplies the web informations. ( David Kosiur, 1997, P.182 )
3.3 An debut to Database systems, C.J. Date, 1995
A database system is fundamentally a computerized record maintaining system ; that is, it is a computerized system whose overall intent is to keep information and to do that information available on demand. ( C.J. Date, 1995, P.4 )
Between the physical databases itself and the user of the system is a bed of package, the database director or, more normally, database direction system ( DBMS ) . All petitions from users for entree to the database are handled by the DBMS. The DBMS provides users with a position of the database that is elevated slightly above the hardware degree, and supports user operations such as the SQL operation. ( C.J. Date, 1995, P.7 )
3.4 UML 2 and the incorporate procedure 2nd edition, Jim Arlow, Ila Neustadt, 2008
The incorporate modeling linguistic communication ( UML ) is a all-purpose ocular modeling linguistic communication for systems. UML was designed to integrate current best pattern in patterning techniques and package technology. ( Jim Arlow, Ila Neustadt, 2008, P.5 )
Use instance modeling is a signifier of demands technology. Use instance modeling is a different and complementary manner of arousing and documenting demands. Use instance patterning typically returns as follows:
- Find a campaigner system boundary.
- Find the histrions.
- Find the usage instance
- Iterate until usage instances, histrions, and system boundary are stable.
( Jim Arlow, Ila Neustadt, 2008, P.69 )
In the usage instance diagram you represent the topic of the usage instance theoretical account by a box labelled with the name of the topic. This box and capable represents the boundary of the system modelled by the usage instance. You show histrions outside the topic and usage instance, which constitute the system behavior, inside the topic. ( Jim Arlow, Ila Neustadt, 2008, P.75 )
3.5 web development tools
3.5.1Macromedia Dreamweaver 4, Betsy Bruce, 2001
Dreamweaver is an HTML ( hypertext mark-up linguistic communication ) editor, authoring tool, and net site direction tool all rolled into one. You can make many things without every lying your eyes on any HTML. But if you want to acquire down and soil with HTML, Dreamweaver makes it easy to make so. ( Betsy Bruce, 2001, P6 )
3.5.2 Adobe Photoshop web site, hypertext transfer protocol: //www.adobe.com/products/photoshop/photoshop/ , 2010 nowadays
Create powerful images with the professional criterion
Adobe Photoshop CS4 package provides improved entree to its matchless power through a more intuitive user experience, greater redacting freedom, and important productiveness sweetenings. The new characteristics consist of accommodation panel, masks panel, content-aware grading, and improved Photoshop lightroom work flow.
3.5.3 MySQL endeavor waiters http: //www.mysql.com/products/enterprise/server.html
MySQL Enterprise Server package is the most dependable, unafraid and up-to-date version of MySQL for cost-effectively presenting E-commerce, Online Transaction Processing ( OLTP ) , and multi-terabyte Data Warehousing applications. It is a to the full incorporate transaction-safe, ACID compliant database with full commit, push back, and crash recovery and row degree locking capablenesss. MySQL delivers the easiness of usage, scalability, and public presentation that has made MySQL the universe ‘s most popular unfastened beginning database.
3.5.5 PHP
3.5.6 HTML hypertext transfer protocol: //www.yourhtmlsource.com/starthere/whatishtml.html
HTML is a computing machine linguistic communication devised to let website creative activity. These web sites can so be viewed by anyone else connected to the Internet. It is comparatively easy to larn, with the rudimentss being accessible to most people in one posing ; and rather powerful in what it allows you to make.
Chapter 4 method
4.1 Introduction
This chapter of my study will be based on my execution development life rhythm. This chapter chiefly covers all the phases of my undertaking from demands garnering, design and physique, proving and the rating stage, in add-on this study will briefly explicate all the work I carried out in all the stages.
4.2 Analysis
For the analysis stage the demands I gathered were collected and documented within the specification and demands papers located in Appendix 3. In add-on apart from the demands that were documented, they besides include information about what methods I will be utilizing to build the system.
4.2.1 Requirements and specification certifications
Good demands garnering techniques are critical in helping the undertaking to win. So it is of import for me to roll up quality demands at the beginning stages of the undertaking, as the undertaking can alter when of all time during the class of the undertaking. All the demands are documented and located in appendix degree Celsius.
For me to be able to pull out Praksh ‘s demands and demands, I had to make my research by traveling on one web site that would hold similar traits to the system I will be planing and edifice. The chief website beginning I used was a good known hard currency and carry company called booking agents hypertext transfer protocols: //www.booker.co.uk/catalog/advertmenu.aspx? pg=offers.
For me to run into some of my purposes and ends, I used two demands garnering techniques that would let me to garner the necessary information for modeling and documenting the demands.
The techniques were:
- Observation
- Structured interview
- Unstructured interview
4.2.2 Observation
For me to cognize what the web site will be based on and what it will be selling I would hold to travel to Patel ‘s hard currency & A ; carry LTD and look at what points they have to sell and what current system they have if they have one. I did this by using the observation technique.
4.2.3 Unstructured interview
I developed an unstructured interview after I conducted my observation technique at Patel ‘s hard currency & A ; carry LTD supervising the ways they did their concern, what system they have in topographic point and what points they are selling. The unstructured interview consisted on inquiries I asked on the topographic point to my client alternatively of fixing inquiries in progress.
This unstructured interview aided me to derive the feeling that allowed me to derive penetration into the initial demands. After I finished the unstructured interview I so moved onto the structured interview stage.
4.2.4 Structured interview
After making the unstructured interview and observation stages, I so got a opportunity to place figure of critical topics based on the system being constructed. These topics were used to build a list of inquiry for the structured interview. These inquiries were aimed at happening what operations should be implemented within the system
4.3 Requirements Specification
The demands specification stage presents all the consequences of the demands I gathered earlier on. The demands phase consists of usage instance diagrams and specifications every bit good as functional and non functional demands.
4.3.1 Use instance diagrams and Specifications
The usage instance diagrams and specifications aided me in depicting the procedures that takes topographic point in the system, besides shows the relationships between the procedures and single system constituents.
I had to first concept the usage instance diagrams for each usage instance in a high degree format, after the diagrams where constructed I than began the usage instance specification process, this was constructed as it covered each procedure separately in deepness inside informations dwelling of alternate classs, stipulations and station conditions. The usage instance diagrams and the specifications clearly represent the relationship of the procedures.
After I constructed and designed the usage instance diagrams and specifications I arranged a meeting with the client, the intent of this meeting was to demo the client the diagrams and specifications, as I required an blessing from his so I can travel onto the following phase. Subsequently on during the undertaking I may hold to modify the diagrams as my clients demands may alter.
4.3.2 Functional and non-functional demands
After the usage instance diagram and specification phase I was able to continue on to the Functional and non-functional demands stage, I will be showing these demands by utilizing the volere templet technique. The demands will arouse what the system processs are and what they will make.
With the assistance of utilizing the volere templet technique I will be able to associate each demand to certain usage instance if possible. Besides I will be able to stand for a elaborate description of the demands by utilizing this technique. Once I have completed this stage I will stand for it to the client to acquire feedback and blessing, besides make any changes if required.
4.3.3 Database linguistic communication choice blessing
After reading several articles and stuffs and stand foring them in the literature reappraisal stage located in chapter 4, I came to a clear determination of utilizing the following techniques to help me in bring forthing my system:
- PHP
- MySQL
- Dreamweaver
4.4 system Design certification
The system design is the following phase after completion of the demands and specification ; this fundamentally explains and represents how the system will be designed. How I designed the system was with the assistance of several techniques from the UML ( incorporate modeling linguistic communication ) technique, the ground why I am utilizing this technique is because, and UML is an object oriented linguistic communication which works expeditiously in concurrence with PHP coding linguistic communication.
The assistance of UML enabled me to build a specific codification that I may be able to recycle during the design stage. The design stage consists of several UML diagrams including state-chart, category diagrams. This will be located in Appendix D.
4.4.1 UML unified modelling linguistic communication
Unified modelling linguistic communication is a good intent for system modeling as it represents a perfect criterion. The theoretical accounts I will be planing and edifice will be in a plan called Magic Draw. The UML theoretical accounts I will be utilizing in the design phase will be Sequence, state-chart and category diagrams.
4.4.2 Class Diagrams
The category diagram will stand for a inactive theoretical account as it will demo the system classes, attributes, and relationship between categories, these relationships between categories will be seen as entities.
4.4.3 State chart diagram
State machines are most normally used to pattern the dynamic behavior of categories. A province machine diagram contains precisely one province machine for a individual reactive object. In add-on province machines tend to be used most in the design work flow ( Jim Arlow, Ila Neustadt, 2008 )
4.4.4 Sequence Diagrams
A sequence diagram shows, as parallel perpendicular lines, different procedures or objects that live at the same time, and, as horizontal pointers, the messages exchanged between them, in the order in which they occur. This allows the specification of simple runtime scenarios in a graphical mode. ( Wikipedia )
4.4.6 User interface designs
The interface design was built upon my client ‘s specification and demands I gathered from carry oning my interviews and observations. The system interface was designed to be simple and easy for my client and his clients to voyage around the web site without any jobs at all.
I made certain the interface design was as user friendly as I could do it with the aid and mention to several articles and novels. I designed the interface with Photoshop CS4 as it made the website aesthetically delighting and really user friendly, after I designed the user interface I presented it to my client to derive feedback and any betterments needed if necessary.
4.5 Execution
The execution is where I would implement the interface designs and the functionality of the system within the website my client has requested me to construct. Due to the system I am doing for my client he has deemed it to be a paradigm as he will be engaging person else to heighten the system I will be constructing for him. The codification for the enrollment and login was taken from a beginning online and was edited to accommodate my client ‘s demand ; the site can be located within the mention. The engagement system map was fundamentally jury-rigged and designed from the enrollment codification I had implemented within the system and the buying characteristic was all done via PayPal as PayPal gives the beginning for the basket and buying characteristic.
To assist me win in the execution I purchased Adobe Dreamweaver CS4 and Photoshop CS4 besides I acquired a free waiter and PHP admin plan called WampServer. It was necessary and important for me to hold these plans in my ownership as I would necessitate it to assist me develop my clients system.
4.5.1 MySQL Database building
Before I could develop the system I would hold to put up the database on the WampServer I had been utilizing, the database was chiefly used to hive away and recover information for my clients system. I created the database utilizing PHPMyAdmin which was included with wamp. The PHPMyAdmin package allowed me to build and utilize database tabular arraies in a simple and easy manner alternatively of making them utilizing other difficult MySQL waiters with hapless user interfaces.
4.5.2 Constructing the Patel ‘s Cash and Carry LTD web site paradigm
The system I was constructing for my client was a paradigm due to him desiring to engage person else to utilize my system as a edifice block to assist them do an enhanced version of my system. I used Photoshop CS4 and Dreamweaver CS4 to make the paradigm.
The website paradigm I have built for my client is technically a partly completed system because, the client and other users have an chance to prove the functionality of the system and go familiarised with how the system looks and works. This fundamentally allows the client to do certain all or some of his requested demands are implemented within the system.
The type of prototyping I used to assist me develop my clients system was evolutionary and incremental prototyping the ground why I chose these two were because, evolutionary prototyping was an efficient method as it allowed me to construct one and merely one paradigm and allow me heighten and better it every clip I showed my client, so this fundamentally saved me clip from maintain constructing a fresh new paradigm from abrasion which is really clip consuming, that type of prototyping is known as street arab prototyping.
The 2nd prototyping method I used was incremental prototyping, ground for this as this method allowed me to construct separate paradigms for each functionality of the web site, so if I did do a error in the prototyping phase it would non impact the whole system which would so be really clip devouring to either expression through the whole beginning codification for the mistake or start from abrasion based on the latest back up I created.
The paradigm I did was for the payment system, booking system as these two were the most important demands stated from my client. So on the twenty-four hours of showing the functionality of these two systems my client was given the chance to prove both systems to see if they were up to standard and run into his demands. I did do a few minor change and alterations due to the layout and functionality of the system as my client had some disfavors about it.
4.6 Testing
The testing phase is the most important and critical phase of the system design and physique because, this allows me to prove the systems functionality with my client and his staff. This fundamentally gave me the chance to descry out any bugs or mistakes within the system, one time spotted this allowed me to travel back to the design phase and better on it.
The type of proving incorporated within my system was two good known and efficient proving methods called Alpha and Beta Testing ; this merely allowed me to prove the system under normal twenty-four hours state of affairss.
I made certain I tested the system after completion of every paradigm and updated versions and the concluding system, which allowed me to descry any defect after every physique phase.
4.6.1 Alpha Testing
Alpha Testing was the preferable method of proving I chose because, the system that was developed and designed for my client at Patel ‘s Cash & A ; Carry LTD was a new merchandise, like all new merchandises being implemented within an administration at that place will ever be some troubles runing or voyaging around the system. So Alpha proving gave me the chance to prove the system I was constructing with my client ‘s employees and really loyal clients. This helped me a batch as there were a few troubles in both navigating and runing the system so one time collected the information went back to the design phase and rectified the jobs.
4.6.2 Beta Testing
Beta testing was the following phase of proving after transporting out Alpha testing,
4.7 Evaluation
Chapter 5 Undertaking Consequences
5.1 debuts
This chapter covers all the consequence and findings I have collected throughout my whole undertaking, this was done so in order to help me to run into all my aims and bring forth a feasible and efficient web site system paradigm for my client.
The consequences will affect all the variables mentioned in “Chapter 4 Methods” runing from:
- Requirements and specifications
- Design
- Execution
- Testing
- Evaluation
5.2 demands and specification
The analysis phase in this undertaking involved me transporting out specific actions which would let me to acquire a clear sight of what I had to make to assist me carry through my undertaking of planing and edifice my clients net based system.
How I accomplished the analysis phase was by transporting out and finishing these certain undertakings:
- Requirements garnering
- Use instance designs
- Use instance specifications
- Functional and non functional demands
5.2.1 Requirements garnering
During the demands phase sensible and objectionable consequences were acquired throughout conductivity specific arousing techniques, the two utile techniques I used to assist me get my client ‘s demands were:
- Unstructured Interview
- Observations
Presented below was the observation I carried out within my clients concern, the observation was a really utile demand assemblage elicit technique, as it helped me acquire a clear position of how my client ran his operation and allowed me to acquire a clear penetration of what current system he had implemented within is administration.
Current system being used at the minute:
- Client goes to clients store.
- Client gives his client a list of points available to buy.
- Once the client has chose the points they want he/she will give it back to client.
- The client will so phone the warehouse to look into if the point is available and measure is available.
- The staff at the warehouse will so inform the client if the points are available.
- If the point is non available the client will state the client and suggest alternate points.
- The client will pay for the point if available and so will be given a bringing day of the month.
- The client will advise the staff at the warehouse and so they will update the stock list.
Problems with the current system:
- The client will hold to be present in their client ‘s stores to be able to do a sale and the client to do a purchase.
- The client does non hold a competitory border against other competition.
The observation technique involved me naming what current system was being used by taking note of how to work and what procedures they would transport out during a normal busy twenty-four hours, besides I listed the chief jobs with utilizing the current system. This was another major aid as it allowed me to build a to the full and efficient structured interview.
For the structured interview I managed to garner all the demands my client would wish to see implemented within his new system I developed for him. This was really utile as it gave me a broad range and penetration to cognize what I was working with in footings of how the system should work.
5.2.2 Use instance diagrams
Using the feedback I acquired from carry oning my structured interview, this allowed me to make a clear and right usage instance diagrams based on all the demands received from my client, which would later on be used for the functionality of the system.
I designed four types of usage instance diagrams admin, client, staff and order procedure the allowed me to place and clear up to my client all the maps the admin and staff carry out in add-on with maps that the clients would transport out. This was done chiefly because, the clients functionality would be wholly different from the admin and staff functionality because, clients merely use the system to assist them buy merchandises and book meetings where ass the staff and admin maintain the system to help them with my clients concern.
These diagrams can be located in“Appendix C Requirements and Specification” paperss, the lone two complex high degree usage instance diagrams that I personally thought was created were the admin and the client usage instance diagrams. Subsequently on during several meetings me and my client decided to scour the whole staff usage instance diagrams as we believed it had the same functionality as the admin usage instance diagram. This was really helpful to me as it saved me from making two separate sides of the system which ab initio did the same thing.
After making the three usage instance diagrams I so constructed more the several usage instance specifications, this allowed me to give my client and supervisor some penetration on how the system will work and what functionality was implemented within the system.
5.2.3 Use instance specifications
The ground behind building the usage instance specifications was because, it allowed me to document the functionality of the system, this was done chiefly to assist I and my client understand what his system would be capable of making.
In entire 35 usage instance specifications were created based from the usage instance diagrams, due to the page limitation I have within this study you can turn up all 35 usage instance specifications in “Appendix C demands and specification document” .
Below are two use instance specifications that were created from a usage instance diagram. This diagram will explicate one of the functionalities implemented within the system.
Use instance: Access web site
Idaho: CUSTOM1
Brief description:
The client accesses the Patel ‘s website via cyberspace browser.
Primary histrions:
Customer.
Secondary histrions:
None
Preconditions:
- The client logs on to his/her computing machine.
- Use their web browser to entree the Patel ‘s hard currency and carry web site.
Main flow:
- The usage instance initiates when the client goes on to their computing machine or laptop
- Customer log ‘s onto their computer/laptop.
- Customer uses their cyberspace browser to travel to the web site.
- Customer has successfully accessed the Patel ‘s hard currency and carry web site.
Post conditions:
- The client has successfully accessed the web site
Alternate flows:
None
Use instance: topographic point order
Idaho: CUSTOM9
Brief description:
The client places an order on the web site.
Primary histrions:
Customer
Secondary histrions:
None
Preconditions:
- The client logs on to his/her computing machine.
- Use their web browser to entree the Patel ‘s hard currency and carry web site.
- The client has logged into their user history on the Patel ‘s hard currency and carry web site.
Main flow:
- The usage instance initiates when the client goes on to their computing machine or laptop
- Customer log ‘s onto their computer/laptop.
- Customer uses their cyberspace browser to travel to the web site.
- Customer has successfully accessed the Patel ‘s hard currency and carry web site.
- The client successfully logs into their user history
- Once logged into the history a members page will look
Members page appears and the member chinks onto the topographic point order check
the topographic point an order window will demo up
here the client will be able to order what merchandises they wish to buy
one time they have finished choosing the points they want they merely click the topographic point an order button
this is when the order will be processed and delay for the admin or staff at Patel ‘s hard currency and carry to
O.K. the order - Once order has been approved the client will have an electronic mail saying order has been approved, how much it will be and what twenty-four hours it will be delivered.
Post conditions:
- The client has successfully found placed an order.
Alternate flows:
None
5.2.4 Functional & A ; non functional demands
After building and finishing the necessary usage instance diagrams and specifications I was able to travel onto my following phase of the analysis phase which consisted of developing the functional and non functional demands of the system. I used an eliciting technique I learnt from my 2nd twelvemonth at university which allowed me to document all necessary functional and non functional demands, the technique I used was called the Volere templet, this allowed me to stand for and show the demands in an efficient and professional manner. This templet besides allowed me associate each usage instance specification to each functional or non functional demand presented by the volere templet. Below is an illustration of one of the volere templets I created.
As you can see from the “customer Non-functional & A ; Admin Functional” demands this allowed me to place which parts of my clients demands from the usage instance diagrams and specifications where really functional demands that would run within the system and what was a non-functional demand which was non needfully needed in the system but had to be implemented to let me to expeditiously and successfully finish the system. All of the functional and non-functional demands can be located in “Appendix C demands and specification document”
5.2.5 Decision
After carry throughing all necessary undertakings involved with the analysis phase and the demands and specification papers, I was able to sum up a decision to assist and do it clear to my client and supervisor what I carried during this phase.
What the writer found utile in the decision phase was, aided in placing what scheduling and database linguistic communications should be used to help on developing the system.
The database and scheduling linguistic communications I decided to utilize where:
- PHP
- MySQL
- Hypertext markup language
5.3 design
After finishing the demands and specification papers the writer so carried out the design papers which can be located in Appendix D, this allowed him to plan the system for his client harmonizing to his demands. The design papers consists of:
- Class diagrams
- Graphical User Interface
- Sequence diagrams
- State chart diagrams
- MySQL design
These diagrams were created by utilizing the UML diagrams that was constructed in the demands and specification papers. The UML diagrams acted out as a design for the writer to build the system in more item with the assistance of the design paperss.
5.3.1 Class diagrams non bundle
The writer created the category diagram non bundle by uniting three category diagram packages together. The category diagram bundles that were used to do this category diagram where:
- Merchandises bundle
- Delivery bundle
- Histories bundle
The combination of all three category diagrams fundamentally allowed the writer to stand for clearly to his client what the functionality of each category consists of and does, located in 5.3.2 will be descriptions of the three category diagrams bundles created. Below is the category diagram non bundle created by the writer.
5.3.2 Class diagrams bundles
For the category diagram packages the writer decided to divide them in to three bundles because, it allowed him to stand for to his client what functionality consists in each category diagram packaged, this helped him explicate to his client what the system does without confounding him with excessively much proficient slang he would non understand.
The merchandises bundle category diagram fundamentally shows the categories and the relationships between them which allowed for the creative activity of the needed merchandises demands and functionality.
The bringing bundle category diagram represents what categories and relationships allowed for the bringing functionality to be created and implemented ; this fundamentally shows how the bringing procedure will be carried out utilizing the system in my client ‘s administrations.
The histories bundle category diagram represents the categories and relationships between the histories functionality and demands the client requested, this fundamentally states how the histories procedure will work and all the procedures that will be carried out when a new history has been made or what inside informations it will incorporate.
5.3.3 Sequence diagrams
The sequence diagrams was created by utilizing the usage instance diagrams and specifications, fundamentally a more complex usage instance diagram was created but in a consecutive manner. During the design phase six sequence diagrams were created. Below is the Login diagram. This can be located in appendix D design papers.
This diagram fundamentally shows what maps are involved harmonizing to the sequence order. This diagram runs thought the login maps, before the client can log in they have to come in their user name and watchword, one time they have entered their inside informations they so can snap the login button, one time clicked the event animal trainer will manage the three events which are username watchword and login, it so connects to the members database where it authenticates the login inside informations if right allows them to log in successfully, if the inside informations are wrong it will so come up with an mistake message.
5.3.4 State chart diagrams
The province chart diagrams fundamentally are a lower degree version of the sequence diagrams, these were created in the same manner the sequence diagrams where created utilizing the usage instance diagrams and specifications. The ground why the writer created the province chart diagrams was because, they show the procedures which contain more than one objects with more than objects within the provinces. Another ground why this method was included in the design stage was it allowed the writer to explicate the functionality of the system in an easy lower degree design position without utilizing any proficient slang that the client would non understand.
Four province chart diagrams were created which were:
- Customer history
- Offers
- Purchase procedure
- booking
These can be located in appendix D design papers. The diagram below is based on usage instance specification “CUSTOM8: Topographic point an order” which can be located in appendix C demands and specification papers.
The first province is entree new merchandises. This is where the client can look at the assorted merchandises the clients system has to offer them. The following province is choice merchandise ; this is when the client selects any coveted merchandise they wish to buy. The 3rd province is add to PayPal shopping cart province, this is where the client will add their selected merchandise to the PayPal shopping basket and acquire re-directed to the PayPal check-out procedure. The 4th province is update PayPal shopping cart, this province is non mandatory as sometimes the clients may non necessitate to update their shopping cart but if they have to they can update their measure they wish to buy or take merchandises. The fifth and concluding province is PayPal purchase procedure ; this is where the client finishes up their purchase by taking payment type and reference and so finalizing their payment by snaping bargain now.
5.3.5 Graphical user interface
As requested from the writers client and stated in his demands, the writer developed a simple and basic user friendly graphical user interface for the system. The writer kept in head that he had to make a simple, basic and user friendly user interface to let his clients clients and staff to easy voyage through the system without acquiring confused or happening it hard to entree specific pages. This can be located in appendix D Design papers.
The writer created graphical user interfaces for several pages for the system which range from:
- Main page
- Login page
- Servicess page
The references GUI ‘s that the writer created were used as a templet to assist make the catalogue, registry, payment, profile, members page, booking page, reach us page and other parts of the system, this was merely done as it allow the writer to salvage clip by making a GUI for each subdivision of the system which is clip devouring and non efficient. Shown below is the chief page of the system.
The variables that consisted of the GUI were of import things like colorss, layout, and menu saloon all these variables have to be consistent as in every page as this would do the web site and system aesthetically delighting to the client and his users. In add-on these variables allowed the client to larn easy how to voyage themselves through the system. All these variables allowed the writer create an aesthetically delighting system which was really user friendly and consistent.
5.3.6 MySQL design
The MySQL design was a important anchor of the system development phase because, this allowed all the functionality within the system to work because, and database stored and retrieved all necessary informations within the system. For illustration, the payment and engagement system requires the client to input informations into the system and the information inputted will be stored into the database, one time the client has made the payments or the engagements the writer ‘s client will so hold to entree the database to recover the coveted information.
Without the database being implemented within the system the payment, engagement, login and registry functionality would non work within the system and the client would merely be left with a inactive web site without any requested demands and functionality.
The image below is the database MySQL cryptography for the members table located within the PatelsCash database located on my waiter.
5.3.7 Design sum-up
The concluding consequence of the system design runing from, graphical user interfaces, sequence diagrams, category diagrams, province charts and MySQL tabular arraies can be located in appendix D design papers. This is used to demo the writers supervisor, client and secondary marker how the system was designed and what tool was used to develop the system.
5.4 Execution
Once the writer completed the demands specification and design paperss, he was so enabled to continue to the execution phase. This consisted of implementing assorted functionalities being implemented within the system designed. How the writer carried on the execution was by choosing preferable database and scheduling linguistic communications, which were stated in the decision of the demands and specifications papers.
5.4.1 MySQL creative activity
Before the writer could transport out any functionality execution he had to first create and implement the MySQL database within a waiter. This was with the assistance of the MySQL designs from the design subdivision, how the writer created the database and MySQL tabular arraies was with a helpful tool included his waiter called phpMyAdmin. After the writer set up the waiter and the MySQL databases he could so eventually travel onto making the system prototypes.
5.4.2 Patel ‘s Cash & A ; carry website paradigm system
The writer created the system for his client as harmonizing to his demands and implemented all the necessary functionalities within the system to assist him run into his clients need and to do the system to the full functional.
The writer created the paradigm system by constructing assorted subdivisions of the system functionality individually. These subdivisions that he built separately ranged from:
- Payment paradigm
- Booking paradigm
- Purchase paradigm
- Contact us prototype
- Login paradigm
- Registration paradigm
From this subdivision forwards the writer will demo the consequences of some paradigm subdivisions he built harmonizing to which he thought was necessary to include within the studies subdivision.
5.4.3 Payment paradigm
The payment paradigm was developed before the engagement paradigm because, the writer found it easy and simple to make as his client would usually let his clients to pay for points brought at meetings if they have deficient financess. The writer made maps that allowed his client ‘s clients pay for points by paying outstanding balance on an bill issued during minutess and payments, the client inputs the bill figure and other inside informations so go onto inputting recognition card inside informations so click submit payment. The writer made the payment paradigm in one spell.
5.4.5 Booking paradigm
The writer developed the engagement paradigm foremost before any other functionality due to his undertaking and his client chief demand was to construct a engagement paradigm, which allowed his client to book meetings and travel to their stores and let the client to do more a net income and derive more clients to crush his competition. The writer made the engagement system in one effort as he found it really simple and basic to develop without running into any high hazard jobs.
5.4.6 Implementation sum-up
At the terminal of the execution phase the writer managed to successfully make the engagement, purchase, payment paradigms. The chief paradigm that had to be completed was the engagement system as his undertaking and his clients demands revolved around the engagement system. The client acknowledged that all of his demands where met when the writer demonstrated his paradigms during a meeting they had which can be located in appendix F meeting paperss.
The lone paradigm that was non created was the admin side this was because ; due to the clip constraints the writer ne’er got clip to finish it and was non one of the important demands stated by his client, the client did non mind and said he “would be engaging a developer to better the paradigm to do it a to the full working commercial system” .
5.5 Testing
The writer conducted two types of trials one was whit box testing and the other was black box testing, both of these proving methods were carried out after each paradigm was developed. How the writer conducted these trials was, he made certain each demand that every bit stated in the demands and specification papers was met. If some of the demands were non met in the testing phase this was due to either the clip constraints the writer had or deficiency of cognition to acquire the demands to work.
The white box proving method was used during the building of the paradigms as it allowed the user to prove his plan codification measure by measure and if any mistakes occurred he could rectify them immediately alternatively of detecting one time the paradigms were all finalised and have to travel back to the design phase to repair the job. This saved the writer sometime as it allowed him to repair mistakes in the design phase and salvage him from documenting this as it was carried out during the development of the paradigms alternatively of after development.
The black box proving method could merely be conducted when the paradigms were to the full developed and finalised, the black box proving method is specifically based on usage instance specifications, functional and non functional demands. The writer carried out the black box proving in two ways one was by proving against the usage instance specifications and the other was against the demands.
