Vision and Scope Document

for

Inventory Mangaement system

Version 1 approved

Prepared by Deka Ibrahim

2/march/2021

ID:

Copyright © 2013 by Karl Wiegers and Seilevel. Permission is granted to use and modify this document.
Vision and Scope for <Project> Page ii

Table of Contents
Table of Contents................................................................................................................ii
Revision History..................................................................................................................ii
1. Business Requirements..................................................................................................1
1.1. Background............................................................................................................1
1.2. Business Opportunity.............................................................................................1
1.3. Business Objectives................................................................................................1
1.4. Success Metrics......................................................................................................1
1.5. Vision Statement....................................................................................................1
1.6. Business Risks........................................................................................................1
1.7. Business Assumptions and Dependences...............................................................2
2. Scope and Limitations...................................................................................................2
2.1. Major Features........................................................................................................2
2.2. Scope of Initial Release..........................................................................................2
2.3. Scope of Subsequent Releases...............................................................................2
2.4. Limitations and Exclusions....................................................................................2
3. Business Context...........................................................................................................2
3.1. Stakeholder Profiles...............................................................................................2
3.2. Project Priorities.....................................................................................................3
3.3. Deployment Considerations...................................................................................3

Revision History

No revision History , first version just created

Prepared by Deka Ibrahim

Vision and Scope for Inventory Management System Page 1

1. Business Requirements
E-shop is a shop that is one of the major shops around and to have a system that shortens the
problem of not having a way to count and have history of their products have been the first
agenda this shop has to face and communicate with software teams to solve this in their own
requirements

1.1. Background
One of the events that had the most profound impact on people throughout
history is certainly the Industrial Revolution, which increased the efficiency and
mass production. The businesses grew, and so did their needs for better
inventory management.
In the early 1930s, a team at Harvard University designed what would become
the first modern check-out system. This system used punch cards, which were
inserted into a computer that read them, and eventually passed the information
to the storeroom. Although it might seem simple now, this automated process
was able to manage inventory as well, which was a huge thing at the time.
However, the system was too expensive to use.

1.2. Business Opportunity

All shops in industry have established a secure inventory system. The competition, which was
behind E-shop in production, are making great headway because of their way of handling the
store. The company has been offered the opportunity of producing this system.

1.3. Business Objectives

By establishing an inventory MS, E-shops will be able to more adequately and efficiently solve
their previous way of handling their products. Because of the those problems of not having their
products counted this is needed for inventory control for the Products.

1.4. Success Metrics

The success of this IMS is going to describe by the IMS-customers including stake holders

1.5. Vision Statement

The Vision Statement is to provide a detailed report for a reliable IM system to develop a very
interesting IMS that will exceed expectations of customers and to out distance the competitors.

1.6. Business Risks

As with any project there are risks that could disrupt processes all the way to causing a complete
failure. Creating a fully detailed, professional document to enable E-shop to manage its products
in a secure environment will contain several of those risks

Potential of Internet service not being available

Potential of power loss to server/equipment
Potential for internal data to be compromised by hackers

Prepared by Deka Ibrahim

Vision and Scope for Inventory Management System Page 2

1.7. Business Assumptions and Dependencies

A functional and secure System and database for our customers
Fast and reliable IMS

2. Scope and Limitations

Scope and Limitations – This project will be limited to a report that will provide detailed
documentation for the Creation of a robust working data presence with limited access to
database resources. This system will be a “No Frills” system; this means no unneeded sources
will not be added into the IMS. The Database will tied into together.

2.1. Major Features

A secure IMS environment for easy use
Product control section for controlling the product
Additonal Security for controlling the IMS

Scope of Initial Release

The report provided by Us will enable E-shops to establish a secure IMS for the
provision of a robust Control over their products. While the purpose of this document is
strictly focused IMS , it will open the door for numerous possibilities with respect to the
applications E-shop will be able to provide its customers

2.2. Scope of Subsequent Releases

Customer account inquiries
 Possible DVR and security team that will watch over key areas in the Shop
 Biometric systems for access to different sectons of the IMS
 Web based Inventory Management system

2.3. Limitations and Exclusions

 This report is entirely focused on the needs required to create a secure, stable IMS for E-
shop
 Databases are not linked on any open source enviroment. .
 No DVR systems will be implemented in this release
 No Biometric systems will be installed for this release

3. Business Context
One of the priorities of building the computer system is to appoint a customer to act as technical
advisor to the team that will be creating the system,. It is necessary to initiate the drafting of
procedure manuals which will reflect the new methods that shall be adopted. The printing section
of the company should be alerted of this possibility Management should also initiate a meeting
where a decision to explore the system inner workings might be explored.

Prepared by Deka Ibrahim

Vision and Scope for Inventory Management System Page 3

3.1. Stakeholder Profiles

Major
Stakeholder Value Attitudes Major Interests Constraints
Marketing Sales and System slow, Faster delivery to No adequate
Marketing inaccurate and wider markets machinery for
Strategies inadequate processing
Printing Exact Information Proof reading of Section located
labeling of provided not items must be less in factory.
dates on reliable arduous for QC Copyright
product issues difficult
labels to resolve
E-shops Immediate All autonomous in Producing different Situated in
and close attitude and lines but united in different towns
cooperation products contribution to with different
revenue names

3.2. Project Priorities

Dimension Driver Constraint Degree of Freedom

(state objective) (state limits) (state allowable range)
Schedule Duration of Training period for Access of two weeks
installation: staff undefined permitted before any loss
Three Months
Features Recent versions of Must operate on staff If database operational in
software to be already trained two months, acceptable.
installed
Quality Management must When prototype passes,
test prototype and installation must be
selected users test established
system
Staff Commencement of Size of team is 5 Permitted to co-opt
Creating the system including Customer employees to train during
form the E-shop installation process

3.3. Deployment Considerations

E-shop will require an enviroment for the system to work and suitable for the system ot work
under the watch of highly trained trainees for the system requries high attension in order to
have data secure and manageable

Prepared by Deka Ibrahim