Virtual Screen Splitter: Virtualians Social Network

Virtualians Social Network
Virtual Screen Splitter

Software Requirements Specification
Version 1.0
Group Id:
Supervisor Name:
Tanveer Arshad

REVISION HISTORY
Date
(dd/mm/yyyy)
05/02/2014
Version
1.0
Description
Author
In ancient times when computer was newly Mc

invented, there were vacuum tubes being
used in order to process data, in that specific
computer
only
addition,
subtraction,
multiplication and division was performed.

With the passage of time computer became
so popular that it was gradually upgraded. In
last decade we are using Windows OS to
operate
computers.
Now
as
computer
became so advanced that it is using some

virtual machine and virtualization concepts.
Virtual Screen Splitter is also an example of
virtualization in which we can perform
active tasks within limited resources and
within time. We are using multiple screens
concept which developed in a way as it
represents that we are working on real active
desktop. Its wide spread use will increase
efficiency and performance of computer.
TABLE OF CONTENTS
1. Scope (of the project)

2. Functional Requirements Non Functional requirements
3. Use Case Diagram
4. Usage Scenarios
5. Adopted Methodology
6. Work Plan (Use MS Project to create Schedule/Work Plan)

SCOPE OF PROJECT
Applying old techniques to our routine work is very difficult. Consumption of paper is
very costly instead of getting a computer and using it for life time. Computer can provide
us proper functionality needed to perform an activity. Using computer applications in
proper way like Virtual Screen Splitter will provide more reliability and better
functionality and performance in doing routine work.
Virtual Screen Splitter can perform any task that will be given to it to perform. We can
run multiple tasks like can listen songs in one screen and play games on other and
installations can be run on another screen parallel to it. Use of VSP is better then
traditional usage.
Virtual Screen Splitter will be able to run on any Windows based Operating System and
we just need to run it and then we will move the tasks by dragging them into their
screens. If user have multiple tasks to perform and current screen is not enough then user
can add another screen into Virtual Screen Splitter by clicking at add screen button.
Newly added screen will also work same as its working in previous active screens.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS
Functional Requirements
As per user requirements this application can easily work and fulfill all needs of
user.
Application can perform any type of task dragged to it.
Every screen have threads which can perform task parallel to one another.
It will use resources from system unit like RAM, Processor and other storage
resources and Virtual Screen Splitter will work according to thread priority.
User can minimize or maximize screen or select number of screens which will
appear on desktop.
Less cost on purchase of equipment is required and provide us more effective way
of management and deployment.
Non-Functional Requirements
Scalability:
VSP fits into any size of windows or can receive and adopt all configurations of active
desktop. No need to configure it separately.
Portability:
Application is easy to install on any operating system. It is portable and can be used
anywhere on Windows Operating System..
Efficiency:
Virtual Screen Splitter can give result and work efficiently within limited resources. It
will provide full functionality without any restriction.
Flexibility:
Virtual Screen Splitter is updateable to any new change in technology, and it also will
guide us to update our software. There will never be any issue to upgrade it to new
version.

Portability:
It is portable application and there will never be any issue in its installation over any
machine. Default system configurations will be applied by Virtual Screen Splitter
automatically. Any change in system configurations will never effect to Virtual Screen
Splitter.
Versatility:
Virtual Screen Splitter is a versatile machine and it provide all required features by the
user and can accept all changings made by a user.
Performance:
VSP provide high performance and give us positive results on its use. System
performance will be boost up when we properly deploy application.
Easy To Access:
This application should be easy to access, we can easily use each pan and can easily
manage the software.
USE CASE DIAGRAM:
USAGE SCENARIOS:
1. DRAG TASK
Use Case Title
Drag Task
Use Case Id
Requirement Id
Description: User Click And Hold The Task, Move Mouse And Drop It To Required
Screen.
Pre-Condition: Application Is Running And User Select The Task
Task Sequence
Exceptions
1. Select And Hold Task

2. Drag It To Relevant Screen
3. User case end.
Post Conditions: Task Added To Screen Successfully.
Authority: User
Modification history: 1.0
Author:

2. ADMINISTER TASK
Use Case Title
Administer Task
Use Case Id
Requirement Id
Description: User Have Dragged Task In VSP Screen And Now He Can Administer The
Task.
Pre-Conditions: Application Must Be Running
Task Sequence
Exceptions
1. Task Added To It And Now Being Performed

2. Task Completed As Required
3. Use case end
Post Conditions: Task Have Completed Work As Per Requirements.
Authority: User
Author:
3. CLOSE TASK
Use Case Title
Close Task
Use Case Id
Requirement Id
Description: User Can Close/Finish Task Which Was Dragged Into Its Screen.
Pre-Conditions: Application Is Running And Task Have Been Completed
Task Sequence
Exceptions
1. User Click At Close Button To Close Application

2. Ask Him To Close It Or Not.
3. Use Case End.
Post Conditions: Task Is Closed Successfully.
Authority: User
Author:
4. CLOSE APPLICATION
Use Case Title
Close Application
Use Case Id
Requirement Id
Description: Application Have Performed Task Required And Now User Click At Close
Button To Close IT
Pre-Conditions: Application Is Running
Task Sequence
Exceptions
1. User Click At Close Button

2. Application Asked To Yes Or No
3. Use Case End.
Post Conditions: Application Closed
Authority: User
Author:
5. SYSTEM MAINTENANCE
Use Case Title
System Maintenance
Use Case Id
Requirement Id
Description: User Must Have Permissions To Manage System Unit, Install Or Uninstall
Applications, Manage Rights and Screen Resolution etc.
Pre-Conditions: System Unit Is Power On
Task Sequence
Exceptions
1. Click At Manage Button As Per Requirements

2. System Will Be Managed.
3. Use Case End.
Post Conditions: System Is Managed.
Authority: User
Author:

6. PUT IN SCREEN
Use Case Title
Put In Screen
Use Case Id
Requirement Id
Description: System Received Task In Screen As It Was Dragged To It.

Pre-Conditions: Application Is Running Smoothly.
Task Sequence
Exceptions
1. System Will Allow User To Drag-in Task.

2. Task Loaded In Screen Of VSP
3. Use Case End.
Post Conditions: Application Loaded Successfully.
Authority: System
Author:

7. TASK PERFORMED/VERIFIED
Use Case Title
Task Performed
Use Case Id
Requirement Id
Description: System Will Allow The User To Perform Tasks In Application.

Pre-Conditions: Application Is Running And Task Added To The Application
Task Sequence
Exceptions
1. System Allow VSP To Run Task

2. System Support VSP To Complete Task
3. Use Case End.
Post Conditions: VSP Completed Task Successfully.
Authority: System
Author:
8. SAVE TASK
Use Case Title
Save Task
Use Case Id
Requirement Id
Description: System Will Display a Dialog box to Save The Specific Task
Pre-Conditions: Application Is Running And Task Saved
Task Sequence
Exceptions
1. Type The Name Of The File To Be Saved

2. Select The Extension To Be Saved
3. Press Enter To Save
Post Conditions: This File Is Saved Successfully
Authority: System
Author:

9. ALLOW TO CLOSE
Use Case Title
Allow To Close
Use Case Id
Requirement Id
Description: System Allow User To Perform Multiple Tasks and System Will Show
Efficiency In Work/Tasks, After Completion Of Task He Can Close Application.
Pre-Conditions: User Created An Event To Close Application
Task Sequence
Exceptions
1. Event Received To System

2. Allow Application To Be Closed
3. Use case end.
Post Conditions: Application Closed Successfully.
Authority: System
Author:
10. ALLOW TO MAINTAIN
Use Case Title
Allow To Maintain
Use Case Id
10
Requirement Id
10
Description: System Will Allow User To Manage VSP As Per Requirement

Pre-Conditions: Application VSP Should Be Running
Task Sequence
Exceptions
1. User Manage VSP

2. System Accept All Changings
3. Use case end.
Post Conditions: VSP Maintained As Per User Requirements.
Authority: System
Author:

ADOPTED METHODOLOGY
In my project Virtual Screen Splitter I strictly followed rules and regulations designed
by Virtual University and adopted process model. This process model is a combination of
waterfall model and spiral model. Combination of these two methodologies will provides
better characteristics to develop a project and also supported me to get better results and
easy planning, designing as well as in every deliverable of this project. Following these
two models parallel to each other provides many advantages appeared in this project and
it tried to remove disadvantages and as per requirements this application will run
smoothly and efficiently.
REASON TO CHOOSE THIS METHODOLOGY

VU process model is heavily dependent on risk analysis and also evaluation in each
phase. This approach of system development maximizes the quality of system and
minimizes the disadvantages and risk.
DIAGRAM OF VU PROCESS MODEL:
WORK PLAN (USE MS PROJECT TO CREATE CHEDULE/WORK

PLAN)

Virtual Screen Splitter: Virtualians Social Network

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Virtual Screen Splitter: Virtualians Social Network

Uploaded by

Copyright:

Available Formats

Virtualians Social Network