Subject-verb agreement

Subject-verb agreement is the grammatical rule that a verb must agree with its subject in number (singular or plural) and person (first, second, third). A singular subject takes a singular verb and a plural subject takes a plural verb. In the present tense, a third-person singular subject takes a verb ending in -s (he writes), while plural subjects take the base form (they write). The verb to be also changes: I am, he is, they are, he was, they were.

Why it is necessary in writing

• Clarity – mismatched verbs confuse the reader about who or what is doing the action.
• Correctness and credibility – errors make a report, letter or paper look careless and unprofessional, which matters especially in technical and business writing.
• Consistency and flow – the reader follows the sentence without stumbling.
• Formal standard – academic, official and published writing requires standard grammar.

Examples

1. The server runs all night. / The servers run all night. (singular and plural subjects take different verbs.)
2. The list of students is on the notice board. The real subject is list (singular), not students, which belongs to the prepositional phrase.
3. Neither the manager nor the engineers were present. With neither...nor, the verb agrees with the subject nearer to it (engineers).
4. Each of the programmers has a laptop. Each is singular.
5. Ram and Sita are working on the project. Subjects joined by and take a plural verb.

Other common rules: collective nouns (team, committee) take a singular verb when acting as one unit; indefinite pronouns such as everyone and somebody are singular; and "there is/are" agrees with the noun that follows.

Imaginary data: pass and failure rates (percent) of first, second and third year students, 2070-2074 BS

Failure rate = 100 - pass rate.

Graph 1: Pass rate (each # = 2 percent)

2070  Year 1 | ###############################            62%
2070  Year 2 | ##################################         68%
2070  Year 3 | #####################################      74%

2071  Year 1 | ################################           65%
2071  Year 2 | ###################################        70%
2071  Year 3 | ######################################     76%

2072  Year 1 | ##############################             60%
2072  Year 2 | ####################################       72%
2072  Year 3 | #######################################    78%

2073  Year 1 | ##################################         68%
2073  Year 2 | #####################################      75%
2073  Year 3 | ########################################   80%

2074  Year 1 | ###################################        71%
2074  Year 2 | ######################################     77%
2074  Year 3 | #########################################  83%

Graph 2: Failure rate (each # = 2 percent)

2070  Year 1 | ###################                        38%
2070  Year 2 | ################                           32%
2070  Year 3 | #############                              26%

2071  Year 1 | #################                          35%
2071  Year 2 | ###############                            30%
2071  Year 3 | ############                               24%

2072  Year 1 | ####################                       40%
2072  Year 2 | ##############                             28%
2072  Year 3 | ###########                                22%

2073  Year 1 | ################                           32%
2073  Year 2 | ############                               25%
2073  Year 3 | ##########                                 20%

2074  Year 1 | ##############                             29%
2074  Year 2 | ###########                                23%
2074  Year 3 | ########                                   17%

Interpretation

• The pass rate of every class rises over the five years: first year from 62% to 71%, second year from 68% to 77%, third year from 74% to 83%.
• Correspondingly, failure rates fall: first year from 38% to 29%, second year from 32% to 23%, third year from 26% to 17%.
• First year consistently has the highest failure rate, since students are adjusting to the new environment, and the rate dips only in 2072 (60% pass).
• The higher classes perform better because weaker students have already dropped out or been filtered.

Desktop, Laptop and Palmtop: Which Computer Suits You?

Computers today come in many forms, and choosing between a desktop, a laptop and a palmtop depends on what a person wants to do and where.

The desktop is the traditional workhorse. It has a separate system unit, monitor, keyboard and mouse, and is meant to stay in one place. Because it has more space for cooling and components, it offers the fastest processors, large memory, powerful graphics cards and big storage at the lowest price per unit of performance. Its parts are easy to upgrade and repair. However, it is bulky, needs a constant power supply and cannot be carried.

The laptop combines the processor, screen, keyboard, touchpad, battery and wireless networking in one portable unit weighing about 1.5 to 3 kg. It can be used in classrooms, offices or while travelling through Wi-Fi and a rechargeable battery. The price is higher for the same power, components are compact and so harder to upgrade, and heat and battery life limit continuous heavy use.

The palmtop, including today's tablets and smartphones, fits in a pocket or the palm. It is operated through a touchscreen or a tiny keyboard, runs a mobile operating system such as Android, and offers instant access to email, maps, calls and messaging. It is the easiest to carry and use, but its small screen, limited processing power and storage make it unsuitable for programming, video editing or lengthy typing.

In terms of access and ease, palmtops are the simplest and cheapest to start with, laptops are the balanced choice for students, and desktops are best for demanding fixed-location work. Technically, their difference lies in processor class (desktop CPUs with higher power draw versus low-power mobile chips), size of RAM and storage, display size and battery. In short, a person who needs power chooses a desktop, one who needs mobility with capacity chooses a laptop, and one who needs convenience chooses a palmtop.

A. Instructions for loading photos into a computer file and using them in a seminar report

Part 1 – Transferring the photos to the computer

1. Connect the camera or phone to the computer using a USB cable, or insert the memory card in a card reader. (Photos may also be sent by email or Bluetooth.)
2. Open This PC and select the device. Open the folder named DCIM.
3. Select the required photos, copy them (Ctrl + C).
4. Create a new folder on the computer, for example Seminar_Report_Photos, and paste (Ctrl + V) the photos into it.
5. Rename the files with meaningful names such as fig1_college_building.jpg, and safely eject the device.

Part 2 – Inserting the photos in the seminar report (Microsoft Word)

1. Open the report document and place the cursor where the photo should appear.
2. Click Insert > Pictures > This Device, browse to the folder, select the photo and click Insert.
3. Click the photo to resize it by dragging a corner handle (this keeps proportions). Use Picture Format > Wrap Text > In Line with Text or Square to position it.
4. Add a caption: right-click the picture and choose Insert Caption, for example "Figure 1: College building".
5. Use the photo in different parts of the report: the title/cover page (college logo), the introduction (the institution or the seminar venue), the body (diagrams, screenshots, equipment), and appendix (event photographs). Refer to each as "Figure 1" in the text.
6. Compress the pictures (Picture Format > Compress Pictures) to keep the file size small and save the report regularly.

B. Instructions for using Photoshop

1. Open Photoshop and choose File > Open to load the photograph.
2. Duplicate the background layer (Ctrl + J) so the original is not damaged.
3. Crop the image with the Crop tool (C) to remove unwanted parts; set size from Image > Image Size.
4. Adjust brightness/contrast and colour using Image > Adjustments > Brightness/Contrast, Levels or Hue/Saturation.
5. Remove blemishes with the Spot Healing Brush or Clone Stamp; use the Selection tools (Marquee, Lasso, Magic Wand) to isolate objects.
6. Add text with the Type tool (T) if a label is needed.
7. Save the working file as .psd (to keep layers) with File > Save As, and export the final picture as .jpg or .png through File > Export > Save for Web for use in the report.

Ramesh Sharma Baneshwor, Kathmandu Phone: 98XXXXXXXX Email: ramesh.sharma@example.com

Date: 12 Magh 2074

The Administration Officer Toyota Nepal Maharajgunj, Kathmandu

Subject: Application for the post of Computer Engineer

Dear Sir/Madam,

With reference to your advertisement for the post of Computer Engineer for a period of seven years, I would like to apply for the position. I hold a Bachelor's degree in Computer Engineering from Tribhuvan University and believe that my qualifications and enthusiasm match the requirements of the post.

During my studies I worked on projects in database systems, networking and software development, and completed an internship in which I maintained a computer network and troubleshot hardware and software problems. I am skilled in programming languages such as Java and C++, in SQL, and in the installation and administration of networks. I am a quick learner, a responsible team member and ready to work for the full term offered.

I have enclosed my biodata along with copies of my certificates and citizenship. I would welcome an opportunity to meet you in person and demonstrate my abilities. I assure you that I will perform my duties sincerely if I am selected.

Thank you for your kind consideration.

Yours faithfully, Ramesh Sharma

Enclosed: Biodata, copies of academic certificates, citizenship certificate and photographs.

---

BIODATA

Academic qualification

Experience: Internship (3 months), network and system support, Computer Solutions Pvt. Ltd., Kathmandu.

Skills: Java, C++, SQL, networking, web design, MS Office. Languages: Nepali, English, Hindi.

References: Available on request.

Devices such as Wi-Fi, Bluetooth, Android and EDGE have changed the way we communicate. On the one hand, they offer great advantages. Wi-Fi provides fast wireless internet access in homes, colleges and offices without any cables, whereas Bluetooth allows short-range sharing of files and connection of devices such as headphones and keyboards at no cost. Android phones, moreover, put thousands of free and paid applications, maps and email in the hand of any user at a low price, that is, a single device serves as a phone, camera and computer. EDGE, for example, enabled mobile internet access in areas where better networks were not available. In brief, these technologies save time, money and effort and make information easily accessible.

However, these devices have disadvantages as well. Wi-Fi and Bluetooth connections can be hacked if they are not secured with strong passwords, that is, personal data may be stolen. EDGE is slow compared with modern networks, whereas Android phones have short battery life and can be infected by malicious applications. Moreover, heavy use may distract students and reduce face-to-face communication, and the radio waves are claimed by some to affect health. On the other hand, such problems can be reduced by careful use and updates, for example, by using secure passwords and installing applications from trusted sources only.

Himal Computer Centre New Road, Kathmandu, Nepal Phone: 01-4XXXXXX Email: info@himalcomputer.example.com

Date: 15 Poush 2075

The Sales Manager Beijing Digital Technology Co. Ltd. Haidian District, Beijing People's Republic of China

Subject: Proposal for regular supply of assembled computers and computer parts

Dear Sir/Madam,

We are running a computer shop at New Road, Kathmandu, selling desktop and laptop computers, accessories and services to individuals, schools, colleges and offices. Our customers are increasingly asking for good quality assembled computers and parts at affordable prices, and we have learned about the reputation of your company as a manufacturer. We would therefore like to establish a business relation with you for the regular supply of assembled computers and computer parts.

We are interested in the following items on a monthly basis: 50 assembled desktop computers, 30 laptops, and spare parts such as processors, motherboards, RAM, hard disks, monitors, keyboards and power supplies. We would appreciate it if you would send us your latest catalogue, a price list with technical specifications, minimum order quantities, and the discount you offer for regular bulk orders.

Payment. We propose payment by an irrevocable Letter of Credit opened through a Nepali commercial bank for the first order. After a few successful transactions, we would like to move to telegraphic transfer with 30% advance and 70% against shipping documents, or credit of 30-60 days. Prices should be quoted on a CIF Kathmandu (Birgunj / Kolkata route) basis in US dollars.

Possible problems. We would like to discuss in advance matters that often cause trouble in international trade: delays and damage in transport and customs clearance, since Nepal is a landlocked country; fluctuation of the exchange rate; defective or dead-on-arrival items, for which we request a warranty of at least one year and replacement or refund; availability of after-sales service and spare parts; and compliance with Nepal's import regulations and taxes. We suggest that these terms be clarified in a written agreement.

We would be pleased to send you our company profile and bank references. We hope for your early and favourable reply and look forward to a long and mutually beneficial relationship.

Yours faithfully,

Suresh Gurung Proprietor Himal Computer Centre

Computers Are Reshaping Higher Education

A feature for students, teachers and campus administrators

Introduction

A decade ago a college library, a blackboard and a printed syllabus were the whole of higher education for most Nepali students. Today a laptop or a smartphone gives the same student access to journals, video lectures, online classrooms and global research communities. The computer has moved from the computer lab into every part of campus life.

In the classroom

Teachers now prepare lessons with presentation software, simulations and short videos. Subjects that are hard to imagine, such as the working of a CPU, a chemical reaction or the structure of a bridge, can be shown on screen. Learning management systems such as Moodle and Google Classroom let teachers share notes, set assignments and mark work online.

Research and the library

Digital libraries and databases (IEEE Xplore, JSTOR, Google Scholar, HINARI) give students access to thousands of journals that no campus shelf could hold. Reference managers, statistical packages and plagiarism checkers make research faster and more honest.

Distance and blended learning

Online courses and video conferencing allow students in remote districts to attend classes without leaving home. During the COVID-19 lockdowns, universities in Nepal continued teaching through Zoom and Google Meet, showing how important computers have become for continuity of education.

Administration

Online admission forms, result publication, exam routines, fee payment and attendance records save time and reduce paperwork. Students can check results from home instead of queuing at the campus office.

Challenges

• Unequal access: many rural students lack reliable electricity, internet and devices.
• Distraction and over-dependence: social media and copy-paste work can weaken real learning.
• Cost and training: institutions need money for equipment and teachers need regular training.
• Security and privacy of student data.

Conclusion

Computers do not replace good teachers, but they multiply what teachers and students can do. If universities invest in infrastructure, digital skills and fair access, computers can make higher education in Nepal wider, cheaper and of better quality.

Facebook, Twitter and Google+ for communication

In general, social networking sites have changed the way people exchange information. Facebook, Twitter and Google+ each serve communication in a different way, and each has advantages as well as disadvantages.

Advantages

At first, the most obvious benefit is speed and reach. A message posted on Facebook or Twitter reaches hundreds of people within seconds, whereas a letter or even an email takes much longer to circulate. Facebook supports long posts, photos, video, groups and pages, so it is useful for keeping in touch with friends and for organising class or club activities. Twitter limits each message to a short length, which forces writers to be concise; it is valuable for news, announcements and following experts. Google+ offered "circles", which let a user share content only with selected groups such as family, classmates or colleagues, and it was integrated with Gmail, YouTube and Hangouts.

All three are free, work on mobile phones, allow two-way feedback through comments, replies and likes, and let organisations promote products and services at low cost. In brief, they are cheap, fast and interactive.

Disadvantages

However, these platforms also have serious drawbacks. Though they connect people, they can reduce face-to-face communication and cause addiction and wasted time. Even though privacy settings exist, personal data can be misused, accounts can be hacked, and posts can remain on the internet permanently. Rumours, hate speech and fake news spread as fast as true information. Twitter's short messages may lead to misunderstanding because tone and detail are lost, whereas Facebook's open nature may expose private matters to employers or strangers. Google+ failed to attract enough users and was finally shut down for consumers, which shows the risk of relying on a single service.

Conclusion

Finally, social media are powerful communication tools if used responsibly. Users should protect their privacy, verify information before sharing and balance online contact with real-life interaction.

Importance of tables, illustrations and graphics in academic writing

Words alone are often not the best way to present data, structure or processes. Visual elements make academic writing clearer, shorter and more convincing.

1. Tables

• Present exact numbers and facts in rows and columns so that comparison is easy.
• Save space: a table can replace paragraphs of figures.
• Example: comparing the marks of three sections.

2. Illustrations (diagrams, drawings, photographs, flowcharts)

• Explain how something looks or works, which is hard to describe in words.
• Help readers with different language levels understand quickly.
• Examples: a block diagram of a computer, a flowchart of an algorithm, a map showing the study area, a photograph of a laboratory set-up.

3. Graphic presentation (graphs and charts)

• Show trends, proportions and relationships at a glance.
• Examples: a line graph of enrolment over ten years, a bar chart comparing results of colleges, a pie chart of the share of internet use by activity.

General benefits

• They attract attention and break up long text.
• They make complex information easy to remember.
• They support arguments with evidence and add credibility.
• They help readers who skim, since key results are visible immediately.

Guidelines for use

• Number each table and figure and give it a clear title or caption (for example, Table 1, Figure 2).
• Refer to it in the text and explain what it shows.
• Keep it simple and readable; label axes and units.
• Place it close to the related discussion and acknowledge the source if it is not your own.
• Use only when it adds value; do not decorate.

Simple sentence

A simple sentence contains one independent clause, that is, one subject and one finite verb (the subject or verb may be compound), and expresses a complete thought.

1. The students submitted their reports.
2. Ram and Sita study computer science.
3. The server crashed during the test.

Compound sentence

A compound sentence contains two or more independent clauses joined by a coordinating conjunction (for, and, nor, but, or, yet, so) or by a semicolon. Each clause could stand alone.

1. The network was slow, so we restarted the router.
2. She wrote the code, and he tested it.
3. I wanted to attend the seminar, but the bus was late.

Complex sentence

A complex sentence contains one independent clause and at least one dependent (subordinate) clause, introduced by a subordinating word such as because, although, when, if, who, which, that.

1. Although it was raining, the students reached the lab on time.
2. The engineer who designed the system explained it to the clients.
3. If you save the file regularly, you will not lose your work.

Technical communication

Technical communication is the process of conveying specialised, practical information about science, engineering, computing, medicine or other technical fields to a defined audience, so that they can understand it, make decisions or perform a task. Examples are user manuals, reports, proposals, instructions, specifications, data sheets and online help.

How it differs from other types of communication

Features that make communication technical

1. Audience awareness: content and vocabulary are matched to the readers' knowledge and needs.
2. Clear purpose: every document aims to inform, instruct or recommend.
3. Accuracy and objectivity: statements are based on facts, measurement and evidence.
4. Clarity and conciseness: short sentences, no unnecessary words, one meaning only.
5. Technical vocabulary and data: use of terms, numbers, units, formulae and codes.
6. Visual support: tables, graphs, diagrams and illustrations.
7. Organisation and format: logical order, headings, numbered steps, standard layouts.
8. Documentation and sources: references and acknowledgement of data.
9. Ethical and professional tone: honest, impersonal and courteous.

Technical writing

Technical writing is the preparation of documents that communicate technical, scientific or specialised information clearly and accurately to a particular audience so that they can understand it, use a product, follow a procedure or take a decision. It is common in computing, engineering, medicine, business and government. Typical forms are user manuals, instructions, proposals, reports, specifications, white papers, memos, emails, online help and web content.

Characteristics of technical writing

1. Audience centred: the writer analyses who will read the document, what they already know and what they need, and adjusts vocabulary and detail accordingly (an expert and a beginner need different manuals).
2. Purpose oriented: every document has a clear purpose such as to inform, instruct, persuade or record, and it should be stated early.
3. Clarity: simple words, short sentences, active voice and one meaning. Jargon is explained or avoided.
4. Accuracy: facts, figures, units and names must be correct and verifiable, since errors may cause loss or danger.
5. Conciseness: no padding; each sentence should add information. Readers are busy.
6. Objectivity: impersonal, factual tone, free from emotion and bias; opinions are supported by evidence.
7. Coherence and organisation: logical order, with headings, subheadings, numbered steps, bullet points and transitions so that readers find information quickly.
8. Use of visuals: tables, charts, diagrams, screenshots and photographs support the text.
9. Standard format and style: use of conventional layouts, consistent terminology, typography and document design.
10. Completeness and honesty: gives all the information the reader needs, acknowledges sources and follows ethical and legal standards.
11. Accessibility and usability: tested with real users, readable and easy to navigate.
12. Collaborative: often produced by teams of writers, subject experts, editors and designers.

Technical writing for internal and external audiences

The statement is true because technical documents are written both for people inside the organisation and for people outside it, and the content, tone and format change accordingly.

Internal audience

These are readers within the same organisation: managers, supervisors, colleagues, other departments and subordinates. Communication supports the daily work of the organisation.

• Examples: memos, internal emails, progress reports, meeting minutes, incident reports, policy and procedure manuals, project proposals to management, training material, feasibility studies.
• Characteristics: readers know the company, its terms and its projects; tone may be less formal; the document often gives instructions, records activity or helps in decisions. A memo informing staff of a new office timing, or a monthly progress report from a software team to the project manager, are typical examples.

External audience

These are readers outside the organisation: customers, clients, suppliers, government agencies, investors, the media and the general public.

• Examples: user manuals, product brochures, websites, press releases, proposals to clients, annual reports, letters to customers, tender documents, technical specifications, FAQs, warranty statements.
• Characteristics: readers know little about the organisation, so more explanation is needed; tone is formal, polite and persuasive; the document represents the company's image, so accuracy and legal correctness are vital. A user manual for a mobile app, or a press release announcing a new product, are examples.

Many documents serve both

A project report may be read by the internal management and also submitted to an external donor; a proposal may be prepared internally and sent to a client; a safety manual is used by staff and shown to inspectors.

Conclusion

Because technical writing supports decisions and actions inside and outside an organisation, a technical writer must identify the audience first and then choose content, vocabulary, tone and format to suit it.

Writing for the web

People read on screens differently from print: they scan, jump between pages, and leave quickly if they cannot find what they need. A writer should keep the following in mind.

1. Know the audience and purpose: identify who will visit the site and what they want (information, a product, help) and write for that.
2. Put the most important information first (inverted pyramid): conclusion and key facts at the top, details later, because many readers read only a few lines.
3. Make text scannable: use meaningful headings and subheadings, short paragraphs, bullet and numbered lists, bold key terms, and tables.
4. Be concise: use roughly half the words of print; simple words, short sentences, active voice, no jargon.
5. Chunk content: one idea per paragraph or page; break long material into linked pages.
6. Write useful links: descriptive link text ("download the admission form") rather than "click here"; avoid broken links; link to related pages.
7. Organise and make navigation easy: logical structure, clear menus, a search box, breadcrumbs, consistent layout so that users find information in few clicks.
8. Use visuals wisely: relevant images, graphics and video with alternative text, optimised so pages load fast.
9. Design for readability and accessibility: readable fonts, good contrast, enough white space, alt text, captions and compatibility with screen readers; works on mobile devices and different browsers.
10. Search engine optimisation: use keywords naturally in titles, headings and descriptions so that the page can be found.
11. Keep content current and accurate: show dates, update regularly, remove outdated pages.
12. Tone and credibility: consistent, friendly yet professional voice; proofread; give contact details and sources; respect copyright and privacy.
13. Test with users: check usability and gather feedback.

Press release

A press release (news release) is a short, official document issued by an organisation to the media to announce something newsworthy, such as a product launch, event, achievement, appointment or policy, in the hope that it will be published or broadcast.

Steps to produce an effective press release

1. Decide that you have real news: it should be timely, relevant and interesting to the public, not an advertisement.
2. Identify the audience and media: choose the newspapers, TV, online media or journalists most interested in the topic.
3. Write a strong headline: short, specific, in active voice, and summarising the news.
4. Write the lead paragraph: answer who, what, when, where, why and how in the first paragraph (inverted pyramid).
5. Add supporting details: background, facts, figures and a short quotation from a spokesperson, in order of importance.
6. Use a standard format: letterhead or organisation name, "For immediate release" or release date, dateline (city, date), body, a short "About the organisation" paragraph, contact person with phone and email, and "###" or "END" at the close. Keep to one page.
7. Use an objective, clear and concise style: third person, no exaggeration or jargon.
8. Attach visuals if useful (photos, logo) and links.
9. Proofread carefully for facts, names and spelling.
10. Distribute and follow up: send to the right journalists at a suitable time, by email or through an agency, and be ready to answer questions.

How I Learned Computer Programming

I know more about computer programming than about any other subject, and the way I acquired this knowledge is a story of curiosity, practice and good guidance.

My interest began in school, when a teacher showed us a small program on the computer that drew shapes on the screen. I was surprised that a few lines of text could make the machine do something visible. At home I had no computer, so I used the school lab during free periods and wrote down code in a notebook to try later.

My first formal learning came from a short course in C programming after the SEE examinations. The instructor explained variables, loops and functions with simple examples, and I solved every exercise in the book. I learned that reading is not enough; programming is learnt by writing code, making mistakes and fixing them. Debugging taught me patience and logical thinking.

Later I used free resources on the internet: tutorials, video lectures and question-and-answer forums. When I got stuck, I searched for answers and read other people's programs. I also built small projects, such as a student record system and a simple calculator, which gave me confidence. At college, subjects such as data structures and object-oriented programming gave me a theoretical base, and working with friends on group projects taught me teamwork and the use of version control.

In short, I acquired my knowledge through a spark of curiosity, a good teacher, regular practice, self-study with online resources and real projects. I am still learning, because technology keeps changing.

Ramesh Karki Software Engineer Himal Soft Pvt. Ltd. Kathmandu

15 Kartik 2078

The Managing Director Himal Soft Pvt. Ltd. Baneshwor, Kathmandu

Subject: Request for increase in incentives for hardworking employees

Dear Sir/Madam,

I am writing, on behalf of myself and my colleagues, to request that the company consider increasing the incentives given to hardworking employees.

Over the past year our company has completed several large projects ahead of schedule, and many staff members have regularly worked extra hours, taken on additional responsibilities and trained new colleagues. Their efforts have helped to increase client satisfaction and the company's revenue. At the same time, the cost of living has risen, and the present incentives do not fully recognise the extra effort of the best performers.

I therefore respectfully suggest that the company:

1. increase the performance bonus for employees who meet or exceed their targets;
2. introduce a monthly or quarterly "best employee" award with a cash prize; and
3. provide extra allowances for overtime and for working on urgent projects.

Better incentives would motivate staff, improve retention of skilled employees and encourage others to work harder, which will benefit the company in the long run.

I would be grateful if you would consider this request and give us an opportunity to discuss it. Thank you for your time and for your continued support.

Yours faithfully,

Ramesh Karki Software Engineer

INCIDENT REPORT

To: Mr. Suman Sharma, Head of Department, Computer Science From: Anita Rai, Lab Assistant Date: 12 Poush 2078 Subject: Failure of the Computer Lab server during the practical examination

Audience analysis

The reader is the head of department, who is familiar with the lab but was not present at the time. He needs a brief, factual account, the cause and the action taken so that he can decide on preventive steps. The tone is formal and objective, and technical details are limited to what is necessary.

1. Summary

On 10 Poush 2078 at about 11:15 a.m., the lab server stopped working during the sixth semester practical examination, interrupting the examination for 45 minutes.

2. Description of the incident

• 11:15 a.m.: 40 student computers lost access to the shared database and examination files.
• 11:20 a.m.: I informed the examiner and the IT technician.
• 11:25 a.m.: The technician found that the server's power supply had failed after a sudden voltage fluctuation, and the UPS had no battery backup left.
• 11:30 to 12:00: The backup server was configured, and student files were restored from the previous night's backup.
• 12:00 noon: The examination resumed, and the students were given 45 minutes of extra time.

3. Impact

No student data was lost, but the examination was delayed by 45 minutes and some students were stressed.

4. Cause

Voltage fluctuation combined with an old power supply and a UPS that was not maintained.

5. Recommendations

1. Replace the server power supply and the UPS batteries.
2. Test the backup server every month.
3. Keep a stabiliser and an emergency generator in good condition.
4. Prepare a written emergency procedure for examinations.

Prepared by: Anita Rai

To: all-staff@technova.com.np From: manager@technova.com.np Subject: Request for a few extra hours each week for our upcoming projects

Dear Team,

I hope you are all well. First of all, thank you for the excellent work you did over the last quarter. Because of your efforts we delivered all three major projects on time, and our clients have given us very positive feedback.

We now have more orders than we can complete in normal hours, including two new projects for banking clients. To meet these deadlines without losing quality, I would like to ask each of you to work about three additional hours per week (for example, one hour on three evenings or one Saturday morning) for the next three months. The timing can be arranged with your team leader.

This will benefit both the company and you:

• Overtime hours will be paid at 1.5 times the normal hourly rate, or you may take compensatory leave if you prefer.
• A quarterly bonus will be given to teams that meet their targets.
• Snacks and transport will be provided for late hours.
• Successful delivery will strengthen the company, creating more job security, promotions and training opportunities.

This request is voluntary, and I understand that some of you may have family or study commitments. Please talk to your team leader by Friday so that we can plan fairly. You may also contact me directly with any concerns or suggestions.

Thank you again for your hard work and commitment. Together we can make TechNova stronger.

Best regards,

Bikash Shrestha Manager, TechNova Pvt. Ltd. Phone: 01-5551234

PRESS RELEASE

FOR IMMEDIATE RELEASE

Himalaya College of Information Technology to Organise Annual IT Fair 2078

Students to showcase innovative projects; entry free for the public

Kathmandu, 20 Falgun 2078 - Himalaya College of Information Technology (HCIT), Baneshwor, will organise its Annual IT Fair 2078 on 5 and 6 Chaitra at the college premises. The theme of the fair is "Digital Nepal: Ideas for Tomorrow".

More than 60 student projects, including mobile applications, web portals, robotics, and artificial intelligence models, will be displayed. The fair will also include a programming contest, a poster competition, career counselling sessions with leading IT companies, and a panel discussion on opportunities in the IT sector.

"The fair gives students a place to turn classroom learning into real solutions and to meet employers," said Mr. Hari Prasad Adhikari, Principal of HCIT. "We invite the public, parents, school students and the media to join us."

The fair will be inaugurated by Mr. Rajan Thapa, Chief Executive Officer of a leading software company, at 10:00 a.m. on 5 Chaitra. It will remain open from 10:00 a.m. to 5:00 p.m. on both days. Entry is free.

About HCIT: Established in 2060 B.S., Himalaya College of Information Technology offers B.Sc. CSIT and BCA programmes affiliated to Tribhuvan University and has trained more than 2,000 graduates.

Media contact: Sunita Gurung, Public Relations Officer Phone: 01-4412345 | Email: pr@hcit.edu.np

How to Begin a Career in the IT Field

Follow these steps in order.

1. Choose a direction. Decide which area interests you: software development, web design, networking, database administration, cyber security, data analysis, testing or support. Read job advertisements to see which skills are in demand.
2. Build a strong foundation. Complete a degree such as B.Sc. CSIT, BCA or BE Computer, or an equivalent course. Learn programming basics, data structures, databases, networking and operating systems.
3. Learn practical skills.
   1. Pick one programming language (for example Python, Java or JavaScript) and practise daily.
   2. Learn Git, SQL and basic Linux commands.
   3. Use free online courses, tutorials and documentation.
4. Create projects. Build at least three real projects, such as a website, a mobile app or a management system, and publish the code on GitHub.
5. Get experience. Apply for an internship or volunteer work, or take freelance and open-source tasks. Even a few months in a company teaches teamwork and deadlines.
6. Obtain certifications if useful. Examples include CCNA, AWS, Oracle or Microsoft certificates, depending on your field.
7. Develop soft skills. Practise communication, teamwork, time management and problem solving. Learn to write clear emails and documentation.
8. Prepare your resume and online profile. Prepare a one-page resume, a LinkedIn profile and a portfolio. Practise interview questions and coding tests.
9. Network. Attend meet-ups, seminars, hackathons and job fairs; ask seniors for advice.
10. Apply and keep learning. Apply to many companies, accept feedback after rejections, and keep updating your skills, because technology changes quickly.

Do not wait for perfection. Start small, practise regularly and be patient.

ANISH KUMAR SHRESTHA Baneshwor, Kathmandu, Nepal | +977-9841234567 | anish.shrestha@email.com LinkedIn: linkedin.com/in/anishshrestha | GitHub: github.com/anishs

Objective

To obtain the position of Software Developer in a reputed IT company, where I can use my programming, database and teamwork skills to build reliable software and grow professionally.

Work Experience

Software Developer Intern, Himal Soft Pvt. Ltd., Kathmandu (Shrawan 2077 to Poush 2077)

• Developed modules of a student information system using Java and MySQL.
• Fixed more than 30 bugs and wrote test cases for the login and report modules.
• Worked in an agile team of five and used Git for version control.

Freelance Web Developer (2076 to 2077)

• Designed and built websites for three small businesses using HTML, CSS, JavaScript and PHP.

Education

• B.Sc. CSIT, Tribhuvan University, Himalaya College of Information Technology (2074 to 2078), CGPA 3.6
• +2 Science, Kathmandu Model College (2072 to 2074), 74%
• SEE, Little Angels' School (2072), GPA 3.8

Skills

• Programming: Java, C, Python, JavaScript
• Web and databases: HTML, CSS, PHP, MySQL, PostgreSQL
• Tools: Git, Linux, VS Code, Postman
• Soft skills: communication, teamwork, problem solving, time management
• Languages: Nepali (native), English (fluent), Hindi (fluent)

Projects

• Online Library Management System (final-year project), built with Java Spring and MySQL.
• E-commerce website with payment integration (freelance).

Achievements and Training

• First place, college programming contest 2077.
• Certificate in Web Development, 2076.

References

Available on request.

Speech at the Inaugural Session of the College IT Fair

Respected Chief Guest, Principal, teachers, honourable guests, dear students and friends,

Good morning, and namaste to you all.

It gives me great pleasure to speak at the inauguration of this year's College IT Fair. On behalf of the organising committee, I warmly welcome all of you.

Information technology is no longer a separate subject; it is a part of banking, education, health, agriculture and government. As Nepal moves toward a digital economy, we need young people who can imagine, create and solve problems with technology. This fair is our attempt to give our students that opportunity.

Over the next two days you will see more than fifty projects built by our students, including mobile apps, web portals, robots and data-analysis tools. There will also be a programming contest, a quiz, workshops and talks by industry professionals. I invite every visitor to ask questions, try the demonstrations and share ideas with our students.

I would like to thank our Principal and teachers for their guidance, our sponsors for their support, and all the volunteers who worked day and night to make this event possible. I also thank the guests for taking time to be with us.

To my fellow students, I say: learn by doing, be curious, work as a team, and do not be afraid of failure. Today's small project can become tomorrow's start-up.

I wish the fair a great success. Thank you.

Skills needed to improve technical writing

1. Audience analysis: the ability to find out who the readers are, what they know and what they need.
2. Language skills: correct grammar, spelling, punctuation and a good vocabulary; clear, concise sentences in the active voice.
3. Technical knowledge: understanding of the subject, so that information is accurate.
4. Research skills: finding, evaluating and citing reliable sources.
5. Organisation skills: planning and structuring content logically with headings, lists and transitions.
6. Visual and design skills: using tables, charts, diagrams, layout and typography effectively.
7. Editing and proofreading: revising for clarity, consistency and errors.
8. Tool skills: word processors, presentation software, document and version-control tools, and web publishing.
9. Collaboration and communication: working with experts, editors and reviewers, giving and accepting feedback.
10. Ethical awareness: honesty, avoiding plagiarism, and respect for copyright and confidentiality.

How to acquire these skills

• Read good technical documents, manuals and reports and study their style.
• Practise writing regularly: reports, emails, instructions, summaries, and rewrite them several times.
• Take courses, workshops and online tutorials in technical and business writing, and use style guides.
• Get feedback from teachers, peers and supervisors, and revise accordingly.
• Use grammar and spell-check tools, but also proofread by reading aloud.
• Study the subject deeply and ask experts questions.
• Learn software tools through practice.
• Join writing groups, internships or projects where you write for real audiences.
• Keep a vocabulary and a checklist of common errors.

Collaborative writing

Most technical documents, such as large manuals, proposals, software documentation and project reports, are too big and complex for one person. They are prepared by teams of writers, subject experts, editors, designers and reviewers. Collaboration is therefore very important: it combines knowledge, saves time and improves the quality of the final document.

Advantages

1. Wider knowledge and skills: different members contribute technical, language, design and research expertise.
2. Better quality: ideas are discussed and checked by others, so errors and weaknesses are found early.
3. Saves time: work is divided and done in parallel, so large documents are completed faster.
4. Multiple perspectives: more creative ideas and better understanding of different audiences.
5. Shared responsibility and motivation: members support one another and learn new skills.
6. Consistency through review: peer editing and feedback improve accuracy and clarity.
7. Teamwork skills: communication, negotiation and leadership are developed.

Disadvantages

1. Conflict: disagreement over ideas, style or credit may cause tension.
2. Time-consuming discussion: meetings and negotiation may delay decisions.
3. Unequal contribution: some members may do less ("social loafing"), while others do too much.
4. Inconsistent style and voice: different writers produce uneven tone, format and terminology.
5. Coordination problems: version control, deadlines, and merging of sections need management.
6. Unclear responsibility: when something goes wrong, it is hard to assign blame.
7. Personality and communication problems: dominating members may silence others.

Conclusion

The benefits usually exceed the drawbacks if the team has clear roles, a schedule, style guidelines, shared tools (for example Google Docs or Git) and a good leader who handles conflict.

Effective communication

Effective communication is the exchange of information in which the receiver understands the message exactly as the sender intended, and responds or acts as desired. It is not enough to send a message; it must be received, understood and, where necessary, acted upon.

Principles of effective communication (the "7 Cs" and related principles)

1. Clarity: express the message in simple, unambiguous language; one main idea at a time.
2. Conciseness: use as few words as are needed; avoid repetition and padding.
3. Completeness: give all the information the receiver needs (who, what, when, where, why, how) so that they can act.
4. Correctness: facts, figures, grammar and spelling must be accurate; use the appropriate format and tone.
5. Concreteness: use specific facts, figures and examples instead of vague statements.
6. Courtesy: be polite, respectful and considerate, and use "you attitude", which keeps the reader's goodwill.
7. Consideration (audience orientation): know the receiver's background, needs and feelings, and adapt the message.
8. Coherence and organisation: arrange ideas in logical order with proper connections.
9. Clear purpose: know why you are communicating.
10. Appropriate channel and timing: select the right medium (oral, written, email, meeting) and send at a suitable time.
11. Feedback: encourage questions and responses to confirm understanding.
12. Active listening and removal of barriers: reduce noise, language differences and prejudice that distort the message.

Oral reporting and professional success

An oral report is a spoken presentation of information, such as a progress update, a project presentation, a briefing in a meeting or a proposal to a client. The statement is true because in most professions people are judged and rewarded largely on how well they communicate their work.

Reasons

1. Visibility and impression: managers and clients often form their opinion of you from presentations and meetings. A confident, well-organised report shows competence and professionalism.
2. Decision making: managers and customers decide on projects, funding, promotions or purchases after listening to oral reports. A weak presentation can lose a good idea.
3. Immediate feedback: speaking allows questions, clarification and discussion on the spot, which builds understanding and trust.
4. Persuasion: voice, emphasis and visuals help to persuade people in ways that written reports cannot.
5. Frequency: professionals give oral reports daily, in team meetings, client calls, reviews and training sessions.
6. Leadership and teamwork: good speakers inspire and coordinate others, and are often promoted to leadership roles.
7. Credibility of the organisation: representatives who speak well enhance the image of the company.
8. Competitive advantage: technical skill alone is not enough; employers look for communication skills, so people who report well stand out in interviews and careers.

Conclusion

A talented engineer or IT professional who cannot explain work clearly may go unnoticed, whereas one who can will be understood, trusted and promoted. Oral reporting skill can therefore decide professional success. To improve, plan the content, know the audience, practise, use simple visuals, maintain eye contact and manage time.

Analysis of a Group Project Experience

Experience

Last semester my team of four classmates developed a student attendance management system as a mini project. At first we were unsure how to divide the work, but after a meeting we assigned roles: one member handled the database, two wrote the interface and logic, and I worked on testing and documentation. We met twice a week and used Git and a shared document to coordinate. Overall the experience was positive and instructive, although at times difficult.

Benefits

• Shared skills: each member brought different strengths, so the project was better than any one of us could have made alone.
• Faster progress: work done in parallel meant that we finished before the deadline.
• Learning from peers: I learnt version control from a teammate and improved my understanding of SQL.
• Better ideas and fewer errors: code reviews and discussion found mistakes early.
• Soft skills: communication, leadership, negotiation and time management improved.
• Motivation: supporting one another made us more committed.

Drawbacks

• Unequal workload: one member missed several meetings and the others had to cover his tasks.
• Disagreements: we argued over design choices, which wasted time.
• Scheduling problems: finding a common time was hard because of different class routines.
• Inconsistent work: the style of code and documentation differed until we agreed on standards.
• Dependence: delay by one person delayed everyone.

Conclusion

The advantages outweighed the problems. The project taught me that successful teamwork needs clear roles, regular meetings, shared tools, open communication and mutual respect. In future I would set deadlines and ground rules at the beginning.

FAQ: Admission to B.Sc. CSIT at Tribhuvan University

1. What is B.Sc. CSIT? It is a four-year (eight-semester) bachelor's programme in Computer Science and Information Technology offered by Tribhuvan University (TU) through its affiliated colleges.

2. Who is eligible to apply? Applicants must have passed the 10+2 (Science, or Management with Mathematics), A-level or an equivalent programme recognised by TU, with at least a second division or a minimum CGPA of 1.8, and with Mathematics or Computer Science studied at the +2 level. Candidates should check the latest eligibility notice.

3. Is there an entrance examination? Yes. Candidates must pass the CSIT Entrance Examination conducted by the TU Institute of Science and Technology (IOST) Dean's Office.

4. When is the entrance examination held? The IOST publishes a notice, usually after the +2 results, with dates for the application, examination and results. Watch the TU/IOST website and national newspapers.

5. How do I apply? Fill in the online entrance application form on the IOST/TU admission portal, upload your photograph and academic documents, and pay the examination fee as prescribed in the notice.

6. What documents are needed? Certificates and mark sheets of SEE and +2 (or equivalent), character certificate, transfer certificate, citizenship certificate or passport, passport-size photographs, and an equivalence letter for foreign qualifications.

7. What is the entrance exam syllabus? Questions are objective (multiple choice) and cover Mathematics, English, Physics, Chemistry and general knowledge/aptitude, according to the syllabus published by TU.

8. How are students selected? Candidates are ranked by their entrance marks, and seats are offered according to merit and the quota for each college. Seat numbers per college are limited.

9. How do I get admitted into a college? After the result, check the list of qualified candidates, choose a college according to your rank, go to the college with your documents, and pay the admission fees within the given deadline.

10. How much will the fees be? Fees vary by college. TU sets a minimum, and colleges publish their own fee structures, so ask each college. Scholarships are available for top-ranking students.

11. Where can I get more information? From the IOST, Tribhuvan University, Kirtipur, from the TU website, and from the admission offices of the CSIT colleges.

PROGRESS REPORT

To: Mr. Prakash Adhikari, Project Supervisor From: Nisha Thapa, B.Sc. CSIT Sixth Semester Date: 25 Ashwin 2079 Subject: Progress report on the "Online Student Feedback System" project (period: 1 Bhadra to 25 Ashwin 2079)

1. Introduction

This report summarises the progress made on the college project to develop a web-based student feedback system, since the project proposal was approved on 1 Bhadra. The project is due on 30 Poush 2079.

2. Work completed

• Requirements were collected through interviews with 10 teachers and 30 students.
• The database design (ER diagram and tables) is complete.
• The login, registration and course-listing modules have been built and tested.
• The user interface design has been approved by the supervisor.

3. Work in progress

• The feedback submission module is about 60 percent complete.
• Report generation for teachers is being designed.

4. Problems encountered

• Two weeks were lost because of the Dashain holidays.
• Difficulty in connecting the database with the server, which was solved with the help of a senior.

5. Remaining work and schedule

6. Overall assessment

About 55 percent of the project is complete, and I expect to finish on time if the schedule is followed. I would appreciate your suggestions on the report module.

Respectfully submitted, Nisha Thapa

NEWS RELEASE

FOR IMMEDIATE RELEASE

Everest Multiple College to Hold Education Fair 2079

Over 40 colleges and universities will participate; admission guidance and scholarships on offer

Kathmandu, 10 Baisakh 2079 - Everest Multiple College, New Baneshwor, will organise a two-day Education Fair on 20 and 21 Baisakh 2079 to help SEE and +2 graduates choose their future studies.

More than 40 colleges, universities and training institutes from Nepal and abroad will have stalls offering information on programmes in science, technology, management, health and the humanities. The fair will include free career counselling, workshops on study abroad and scholarships, a talk on "Choosing the Right Career" by industry experts, and on-the-spot admission and scholarship forms.

"Many students and parents do not have enough information about the options available after school and +2. This fair gives them one place to meet institutions and ask questions directly," said Principal Mr. Krishna Prasad Poudel.

The fair will open at 10:00 a.m. on 20 Baisakh at the college hall and run until 5:00 p.m. on both days. Entry is free for students, parents and teachers.

About Everest Multiple College: Established in 2050 B.S., the college offers Bachelor and Master programmes in science, management and education under Tribhuvan University.

Media contact: Binita Karki, Coordinator Phone: 01-4467890 | Email: fair@everestcollege.edu.np

Cover letter for a dream job (model)

Kathmandu, Nepal 15 Magh 2081

The Human Resource Manager Nepal Digital Solutions Pvt. Ltd. Babarmahal, Kathmandu

Subject: Application for the position of Junior Software Engineer

Dear Sir/Madam,

I am writing to apply for the post of Junior Software Engineer advertised on your website on 10 Magh 2081. I have just completed my Bachelor's degree in Computer Science and Information Technology from Tribhuvan University with a GPA of 3.8 out of 4.0, and I am eager to build my career with a company known for innovative and reliable software.

During my studies I developed a strong foundation in programming, databases, networking and software engineering. In my final-year project, a hospital appointment system built with Java, Spring Boot and MySQL, I led a team of four, gathered requirements from real users, and delivered a working system that reduced queue time in a pilot clinic. I also completed a three-month internship at a Kathmandu software firm, where I fixed more than 30 bugs, wrote unit tests and learned agile practices such as daily stand-ups and code review.

I can offer you:

• sound knowledge of Java, Python, JavaScript, SQL and Git;
• the ability to learn new tools quickly and to work in a team;
• clear written and spoken communication in Nepali and English; and
• a disciplined, punctual and honest work attitude.

Your company's work on digital services for Nepali businesses matches my interests, and I believe I can contribute from the first month while continuing to learn from your senior engineers. My resume is enclosed with copies of my transcript and certificates.

I would welcome the opportunity to discuss my application in an interview at your convenience. You can reach me at 98XXXXXXXX or at ram.sharma@example.com.

Thank you for your time and consideration.

Yours faithfully,

Ram Sharma

Enclosures: resume, transcript, character certificate, internship letter

Speech: The difficulty of being a student and an employee

Respected principal, teachers, and dear friends,

Good morning. Today I would like to speak about something many of us know well: the difficulty of being a student and an employee at the same time.

In Nepal, thousands of students work part-time or full-time because tuition, rent and daily expenses are high. Some of us teach tuition classes, some work in offices and IT firms, and some work in shops after college hours. We admire this independence, but it is not easy.

First, time is always short. After a full day at work, we reach class tired. Assignments, lab reports and exam preparation are left for late night, and sleep suffers.

Second, attention is divided. A work deadline can arrive on the same day as a college test. One of the two usually pays the price.

Third, there is little social life. We miss campus events, group study and time with family, and this creates stress and loneliness.

Fourth, the pressure is financial and emotional. We worry about fees, about our attendance, and about whether we are doing justice to both roles.

Yet this struggle also teaches us. We learn time management, responsibility and the real value of money. We bring practical experience into the classroom and theory into the workplace. Employers respect candidates who have already shown discipline.

My advice is simple: plan the week, use small gaps for study, talk to teachers and employers early about conflicts, protect your sleep, and ask for help when you need it. I also request the college to offer flexible schedules for working students.

Being a student and an employee is hard, but it shapes strong people. Thank you.

Recommendation report on improving waste management

To: The Mayor, Kathmandu Metropolitan City From: Environment Study Group, Tribhuvan University Date: 15 Magh 2081 Subject: Recommendation for household-level waste segregation and community composting

1. Introduction

Kathmandu produces more than 1,200 tonnes of solid waste per day, and about 60-70% of it is organic. Mixed waste is collected, carried to landfill and dumped, which causes bad smell, blocked drains, river pollution and health risks. This report recommends one action that can reduce the problem at its source.

2. Problem

• Households and shops put organic, plastic and paper waste in the same bag.
• Collection vehicles are overloaded and the landfill fills quickly.
• Recyclable materials are lost and the cost of collection rises.

3. Recommendation

The city should introduce compulsory source segregation with ward-level composting centres.

• Households give wet (organic) waste and dry waste in two colour-coded bins or bags: green for wet, blue for dry.
• Collection vehicles visit on fixed days, wet waste daily and dry waste twice a week.
• Wet waste goes to a composting plant in each ward or cluster of wards; compost is sold to farmers and nurseries.
• Dry waste goes to registered recycling agents.
• Awareness campaigns through schools, FM radio and ward offices explain the system.

4. Benefits

• The volume sent to landfill falls by an estimated 50%.
• Compost and recyclables create income and jobs.
• Cleaner streets and rivers, and better public health.
• Lower transport and landfill costs in the long run.

5. Cost and implementation

Costs include bins, small composting units, training and publicity. A pilot in five wards for six months is proposed first, then expansion to all wards in two years. Fines may be applied after a grace period, and sale of compost will help to meet running costs.

6. Conclusion

Segregation at source is simple, low cost and proven in cities such as Bhaktapur. We respectfully recommend that the Metropolitan City approve the pilot project and set up a monitoring committee.

Proposal: Permission for a vacation trip with friends

Submitted to: Dear Mom and Dad Submitted by: Your son/daughter Date: 15 Magh 2081

1. Purpose

I request your permission to travel with five close friends to Pokhara for five days (Chaitra 5 to 9) during my college vacation.

2. Why this trip

• After a hard semester, I need rest, and a change of place will help me return to studies fresher.
• It will teach me planning, budgeting and responsibility.
• Pokhara is a safe and popular tourist city, and I have always wanted to see Phewa Lake, the Sarangkot sunrise and the World Peace Pagoda.
• I will learn to work with friends and to take independent decisions.

3. Plan

4. Budget

I have saved Rs 8,000 from my pocket money and tuition income, and request your support for the remaining Rs 6,000.

5. Safety and responsibility

I will avoid risky activities, travel only in daylight, keep emergency numbers, and return on the date promised. I will complete my pending assignments before leaving.

6. Conclusion

I understand your concern for me and I promise to justify your trust. Please give me this chance, and I will share photos and stories when I return.

Thank you for your love and support.

E-mail announcing a skill-oriented program

To: all-staff@shikharit.com.np From: hr@shikharit.com.np Subject: Launch of the "Learn and Grow Together" skill-sharing program

Dear colleagues,

I am pleased to announce a new skill-oriented program at Shikhar IT Solutions called Learn and Grow Together. It will let us share our experience with each other and grow as one team.

What is the program?

Every Friday from 3:00 to 4:30 pm, one employee will lead a session on a skill or lesson from their own work, for example a programming technique, a client-handling method, a testing tool or a time-management habit. Sessions will be held in the conference room and also online for staff at our branch offices.

Why are we doing this?

• Everyone has knowledge that others can use.
• Sharing saves time and reduces repeated mistakes.
• Teams become stronger when members understand each other's work.
• Presenters build confidence, and listeners gain new skills.

How to take part

1. Choose a topic from your own experience.
2. Send your name and topic to hr@shikharit.com.np by 25 Magh.
3. The first session starts on 1 Falgun. A schedule will be circulated.
4. Attendance certificates will be given, and active participation will be considered in annual appraisal.

Please come with questions and ideas. If you need help in preparing a session, my team is happy to help.

Thank you, and let us learn together.

Best regards, Sita Thapa Human Resource Manager Shikhar IT Solutions Tel: 01-4XXXXXX

MEMO

Nepal Distillery Ltd.

To: All employees From: Company Secretary Date: 15 Magh 2081 Subject: Board decision on bonus and incentives

The Board of Directors, in its meeting held on 12 Magh 2081, has decided to provide a bonus and incentives to all employees in recognition of their hard work and the company's good performance this year.

Decisions of the Board

1. A festival bonus equal to one month's basic salary will be paid to all permanent employees. Temporary and contract staff will receive a proportionate amount.
2. A performance incentive of up to 10% of basic salary will be given on the basis of attendance, productivity and department targets.
3. Payment will be made through bank accounts on 30 Magh 2081.
4. Employees who joined after Shrawan 1, 2081 will be paid in proportion to their length of service.

What you need to do

Please check your bank details with the accounts section by 24 Magh. Department heads should submit performance evaluation sheets to the HR section by 22 Magh. Queries may be sent to the Secretary's office.

The management thanks every employee for their dedication and hopes for the same commitment in the coming year.

Company Secretary Nepal Distillery Ltd.

Proposal for the purchase of five laptops

To: The Manager, National Bank of Nepal From: IT Section Date: 15 Magh 2080

1. Objective

To purchase five reliable laptops for daily banking operation, reporting and customer service, within a suitable budget and time.

2. Problem

Staff currently share old desktop computers. These are slow, break down often, and cannot be moved to meeting rooms or branch counters. This delays work and customer service.

3. Requirements

Intel Core i5 (or equivalent), 16 GB RAM, 512 GB SSD, 14-15 inch display, 3-year warranty, Windows 11 Pro, battery life of at least 8 hours.

4. Comparison of available laptops

Prices are approximate and must be confirmed by quotation.

5. Findings

All three meet the specification. The HP ProBook has the lowest price and a good battery, the Lenovo ThinkPad has the best keyboard and service network but costs most, and the Dell is in between with strong business support.

6. Solution and recommendation

Buy five HP ProBook 440 G10 laptops.

7. Cost

5 x Rs 108,000 = Rs 540,000, plus 13% VAT of Rs 70,200, for a total of Rs 610,200. Carry bags and antivirus licences will cost about Rs 20,000.

8. Time schedule

The laptops can be in use within five weeks.

9. Conclusion

I request approval of this proposal so that staff can work more efficiently.

The process of technical writing

Technical writing is a planned activity. A writer moves through a series of stages, and may return to earlier stages when needed. A common process has the following steps.

1. Planning (prewriting)

• Define the purpose: what the document must do (inform, instruct, persuade, record).
• Analyse the audience: their knowledge, needs, and how they will use the document.
• Decide the scope, format, length, deadline and resources.

2. Research and gathering information

Collect data from manuals, books, journals, websites, interviews, surveys and experiments. Record sources so that they can be cited.

3. Organising

Sort information into main points and sub-points. Use an outline, a mind map or a list. Choose a pattern such as chronological, general to specific, problem and solution, or order of importance.

4. Drafting

Write the first version quickly following the outline. Concentrate on content and structure, not on perfect wording. Use clear, short sentences and plain words. Add headings, lists, tables and graphics.

5. Revising

Check the draft for completeness, accuracy, logical order, clarity, and whether it meets the audience's needs. Add, delete or rearrange material.

6. Editing

Correct grammar, spelling, punctuation and style. Remove wordiness and ambiguity. Check consistency of terms, numbering and format.

7. Proofreading

Read the final version carefully for small errors in typing, figures, page numbers and layout.

8. Reviewing and feedback

Ask peers, supervisors or users to test the document. Revise according to their comments.

9. Publishing and delivery

Submit or distribute the document in the right format (print or digital), on time, and keep a copy for updates.

In practice, writing is recursive: while revising, a writer may do more research or reorganise. Spending time on each stage gives a document that is accurate, usable and professional.

Feedback on a peer's vlog: "Blocked mind as a malfunction of communication"

Dear Anil,

Thank you for sharing your vlog on blocked mind as a malfunction of communication. I enjoyed it, and I would like to give some feedback.

What I learned from your vlog

Our teacher explained that a mental block is a barrier that stops ideas from reaching words, for example fear of judgement, lack of confidence, stress, or lack of knowledge about the topic. Your vlog added three useful ideas.

• A blocked mind is not only an individual problem. It is a communication malfunction in which the message is stuck between the sender and the receiver because of emotional noise.
• Your real-life example of freezing in front of an interview panel showed how anxiety can wipe out well-prepared answers.
• The simple habit of pausing and writing three key words before speaking is practical, and I had not thought of it.

How my experience differs

When my mind is blocked, I usually do not feel fear but rather overload: too many ideas arrive together and I cannot decide where to begin. What helps me is different from what you described. I do free writing for five minutes, then arrange points in order, and I discuss the topic with a friend before I present. You rely on breathing and positive self-talk, while I depend on structure and preparation. Both methods work, depending on the cause of the block.

Strengths

Your voice was calm, the examples were relatable, and the video was short and well edited.

Suggestions

• Add a short summary of tips at the end.
• Show text on screen for key points.
• Improve the sound, since there was slight background noise.

Overall it was an honest and helpful vlog. I look forward to your next one.

Best wishes, Sunita

Graphics in technical writing

What are graphics?

Graphics are visual elements used to present information, such as tables, charts, graphs, diagrams, drawings, photographs, maps, flowcharts and screenshots. They show data, objects or processes in a form that can be understood quickly.

Main types and their uses

How they are used in technical writing

1. To explain complex ideas simply. A diagram of a network is clearer than paragraphs of description.
2. To present data compactly. A table or graph replaces long text full of figures.
3. To support instructions. Screenshots and drawings help users follow steps.
4. To emphasise and persuade. A graph that shows a sharp rise in sales supports a recommendation.
5. To help different readers. Visuals are useful to non-experts and to readers who skim.

Guidelines for using graphics

• Use a graphic only when it adds value; do not use it for decoration.
• Place it near the text that refers to it, and mention it in the text (for example "see Figure 2").
• Give each a number and a clear title or caption (Table 1, Figure 2).
• Keep it simple, labelled and readable, with units and legends.
• Choose the right type for the message.
• Cite the source if the data is not your own.
• Keep it ethical: do not distort scales or hide data.

Technical writing and academic writing

Common ground: both need accuracy, clear organisation, correct grammar and honest use of sources. Technical writing is judged by whether the reader can use it, while academic writing is judged by the depth of its ideas.

Plagiarism and honesty in borrowing ideas

What is plagiarism?

Plagiarism is the use of another person's words, ideas, data, images or work as one's own without giving proper credit. It includes copying text word for word, paraphrasing without citation, copying from the internet or from classmates, buying an assignment, reusing one's own earlier work without saying so, and taking pictures or code without permission.

Common forms

• Direct copying without quotation marks
• Paraphrasing too closely without a source
• Mosaic plagiarism (patching phrases from several sources)
• Self-plagiarism
• Using false or missing citations

Why we should be honest in borrowing ideas

1. It is a matter of ethics. Ideas are the intellectual property of their creators. Taking them is a kind of theft.
2. It gives credit to the people whose effort produced the knowledge.
3. It protects reputation. A student or professional caught plagiarising may fail, be expelled, lose a job or face public disgrace.
4. There are legal consequences. Copyright law can lead to fines and lawsuits.
5. It builds trust. Readers trust writers who show where their information comes from, and they can check it.
6. It supports learning. Writing in your own words develops understanding and original thinking.
7. It keeps knowledge fair. Research grows when each person builds openly on earlier work.

How to avoid plagiarism

• Quote exact words with quotation marks and cite them.
• Paraphrase in your own words and still cite the source.
• Keep a record of all sources while researching.
• Use a standard style (APA, IEEE) for references.
• Use plagiarism-checking software before submission.
• Cite common sources when in doubt; common knowledge needs no citation.

Honest borrowing is not weakness. Good writers use others' ideas and openly acknowledge them.

E-mail on arrangements for the IT fair

To: dr.sharma@campus.edu.np Cc: itfair-committee@campus.edu.np Subject: Arrangements for the upcoming IT Fair on 25 Falgun

Dear Sir,

I am writing to report the arrangements completed so far for the IT Fair to be held at our campus premises on 25 and 26 Falgun 2080.

Venue and layout

• The main hall and the ground in front of the library are reserved. We have planned 30 stalls, a stage for presentations, and a registration desk at the gate.
• Electricity and backup power from the generator have been arranged. Wi-Fi access points have been installed in the hall.

Participants

• 22 stalls are confirmed by student teams and 8 by partner companies. Invitation letters have been sent to nearby colleges and schools.
• Three guest speakers from the IT industry have accepted our invitation.

Publicity and registration

• Posters are displayed and the event is advertised on the campus Facebook page. An online registration form is open.

Security and services

• Volunteers (40 students) are assigned to guide visitors, with first aid and a security desk set up.
• A canteen stall and drinking water have been arranged.

Budget

The estimated expenditure is Rs 150,000. Rs 90,000 has been received from sponsors, and Rs 60,000 is requested from the campus.

Pending work

Final approval of the schedule, printing of ID cards, and sound system testing will be completed by 22 Falgun.

I request you to review the arrangements and give your suggestions. I am available to meet at your convenience.

Thank you.

Sincerely, Binod Karki Coordinator, IT Fair Tel: 98XXXXXXXX

Issues a web designer should consider when planning a web page

1. Purpose and goals Know what the page must achieve: inform, sell, register users, or provide services. Every design decision should support this goal.

2. Audience Identify users' age, language, technical skill, devices and needs. Content, tone and layout should suit them.

3. Content Content should be accurate, relevant, short and up to date. Break text into small sections with headings. Decide what is most important and place it first.

4. Organisation and navigation Use a clear structure with a sitemap. Menus should be consistent and simple, with a visible home link and a search box. The user should reach information in few clicks.

5. Layout and visual design Use white space, alignment and a clear hierarchy. Keep colours, fonts and style consistent. Ensure good contrast and readable text size.

6. Responsiveness and compatibility The page must work on phones, tablets and desktops and in different browsers. Use responsive layouts.

7. Loading speed Optimise images, limit scripts and use compression, so that the page loads quickly even on slow internet connections as in many parts of Nepal.

8. Graphics and multimedia Use images, audio and video only when they help, and add alternative text and captions.

9. Accessibility Design for users with disabilities: text alternatives, keyboard navigation, readable colours, and support for screen readers.

10. Usability and interactivity Forms should be short and clear, with helpful error messages. Buttons and links should look clickable.

11. Security and privacy Use HTTPS, protect user data and forms, and state a privacy policy.

12. Search engine optimisation Use meaningful titles, headings, meta descriptions and keywords so users can find the page.

13. Legal and ethical issues Respect copyright for images and fonts, and credit sources.

14. Maintenance and testing Plan updates, test links, forms and pages across devices, and collect user feedback.

Resume for the position of IT Officer

RAM BAHADUR SHARMA Kathmandu, Nepal | +977-98XXXXXXXX | ram.sharma@example.com | linkedin.com/in/ramsharma

Career objective

Detail-oriented IT professional with four years of experience in systems administration, networking and technical support, seeking the position of IT Officer to help the company keep its systems secure, reliable and efficient.

Professional summary

• Over four years of experience supporting 200+ users and managing servers, networks and databases
• Strong troubleshooting, documentation and communication skills
• Fluent in English and Nepali, and comfortable working with international teams

Professional experience

IT Officer, Himalayan Finance Ltd., Kathmandu (2021 - present)

• Administer Windows and Linux servers, maintaining 99.5% uptime
• Reduced helpdesk ticket resolution time by 35% through a knowledge base and ticket system
• Set up backup, antivirus and firewall policies, preventing data loss in two incidents
• Managed network of 8 branches, including VPN and Wi-Fi setup
• Trained 60 staff in cyber security awareness

IT Support Intern, Nepal Telecom, Kathmandu (2020 - 2021)

• Handled hardware and software issues, imaged 50 computers and prepared documentation

Education

• Bachelor of Science in Computer Science and Information Technology (B.Sc. CSIT), Tribhuvan University, 2020 (GPA 3.7/4.0)
• Higher Secondary (Science), NEB, 2016

Technical skills

• Systems: Windows Server, Linux (Ubuntu, CentOS), VMware
• Networking: TCP/IP, DNS, DHCP, VLAN, Cisco routers and switches
• Databases and scripting: MySQL, SQL Server, Python, Bash, PowerShell
• Cloud and security: AWS basics, Microsoft 365, firewalls, backup tools

Certifications

CCNA (Cisco), CompTIA Security+, ITIL Foundation

Projects

• Migrated an on-premise mail server to Microsoft 365 for 150 users with no downtime
• Built a network monitoring dashboard with Zabbix

Languages: English (fluent), Nepali (native), Hindi (good)

References: Available on request.

Friendship across cultures

Yes, I believe a person can be as good a friend with someone from another culture as with someone from their own. Good friendship depends on trust, respect, honesty, shared interests and care, and these values exist in every culture.

Why cross-cultural friendship is possible

• Common human needs. Everyone wants to be understood, supported and valued. Laughter, kindness and loyalty are not limited to one culture.
• Shared interests. Music, sports, studies, technology and humour bring people together regardless of origin. In a class of IT students, a Nepali and a Korean student can share the same love of programming.
• Learning and growth. A friend from another culture gives new views, food, languages and customs, and widens our minds.
• Practical benefits. In a global workplace, such friendships improve teamwork and open opportunities.

Challenges

Differences in language, communication style (direct or indirect), attitude to time, religion, food, gender roles and family expectations can cause misunderstandings. For example, eye contact is respectful in some cultures and rude in others. Stereotypes and prejudice can also create distance.

How to overcome them

1. Be curious and ask politely instead of assuming.
2. Listen actively and avoid judging.
3. Respect the other's beliefs and customs.
4. Be patient with language and humour.
5. Focus on shared values rather than differences.
6. Apologise and clarify quickly when a misunderstanding occurs.

Conclusion

Cultural difference does not prevent deep friendship. It may need extra effort, but it gives a richer relationship. What matters is the person's character and mutual respect, not the country they come from.

Universal IT Solution opens its 25th branch in Pokhara

Pokhara, 15 Magh 2080 - Universal IT Solution, one of the leading information technology companies in the country, opened its 25th branch at Lakeside Road, Pokhara, on Sunday, strengthening its presence in the western region.

The new branch was inaugurated by the Mayor of Pokhara Metropolitan City, who cut the ribbon in the presence of company directors, local business leaders, officials and invited guests. In his address, the Mayor praised the company for creating jobs for local youth and supporting the digital growth of the city.

Speaking at the program, Chief Executive Officer Mr. Suresh Adhikari said that the branch will provide software development, web and mobile application services, cloud solutions, cyber security support and IT training. "Pokhara has a bright future as a tourism and technology centre. This branch is our commitment to customers in the Gandaki Province," he said.

The company said that 45 local professionals have been recruited for the branch and that scholarship training will be offered to 100 students in the first year. The branch has a modern office, a training lab and a customer support desk open from 9 am to 6 pm.

Since its establishment 15 years ago in Kathmandu, Universal IT Solution has served more than 2,000 clients. The company plans to open five more branches in the next two years.

The program ended with a tea reception and demonstration of the company's products.

Advantages of collaborative writing

Collaborative writing means two or more people working together to plan, draft, revise and finish one document, such as a report, proposal, manual or website. It is very common in technical and business work.

Advantages

1. Wider knowledge and skills. Members bring different expertise, for example one knows the technology, another the data, another the language, so the document is more complete and accurate.
2. Better quality. Ideas are discussed and criticised, errors are caught early, and the final version is better than any single member's draft.
3. Saves time. Large documents can be divided, and sections written at the same time, which helps meet tight deadlines.
4. More ideas and creativity. Brainstorming produces many options and new solutions.
5. Shared workload and responsibility. The pressure on one person is reduced and members support one another.
6. Different viewpoints. Representing the views of several departments or user groups makes the document balanced and suitable for a larger audience.
7. Learning and skill development. Members learn from each other and improve teamwork, communication and leadership skills.
8. Consistency and agreement. Since the team approves the content, there is more commitment and acceptance in the organisation.
9. Use of tools. Tools such as Google Docs and version control allow real-time editing, comments and tracking of changes, even for distant members.

Conditions for success

Set clear goals, assign roles, agree on style and schedule, communicate regularly, resolve conflicts respectfully, and use one person to do the final edit for a uniform voice.

Although it can bring disagreement and delay, good planning makes collaborative writing efficient and productive.

Flowchart of my dream application: a student study-planner mobile app

The application lets a student register, add subjects and deadlines, receive reminders and track progress. The flow is shown below.

        ┌───────────┐
        │   Start   │
        └─────┬─────┘
              ▼
      ┌───────────────┐
      │  Open the app │
      └───────┬───────┘
              ▼
       ◇ Already registered? ◇
        │ No            │ Yes
        ▼               ▼
 ┌────────────┐    ┌───────────┐
 │  Sign up   │    │  Log in   │
 └─────┬──────┘    └─────┬─────┘
       └────────┬────────┘
                ▼
        ◇ Valid credentials? ◇
         │ No          │ Yes
         ▼             ▼
   (show error,   ┌───────────────┐
    try again)    │ Show dashboard│
                  └───────┬───────┘
                          ▼
                ┌──────────────────────┐
                │ Add subject, task and│
                │ deadline             │
                └──────────┬───────────┘
                           ▼
                ┌──────────────────────┐
                │ App creates a study  │
                │ schedule & reminders │
                └──────────┬───────────┘
                           ▼
                ◇ Task completed? ◇
                 │ No          │ Yes
                 ▼             ▼
        (send reminder,   ┌───────────────┐
         reschedule)      │ Update progress│
                          │ report         │
                          └───────┬───────┘
                                  ▼
                         ◇ Add more tasks? ◇
                          │ Yes        │ No
                          ▼            ▼
                  (back to add     ┌────────┐
                   task)           │ Logout │
                                   └───┬────┘
                                       ▼
                                  ┌─────────┐
                                  │   End   │
                                  └─────────┘

Symbols used: the rounded boxes mark the start and end, rectangles are processes, diamonds (◇) are decisions with Yes/No branches, and arrows show the direction of flow.

The chart is simple and shows one decision per diamond, so any user or developer can follow the logic.

MEMO

To: All staff From: Manager Date: 15 Chaitra 2080 Subject: Launch of our new product on Nepali New Year 2081

I am pleased to inform you that our company will launch a new product, the SmartHome Hub, on 1 Baisakh 2081, on the occasion of the Nepali New Year. This is a big step for the company, and I need the support of every department.

Launch details

• Date and time: 1 Baisakh 2081, 11:00 am
• Venue: Company showroom, New Baneshwor
• Special introductory offer: 15% discount from 1 to 10 Baisakh

Responsibilities

Action required

1. Department heads must meet me on 18 Chaitra at 3 pm to confirm plans.
2. All staff must be present on launch day. Leave will not be granted from 29 Chaitra to 3 Baisakh.
3. Please report any problem immediately to my office.

I am confident that, by working as a team, we will make this launch a success. Thank you for your cooperation.

Manager

Short notes

1. Zoom presentation

A Zoom presentation is a talk or demonstration delivered online through the video-conferencing platform Zoom, used in classes, meetings, training and webinars.

• Features: screen sharing (slides, software, documents), video and audio, chat, polls, breakout rooms, recording, raise-hand and virtual backgrounds.
• Advantages: people in different places can join, saves travel cost and time, sessions can be recorded for later, and it is easy to share files and take questions.
• Tips for an effective presentation: test the internet, camera, microphone and slides before starting; join early; use a quiet, well-lit place; keep slides simple with large text; look at the camera; speak clearly with pauses; mute when not speaking; engage the audience through questions and polls; and manage time.
• Limitations: poor internet connection, technical failure, distraction at home, reduced eye contact and difficulty in reading audience reaction.

2. Ethical dilemma

An ethical dilemma is a situation where a person must choose between two or more options, each of which conflicts with some moral principle or duty, so that no choice is fully right.

• Examples in technical work: an engineer finds a safety defect in a product but the company wants to delay the report to meet a launch date; an employee is asked to use data in a way that violates users' privacy; a writer is pressured to exaggerate results in a report for a client.
• Causes: conflict between honesty and loyalty, profit and safety, personal interest and public good, or between rules and compassion.
• Resolving it: identify the facts and the people affected; recall laws, company codes and professional codes of ethics; consider options and consequences; consult seniors or an ethics committee; choose the action that protects the public, honesty and fairness; and document the decision.
• Importance: handling dilemmas wisely protects the reader, the organisation's reputation and the writer's integrity.

Role of audience analysis in technical writing

Audience analysis is the study of who will read or use a document, what they already know, what they need, and how they will use it. It is done before writing begins and guides every decision.

Role and importance

1. Decides content. The writer includes what the reader needs and leaves out what is irrelevant. Experts need data and details; beginners need background and definitions.
2. Decides level of technical detail. The right amount of jargon, explanation and examples depends on the reader's knowledge.
3. Decides style and tone. Formal for senior officials, friendly and simple for general users. Sentence length, vocabulary and voice change with the audience.
4. Decides organisation. Managers want the summary and recommendation first, while technicians want procedures and specifications.
5. Decides format and graphics. Users may need screenshots and numbered steps, while analysts prefer tables and charts.
6. Considers context and culture. Language, cultural expectations, reading situation (on a phone, in a hurry) and purpose (to act or to decide) affect the document.
7. Improves effectiveness. The document is more useful, readers make fewer errors, support costs fall, and the writer's credibility rises.

Types of audience

Experts, technicians, managers/executives, and lay (general) readers. Many documents have a mixed audience, so writers use layered sections (summary for managers, appendices for experts).

Questions to ask

Who are the readers? What do they know? Why will they read? What will they do with it? What are their attitudes and expectations?

Example

Suppose a company must explain a new software update.

• For end users, the writer produces a short guide: "Click Update, wait for the progress bar, and restart." It uses simple words, screenshots and a friendly tone, and avoids technical terms.
• For system administrators, the writer produces release notes: version number, changed modules, database schema changes, API compatibility, installation commands and rollback steps, in precise technical language.
• For managers, the writer prepares a one-page summary: benefits, cost, risk and schedule.

The facts are the same, but the content, style and format change. Writing for the wrong audience, such as giving a layperson API details, makes the document unusable. Audience analysis is therefore the foundation of good technical writing.

Letter to the Chief District Officer requesting permission to collect donations

Kirtipur, Kathmandu 15 Magh 2081

The Chief District Officer District Administration Office Kathmandu

Subject: Request for permission to collect donations for computers for Shree Janajyoti Secondary School

Respected Sir/Madam,

I am a student of B.Sc. CSIT at a campus under Tribhuvan University. Our campus has a well-equipped computer lab, which has helped me greatly in learning. I remember my school, Shree Janajyoti Secondary School in Dolakha, where about 400 students share only two old desktop computers. Because of this, most students finish school without basic computer skills.

To help, I and a group of fellow students want to donate twelve desktop computers to the school. For this purpose we would like to raise funds from well-wishers, alumni, businesses and the public. I therefore request your kind permission to collect donations from 1 Falgun to 30 Chaitra 2081.

Specifications of each computer

• Processor: Intel Core i3, 10th generation
• RAM: 8 GB
• Storage: 256 GB SSD
• Monitor: 19-inch LED
• Keyboard, mouse and UPS included
• Operating system: Windows 11 / Ubuntu (licensed or free)

Price list

(Prices are approximate, based on quotations from local suppliers.)

We promise to follow all rules, to issue receipts for each donation, to deposit the money in a joint bank account of the campus student committee, to publish a statement of income and expense, and to use the money only for this purpose. Any surplus will be spent on school internet service.

We request you to grant permission and to instruct the concerned offices to cooperate. We shall be grateful for your support in improving education in rural Nepal.

Thank you.

Yours faithfully,

Ram Sharma B.Sc. CSIT, Tribhuvan University Tel: 98XXXXXXXX

Enclosed: price list and quotations, campus recommendation letter, group member list

Structure and key components of a technical report

A technical report is a formal document that presents the results of an investigation, project, test or study to a specific audience. It follows a standard structure that has three main parts: front matter, main body and back matter.

A. Front matter

1. Cover (title) page. Title, author, organisation, date and recipient.
2. Letter or memo of transmittal. A short note that sends the report to the reader and states its purpose.
3. Abstract / executive summary. A brief summary of the problem, method, findings and recommendations, usually one page, for busy readers.
4. Table of contents. Headings with page numbers.
5. List of figures and tables.
6. Acknowledgements (optional).

B. Main body

1. Introduction. Background, purpose, scope, limitations, and plan of the report.
2. Methodology. How data was collected and analysed (survey, experiment, observation, tools).
3. Findings / results and discussion. Data presented in text, tables and graphs and interpreted.
4. Conclusions. What the findings mean, answering the main question.
5. Recommendations. Specific actions suggested, with reasons.

C. Back matter

1. References / bibliography. Sources cited in a standard style such as APA or IEEE.
2. Appendices. Supporting material: questionnaires, raw data, detailed calculations, code.
3. Glossary and index (if needed).

How the structure improves effectiveness

• Quick access. Readers can find the summary, conclusions or details they need using the contents page and headings.
• Serves different readers. Managers read the summary and recommendations; experts read the method and data; appendices keep detail out of the main text.
• Logical flow. Moving from problem to method to results to recommendations makes the argument easy to follow.
• Credibility. Method and references show that the findings are reliable and can be verified.
• Consistency and professionalism. A familiar format meets reader expectations and reduces confusion.
• Supports action and record keeping. Clear conclusions and recommendations lead to decisions, and the report is a lasting record.

Ethical considerations in technical writing

Ethics means the principles of right and wrong that guide behaviour. Technical documents influence decisions, safety, money and people's trust, so a writer has a duty to act ethically.

Key ethical considerations

1. Honesty and accuracy. Present facts, data and results truthfully. Do not exaggerate, falsify, hide errors or mislead with selective data.
2. Avoiding plagiarism and respecting intellectual property. Credit all sources, quote and cite properly, and respect copyright, patents and licences.
3. Confidentiality and privacy. Do not reveal trade secrets, client information or personal data without permission.
4. Safety and public welfare. Warn readers clearly of hazards, risks and side effects. Hiding a danger to protect profit is unethical and can harm people.
5. Fairness and objectivity. Present all relevant facts and alternatives without bias. Disclose conflicts of interest.
6. Clarity and non-deception. Use plain language and honest graphics. Avoid unclear wording, fine print or distorted charts (for example, misleading scales) that deceive the reader.
7. Respect and inclusiveness. Use unbiased language free from discrimination based on gender, caste, religion, ethnicity or disability, and consider cultural differences and accessibility.
8. Responsibility and accountability. Take responsibility for the document, correct mistakes promptly, and follow laws and company or professional codes.
9. Proper credit for collaborators. Acknowledge the contributions of all team members.

How a writer can follow ethical standards

• Verify facts and data and keep records of sources.
• Cite every borrowed idea or image, and get permission where required.
• Follow professional codes of ethics (such as those of IEEE or STC) and organisational policy.
• Consider the effect on every reader before publishing: ask "Who could be harmed or misled?"
• Present limitations and uncertainties openly.
• Have the document reviewed by colleagues or legal experts.
• Use bias-free language and accessible formats.
• Refuse to write misleading material, and report unethical pressure through proper channels.
• Admit and correct errors after publication.

Ethical writing builds trust, protects users and the public, and supports the long-term reputation of both the writer and the organisation.

An FAQ (Frequently Asked Questions) is a page or section of a website that lists the questions users ask most often, each followed by a short, direct answer. It reduces repeated support requests, helps visitors find information quickly and builds trust. A good FAQ uses the users' own wording, puts the most common questions first, keeps answers brief and links to detailed pages where needed.

Five FAQs for a college notes and exam-preparation website (Education Nepal):

1. Is the website free to use? Yes. All notes, past questions and model answers can be read free of charge. No registration is required to view them.

2. Which universities and programmes are covered? We cover TU, PU, KU, IOE and IOM, with a focus on BSc CSIT, BCA, BE and related programmes. New subjects are added regularly.

3. How can I find past questions for my subject? Open the programme, choose your semester and subject, and select the exam year. Questions are grouped by chapter so you can revise topic by topic.

4. Are the model answers official? No. They are written by our team as study aids. Always confirm the syllabus and marking scheme with your university and teachers.

5. How do I report an error or request a missing subject? Use the "Contact us" form or email the address shown in the footer. State the page, the mistake and, if possible, the correct information. We reply within a few working days.

A Gantt chart is a bar chart used in project management to show a schedule. Tasks are listed down the vertical axis and time (days, weeks, months) runs along the horizontal axis. Each task is drawn as a horizontal bar whose start and end show when it begins and finishes. Gantt charts also show task duration, overlaps, dependencies and milestones, so they help in planning, tracking progress and allocating time.

Gantt chart for an assignment schedule (6 weeks)

Dependencies: the draft starts only after the outline is ready; revision starts after the draft is complete; submission follows proofreading. Milestones: outline approved (end of Week 2), first draft complete (end of Week 4), final copy submitted (Week 6).

AIDA stands for Attention, Interest, Desire, Action. A persuasive message first catches attention, builds interest with relevant facts, creates desire by showing benefits, and ends with a clear call to action.

Subject: Meet StudyMate, the Nepali student's pocket tutor

Attention: Tired of carrying heavy notes and searching for past questions the night before an exam?

Interest: StudyMate is our new mobile app that puts TU, PU and IOE syllabus notes, past questions and model answers in your phone. It works offline, loads in seconds and is organised by semester, subject and chapter.

Desire: Imagine revising a full chapter on the bus, tracking your progress with built-in quizzes and getting reminders before every exam. Over 2,000 students in our pilot said they saved at least five hours of study time each week, and the basic version costs nothing.

Action: Download StudyMate today from the Google Play Store or App Store, and sign in with your email to start. Install it before this Friday and get the premium quiz pack free for one month.

Download now: www.studymate.example

An executive summary is a short, self-contained overview placed at the start of a technical document (report, proposal or plan). It lets a busy reader grasp the whole document without reading it in full.

Purposes:

• Saves time for decision makers. Managers and clients often read only the summary and decide whether to approve, fund or read further.
• States the essentials. It summarises the problem or purpose, the method or scope, the main findings, conclusions and recommendations.
• Supports decisions. It highlights costs, benefits, risks and the action required.
• Acts as a preview and guide. It orients readers to the structure and importance of the content.
• Stands alone. It makes sense without the body of the document and should not introduce new information.

It is written last, in plain language, usually one page or about 5-10% of the report length, and avoids jargon and detailed data.

Technical writing communicates specialised, practical information so that a reader can understand it or act on it. It differs from other forms of writing (literary, journalistic, academic or creative) in several ways.

Technical documents such as manuals, user guides, reports and proposals are also usually reviewed, tested for usability and revised, and they follow organisational or industry standards.

A chronological resume suits a candidate with continuous experience in the target field. A functional resume suits a student or someone changing fields, whose skills matter more than the job record.

The technical writing process is a sequence of stages that turns an idea into a clear, usable document.

1. Planning and analysis. Define the purpose, analyse the audience (their knowledge, needs, and use of the document), determine the scope, deadline, format and medium.
2. Research and information gathering. Collect facts from sources, interviews, experts, experiments, existing documents and the product itself, and record sources for citation.
3. Organising and outlining. Arrange the material logically (chronological, general-to-specific, problem-solution) and prepare an outline with headings.
4. Drafting. Write the first version, focusing on content and clarity rather than perfection. Add visuals, tables and examples.
5. Revising. Improve organisation, completeness, accuracy, tone and clarity; remove unnecessary content.
6. Editing and proofreading. Correct grammar, spelling, punctuation, style, consistency and formatting.
7. Review and testing. Peers, experts and sample users check the document and test its instructions for usability.
8. Publishing and distribution. Release in print or online, and then collect feedback.
9. Maintenance. Update the document when the product, procedure or information changes.

The stages are iterative: the writer often goes back to earlier steps as feedback arrives.

Peer review means that colleagues or subject experts read and evaluate a document before it is published. It is important because:

• Accuracy. Reviewers catch technical errors, wrong data and misleading statements that the writer may not notice. In safety or software documentation these errors can be costly.
• Fresh perspective. Writers become too close to their text. Peers see gaps, ambiguity and confusing parts.
• Audience fit. Reviewers can judge whether the content, tone and level suit the intended readers.
• Quality and consistency. They check organisation, terminology, style, format and compliance with standards.
• Completeness. Missing steps, warnings or references are identified.
• Reduces risk and cost. Errors found before release avoid rework, support calls, legal problems and loss of credibility.
• Collaboration and learning. It shares knowledge among team members and improves the writer's skills.

For best results, give reviewers clear criteria, a reasonable deadline, and accept feedback professionally.

Example definition: A router is a networking device that forwards data packets between computer networks. Example description: A description of the router would give its size, ports, antennas, power supply, internal components (CPU, memory, interfaces) and how packets are received, looked up in the routing table and forwarded.

A definition answers "What is it?" and a description answers "What does it look like, what are its parts and how does it work?"

(a) Pilot study: a small-scale preliminary study carried out before the main research to test the feasibility, methods, time, cost and tools (such as a questionnaire), so that problems can be fixed before full implementation.

(b) Clinical research: systematic investigation involving human participants to evaluate the safety and effectiveness of medicines, devices, treatments or diagnostic methods, and to understand health and disease.

(c) Alignment: the positioning of text or objects relative to a margin or to one another, such as left, right, centre or justified. In a broader sense it means arranging things in a consistent line or in agreement, such as aligning a document with goals.

(d) Stakeholder: any individual, group or organisation that has an interest in, is affected by, or can influence a project, product or document, for example clients, users, employees, managers and investors.

(e) Rehearsing: practising a presentation or speech beforehand, including timing, delivery, gestures and use of visual aids, in order to improve confidence and quality and to find problems before the real event.

(a) Copy editing

Copy editing is the stage in which an editor reviews a written document to correct and improve its language and presentation, without changing its meaning. It comes after the content is finalised and before final proofreading.

• Correct grammar, spelling, punctuation and usage.
• Ensure consistency in terminology, spelling style, capitalisation, abbreviations, numbers and formatting.
• Improve clarity, conciseness and sentence flow, and remove redundancy.
• Check headings, captions, tables, references and cross-references.
• Check facts, names and figures that look doubtful and mark queries for the author.

A style guide is followed so that the document is accurate, readable and professional.

(b) Whistleblowing

Whistleblowing is the disclosure by an employee or member of an organisation of illegal, unethical or harmful activity within it, such as fraud, corruption, safety violations or concealed defects, to someone able to act.

• Internal whistleblowing reports to higher management, an ethics officer or a hotline.
• External whistleblowing reports to regulators, the police, media or public.
• Technical writers may face it when they discover false data, unsafe product information or a cover-up.
• Many countries provide legal protection against retaliation, but whistleblowers may still risk their jobs or reputations.

It should be done in good faith, with documented evidence, after trying internal channels where reasonable.

Recommendation report

A recommendation report is a document that evaluates two or more options against stated criteria and recommends the best one, with evidence and justification. It answers the question "Which option should we choose, and why?" Typical parts are problem statement, criteria, analysis of alternatives, conclusion and recommendation.

Difference from a proposal

---

Recommendation Report: Cloud Storage Solution for a 50-Employee Business

Prepared for: Management, [Client Company] Prepared by: [Consulting Firm], IT Consulting Division

1. Executive summary

Three cloud storage services, Google Drive (Google Workspace), Dropbox Business and Microsoft OneDrive (Microsoft 365), were evaluated for a 50-employee business. We recommend Microsoft OneDrive with Microsoft 365 Business Standard if staff already use Office applications, and Google Workspace as the strongest alternative. Because most business documents are Office files, OneDrive offers the best integration, security and value.

2. Problem statement

Staff currently share files through email and personal drives. This causes version conflicts, lost files, weak access control and no reliable backup. The business needs a central, secure, affordable cloud storage service that supports collaboration for 50 users, remote access and data protection.

3. Evaluation criteria

1. Cost per user and for 50 users per year.
2. Storage capacity.
3. Security and compliance: encryption, two-factor authentication, admin controls, audit logs.
4. Collaboration: co-editing, comments, sharing control, version history.
5. Integration with tools the business already uses.
6. Ease of use and administration.
7. Reliability, backup and support.

(Prices below are approximate list prices and should be verified before purchase.)

4. Analysis of options

Google Drive (Google Workspace Business Standard)

• Cost: about USD 12 per user per month, about USD 7,200 per year for 50 users.
• Storage: 2 TB per user (pooled).
• Security: encryption in transit and at rest, 2-step verification, admin console, audit logs, data loss prevention in higher plans.
• Collaboration: excellent real-time co-editing in Docs, Sheets and Slides; simple sharing.
• Integration: Gmail, Meet, Calendar; weaker handling of complex Microsoft Office files.
• Ease: very simple interface and administration.

Dropbox (Business)

• Cost: about USD 15 per user per month, about USD 9,000 per year.
• Storage: from 9 TB shared by the team.
• Security: strong encryption, two-factor authentication, remote wipe, file recovery.
• Collaboration: reliable file sync and Paper; good third-party integrations, but no built-in office suite.
• Integration: works with Office and Google tools through add-ons.
• Ease: very good syncing performance; costs more than the others.

Microsoft OneDrive (Microsoft 365 Business Standard)

• Cost: about USD 12.50 per user per month, about USD 7,500 per year, and it includes Word, Excel, PowerPoint, Teams, Outlook and SharePoint.
• Storage: 1 TB per user.
• Security: encryption, multi-factor authentication, conditional access, retention policies and audit logs through the admin centre.
• Collaboration: real-time co-authoring in Office, Teams integration, version history.
• Integration: best with Windows and Office.
• Ease: more complex administration, but familiar to most users.

5. Comparison summary (score 1-5)

Google Drive and OneDrive tie on score; integration and security for Office-based work break the tie.

6. Recommendation

We recommend Microsoft OneDrive (Microsoft 365 Business Standard).

Justification:

• It costs about the same as Google but also includes the full Office suite, Teams and SharePoint, giving more value for 50 users.
• It has the strongest administrative security controls.
• Staff already working in Word and Excel will need little training.
• Dropbox is the most expensive and lacks an office suite.

If the business already uses Gmail and Google Docs, Google Workspace would be the better choice.

7. Implementation steps

1. Run a pilot with 5 users for two weeks.
2. Migrate files in stages and set up folder structure and permissions.
3. Enable multi-factor authentication for all accounts.
4. Train staff in a half-day session.
5. Review usage and cost after three months.

The technical writing process

The technical writing process is a series of connected stages. In a software project it looks like this.

1. Planning. Identify the purpose, audience, scope, schedule and deliverables. Example: for the user guide of a mobile banking app, decide that it is for first-time customers, to be published online and in the app in 6 weeks.
2. Research. Collect information from developers, product owners, source documents, specifications and by using the software.
3. Organising. Create an outline and information structure (installation, getting started, features, troubleshooting) and plan visuals.
4. Drafting. Write the content in plain language, with numbered steps, screenshots and warnings.
5. Revising. Improve organisation, completeness and clarity from the reader's view.
6. Editing and proofreading. Correct grammar, consistency, terminology and format.
7. Review and usability testing. Developers verify accuracy; test users follow the steps and report confusion.
8. Publishing. Release in the chosen formats (PDF, help centre, in-app help) and manage versions.
9. Maintenance. Update for each software release and use feedback.

Collaborative writing

Collaborative writing is when two or more people share the planning, writing and reviewing of a document, as happens in most software documentation, for example when writers, developers, testers and designers jointly produce API documentation in a shared repository.

How it enhances the process

• Combines expertise, since developers provide technical depth and writers provide clarity.
• Divides workload, which allows large documents to be completed faster.
• Provides built-in review and a variety of perspectives, which improves accuracy.
• Tools like Git, Google Docs, Confluence and Markdown enable concurrent work and version control.

How it complicates the process

• Different writing styles and terminology reduce consistency.
• Version conflicts and overwritten edits can occur.
• Coordination, meetings and approvals consume time.
• Responsibility can be unclear.
• Disagreements about content or direction can delay delivery.

Advantages

1. Better quality and accuracy.
2. Faster delivery of large projects.
3. Shared ownership and learning.
4. Wider knowledge and creative ideas.

Challenges

1. Inconsistent voice and style.
2. Scheduling and communication difficulties, especially with remote teams.
3. Unequal contribution (some members do less).
4. Tool and version control issues.
5. Conflicts of personality and opinion.

Conflict resolution strategies

• Set roles and responsibilities at the start (project lead, writers, reviewers, final approver).
• Adopt a style guide and templates to settle style disputes objectively.
• Use version control and a change log so edits are traceable.
• Hold regular meetings and keep communication open.
• Focus on the audience and project goals rather than personal preferences.
• Listen and compromise, using data such as usability test results to decide.
• Escalate to the project manager when agreement cannot be reached.

Example: two developers disagree about whether a REST API guide should show code in Python or JavaScript. The team checks user analytics, finds most users prefer Python, shows Python first and JavaScript as an alternative tab. The decision uses evidence rather than opinion.

Collaboration improves the process when roles, tools and standards are clear; without them it complicates it.

Proposal: Redesign of the Company Website

To: Management, [Company], Kathmandu From: Web Content Manager Purpose: To obtain approval to redesign the company website so that it improves user experience, accessibility and search engine visibility.

Background and problem

The current website is outdated: pages are cluttered, navigation is unclear, it loads slowly on mobile phones, and customers cannot easily find services or portfolios. Visitors leave quickly, search rankings are weak, and some users with disabilities cannot use the site.

Objectives

• Reduce bounce rate and increase enquiries.
• Make the site mobile-friendly and fast.
• Meet WCAG 2.1 level AA accessibility.
• Increase organic search traffic.

(a) Key principles for organising and designing web pages

1. Clear purpose and user focus. Each page serves one main goal, such as "Request a quote".
2. Visual hierarchy. Use size, colour and position so the most important items (headline, main button) are seen first.
3. Consistency. Use the same layout, navigation, fonts and colours on every page.
4. Simplicity and white space. Limit clutter and use short blocks of content.
5. Navigation. Provide a clear top menu (Services, Products, Portfolio, About, Careers, Contact), a logo link to home, breadcrumbs and a search box.
6. Responsive design. The layout adapts to mobile, tablet and desktop; Nepali users mostly browse on phones.
7. Performance. Compress images, minimise scripts and use caching; pages should load in about 3 seconds even on slow connections.
8. Visible calls to action. Buttons such as "Get a free consultation".
9. Readable typography and contrast.

(b) Best practices for writing effective web content

• Write for scanning. Use short paragraphs, informative headings, bullets and bold key words. Users read in an F pattern.
• Inverted pyramid. Put the main point first.
• Plain language and active voice. Avoid unexplained jargon; explain terms like "API" or "cloud migration".
• Be concise. About half the words of print copy.
• Descriptive link text, for example "Read the mobile app case study", not "click here".
• SEO. Use researched keywords naturally in titles, headings, URLs and meta descriptions; write unique page titles, and image alt text.
• Credibility. Add client logos, testimonials, certifications and real project numbers.
• Keep content current and review it regularly. Offer English and Nepali versions where useful.

(c) Information architecture considerations

Information architecture (IA) is the structure and labelling of content so users can find it.

• Content audit and user research. Inventory existing pages; use interviews, surveys and analytics to learn what visitors need.
• Grouping and labelling. Use card sorting to group content using terms users understand.
• Hierarchy. Keep it shallow, so key content is within three clicks.
• Proposed structure:
  • Home
  • Services (Web Development, Mobile Apps, Cloud, AI/Data, Support)
  • Products
  • Portfolio / Case Studies
  • Blog and Resources
  • About (Team, Careers)
  • Contact
• Navigation systems. Global menu, local menu, footer links, breadcrumbs, internal search.
• URL structure. Short and meaningful, e.g. /services/mobile-apps.
• Testing. Tree testing and usability testing before launch.
• SEO. Logical structure with internal linking and an XML sitemap.

(d) Ensuring web accessibility

Follow the WCAG principles: content must be Perceivable, Operable, Understandable and Robust (POUR).

• Text alternatives: alt text for images and transcripts or captions for videos.
• Colour contrast: at least 4.5:1 for normal text; do not rely on colour alone.
• Keyboard navigation: all functions work without a mouse, with visible focus indicators and a "skip to content" link.
• Semantic HTML and ARIA: proper headings, landmarks, labelled form fields, so screen readers (NVDA, JAWS) work.
• Resizable text and responsive layout up to 200% zoom.
• Clear form errors and instructions; avoid CAPTCHAs without alternatives.
• No flashing content; controls for animations and carousels.
• Nepali language support: Unicode fonts and the language attribute set.
• Testing: automated tools (Lighthouse, WAVE), manual keyboard checks, and testing with users with disabilities.

Examples for a tech company

• A "Request a Demo" button in a contrasting colour on every service page.
• A case study page titled "How we built a mobile banking app for a Nepali bank", with key results at the top, an alt text for each screenshot, and a transcript for the demo video.
• Careers page with filters and keyboard-accessible forms.

Timeline and budget (summary)

Budget will be provided after approval of scope.

Conclusion

The redesign will make the website easier to use, accessible to all, and more visible on search engines, which will support lead generation and the company's reputation. We request approval to begin.

Importance of ethics

Ethics are the moral principles that guide behaviour. In technical writing and workplace communication they matter because readers rely on documents to make decisions, operate systems and protect safety. Unethical communication can cause injury, financial loss, legal action and loss of trust.

Ethics are important because they:

• protect users from harm (accurate warnings, instructions);
• build the credibility and reputation of the writer and the organisation;
• ensure honesty in data, claims and credit;
• keep the organisation within law (copyright, privacy, contracts);
• promote fairness and respect for diverse audiences.

Core principles are honesty, accuracy, confidentiality, respect for intellectual property, fairness, clarity and responsibility to the public.

Ethical dilemmas in the IT industry

• Pressure to hide or play down a software bug or security vulnerability in release notes.
• Exaggerated marketing claims (e.g. "100% secure").
• Copying code, text or images without permission or licence (plagiarism, open-source licence violations).
• Revealing confidential customer data, source code or trade secrets.
• Dark patterns in user interface text that trick users into consent.
• Falsified test results, benchmarks or statistics.
• Documents biased against groups, or not accessible.
• Discovering company wrongdoing such as data misuse.

Steps when confronted with ethical issues

Inaccurate information

1. Verify the facts with reliable sources and experts.
2. Correct the document and record the change.
3. Notify the supervisor and affected readers; issue an errata or update.
4. Refuse to publish what you know is false.

Plagiarism

1. Identify the source and check the licence.
2. Quote, paraphrase and cite properly, or obtain written permission.
3. Rewrite in your own words or remove the material.
4. Use plagiarism checkers and keep reference records.

Organisational wrongdoing

1. Document the facts calmly and keep evidence.
2. Check relevant laws, company code of ethics and policies.
3. Raise the matter with your supervisor.
4. If it is ignored, escalate to an ethics officer, compliance, legal team or senior management.
5. As a last resort, report externally (regulator) where the law protects whistleblowers.
6. Do not take part in the wrongdoing, and seek legal advice if necessary.

Creating a culture of ethics

• Publish a clear code of ethics and apply it to everyone, starting with leaders.
• Train employees with case studies.
• Provide safe, anonymous channels to report concerns and protect from retaliation.
• Reward honesty and make ethics part of performance reviews.
• Build review and approval procedures for documents (peer review, legal review).
• Encourage open discussion of mistakes.

Real-world examples

• Volkswagen emissions scandal (2015): software was written to cheat emission tests; staff who knew of it did not report it. The company paid billions in fines.
• Boeing 737 MAX: the pilot training and technical documentation of the flight-control system (MCAS) were criticised for not informing pilots, and two crashes followed.
• Equifax breach (2017): failure to patch a known vulnerability and delay in telling the public damaged millions of people.
• Facebook/Cambridge Analytica: misuse of user data raised privacy and transparency issues.

These cases show that ethical writing and honest communication protect people and the organisation.

Unique characteristics of technical writing

• Reader-centred: designed so that the reader can use the information.
• Accurate and precise: errors can cause damage or danger.
• Clear and concise: plain language and unambiguous terms.
• Well organised and easy to scan: headings, numbering, white space.
• Visual: diagrams, screenshots, tables.
• Objective and ethical.
• Task-oriented: supports a work process.

It is essential in professional contexts because organisations depend on documentation to train users, operate systems safely, comply with law, win contracts and maintain products. Good technical writing reduces errors and support costs.

Audience analysis is the process of identifying who will read or use a document and finding out their knowledge, needs, attitudes, expectations, context of use and constraints (such as language, time and reading medium). It is done before writing and guides every decision.

How the audience affects the document

Purpose. The purpose depends on what readers need. Executives need information to decide, so the purpose is to persuade and recommend. Technicians need to perform a task, so the purpose is to instruct step by step.

Scope. Experts need detail and depth without basic explanations; novices need background, definitions and examples, but less advanced content. Decision makers need a short overview of cost and risk, not technical details.

Medium. A mobile user may need a short in-app help screen; a manager may want a short report or slide deck; developers may prefer online, searchable documentation with code samples; field staff with poor connectivity may need printed or PDF guides.

Audience also affects tone, vocabulary, level of jargon, organisation, graphics and length.

Example from the IT industry

A company releases a new cloud backup service.

• End users (non-technical): a short quick-start guide with screenshots and simple words ("Click Back Up Now"), delivered in the app and as a video.
• System administrators: an installation and configuration manual with command-line examples, ports, and security settings, as a searchable online knowledge base.
• Executives: a two-page executive summary covering cost savings, risk reduction and compliance.

The same product leads to three documents with different purposes, scopes and media, because the audiences differ.

The phases total $2+2+5+2+1=12$ weeks, so each phase starts when the previous one finishes (finish-to-start dependency).

Critical path: 1 -> 2 -> 3 -> 4 -> 5. Any delay in one phase delays the whole 12-week project.

Milestones

Parallel sub-tasks (backend and front end) in development save time while remaining inside the 5-week phase.

Copyediting and publishing phase

Copyediting comes after the content has been drafted and revised. The editor improves the text without changing its meaning:

• correcting grammar, spelling, punctuation and word usage;
• ensuring consistency of terminology, abbreviations, capitalisation, numbers, headings and style;
• improving clarity, concision, tone and sentence structure;
• checking tables, figures, captions, references and cross-references;
• querying facts and unclear points for the author.

Publishing is the release of the finished document:

• apply final layout, templates and branding;
• final proofreading of the formatted version;
• produce formats (PDF, web page, print, help system);
• check links, accessibility and metadata;
• obtain final approval, release, distribute and archive with version number;
• collect feedback and plan updates.

Copyediting, proofreading and peer review

Comparison

When to use

• Chronological: for people with steady, relevant experience and clear progress in the same field, e.g. a developer applying for a senior developer post.
• Functional: for fresh graduates, career changers, people returning after a gap, or people with varied jobs whose skills matter more than history.

Functional resume for a Technical Writer position

SAMIR THAPA Kathmandu, Nepal | +977-98XXXXXXXX | samir.thapa@example.com | linkedin.com/in/samirthapa

Career objective Detail-oriented BSc CSIT graduate seeking a Technical Writer position to produce clear, accurate and user-focused documentation.

Technical writing skills

• Wrote user guides, README files and API documentation for three academic software projects.
• Created step-by-step tutorials with screenshots and flowcharts.
• Edited and proofread reports to a consistent style.

Technical skills

• Markdown, HTML/CSS, Git/GitHub, Microsoft Word, Google Docs, Figma basics, Canva.
• Basic knowledge of Python, SQL and web development to understand the products documented.
• Documentation tools: Docusaurus, Confluence (basic).

Research and communication skills

• Interviewed developers and users to collect requirements.
• Presented project documentation to classmates and faculty.
• Conducted peer review and usability checks of manuals.

Collaboration

• Worked in teams of four using GitHub issues and pull requests.

Experience

• Documentation Intern, XYZ Software, Kathmandu
• Content Volunteer, College IT Club

Education BSc CSIT, Tribhuvan University, [College], [Year]

Certifications Technical Writing course (Google Technical Writing)

References available on request.

Information architecture in web design

Information architecture (IA) is the practice of organising, structuring and labelling the content of a website so that users can find information and complete tasks easily. It includes site structure (hierarchy), navigation systems, labelling, search and the relationships between pages. Good IA is based on user research, card sorting and testing, and it improves usability, findability and search ranking. A well-built IA keeps important content within a few clicks and uses language users understand.

Writing different types of web pages

Homepage

• Purpose: introduce who you are, what you offer and direct visitors to the right place.
• A clear headline and short value statement in the first screen.
• Brief summaries with links to main sections (services, products, news), rather than full details.
• Prominent navigation, search, and one primary call to action (e.g. "Request a demo").
• Trust items such as client logos and testimonials.
• Minimal text; users scan and decide in seconds.

Product page

• Purpose: help the user evaluate and buy or try the product.
• Descriptive product name and a benefit-focused headline.
• Key features written as user benefits, in bullets, with specifications in a table.
• High-quality images, screenshots, or demo video with alt text.
• Price, plans, availability, and clear "Buy" or "Free trial" button.
• Reviews, case studies, and compatibility/requirements.
• Keywords for SEO, and links to related products and support.

FAQ page

• Purpose: answer common questions quickly and reduce support load.
• Write questions in the users' own words, as real questions.
• Group by topic (billing, account, technical) with headings or collapsible sections.
• Short, direct answers that link to detailed pages.
• Put the most frequent questions first, add search, and update regularly based on support requests.
• Use plain language and a contact option for unanswered questions.

FOR IMMEDIATE RELEASE

Kathmandu Firm Launches ShieldNet, AI-Powered Cybersecurity Platform That Stops Threats Before They Strike

Kathmandu, 21 October 2026 - TechSure Nepal today launched ShieldNet, a cybersecurity software product that detects and blocks ransomware, phishing and network intrusions in real time, helping organisations cut security incidents by up to 70 percent.

ShieldNet uses machine learning to monitor network traffic and user behaviour, identify suspicious activity within seconds and isolate affected devices automatically. Its single dashboard gives IT teams a clear view of risks, and a guided response removes the need for a large security team.

"Cyberattacks on banks, hospitals and schools are rising, and most small organisations cannot afford a full security operations centre," said Anita Sharma, CEO of TechSure Nepal. "ShieldNet gives them enterprise-grade protection that is simple to deploy and affordable."

In a three-month pilot with 15 organisations, ShieldNet blocked more than 12,000 malicious attempts, with less than 1 percent false alarms. Key features include:

• real-time threat detection and automatic response;
• endpoint, email and cloud protection;
• compliance reports for banking and data-protection rules;
• installation in under one hour, with local support in Nepali and English.

ShieldNet is available from today in three plans, starting at Rs 1,500 per device per year. A 30-day free trial can be requested at www.techsure.example/shieldnet.

About TechSure Nepal: Founded in 2015, TechSure Nepal provides software and security solutions to more than 200 organisations in Nepal.

Media contact: Ramesh Karki, press@techsure.example, +977-1-XXXXXXX

Principles of effective graphics

1. Purpose. Every graphic must support a point in the text; do not add decoration.
2. Simplicity. Show only necessary data, avoid chartjunk, 3D effects and clutter.
3. Accuracy and honesty. Use correct scales (a bar chart axis starting at zero), proportional elements and no distortion.
4. Clarity and labels. Give a number and title, axis labels with units, legends, and source.
5. Audience and context. Match complexity to readers' knowledge; make the graphic understandable alone.
6. Placement and integration. Place near the text that refers to it and refer to it in the text ("see Figure 2").
7. Consistency. Use the same fonts, colours and style across the document.
8. Colour and contrast. Use limited colours, contrast for readability, avoid relying on colour only (accessibility), and check how it prints in greyscale.
9. Ethics and permission. Cite sources and get permission for borrowed graphics.

Choosing the graphic type

Factors to consider: the type of data (exact or relative, categorical or time series), the message to be communicated, the audience, the amount of data, the medium (print, screen, mobile), the available space, and the cost and time to produce.

MEMORANDUM

TO: Sita Rai, Head of Documentation and Product Support FROM: Hari Basnet, Technical Writer DATE: 21 October 2026 SUBJECT: Inaccurate safety information in the CVE-2026-XXXX vulnerability documentation - immediate correction needed

Problem While reviewing the security guide for Version 4.2 of our product, I found that the section on vulnerability CVE-2026-XXXX says that the problem affects only the older Version 3 and that no user action is needed. Our engineering report shows that Version 4.0 to 4.2 are also affected and that attackers could access stored user data. Customers who follow our documentation may leave their systems exposed.

Risk

• User data could be stolen or altered.
• The company could face legal and regulatory consequences and loss of customer trust.
• The risk increases every day the guide remains available.

Recommended action

1. Immediately mark the current page as under review or temporarily remove it.
2. Confirm the correct information with the security engineering team today.
3. Publish a corrected advisory listing affected versions and the patch or workaround.
4. Notify customers and support staff by email and the website, with a note explaining the correction.
5. Check other documents, release notes and the knowledge base for the same error.
6. Add a technical review by security engineering to the documentation process for future vulnerability notices.

I can draft the corrected text within two hours of receiving the confirmed details. Please let me know by 3 p.m. today how you would like to proceed. I can be reached at extension 214.

Attachment: Engineering report excerpt and screenshots of the current documentation page

(a) White paper: an authoritative, in-depth report that explains a problem, technology or issue and presents a solution or position, backed by facts and research. It is used by organisations to educate readers, support decisions and promote products or ideas. Example: a white paper on zero-trust security for banks.

(b) Usability testing: a method of evaluating a product, website or document by watching representative users perform realistic tasks. It identifies difficulties, errors and satisfaction, and the results are used to improve the design.

(c) Stakeholder analysis: the process of identifying all individuals or groups who affect or are affected by a project or document, and assessing their interests, influence, needs and expectations, so that communication and decisions can address them appropriately.

(d) Content Management System (CMS): software that lets users create, edit, organise, publish and manage digital content (usually web content) without detailed programming knowledge. It handles templates, user roles, versions and workflow. Examples: WordPress, Drupal, Joomla.

(e) Plain language: a style of writing that is clear, direct and easy for the intended audience to understand the first time they read it, using familiar words, short sentences, active voice, logical organisation and few technical terms or jargon.

(a) Whistleblowing in technical communication

Whistleblowing is the act of an employee or insider disclosing information about illegal, unsafe, unethical or fraudulent activity inside an organisation to someone who can act on it. The recipient may be a higher authority inside the organisation (internal whistleblowing) or a regulator, the press or the public (external whistleblowing).

It matters in technical communication because engineers, programmers and technical writers often hold the information that shows a product or practice is dangerous. Examples are a hidden software defect, falsified test data, unsafe construction, data-privacy violations or misreported safety reports.

Key points:

• Ethical basis: The professional duty to protect public safety and welfare can outweigh loyalty to the employer. Codes of ethics such as those of IEEE and ACM place public interest first.
• When it is justified: There is a serious harm or violation. The evidence is solid and documented. The employee has first tried internal channels, and no other remedy remains.
• Communication practice: The report must be factual, objective, specific and supported by documents, with dates, names of records and no emotional language or personal accusations. It is addressed to the right authority, and a copy is kept safely.
• Risks: Retaliation, dismissal, harassment, loss of career and legal action for breach of confidentiality.
• Protection: Whistleblower protection laws, anonymous reporting channels and a company ethics hotline reduce these risks.

Well-known examples are the Challenger disaster, where engineers warned about the O-ring seals before launch, and the Snowden disclosures.

(b) Mechanism description versus process description

Both describe something without teaching the reader to do it. A process description tells how something happens in general, which is different from instructions that tell the reader how to carry out the steps. Both use definition, clear structure and graphics. A mechanism description often includes a short operation section, which links the two.