Table of Content

Title Page

1. Introduction 1
2. Business Case of the Product 1
3. Analysis Phase 1
3.1 Requirement Analysis 2
3.2 Domain Analysis 3
3.3 User Requirements 3
3.3.1 User Requirement Functions 3
3.3.2 OSS Administrator Functions 3
3.4 Service Requirement Analysis 4
4. Service Domain Analysis 8
5. User Interface 14
6. Conclusion 18
7. References 19

1
 List of Figures

Title Page

Figure 1. Use Case Diagram for OSS 6

Figure 2. Work Flow Diagram for OSS 9
Figure 3. Class Diagram of OSS 11
Figure 4. Entity-Relationship (ER) Diagram for OSS 13
Figure 5. Working Frame for OSS 14
Figure 6. Login Form for OSS 15
Figure 7. Product Subscription Form for OSS 16
Figure 8. A Screen Appearance of OSS showing Transaction Overview 16
Figure 9. A Screen Appearance for Subscription Writer 17

List of Abbreviations

2
 OSS Online Subscription System

NJ Nepal Judiciary

NJA Nepal Judiciary Academy

UML Unified Modeling Language

ER Entity-Relationship

OOAD Object Oriented Analysis and Design

PCS Professional Computer Systems P. Ltd.

1. Introduction

3
 Online subscription system (OSS) is the web based system. OSS provides to sell its
products and services such as news letters, Nepal Law report, bulletin transaction the
laws and case laws and any other physical books, research report etc to its subscriber
through web.

This document is focused to NJA (Nepal Judicial Academy). OSS is developed as a

part of TOR of Europe Aid/127-293/C/SUP/NP contract with European Commission
for the Supply of IT Equipment for the Human Rights and Judicial Sector in Nepal.
Nepal Judicial Academy (NJA) will be the prime stakeholder owner of this product.
NJA service is place bound so it needs to look forward to have better option to
provide services. At present, NJA doesn’t have system to facilitate online subscription
system. People have to be physically present to buy NJA products such as news
letters, research reports, etc. In this digital world it has to walk with new vibes of
development. So NJA needs to develop OSS which will help them to provide their
services to country through internet service. It helps the subscriber to download the
contents or sent through email as per the subscription. It also offer/sell its product
through web which facilitate online sell.

2. Business Case of the Product

NJA is advancing its services through web for sell /offer its products/services. For the
purpose it needs a suitable system which helps them to manage certain data in public
domain information system. For the service provided it allocates certain amounts. The
beneficiaries of the subscription system extend all over the country. For this
infrastructure for internet and e-commerce are being set up in country. The
beneficiaries of the OSS system will be as follows:

 Judges
 Government attorneys
 Government legal officers
 Private law practitioners
 Others who are directly involved in the administration of justice in Nepal.
 Any other public

3. Analysis phase

The analysis is the second phase in the traditional Object-Oriented Process. It is

projected to capture and describe all the requirements of the system, and to make a
model that defines the key domain classes in the system. The purpose is to provide an
understanding and to enable a communication about the system between the
developers and the people establishing the requirements (users/customers). It is the
first step towards understanding the requirements and the reality of the system under
design. The analysis is usually performed in two steps:

4
 1. Requirements Analysis
2. Domain Analysis

3.1 Requirements Analysis

The analysis phase of the OOAD process starts with the Requirements Analysis. The
first step is to define the actors and the use cases of the system. It includes the
requirements of the users of the OSS. Capturing and documenting the requirements of
the system from users is the important aspects of the success. The analysis phase
helps to define the actors of the use cases of the system.

Actors represent roles that are played by the users of the system. Each actor is
someone or something that interacts with the system.
Use Cases describes the behavior of the system when one of the actors sends one
particular stimulus. Use case represents a complete functionality of the OSS as
perceived by an actor. Use case describes the functionality requirements of the OSS.

The users of the OSS are as follows:

 General public
 Member/subscriber
 OSS administrator(Site admin)
 OSS administrator(Finance)
 Editors/Chief editors

General Public are those persons who can browse the public information as view the
list of available subscription, its published date, specific notices/upcoming events.
They can also send queries to site administrator on specific topic if they like. They
can have access to the registration form also.

Members/Subscribers are those who can download the contents and can make
request to extend their validity.

OSS Administrator (Site Admin) is the person who adds, deploys, upload and
disable e-products/services as required by the system.

OSS Administrators (Finance) is the people who administers members and take care
about subscribers’ fee management.

Editors/Chief Editor is responsible for rectifying documents to be deployed in OSS.

3.2 Domain Analysis

5
 The analyses phase of the study, studies the key classes in the system. To conduct a
domain analysis the specifications and the use cases figure out which concepts should
be handled by the system. Once the domain classes are identified, they must be
documented with a description of their semantics, their structure and their behavior.
The structure of a class is represented by its set of attributes. Its behavior is
represented by its operations (methods).

The OSS has to provide the infrastructure for the management of the different types of
users and their products and services. The service can be divided in the following
functions:

3.3 User Requirement

3.3.1 User Management Functions

1. General Public:
 Browse public information
 Download free subscription/e-products
 They have access to view available e-products/services through search
mechanism
 Apply for membership to get access for fee based subscription
 Send queries to administrator

2. Members/Subscribers:
 View the validity
 Send request to extend their membership validity
 View member and general contents
 Download both free subscription and paid subscription
 View the downloaded lists
 Can search the list of subscription using content, author, subject and
date
 Send information regarding payment

3. Editors:
 Converts physical products to understandable pdf/doc/jpeg format

4. Chief Editor:
 Verify the contents to check errors and for up to date publish of e-
products/services
 Add/deploy/update/delete e-products/services

3.3.2 OSS Administrators Functions

1. Site Administrator:
 Add/deploy/upload/disable e-products/services
 Assign translator and keep track of translator(Editors, Chief Editor)

6
 2. Finance Administrator:
 Administer member fee
o Payment methodology
o Confirmation against demand draft/money order
o Confirmation by passing id, password
o Controlling access to relevant materials, research documents,
etc

3.4 Service Requirement Analysis

The UML is a well-defined and widely accepted modeling for modeling software
systems. It is the illustration modeling language for building object-oriented and
component-based systems. It provides a communication method that empowers
organizations to capture and communicate business and technological knowledge.
Such knowledge can be applied to improve value by increasing quality, reducing
costs, and reducing time-to-market while managing risks and being proactive to ever-
increasing change and complexity.

This section provides the detailed requirement analysis for Online Subscription
System. For the connivance of the study we used use case diagram, class diagram, ER
diagram and workflow diagram.

Use case diagrams are used to capture the requirements by creating different scenarios
and to uncover the underlying requirements as well. Use case is a potential
requirement and until the requirement is captured, we will not be able to plan and
move further. Thus, Use case becomes a vital in Object-Oriented modeling which
represents an external view of the system.

Actors

The figure1 is use case diagram showing the actors of the OSS with the relationship
that exists between them. Following are the description for each of the actors:

General Public are those persons who can browse the public information as view the
list of available subscription, its published date, specific notices/upcoming events.
They can also send queries to site administrator on specific topic if they like. They
can have access to the registration form also.

Members/Subscribers are those who can download the contents and can make
request to extend their validity.

OSS Administrator (Site Admin) is the person who adds, deploys, upload and
disable e-products/services as required by the system.

OSS Administrators (Finance) is the people who administers members and take care
about subscribers’ fee management.

7
Editors/Chief Editor is responsible for rectifying documents to be deployed in OSS.

System Administrator is the person who is responsible for creating the user, site
maintenance and system backup.

8
9
Use Cases

Following are the use cases identified for the Online Subscription System.

1. Use cases in the User Management Function

General Public:
 Browse Public Information
 Send Queries
 Download Free Subscription
 Subscribe

Subscription Member:

 Browse Public Information

 Send Queries
 Download Free Subscription
 Send Request To Extend Validity
 View Member Contents
 View Validity
 Download Paid Subscription
 Search Information
 Send Payment Information

Editor:

 Create PDF/DOC/JPEG Products

 Verify Contents
 Check Errors
 Up TO Date For Publish

Chief Editor:

 Manage E-Product Services

2. Use Cases for OSS Administrator Function

Site Administrator

 Add/deploy/upload/disable e-products/services
 Assigns Translator
 Keep track of translator(Editors, Chief Editor)

Finance Administrator
 Control Access

10
  Administer Member Fee
 Confirmation Against Demand/Draft/Money Order

System Administrator
 Create User
 Backup System
 Site Maintenance

Description of the Use Case Diagram required for processing the System

 A User opens the Subscriber Registration Page.

 The system specifies whether the user is registered or general public. If the
user is Authenticated User then he is prompted to enter his account's user
name and password.
 The Authenticated User can perform all the activities provided by the system.
He can request to extend his validity by paying certain charges.
 General public can only browse the public information, send queries and
download subscriptions but is not allowed to download and view paid
subscriptions.
 To access these services general public can register if he likes. The general
public fills-in and submits the Subscriber Registration Form, choosing the
Type of Subscription he wants after completing financial issues. System
Administrator is responsible for creating the new user and backups the system
when ever required.
 The account of the new member is activated and obtains the appropriate access
rights of the subscription. An email message is sent to him, notifying that his
application has been successfully processed. This process is done by Finance
Administrator. The Finance Administrator is responsible for all the function
regarding the payment.
 The Site Administrator adds, uploads, deploys and disables the
e-products/services. Site Administrator also assigns the translator and keeps
the track of translator (Editor/Chief Editor).

3. Services Domain Analysis

This section contains a domain analysis for the Online Subscription System. Figure2
represents the work flow diagram of Online Subscription System.

11
12
The work flow diagram can be illustrated as follows:

 User sends the request to the system.

 System identifies whether the request is valid or not. If valid user i.e.
authenticated user then the user can login for subscription of the product
provided by the system.
 Authenticated user can access both free and paid subscription.
 If the user is general public then the user can have access to the free
subscription only but is unable to access paid subscription.
 General user can register for accessing the paid subscription by paying some
charges as mentioned.
 General public can now access the paid as well as free subscription.

Class Diagram is provided to show the domain classes and their relationships to each
other. Class diagram is the backbone of nearly all the Object-Oriented methods. The
following class diagram shows all the classes for the Online Subscription System
along with their relationships.

13
14
Methods of User Class and its Derived Class are defined as follows:

1. getUserInfo(): fetches the information about the logged on user

2. Login(): validates the user
3. Logout(): destroys the session of the logged on user
4. getPaymentMode(): fetches the information about the mode of payment by the
user
5. depositFee(): deposits the fee of the user
6. withdrawlFee(): withdraws the fee of the user
7. getUserConfirmation(): fetches the information whether the user has paid or not
for subscription
8. getControlAccess(): fetches access control information for each subscription item
9. getPaymentConfirmation(): fetches the information about payment
10. uploadProductServices(): uploads the product services
11. addNewService(): adds the new services in the system
12. deployService(): deploys the services
13. disableService(): disable the product services
14. assignTranslator(): assigns the translator(chief editor)
15. browsePublicInfo(): browses the public information
16. downloadFreeSubscription(): downloads the free subscription items
17. view(): views the available subscription products
18. getMembership():
19. sendQueries(): sends the queries regarding subscription product
20. getValidity(): checks the validity period of the user
21. requestValidity(): requests for extending validity
22. viewContent(): views the content of subscription
23. downloadContent(): downloads the subscription contents (product/services)
24. viewSubscriptionType(): view the type of subscription(weekly/daily/yearly)
25. viewList(): views the list of available services/product
26. searchItemInfo(): searches the information regarding item (product/services)
27. getPaymentInfo(): fetches the information regarding payment of the subscription
28. getPaymentMode(): fetches the information regarding mode of payment for
subscription(cash/draft/money order/cheque)
29. controlAccess(): fetches the access control information about subscription of fee
30. addNewProduct(): adds new product/services
31. deleteProduct(): deletes the product from subscription list
32. updateProduct(): updates the product for subscription
33. deployProduct(): deploys the product
34. getSubscriptionType(): fetches the information about type of
subscription(daily/weekly/yearly)
35. downloadSubscriptionType(): downloads the subscription based upon type of
subscription
36. viewSubscriptionType(): view the type of subscription provided
37. getWeeklySubscription(): fetches the information about weekly subscription

15
38. getDailySubscription(): fetches the information about daily subscription
39. getYearlySubscription(): fetches the information about yearly subscription
40. createUser(): registers the user for login in the system
41. selectSubscription(): selects the required subscription

16
5. User Interface

Fig 5: Working Frame for Online Subscription System

17
18
 Fig 6: Login Form for Online Subscription System

Fig 7: Product Subscription Form for Online subscription System

19
Fig 8: The Screen Appearance of the System Showing Transaction Overview of OSS

20
 Fig 9: The Screen Appearance of the System for Subscription Writer

6. Conclusion

Nowadays business is competing vigorously in a global market filled with

opportunities and risks. They are compelled to think about new technological
methodologies to apply in their business. For the success of the organization business

21
 firms are adopting new technology. In the mean time, NJA cannot lack behind from
the rising advantage of the e-commerce. For better advancement and to provide better
service to its user NJA is adopting Online Subscription System. The system helps
NJA to offer /sell its e-product/services to public through the internet.

The OSS system follows the analysis phase which uses Object Oriented Methodology
followed by Unified Modeling Language.

The Analysis Phase brings the users and developers of a system together uniting them
with a common terminology drawn from the problem domain. As UML is the
fundamental language for building the object oriented and component based systems,
it provides the communication method for empowering organizations to capture and
communicate business and technological knowledge. This results in the less time
wastage and provides better system.

This case-study of OSS has been profitable for us to pursue which has given us an
opportunity to explore the theoretical knowledge acquired during the course of
OOAD.

7. References
 Ashok Kumar Shah, Manoj Maharjan; Supply of IT Equipment for the Human Rights
and Judiciary Sector in Nepal.
 Object Oriented Analysis and Design with application, 2nd edition, Grady Booch.

22