INSY Analysis and Design Object-Oriented Approach with UML

Question: Discuss about the INSY Analysis and Design for Object-Oriented Approach with UML? Answer: Introduction about the problem domain: In this project, the analyst has chosen the Red Hat Inc. as a case study. The problem domain is to implement an information system to incorporate the customers and employees. The information system will be designed according to the Bell-LaPaula model to confirm the security level of the documents. The Red Hat Inc. is a multinational software corporation to provide the open source software platform to the clients (Meeker, 2012). The company introduces a project named fedora in this context. Fedora project is a subsystem to boost the repeated innovation on the open source software domain. The main part of the project has chosen the Linux platform for the implementation. The problem domain is to design a quality assurance and client support model in the information system. The problem domain is to be designed on the system request model. System Request: The system request model is designed as following the given table format. Element Description Examples Project sponsor The persons initiating the project and serves the primary point of the contract for the project on the business side The Red Hat Inc. organization has several members (approximately 7300) in the department, CEO, It manager and supporting committee. Business model The business reason for the initialization for the system Implement fedora project with the improvement of the sales, market share, information access. Business requirements The business capabilities for the system will be provided The information system will provide online access to the clients and employees. Improve the product search capabilities along with interactive modules design in the information system. Business value This value redefines the benefits of the system Total revenue US$ 1.534 billion, operating outcome US$ 232.29 million, net income US$ 178.29 million, total assets US$ 3.107 billion and total equity US$ 1.551 billion. Special issues or constraints The issues that are relevant in the implementation and beneficial in the approval committee Top level security and firewall implementation is needed in the open-source software and platform development. Feasibility Analysis: Serial no. Feasibility types 1 Technical feasibility The building feasibility of the project is dependent on the following criteria: The application familiarity reduces design risk. The technology familiarity reduces technical risks. Size of the project for instance large projects are more risky to implement. Checking of compatibility depends on the existing technology. 2 Economic feasibility The development cost is the main concern in the feasibility study. Annual operating cost, benefits and intangible costs management is also a part of economic feasibility. 3 Organizational feasibility The main concern in this feasibility analysis is the development issue of organizational effectiveness. The project is whether aligned or not with the profits and the strategies of business. Requirements Definition: Requirement type Description 1. Functional requirements This is the main requirement of the organization including the functionality of the software 1.1.Software management The software requirement of the fedora project is the main deliverable here. 2. Nonfunctional requirements Another requirement is the non-functional type including the operational, performance and security management. 2.1.Operational requirement The feasibility and requirement of hardware requirement is needed for better operation ability. 2.2.Performance requirement The performance requirement is the analysis of the sales target fulfillment in the business. 2.3.Security management The integration of security measures to be introduced in this part. 2.4.Cultural and political management The cultural and political requirement is the policy adoption of equipment of another organization and company to fulfill the performance requirements. Analysis Modeling Part A: Activity Diagram: Part B: Use Cases Diagram: Part C: Use Cases Descriptions: Here the use case diagram shows the operation between client end and employee end. Client uses the products, services, technologies, modification, features and tools of the portal. The employee gives the service, products after validated by the admin. Admin is the main entity of validation to the login details and modification of any products (Dennis et al. 2015). The employee according to the clients frequent demand updates the technological aspects to the portal. Class Diagram: The main classes are displayed with the data types and relevant methods with the proper return types. The admin class inherits the modification interface with getID() and getModi() method. The employee class inherits the interfaces named products and services with ID generation method with operation setup method (BU and LI, 2012). The employee and admin classes are the main operating part of the class diagram. Client is with getProduct(), getService(), getrestration() method that are implemented by the employees and admins. Sequence Diagram: The entire operation is displayed to the sequence diagram from the clients activation panel to the admin and employee class. The other classes are the product and services for the other methods to be executed in the orderly manner to the sequence diagram (Drusinsky, 2011). Design Modeling Part A: Final Class Diagram: This is the final class diagram of customer portal with the help of the previous class diagram. The final class diagram is designed with different classes with separate functionality (Strembeck and Mendling, 2011). The figure defines the data types and the methods. Package Diagram: The main package and the subpart of them are designed according to the Red Hat Inc. and Fedora project. The Net Beans platform is used to implement the packages in this context. All the sub packages are important for open source software development (Gomaa, 2011). Part C: Database Design: A brief structure of database design is displayed here. The client details are saved in a database named client database (Budgen et al. 2011). The services and product are stored in respective database according to their ID and frequency of usage. According to the client details the database is updated and modified. Part D: Data Access and Manipulation Design: The client gets login ID and password from admin by registering the website with information. Client fills up the information panel; the admin updates the database with details. After updating the database he admin send an ID and password to the client. The client then performs log-in with the ID and password (Sequeda et al. 2011). Admin checks the ID and password with the database and gives the validation of the portal. Client requests for a product and admin replies if the product is in the store. Client then gets the product otherwise; the client gets an error message. The employee logs in with valid ID and password given previously from the admin panel. Employee provides the product to the admin and the admin stores the product to the database. Admin then allocates the products and service according to the clients request. Reference list: Dennis, A., Wixom, B. H., and Tegarden, D. (2015).Systems analysis and design: An object-oriented approach with UML. John Wiley Sons. BU, X. X., LI, Y. Z. (2012). The Development of The Enterprise Logistics Management Information System based on UML.International Journal of Advancements in Computing Technology,4(16). Drusinsky, D. (2011).Modeling and verification using UML statecharts: a working guide to reactive system design, Runtime Monitoring and Execution-based Model Checking. Newnes. Strembeck, M., Mendling, J. (2011). Modeling process-related RBAC models with extended UML activity models.Information and Software Technology,53(5), 456-483. Gomaa, H. (2011).Software modeling and design: UML, use cases, patterns, and software architectures. Cambridge University Press. Budgen, D., Burn, A. J., Brereton, O. P., Kitchenham, B. A., Pretorius, R. (2011). Empirical evidence about the UML: a systematic literature review.Software: Practice and Experience,41(4), 363-392. Sequeda, J. F., Tirmizi, S. H., Corcho, O., Miranker, D. P. (2011). Survey of directly mapping sql databases to the semantic web.The Knowledge Engineering Review,26(04), 445-486. www.redhat.com, (2015). Red Hat Inc. [online] Available at: https://www.redhat.com/en [Accessed on 16 Sep 2015]