System Engineering Assignment On Design and Function Analysis

Posted on the 21 January 2020 by Jaxon Smith @jaxonsmith32

Introduction:
The main objective of this system engineering assignment is to transform the interface, functionality and some other demands, which is identified by the process of requirement analysis into the function description of the system. This is used to manage and monitor the activity of the synthesis design. The function arrangements and decomposition of the function from a high level to a low level and performance of duty can define the above thing. The analysis of the timeline and the flow block diagram is included in the tools, which is used in this (Chapman, 2018). The result of the design synthesis is the solution of the requirements, which is correctly done by the functional analysis and allocation. The function is used to identify the objective of the system. The elements can derive them, or they might be explicitly described. The function is the central part of designing the operation of any organization.

The process overview of the functional analysis and allocation:
From the requirements of the higher level, the functionality and the performance of the elements are developed in any level of the system. To define the function of the lower level and requirement of the function, successively is repeated by the functional analysis and allocation (Bahr, 2018). To provide the verification of the system and the design of the system, the requirements of the system is allocated, and this is used to support the integrated design of the system. Here the process of design is as follows.

  • At first, make the function according to the system and then decompose the function into small sub function.
  • The requirement performance of the high level is translated into the design criteria's performance. This is describing the performance of the function.
  • Internal and external interfaces of the function are identified
  • All characteristics of the function are determined and co-operated them into the process of function analysis and allocation.
  • Examine the life cycle of the function and include some primary function, which is needed for the project.
  • Arrange the alternative function to fulfil the requirements and again revise the whole process to solve the problem with the functional risk.
  • Inputs: the input of the functional analyzing and allocation is the result of the analysis of the requirements process.
    Outputs: the outputs are the details of function architecture and the details of the architecture.
    Supporting process: some models like QFD, diagram of block flow, IDEF, chart of N2 etc. some organizational inbuilt process is used.

The function analysis approaches/ methods:
The function is called the interaction between the input and output. In another word, the function is called the duty of the product that it is capable of doing that. To solve the design problem, some service is used, and function is made according to the design of the system (Chapman, 2018). The function does not depend upon the solution, and it consists of the input and output, which is used to solve any design problem of the system. The function establishes the relationship between the input and output. There are some methodologies of the function analysis in system engineering. The first step of the method is to identify the physical components from the starting point or the top level. The identifying product is used in future to produce the future product. The analysis of function is applied in every level of the design, sub level and the system of the system. The total methodology of the function analysis process is shown in the Fig1of this system engineering assignment. It also shows the tasks, relationship between each job and lastly the input and output of the job. The functions of the functional analysis are listed below:

  • Tree of the function
  • Matrix of the function components
  • Tree of product
  • Relationship matrix
  • Block diagram of function

Fig1: input out relationship using function

(source: Mensah, Kakaï and Seifert, 2016)

The function tree is generated at the first step of the analysis process of the function based on the requirements of the system (Garvey, Book and Covert, 2016). After generating the functional tree, the component matrix of the function is created and is identified the basic component for the product tree. After identifying the necessary ingredients, the product tree and the relation or connection matrix both are built successfully. Now with the help of the product tree and the relation matrix, the final functional block diagram can be drawn. Useful tree, a matrix of the function and the tree of the product is the core part of the functional analysis. Mainly, with the help of identified components and the requirement the future product will be generated. To determine the future product, product tree is used (Morse et al., 2018.). When the connection and relationship between each task is identified, then the architecture of the future product is wholly done. The primary output of the function analysis process is the function tree and the tree of product. The secondary production of the functional analysis is the diagram of the functional block.

The function allocation approaches/ methods:
In the allocation of the function approach, the main thing is to use the FAR approach the output of the distribution of the function is generated, and a use case model shows the actual output using this FAR approach (McKean, 2019). The use case model is used to define all use case, which is analyzed from the system. FAR produces the function breaks down structure, description of the functional architecture and the sheet of requirements allocation. The input of the activity of flow down is the FAD and RAS. The information now changes as the output of the different system's requirement specification.

The function breaks down structure: the functional break down structure provides the complete functionality of the system and the complete overview. The system provided a group of function is included in the functional break down structure. This added function is the primary function served by the requirements of the system.

Survey of use case model: the main objective of this system engineering assignment is to give the whole concept of the every use case, which is present in the model.

Specification of the use case: the specification consists of the precondition, postcondition and the context information. This information is the introduction of the specification. It defines the black box scenario that means the relationship between the system and the user is described by the use case specification (Mensah, Kakaï and Seifert, 2016). Use case model shows the fragments of scenario and by using this scenario reach to the scene of success. The primary step is to identify the proper position of situation based on the pieces. Fragments are inserted place, which is suitable for the fragments. The result of the fragment may be generating a success scenario, or it closes the use case. The following steps are the scenario of the black box.

Step1: when the customer provides a general id, then the use case is started. After accepting a public id from the customer, a unique identifier is requested from the customer. It requires 1 sec response time to do this step.

Step2: in step 2, the customer or user provides the unique id, and the system accepts the id. The system creates a platform to check the validity of the general id and the unique id. The maximum response time of this step is 0.5sec

Step3: if the generated identifier is valid, the system provides services as per the requirements and then use case is finished. It also requires 0.5sec.

If the unique id is not valid, then the system gives an error message to the customer and suggests generating a new unique identifier. Then the use case again continues with the normal process.

If both the unique id and general id are invalid, then the system generates some error message after accepting the public id.

Description of functional architecture: the technical architecture description includes the realization of all use case of the system (Smith et al.,2019). The collaboration of all the subsystem and representation of how they solve a specific task with excellent communication is called the realization of the use case. In the other hand, it is known as white box description of the use case. Each black box steps of the use case is decomposed into several numbers of white box steps. Here discuss the step of the white box where shown the collaboration of every subsystem.

After accepting the authentication result from the validation of the unique id then the card reader captures the general id (Gore, 2016). If there is any error, then transaction control gives an error message with the help of output devices. Then the error message is presented to the customer by the output devices.

The sheet of requirements allocation: there are two purposes for the requirements allocation sheet. The first one is that it manages the overall system between the use case and the needs of the system. The second one is that it is used to allocate some not suitable requirements for the use case. It is tough for the use case to handle the conditions, which is non-functional.

Requirements of the subsystem: the primary responsibility is to specify all elements of the subsystem. This is the primary work for the domain engineers. The system engineer is used to ensure that the result of the requirements of the sub system is presented in the original order and ensure their allocation. More than one subsystem requirements are resulted in the analysis of FAD and RAS.

Conclusion
It is concluded from this system engineering assignment that the function analysis and allocation is an essential part of the system engineering. With the help function, the designing of any system is possible. The service creates some relationship between the input and output. To solve the design problem, some function is used and function is made according to the design of the system. The function does not depend upon the solution, and it consists of the input and output, which is used to solve any design problem of the system (Krarti, 2016).To develop the design of the system the function is designed. According to the behaviour of the system design, the function is generated. Use case model shows the fragments of scenario and by using this scenario reach to the scene of success. The collaboration of all the subsystem and representation of how they solve a specific task with excellent communication is called the realization of the use case. The first part of the system engineering assignment shows the method of function analysis. Here using some steps like the functional tree, requirements tree, tree of the product, then making the relationship matrix for this and lastly, draw a function block diagram to analyze the function. Then the step is to discuss the allocation method of the service. In this step use some use case model, function break down structure, specification of use case model, black box description of use case, white box description of use case, then make functional architecture description maintain the allocation sheet and lastly discuss the requirements of the subsystem. Here to generate the success scenario, many fragments are used. The best performance is managed by the FAR approach based on the needs of the company. This study is also used in system engineering, software engineering and electrical engineering. This is used in some pilot project in future (Hui et al., 2015). This will help to describe all the functionality of the system. But there may be a problem of identifying the best possible use case and make all types of description of the use case. Here methodological support is necessary for this approach. So functional analysis is starting with identifying the physical components of the high level and then decomposed them into the lower level. After completing the decomposition of the requirements of the function, individual allocation is performed at the lower level. Then showing the allocation process of the lower level then combined all the result of that level and passes it to the higher level to produce the final scenario and then the improved design of the system is done. In other word, the function is the interface between the requirements of the system and then according to the conditions they design the system correctly. System engineering assignments are being prepared by our engineering assignment help experts from top universities which let us to provide you a reliable assignment help online service.

Reference List
Bahr, N.J., 2018. System safety engineering and risk assessment: a practical approach. CRC press.

Chapman, W., 2018. System engineering assignment Engineering modelling and design. Routledge.

Chapman, W., 2018. Engineering modelling and design. Routledge.

Garvey, P.R., Book, S.A. and Covert, R.P., 2016. Probability methods for cost uncertainty analysis: A systems engineering perspective. Chapman and Hall/CRC.

Gore, P., 2016. Creating a Mission Architecture Step to Inform the System Engineering Process.

Hui, S., Silverman, J.M., Chen, S.S., Erickson, D.W., Basan, M., Wang, J., Hwa, T. and Williamson, J.R., 2015. Quantitative proteomic analysis reveals a simple strategy of global resource allocation in bacteria: molecular systems biology, 11(2), p.784.

Krarti, M., 2016. Energy audit of building systems: an engineering approach. CRC press.

McKean, D.K., 2019. Leveraging Model-Based Techniques for Component Level Architecture Analysis in Product-Based Systems (Doctoral dissertation, The George Washington University).

Morse, E., Dantan, J.Y., Anwer, N., Söderberg, R., Moroni, G., Qureshi, A., Jiang, X. and Mathieu, L., 2018. Tolerancing: Managing uncertainty from conceptual design to the final product. CIRP Annals, 67(2), pp.695-717.

Smith, H.L., Stevens, A., Minogue, B., Sneddon, S., Shaw, L., Wood, L., Adeniyi, T., Xiao, H., Lio, P., Kimber, S.J. and Brison, D.R., 2019. Systems based analysis of human embryos and gene networks involved in cell lineage allocation. BMC Genomics, 20(1), p.171.