Microsoft Word (MS OFFICE)

Submitted by
Name MIS ID
Basit Ali 31211
Rimsha Yasmin 31659
Syed Rizwan Ghani 30718
Aftab Nazir 31679
Lecturer: Mrs. Aleena Sumbalin
Course: Introduction to Software Engineering
Date: 25/12/2022
Contents
1.0. Introduction..........................................................................................................................................3
1.1. Purpose.............................................................................................................................................3
1.2. Scope of Project................................................................................................................................3
1.3. Glossary............................................................................................................................................4
1.4. References........................................................................................................................................4
1.5. Overview of Document.....................................................................................................................4
2.0. Overall Description...........................................................................................................................5
2.1 System Environment..........................................................................................................................5
2.2 Functional Requirements Specification.............................................................................................5
2.3 Non-Functional Requirements...........................................................................................................6
3.0 Interface of MS Word............................................................................................................................6
3.1 Components of the Word Window....................................................................................................6
3.2 Functional Requirements...................................................................................................................7
3.3 Detailed Non-Functional Requirements.............................................................................................7
3.3.1 Performance and scalability.......................................................................................................7
3.3.2 Performance...............................................................................................................................8
3.3.3 Scalability....................................................................................................................................8
3.3.4 Portability and compatibility.......................................................................................................8
3.3.5 Portability...................................................................................................................................8
3.3.6 Compatibility..............................................................................................................................8
3.3.7 Reliability, Maintainability, Availability.......................................................................................9
3.3.8 Reliability....................................................................................................................................9
3.3.9 Maintainability............................................................................................................................9
3.3.10 Availability................................................................................................................................9
1.0. Introduction
1.1. Purpose

Microsoft Word is a word processing program that is part of the Microsoft Office Suite

package. The main purpose of Word is to create text documents that can be saved

electronically, printed on paper or saved as PDF files.

1.2. Scope of Project

Microsoft Word Is Actually for Documentation Purposes And It allows users to alter the

appearance of text easily by changing its color, font style, and size. For That Reason, the file is

easily stored as a report on a laptop or other media device and retrieved on Any Event needed

for editing, sharing, or printing.

Word processing involve formatting of word documents, correction of errors in a word document,

typing data into word document, etc. it is the result of drastic transformation of business

documents from hard copies or hand written papers into digital format. MS word is the best

product of MS office suite that gives a variety of features and tools for documentation work and

covers almost every important business function.

Due to global acceptance of word documents for their business activities there is a wide scope of

word processing solutions applicable in various industries such as Medical, Legal, Education,

Design, Corporate, Real Estate, Finance, etc. scattered globally and having routine operations

through word documents. There are large organizations from western countries that outsource
word processing services to eastern countries; especially India based companies to perform their

non-core operations of word processing work.

1.3. Glossary

Term Definition

Attribute a characteristic of a text or graphic object that can be

altered, such as bold, italic, shadowed etc.
AutoCorrect a feature that corrects commonly misspelled words
automatically as they are typed.
a small graphic, commonly a large dot, that starts each item
Bullet
in a list
Font a set of characters that all use the same basic design
Page Orientation the way in which pages are laid out in a printed document
Styles for entire paragraphs, including their fonts, tabs,
Paragraph Styles
alignments etc.
Print Layout View a view that shows how a document will appear when it is
printed.
the process of creating, editing and printing a computer
Word Processing
written text document.
Thesaurus a feature that looks up alternative words with the similar
meanings
Style a collection of formatting choices that can be applied
throughout a document.
Tab Leader an index format that separates the entry from the page
number associated with it.
Theme a unified look in a document that incorporates heading and
text styles.
semi-transparent text or picture that are ‘behind’ the main
Watermark
text of the document.
1.4. References

Referance Pager for MS WORD GLossary

1.5. Overview of Document

The next chapter, the Overall Description section, of this document gives an overview of

the functionality of the product. It describes the informal requirements and is used to establish

a context for the technical requirements specification in the next chapter.

 The third chapter, Requirements Specification section, of this document is written

primarily for the developers and describes in technical terms the details of the functionality of

the product.

Both sections of the document describe the same software product in its entirety, but

are intended for different audiences and thus use different language.

2.0. Overall Description

2.1 System Environment

2.2 Functional Requirements Specification

 Creating text documents.

 Editing and Formatting the existing documents.
 Making a text document interactive with different features and tools.
 Graphical documents, comprising images.
  Used by Authors and Researchers.
 Detect grammatical errors in a text document.

2.3 Non-Functional Requirements

 The most common ones are

 performance,

 scalability,

 portability,

 compatibility,

 reliability,

 availability,

 maintainability,

 security,

 localization,

 usability.

3.0 Interface of MS Word

3.1 Components of the Word Window

Besides the usual PC window components (close box, title bar, scroll bars, etc.), a Word window
has other elements

Component Functionality or Purpose of the Component

Menu Bar Contains File,Edit, View, Insert, Format, Tools, Table, Window and Help menus

Standard Contains icons for shortcuts to menu commands.

Toolbar

Formatting Tool Contains pop-up menus for style, font, and font size; icons for boldface, italic, and
Bar underline; alignment icons; number and bullet list icons; indention icons, the border
 icon, highlight, and font color icons.

Ruler Ruler on which you can set tabs, paragraph alignment, and other formats.

Insertion Point Blinking vertical bar that indicates where text you type will be inserted. Don’t confuse
the insertion point with the mouse I-beam. To move the insertion point, just click the
mouse where you want the point moved.

End-of-File Non-printing symbol that marks the end of the file. You cannot insert text after this
Marker mark.

Selection Bar Invisible narrow strip along the left edge of the window. Your mouse pointer changes
(Gutter) to a right-pointing arrow when it is in this area. It is used to select a line, a paragraph,
or the entire document.

Split Handle Double-click to split the window in two (to view different portions of the same file).
Double-click to return to one window

Status Bar Displays page number, section number, and total number of pages, pointer position on
page and time of day.

Task Pane Displays and groups commonly used features for convenience.

Office Assistant An animated character that can provide help and suggestions. There are multiple
characters to choose from, and it is possible to turn the Office Assistant off.

3.2 Functional Requirements

Described in Topic 2.2

3.3 Detailed Non-Functional Requirements

Performance and scalability

Performance and scalability are the two core non-functional requirements no system can do
without. Since they go hand in hand, we’ve put them in one section.

Performance

Performance defines how fast a software system or a particular piece of it responds to certain
users’ actions under a certain workload. In most cases, this metric explains how long a user must
wait before the target operation happens (the page renders, a transaction is processed, etc.) given
the overall number of users at the moment. But it’s not always like that. Performance
requirements may describe background processes invisible to users, e.g. backup. But let’s focus
on user-centric performance.

Scalability

Scalability assesses the highest workloads under which the system will still meet the
performance requirements. There are two ways to enable your system scale as the workloads get
higher: horizontal and vertical scaling.

 Horizontal scaling is provided by adding more machines to the pool of servers.

 Vertical scaling is achieved by adding more CPU and RAM to the existing machines.

Portability and compatibility

Two more key players in the world of non-functional requirements are such attributes as
portability and compatibility.

Portability

Portability determines how a system or its element can be launched within one environment or
another. It usually includes hardware, software, or other usage platform specifications. Put
simply, it establishes how well actions performed via one platform are run on another. Also, it
prescribes how well system elements may be accessed and may interact from two different
environments.

Compatibility

Compatibility, as an additional aspect of portability, defines how a system can coexist with
another system in the same environment. For instance, software installed on an operating system
must be compatible with its firewall or antivirus protection.

Portability and compatibility are established in terms of operating systems, hardware devices,
browsers, software systems, and their versions. For now, a cross-platform, cross-browsing, and
mobile-responsive solution is a common standard for web applications.

Portability non-functional requirements are usually based on preliminary market research, field
research activities, or analytics reports on the types of software and devices the target audience
has. If you are working within a corporate environment and the software will be accessed
through a documented list of devices and operating systems, it’s quite easy to define
compatibility and portability.

Consider the most complete list of portability requirements. Not only will this document
provide guidance to engineers, it will also outline the scope of testing scenarios. This includes:
  the list of supported operating systems and their versions,
 network specifics,
 the list of supported browsers and their versions, and
 devices and other hardware requirements.

Reliability, Maintainability, Availability

While these three types of requirements are usually documented separately, we aggregate them
in one section, since they approach the same problem from different angles. Another thing to
keep in mind with these requirements is that they are extremely hard to express in terms of
calculating. And, frankly, many system providers don’t document them at all. Let’s see.

Reliability

Reliability specifies how likely the system or its element would run without a failure for a given
period of time under predefined conditions. Traditionally, this probability is expressed in
percentages. For instance, if the system has 85 percent reliability for a month, this means that
during this month, under normal usage conditions, there’s an 85 percent chance that the system
won’t experience critical failure.

As you may have guessed, it’s fairly tricky to define critical failure, time, and normal usage
conditions. Another, somewhat simpler approach to that metric is to count the number of critical
bugs found in production for some period of time or calculate a mean time to failure.

Maintainability

Maintainability defines the time required for a solution or its component to be fixed, changed to
increase performance or other qualities, or adapted to a changing environment. Like reliability, it
can be expressed as a probability of repair during some time. For example, if you have 75
percent maintainability for 24 hours, this means that there’s a 75 percent chance the component
can be fixed in 24 hours. Maintainability is often measured with a metric like MTTRS — the
mean time to restore the system.

Availability

Availability describes how likely the system is accessible to a user at a given point in time.
While it can be expressed as an expected percentage of successful requests, you may also define
it as a percentage of time the system is accessible for operation during some time period. For
instance, the system may be available 98 percent of the time during a month. Availability is
perhaps the most business-critical requirement, but to define it, you also must have estimations
for reliability and maintainability.