Use Case Project

UseCaseProject-MAllibalogun-ReviseVersion4.docx

Home >Computer Science homework help >Use Case Project

Microsoft Word Editing	Version: 1.0
Software Requirement Specification	Date: 7/3/2020
YLLC-001

Yohammed LLC

Software Requirements Specification

For Microsoft WORD

Version 2016

Revision History

Date	Version	Description	Author
7/3/2020	1.0	Initial document	Mohammed Allibalogun
10/3/2020	1.0.1	Revise documentation of Initial document	Mohammed Allibalogun

Contents 1. Introduction 5 1.1 Purpose 5 1.2 Scope 5 1.3 Definitions, Acronyms, Abbreviations 5 1.4 References 5 1.5 Overview 6 2. Overall Description 6 2.1 Use-Case Model Survey 6 2.1.1 Sign in 6 2.1.2 Open 6 2.1.3 New 7 2.1.4 Save 7 2.1.5 Save As 7 2.1.6 Export 7 2.1.7 Print 7 2.1.8 Change Font 7 2.1.9 Use case Diagram: 7 2.2 Assumptions and Dependencies 7 3. Specific Requirements 7 3.1 Use-Case Reports 8 3.1.1 Sign in 8 3.1.2 Open: 9 3.1.3 New: 10 3.1.4 Save: 11 3.1.5 Save As: 12 3.1.6 Export: 13 3.1.7 Print: 14 3.1.8 Change Font: 15 3.2 Supplementary Requirements 16 3.2.1 Performance: 16 3.2.2 Usability: 16 3.2.3 Supportability: 16 3.2.4 Configurability: 16 3.2.5 Recoverability: 16

Software Requirements Specification

Introduction

Microsoft Word is a word processor created by Microsoft. It was first discharged on October 25, 1983, under the name Multi-Tool Word for Xenix frameworks. Microsoft Word 2016 was released in the year 2016. The Microsoft Word application location was made to facilitate its users in ways where they could document things, save them on their hard drives or online, and even print them. With a wide range of scopes, any type of document such as assignments, reports, proposals, brochures, memorandums, etc. can be made on created through MS Word. When the file is saved, a .docx extension file is made and saved on the system. Even though MS Word is a very helpful application location, it still has its drawbacks. One of them is due to the presence of too many options. A novice user may feel overwhelmed with the number of features that can be executed through this software.

Purpose

The purpose of the Microsoft Word application location is to document i.e. write any type of document such as assignments, quizzes, reports, etc. This does not mean that you can only write something on the word. You can also use tools to make your document look better such as using different layouts, different shapes, adding pictures and tables, etc. Thus, word lets you make a document and edit it. There are no critical bugs and the defect rate of MS Word is zero. The learning time for an average user is 30 to 60 minutes.

Scope

The project aims to efficiently document your need for both, your professional or personal life. The focus of this application location is to provide help for the user to inscribe a document in a multitude of formats. This will provide more options and facilitate the user with different modules so the document can always look professional.

Definitions, Acronyms, Abbreviations

Following are the abbreviations in the document:

· MS: Microsoft

· SRS: Software Requirement Specification

· RAM: Random Access Memory

References

Reference for this document:

https://en.wikipedia.org/wiki/Microsoft_Word(Wikipedia, n.d.)

“SRS Use Case Template”. (n.d.). UMGC. Retrieved on March 10, 2020, from https://learn.umuc.edu/d2l/le/content/444081/viewContent/16971639/View

Wyatt, A. (n.d.). Scope of Word Options. Retrieved March 10, 2020, from https://word.tips.net/T000326_Scope_of_Word_Options.html

Microsoft Word 2016 Features, Tips, and Tricks: Microsoft Office 2016. (2018, February 14). Retrieved March 10, 2020, from https://www.spadetechnology.com/microsoft-word-2016/

Microsoft Word. (2020, February 27). Retrieved March 10, 2020, from https://en.wikipedia.org/wiki/Microsoft_Word

Overview

The remaining SRS document has the description, the use cases model survey, and requirements related to the application location.

Overall Description

One of the factors affecting the product is the operating system on your system. Even though word runs on almost every operating system it still has some features minus or added when used in operating systems like Linux or Unix. MS Word is an application used for documentation. The key ability of the product is to enter and format text. It can save and print documents. It has themes and styles for making your document look professional. It also provides an automatic table of contents function, so now you do not have to type each content yourself. Similarly, there are many other features of the product.

Use-Case Model Survey

There will be 8 Use cases presented in this document. There’ll be one actor using this product;

· Non-corporate User: A novice user who does not go through any incorporation process.

The list of use cases is as follows:

· Microsoft word can run on basic 1 GB RAM easily.

· The system should also have a storage unit to save the documented word file.

· The document should be named before it is saved.

· To save a file. It should at least have a character on it. An empty word file cannot be saved.

Use-Case Reports

Sign in

Use Case ID:	UC-1
Use Case Name:	Sign in
Actor:	Non-Corporate User
Description:	Users are allowed to sign in to their Microsoft account.
Level:	Medium
Trigger:	When the user opens the word application.
Normal Flow:	1- The user is going to open the application present on the desktop. 2- The application will open and provide the user with a menu. Comment by Sheldon Linker: Throughout, this is not a proper name, so it should not be capitalized. Comment by Allibalogun, Mohammed (ctr): Modified all application to not be capitalized 3- The user will select a new document or an existing document. Comment by Sheldon Linker: Note that #1 is a descriptive sentence in the 3rd person, and #3 is an imperative in the implied 2nd person. All of these should be descriptive sentences, from here on down. Comment by Allibalogun, Mohammed (ctr) [2]: Corrected the issue 4- At the top right of your screen, there is a “Sign in” label. 5- Click that label. 6- A small window will open which will ask the user about your information to log in. 7- User will enter an email in the text field asking the email. 8- User enters password in the text field asking the password. 9- User click the “Sign in” button to sign in to his/her Microsoft account. 10- The system will log the user into the Microsoft account.
Exception:	The system will go back to the “home” menu. Comment by Sheldon Linker: Why and how is this an exception? That's not at all clear. Rather than list "Exception", when required, show an alternate flow. Make this change from here to the end of the document. Comment by Allibalogun, Mohammed (ctr): I don’t quite understand what other option could there be.
Postconditions:	The user is logged in.
Screenshot

Open:

Use Case ID:	UC-2
Use Case Name:	Open
Actor:	Non-Corporate User
Description:	Users are allowed to open an existing file.
Level:	Medium
Trigger:	When the user clicks the “Open” label.
Pre-conditions:	User should have opened MS Word.
Normal Flow:	1- The user is going to open the application present on the desktop. 2- The application will open and provide the user with a menu. 3- One of the labels on the menu will be the “Open” label. 4- User will click that label. 5- The system will ask the user to select the file the user wants to open. 6- The user selects the file. 7- User clicks the “open” button. 8- The system will open the file on Microsoft Word.
Postconditions:	The file is opened.
Assumptions:	The file already exists on the system.
Screen capture

New:

Use Case ID:	UC-3
Use Case Name:	New
Actor:	Non-Corporate User
Description:	Users are allowed to open a new file.
Level:	High
Trigger:	When the user clicks the “New” label.
Pre-conditions:	User should have opened MS Word.
Normal Flow:	1- The user is going to open the application present on the desktop. 2- The application will open and provide the user with a menu. 3- One of the labels on the menu will be the “New” label. 4- User clicks that label. 5- The system will make a new file for the user.
Postconditions:	A new file is opened. Comment by Sheldon Linker: These blocks are short enough that they should not be spanning page boundaries. Have the new page start at §3.1.3. Do this throughout the document. Comment by Allibalogun, Mohammed (ctr): Ensure all Use cases start in a new page
Screen Capture

Save:

Use Case ID:	UC-4
Use Case Name:	Save
Actor:	Non-Corporate User
Description:	Users are allowed to save a file.
Level:	High
Trigger:	When the user clicks the “Save” label.
Pre-conditions:	User should have opened MS Word.
Assumptions:	A document is opened.
Normal Flow:	1- User clicks the “File” label. 2- The system will show the user a Menu. 3- One of the labels on the menu will be the “Save” label 4- User clicks that label. 5- The application will ask the user where to save the file. 6- User specifies the location. 7- User clicks the “save” button.
Post conditions:	The file is saved.
Screenshot

Save As:

Use Case ID:	UC-5
Use Case Name:	Save As
Actor:	Non-Corporate User
Description:	Users are allowed to save a pre-existing file as a new file.
Level:	Medium
Trigger:	When the user clicks the “Save As” label.
Pre-conditions:	User should have opened MS Word.
Includes:	Save
Assumptions:	The file is already saved.
Normal Flow:	1- User edits the document. 2- User clicks the “File” label and open the menu. 3- One of the labels on the menu will be the “Save As” label. 4- User clicks that label. 5- The application will ask the user where to save the file and what name it should have. 6- User specifies the location and name. 7- User clicks the “save” button.
Postconditions:	The file is saved as a new file.
Screen Capture

Export:

Use Case ID:	UC-6
Use Case Name:	Export
Actor:	Non-Corporate User
Description:	Users are allowed to export the document.
Level:	Medium
Trigger:	When the user clicks the “Export” label
Pre-conditions:	1- User should have opened MS Word. 2- A file should be saved before it is exported.
Includes:	Save
Assumptions:	1- User is on the “Home” menu. 2- File is already saved.
Normal Flow:	1- User clicks the “File” label and open the menu. 2- One of the labels on the menu will be the “Export” label. 3- User clicks that label. 4- The user will have the option to either export the file as PDF or XPS. 5- User chooses one format. 6- User clicks the “export” button.
Postconditions:	The file is exported.
Screen Capture

Print:

Use Case ID:	UC-7
Use Case Name:	Print
Actor:	Non-Corporate User
Description:	Users are allowed to print the document.
Level:	Medium
Trigger:	When the user clicks the “Print” label.
Pre-conditions:	1- User should have opened MS Word 2- A file should be saved before it is printed
Includes:	Save
Assumptions:	1- The printer is attached to the system. 2- Document is already saved. 3- The user is on the “Home” menu.
Normal Flow:	1- User clicks the “File” label and open the menu. 2- One of the labels on the menu will be the “Print” label. 3- User clicks that label. 4- The user will have the option to select the way he wants to print the file. 5- User selects those options. 6- User clicks the “print” button.
Postconditions:	The file is printed.
Screen Capture

Change Font:

Use Case ID:	UC-8
Use Case Name:	Change Font
Actor:	Non-Corporate User
Description:	Users are allowed to change the font of the text in the document.
Level:	Low
Trigger:	When the user selects the change font area in the “home” panel.
Pre-conditions:	User should have opened MS Word.
Includes:	New
Assumptions:	A document is already opened.
Normal Flow:	1- User selects the home panel from the navigation bar. 2- The user will see a font changing drop-down menu. 3- User selects it and choose a font of his/her liking.
Postconditions:	The font is changed.
Screen Capture

Use Case Project

Software Requirements Specification

For Microsoft WORD

Version 2016

Revision History

Table of Contents

Software Requirements Specification

pg. 16