Articles

Database Development Cycle: - Need to create & design database document

by Alice Portman Technical Writer

The database is implemented in following six phases.

  •          Database study
  •          Database design
  •          Implementation and loading
  •          Testing and evaluation
  •          Operation
  •          Maintenance and evolution

 

 Here we discuss the phases of database development cycle:

·         Database study: This phase includes the study of the database existing and proposed requirements. With the SSAD methodology, requirements specifications are meeting. HPI firm, wants to upgrade their operations, it will helps in reducing fraudulent claims to the insurers. So it is clear that there main requirement is make a database that only allows one vehicle only be insured by only one insurer. It will help them for genuine claims proceeding. The database will relational as it will be connected to the insurer’s database.

·         Design: The SMART process results the logical design of the database. On the basis of logical design the real database is developed. Throughout the design process pieces conjoint in RDBMS. For the HPI database Ms-SQL is used as server. The relational database management system is design will fulfil the all requirement of HPI firm.

 ·         Loading and development: In this phase, the tables will be load and database will be developed. This phase will also perform the testing of the developing database. In this phase logical design and technical specification management is tested. The database configuration and field constraints are set in this phase.

 ·         Evaluation and Testing: The implemented database is assessed and tested in this phase. The database is tested by analysing the mapping of the database. The access methods and key management in the database is managed for the HPI firm. This phase narrates about the performance analysis of the developed system.

 ·         Operation: in this phase, operations are performed on database. All the functionality is applied for the developed system. For HPI firm data with different tables has been analysed.

·         Maintenance and evolution: with this phase maintenance plan has been developed for the database. it is known thing that end user will involve in the application of database but if any malware attack or any other vulnerability occurs on the database, what to do and how rescue operation is perform, is decided.

 3.2          design a fully functional database (containing at least four inter-relational tables) including user interface

This developed database is RDBMS and it is based on the given requirements. With this following things can be performed:

 

·         Entering and maintaining vehicle, insurer and firm information

·         View information from all the tables

·         Insertion and maintains stolen and fraudulent vehicle  details

·         View reports

 3.3 Testing of the database using queries

Database testing is a crucial stage in database management system. The database testing is important because of following reasons:

·         To perform mapping transformation between the front end and back end (tables) which is called data mapping. This mapping is done by checking the invoked action at the front end and the event occur at back end operations like create, insert, update, delete and so on.

·         To validate the ACID properties of database testing is important. These words are itself a testing procedure.

Ø  Atomicity

Ø  Consistency

Ø  Isolation

Ø  Durability

·         To maintain integrity it is must that if any of the database operations are performed the results must be reflected at form screens as well.

·         Business Rule conformity states that there might the cases where database is so complex that it can’t be solved by single statement queries. In such cases complex objects like triggers, procedures, and assertions are used.

 Database testing process involves:

3.4 evaluate the effectiveness of the database solution and suggest methods of improvement

 The developed RDBMS of HPI firm will manage the whole fraud detecting activity and manage the things that are effective administration, fraudulent vigilance and information management. This database system will be responsible to serve Association of British Insurers (ABI) and positive results from its implement will cut insurance costs for honest motorists. HPI is firm that keeps the information of all vehicles and it only allows that one vehicle will only be insured by once. The developed functional database will handle the vehicle details, stolen vehicle, and insurer details. The developed database is restricted and required to be more restricted as it contains the valuable information. The developed database can be more effective with following methodology 

 

Database Expansion:  As the data will be continuous incremented, thus database must be expand with the time. This database can be expanding more by building process. With that more information can be stored according to the requirement 

Expanding and Building- in the Expanding and Building Process, ABC ltd. required to verify the requirement of existing data. Building of existing data helps the company so it can easily access the data as per their requirements. Furthermore, in this database we can implement more information according to the requirements.


Cleaning- In such kind of database where the information insertion will be done in continuous way, cleaning of database plays important role. For the cleaning of HPI firm will erase the replicate and old data automatically. It is need of time as new data will requires space and if there is option to make space then choosing it is good idea. The cleaning process includes the removal of inactive tables, duplicate entries and propagates table merging.

 

Regular Update – Regular updating is good practice but for the HPU firm it will be updated daily but there are table which holds the ‘pending statements’ such the cases where single vehicle have multiple insurance so that will be flagged as fraudulent status. So if the database reminds the admin about such pending tables, then it will be greater as one table will be removed from one flag to another flag. The daily updating helps to work on such cases easy.

 

3.5 provide supporting user and technical documentation.

In a technical documentation the functionality, architecture and handling methods are provided. The documentation will work for the end user and administrator. The documentation will define external and internal dependencies of the system.

In the developed database system, the database of firm and insurer is directly connected and they are relational table. The details of vehicles are saved separately where the details of stolen vehicles and fraudsters will be managed separately. The number of driver that drive specific vehicle will be saved in separate table.

With this database HPI firm will be able to store the details of all vehicles, stolen vehicles and fraudster vehicle. Each vehicle has contains the foreign key with the status i.e. stolen and fraudster. This will help in identifying the status of the particular vehicle.

The technical documentation contains the following thing described in this reports earlier section.

·         Architecture or Design of system – the design of the system shows the interface and how the data will be store in the backend.

·         End user- It discusses the way by which end user of the system how interact with the system. Since this application is implemented in backend only and front end yet to construct, is not provided.

·         Technical – It consists of documentation of used code, set of tables, interfaces, and APIs.

·         Requirements – To run this database a system required to have MS-SQL.

 

4.1 Reflections on the whole process of designing and development of the system.

According to the whole case study what we have understood is to make a new modernized database which will help our company to detect fraud related to vehicle. The process has been started from the analysis of the case study as it is the first step in any system. An in-depth analysis is done as the case study for database is quite typical to understand and to design. In the design process of database we find difficulties to make relations and tables as it is going to be used as software to detect car fraudsters which is itself a sensitive topic. To ensure primary key and ensure referential integrity was a challenging task. Although somehow the database has been created, keeping all guidelines, assumptions and points related to case study in mind. The outcome proved to be fulfilling all the requirements stated by the vehicle information firm HPI.

·         There is a log maintain by the database for the stolen vehicle in the stolen vehicle table.

·         There exists a fraud vehicle table to detect fraudsters.

·         The insurer table maintains the records of all the vehicles registered to the insurance company.

The database detects those vehicles which have multiples instances of insurance to be claimed.

4.2 User Feedback

There might be the case that it will not be easy for the users to understand the database and fire queries as the complexity exits in the database. The data must be inserted wisely to avoid data inconsistency. The chances of detecting fraudsters are very high in this database management system. The implementation of such a database solves the problems of various sectors and proves to be a powerful database as it is a need of general public and insurance companies.

4.3 Future amendments

From the future perspectives we are going to add more tables to the database to give the better understanding of the database handling. We will try to reach at the third level of normalization (3NF) to improve database functioning and reduce anomalies related to redundant or inconsistent data. In future the user interface can also be made for user point of view to give users an interactive approach to connect with the database. We can make data flow diagrams in future to describe the flow of data during the entire process. Entity relationship diagrams will be changed with the more functionality added. The complexity will be reduced to a level by modifying data or field values in the relations. Dependency will be stated between the relations and between the attributes.

Top Grade Assignment Help is an online assignment help company which deals in computer Top Grade Assignments EXCLUSIVELY. We are having experts who are from many leading universities and possess sound experience in providing Database Assignment Help to grab  technical assignment help


Sponsor Ads


About Alice Portman Freshman   Technical Writer

13 connections, 0 recommendations, 45 honor points.
Joined APSense since, September 29th, 2016, From 480 George St, Sydney NSW 2000, Australia.

Created on Dec 31st 1969 18:00. Viewed 0 times.

Comments

No comment, be the first to comment.
Please sign in before you comment.