शैडोइंग अभ्यास: English Conversations | Listen & Read | Software Engineering - वीडियो के साथ अंग्रेजी बोलना सीखें
अभ्यास मोड चुनें
हर मोड पूरी स्क्रीन का अभ्यास कक्ष खोलता है।
843 वाक्य
यदि वाक्य बहुत छोटे या लंबे हों, तो समायोजित करने के लिए Edit पर क्लिक करें।
1
Welcome to English Conversations for Software Engineering.
2
Listen, read and practice to boost your skills.
3
Professor Wendell, I'm really interested in software engineering, but is it a good career choice?
4
I think so.
5
You are a good leader.
6
You'd enjoy programming in the large.
7
I agree.
8
I like working in groups.
9
You like to investigate problems, right?
10
Yes, I do, but software engineering seems like it could be hard.
11
It's sometimes challenging when others evaluate your work, but if you are patient, it is very rewarding.
12
That sounds like something I can do.
13
Hey, Grace.
14
What are you working on?
15
I'm still developing the home banking application.
16
Wait.
17
Didn't you finish that already?
18
Well, sort of.
19
I finished a version for laptops and desktops.
20
So, what are you doing now?
21
Next, I'm going to create an application for tablets.
22
Oh, that's a good idea.
23
Lots of people carry tablets nowadays.
24
Right.
25
That's why this version needs to work well with a touchscreen.
26
Thanks for calling
27
Worldwide Comp Supply.
28
How can I help you?
29
Hi.
30
I'm calling about order number 25841.
31
Some of the order is incorrect.
32
I'm sorry to hear that.
33
What's the problem?
34
I ordered 36 optical mice.
35
30 were regular and 6 were wireless.
36
I see that on your order confirmation.
37
How many were in the shipment?
38
Well, I received all 36 mice, but none of them are wireless.
39
Oh, no. We'll get this fixed right away.
40
This is a real hassle.
41
I needed this equipment immediately.
42
Again, I'm really sorry.
43
I'll throw in two more mice for free.
44
Hey, Greta, have you used the computer in the conference room?
45
No. Is there a problem with it?
46
Yeah, I think it's overheating.
47
Oh, that's not good.
48
What's it doing?
49
Well, the processor is working really slow, and the case feels unusually warm.
50
Does it make a lot of noise?
51
Now that you mention it, the fan did seem really loud.
52
It sounds like you're right.
53
If I were you, I'd replace the heat sink.
54
Yeah, it's probably defective.
55
I'd better give that a try.
56
What did you think of that assignment about early system software?
57
That was a really hard assignment.
58
I thought so too.
59
I can't believe people used to enter everything manually.
60
I know what you mean.
61
I'm ready to study modern operating systems.
62
I agree.
63
They're so much easier to use.
64
Are you ready for the quiz tomorrow?
65
I need to review that chapter again.
66
Don't forget to study about device drivers.
67
I'm not too worried about that.
68
Well, Mr Clay, I removed the spyware from your company's system.
69
Oh, thank you.
70
Our systems contain a lot of confidential information.
71
Yes, I can see that.
72
If you don't update your security software, you could really be in trouble.
73
Really?
74
You think this will happen again?
75
Whoever wanted your information is likely to keep trying.
76
I guess we'd better update the company's antivirus software then.
77
Definitely.
78
And I recommend a better firewall.
79
What does that do?
80
That makes it harder for unauthorised users to access the company's network.
81
Can you help me with something?
82
Sure, what is it?
83
I'm confused about the difference between linkers and compilers.
84
OK, well, a linker connects a program to information it needs from other programs.
85
Wait, I thought an interpreter did that.
86
No, an interpreter just reads the information so the program can run.
87
OK.
88
So then a compiler is what decodes program instructions?
89
Exactly.
90
It translates information from different programming languages.
91
I get it now.
92
Thanks.
93
Did you see the memo from the CEO?
94
Do you mean the one about the accounting software?
95
Yeah.
96
They want a whole new program for the Office Suite.
97
We're supposed to develop it by the end of the month.
98
I think that's a good idea.
99
A lot of our customers probably use accounting anyway.
100
Yeah, but I'm worried.
101
What will that mean for the other programs in our office suite?
102
What do you mean?
103
Well, our word processor needs to be updated.
104
I'm afraid that a new program will take away from that.
105
I see what you mean, but I think it'll be fine.
106
Another team is scheduled to complete that update this week.
107
Owen, where are we on software developments?
108
We're working on a lot of new things, Ms Thompson.
109
Last I heard, you were finishing a mobile app for cost analysis.
110
We finished that.
111
Now we're working on a program for route planning.
112
Can you tell me more about that?
113
We want to adapt a satellite navigation program, but ours will be much smaller.
114
Why's that?
115
It needs to be compatible with digital assistants.
116
Thanks for calling Mailbag Support.
117
How can I help you?
118
Hi.
119
I just installed the new Mailbag Deluxe, but I can't open it.
120
I'm sorry to hear you're having trouble.
121
Do you see the icon on your desktop?
122
Yes, it's there, but nothing happens when I click it.
123
Did you right -click the icon?
124
No. Should I try that?
125
Yeah.
126
Go ahead and right -click it instead.
127
Let's see.
128
Oh, I see.
129
And now I click Open Mailbag?
130
That's right.
131
What's the status on the new programme?
132
We're right on schedule.
133
Great.
134
Will you finish it by next Friday?
135
That's ten days away, right?
136
And we need about fifteen hundred more lines of code.
137
Fifteen hundred divided by ten is one hundred and fifty lines per day.
138
Can you do it?
139
I think so.
140
We have three engineers working on it.
141
So you need each engineer to do fifty lines per day.
142
Fifty?
143
Oh, of course.
144
Fifty lines times three engineers equals one hundred fifty.
145
We can handle that.
146
Hi, Mr. Lennox.
147
You wanted to see me?
148
Yes, Jenna.
149
Our clients are asking about the new software update.
150
We're working on it.
151
We already fixed 12 out of the 15 problems.
152
Well, that's four -fifths done.
153
What about the other three problems?
154
They're tricky.
155
The sudden shutdowns are the biggest issue.
156
I want you to focus on fixing that.
157
We'll release the update as soon as that's done.
158
So you want us to spend 100 % of our time on it?
159
Yes, the other fixers can wait until the next update.
160
Hey, Mary, how did the new programmes do on the market?
161
The demand for the route planning programme has really fluctuated.
162
That's strange.
163
Why do you think that is?
164
It seems to increase in the summer.
165
That's when people travel the most.
166
Oh, that makes sense.
167
What about the Budget Mobile app?
168
That did better.
169
The demand increased at a steady pace.
170
How do you think it will do in the future?
171
I have no doubt it will do well.
172
What did you think of my presentation?
173
I was impressed with your ideas, but you need to work on your presentation skills.
174
What do you mean?
175
For one, the audience couldn't hear you towards the back.
176
Oh, I didn't realise that.
177
So I need to project my voice next time.
178
Exactly.
179
And let's work on using fewer note cards next time.
180
Why?
181
What's wrong with them?
182
You looked at them too much.
183
You need to make eye contact with your audience.
184
I see.
185
I guess I should practice before my next presentation.
186
So, Ben, let's talk about next semester.
187
OK.
188
Can I enrol in advanced courses yet?
189
Well, not quite.
190
You still have some foundation work to finish.
191
Really?
192
Like what?
193
First you need to take calculus.
194
Then you can enrol in upper -level courses.
195
I guess I'll do that then.
196
What else should I take next semester?
197
Let's get you started on some basic computer engineering courses.
198
Yes, I think I'm ready for that.
199
I'll sign you up for computer architecture.
200
How do the job applications look?
201
There are a couple of good applicants.
202
I like this one, Paula Gardner.
203
Oh, yeah?
204
What does her resume say?
205
Let's see.
206
She has a degree from Lord Technical Institute.
207
And she worked for several high -profile firms.
208
So, she has strong technical expertise.
209
Who else is there?
210
I like Henry Pacheco too.
211
But he's still in college.
212
That might be okay.
213
What's his experience like?
214
He helped develop the X99 traffic analysis software.
215
Really?
216
That was a fascinating project.
217
Those engineers really had to think outside the box.
218
Yeah, that's what I thought.
219
Should I set up an interview with him?
220
Definitely.
221
Experience is nice, but I'd rather go with a curious, innovative person.
222
OK, I'll call
223
Henry right away.
224
Hey, how is your project going?
225
Not very well.
226
I'm still having a lot of problems when I try to run the software.
227
Really?
228
What have you done to fix it?
229
I did a quick analysis of the code.
230
Have you tried anything else?
231
Yeah.
232
I ran some standard debugging procedures.
233
Then I tried applying some common solutions.
234
Huh.
235
What will you do next?
236
Well, I just started a more detailed analysis of all the code.
237
That's a good way to start.
238
My two earlier changes helped in different ways.
239
If this doesn't work, I might try a synthesis of both iterations.
240
That's a good plan.
241
It sounds like you're addressing the problem from all angles.
242
If I keep looking, I'm bound to find the solution soon.
243
Are you ready for the accounting test this week?
244
I don't know.
245
I still mix up some of the concepts.
246
Yeah, so do I.
247
Do you remember the difference between an open system and a closed system?
248
I think so.
249
The open system allows mass to move in and out, right?
250
Let me make sure.
251
Yes, that's right.
252
The ones that always confuse me are the extensive and intensive quantities.
253
Those are easy to get backwards.
254
So let me see if I can remember this.
255
If you can count something, it's extensive.
256
That sounds right.
257
On the other hand, intensive quantities cannot be counted.
258
Right, but you can't measure them.
259
I still don't quite get how that works.
260
Think about temperature.
261
You can't count it, but you can still monitor its changes.
262
OK, that makes sense.
263
Can you give me an update on the requirements for the library catalogue application?
264
It's going slowly.
265
It was good at first, but we found some major problems when we did the validation.
266
I don't like the sound of that.
267
What happened?
268
Some of the specifications were based on old data.
269
The requirements didn't include the library's new DVD catalogue.
270
Oh, that's right.
271
Originally they only included books.
272
Will we be able to fix the problem?
273
We're updating the data now.
274
Then we'll just plug it into the existing requirements document.
275
How long will that take?
276
We should have it done by the end of the week.
277
Oh, good.
278
I'm really glad to hear it.
279
I was worried that we wouldn't make the client's deadline.
280
I don't think that'll be a problem.
281
We'll keep you updated.
282
Come in, Evelyn.
283
Please have a seat.
284
Is there a problem?
285
No. Actually, quite the opposite.
286
I really enjoyed your presentation last week on the design pattern for our current project.
287
Really?
288
Thank you.
289
It's hard to describe software architecture to clients, but I did my best.
290
You did a great job.
291
Would you be interested in putting together another client presentation?
292
Sure.
293
I'd be happy to.
294
Great.
295
I need to give a presentation to some other clients.
296
It's an overview of our progress on the application framework.
297
Sure.
298
Just send me the information.
299
I'm sure I can put something together.
300
Great.
301
We already have an implementation view.
302
I'll send it to you this afternoon.
303
When will the presentation be?
304
The presentation is next week.
305
Can you finish your notes by Friday?
306
I'd like to look over them.
307
No problem.
308
I'll send them to you as soon as they are ready.
309
We need to start on this database software.
310
Do you have any ideas?
311
Well, first, we need to decide on an architectural structure.
312
I agree, but I'm not sure which one we should use.
313
Hmm.
314
We're going to bring in a lot of data from outside sources.
315
Maybe we should think about a repository.
316
I thought about that, but I don't think our data will work with the repository system.
317
OK, what were you thinking then?
318
I think pipes and filters might work better.
319
It has better mechanisms for ordering data.
320
I really don't like that idea.
321
Pipes and filters plans are more complicated than we need.
322
Really?
323
I guess I don't have much experience with them.
324
I do, and I think we can do this with a simpler plan.
325
Thank you.
326
What about an abstract data type?
327
That could work.
328
We would just have to design components and connectors that match our data.
329
Is there anything you need help with?
330
Actually, there is.
331
I'm still confused about a few things.
332
Let's see if we can get that cleared up.
333
What is confusing you?
334
Why do we need to make a call graph before adding the details?
335
What do you mean?
336
Wouldn't it save time to add the details as we create the design?
337
No, you need to consider the purpose of an abstraction.
338
An abstraction?
339
Yes, creating a design without details lets us find problems early.
340
That way we can fix them before the software is too complex.
341
Does that make sense?
342
Yes, I think I understand.
343
So, the cohesion of different modules is clearer in an abstraction.
344
Exactly.
345
Do you have any other questions?
346
No, I think I get it now.
347
Thanks.
348
Can anyone tell me about the limitations of a bottom -up design?
349
Yes, Linda.
350
A bottom -up design has to be created from scratch.
351
The designer has no previous function to work with.
352
Very good.
353
Can you tell me about some of the benefits of a bottom -up design?
354
Um, I'm not sure.
355
What about in regards to managing problems in a design?
356
Oh, well, a bottom -up design is less likely to have problems.
357
But if it does, it's more difficult to eliminate them.
358
Great.
359
And what about top -down designs?
360
Well, top -down designs tend to have more problems, but it's easier to eliminate them.
361
And how would one do that?
362
I'm not sure.
363
Maybe by decomposing the software?
364
That's correct.
365
It looks like you've been keeping up on the reading.
366
Excuse me, do you mind if I ask you a few questions about your project?
367
Not at all.
368
Go ahead.
369
I'm interested in different software design methods.
370
Are you working in JSP?
371
No, but you're close.
372
For this project, I'm using the JSD system.
373
Oh, that's interesting.
374
What made you decide to plan it that way?
375
Well, I prefer the structured stages of the JSD system.
376
It's easier to gauge how far along you are with the project.
377
That makes sense.
378
What stage of the project are you in now?
379
Right now, I'm working on the network stage, but I'm having some problems.
380
What kind of problems?
381
The data flow isn't working like I hoped.
382
I might have to go back to my DFDs before I continue.
383
I see.
384
Let me know if I can help.
385
I'd love to be involved in this project.
386
Sounds good.
387
Thanks.
388
class diagram and an interaction diagram.
389
Okay.
390
Did the engineers finish mapping the object interactions yet?
391
No, so you'll have to work on the interaction diagram last.
392
In the meantime, you can get started on the collaboration diagram.
393
Okay.
394
Can you send me the interaction data when it's available? Of course.
395
Now listen, these diagrams need to be done by the end of the month.
396
They're a client.
397
So they need to be especially clear, right?
398
Right.
399
I'll send you that data as soon as it's ready.
400
I need an update on the testing for the latest project.
401
I was just looking over the latest test results.
402
What do they say?
403
It looks like the software did pretty well.
404
Only a few failures were detected.
405
What testing model did you use?
406
For this test, we use the destruction model.
407
Good.
408
Use an oracle to determine where the failures are coming from, then have an engineer fix them.
409
Okay, we will probably run some more tests while we do that.
410
That's a good idea.
411
I think you're going to find more faults when you look at other models.
412
Do you have a suggestion about what testing model we should use?
413
I'd like to see the results from a prevention model test, but do the oracle comparison first.
414
OK, I'll bring you the results shortly.
415
How is the testing going on the accounting software?
416
Actually, I have some bad news about that.
417
The white box testing we did found a lot of faults.
418
That's not good.
419
What are you going to do?
420
We're going to do some black box testing before we start making any changes.
421
Good.
422
Are you using both dynamic and static analysis?
423
For now, we're just doing static analysis.
424
OK.
425
Try to get this taken care of quickly.
426
I want the software ready for Fagin inspection by next month.
427
I understand.
428
I've got the whole team working on it.
429
Maybe you should get another team leader to do a peer review.
430
That's a good idea.
431
I can have someone do stepwise abstraction on it.
432
Yes, do that.
433
I'll check back with you in a week.
434
OK, we should have a lot of the problems fixed by then.
435
Your test sets were good for a first try, but I have some feedback for you.
436
OK, I'd love to hear it.
437
You covered the statement coverage property really well, so that was great.
438
I'm glad you noticed.
439
I worked really hard on that.
440
But there are some problems too.
441
Like what?
442
It seems like you relied too much on the last project's tests.
443
Well, I use the renaming property.
444
I see.
445
I'd advise you to be careful about that.
446
Remember the general multiple change property.
447
So I should try to write new tests?
448
Yes, whenever you can.
449
Even if programs are similar, they often need different tests.
450
Oh, right.
451
That's the anti -extensionality property, isn't it?
452
Yes, that's absolutely right.
453
Just remember that next time, and you'll be fine.
454
I will, thanks.
455
The database software needs some reverse engineering.
456
What are we doing about that?
457
We'll definitely need to do some re -documentation.
458
Really?
459
Won't that take a long time?
460
It will, but the code is too unstructured to edit right now.
461
Okay.
462
Do you think we'll have to edit the software after re -documentation?
463
Definitely.
464
It's going to take a lot of work to modernize this software.
465
Should we revamp the user interface also?
466
I think so, but we should work on that last.
467
This seems like a lot of work.
468
Why don't we just write a whole new program?
469
I thought about that, but I really think the legacy system has a lot of useful features.
470
Maybe you're right.
471
The update probably won't take as long as starting from the beginning.
472
Exactly.
473
Restructuring is much faster than writing new software.
474
Okay.
475
We'd better get started.
476
Hey, have you got a second?
477
Sure, what's up?
478
We need to talk about the components on the library software.
479
Okay.
480
Well, the material component is almost finished.
481
When will it be done?
482
Probably by the end of this week.
483
That's good.
484
What about the conceptual component?
485
We didn't start that yet.
486
Oh.
487
I think we should get to work on that as soon as possible.
488
I agree.
489
Do you want to split up the levels and work on them separately?
490
That's a good idea.
491
I'll take the semantic level.
492
You get started on the task level.
493
What goes into the task level again?
494
You define the tasks performed by the user and the tasks performed by the software.
495
Right.
496
And the semantic level describes the tasks more generally, right?
497
Yeah, that's correct.
498
Do you think you can manage it?
499
It shouldn't be a problem.
500
I'll keep you updated on my progress.
501
I'm excited to meet with you today.
502
Good.
503
Let's talk about your experience.
504
It says here that you worked on ergonomic design before?
505
Yes, I designed keyboards for a hardware production company.
506
How would you incorporate that experience into software design?
507
I think it's really important that software engineers understand the hardware for their systems.
508
How do you think they can do that?
509
They need to think about the physical way a user interacts with a computer.
510
I agree.
511
Do you have experience with artistic design?
512
Yes.
513
I worked on web interfaces at my previous firm.
514
And what place do you think artistic design has in software design?
515
I think it's one of the most important factors.
516
Good software is useless if it has an inefficient interface.
517
That's a great point.
518
And it says here that you have a degree in computer science.
519
Yes, that's right.
520
Well, it certainly seems like you have the qualifications for this job.
521
I'll make my decision soon.
522
Hey, can you help me with something?
523
Sure.
524
What do you need help with?
525
I'm thinking about reusing some software on a new project.
526
But I never tried that before.
527
I did some black box reuse on my last application.
528
Did it work well for you?
529
Yeah, it was great.
530
It really saved me a lot of time on the project.
531
Huh.
532
Would you recommend
533
Black Box Reuse?
534
Yeah, it was okay.
535
I used source codes that were for sale.
536
They were more suited to the project I was working on.
537
Is it possible to get source codes for free?
538
I think so, but they might not be as specific as the kind I used.
539
I could just do some ad hoc application.
540
Yeah.
541
It would take more time than black box reuse, but I think it would still save you time in the long run.
542
Do you think software reuse is a good idea?
543
Or should I just write the code myself?
544
Try the reuse.
545
If it doesn't work out, you can start from scratch on your next project.
546
I guess that's true.
547
I'll look into getting the codes I need.
548
Thanks for your help.
549
Excuse me, could I talk to you for a moment?
550
I have a few questions on software reuse.
551
Sure, what do you need?
552
I don't really understand the benefits of transformation systems.
553
Why can't engineers do that work themselves?
554
Transformation systems save time.
555
While the system transforms their code, engineers can work on other projects.
556
Aren't they worried that the system will make mistakes?
557
Not really.
558
These systems are usually pretty sophisticated.
559
The task they perform is more basic than it might sound.
560
Okay, I guess I understand.
561
Can you explain middleware to me?
562
Sure.
563
Middleware is go -between software.
564
It connects individual applications to an operating system.
565
But why is it necessary?
566
The benefit of middleware is that it helps the operating system make sure that applications are running smoothly.
567
Middleware works even if there are a lot of applications running at the same time.
568
Oh, I see.
569
It's like an application manager.
570
Yes, exactly.
571
Do you have any other questions?
572
No, I think that clears everything up.
573
Great.
574
We'll talk about this more in class today.
575
How do you plan to check the reliability of your new program?
576
I haven't even finished the standard and exception domains yet.
577
Yeah, but you still need to think about your reliability checks.
578
I guess so.
579
What would you recommend?
580
When I make a program, I like to use BM and LPM.
581
Why do you prefer those?
582
I find that they give more accurate error probabilities than other methods.
583
I didn't know that.
584
I'll keep it in mind when I get to that stage.
585
You definitely should.
586
Accurate error checks will save you a lot of trouble in the long run.
587
I understand that.
588
I'm probably going to use recovery blocks in this application, too.
589
That's a good idea.
590
It sounds like you have a strong piece of software.
591
That's what I'm hoping for.
592
I don't want any problems like last time.
593
What happened before?
594
The application wasn't as fault -tolerant as I thought it was.
595
That's too bad.
596
Did it malfunction a lot?
597
It did.
598
It was disappointing, but I learned a lot from that experience.
599
Have you finished the specifications for the new project yet?
600
I'm just putting the final touches on them now.
601
Great.
602
I need to talk to you about the user scale.
603
I think it's going to be pretty big.
604
Do you think it will be family level?
605
Actually, I'm looking at city level.
606
If we're going to finish on time, we'll need a lot of engineers.
607
Wow.
608
I guess it's even bigger than I thought it would be.
609
Yeah.
610
Anyway, you might want to start selecting the environments.
611
Great.
612
I'll do that right away.
613
What kind of environment do you think is best?
614
Well, we definitely need something that can manage input from a lot of people.
615
So do you think you will use a process -centered environment?
616
Probably.
617
I just want to make sure the one we're looking at has the right tools.
618
I want our engineers to have everything they need.
619
How soon can you get the environment set up?
620
Probably within the next few weeks.
621
Can I talk to you for a minute?
622
I have a request from the engineering staff.
623
Sure.
624
What's up?
625
It involves the case software that we are currently using.
626
Is it malfunctioning?
627
Not exactly.
628
It is kind of outdated, though.
629
We'd like to get a new Unix program.
630
How is the Unix program going to help?
631
Well, one of our problems is the reserved checkout.
632
Right now, only one engineer at a time can work on the program files.
633
With unreserved checkout, several engineers could work at once.
634
I see.
635
Are there other benefits?
636
Yes.
637
The Unix program comes with an MWB.
638
This would help out our project managers.
639
It sounds good, but I'm not sure if we have the budget for it.
640
Is this program really necessary?
641
I think so.
642
To produce software at a competitive rate, we need programs that support our engineers.
643
I understand that.
644
I'll go over the budget and see if the upgrade is possible.
645
Great.
646
Let me know what you decide.
647
Can you give me an update on that flaw that we found last week?
648
Yeah, I retraced all the steps to find the problem.
649
And were you successful?
650
Yes, I just finished double -checking my work.
651
Great.
652
Did you send a request to the CCB about changing the baseline?
653
The request is already sent.
654
I'm just waiting for them to approve it.
655
Great.
656
You're really on top of things.
657
Well, there are still a few steps before this flaw is fixed.
658
Like what?
659
First, I need to get the latest copy of the parallel development documents.
660
That shouldn't take too long.
661
What else do you have to do?
662
Well, then I need to merge the fixed version with the updated version.
663
Oh, that sounds like it could be time -consuming.
664
It will be, but I should be able to finish it by the end of the week.
665
That's the spirit.
666
I just hope this is the only flaw we have to deal with on this project.
667
I do too.
668
I definitely don't want to have to do all of this again.
669
Hi, Cindy.
670
Do you have a minute to discuss the new team organization?
671
Yes, I'd be happy to.
672
Did you come up with any ideas for the latest project?
673
I did.
674
I think it'll be most efficient to divide the employees into SWOT teams.
675
What benefit will that offer us?
676
With SWOT teams, we can assign specific tasks to units of employees.
677
Each unit works independently on a particular task.
678
That sounds good, but I'm worried that the units won't communicate with each other enough.
679
Hmm, that's a good point.
680
We could create a hierarchical structure instead.
681
I think that might be a better idea.
682
Maybe, but I'm not sure if it would be the most efficient.
683
You're right.
684
We need a structure with defined units, but we also need strong management.
685
We could use chief programmer teams.
686
I was just thinking that.
687
That way everyone knows whom to report to.
688
Right.
689
But they would still be working on specialized tasks.
690
I like this idea.
691
Can you start assigning employees to different units?
692
Sure.
693
I can send you some lists tomorrow.
694
Did you see the latest quality control report?
695
I did.
696
It looks like a few things are going to change around here.
697
I know.
698
I was really surprised.
699
I felt we did a good job on quality control.
700
Really?
701
I expected them to find some problems.
702
My department's having trouble meeting key practices.
703
Now that you mention it, I guess that's a problem in my department, too.
704
I think we'll be okay if we redefine the key process areas.
705
But I didn't notice any other problems. Did you?
706
A few.
707
I think the company needs to stop focusing so much on quality factors.
708
Really?
709
Why?
710
Because it's hard for a lot of engineers to work that way.
711
It's better to think about the quality criteria.
712
Oh, I understand.
713
That way, engineers can actually measure their improvement.
714
Exactly.
715
That makes sense.
716
Hopefully, management will address all of this at the next meeting.
717
I think they will.
718
I know that most of the managers were not very pleased with the audit results.
719
I have the latest budget and cost reports for the accounting software project.
720
Great.
721
I'd love to hear them.
722
How do they look?
723
It's hard to say.
724
The reports are a little different depending on which algorithm you look at.
725
Give me the good news first.
726
Okay.
727
Fortunately, according to the Putnam model, we are right on schedule.
728
That's great.
729
What about if you look at the Delphi method?
730
According to the Delphi method, we are just barely behind schedule.
731
That's not too bad.
732
Why are we behind schedule?
733
We estimated some software sizes incorrectly.
734
Some have a higher clock than we expected.
735
Will this affect the cost of the project?
736
It will, but the overall budget estimate is still pretty accurate.
737
Luckily, we didn't make it too optimistic.
738
That's good.
739
I can't afford to have another project go over budget.
740
I understand.
741
We're working really hard to get the development time down.
742
Good.
743
Keep me updated on any other changes in the budget.
744
I will.
745
I'm hoping we won't have to make any more.
746
Hey, Shirley.
747
Where have you been?
748
I was at the workshop on project management.
749
It was interesting.
750
I didn't sign up for it.
751
Was there any good information?
752
Overall, it was really informative.
753
They discussed three main topics in project management.
754
I learned a lot about degree of certainty.
755
Interesting.
756
What else did they discuss?
757
They also talked about risk management.
758
I didn't realize how important it is actually is to identify risk factors early.
759
I hadn't really thought about it either.
760
Did they give any tips for organization?
761
Yeah.
762
That was the last topic they addressed.
763
I already knew about a lot of them, though.
764
Which methods did they discuss?
765
I'm about to run my first project, and I'm wondering what might be useful.
766
Well, they talked about WBS, Yes, which I use all the time.
767
They also talked about PERT charts.
768
Did they cover Gantt charts?
769
Time ran short, so they just told us where to find more information.
770
I'd like to know more about it.
771
I'll give you some handouts from the workshop.
772
All right, John, let's talk about ethics.
773
It is an increasingly important topic in software engineering.
774
I'm glad to hear you say that.
775
Can you tell me about a time when you had to defend your principles?
776
At my last job, my manager really pushed me to meet a deadline, but the software wasn't ready for public use yet.
777
What was wrong with it?
778
It was designed to protect private records, but it wasn't tested yet to ensure security.
779
So what did you do?
780
Well, I wanted to protect the best interests of the public.
781
I refused to deliver the software without adequate testing.
782
That was very bold.
783
Why did you make that decision?
784
For one thing, I have high standards for the software that I produce.
785
Weren't you afraid that you would be fired?
786
Not really.
787
In the long run, I was protecting the welfare of the company, too.
788
That's great.
789
High standards for software are important, but they should never be valued more than integrity.
790
Yeah, integrity is important to me.
791
I want employers and clients to trust me.
792
Hey, Tonya.
793
I'm thinking about upgrading the company's network, and I was wondering what you know about SOS.
794
SOS is a networking model.
795
I don't know much about computers.
796
What does that mean?
797
Let me explain the basics.
798
SOS stands for Software as a Service.
799
It is a model that operates under cloud computing.
800
What's cloud computing?
801
It's a distribution of computing and storage services.
802
So it's a way to access information?
803
Yes, partly.
804
Clients purchase the rights to a software license.
805
Then they share that software with their users.
806
Okay.
807
How do they pay for that, though?
808
Clients typically pay regular fees.
809
Some companies charge users metered fees, while others prefer pay -as -you -go.
810
It just depends on your needs.
811
I see.
812
So what role does
813
Sauce play in cloud computing?
814
SOS is a type of cloud in which software is available over a network.
815
In my opinion, it is a reliable way of sharing information and software.
816
How does someone access the software?
817
That's easy.
818
You can access the cloud through any web browser.
819
Hey, Dana.
820
I wanted to thank you again for your letter of recommendation.
821
Oh, you're welcome, Clyde.
822
I hope you get into that engineering degree program.
823
Yeah, it should be a great experience for me.
824
Do you know what your focus will be?
825
Eventually, I want to be a developer, but the academic side interests me too.
826
So you might want to be a researcher?
827
I'm considering it.
828
What do you think of that idea?
829
I think that's a smart move.
830
You have to be able to analyze technology before you can develop it.
831
That's what I thought.
832
Then maybe I could be a freelancer on the side.
833
Oh, sure.
834
That's a great way to advance your career.
835
Right.
836
Wow, it really seems like there are lots of options in this field.
837
There are.
838
Software engineering is an exciting industry to work in.
839
Do you know where I can get more information about career options?
840
The IEEE is a well -respected international organization.
841
Check out their website.
842
Great.
843
I'll take a look.
ऐप डाउनलोड करें
धाराप्रवाह बोलने के लिए ज़रूरी सब कुछ
AI उच्चारण स्कोरहर वाक्य का स्कोर
IPA अभ्यासहर ध्वनि में महारत
शब्दावलीअपना शब्द भंडार बनाएँ
शब्द गेमखेलते हुए सीखें
उसी चैनल से
A2English Listening A2 Practice
Daily ConversationWorking Adults
A13
(4) - English Conversation For Beginners (A1)
Daily ConversationWorking Adults
A15
(2) - English Conversation For Beginners (A1)
KidsTravel EnglishTeens
A13
(5) - English Conversation For Beginners (A1)
KidsTeensDaily Conversation
A15
(1) - English Conversation For Beginners (A1)
KidsTravel EnglishTeens
FOR YOU
अनुशंसित वीडियो
B23
87 वाक्य
Data Engineering - Practice English Conversation
Daily ConversationUniversity Students
B11
299 वाक्य
Tactics for Listening Third Edition Developing Unit 15 Hotel Services
Travel EnglishDaily ConversationHigh School Students
C11
161 वाक्य
LanguageCert Academic Speaking
Daily ConversationUniversity Students
B26
209 वाक्य
Everyday Life English Conversations
Interview EnglishDaily ConversationUniversity Students
B1488 वाक्य
Real Conversations for English Speaking Practice | If you can Understand This, Your English Is Good
Daily ConversationHigh School StudentsUniversity Students
![[B1] How to Talk About your Work | English Listening & Speaking Practice](https://img.youtube.com/vi/akGBBzXmE8w/mqdefault.jpg)
B111
79 वाक्य
[B1] How to Talk About your Work | English Listening & Speaking Practice
Business EnglishInterview EnglishDaily Conversation
B15
332 वाक्य
Real-Life English Conversations | Learn to Speak with Confidence
Business EnglishDaily ConversationUniversity Students
B21
194 वाक्य
Practice English speaking skills - Easy to speak English fluently - Spoken English practice
Business EnglishDaily ConversationHigh School Students
B13
96 वाक्य
Improve Your English Speaking | Let’s talk about Artificial Intelligence (Shadow Reading)
Business EnglishDaily ConversationHigh School Students
B14
130 वाक्य
10 Minutes to Improve English Listening Skills - Practice English Conversations
Business EnglishInterview EnglishDaily Conversation
B11
282 वाक्य
Speak English Without Freezing | Ordering Food at a Restaurant | 21-Day Shadowing Challenge
Travel EnglishTeensDaily Conversation
B138
227 वाक्य
Improve English Listening Through Real-Life Conversation Shadowing | Repeat After Me
Business EnglishDaily ConversationHigh School Students
इस पाठ की शब्दावली और बोलने के सुझाव
यह स्पीकिंग पाठ वीडियो “English Conversations” पर आधारित है। सबसे ज़्यादा दोहराए गए शब्द ये हैं: software, project, program। इस वीडियो में शैडोइंग के लिए 667 वाक्य और 5524 शब्द हैं। बोला गया हिस्सा 38:52 लंबा है। वक्ता लगभग 142 शब्द प्रति मिनट की स्थिर गति से बोलता है, जो शैडोइंग के लिए आरामदायक है। 84% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं; बाकी शब्द अभ्यास से पहले देख लेना अच्छा रहेगा। इसके 667 वाक्यों में से 188 प्रश्न हैं, इसलिए यह प्रश्नों के लहजे और छोटे जवाबों के अभ्यास के लिए अच्छा है।
इस वीडियो की मुख्य शब्दावली
वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:
| शब्द | उच्चारण | अर्थ |
|---|---|---|
| diagram संज्ञा | /ˈdaɪ.ə.ɡɹæm/ | आलेख, मापचित्र |
| cloud संज्ञा | /ˈklaʊ̯d/ | मेघ, बादल |
| topic संज्ञा | /ˈtɑpɪk/ | प्रसंग, विषय |
| mouse संज्ञा | /maʊs/ | चूहा |
| chart संज्ञा | /t͡ʃɑɹt/ | लेखाचित्र, चार्ट |
| confused विशेषण | /kənˈfjuːzd/ | भ्रमित |
| architecture संज्ञा | /ˈɑː.kɪˌtɛk.t͡ʃə/ | वास्तुकला, स्थापत्य |
| hardware संज्ञा | /ˈhɑɹdˌwɛɹ/ | हार्डवेयर |
| filter संज्ञा | /ˈfɪltɚ/ | फ़िल्टर, साफी |
| wireless विशेषण | /ˈwaɪ(jə)ɹ.ləs/ | बेतार |
| assignment संज्ञा | /əˈsaɪn.mənt/ | नियुक्ति |
| artistic विशेषण | /ɑɹˈtɪs.tɪk/ | कलापूर्ण |
| scratch क्रिया | /skɹæt͡ʃ/ | नोचना |
| workshop संज्ञा | /ˈwɝk.ʃɑp/ | कर्मशाला, कारख़ाना |
| divide क्रिया | /dɪˈvaɪd/ | बांटना |
वीडियो में आने वाली फ़्रेज़ल वर्ब
| शब्द | उच्चारण | अर्थ |
|---|---|---|
| go ahead क्रिया | /ˌɡoʊ əˈhɛd/ | आगे बढ़ना |
दोहराने लायक वाक्य
वीडियो के छोटे, पूरे वाक्य जिन्हें आप रोज़ की बातचीत में इस्तेमाल कर सकते हैं:
- What are you working on?
- How can I help you?
- Have you used the computer in the conference room?
- You think this will happen again?
- Do you see the icon on your desktop?
इस वीडियो का व्याकरण
वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:
| संरचना | वीडियो में |
|---|---|
| शर्त वाले वाक्य if + उपवाक्य, will/would + क्रिया — शर्त और उसका नतीजा | If I were you, I'd replace |
| Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है | be updated · is scheduled · cannot be counted |
| Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है | has really fluctuated · have you done · Have you tried |
ध्यान देने योग्य उच्चारण
वक्ता 155 बार संक्षिप्त रूपों का प्रयोग करता है, जैसे I'm, I'll, don't। इन्हें वैसे ही छोटा बोलें जैसा आप सुनते हैं।
- “th” की ध्वनियाँ: thirty /ˈθɝti/, ethics /ˈɛθ.ɪks/, algorithm /ˈælɡəɹɪðm̩/
- “sh” और “zh” की ध्वनियाँ: presentation /ˌpɹɛzn̩ˈteɪʃn̩/, interaction /ˌɪn.təˈɹæk.ʃən/, efficient /ɪˈfɪʃənt/, collaboration /kəˌlæbəˈɹeɪʃən/, workshop /ˈwɝk.ʃɑp/
- लंबे शब्द — बलाघात सही रखें: interaction /ˌɪn.təˈɹæk.ʃən/, architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, collaboration /kəˌlæbəˈɹeɪʃən/, integrity /ɪnˈtɛɡɹəti/, eliminate /ɪˈlɪm.ɪ.neɪt/
हिंदी भाषियों के लिए मुश्किल ध्वनियाँ:
- /v/ और /w/ का फ़र्क़ — /v/ में ऊपर के दाँत निचले होंठ को छूते हैं, /w/ में होंठ गोल होते हैं: hardware /ˈhɑɹdˌwɛɹ/, wireless /ˈwaɪ(jə)ɹ.ləs/, suite /swiːt/, workshop /ˈwɝk.ʃɑp/, divide /dɪˈvaɪd/
- /z/ — इसे “ज” (/dʒ/) न बनाएँ: presentation /ˌpɹɛzn̩ˈteɪʃn̩/, confused /kənˈfjuːzd/, designer /dɪˈzaɪnɚ/, mechanism /ˈmɛk.ə.nɪ.zəm/, regards /ɹɪˈɡɑɹdz/
- शब्द की शुरुआत में s + व्यंजन — पहले “इ” न जोड़ें: suite /swiːt/, scratch /skɹæt͡ʃ/, static /ˈstæt.ɪk/, steady /ˈstɪdi/, specialize /ˈspɛʃəˌlaɪz/
इस वीडियो से अभ्यास कैसे करें
- पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
- सामान्य गति पर एक-एक वाक्य की शैडोइंग करें और हर वाक्य तब तक दोहराएँ जब तक आपकी लय वक्ता से न मिल जाए।
- अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर diagram, cloud, topic जैसे शब्दों पर ध्यान दें।
शैडोइंग तकनीक क्या है?
शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।