Object Oriented Application Development

Question: Describe different types of A/D methodologies and modelling techniques. Understand and apply concepts and principles of object oriented technology. Analyse problems associated with modelling and designing Information Systems. Apply object-oriented methods in the design, modelling and evaluation of computer-based applications. Design and model a simple information system using object oriented models and tools. Work effectively with UML and RAD tools to develop prototype models and software for a given scenario. Answer: Introduction The aim of this report is to understand the concepts of OOA/D or Object Oriented Application Development using object oriented technologies, terminologies etc. The report will help to understand the application of UML or Unified modelling Language in case of OOA/D. There will be application of UML for system requirement analysis, use case modelling, class modeling and interaction diagram like sequence diagram. Case Study M S Company want to have their updated and improves sales information system that will be integrated to the accounting system. The system will be used as a desktop application installed on the computers of the employees. The important aspects of the system are, Buyer must be registered to the system. A registered buyer will be able to create username and password for the buyer account. The buyer must be able to browse items. The buyer must be able to navigate for finding an item. The buyer must be able to place order for one or more items. The buyer must be able to add credit card to the system. The system must be able to store the details of the credit card of the buyer for future payments. The system must be able to export transaction data into the account system. The system must be able to import data from bank and account system. The system must be able to track the credit card purchases. The system must be able to generate invoices timely. The system must be able to track the due credits from bank. The system must be able to allow access and view to the purchase details based on the category and user ID of the user. The requirements of the system are, It must be able to export the transactional data into the accounting system so that the issues with double keying process is minimized. Data security must be there. Authorization using username and passwords must be supported by the system. Users can see the purchase data based on the user categories and IDs. Transactional and operational data from accounting systems and banks must be done to reduce redundancy in the process. Payment of invoices must be reconciled timely, The purchases through credit cards must be tracked. Records about the due credits from the bank, must be maintained. Use Case diagram The use case diagram for the system is, Individual use case descriptions The use case description of the use cases are, Use Case Actors Associations Extension Inclusion Register into System Buyer Buyer registers into the sales information system No Allocate username and password Browse item Buyer A registered buyer will be able to browse items. No No Find item Buyer A registered buyer will be able to navigate through the system for finding an item. See Purchase History Buyer A registered user will request to see purchase history. The system will authenticate the user and grant the permission. No Authenticate user Place order Buyer A registered use can place order for an item. No No Add Credit card Buyer The register user can make payment by adding a new credit card. It will let the user to store the credit card details for future use. Store credit card No Track credit card purchases system The system will track the credit card purchases of the users. No No Export transaction data Accounts system The system will export transaction data to accounts system No No Generate invoice System The system will generate invoice. No No Import bank tables Bank The system will import table data from bank. No No Check dues Bank The system will check the dues from the bank. No No Class diagram The class diagram of the sales information system is, Code Generation Sequence diagram The sequence diagram is, Working prototype Evaluation and Conclusion In this report OOAD methodology has been used. OOAD is a partial software development lifecycle, here the system is decomposed based on the concept of objects. M S Company was interested in developing a suitable sales information system for their business. OOAD methodology is selected as it is suitable for the development of the information system. This methodology has helped to understand the real world entities related to the information system. Based on the interactions of those entities and the system, the modules of the information system like the payment module, purchase module, inventory management module etc. can be developed from these entities and the core functions of the modules. OOAD methodology supports modeling and design the system from different perspective. Hence, it helps in better understanding of the system so that OO principles like polymorphism, reusability etc. can be implemented in the system. The decomposition of the system into multiple modules and objects help in implementation of parallelism. That in turns makes the application development faster. In this report, UML has been used for system analysis and design based on OOAD principles. UML use case modeling has been used to realize different functions of the system and how the system interacts with different types of external users. Then the class diagram shows different entities of real world being modeled by the system.(Dennis, et al., 2011) Each class has own set of attributes and operations. Then the data entity diagram helps to understand the entities to be modeled in the database supporting the sales information system. There are information about the interaction of the system, objects and the users through the classes and operations identified for the application. Those are represented by the interaction diagram of sequence diagram.(Shelly Rosenblatt, 2011) References Ambler, S. W., 2005. The Elements of UML(TM) 2.0 Style. s.l.:Cambridge University Press. Dennis, A., Wixom, B. H. Tegarden, D., 2011. Systems Analysis and Design with UML 2.0. s.l.:John Wiley Sons, Inc.. Larman, C., 2012. Applying Uml And Patterns. s.l.:Pearson . Satzinger, J. W., Jackson, R. B. Burd, S. D., 2015. Systems Analysis and Design in a Changing World. s.l.:Cengage Learning. Shelly, G. Rosenblatt, H. J., 2011. Systems Analysis and Design. 9th ed. s.l.:Cengage Learning.