Call/WhatsApp: +1 914 416 5343

Performance Engineering

Performance Engineering

I. Assessment Requirements

Aim: To assess your ability to apply the techniques learnt in ENG30111 to analyse, understand, and improve engineering processes and to communicate these.
Task: Write a 2000 to 2500 word* report (not including data tables) describing the manufacture of a product relevant to your engineering discipline and apply statistical and other techniques from the module in analysing the processes utilised. Neither the product nor the manufacturing process needs to be taken from a real manufacturing scenario, however they should be realistic enough to enable analysis.
Suggested Structure:
• Briefly describe the company manufacturing the product.
• Describe the product being manufactured and the manufacturing process. You will not be directly assessed for either the quality of the product design nor the manufacturing process, however your process should be sufficiently realistic and detailed to enable analysis using the methods learnt in the module. Emphasis should be on clearly communicating the processes using flow charts and other methods.
• Illustrate techniques learnt during the module by applying them to the processes described. You will need to create example data for the processes to illustrate statistical techniques. Possible techniques include:

 Kano model applied to classify product quality characteristics
 Sampling techniques applied to estimate quality characteristics and determination of confidence intervals
 Distributions of characteristics
 Process capability calculations
 Cause and effect analysis for manufacturing variables
 Scatter diagrams showing the relationship between quality characteristics and manufacturing variables
 Correlation and regression calculations for variables
 Design of experiments and calculation of factor effects
 Hypothesis tests / Analysis of Variance
 Control charts and establishing control limits relevant to manufacturing processes
 Application of methods from reliability engineering.

• Ensure that you not only apply the techniques but that you clearly explain what the objective of each technique is, why you are using it, how it can be applied to improve processes and what your conclusions are for your example data. You should also explain the limitations of your methods.
• Conclude with recommendations to management for the improvement of their engineering processes.

*If the word count causes problems, please discuss with the module leader.

II. Assessment Criteria
First Upper Second Lower Second Third Fail
Description of processes (20%) The company, product and manufacturing processes are described clearly and in detail with a genuine effort to explain relevant features in depth. Flow charts or other appropriate means are used to support descriptions. The product and manufacturing processes are described clearly. Flow charts or other appropriate means may be used to support descriptions. Key manufacturing processes are described in sufficient detail to enable analysis. Manufacturing processes are described but with insufficient depth or clarity making subsequent analysis problematic. No or inadequate description of manufacturing processes is provided.
Application of techniques
(60%) A wide range of techniques are used from across the module and applied to multiple processes. Example data is provided and calculations illustrated with appropriate application.

All techniques are thoroughly explained including their purpose and limitations. Clear and appropriate conclusions are drawn with suggestions for further investigation.

Analysis is synthesised into clear recommendations to management including setting up ongoing systems for process control and quality management. A wide range of techniques are used from across the module and applied to multiple processes. Example data is provided and calculations illustrated with appropriate application.

All techniques are explained including their purpose. There is consideration of the limitations of some techniques. Clear and appropriate conclusions are drawn.

Appropriate recommendations are made to management with reference to the outcome of techniques illustrated. A range of techniques are used from the module and applied to processes. Example data is provided and calculations illustrated with appropriate application.

Techniques are explained. There is discussion of the purpose or limitations of some techniques. Appropriate conclusions are drawn.

Some recommendations are made to management with reference to the outcome of techniques illustrated. Some techniques are used from the module and applied to processes. Calculations are illustrated with some attempt at application. The range of techniques is limited and / or techniques are not always appropriate.

Techniques are explained but not in sufficient detail. There is little discussion of the purpose or limitations of techniques. Conclusions drawn are unclear or inappropriate.

Recommendations to management are unclear or inappropriate. No or an inadequate range of techniques are illustrated. Little attempt is made at illustrating calculations.

Explanation of techniques is lacking / unclear / incorrect. No appropriate conclusions are drawn.

No or little attempt is made to make recommendations to management.
Style
(20%) Language is clear, formal and professional throughout. Excellent spelling and grammar.

All tables, graphs, diagrams and calculations are presented well and labelled where appropriate.

Structure of report is logical and has a clear organising principle. Language is generally clear, formal and professional. Good spelling and grammar with only occasional errors.

Tables, graphs, diagrams and calculations are presented well with only occasional mistakes.

Report is well-structured with appropriate sections. Language is not always as professional as it could be. Frequent spelling and grammar mistakes but these do not significantly detract from the flow or comprehensibility of the report.

Tables, graphs, diagrams and calculations contain errors but these do not undermine their purpose.

Report structure isn’t always clear. Language is not sufficiently formal or professional. Spelling and grammar mistakes impact upon the flow and comprehenisbility of the report.

Tables, graphs, diagrams and calculations contain frequent errors that sometimes undermine their purpose.

Structure of report is poor. Language is informal and unprofessional. Spelling and grammar mistakes make the report difficult to read.

Tables, graphs, diagrams and calculations have errors throughout that undermine their purpose.

Efficiency design entails the techniques employed in a solutions advancement existence period to guarantee the non-functional requirements for performance (including throughput, latency, or memory space usage) will be satisfied. It could be alternatively termed as solutions performance technology within methods technology, and software overall performance engineering or application overall performance engineering within software engineering.

As being the link between software achievement and business good results is constantly get identification, especially in the cellular place, software performance architectural has brought with a preventive and perfective[1] position in the software program advancement daily life routine. As a result, the phrase is normally utilized to describe the processes, individuals and technology required to effectively analyze non-functional demands, make certain adherence to service ranges and maximize app overall performance just before deployment.

The expression performance technology includes not just the application and helping infrastructure, and therefore the term functionality design is more suitable from your macro perspective. Adherence for the non-practical demands is additionally validated post-implementation by checking the development solutions. This is certainly part of IT service control (see also ITIL).

Efficiency architectural has turned into a independent self-discipline at numerous big companies, with tasking independent but parallel to techniques design. It is actually pervasive, concerning folks from a number of organizational devices but predominantly in the i . t business. Because this self-discipline is used within multiple methodologies, these pursuits will arise within differently given stages. Nevertheless, in the event the phases of your reasonable unified process (RUP) are employed as a framework, then the pursuits will happen as follows:

During the first, Conceptual cycle of the system or task, vital enterprise processes are discovered. Typically they may be classified as critical in relation to revenue importance, cost benefits, or another designated enterprise importance. This category is performed from the enterprise unit, not the IT business. Higher level hazards which could affect system performance are recognized and described currently. One example could possibly be recognized performance risks for a particular vendor process. Lastly, functionality routines, roles and deliverables are identified for your Elaboration phase. Pursuits and source of information reloading are included in the Elaboration stage undertaking ideas.

Elaboration During this determining phase, the vital enterprise functions are decomposed to critical use circumstances. Probe instances is going to be decomposed additional, when necessary, to solitary web page (monitor) transitions. They are the use instances that can be exposed to set of scripts driven performance testing.

The type of demands that connect with overall performance engineering are the non-useful requirements, or NFR. While a functional condition relates to which organization procedures are to be performed, a overall performance relevant non-practical necessity will correspond with how fast that organization operations functions under identified situations.

Development At the outset of this stage a number of overall performance instrument relevant pursuits are required. Such as:

Determine essential development associates as subject material professionals to the determined resources. Specify a profiling device for your growth/element system analyze setting. Establish a computerized device (part) overall performance analyze instrument for that development/part unit check surroundings this can be used when no GUI yet is available to drive the components under growth. Stipulate a computerized tool for driving hosting server-aspect unit (elements) for that development/part model examination surroundings. Stipulate an automated multiple-end user equipped set of scripts-driven stop-to-end instrument to the advancement/aspect system test atmosphere this can be used to perform screen-driven use cases. Determine a data source check info fill instrument for your growth/aspect device examination surroundings this is needed to ensure that the database optimizer chooses right performance routes and to make it possible for reinitializing and reloading the data source as needed. Deploy the overall performance resources for that growth crew. Presentations and education has to be given to improvement associates on the determined resources. The performance test group normally fails to carry out functionality assessments inside the advancement atmosphere, but rather in the specialized pre-implementation environment which is configured being as near as you possibly can to the arranged creation environment. This staff will implement overall performance evaluating against check circumstances, validating the essential use instances conform to the specified non-functional requirements. The group will perform stress tests against a normally expected (median) weight together with a maximum fill. They are going to often work pressure exams that will recognize the machine bottlenecks. The info obtained, as well as the examination, will be fed straight back to the audience that does functionality tuning. Where required, the machine will be tuned to give nonconforming tests into conformance with the non-practical specifications.

If performance engineering continues to be properly utilized at every iteration and phase from the venture to the point, hopefully this could be enough to enable the system to acquire overall performance accreditation. However, if for some reason (perhaps proper overall performance engineering operating methods had been not utilized) you will find assessments that cannot be tuned into conformity, then it will likely be necessary to return servings of the machine to improvement for refactoring. Occasionally the trouble can be resolved with a lot more computer hardware, but incorporating more equipment sales opportunities quickly to decreasing earnings.

Changeover In this ultimate cycle the machine is deployed to the manufacturing atmosphere. A variety of preparatory methods are needed. Such as:

Configuring the operating systems, system, web servers (application, internet, data source, fill balancer, and so on.), as well as any meaning queueing computer software based on the foundation checklists and also the optimizations determined within the performance analyze setting Making certain all overall performance tracking software program is used and configured Running statistics in the data source after the production information weight is completed When the new system is used, ongoing operations grab efficiency actions, such as:

Validating that weekly and monthly performance reviews suggest that crucial use circumstances execute inside the specific non useful prerequisite requirements Exactly where use situations are falling outside NFR requirements, publish disorders Establish projected styles from month-to-month and every quarter reviews, as well as on a every quarter schedule, carry out ability preparing control routines Support management Within the working site (post generation implementation) overall performance architectural centers primarily within three locations: services level administration, ability control, and problem control.

Assistance levels managing Within the assistance levels administration region, overall performance engineering is involved with support level deals as well as the related techniques checking that serves to authenticate assistance levels compliance, identify issues, and identify developments. For example, when actual consumer keeping track of is used it is actually feasible to make sure that user deals are increasingly being carried out in conformance with specified non-efficient specifications. Purchase reaction time is recorded within a data base to ensure that questions and records may be operate from the details. This makes it possible for pattern examination which can be useful for capacity managing. When user deals fall out of band, the occasions should generate signals so that attention may be placed on the specific situation.

Potential management For ability control, efficiency technology concentrates on ensuring that the solutions will continue to be within functionality conformity. This simply means executing pattern examination on historical checking generated data, such that the long run time of non agreement is foreseeable. For instance, when a product is demonstrating a tendency of slowing down deal finalizing (which might be as a result of expanding info establish styles, or growing quantities of concurrent customers, or some other elements) then at some point the machine will no more fulfill the standards specific within the service level contracts. Ability administration is involved in ensuring that further ability is included prior to that point (additional CPUs, much more recollection, new data base indexing, et cetera) in order that the trend lines are reset as well as the method will remain throughout the given performance collection.

Problem administration Inside the dilemma managing domain name, the performance engineering techniques are focused entirely on handling the main cause of performance relevant issues. These typically entail method adjusting, changing platform or product factors, as well as refactoring the application form application to settle bad functionality as a result of inadequate style or awful programming methods.