Answer:
B. Information security analysis.
Explanation:
<h2>
Answer:</h2>
Option D: All of above.
is the correct answer.
<h2>
Explanation:</h2>
Risk of Collision can be defined as a chance when two different bodies start bearing same position after some time of following some courses/situations.
In order to determine risk of collision, many procedures are used. Some of them include procedures like Long-range radar scanning, Systematic observation of objects detected by radar and watching the compass bearing of an approaching vessel are used.
According to Rule 7 (Risk of Collision):
All accessible sources that are right according to the faced circumstances shall be used for each vessel so that the collision risks (if any) are determined easily.
<h2>I hope it will help you!</h2>
Answer:
Explanation:
This is a project I already submitted, but I never received feedback. All my upcoming assignments will be based on this, so I wanted to make sure it is correct. I got this program to work as far as calculating the information, but I was hoping someone could please let me know if it meets the parameters/requirements?
I did attempt it. It works and adds the items exactly how the example showed in the video. However, I wanted to make sure my code is solid, and not just a mishmash or working because I got lucky, and if there is a better more solid way to do this I want to make sure I can. I do want feedback so I can learn and get better and I am trying my hardest. I always right out all the code I see here and try it and learn what it does piece by piece, because it helps me learn and improve. I also want to make sure it is going to work once I start the code for the next half of the requirements.
i cant really help they dont let us put codes on here
Answer:
Giving that: The following is a sequence of undo-log records written by 2 transactions T and U:
< START T >;
< T,A,10 >;
< START U >;
< U, B, 20 >;
< T, C, 30 >;
< U, D, 40 >;
< Commit U >;
< T, E, 50 >;
< Commit T >;
1. < START U >
Recovery action in this case will be undo(-1) and undo(0). All restored to its original Value
log records < T, A, 10 >, < T, abort >; as written out
2. < T, E, 50 >
Recovery action in this case will be undo(8) and redo(0). A and C is restored to its original value, B and D are set to 20 and 40
log records <T, C, 30 >, < T, A, 10 >, < T, abort > are written out
3. < Commit T >
Recovery action in this case will be redo(7) and redo(4). A and C are set to 10 and 30, B and D are set to 20 and 40
Answer:
1. Write to the Reader
2. Structure your report
3. Back up your report with data
4. Separate facts with opinions
Explanation:
1. Remember that you’re not writing the report for yourself. You’re probably writing for clients or management, so you need to know how familiar they are with the concepts and terminologies that your team uses. If they’re not well-acquainted with it, you may have to spend the first part of your report defining them so readers can follow along. Or, you might want to dumb it down a bit to layman’s terms and cut back on acronyms and jargon. A good way to practice this is to do the same with meeting notes.
2. One thing all reports should have in common is a form of structure. Ideally, you want to organize information into different segments so that your reader can identify relevant sections and quickly refer back to them later on. Common sections include a background or abstract to explain the project’s purpose, and a final summary of the document’s contents.
3. A good project report is going to have lots of data backing it up, whether it is defending the team’s performance or breaking down a successful project. Accurate charts, spreadsheets, and statistics are a must if the report is to have any degree of credibility when presented to clients. Many project management tools provide flexible project reporting features to help PM’s compile and present data in meaningful ways.
4. You should never confuse the two when writing a project report, especially if you are doing a post-mortem on a failed project. Opinions are subjective and should never be presented as absolutes. The report should be scrubbed of any personal views or preferences unless absolutely necessary. And if your opinion is required, be sure to clearly identify it as such. You may want to put it in an entirely different section, if possible.
Hope this helped
Kinda, really good at this stuff.