Rendering the Sub-Architecture - Term Paper Example

System Architecture Assignment 1 Part1--Abstract Name:Yixin Sun (Martin) ID:110077417 Email ID: sunyy042 Abstract We are required to build system architecture to display furniture choice for their house in the use of the SAR System for client. We put the system into several parts: 1. User Interface, 2. Implementation, 3. Data Store and Tracking, 4. Rendering. Also, there are four tiered approach about layered style and client/server architecture: User interface-->Control level-->Processing level-->Hardware(from Highest to lowest). My sub-architecture is about rendering, which means the projectors display picture or video(like real world objects) to the customer. Rendering system will do both the virtualization on the tablet device to the customer (3D view in the house). The rendering is necessary because the material information and light and shadow information are calculated independently, we need to put them together into pixel information – Rendering. These pieces of information will be integrated into the plane of graphics or video. Rendering system needs to decide the position of an furniture. For example, which furniture in the front or behind, which furniture will be obscured, etc. Also, light source and color setting are important parts in the rendering system. Interacts with User interface: The customer can change something in the house such as the position of the furniture and color. For example, the rendering system will change the color in the real time on the tablet screen if a customer chooses a new color on the tablet devices. Interacts with Implementation: Set all furniture in the house and manage the machine to process the rendering. Interacts with Tracking and Data store: Tracking system is an integral part of the rendering system. The tracking system need to find the correct coordinates in the real time of the physical objects so that the rendering system Will present a good effect, and then it will be used to projected rendering for every customer. The rendering system also needs Data store’s supporting, because the 3D models of the furniture are stored. The modifications are allowed for the client to change its properties such as colors, shapes, materials, etc. Table of Contents Abstract 2 The stakeholders for rendering sub-architecture 5 Rendering the sub-architecture 6 The limitations of rendering the sub-architecture 10 A summary of sub-architecture 12 References 14 The stakeholders for rendering sub-architecture The stake holders of rendering sub-architecture vary from customers, end users, businesses, domain experts and developers. End users are individuals who use the architecture for various purposes. Most users of rendering architecture are individuals interested in making 3D models of furniture’s and they need the images to have its properties change in terms of shape and colors. The end users are critical in any product because are the individuals to determine the importance of the product. They can be employees of architecture of fans, designing fans, students, colleges and any other person who is interested in 3D models. Customers- for continuing success in business customers are important for the sub-architecture and will need to be kept satisfied. As long as the customer receive the rendering sub-architecture system that is satisfactory and meets their needs their will be not be any cause for alarm. The customer is different from end user. Customers and end users are both important; however end user uses the product while the customer is a middle man. Domain experts are individuals who provide necessary knowledge in designing rendering sub-architecture. These individuals use their knowledge to design their architecture that will meet the purposes of institution. They are problem solvers. Testers and developers- these are experts developed in developing and testing of the architecture that will be used in the running of the organization. They will ensure there is proper debugging of the system. Therefore these are individuals developed in technical visibility and ensure the release of a reliable product in the market. Rendering the sub-architecture Rendering sub-architecture is a system that will do virtualization on tablet device to produce 3D models of various objects including household furniture. It will have the ability to change image information such as pixel information, light, color, and shape. It will integrate information in a graphic or video to fill the needs of an individual. Then this system will be able to send the information to a storage device where it will be stored and will be accessed by customers whenever they need them, the sub-system will help in projecting the images on the screen. In order to understand the working principle of Rendering sub-architecture and possible areas of improvement, it is important to have an in-depth understanding its instrumentation. Most of the features depend on the software supplied by the manufacturer. However, most hardware features of rendering sub-architecture are similar and have the same working principles. A typical rendering sub-architecture is made up of image/data acquisition system and processing systems. A block diagram and a schematic diagram of a typical system are shown in figure above. Another important component is the tablet that is used to control the orientation and functionality of the other rendering sub-architecture. The operator selects certain furniture and parameters like geometrical parameters and other configurations on the table. This gives the operator the ability to quickly vary the amplitude and waveform of taking the image. The following diagram presents the diagram for processing, managing, presentation and storage of the data in the database. It is a four tier. The ipad/tablet device that the client is able to make selections from and project the chosen products to the physical room setup. This level of abstraction is not concerned with how the system works. Control Level: this involves Terminal Computer + Back end matrix and servers for Rendering and Maintenance and Tracking/Camera Translation. Processing Level: this where the rendering and tracking systems in software form itergrate. How all of the information is calculated and then pushed up to be presented at the user level. Database tier – this where the data is stored. Rendering has interaction with the Data Store as this is where the 3D models of the furniture is stored as well as its properties and the modifications allowed for the client to change its properties (materials, colors, shapes, etc). UI client chooses the wanted product. Data Store interacts with rendering. Rendering gets info and can modify and displays. Hardware - All of the hardware level devices such as the physical objects in the room, tracking objects, projectors, cameras, and physical adjustable walls. From diagram above layered architecture diagram it can be noted that each layer interacts with next layer, the interaction is through the domain the software is related to, and uses layers beneath to fulfill some task. The focus of this article is on the Presentation Layer, its integration with Knockout and the connection between the Presentation and the Application layer. From the diagram above it can be noted that Rendering system will do both the virtualization on the tablet device. Rendering on the 3D objects which will later be projected onto the physical objects in the room. Once a client chooses a new color on the tablet devices' UI, the Rendering System will change the properties in real time and on the tablet screen. Then Implementation manages the machines that handle the Rendering processing. The tracking system is an integral part of the rendering system. The rendering system relies on the tracking system to have the correct coordinates in real time of the physical objects that will later be used to have the projected renderings as per the client's request. Rendering has interaction with the Data Store as this is where the 3D models of the furniture is stored as well as its properties and the modifications allowed for the client to change its properties (materials, colours, shapes, etc). The limitations of rendering the sub-architecture Theoretically rendering the sub-architecture can achieve extremely high quality 3D image. In essence, a rendering sub-architecture has not reached its true potential due to the presence of some crucial limitations. These limitations include the relatively small screen of the device due to which the input mechanism has become complicated. Therefore, it can be said that although rendering sub-architecture have greatly enhanced the efficiency of work, there is still the repercussion of not being user-friendly. The rendering sub-architecture are seemingly more difficult to use than the tablets due to their small screen size. Besides, many applications do not work properly due to the reduced size of the screen. Another important limitation worth considering is the small battery life. The limited life of the battery also restricts the users from using the applications after a certain period of time. This affects the effectiveness of the tablet devices. Moreover, there are certain technical restrictions associated with the tablet based applications. It is nearly impossible to have the signals and wide diffusion of tablet based applications. The major reasons are the low bandwidth and limited coverage of the tablet companies. The final issue is that of security of the tablet applications. Since the whole process involves wireless communications, tablet based applications are considered insecure by the end-users and there is the threat of data breach. This makes many of the potential users reluctant to rely on the tablet based applications The rendering the sub-architecture does empower the users but eliminates creativity. Users are given the freedom to modify and/or enhance the image contents for certain purposes thus affecting tracking system. It requires an additional feature that may not be relevant to the clients that it serves. On the other hand, users have the liberty to determine for themselves the features and enhancements they deem necessary. In terms of rendering the sub-architecture features, networking is another key parameter. Monitoring is a fundamental operation that must be met by the rendering the sub-architecture component in running a system. In connection, it offers solutions to various network monitoring and have strong network that periodically update the contents of the sub-architecture. Any type of sub-architecture has specific requirements in terms of deployment and maintenance. Rendering sub-architecture is more difficult to operate. Today, deploying sub-architecture has significantly changed with more ease. Users of sub-architecture are at an advantage when it comes to license management. Users are allowed to install limitless copies whereas those of the closed source users are given certain limitations. Additionally, users that utilize open source software would not encounter any legal issues as the copying or sharing of contents in such software does not need any prior authorizations. Cost is an important aspect that it requires good investment. The most relevant aspect pertains to the total cost of ownership (TCO); hence, a product that has the lower TCO is often the one more in demand, pertaining to the sub-architecture. A summary of sub-architecture To begin with, the rendering sub-architecture will be divided on the basis of whether they were system administrators or end user. Those that fall under the rendering sub-architecture administrator are charged with the responsibility of technical implementation, whilst the end user on the other hand are exempted from the any kind of technical work that is related to the use of system. Thus, the activities of end user involve analyzing and choosing the data/images sorted and gathered by the systems, by utilizing the user interface. Technical administrator have the duty and responsibility of technically implementing the tool as well as being responsible for applying the knowledge of the organization’s environment in the tool. The purpose of the rendering sub-architecture is to produce a high strength, uniform and quality data. rendering sub-architecture are not developed in vacuum, rather they are created to target a specific audience, an audience which appreciates the specific application and demands a necessity. These applications are directed towards real people in a real world. There are many considerations which must be taken into account when planning the specific application. There are different types of people out there, belonging to different classes, age-groups, ethnicities and political inclinations. The applications designed must cater to the target group of customer. All these considerations must be undertaken when planning the new application. The function of the app and its design should streamline with the requirements of the target group of customers. Moreover, the organization must set an objective to achieve before designing a final application. The application must be designed to perform a specific set of tasks. Even though it is possible to design an application which is capable of performing various tasks simultaneously, it will only serve to confuse the customer and he won’t be able to attribute a single value to the application. Therefore, the application must serve to achieve a single objective. Following the setting of an objective, the organization must have gauging method to measure success of the application it launches. This would mean that the organization must possess an accurate and efficient system for measuring the effectiveness of the application. These measurement tools can include the scoring board or metrics. An effective metric system would enable the test of application on regular basis. Companies must continuously strive to know the changing trends in the target market and develop their product accordingly. The rendering sub-architecture today, is infamously unreliable and this lets down the core value as claimed by the applications. The core value that the tablet applications are delivering is the availability of services of that application anywhere on the move. Due to the weak bandwidth of the internet, this core value is not fulfilled which strongly affects the business of tablet applications. In truth, the tablet based applications are dependent of the rendering sub-architecture for its working and it has greatly crippled the essence of a tablet application. This brings us to the requirement of tablet commerce clients which will enable the effectiveness of tablet applications. The tablet clients will serve to deal with the tablet applications locally and enable the applications to work even when the internet service is not available. These tablet applications would require an advance platform for data storage and management tools. It is important that the application is run on the right tablet database so as to get maximum availability and compatibility in this diverse market. It is important to analyze the requirements of the applications if they are to operate in the absence of an internet. The first one is the storage and management of application data on the device. The preferred platform only provides a limited space for the application to store data on the device. The biggest contributing factor in the availability of tablet applications is the selection of right tablet database. It is a complex decision for business to select the right tablet database product. Usually, the databases are embedded into the client application, there are times when the firms have to pay royalties for all the products that they have bought and distributed. Therefore, the firms must negotiate a good contract so as to get the maximum availability of their applications. In addition, there is the issue of vendor lock-in door to the synchronization problems associated with the product. As a consequence, the developers of the applications must consider the technical merits of the product as well as the overall reliability and reputation of the vendor. References Keefe, D., and Isenberg, T. 2013. Reimagining the scientific visualization interaction paradigm. Computer 46, 5 (May), 51–57. Kirk, D. & Hwu, W. 2014. Programming Massively Parallel Processors A Hands-On Approach Marner, MR, Smith, RT, Porter, SR., Broecker, MM., Close, B. & Thomas, B. H., 2011. "Large Scale Spatial Augmented Reality for Design and Prototyping," Handbook of Augmented Reality, pp. 231-254, 2011. Michael J. Doyle, Colin Fowler, and Michael Manzke. 2013. A hardware unit for fast SAH-optimised BVH construction. ACM transactions on Graphics (SIGGRAPH ’13) 32, 4, Article 139 (July 2013), 10 pages. Pharr, M., 2005. GPU Gems2: Programming techniques for high performance graphics and general-purpose computation. Reading, MA: Addison-Wesley Qiming Hou, Xin Sun, Kun Zhou, Christian Lauterbach, and Dinesh Manocha. 2011. Memory-Scalable GPU Spatial Hierarchy Construction. IEEE Transactions on Visualization and Computer Graphics 17, 3 (2011), 466–474. Rodr´ıguez, M. B., Agus, M, Marton F. & Enrico Gobbetti, E., 2014. HuMoRS: Huge models Mobile Rendering System Stratton,J.A.,Stone,S.S.,& Hwu,W.W.M( 2008). CUDA (2008) An Efficient Implementation of CUDA Kernels for Multi-CoreCPUs- The 21st International Workshop on Languages and Compilers for Parallel Computing, July 30_31, Canada,2008.AlsoavailableasLectureNotesin Computer Science, 2008. Tan, B., et al. 2001. Web information monitoring: an analysis of Web page updates. Online Information Review, 25(1), 6-18. Thomas, B. H. Von Itzstein, G. S., Vernik, R., Porter, S. Marner, MR, Smith,R.T., Broecker, M., Close, B., Walker, S., Pickersgill, S., Kelly, S. & Schumacher, P., 2011. "Spatial augmented reality support for design of complex physical environments," in Pervasive Computing and Communications Workshops (PERCOM Workshops), 2011 IEEE International Conference Sssssssssss Bbbbbb Read More