1. 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

2. Final Document
Table of Contents
Introduction ..................................................................................................................................................... 13
Development team & OURS project ................................................................................................................ 13
Problem Statement .......................................................................................................................................... 15
Project background ...................................................................................................................................... 15
Key users ...................................................................................................................................................... 15
Stakeholders ................................................................................................................................................ 16
Assumptions & Constraints of Online University Registration System ......................................................... 17
Vision of Solution ............................................................................................................................................. 17
Vision statement .......................................................................................................................................... 17
Scope ........................................................................................................................................................... 18
List of features ............................................................................................................................................. 18
List of features will not be developed .......................................................................................................... 18
Business Plan & SRS Document ....................................................................................................................... 20
STATEMENT OF WORK ..................................................................................................................................... 21
RESOURCE LIST ................................................................................................................................................ 24
Human ......................................................................................................................................................... 24
Software ...................................................................................................................................................... 24
Hardware ..................................................................................................................................................... 24
ESTIMATION .................................................................................................................................................... 25
Huynh Da Thuc estimation ........................................................................................................................... 25
Phan Duy Tan estimation ............................................................................................................................. 28
Tran Minh Phung estimation ....................................................................................................................... 31
Nguyen Duc Quan estimation ...................................................................................................................... 34
Le Vu Hoang estimation ............................................................................................................................... 37
Estimation Summary .................................................................................................................................... 39
SCHEDULE ........................................................................................................................................................ 43
Task list ........................................................................................................................................................ 43
2

3. Final Document
Gantt chart (reference) ................................................................................................................................ 45
RISK PLAN ........................................................................................................................................................ 46
DISCUSSION SUMMARY ................................................................................................................................... 48
Project background ...................................................................................................................................... 48
Purpose of project ................................................................................................................................... 48
Scope of project ....................................................................................................................................... 49
Perspectives ................................................................................................................................................. 51
Who will use the system? ........................................................................................................................ 51
Who can provide needs about the system? ............................................................................................. 51
Project objectives ........................................................................................................................................ 52
Know business rules ................................................................................................................................. 52
System information and/or diagrams ...................................................................................................... 52
Assumptions and dependencies .............................................................................................................. 54
Design and implementation constraint .................................................................................................... 54
Risks ............................................................................................................................................................. 54
Known future enhancements ...................................................................................................................... 55
References ................................................................................................................................................... 55
Open, unresolved issues ............................................................................................................................. 55
SOFTWARE REQUIREMENT SPECIFICATION ..................................................................................................... 56
USE CASE SPECIFICATION ............................................................................................................................. 56
Log in and Log out .................................................................................................................................... 56
Manage Department Information ............................................................................................................ 58
Manage Lecturer Information .................................................................................................................. 60
Manage Student Information................................................................................................................... 63
Manage Course Offering .......................................................................................................................... 66
Manage Financial Activities ...................................................................................................................... 69
View Academic History ............................................................................................................................ 71
Register Course ........................................................................................................................................ 72
Manage Course Catalogue ....................................................................................................................... 74
Manage User Account .............................................................................................................................. 77
3

4. Final Document
Appendix .................................................................................................................................................. 80
FUNCTIONAL REQUIREMENT ....................................................................................................................... 82
NON-FUNCTIONAL REQUIREMENT .............................................................................................................. 86
Performance: ........................................................................................................................................... 86
Reliability: ................................................................................................................................................ 86
Availability: .............................................................................................................................................. 86
Efficiency:................................................................................................................................................. 86
Supportability: ......................................................................................................................................... 86
Integrity: .................................................................................................................................................. 86
Portability: ............................................................................................................................................... 86
Flexibility: ................................................................................................................................................. 87
INSPECTION REPORT ........................................................................................................................................ 88
GLOSSARY ........................................................................................................................................................ 89
Introduction ................................................................................................................................................. 89
Definitions.................................................................................................................................................... 89
OURS ........................................................................................................................................................ 89
Academic staff ......................................................................................................................................... 89
Finance staff ............................................................................................................................................. 89
Department ............................................................................................................................................. 89
Faculty...................................................................................................................................................... 89
Curriculum ............................................................................................................................................... 89
Subject ..................................................................................................................................................... 89
Course Offering ........................................................................................................................................ 90
Prerequisite.............................................................................................................................................. 90
Course Catalog ......................................................................................................................................... 90
Lecturer .................................................................................................................................................... 90
Student .................................................................................................................................................... 90
Student priority ........................................................................................................................................ 90
Discount rate............................................................................................................................................ 90
Grade ....................................................................................................................................................... 90
4

5. Final Document
Schedule .................................................................................................................................................. 90
Tuition fee ................................................................................................................................................ 90
Credit ....................................................................................................................................................... 90
Academic duration ................................................................................................................................... 90
Academic year.......................................................................................................................................... 91
Testing Plan & Test case Document ................................................................................................................. 93
A- Test Plan .................................................................................................................................................. 94
Introduction ..................................................................................................................................................... 94
Purpose ........................................................................................................................................................ 94
Scope ........................................................................................................................................................... 94
References ................................................................................................................................................... 94
Review requirement and Design ...................................................................................................................... 94
Review system architecture ......................................................................................................................... 95
Features to be tested ....................................................................................................................................... 97
Features not to be tested ................................................................................................................................ 98
Approach ......................................................................................................................................................... 99
Kind of test ................................................................................................................................................... 99
Data and Database Integrity Testing ........................................................................................................ 99
System testing.......................................................................................................................................... 99
Performance Testing .............................................................................................................................. 100
Load Testing ........................................................................................................................................... 100
Stress Testing ......................................................................................................................................... 100
Volume Testing ...................................................................................................................................... 100
Test Strategy .............................................................................................................................................. 100
Checklist of unit test .............................................................................................................................. 100
Unit testing ............................................................................................................................................ 101
Smoke test ............................................................................................................................................. 101
Test Automation .................................................................................................................................... 101
Data and Database Integrity Testing ...................................................................................................... 102
System Testing ....................................................................................................................................... 102
5

6. Final Document
Performance Testing .............................................................................................................................. 103
Load Testing ........................................................................................................................................... 104
Stress Testing ......................................................................................................................................... 105
Volume Testing ...................................................................................................................................... 106
Suspension criteria and resumption requirements ........................................................................................ 107
Suspension criteria..................................................................................................................................... 107
Resumption requirements ......................................................................................................................... 107
Environmental Needs .................................................................................................................................... 108
Tools .......................................................................................................................................................... 108
Software .................................................................................................................................................... 108
Hardware ................................................................................................................................................... 109
Schedule ........................................................................................................................................................ 109
Acceptance criteria ........................................................................................................................................ 110
Resources ...................................................................................................................................................... 110
B- Test Case ................................................................................................................................................ 113
Unit testing .................................................................................................................................................... 113
Test Cases of Log in and Log out Use Case ..................................................................................................... 115
User logs in successfully with valid username and password .................................................................... 115
Fail to login the system when providing invalid username ........................................................................ 115
Fail to login the system when providing username or password containing special character(s).............. 115
Fail to login the system when providing valid username and invalid password ......................................... 116
Fail to login the system when providing empty username ........................................................................ 116
Fail to login the system when providing valid username and empty password ......................................... 117
User account is locked after failing to log in 3 times .................................................................................. 117
User logs in the system using an account is being used by another user................................................... 118
User logs in the system using an account is being locked .......................................................................... 118
Change password successfully ................................................................................................................... 118
Fail to change password when old or new or confirmed password is empty ............................................ 119
Fail to change password when old password is incorrect .......................................................................... 119
Recover the password successfully ............................................................................................................ 120
6

7. Final Document
Fail to reset password when inputting wrong answer for the security question ....................................... 120
Fail to reset password when inputting answer containing special character(s) for the security question . 121
Fail to reset password when inputting empty answer for the security question ....................................... 122
Test Cases of Manage Department Information Use case ............................................................................. 122
Add a department with valid information successfully .............................................................................. 122
Fail to add a department with name that already exists in the system ..................................................... 123
Fail to add a department when one or some or all fields are empty ......................................................... 123
Fail to add a department when inputting special character(s) to one or some or all fields ....................... 124
Update a department with valid information successfully ........................................................................ 125
Fail to update a department with name that already exists in the system ................................................ 125
Fail to update a department when one or some or all fields are empty .................................................... 126
Fail to update a department when inputting special character(s) to one or some or all fields .................. 127
Update cancel ............................................................................................................................................ 127
Delete a department .................................................................................................................................. 128
Delete cancel ............................................................................................................................................. 128
Test Cases of Manage Lecturer Information use case.................................................................................... 129
Add a lecturer with valid information successfully .................................................................................... 129
Fail to add a department when one or some or all fields are empty ......................................................... 129
Fail to add a lecturer when inputting special character(s) to one or some or all fields.............................. 130
Look for a lecturer...................................................................................................................................... 131
Update a lecturer with valid information successfully ............................................................................... 131
Fail to update a lecturer when one or some or all fields are empty .......................................................... 133
Fail to update a lecturer information when inputting special character(s) to one or some or all fields .... 133
Update cancel ............................................................................................................................................ 134
Delete a lecturer ........................................................................................................................................ 135
Delete cancel ............................................................................................................................................. 135
Test Cases of Manage Student Information Use Case ................................................................................... 136
Add a student with valid information successfully..................................................................................... 136
Fail to add a student when one or some or all fields are empty ................................................................ 136
Fail to add a student when inputting special character(s) to one or some or all fields .............................. 137
7

8. Final Document
Search student by student ID or/and by student name ............................................................................. 138
Fail to search student by student ID or/and by student name when providing invalid student ID or/and
student name ............................................................................................................................................. 138
Fail to search student by student ID or/and by student name when providing empty student ID or/and
student name ............................................................................................................................................. 139
Search student by faculty and academic duration ..................................................................................... 139
Search student by academic year, semester, and course .......................................................................... 141
Update a student with valid information successfully ............................................................................... 141
Fail to update a student when one or some or all fields are empty ........................................................... 142
Fail to update a student when inputting special character(s) to one or some or all fields ........................ 142
Update is canceled ..................................................................................................................................... 143
Delete a student ........................................................................................................................................ 144
Delete is canceled ...................................................................................................................................... 144
Test Cases of Manage Course Offering Use Case ........................................................................................... 145
Create list of courses offering successfully ................................................................................................ 145
Update the list of course offering .............................................................................................................. 145
Cancel during the Create list of course offering operation ........................................................................ 146
Cancel during the Update list of course offering operation ....................................................................... 147
Fail to create an empty list of course offering ........................................................................................... 147
Update list of course offering while there’s no list of course offering for specific faculty ......................... 148
Test Cases of Manage Financial Activities Use Case ...................................................................................... 150
View tuition fee by student ID or/and by student name............................................................................ 150
Fail to view tuition fee by student ID or/and by student name when providing invalid student ID or/and
student name ............................................................................................................................................. 150
Fail to view tuition fee by student ID or/and by student name when providing empty student ID or/and
student name ............................................................................................................................................. 151
View tuition fee by faculty or/and by academic duration .......................................................................... 151
View tuition fee by academic year, semester, and course ......................................................................... 152
Update tuition fee status of a student ....................................................................................................... 152
Test Cases of View Academic History Use Case ............................................................................................. 153
View academic history successfully ........................................................................................................... 153
8

9. Final Document
View all course have taken history............................................................................................................. 153
View by specific year and semester. .......................................................................................................... 154
View by passed and failed status. .............................................................................................................. 154
Test Cases of Register Course Use Case ......................................................................................................... 155
Fail to register more than 30 credits .......................................................................................................... 155
Fail to register less than 15 credits ............................................................................................................ 155
Register for courses successfully................................................................................................................ 156
Update the existing schedule successfully ................................................................................................. 157
Test Cases of Manage Course Catalogue Use Case ........................................................................................ 157
Add new course to course catalogue successfully ..................................................................................... 157
Fail to add a course when one or some or all fields are empty .................................................................. 158
Fail to add a course when inputting special character(s) ........................................................................... 159
Search for course by ID or Name ............................................................................................................... 159
Fail to search for course by ID or Name when inputting invalid ID and/or Name ...................................... 160
Fail to search for course by ID or Name when inputting empty ID and/or empty Name ........................... 160
Update course with valid information successfully.................................................................................... 161
Fail to update a course when one or some or all fields are empty ............................................................ 161
Fail to update a course when inputting special character(s) ...................................................................... 162
Update operation is canceled .................................................................................................................... 163
Delete a course .......................................................................................................................................... 163
Delete operation is canceled ..................................................................................................................... 163
Test Cases of Manage User Account Use Case ............................................................................................... 164
Create a new user account successfully ..................................................................................................... 164
Fail to create a new user account when the username that user has provided existing in the system
already ....................................................................................................................................................... 164
Fail to create a new user account when inputting empty username ......................................................... 165
Fail to create a new user account when the inputs containing special character(s) .................................. 166
Search for account by username ............................................................................................................... 166
Fail to search for account by empty username .......................................................................................... 167
Fail to search for account by username that does not exist in the system ................................................ 167
9

10. Final Document
Fail to search for account by username containing special characters(s) .................................................. 167
Update an account ..................................................................................................................................... 168
Update operation is canceled .................................................................................................................... 168
Delete an account ...................................................................................................................................... 169
Delete operation is canceled ..................................................................................................................... 169
Test Cases of Non-functional requirement testing ........................................................................................ 170
Switch from Vietnamese to English ........................................................................................................... 170
Switch from English to Vietnamese ........................................................................................................... 170
Load testing with 15 requests at the same time ........................................................................................ 170
Load testing with 25 requests at the same time ........................................................................................ 171
C- Appendix ................................................................................................................................................ 171
D- Inspection Checklist ............................................................................................................................... 173
The following checklist items apply to the test plan. ..................................................................................... 173
The following checklist items apply to the test cases: ................................................................................... 173
Testing demo ................................................................................................................................................. 176
Unit testing .................................................................................................................................................... 177
Functional requirement testing ..................................................................................................................... 177
Test Cases of Log in and Log out Use Case ..................................................................................................... 177
User logs in successfully with valid username and password .................................................................... 177
Fail to login the system when providing invalid username ........................................................................ 178
Fail to login the system when providing username or password containing special character(s).............. 178
Fail to login the system when providing valid username and invalid password ......................................... 179
Fail to login the system when providing empty username ........................................................................ 179
Fail to login the system when providing valid username and empty password ......................................... 179
User account is locked after failing to log in 3 times .................................................................................. 180
User logs in the system using an account is being used by another user................................................... 180
User logs in the system using an account is being locked .......................................................................... 181
Change password successfully ................................................................................................................... 181
Fail to change password when old or new or confirmed password is empty ............................................ 182
Fail to change password when old password is incorrect .......................................................................... 182
10

11. Final Document
Recover the password successfully ............................................................................................................ 183
Fail to reset password when inputting wrong answer for the security question ....................................... 183
Fail to reset password when inputting answer containing special character(s) for security question ....... 184
Fail to reset password when inputting empty answer for the security question ....................................... 184
Test Cases of Manage Course Offering Use Case ........................................................................................... 185
Create list of courses offering successfully ................................................................................................ 185
Update the list of course offering .............................................................................................................. 186
Cancel during the Create list of course offering operation ........................................................................ 186
Cancel during the Update list of course offering operation ....................................................................... 187
Fail to create an empty list of course offering ........................................................................................... 188
Update list of course offering while there’s no list of course offering for specific faculty ......................... 188
Test Cases of Manage Department Information Use case ............................................................................. 189
Add a department with valid information successfully .............................................................................. 189
Fail to add a department with name that already exists in the system ..................................................... 189
Fail to add a department when one or some or all fields are empty ......................................................... 190
Fail to add a department when inputting special character(s) to one or some or all fields ....................... 191
Update a department with valid information successfully ........................................................................ 191
Fail to update a department with name that already exists in the system ................................................ 192
Fail to update a department when one or some or all fields are empty .................................................... 193
Fail to update a department when inputting special character(s) to one or some or all fields .................. 193
Update cancel ............................................................................................................................................ 194
Delete a department .................................................................................................................................. 194
Delete cancel ............................................................................................................................................. 195
Test Cases of Register Course Use Case ......................................................................................................... 195
Fail to register more than 30 credits .......................................................................................................... 195
Fail to register less than 15 credits ............................................................................................................ 196
Register for courses successfully................................................................................................................ 196
Update the existing schedule successfully ................................................................................................. 198
Non-functional requirement testing .............................................................................................................. 198
Test Cases of Non-functional requirement testing ........................................................................................ 198
11

12. Final Document
Switch from Vietnamese to English ........................................................................................................... 198
Switch from English to Vietnamese ........................................................................................................... 199
Load testing with 15 requests at the same time ........................................................................................ 199
Load testing with 25 requests at the same time ........................................................................................ 199
System architecture introduction .................................................................................................................. 200
How to download & install tools .................................................................................................................... 201
How to install OURS ....................................................................................................................................... 205
How to run OURS ........................................................................................................................................... 207
How to setup and run tests of OURS ............................................................................................................. 208
How to use OURS ........................................................................................................................................... 209
Login and Logout ........................................................................................................................................... 209
Register Course .............................................................................................................................................. 209
View Academic History .................................................................................................................................. 209
Manage Department Information ................................................................................................................. 210
Manage Student Information ........................................................................................................................ 210
Manage Course Offering ................................................................................................................................ 211
Manage Lecturer Information ........................................................................................................................ 212
Manage Financial Activities ........................................................................................................................... 213
Manage Course Catalogue ............................................................................................................................. 214
Manage User Account ................................................................................................................................... 214
12

13. Final 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
13

14. Final Document
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.
SYSTEM ANALYST : Analyze system requirements.
SYSTEM 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
14

15. Final 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.
Key users
STUDENT: use the system to register for course or view academic history.
ADMINISTRATOR: Manage the system after it is built and the authentication mechanism of the
system.
15

16. Final Document
ACADEMIC AFFAIR STAFF: use the system to manage department and faculty, lecturer, student,
course catalogue, list of course offering 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
ADMINISTRATOR : Manage the system after it is built and the authentication mechanism of the
system.
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.
FINANCIAL OFFICE STAFF: use the system to monitor financial activities related to course
registration.
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 members 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.
Development time is limited in 2 months only. Therefore the pressure is really high.
16

17. Final Document
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.
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
17

18. Final Document
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 and log out
View Academic History
Register for course
Manage Department Information
Manage Student Information
Manage Courses Offering
Manage Course Catalogue
Manage Lecturer Information
Manage Financial Activities
Manage User Account
List of features will not be developed
Pay tuition fee (billing system)
Access the system as professor or lecturer
18

19. Final Document
Business Plan &
SRS Document
11/9/2007
Ho Chi Minh National University – International University
Instructor: Phan Viet Hoang
Group 6
Date November 9th , 2007
Version 1.0
Status Baseline
Author Team TiHonMumMim
Reviewer Team TiHonMumMim
Documenter Nguyen Duc Quan
Team member Signature
Nguyen Duc Quan
Le Vu Hoang
Tran Minh Phung
Phan Duy Tan
Huynh Da Thuc
19

20. Final Document
Business Plan & SRS Document
20

21. Final Document
STATEMENT OF WORK
As the head of information systems for International University, our team is tasked with developing
a new Online Course Registration System.
The 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.
The academic affair staffs will use the system as a mean to manage information of
departments, faculties, students and offering courses.
The system also supports financial office staffs in monitoring financial activities.
The features of the systems can be summarized as the following table:
Group of users Features OURS provides
All Users Login and Log out
Academic Affair Staffs Manage Department
Information
Manage Lecturer Information
Manage Course Catalogue
Manage Student Information
Manage Courses Offering
Financial Office Staffs Manage Financial Activities
Students View Academic History
Register for courses
Administrator Manage User Account
Our team is going to develop the system using Rational Unified Process with use-case driven. It
includes four phases (inception, elaboration, construction, and transition). And in each phase, we
will go through 6 workflows only (Management, Requirement, Analysis, Design, Implementation,
and Testing). In fact, all 6 workflows will be done iteratively in each phase. However, attention level
of ours team on each workflow in different phases is different. In particular,
Inception: It can be referred as Initial phase. In this phase we will review the initial system request
from customer, do feasibility study, define the vision and scope of the new system, and the initial
project plan.
21

22. Final Document
Elaboration: It can be referred as planning & requirement phase. In this phase we will pay
attention on detail plan which includes risk plan, estimation, and detail schedule. We also capture
& analyze most of requirements to define the system and analyze its behaviors.
Construction: It can be referred as executing, monitoring, and controlling phase which includes 3
main parts: system design, system implementation, and testing.
Transition: It can be referred as closing phase. In this phase, we will complete and improve the
system, and performance acceptance test to prepare for delivering the system to the stakeholders.
Inception Elaboration Construction Transition
In order to complete the system development, our team will complete the vision and scope
document, project plan and 6 primary development models which are key products of each phase.
[Use-case driven]
Design
Model
Use case Analysis Implementation Test
Model Model Model Model
Deployment
Model
Vision and Scope document: It provides a vision of current problem and solution for the problem.
It also defines what will be developed and what will not be developed. It is done in Inception phase.
Project plan: It is a business plan. It includes statements of works, project estimation, schedule,
and risk plan. It is also done in Inception phase.
Use case model: It is a group of use-case package, which includes one or some related use-cases.
And each use case will contain related users’ needs, goals, tasks, processes…, and resources
22

23. Final Document
involved to it together. It is created after users and stakeholders’ requirements are captured by
business analysts. The most important document included in use case model is use-cases
specification document. Use-case model will be done in Inception & Elaboration phases.
Analysis model: It contains use-cases and theirs realization which includes domain study, analysis
classes and objects, interactions and behaviors of the system. It also defines the design constraints,
test plan and test cases for the system. Analysis model is mainly done in Elaboration phase.
Design model: It includes system design specifications that define the system architecture and
detail design of components, database, graphical user interface, and the constraints for
implementation. Design model is done in Construction phase.
Deployment model: It defines how we can deploy the system so that it can run on server(s).
However, we intent to develop the system running on one server only, not distributed on many
server. Therefore, we will not pay much attention on deployment model. This model will be done in
Construction phase.
Implementation model: It defines the way we transfer from logical system architecture into
physical system architecture; test components (unit testing) and integrate them together in order
to form a unique system that satisfies users and stakeholders’ needs.
Test model: It includes many checklists and test cases that are planned and designed in previous
phases. It also requires all defects or errors to be recorded in defects and errors reports. It is done
in Construction phase.
The detail of each workflows and models will be presented in detail schedule, and the plan for each
phase.
Development team will use web-base and J2EE technologies to develop the system.
23

24. Final Document
RESOURCE LIST
Human
Team member Main roles Responsibilities
Tran Minh Phung Tester, Integrator Integrate, test components, builds, and system
Le Vu Hoang System Designer, Coder Design components, system and implement
components
Huynh Da Thuc Tester, UI Designer Design graphical user interface, and test components,
builds, and system
Phan Duy Tan System Analyst, Coder Analyze system and implement front end of the
system
Nguyen Duc Quan Team leader, Business Monitor, control the project; analyze requirements
Analyst, Documenter and system behaviors; and do documentation
Software
Documentation tool Microsoft word 2007
Scheduling tool Microsoft project 2007
IDE Netbean 6.0
Web Server Glassfish server 2.0
Photoshop CS2
Design tool
Microsoft Express Web Designer
JDK JDK 6.0
DBMS MySQL 5.0
Browser Internet Explorer 6.0, 7.0
Firefox, Opera
Operating system Windows XP, Vista, Linux
Hardware
Client 3 laptops
2 desktops
Server Reuse one 24/7 available desktop to simulate the server for testing
and deployment
24

25. Final Document
ESTIMATION
Huynh Da Thuc estimation
Name : Huynh Da Thuc Date: 11/09/2007 Estimation form ///
Goal statement: To estimate the time to develop prototype for customer A and B Unit: days
Category x goal tasks x quality tasks waiting time project overhead
No. Task Est Del1 Del2 Del3 Del4 Total Assumption
Initial
1 Write team introduction 3 1 4
The system request is quite complex than initial
2 Review system request 4 2 1 -4 3 review
The key user and stakeholder varies and
3 Identify User and Stakeholder 4 -4 3 3 changes
Gather user and stakeholder
2 3 5 -5 5 Difficult in getting appointment and interview
4 ideas
5 Write Project background 2 0.5 0.5 3
6 Write Vision statement 1 2 3 6
7 Write Scope statement 2 -1 1 2 The scope is quite simple
8 Identify risks and assumption 2 0.5 2.5
The document should be review again and
9 Complete vision and scope 1 0.5 0.5 2 check any existing error
10 Team Review 3 -1 2 Team gather late and far distance
11 Review 1 3 0.5 0.5 4
Planning
1 Complete statements of works 2 1 3 Statement of works is more complex
Risk varies and should be coherent between
2 Plan for risk 4 1 -1 4 the team members
3 WBS 2 3 -1 1 5
4 Estimation & assumption 1 0.5 0.5 2 Idea should be coherent
5 Schedule 0.5 0.5 1 2
The document is long and complex, need more
6 Discussion summary 2 3 1 7 time to review
7 Analyze initial requirement 2 2 2 6
Understand stakeholder & user
8 needs 1 1 -2 2 2
9 Complete glossary 2 1 1 4 The glossary should be exact and complete
10 Login use case 1 1 -2 3 3
11 Manage faculty use case 1.5 2
12 Manage lecturer use case 1 1 1 3 The use case should be reviewed many times
13 Manage student use case 0.5 2 3 The use case should be reviewed many times
14 Manage courses offering 2 1 1 4 The use case should be reviewed many times
15 View academic history 2 2 1 5
25

26. Final Document
16 Register courses use case 3 1 1 1 6
17 Manage financial activities 3 2 -3 1 3 Financial activities are quite complex
Complete functional
18 requirement 1 1 -4 4 2
Complete non-functional
19 requirements 2 1 3
20 Define the system 1 1 3 1 6 Team should consider carefully this part
Manage the scope of the
21 system 2 1 1 1 5
Requirement is complex and should be
22 Complete SRS 1 1 1 3 reviewed more
23 SRS inspection 0.5 1 2
24 Test Plan 1.5 1 3
25 Test case 2 1 3
26 Detail WBS 2 2
27 Re-estimation & assumption 1.4 1 2
28 Detail Schedule 1.5 2
29 Team review 1 2 3
30 Review 2 2 2
Executing
1 Define candidate architecture 1.5 2
2 Refine the architecture 1 1 2 Refinement should last for more session
3 Analyze behaviors 2 2
4 Complete analysis model 2 1 3
Complete design model &
5 system architecture 1 1 1 3 The architecture grows rapidly
6 Design GUI 2 1 3
7 Design database 1.5 2
8 Design persistence layer 2 1 3
9 Design business logic layer 1.5 2
10 Design presentation layer 1.5 1 3
11 Design test case 2 2
Complete Implementation
12 model 1 1 2
Complete Implementation
13 guidelines & code conventions 2 2
14 Produce Integration build plan 1 1
15 Review OOAD 1 1
16 Create file structure of system 1 1
17 Implement GUI 10 10
18 Implement database 9 2 11 No experience in using MySQL
19 Implement persistence layer 11 11
26

27. Final Document
20 Implement business logic layer 9 9
21 Implement presentation layer 9 9
Review code & update
22 changes 2 1 3 Fixing bugs and updates encounter difficulty
23 Integrated build 2 2
24 Do integration test 1 1 2
25 Test build 1 1 2
26 Test system 2 1 3 System should be tested well
Inspection meeting should be established
between this duration to ensure the report is
27 Complete test report 6 2 8 defection-free and coherent
28 Rework 4 2 6
29 Team review & evaluation 1 1 2
30 Review 3 1 2 3
Closing
Need coherence and re-check logic
1 Complete source code 6 2 4 12 functionality
2 Complete User Manual 3 2 1 1 7 User manual must be in detail
3 Do acceptance test 3 1 1 5 Acceptance test is brand new to team
4 Team review & evaluation 2 2
5 Complete all documents 2 2 3 7
6 Review 4 2 2
27

28. Final Document
Phan Duy Tan estimation
Name : Phan Duy Tan Date: 11/09/2007 Estimation form ///
Goal statement: To estimate the time to develop prototype for customer A and B Unit: days
Category x goal tasks x quality tasks waiting time project overhead
No.
Task Est. Del1 Del2 Del3 Del4 Total Assumption
Initial
1 Write team introduction 0.5 0.5 1 discuss
2 Review system request 0.5 0.5 1 additional requirement
3 Identify User and stakeholder 1 1 1 3 Interview
2 members do not know requirements provides
Login use case 4 -2 2
4 last year
5 Write Project background 1 1 2 Spend time to understand current problem
6 Write Vision statement 0.5 0.5 1 review
7 Write Scope statement 0.5 0.5 1 review
8 Identify risks and assumption 3 -1 2 4 cannot find all risk and assumption
All parts of Vision and Scope document have to
Complete vision and scope 0.5 0.5 1
9 be finished
10 Team Review 1
11 Review 1 0.5 0.5
Planning
1 Complete statements of works 0.5 0.5
2 Plan for risk 6 4 -1 9 Need a lot of meeting to identify mitigation plan
3 WBS 0.5 0.5
4 Estimation & assumption 1 1
5 Schedule 0.5 0.5
6 Discussion summary 1 1
7 Analyze initial requirement 2 1 3 Review
Understand stake holder &
8 user needs 2 2
9 Complete glossary 0.5 0.5 1 Double-check term definitions
10 Login use case 1 1
11 Manage faculty use case 1 1
12 Manage lecturer use case 1 1
13 Manage student use case 2 2
28

29. Final Document
There are many solutions in solving problem of
Manage courses offering 4 -1 1 4 course offering management. It is difficult to
14 choose one
15 View academic history 1 1
16 Register courses use case 4 -1 3 Team brainstorming
17 Manage financial activities 2 -1 1 only simple activities
Complete functional
18 requirement 3 3
Complete non-functional
19 requirements 3 3
20 Define the system 2 1 3 Review
Manage the scope of the
21 system 2 2
22 Complete SRS 1 1 2 Use cases are written in details
23 SRS inspection 1 1
24 Test Plan 2 1 3 No experience
25 Test case 2 1 3 Review
26 Detail WBS 0.5 0.5
27 Re-estimation & assumption 0.5 0.5 1 Under-estimate tasks
28 Detail Schedule 0.5 0.5
29 Team review 1 1
30 Review 2 1 1
Executing
1 Define candidate architecture 3 2 5 J2EE architecture is complex
2 Refine the architecture 1 1 2 J2EE architecture is complex
3 Analyze behaviors 1 1
4 Complete analysis model 1 1
Complete design model &
5 system architecture 2 1 3 Review
6 Design GUI 1 1
7 Design database 2 2
8 Design persistence layer 1 1
9 Design business logic layer 1 1
10 Design presentation layer 1 1
11 Design test case 2 1 3 test case document
Complete Implementation
12 model 2 2
Complete Implementation
13 guidelines & code conventions 0.5 0.5
14 Produce Integration build plan 0.5 1
15 Review OOAD 0.5 0.5 1 Debate
16 Create file structure of system 0.5 0.5 1 Packaging
29

30. Final Document
Tan has a lot of experience in implementing
17 Implement GUI 6 -1 -1 1 5 GUI
18 Implement database 4 4 2 1 11 First time using MySQL
19 Implement persistence layer 9 9
20 Implement business logic layer 10 10
21 Implement presentation layer 6 1 7 Environment integration
Review code & update
22 changes 1 1
23 Integrate build 1 1
24 Do integration test 2 -1 1 No experience
25 Test build 2 2
26 Test system 2 2
27 Complete test report 3 2 5 Fix new defects
28 Rework 3 3
29 Team review & evaluation 1 1
30 Review 3 1 1
Closing
1 Complete source code 10 -1 -1 8 use IDE
2 Complete User Manual 6 -1 5 Thuc has a very good writing skill
3 Do acceptance test 3 3
4 Team review & evaluation 1 1
5 Complete all documents 3 3
6 Review 4 1 1
30

31. Final Document
Tran Minh Phung estimation
Name : Tran Minh Phung Date: 11/09/2007 Estimation form ///
Goal statement: To estimate the time to develop prototype for customer A and B Unit: days
Category x goal tasks x quality tasks waiting time project overhead
No. Task Est Del1 Del2 Del3 Del4 Total Assumption
Initial
1 Write team introduction 2 0.5 0.5 3 Understanding the problems
2 Review system request 2 1 0.5 0.5 4
3 Identify User and Stakeholder 2 0.5 0.5 3
Gather user and stakeholder
3 1 1 5 Use all existed documents
ideas
4
5 Write Project background 1 1 2 4
6 Write Vision statement 3 1 1 0.5 0.5 6
7 Write Scope statement 4 1 2 7
8 Identify risks and assumption 1 0.5 0.5 1 3
9 Complete vision and scope 1 0.5 0.5 2 Have enough all information
10 Team Review 1 1
11 Review 1 1 1
Planning
Vision and Scope documents is baseline
1 Complete statements of works 1 0.5 0.5 2
Candidate risks must be listed out already
2 Plan for risk 3 2 1 1 5
3 WBS 4 0.5 0.5 1 6
4 Estimation & assumption 1.5 0.5 2
5 Schedule 2 1 3
6 Discussion summary 6 1 7
7 Analyze initial requirement 2 2
Understand stake holder &
8 user needs 1 1 1 3
9 Complete glossary 4 1 0.5 0.5 5
10 Login use case 3 0.5 0.5 4
31

32. Final Document
11 Manage faculty use case 2 0.5 0.5 3
12 Manage lecturer use case 3 0.5 0.5 4
13 Manage student use case 3 1 4
14 Manage courses offering 3 1 4
15 View academic history 4 1 1 6
16 Register courses use case 4 1 1 1 7
17 Manage financial activities 1 0.5 2
Complete functional
18 requirement 1 1
Complete non-functional
19 requirements 3 1 4
20 Define the system 7 0.5 0.5 8
Manage the scope of the
21 system 8 1 2 11
22 Complete SRS 1 1
23 SRS inspection 1 1
24 Test Plan 2 1 3
25 Test case 2 1 3
26 Detail WBS 2 2
27 Re-estimation & assumption 1 1
28 Detail Schedule 1 1
29 Team review 1 1
30 Review 2 1 1
Executing
1 Define candidate architecture 1 1 2
2 Refine the architecture 1 1
3 Analyze behaviors 1 1
4 Complete analysis model 2 2
Complete design model &
5 system architecture 2 2
6 Design GUI 1 1 2
7 Design database 1 1 2
8 Design persistence layer 1 1 2
9 Design business logic layer 1.5 0.5 2
10 Design presentation layer 1.5 0.5 2
11 Design test case 1.5 0.5 2
Complete Implementation
12 model 2 2
Complete Implementation
13 guidelines & code conventions 1 1
14 Produce Integration build plan 2 2
15 Review OOAD 1 1
32

33. Final Document
16 Create file structure of system 1.5 0.5 2
17 Implement GUI 10 2 12
18 Implement database 8 1.5 0.5 10
19 Implement persistence layer 9 0.5 0.5 10
20 Implement business logic layer 8 0.5 0.5 1 10
21 Implement presentation layer 7 2 1 10
Review code & update
22 changes 1 1 2
23 Integrate build 1 1 2
24 Do integration test 1 1 2
25 Test build 1 0.5 0.5 2
26 Test system 3 3
27 Complete test report 6 2 1 9
28 Rework 5 2 7
29 Team review & evaluation 1 1 2
30 Review 3 1 1
Closing
1 Complete source code 10 1 1 1 13
2 Complete User Manual 6 1 1 8
3 Do acceptance test 4 2 6
4 Team review & evaluation 1 2 3
5 Complete all documents 4 3 1 8
6 Review 4 1 1
33

34. Final Document
Nguyen Duc Quan estimation
Name :Nguyen Duc Quan Date: 11/09/2007 Estimation form ///
Goal statement: To estimate the time to develop prototype for customer A and B Unit: days
Category x goal tasks x quality tasks waiting time project overhead
No. Task Est Del1 Del2 Del3 Del4 Total Assumption
Initial
1 Write team introduction 1 2 -1 2
2 Review system request 1 1 2
3 Identify User and Stakeholder 2 1 -1 2
Gather user and stakeholder Use existing requirements provided last year,
1 1
ideas additional requirements
4
5 Write Project background 1 1
6 Write Vision statement 1 1
7 Write Scope statement 1 1
this task must be done along the summary
task
8 Identify risks and assumption 4 2 2 -2 6
9 Complete vision and scope 0.5 0.5 1 must do informal review
10 Team Review 1 1
11 Review 1 1 1
Planning
1 Complete statements of works 0.5 0.5 1
lack of experience in risk mitigation
2 Plan for risk 8 2 1 -2 11
3 WBS 1 1
4 Estimation & assumption 1 1
5 Schedule 1 1
must be more detail than vision and scope
6 Discussion summary 1 0.5 0.5 2
7 Analyze initial requirement 1 1 2
Understand stake holder &
8 user needs 2 2
34

35. Final Document
9 Complete glossary 2 2
10 Login use case 3 -1 2 Login is a popular function
11 Manage faculty use case 2 1 3
12 Manage lecturer use case 2 1 3
13 Manage student use case 2 1 3
14 Manage courses offering 2 1 3 3 members are familiar with old requirements
15 View academic history 2 1 3
16 Register courses use case 2 1 3
17 Manage financial activities 2 1 3
Complete functional
18 requirement 1 1 1 3
Complete non-functional
19 requirements 1 1 1 3
20 Define the system 1 1 1 3
Must perform scope management during the
requirement phase
Manage the scope of the
21 system 6 2 1 1 10
22 Complete SRS 1 1
23 SRS inspection 1 1
24 Test Plan 1 1 2
25 Test case 1 1 2
26 Detail WBS 1 1
27 Re-estimation & assumption 1 1
28 Detail Schedule 1 1
29 Team review 1 1
30 Review 2 1 1
Executing
1 Define candidate architecture 2 1 3
2 Refine the architecture 1 1
3 Analyze behaviors 1 1
4 Complete analysis model 1 1
Complete design model &
5 system architecture 1 1
6 Design GUI 1 1 2
7 Design database 1 1
8 Design persistence layer 1 1
9 Design business logic layer 1 1
10 Design presentation layer 1 1
35