Page 137 - ASBIRES-2017_Preceedings
P. 137

INSURANCE QUOTATION MANAGING SYSTEM






































                                                   Figure 1: UML use case diagram



                               3  METHODOLOGY                             Figure 1 shows the steps used to analyze
                                                                       the system and do the designing. Hence the
                     3.1 Overview of the System Architecture           unit  testing,  Integration  Testing,  System
                                                                       Testing  and  Acceptance  Testing  were  done
                        Architectural design is the first illustration   to  ensure  the  system.  Testing  procedure  is
                     of  the  overall  structure  of  the  main        used to verify the proper functioning of the
                     components  of  the  insurance  quotation         software application.
                     comparing  system.  The  total  structure  is
                     based  on  how  it  would  suit  the  software         4 RESULTS AND DISCUSSION
                     architecture  of  the  application  and  the
                     authentication  module.  Overall  system  will    4.1 Results
                     be  split  in  to  three  layers’  names  as         Evaluation  will  be  helpful  to  identify
                     application layer, data layer and presentation    whether we are able to achieve our expected
                     layer.  Overall  system  architecture  of  the    level  of  system  application.  To  ensure  the
                     proposed system is given in Figure 2.             well  functionality  of  the  final  development,

                                                                       testing  is  essential.  Proper  testing  process
                                                                       makes sure that functional requirement or the
                                                                       business  requirements  are  met  in  the
                                                                       perspective  of  the  developer  and  the
                                                                       perspective of the clients.

                                                                          Testing  should  be  conducted  in  well-
                                                                       organized  manner  wrapping  all  the  related

                                                                       components.  Missing  components  may  lead
                                                                       to a poor testing procedure and generating an
                                                                       output with bugs which may discourage the
                                                                       clients  to  use  the  software  application  and
                                                                       get a productive output. Also Summative and
                       Figure 2: Three tier architecture model         Formative  evaluations  are  done  to  evaluate



                                                                    127
   132   133   134   135   136   137   138   139   140   141   142