SJTU
Your Movie DataBase (YMDB)
Vision
Version 1.0
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
Revision History
Date
05/10/2007
YMDB
Version
1.0
Description
The initial vision
SJTU, 2016
Author
hAmmeRoL Lu
Page 2
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
Table of Contents
1.
2.
3.
4.
Introduction
4
1.1
4
References
Positioning
4
2.1
2.2
Problem Statement
Product Position Statement
4
4
Stakeholder and User Descriptions
4
3.1
3.2
3.3
3.4
3.5
5
5
5
5
6
Stakeholder Summary
User Summary
User Environment
Summary of Key Stakeholder or User Needs
Alternatives and Competition
Product Overview
6
4.1
4.2
6
8
Product Perspective
Assumptions and Dependencies
5.
Product Features
8
6.
Other Product Requirements
9
YMDB
SJTU, 2016
Page 3
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
Vision
1.
Introduction
The purpose of this document is to collect, analyze, and define high-level needs and features of Your Movie
DataBase (YMDB). It focuses on the capabilities needed by the target users, and why these needs exist. The details
of how the YMDB fulfills these needs are detailed in the use-case and supplementary specifications.
1.1
References
[This subsection provides a complete list of all documents referenced elsewhere in the Vision document. Identify
each document by title, report number if applicable, date, and publishing organization. Specify the sources from
which the references can be obtained. This information may be provided by reference to an appendix or to another
document.]
2.
Positioning
2.1
Problem Statement
2.2
3.
The problem of
The outdated and largely manual movie collection / DVD
management and classification.
affects
Customers with a lot of DVDs, movie fans who want to
manage their movies efficiently and movie rental stores that
are looking for an automatic DVD loan solution.
the impact of which is
A slow and costly manual management and classification with
inevitable errors and mistakes.
a successful solution would be
Greatly improve the speed and makes movie / DVD
management and classification altogether with loan
registration easy to use even for a newbie of computers.
Product Position Statement
For
DVD owners, movie fans and DVD rental stores
Who
Need an automatic movie / DVD management and classification
program
The YMDB
is a tool
That
Makes movie / DVD collection and management an easy job
even for total computer newbie.
Unlike
The outdated manual movie / DVD collection and management
Our product
Provides a one-key information grabber that can extract the
information of a specific movie / DVD from the Internet
automatically.
Stakeholder and User Descriptions
This section describes the users of YMDB. There are 3 types of users of the system; DVD owners, Movie fans, and
DVD rental stores.
YMDB
SJTU, 2016
Page 4
YMDB
Vision
YMDB
3.1
Version:
1.0
Date: 05/10/2007
Stakeholder Summary
3.2
Name
Description
Responsibilities
YMDB Dev Team
The YMDB development
team composed of one
project leader and two
programmers
YMDB Dev Team is responsible for the
development and maintenance of the project
and provides technical support.
The project leader is also responsible for
monitoring project progress.
User Summary
3.3
Name
Description
Responsibilities
Stakeholder
DVD
owners
DVD owners with a
lot of DVDs that
need to be classified
and managed.
Is responsible for producing report
and coordinating work.
Self-represented
Movie
fans
Movie lovers who
want to customize
their movie
information and
manage their
favorite movies.
Is responsible for producing report
and coordinating work.
Self-represented
DVD
rental
stores
DVD rental stores
that want an
automatic DVD
loan management
and registration
solution.
Is responsible for producing report
and capturing details.
Self-represented
User Environment
Number of people / users
multiple
Supported platforms
Windows, Linux, Max OS X
System environment
Java Runtime Environment
Needed libraries / applications
Movie Info Extractor (MIE)
Local Database Driver (LDD)
3.4
Summary of Key Stakeholder or User Needs
[List the key problems with existing solutions as perceived by the stakeholder or user. Clarify the following issues
for each problem:
•
What are the reasons for this problem?
•
How is it solved now?
•
What solutions does the stakeholder or user want?]
YMDB
SJTU, 2016
Page 5
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
[It is important to understand the relative importance the stakeholder or user places on solving each problem.
Ranking and cumulative voting techniques indicate problems that must be solved versus issues they would like
addressed.
Fill in the following table—if using Rational RequisitePro to capture the Needs, this could be an extract or report
from that tool.]
Need
Priority
Concerns
Current Solution
Proposed Solutions
Automatic movie / DVD
information collection
High
It is dull and
error-prone to
input the
information
of a movie
manually.
Manually input the
information all by the
users themselves.
An automatic one-key
information extraction
form many famous Internet
sites (e.g.
http://www.imdb.com)
Customizable movie
management
High
There is no
good solution
to the
problem that
movie fans
want to
customize a
personal
movie list to
meet their
own needs.
None
A special-designed movie
rating and classification
feature that allows users to
view their own favorite /
expected movie lists.
Easy-to-use DVD loan
management
Medium
It is errorprone to
manage DVD
loan
information
manually.
Manual input in
Excel files.
A special loan / registration
feature in YMDB that
provides automatic loan
management.
3.5
Alternatives and Competition
An on-the-shelf alternative is Movie Collector (http://www.collectorz.com/movie/). Although it provides sufficient
management functions, but it lacks the easy-to-use interface for computer newbie and it costs $39.95.
4.
Product Overview
This section provides a high level view of YMDB capabilities, interfaces to the external Movie Info Extractor and
Local Database Driver, and the system configuration.
4.1
Product Perspective
[This subsection of the Vision document puts the product in perspective to other related products and the user’s
environment. If the product is independent and totally self-contained, state it here. If the product is a component of a
larger system, then this subsection needs to relate how these systems interact and needs to identify the relevant
interfaces between the systems. One easy way to display the major components of the larger system,
interconnections, and external interfaces is with a block diagram.]
YMDB
SJTU, 2016
Page 6
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
The new YMDB system provides the user with an automatic online movie / DVD information collection and
management. The YMDB system interacts with the MIE system which extracts movie / DVD information from all
kinds of resources. Besides, YMDB system also interacts with the LDD system which provides several popular local
database support (e.g. MySQL, Oracle, DB2 …). The system context diagram is shown in Fig 4.1.
The YMDB, MIE and LDD system are installed in a single PC. YMDB sends a request to MIE, and MIE extracts
the information from the web sites and stores it into local database through LDD. The system overview diagram is
shown in Fig 4.2.
YMDB
SJTU, 2016
Page 7
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
4.2
Assumptions and Dependencies
[List each factor that affects the features stated in the Vision document. List assumptions that, if changed, will alter
the Vision document. For example, an assumption may state that a specific operating system will be available for
the hardware designated for the software product. If the operating system is not available, the Vision document will
need to change.]
The following assumptions and dependencies relate to the capabilities of the YMDB System as outlined in this
Vision Document:
 The MIE System can extract the information from the web pages as required
 The LDD System can manage to store information to several local databases and provide a generic interface as
required
 The MIE System can keep track of the changes in the web pages and make sure it has the same interface to
YMDB System.
5.
Product Features
[List and briefly describe the product features. Features are the high-level capabilities of the system that are
necessary to deliver benefits to the users. Each feature is an externally desired service that typically requires a
series of inputs to achieve the desired result. For example, a feature of a problem tracking system might be the
ability to provide trending reports. As the use-case model takes shape, update the description to refer to the use
cases.
Because the Vision document is reviewed by a wide variety of involved personnel, the level of detail needs to be
general enough for everyone to understand. However, enough detail must be available to provide the team with the
information they need to create a use-case model.
To effectively manage application complexity, we recommend for any new system, or an increment to an existing
system, capabilities be abstracted to a high enough level so 25-99 features result. These features provide the
fundamental basis for product definition, scope management, and project management. Each feature will be
expanded in greater detail in the use-case model.
Throughout this section, each feature will be externally perceivable by users, operators, or other external systems.
These features should include a description of functionality and any relevant usability issues that must be addressed.
The following guidelines apply:
YMDB
SJTU, 2016
Page 8
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
•
Avoid design. Keep feature descriptions at a general level. Focus on capabilities needed and why (not how)
they should be implemented.
•
If you are using the Rational RequisitePro toolkit, all need to be selected as requirements of type for easy
reference and tracking.]
[Define the priority of the different system features. Include, if useful, attributes such as stability, benefit, effort, and
risk.]
This section defines and describes the features of the YMDB System. Features are the high-level capabilities of the
system that are necessary to deliver benefits to the users.
5.1
One-key movie info addition
The system can extract movie / DVD information from famous web sites and add it to local database.
5.2
Manual movie info modification / deletion
After movie information is added in to the database, the user can now manually modify the information or
delete the whole file.
5.3
Update movie info online
The user can choose to update the information of a specific movie online.
5.4
Add personal tags
A personal tag can be added into the movie to include the personal plot summary.
5.5
Add personal reviews
The user can add personal reviews to the movie information and give a score to the movie.
5.6
Advanced search
The user can search the local movie database according to a set of keywords.
5.7
Custom classification
The user can add movie into customized folders to meet his personal needs.
5.8
View front covers thumbnails
The user can view DVD front covers and view the thumbnails slideshow.
5.9
View multiple look-and-feels
The user can choose from several look-and-feels of the GUI.
5.10
Export HTML files
The movie information can be exported to HTML files to view in web browsers.
6.
Other Product Requirements
[At a high level, list applicable standards, hardware, or platform requirements; performance requirements; and
environmental requirements.
Define the quality ranges for performance, robustness, fault tolerance, usability, and similar characteristics that are
not captured in the Feature Set.
Note any design constraints, external constraints, or other dependencies.
YMDB
SJTU, 2016
Page 9
YMDB
Vision
YMDB
Version:
1.0
Date: 05/10/2007
Define any specific documentation requirements, including user manuals, online help, installation, labeling, and
packaging requirements.
Define the priority of these other product requirements. Include, if useful, attributes such as stability, benefit, effort,
and risk.]
6.1
Applicable Standards
The desktop user-interface shall be Windows XP / Vista / Gnome / KDE compliant.
6.2
System Requirements
The client program can be run on PC with no less than 256MB memory. The client program will need
access to the Internet.
6.3
Performance Requirements
The advance search of the local database will cost no more than 5 seconds.
6.4
Platform Requirements
The client program should run on Windows / Linux / Mac OS X with JRE installed.
YMDB
SJTU, 2016
Page 10