SE Final Year Project, Lab Reports of Software Engineering

Download SE Final Year Project and more Lab Reports Software Engineering in PDF only on Docsity! Shahwar Irshad 29787 Osama Intikhab Zarar Haider 29711 Syed Haseeb 30112 30413 Ms.Toba Nasir A Final Year Project Report is Submitted in Partial Fulfilment of the Requirements for the Degree of Bachelor of Science in Department of Computing & Technology Iqra University, Islamabad Campus January 2021 Power station information system Certificate We hereby accept the work contained in this report titled: Power station, as a confirmation to the required standards for the partial fulfillment of the degree of Bachelors of Science in Computer Science. Internal Examiner External Examiner Project Supervisor Head of Department 2 Acknowledgements All praises are for Allah Almighty and Holy Prophet Muhammad (peace be upon him) for giving us knowledge, power and strength to accomplish this task. Many people have helped me to contribute a little bit to build me up as a researcher and more imperative as a human. Here, I wish to express my gratitude for their help. We would also like to express our gratitude towards our Teacher mam Toba, her patience, understanding, and expertise added considerably to our project experience. We have learned a lot from this experience which hopefully will be a great help in our future. Last but not the least; this is also the time to thank our families for all the support, love, and encouragement they provided to make the best of this experience. It wouldn’t have been possible without their support and motivation. We would also like to thank all our friends who have contributed to this work by being always there whenever we needed them the most. A special thanks goes to Faraz, Zarar and Hamza. Abstract Power Station System is a Java web project which reduces the misery of power and makes it easy in a short period of time. The project is dedicated to the power plants this project enables users to access mobility assets owned by others exactly when they need. This task is hundred years old, but with the market tools implementation on power systems operation and planning the feasibility study conditions change substantially. The criteria for maximizing the profit of stakeholders of power plants should be reformulated. The criteria may contain the uncertain and random variables. The task becomes much more complicated which necessitates the creation of new algorithms and software tools for its solution. Using this software the users are able to view planned load shedding schedule and actual load-shedding. The users are able to view billing information and get duplicate bills. The users are able to get estimated bills through bill estimators by just entering consumed units, Contents Declaration..................................................................................................................................................1 Dedication...................................................................................................................................................2 Acknowledgements.....................................................................................................................................3 Abstract.......................................................................................................................................................4 List of Tables................................................................................................................................................9 Chapter 1 Introduction..............................................................................................................................11 1.1. Overall Description...........................................................................................................................2 1.1.1. Objectives..................................................................................................................................2 1.1.2. Problem Description..................................................................................................................2 1.1.3. Methodology.............................................................................................................................2 1.1.4. Product Scope............................................................................................................................3 1.1.5. User Classes and Characteristics................................................................................................3 1.1.6. Operating Environment.............................................................................................................3 1.1.7. Assumptions and Dependencies................................................................................................3 1.2. External Interface Requirements......................................................................................................4 1.2.1. User Interfaces...........................................................................................................................4 1.2.2. Hardware Interfaces..................................................................................................................9 1.2.3. Software Interfaces....................................................................................................................9 ...........................................................................................................................................................10 1.2.4. Communications Interfaces.....................................................................................................10 ...........................................................................................................................................................10 1.3. Nonfunctional Requirements......................................................................................................10 1.3.1. Performance Requirements.....................................................................................................10 1.3.2. Safety Requirements................................................................................................................10 1.3.3. Security Requirements.............................................................................................................10 1.3.4. Software Quality Attributes.....................................................................................................11 Chapter 2 Literature Review......................................................................................................................12 2.1. Introduction....................................................................................................................................13 2.2. Related Works.................................................................................................................................13 2.2.1. Categorization of Existing Techniques/Works/Research..........................................................13 2.2.2. Limitations/Gaps within Existing Techniques/Works...............................................................13 2.2.2. Limitations/Gaps within Existing Techniques/Works...............................................................13 2.3. Proposed Improvements in Existing Works....................................................................................13 2.4. Summary.........................................................................................................................................14 Chapter 3 System Design...........................................................................................................................15 3.1. Introduction................................................................................................................16 3.2. Design Considerations....................................................................................................................21 3.2.1. Assumptions.............................................................................................................................21 3.2.2. Constraints...............................................................................................................................21 3.2.3. Risks and Volatile Areas...........................................................................................................21 3.3. High Level Design............................................................................................................................22 3.3.1. View / Model Element 1…N.....................................................................................................22 3.4. User Interface Design......................................................................................................................24 Chapter 4 Implementation........................................................................................................................31 4.1. Discussion............................................................................................................32 4.2. Development Methodologies..............................................................................32 4.3. Implementation Tools and Technologies.............................................................32 4.4. Summary.............................................................................................................32 Chapter 5 Testing.......................................................................................................................................33 Chapter 6 Conclusions and Future Work...................................................................................................41 6.1. Contributions..................................................................................................................................42 6.1.1. Contribution 1..........................................................................................................................42 6.1.2. Contribution 2..........................................................................................................................42 6.2. Future Work....................................................................................................................................42 6.2.1. Improvements in the existing System......................................................................................42 References.................................................................................................................................................43 Appendices................................................................................................................................................44 List of Tables Declaration..................................................................................................................................................1 Dedication...................................................................................................................................................2 Acknowledgements.....................................................................................................................................3 Abstract.......................................................................................................................................................4 List of Tables................................................................................................................................................9 Chapter 1 Introduction..............................................................................................................................11 1.1. Overall Description...........................................................................................................................2 1.1.1. Objectives..................................................................................................................................2 1.1.2. Problem Description..................................................................................................................2 1.1.3. Methodology.............................................................................................................................2 1.1.4. Product Scope............................................................................................................................3 1.1.5. User Classes and Characteristics................................................................................................3 1.1.6. Operating Environment.............................................................................................................3 1.1.7. Assumptions and Dependencies................................................................................................3 1.2. External Interface Requirements......................................................................................................4 1.2.1. User Interfaces...........................................................................................................................4 1.2.2. Hardware Interfaces..................................................................................................................9 1.2.3. Software Interfaces....................................................................................................................9 ...........................................................................................................................................................10 1.2.4. Communications Interfaces.....................................................................................................10 ...........................................................................................................................................................10 1.3. Nonfunctional Requirements......................................................................................................10 1.3.1. Performance Requirements.....................................................................................................10 1.3.2. Safety Requirements................................................................................................................10 1.3.3. Security Requirements.............................................................................................................10 1.3.4. Software Quality Attributes.....................................................................................................11 Chapter 2 Literature Review......................................................................................................................12 2.1. Introduction....................................................................................................................................13 2.2. Related Works.................................................................................................................................13 2.2.1. Categorization of Existing Techniques/Works/Research..........................................................13 2.2.2. Limitations/Gaps within Existing Techniques/Works...............................................................13 2.3. Proposed Improvements in Existing Works....................................................................................13 2.4. Summary.........................................................................................................................................14 Chapter 3 System Design...........................................................................................................................15 3.1. Introduction................................................................................................................16 3.2. Design Considerations....................................................................................................................21 3.2.1. Assumptions.............................................................................................................................21 3.2.2. Constraints...............................................................................................................................21 3.2.3. Risks and Volatile Areas...........................................................................................................21 3.3. High Level Design............................................................................................................................22 3.3.1. View / Model Element 1…N.....................................................................................................22 3.4. User Interface Design......................................................................................................................24 Chapter 4 Implementation........................................................................................................................31 4.1. Discussion............................................................................................................32 4.2. Development Methodologies..............................................................................32 4.3. Implementation Tools and Technologies.............................................................32 4.4. Summary.............................................................................................................32 Chapter 5 Testing.......................................................................................................................................33 Chapter 6 Conclusions and Future Work...................................................................................................41 6.1. Contributions..................................................................................................................................42 6.1.1. Contribution 1..........................................................................................................................42 6.1.2. Contribution 2..........................................................................................................................42 6.2. Future Work....................................................................................................................................42 6.2.1. Improvements in the existing System......................................................................................42 References.................................................................................................................................................43 Appendices................................................................................................................................................44 Put in a reference number, you don’t have to enter it again while you’re jumping around the options. Our UX/UI team will then use the research for a better UX/UI design. Our Software programming department will then sort out an algorithm for a fast and flawless response of our UI. Our Interview team will evaluate the customer demands. 1.1.4. Product Scope As, there is no such features in any app now working in Pakistan, like this so it will make an obvious image in the market. Basically the purpose of this project is to facilitate the Customers and also other users by providing them online service all over the country. The things which are include in the online service are to provide the information about the services and also t for example if a user want to know the price of per unit price of electricity and also the user can register their compliant online by the mobile phones as well they can access it through online and there is no need to go the office of Electric company and also other purposes to convenience of users. The system assign every user who register himself in the Electric company with a unique I’d which will be the primary key So, it will increase the value in the market as the customers will be attracted towards it. 1.1.5. User Classes and Characteristics This software is designed to lessen the burden of front-desk staff. Users of the system should be able to retrieve billing information with the given number from the database. The system will support two types of user privileges, Customer, and Employee. Customers will have access to customer functions, and the employees will have access to both customer and management functions. User should be familiar with the terms like login, checking info, paying bills. 1.1.6. Operating Environment The product is basically digital so the operating environment will be on phones, desktop and tablets. The interaction will be done via opening an app icon on the customer side and employee side both will have different types of usability according to their needs. 1.1.7. Assumptions and Dependencies A power station is a technology based company most of our work is software or hardware based. The technology that is used for our this project is as follows 1: The research department will use a set accounting and research software mainly for requirements and data gathering. Cost: 1000 Dollars. 2: The UX/UI will conduct research and interviews based on user experience and the piece of software they will use Adobe Photoshop and Adobe XD. Cost: 200 dollar subscription. 3: The IT department will work on the functioning of the servers at the power station technologies headquarters; the total quantity of these server units are 50. 4: The IT department has issued an order of 10 server units each costing a 1000 dollars along with an update to the data centers. Cost: 50,000 dollars. 1.2. External Interface Requirements 1.2.1. User Interfaces It must be connected with the network, and the user can see the home page efficiently. Opening up, you see three options to check the load shedding schedule, billing information and calculate bills Load shedding Schedule: To check your load shedding schedule, simply put in the correct reference number. You’ll get details like your name, address, feeder and grid as well as an hour by hour breakdown of the load shedding schedule, there is also an option to generate a graph of the schedule. The Bill Estimator features options for domestic and commercial billing, and one-phase and three-phase meters. Put in the number of units. If there are any applicable exemptions to get a bill estimate with a breakdown. 1.2.2. Hardware Interfaces Hardware requirements for insurance on the internet will be the same for all. ● System unit router. ● All OS ● A browser which supports CGI, HTML & JavaScript. ● 2 GB ram. ● Communication interface: two parties are connected to each other by LAN/WAN for the communication purpose. 1.2.3. Software Interfaces ● Our System that we are proposing is software based so communication will be done via software, UI and server ● We have chosen Windows and Android operating systems for its best support and user-friendliness. ● To save the information we have chosen SQL database. ● Software is web based so it needs an internet connection. ● To implement the project we have chosen Vb.Net language for its more interactive support. . 1.2.4. Communications Interfaces This project supports all types of web browsers. We are using simple electronic forms for the theft forms, complaints from etc. Or users will communicate directly using power station numbers. Our communication team will reply as soon as they can. 1.3. Nonfunctional Requirements 1.3.1. Performance Requirements ● The System loading speed of content is around 1 seconds due to the new software. ● During workloads our servers have the capacity to maintain speed even when 100,000 users are present at one time. ● Once an error has occurred, the system should detect and display an error message ● .The customer should be able to view last year bills for tax and other purposes. Note 9, running Android 10. ● Responses to view information shall take no longer than 5 seconds to appear on the screen. 1.3.2. Safety Requirements  Our new and improved system is much more reliable than before due to the complaint of our customer care department we now have invested in server farm as well online cloud server which will be hosted by liquid sky our new Partner.  System use shall not cause any harm to human users. 1.3.3. Security Requirements ● The application should ensure the privacy of the users. ● The login system should also be robust where only authorized users can post and edit their own information. ● The security of our software is updated with the latest technologies blocking any malware, hack or Trojan attack. ● System will use a secured database. ● All communication between server data with clients shall be encrypted by using secure socket layer technology. 2.1. Introduction This Power Station System provides relevant Information that makes energy performance visible to various levels of an organization, enabling individuals and departments to plan, make decisions and take effective action to manage energy. The government has given power consumers the excess information regarding their billing and power supply situation in the area. Through the app, the users are able to view planned load shedding schedule and actual load- shedding. The users are able to view billing information and get duplicate bills. The users are able to get estimated bills through bill estimators by just entering consumed units. The users can know about the facility of net metering at their respective feeder by just entering the reference number. 2.2. Related Works 2.2.1. Categorization of Existing Techniques/Works/Research The software will function as a helping hand for power stations so that they can function as a helping hand for consumers in their issues and to assist them with this power information and services. The major improvement is mainly “time saving” the clients will not have to wait for their complaints or orders of parts to be approved. Due to our new data processing algorithm we have now moved from email notification to direct notifications to our department which is innovative and fast paced. The customer will have a different set of UI for understanding. Our AI algorithm will help connect the department to other departments of our company. Either that can be the Hardware department or the software department. 2.2.2. Limitations/Gaps within Existing Techniques/Works To conduct an analysis of importance time’s performance, data regarding customer satisfaction with various attributes are used to build a matrix, where the importance is on the Y-axis and the performance is shown by the X-axis. The Security of our software and data centers will be re updated with the latest technologies blocking of any malware, hack or Trojan attack. Our UX/UI team will modernize our usability system to make it more user friendly as possible. 2.3. Proposed Improvements in Existing Works ● Our UX/UI team will modernize our usability system to make it more user friendly as possible. 13 ● To conduct an analysis of importance time’s performance, data regarding customer satisfaction with various attributes are used to build a matrix, where the importance is on the Y-axis and the performance is shown by the X-axis. ● The Security of our software and data centers will be re updated with the latest technologies blocking of any malware, hack or Trojan attack. ● During workloads our servers will have the capacity to maintain speed even when 100,000 users are present at one time. 2.4. Summary We will further keep on studying the upcoming systems based on this and will explore some of the newer technologies which can be beneficial for the power station management system. It will help the online system to gain popularity and become famous. And make easy for people. It’s a nice first step and in the future, we’d like to see more detailed options like whether a particular bill has been paid or not, load shedding schedule based on area and cities as well as options to pay the bill within the app itself through partnership with Mobile payment solutions. A detailed bill estimator would also be a welcome addition. Chapter 3 System Design USE-case diagram: \ / Panes sate pod Deen a / a / ett Peres | Hardware Techiiian Zz Cre ETc) six manth Detail eee T Security Bere Panes etd Programmer Class Diagram: Reading lass ‘reading int “reading type: string -treaing_descriation: string +reading-name: string ‘reddReactng) +teoitReading ‘deleteteadingt +tscarcheeding} Customer cass Pesmission class “Permission i int +Petmission-roe i int “customer i nt ~easlomer name: sting customer mobile sting seustomer adress string ~eoustomer_pinstring “permission. string “sPetmission_modle: tring +Permission-discriavonsting “rAdgpermission) ~sdacustomer) ~eaitCustomert) deeteCustomet) *searehCustomer) +ecitpermission? +deletepermissiond ssearchpermission) Connections cass “Feonneetion id int ++connection-name: string ‘connection type string +tconnection_escripton:string ‘aceConaectionst) +ealtComnections) +eeleteConnectionst *searehConnections) Units aes Bills ase “Fie int unit ame: string unit type: string ‘unit eiscription: string User cass ‘addr +ealitUnits) +eleteUnist *searehUnits “bili -ileustomer id int bill type = sting “ll. escriotion string ‘bill umber: string oil recent string “userid int “turer role. int +user amessting ssuser ema string “user dob: date user adetesesting Role class “role ine Hole tive: sting +role-descrption sting ‘aco “edcUsen) ecitUsert) sdeeteser) searcher) eae ‘eeletekel) ++searchRolel debi) etl) sdeetesilst searches) ER Diagram: o 3.4. User Interface Design It must be connected with the network, and the user can see the home page efficiently. Opening up, you see three options to check the load shedding schedule, billing information and calculate bills Load shedding Schedule: To check your load shedding schedule, simply put in the correct reference number. Checking Billing Information: To check the billing information, the user puts his/her reference number and it’ll show you all bill details including a six month history. User can also generate a duplicate bill, but for that users redirected to a browser Getting a Bill Estimate: The Bill Estimator features options for domestic and commercial billing, and one-phase and three-phase meters. Put in the number of units. If there are any applicable exemptions to get a bill estimate with a breakdown. Units (Off peak) Units (Peak) Cost of electricity 5726 ‘TR-Surcharge NOTE The values shown abave are aperouimate values only Fuel peice adjustment wil be nchuced 0 tha bil in addition to above calculator SS & [om Chapter 5 Testing 5.1. Testing Techniques Employed for This Project We will test this project using different usability testing methods. 1) First we go to some public place and ask people to test this software in exchange for a small gift and note there feedback. 2) We also try lab usability test and give task to the participants. 3) The third phase will be done on the server and data hubs on the system in which the experienced members of our IT team will check and maintain the overall standard of our servers 5.2. Test Cases The quality assurance team used coding platform such as visual studio and sublime text as their platform for testing and the IT team issued their own software for assurance of the server system Load shedding Schedule: 34 Test case ID Test Scenario Test Steps Test Data Expected Results Actual Result SE01 Check load shedding schedule using valid Data 1.open software 2.click load shedding schedule tab 3.enter reference number 4.submit Refid=12345 6 it display load shedding schedule As Expected SE02 Check load shedding schedule using invalid Data .open software 2.click load shedding schedule tab 3.enter reference number 4.submit Refid=08410 4 Error wrong reference number As Expected Checking Billing Information: 35 5.3. Test Results our project is ready now all the rest result are just like we want out it team will double check everything and all our test result is As Expected now it’s the time to publish it and take some advantage. The quality assurance team used coding platform such as visual studio and sublime text as their platform for testing and the IT team issued their own software for assurance of the server system.. 38 5.4. Summary After successfully build our software we go for testing we will test using automatic and manual method First we go to some public place and ask people to test this software in exchange for a small gift and note there feedback. We also try lab usability test and give task to the participants. The third phase will be done on the server and data hubs on the system in which the experienced members of our IT team will check and maintain the overall standard of our servers. We test different cases with result as we expected. 40 References Systems Analysis and Design 5th Edition Shelly Cashman system analysis and design 9th Edition PDF https://www.guru99.com https://app.diagrams.net https://www.tutorialspoint.com https://www.javatpoint.com https://www.geeksforgeeks.org https://www.lucidchart.com https://www.visual-paradigm.com 43 Appendices Appendix A: Plagiarism Report This should be your Plagiarism Report!! Appendix B: Glossary Appendix C: Analysis Models Appendix D: To Be Determined List 44