Conclusion 


The flight system was selected by our team for the case study. We have six members and I am the team leader. As a team leader, the support I received from other members was great. Everyone shared the work equally.

Uvindu created the elements, attributes, relationships and ER diagrams associated with the system. It was Savindu's job to identify and document the actors and business processes in the system. Mashi performed the identification of system functional needs and non-functional needs. I dealt with the issue of standardization and relational schema. SQL coding was done by Sahan and Sampath. Although working separately, everyone focused on each task.

Several problems arose while studying these cases. The main problem was the power outage. Power outages can cause data problems. Unable to connect at the same time due to group members joining online. Face-to-face encounters take place online. Having some problems making decisions.

Much valuable knowledge was gained in this case study process. Gain a better understanding of how to create a blog. I also had the ability to maintain a blog. They were able to exchange creative ideas with each other. It was a great opportunity to show off their talents. We had the opportunity to interact with each other. They were also able to solve their own problems. Was able to work on time. Saving time is also unique. Members' contributions are also welcome. It is also important to have the guidance needed to carry out more productive activities in the future.

My heartfelt thanks to the Coordinator , the Instructor in charge of the subject , my team members and everyone else who contributed to the success of this case study.