Vision and Scope document

1. Vision and Scope Document
Vision and Scope Document
10/12/2007
Ho Chi Minh National University – International
University
Instructor: Phan Viet Hoang
Date October 10th , 2007
Version 1.0
Status Baseline
Author Team TiHonMumMim(Group 6)
Reviewer Team TiHonMumMim(Group 6)
Documenter Nguyen Duc Quan
Team member Signature
Nguyen Duc Quan
Le Vu Hoang
Tran Minh Phung
Phan Duy Tan
Huynh Da Thuc
1

2. Faculty of Computer Science and Engineering
Table of Contents
Introduction ......................................................................................................... 05
Development team and OURS project ..................................................................05
Problem Statement ...............................................................................................07
Project Background ...............................................................................................07
Key Users .........................................................................................................08
Stakeholders .....................................................................................................08
List of Risks .......................................................................................................08
Assumptions and Constraints of OURS .............................................................09
Vision of Solution ..................................................................................................10
Vision of Statement ..........................................................................................10
Scope ................................................................................................................10
List of Feature ...................................................................................................10
Features not developed ....................................................................................11
2

3. Vision and Scope Document
Introduction
This is the Vision and Scope document of OURS project. Like any other Vision and
Scope document, this document will cover the problem and vision statement
including project background, list of users, stakeholders, candidate risks,
assumptions & constraints, and project scope. In addition, the document will also
cover the part of development team introduction.
Development team & OURS project
TiHonMumMim is a small software development team set up in 2007 by 5 students
of International University. The structure of the team includes 3 software engineers,
1 system & networking engineer, and 1 team leader.
Our business goal is to be a leading company in IT. And our slogan is “Computing,
consulting, and programming professionally” (CC&PP).
For more information about our team:
Email: TiHonMumMim@yahoo.com
Blog: http://360.yahoo.com/TiHonMumMim
3

4. Faculty of Computer Science and Engineering
We are assigned to build Online University Registration System (OURS). The internal
development team structure and roles on OURS project:
OURS project
Team leader
Documenter Tester Coder Integrator
Business System System UI
Analyst Analyst Designer Designer
TEAM LEADER: Responsible for all project management.
DOCUMENTER: Responsible for documentation from other members’ according to the
RUP document standard.
BUSINESS ANALYST: Capture and analyze user requirements.
S YSTEM ANALYST: Analyze system requirements.
S YSTEM DESIGNER: Design the internal structure and operations of system.
UI DESIGNER: Design user interface for the system.
CODER: Responsible for implementing the system.
INTEGRATOR: Integrate the system components.
TESTER: Responsible for testing activities.
Team member ID Email Main roles
Tran Minh Phung 090401096 toyohiko1507@yahoo.com Tester, Integrator
Le Vu Hoang 090401019 smallwildcat_86@yahoo.com System Designer, Coder
Huynh Da Thuc 090401121 runnfire@yahoo.com Tester, UI Designer
Phan Duy Tan 090401044 kingduytan@yahoo.com System Analyst, Coder
Nguyen Duc Quan 090401038 duc.quan@yahoo.com Team leader, Business
Analyst, Documenter
4

5. Vision and Scope Document
Problem Statement
Project background
There is a widespread agreement that the policy in course registration is very
complicated, costly, take-time, and inconvenient to both students and university. This is
due the fact that at the beginning of each semester, the university has to pause or delay
some activities to spend time for course registration of students. Some staffs have to
prepare for offering courses list (including selecting courses and inviting lecturers …),
print it out, and deliver the registration form to each student. After around one week, all
students’ registration form will be returned. And the staffs have to input students’
registration information to Excel files. They also have to check manually whether the
registration form of each student is legal or not basing on some conditions such as
prerequisite course, maximum and minimum number of credits allowed to register … If
there is anything wrong or students want to add or drop the courses, everything in the
above process has to be restarted. And sometimes some papers are lost when
documents are moved from one place to another place; both students and university
have to spend time for retrieving necessary information and approve it. However, it is
impossible to do that in some cases.
In addition, calculating tuition fee for students, managing students’ academic
history… are also thorny issues. Mistakes can occur anytime when financial office‘s
staffs use calculator or Microsoft excel to calculate tuition fee.
Students’ transcript management is also another issue. When students want to have
transcript to see their academic history, they have to wait at least two weeks to receive
it from academic affair.
Those are some typical examples for the inconvenience and complication of the
current course registration policy. They lead the university to the decision of building
Online Course Registration System to improve effectiveness, reduce time and cost in
course registration process.
5

6. Faculty of Computer Science and Engineering
Key users
STUDENT : use the system to register for course or view academic history.
ACADEMIC AFFAIR STAFF: use the system to manage school, lecturer-professor, and
student information.
FINANCIAL OFFICE STAFF: use the system to monitor financial activities related to
course registration.
Stakeholders
STUDENT : use the system to register for course or view academic history.
ADMINISTRATOR: Manage the system after it is built.
ACADEMIC AFFAIR STAFF : use the system to manage school, lecturer-professor, and
student information.
PROFESSOR LECTURER: They could give ideas or comment on the solution for the
system’s development and improvement.
FINANCIAL OFFICE MANAGER: They also manage the investment of university for the
system development.
DEVELOPMENT TEAM : include all software engineers, business analysts, system
analysts, system designers, implementers, testers, QA, and project manager… They
are tasked to build the system.
List of Risks
All team member need preparation time for midterm, final exam, and
other subjects.
Phung, Thuc, and Hoang take pre-thesis course.
Lack of experiences in software project management, especially in
testing, verification, validation, risks management and changes
management exists in the Team.
No substitution if any team member cannot continue to contribute to the
project. Applying the project again from the beginning could take
development team more time.
6

7. Vision and Scope Document
Development time is limited in 2 months only. Therefore the pressure is
really high.
Development team cannot deliver the components when reviewed.
Development team could deliver components of unacceptably low
quality, and time must be added to improve quality.
Developing extra functionalities that are not required will extends the
schedule.
Low motivation and moral reduce productivity.
Team member needs extra time to learn unfamiliar tools or techniques.
Conflicts among team members’ ideas results in poor performances,
more meeting, and extra rework.
People’s assignments do not match their strengths.
Components developed separately cannot be integrated easily, requiring
redesign and rework.
Detail reporting could take more development time.
Assumptions & Constraints of Online
University Registration System
The system will be applied for universities using credit system like
International University.
The registration information of students is processed by academic affair. And
only academic affair has right to manage and process the registration
information.
Development team will use J2EE architecture to develop system.
Policy for tuition fee payment is using cash and it is managed by financial
office.
Development team must have at least one 2-hour meeting per week.
Development time 2 months and 10 days (from 01/10/2007 to 20/12/2008)
Development team must produce the first build before review 3
(05/12/2007).
Each team member must work at least 15 hours per week.
7

8. Faculty of Computer Science and Engineering
Vision of Solution
Vision statement
As the head of information systems for International University team are tasked with
developing a new Online Course Registration System. The new system will allow
students to access the system during registration time to register for courses, add or
drop the registered courses, check tuition fee, and review their academic history.
Academic affair can use the system as a mean to manage information of schools,
classes, professors, students and offering courses. Financial office will use the system to
monitor financial activities. The system provides a better solution and policy for course
registration in International University. It reduces much time, cost, and resources
required in processing registration information of students.
Scope
To be noticed on the scope of the system that this system is an Online University
Registration System. It is not a university management system which is much larger
than the system we try to build. It is only a part of the university management system.
Therefore, we have to pay attention on building applications supporting students to do
registration, academic affairs to manage information related to students’ courses
registration, and financial office to mange financial activities.
List of features
User login
View Academic History
Register for course
Manage School Information
Manage Student Information
Manage Offering Courses
Manage Professor Information
Manage Financial Activities
8

9. Vision and Scope Document
List of features will not be developed
Pay tuition fee (billing system)
Access the system as professor or lecturer
9