Ah Discussion

1- AL JOHARA

In 1994 the European Channel Tunnel was opened, and it linked the European continent and Britain.  It is a 31-mile tunnel carrying freight trains and Eurostar trains between Paris and London and is today considered the fast and modern transport institution. Although the tunnel traces its background to the 19th century, it is considered an achievement of the 20th century (Syon, 2008).

Though the project has been credited to be a success, the size of the channel had intrinsic uncertainties and risks. Tunneling projects are naturally high risk and often end up in high overrun on budget and completion dates due to the underground setting that were not anticipated during the contract (Syon, 2008). The risks present in the Chunnel project were design and construction challenges brought about by the changing geological situations, the third-party issues, the safety of the workers, infrastructure/property damage and environmental risk (Berend, 2016). In Britain there was no space for disposing of spoil and emission of waste became a significant challenge. Though there was a mitigation of disposing spoil in the Coast, some critiques were of the view that it would destroy the environment. The risk of the tunnel collapsing due to earthquakes was a concern to many individuals; however, the tunnels had a design which ensured they were resistant and caution was taken to reduce possibility of damage to equipment installed in them and to make sure entrances couldn’t be blocked by local collapses and landslips (Pireddu, 2017). 

Technological risks were experienced in the construction of the tunnel.  These include the political and economical viability of the machinery that were required to ensure the project goals were achieved. In the Chunnel tunnel, this risk was mainly assumed by the contractor, Eurotunnel. All the technological risks involved were mitigated by the comprehensive geological research of the strata of where the tunnel was to be constructed (Berend, 2016). Earlier concerns demanded the state of the art equipment which were costly and afterward found unnecessary. The political risks were mitigated by assigning the task to a private investor after the conservative and left-wing reign in Britain (Pireddu, 2017).

 The project further experienced credit risk. The risk calculated on the basis of the investor’s creditworthiness. Unlike other mega-projects which are normally funded by the government, the Channel tunnel was private-funded and therefore presented a high risk to the contractors and investors. Most private investors were giving a small fraction of the total approximation cost. The administration for example under credit limitation had to suggest lump-sum contracts, which were impractical for such projects. Litigation and claims at the end of the project were experienced (Berend, 2016).

2- Fahad ALMahmoud

One of the risks that the English tunnel faced is aerodynamic of the tunnel, the designers have found that the temperature in the middle of the tunnel is going to reach a very high degree since the heat is going to be generated from the high speed of the trains as they go through the long tunnel and air circulation won’t be available in our case. The engineers have decided to install a cooling system inside the tunnel, the system includes pipes along the tunnel where chilled water can circulate freely from refrigeration units designed at both ends of the tunnel.

The second risk of the construction of the tunnel is the safety if the tunnel catches fire of a natural disaster. In 1996, a fire incident caught a train was heading toward France which caused huge destruction to the tunnel and the repairment took a long time to be done. After this incident, the designers create a Fire Equipment Management Centers (FEMC) and a traction system which divides every 1,500 meters into sections that can be isolated when a certain disaster occurs, so the damage and destruction can be stopped and limited.

Discussion 6

1- naif al ghuthami

(a) Develop a set of operational requirements for a simple lawn tractor. Limit

yourself to no more than 15 operational requirements.

Operational requirements for a simple lawn tractor are:

1.  E ffective  knife stroke

2.  Effective cutting height

3.  Sufficient working width

4.  Knife speed

5.  Knife forward speed

6.  Crank speed

7.  Ratio of speed

8.  Sufficient filed capability

9.  Filed efficiency 

10.  Sufficient harvest capability

11.  Economic fuel consumption

12.  Effective in all weather

13.  Rotating blades 

14.  Lights to work in the dark

(b) Develop a set of performance requirements for the same lawn tractor.

Limit yourself to no more than 30 performance requirements.

Performance requirements for a simple lawn tractor are:

1.  H igh quality knife to cute efficiently

2.  Capacity to move knife to change cutting depth

3.  Rotation of blades to maximize efficiency 

4.  Setting of speed to make it high/low

5.  Effective materials to sustain quality of parts

6.  Cost-effective fuel usage system

7.  Cover all running parts to prevent damage 

8.  Effective light system to perform in the shaded areas

9.  Light-weight to move is easily 

10.  Easy and safe to use in all weather

11.  Knife need to be stop in minimum time

12.  Guards on the blades 

13.  Proper lubrication of the running parts

14.  Efficient ignition for start it

15.  Distance meter to cut grass with required length

16.  Gear system to manage its speed

17.  Sufficient blade control system

18.  High quality color and finishing

19.  Sufficient sitting capacity

20.  Easy to operate and signal

21.  Overall  high efficiency  in all operations

(d) How would you go about validating the requirements in (b)?

To validate the requirements, I make comparison between operational requirements and performance requirements. I analyze its operations and performance to make it time-effective and cost-effective. 

2- Khalid al assaf

- Develop a set of operational requirements for a simple lawn tractor. Limit yourself to no more than 15 operational requirements.

Ø  Blades to function when gear changer is used 

Ø  Should be simple and easy to operate. 

Ø  Should have a 4wheel drive. 

Ø  Should shave grass to the minimum level possible

Ø  Should cover a wide area of about 30 inches when cutting

Ø  The driver should be covered from rain. 

Ø  The feet should be protected from rotating blades 

Ø  Blade to only operate when driver releases the command.

· The driver should be able to sit 

- Develop a set of performance requirements for the same lawn tractor. Limit yourself to no more than 30 performance requirements.

Ø  Should have numerous blades

Ø  The rotating horse power should be high 

Ø  Cutting blades to rotate at speed

Ø  Tractor should have a balanced weight.

Ø  Should be well painted with a long lasting paint

Ø  Should operate safely and always reliable. 

Ø  Blades not to run for long after stop command.   

Ø  Should pass all the tests on functionality. 

Ø  Have parts properly greased.

Ø  Have steering wheel for navigation.

Ø  Be able to take a tight bend.

Ø  Have a sound silencer to minimize noise pollution. 

Ø  Should have shock absorbers to minimize vibration. 

Ø  To have a weather roof for the driver.

Ø  Have lighting system.

Ø  Moderate fuel consumption.

Ø  Accessible re-fuel tank.

Ø  Have rechargeable battery for ignition. 

Ø  Spear wheel 

Ø  Toolbox for minor repairs.   

-  How would you go about validating the requirements in (b)?

Ø  I will carry out analysis to ascertain that performance requirements are meeting the operational requirements as set by the users. 

Discussion 7

1- aljohara

8.4 Under the subsection Program Risks, five examples are listed of conditions that may result in a significant probability of program failure. For each example, explain briefly what consequences of the condition may lead to a program failure. 

·  A leading-edge unproven technology is to be applied: Implementing unproven new technology may lead to program failure because there is not enough information on this technology. Therefore, it is impossible to identify some of the issues that might arise and impossible to predict the outcome of the new technology. Also, new technologies cost a lot of money, and it is expensive to maintain. These technologies require very skilled and knowledgeable engineers to work on the implementation process and direct and guide the people who are going to use it.

·  A major increase in performance is required: An increase in performance may result in program failure because the system might not handle the required increase and the increase is beyond its capabilities. This could result in slowing down the system and possibly a complete shutdown of the entire system. Also, increasing the performance require additional costs that might not be available.

·  A major decrease in cost is required for the same performance: A decrease in cost may lead to program failure because it will affect the quality of the product or service performed. The decrease in cost can be in the form of cutting down on the number of employees, using cheaper technologies, and reducing maintenance. Reducing the cost and maintaining the same level of performance is a big challenge in any project that can lead to failure. 

·  A significantly more severe operating environment is postulated: Operating in a severe environment may lead to program failure because the program is not intended to operate in this environment. The program will break down fast and will require additional cost to repair. Also, the program will need to be maintained more frequently.    

· An unduly short development schedule is imposed: Imposing a short development schedule may lead to program failure because it will affect the overall prosses of development. The developer will have to cut the time from testing or evaluation which in the end might affect the quality of the final product.

2- Fahad almahmoud

1.  Poorly defined program scope- Project/program scope is an essential part of project planning that involves identifying and documenting the project goals, deliverables, costs, activities and the due date for delivery of the project. Scope section in project planning also includes guidelines for making decisions for any change requests that arise during the course of the project. If the program scope is not properly defined i.e., without specific goals and deliverables, then it would eventually lead to program failures. In large projects, there are possibilities of ‘scope creep’. Scope creep is a situation in which part or the whole project requires additional work, time and efforts due to poor planning or miscommunication. If all these factors are not documented properly in the project’s scope, then it leads to project failure.

2. Failure to identify key assumptions- The assumptions and constraints are factors that needs to be identified correctly and documented in the entire project life cycle. These factors play a vital role in the planning phase. The risk management is heavily reliant on the assumptions. Hence, if they are not analyzed properly, it might lead to project failures affecting project’s outcome.

3. Inadequate risk management- Poor or inadequate risk management is one of the major causes for project failures. Ignoring or not identifying any possible risks in the project life cycle might lead to huge loss in terms of cost, time and assets. It spoils the reputation of the company and also strains the relationship between the company and its clients. Accurate intelligence is required to identify the potential threats and challenges facing the project. If this is not done properly, then it may lead to program failure.

4. No use of formal processes and strategies- There is a strong link between the project and the organization’s key processes and strategic practices. There are procedures and processes followed by organizations that are successful for them. However, if projects do not use these defined processes and strategic practices, then it might lead to project failure. It is pertinent that the project managers follow the formal processes and strategies in the project life cycle to ensure adherence and compliance with the company policies and procedures. Without these, the project is a failure.

5. Lack of details in program plans- Lack of details or poor planning leads to project failures. The planning phase is the most important phase in a project as it leads to success if properly planned. Otherwise it ends in project failure. All the essential details in planning such as resources, cost, equipment, time, delivery deadlines, etc need to be planned with precision. If the plans does not have such details, then the project team members will not have any focus to drive the project towards success.

Discussion 8

1- Fahad almahmoud

For this trade study, four different models of sports cars of the year 2018, the four cars will be evaluated based five criteria’s are selected with points which are given to each model on the basis of the criteria’s given below:

1. Price:

30k – 45k US $ = 2 point

25k – 29k US $ = 3 points

20k – 24k US $ = 4 points

15k – 19k US $ = 5 points

1. Mileage:

15,000 – 20,000 MPG = 5 points

21,000 – 25,000 MPG = 4 points

26,000 – 30,000 MPG = 2points

Above 30,000       = 1 points

1. How many seats:

5 seats = 5 points

4 seats = 4 points

3 Seats = 3 points

2 Seats = 1 point

1. performance:

350 - 450 hp. = 5 points

250-350 hp. = 4 points

200 – 240 hp. = 2 points

100 -200  hp. = 1 points

1. Test speed 0-60 mile per hour:

.Less than 5 second= 5 points

Less than 8 seconds= 3 points

Less than 10 seconds= 1 point

Comparison:

Based on the study we will go with the Ford Mustang GT.

2- shahad

Perform a trade study on choosing a new car. Identify four alternatives between three and five criteria and collect the necessary information required.

For this trade study, four different models of vehicles of year 2019 of four different automobile companies are selected. Then five criteria’s are selected and points are given to each model on the basis of the criteria’s given below:

· Price:

Price defines the actual cost of the cars under study.

30k – 35k US $ = 2 point

25k – 29k US $ = 3 points

20k – 24k US $ = 4 points

15k – 19k US $ = 5 points

· Mileage:

Mileage defines the consumption of fuel by the vehicle. How many miles can a car can travel in one gallon of fuel. Here combined mileage of the vehicle is taken.

15 – 20 MPG = 1 points

21 – 25 MPG = 3 points

26 – 30 MPG = 4 points

Above 30       = 5 points

· Seating Capacity:

It means how many seats are available in the vehicle for the people.

2 Seats = 1 point

5 Seats = 3 points

More than 5 seats = 5 points

· Horse Powers:

Horse power defines how powerful the engine of the vehicle is.

140 – 190 hp. = 3 points

200 – 240 hp. = 4 points

More than 240 hp. = 5 points

· Warranty:

Basic numbers of years provided for the warranty.

3 Years = 3 points

4 Years = 4 points

5 Years = 5 points

Comparison:

Disscussion 9

1- aljohara

As far as preliminary design review is concerned, this operation mostly involves the acquisition of an agency to certify the successful completion of the preliminary design. The main focus of preliminary design is to undertake a though analysis of systems components, interfaces as well as all the risky areas in the implementation of the system. In this case, there is a critical review of the design requirements and specifications. Before undertaking preliminary design review, organizations need to embark on the internal reviews to ensure that the requirements are clear and well addressed for the implementation of a workable system (Kossiakoff, Sweet, Seymour, & Biemer, 2011)

In preparation for the PDR review, I will do the following:

1. Arrange an internal review with the design team.

2. Assign key persons from the design team to present with me. 

3. Understand the design requirements, objectives, and specifications. 

4. Review the process of how the team came up with the final design. 

5. Familiarize myself with design drawings and details.

6. Focus on the most critical and controversial areas.  

7. Hold a practice session for questions that might come up during the PDR.

8. Prepare an agenda for the actual presentation.

2- fahad almamhmoud

The Preliminary Design Review (PDR) is a technical assessment that establishes the Allocated Baseline of a system to ensure a system is operationally effective.  A PDR is conducted before the start of detailed design work and is the first opportunity for the Government to closely observe the Contractor’s hardware and software design.  This review assesses the allocated design documented in subsystem product specifications for each configuration item in the system and ensures that each function, in the Functional Baseline, has been allocated to one or more system configuration items. The PDR establishes the allocated baseline (hardware, software, human/support systems) and underlying architectures to ensure that the system under review has a reasonable expectation of satisfying the requirements within the currently allocated budget and schedule.

Completion of the PDR should provide the following:

· An established system allocated baseline

· An updated risk assessment for the Engineering, Manufacturing, and Development (EMD) Phase,

· An updated Cost Analysis Requirements Description

· An updated program schedule including system and software critical path drivers,

· An updating report regarding program sustainment development efforts and schedules.

Disscussion 10

1- naif alghuthami

13.7 Define the terms “verification” and “validation.” Describe the types of tests

that are directed at each, and explain how they meet the definitions of these

terms.

In simple terms verification in engineering refers to the process of checking the correctness of elements in a process, program or system. Verification is derived from the verb verify which refers to making sure that an element or what it purports to do is true or correct or even accurate. The verification process happens or takes place mainly in order to do away with human errors during engineering processes. There are different tests that are carried out in the verification process. The tests include acceptance testing, smoke testing, and interface testing. A look at the types of tests carried out during the verification process reveals the tests meet the verification term. For example, interface testing allows the test team and other stakeholders to verify whether the interface in place allows for the activities that it is supposed to.

On the other hand, validation refers to the acts of proving the accuracy of an action or an element. There are four types of validation that are carried out in engineering. The first type is the prospective validation which refers to checking whether a program does what it is supposed to do in reference to its pre-planned protocols. The second type of validation is the retrospective validation which refers to the process of using historical data to establish whether processes are running as they are supposed to. The third type of validation is the concurrent validation which involves establishing whether functions are running as they are supposed to as production and manufacturing take place.

The fourth type is revalidation which refers to the repeating of a validation process already carried out. Tests carried out in validation testing include; unit testing, system testing, regression testing amongst others. A look at the types of tests carried out during the validation process reveals the tests meet the validation term. For example, in system testing, the tests carried out help in revealing the accuracy of a system in terms of meeting its objectives.

2- shahad

Define the terms “verification” and “validation.”Describe the types of tests that are directed at each, and explain how they meet the definitions of these terms.

Validation can generally be defined as personifying the actions to reveal the qualities of any product and to conclude its eagerness for ensuing the processes by comparing it with its expectations. Verification can generally be defined as “whether the product meets the specifications mentioned initially or not. It also justifies whether we are on a right track towards the final task or not”. There are many differences in validation and verification, one of the difference is: Verification can be done without executing the product while for the validation we have to execute the product first. Development phase has different phases. Verification and validation are executed in every phases of the lifecycle. 

In verification we consider reviews, walk-throughs and the inspections while in verification we do the testing phenomenally. There are different tests that are directed at both verification and validation. They can be tested in different ways that is more practicable according to the environment. It is more important to know that it is not compulsory that a product passes both the tests, there is always a probability that one product may pass validation process and fail verification process or vice versa. 

Validation is often executed at the completion of the testing cycle. A person spends a lot of time describing a product, building it, making sure his software is bug-free, and then do user acceptance testing, or submit it to a client / users, perhaps even a Beta discharge. But sometimes we require Beta testing too. Verification on the contrary can is tested in the other ways, and are considered the easy ways (They can be performed through direct testing, random testing, formal testing or combining all the tests). For instance we are to design a product that shouldn’t do 100 rpm, then we have to make sure that it should not complete more revolutions in the same time. Moreover, suppose we have the stipulations related to the project than by checking that specifications without implementing to see whether the conditions are up to the spot or not, what we have just done is verification.