focus on functional capability development | My Assignment Tutor

Assignment 2 has focus on functional capability development, function design verification.All assignments must be submitted via Canvas assignment submission link for checking by Turnitin system.  All submissions must obtain a similarity index of 20% or below in order to be qualified for assessment.  In that case, zero mark is recorded as default.  Submitted assignments with similarity index higher than 20% will be requested to revise and re-submit until the similarity index is 20% or below. Theme: In Assignment 1, you were asked to be innovative and propose high level conceptual blocks that can make up the integrated “100% Renewable Victoria 2030” system to satisfy user needs, i.e. concepts of operation. This situation is similar to the customer asking as many vendors as possible ideas of designing and implementing the system. Any company can propose new ideas to attract attention and opportunities. However, once the ideas are filtered, it is common practice that some companies enter a joint venture so that they can combine expertise and capacity of several companies to build a better engineering system for the customer. In this case, the partner companies will need to discuss the best selection in the interest of the customer. You will need to discuss the best option for the “customer” and consolidate to a single “100% Renewable Victoria 2030” proposal. From individuals’ perspective, there will be “give-and-take” on system functions. However, if everyone in the group has the same aim, i.e. develop a system that has high integrity, this discussion should be rather straight forward. Once the group reaches consensus of what to produce, the system will enter into detail design stage of the systems engineering V lifecycle. You should provide a professional overview of the system, concepts of operation, user requirements, system requirements as the basis for understanding how the system will be put together. Based on the professional overview, a functional hierarchy of the new system should be introduced, providing a bird’s eye view of the system to be proposed.  With the functional hierarchy in place, expanding a high level design into detail design requires modelling tools. The modelling tools are most appropriate for this work. You are expected to decompose your high level functions to lower levels so that the functions can be implemented more readily, or suitable commercial-off-the-shelf components can be sourced quickly. The “Renewable Victoria 2030” system can be a complex system. It is natural that you will find many high level functions. In order to balance your workload, you are not expected to expand every function but a reasonable number of functions should be elaborated adequately so that the overall system can be demonstrated to satisfy all the key user requirements. Once the detail designs are created, synthesising these designs into a physical architecture can be challenging. The process of system synthesis depends largely on the experience of the system design team, however, some heuristic rules are provided in this course to help you make the right decisions. In particular, you should pay attention to the maturity measures of the technologies that you are going to adapt in the system. Any technology that is at a level lower than technology readiness level 9 are likely to require further researches and will be costly and delay the project due to immaturity of the technology in mission situation. The purpose of systems engineering is to develop the best system for the client. A large scale complex system must have a lot of different design options that can fulfil the basic user requirements. However, the systems engineer should strive to deliver an optimum solution. Techniques for considering different options by trading off some less important features help the design team to find an optimum solution so the client can feel they are receiving the best value for their money. In arriving at your answer to Assignment 2, you should include a trade-offs process for one of your key components/subsystems. Like Assignment 1, to practice the essence of Systems Engineering, for each of the functions that you have expanded into subsystems, you need to develop the subsystem verification plan. All subsystems must be tested before assembling into the final system.  The number of subsystem test plans would be equivalent to the number of functions that you have expanded in this assignment.  This means when you test the subsystems, they are not working together in the total system setting. They have to be tested separately. Your subsystem test plans are expected to show that the subsystem performance can be measured independently. Please note that system validation plan in Assignment 1 is to test the system as an integrated whole of all subsystems and should demonstrate satisfaction of user requirements, hence you have one system validation plan but you will have as many (sub)system verification plans as the number of function. This level of testing is usually done in a laboratory or tightly controlled environment with only that subsystem under test, i.e. the other parts of the overall “Renewable Victoria 2030” system are still being manufactured and not ready to be assembled. Given the complexity of this proposal, there is NO WORD OR PAGE LIMIT to this document.  However, the formatting, i.e. A4 size, 12 font Times New Roman, single line spacing still apply.


Leave a Reply

Your email address will not be published. Required fields are marked *