Evaluation Document for ADORN BAGS WHOLE SALE

INTRODUCTION:
The first part of this graded unit intends to evaluate the project performance. That refers to the concept of verifying the desired output of the said application. In Second part my (developers) evaluation is required to be performed that either the performance during the development remained up to the mark or not.

PART 1 - EVALUATING THE PRODUCT

This part is divided as: Analysis of the project Project plan Effectiveness of the solution including Implementation Testing Deployment

1. Analysis of the project:

The software is designed for a small store management system. To me the requirement gathering phase was of most importance because this module defines the effectiveness and efficiency of the desired system. It actually was the phase where I actually identified that what is expected of me in terms of this application. Functional requirements were identified during this phase.

2. Project Plan:
It informs that how actually the development is carried out. In first stage or planning stage functional and non-functional requirements were maintained. Methodology for moving from problem domain to solution domain was identified. Secondly the resources to accomplish those requirements were identified to complete the project. Thirdly development stage was achieved which further includes three parts:

Design, Implementation and Testing:

Originally it was planned to design the required system using an object-oriented programming language like C# for the design and implementation and oracle had to be used for the database design and Universal Modelling Language (UML) was also necessary for creating diagrams related to the objects and code. But later the event driven approach of visual basic 6.0 attracted me towards its use and Microsoft Access 2003 database system proved to be the best compatible DB solution with VB. Then the project plan was updated accordingly for the analysis and design as well as the Implementation part of the development stage. Proper project planning helped me in prioritising my tasks and their successful achievements. Testing is a very important and affective part of the program to ensure that program is error free and accurate as per the requirements. Testing each form separately helped me in minimizing the risk for bug occurrence. Testing strategies were actually made to perform the testing. Those test plans were adopted accordingly to verify the outputs.

3. Effectiveness of Solution Methodology:

To keep it more simple and effective the chosen approach was thought to be simple and effective because its easy to check whether its working or not time to time. By using this approach we actually get to know that are we really building the thing RIGHT and we are building the RIGHT thing. By continuous evaluation of our plan and approach the efficiency can be checked accordingly.

Documentation
Detailed documentation of all the modules and of overall project is maintained so that any future enhancement could be made easy and convenient to new users or developers. Following two different reports after each stage were maintained; Planning report Developing report

PART 2 - EVALUATING MY PERFORMANCE

In this part, I will evaluate my activities which were carried out during the project execution phase. The following areas will be evaluated: The outline of the assessment The handling of unforeseen events The identification of any knowledge and skills gained Evaluating the effectiveness of the problem solving activity Modifications to Approach Design or Implementation Concluding Recommendations for the future.

1. The outline of the assessment :

The required system was designed for a small Adorn Bags Whole Sale. All necessary data was given from the outset therefore I felt confident initially as far as the interface and the coding were concerned. However, the software to be designed required a connection to a database and manipulation of data to/from the same database. That is why I chose Visual Basic 6.0 as my development environment because I was already familiar with forms.

2. Handling of unforeseen events :

The only unforeseen event which I faced was the connection between Visual Basic 6.0 and Microsoft Access because I didnt study about this in my HNC Course. To solve this problem I used the Internet Search Engine GOOGLE. And get some more information from YOU TUBE.

3. Identification of any Knowledge and skills gained:

I used Microsoft Visual Basic 6.0 to design the user-interface and develop the code. However, the aspects related to the Database connectivity and data manipulation wasnt so easy to deal. Therefore, I did some research to discover that how can we connect to a remote database and interact with it using ADO (Active X Data Objects). Additionally, I learnt how to use new tools such as the ADODC, the status bar and the data grid. I also learned how to use the combination of SQL, ADO and code to communicate with database and perform any necessary task such as finding a specific record or retrieving specific data from the database and displaying it on a Data grid.

4. Evaluating Effectiveness of The Problem Solving Activity:

While executing project activities original scenario was kept in mind to make it closer to the real time environment at its maximum. The aims of the graded unit are fully covered, and there is no level or degree of the information not completed which were supposed to be completed and gathered for this project. I can confirm that the software I have designed meets all the clients requirements. In fact, the system is user-friendly, functional, robust and error-free. Furthermore, while evaluating the problem solving activity, following things was kept in mind;

a. Design b. Implementation c. Test strategy

5. Modifications to Approach, Design or Implementation:

Nothing is or can be perfect. Although the project modules were carried out to their best but there is always room for improvements. Further modifications which can be performed on the modules are; Approach Design Implementation

6. How Could Project Be Improved:

The Project Adorn Bags Whole Sale is tried to make up to the best in its functionality. However it can be upgraded in some ways. We can make a user registration and LogIn menu for both user and administrator separately, where the administrator could only perform the tasks regarding management issues, while on the other hand an ordinary user could search his/her desired material accordingly after providing required necessary information. We can make it better by inserting the upload picture (for the product) function and by separating the different categories of the product such as bags, purse, luggage etc.

7. Recommendations:
It is recommended to carry out the future projects of this nature in the similar way but with more precision. As it forms the overall project execution it is found that the used approach is quite easy in its handling. Furthermore the design and implementation also doesnt cause any problem.

8. Conclusions:

At last but not the least the software product named Adorn Bags Whole Sale is a full and final product which is capable of being deployed in any sort of Product management environment. It is also important to note that it can be access at any time. It is user friendly in its nature and requires least technical skills for its handling and management.