Implementing HIS with AHP Method
VerifiedAdded on 2020/04/15
|16
|2934
|43
AI Summary
This assignment delves into the implementation of a Hospital Information System (HIS) leveraging the Analytic Hierarchy Process (AHP) method. It examines various aspects of HIS implementation, drawing upon relevant research and case studies. The focus is on applying AHP to analyze and prioritize key factors involved in successful HIS implementation within a hospital setting.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Running Head: REQUIREMENTS ANALYSIS AND MODELLING
Requirements Analysis and Modelling: Case Study of Lilydale Movies
Name of the Student
Name of the University
Requirements Analysis and Modelling: Case Study of Lilydale Movies
Name of the Student
Name of the University
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
1REQUIREMENTS ANALYSIS AND MODELLING
Executive Summary
This project is based on the development of centralized data server in Lilydale Movies in order to
connect all the branches together with a common management system. The main objective is to
address a number of problems that are existing in the current system and accordingly, in this
report, a plan has been created for implementation. The plan includes use case diagram and
descriptions that can be used as system blueprint and further development plan can be created
accordingly.
Executive Summary
This project is based on the development of centralized data server in Lilydale Movies in order to
connect all the branches together with a common management system. The main objective is to
address a number of problems that are existing in the current system and accordingly, in this
report, a plan has been created for implementation. The plan includes use case diagram and
descriptions that can be used as system blueprint and further development plan can be created
accordingly.
2REQUIREMENTS ANALYSIS AND MODELLING
Table of Contents
Task Part A......................................................................................................................................3
1.0 Introduction............................................................................................................................3
2.0 Problems to Solve..................................................................................................................4
3.0 Scope and System Requirements...........................................................................................5
4.0 User Stories and Acceptance Criteria....................................................................................6
5.0 Recommendations..................................................................................................................7
6.0 Conclusion.............................................................................................................................8
Task Part B......................................................................................................................................9
7.0 Use Case Diagram.................................................................................................................9
8.0 Use Case Descriptions.........................................................................................................10
9.0 Activity and Sequence Diagrams.........................................................................................12
References......................................................................................................................................15
Table of Contents
Task Part A......................................................................................................................................3
1.0 Introduction............................................................................................................................3
2.0 Problems to Solve..................................................................................................................4
3.0 Scope and System Requirements...........................................................................................5
4.0 User Stories and Acceptance Criteria....................................................................................6
5.0 Recommendations..................................................................................................................7
6.0 Conclusion.............................................................................................................................8
Task Part B......................................................................................................................................9
7.0 Use Case Diagram.................................................................................................................9
8.0 Use Case Descriptions.........................................................................................................10
9.0 Activity and Sequence Diagrams.........................................................................................12
References......................................................................................................................................15
3REQUIREMENTS ANALYSIS AND MODELLING
Task Part A
1.0 Introduction
This case is about the Lilydale Movies, a Melbourne-based company that deals with the
rent and sale of movies to the customers. The owners of the company first founded it for
addressing the gaps that were existing in the contemporary movie businesses where the stores
only sold latest and updated popular movies for instant revenue and profit (Laudon & Laudon
2016). However, the owners emphasized the need for a company that will sell all types of movies
(not only popular latest movies) including past popular movies, international movies of various
languages and others. The company is now operating with five separate branches in Melbourne.
However, the main problem that has arisen is that although each of the branches has its own
database server, none of them are connected together (Arvidsson, Holmström & Lyytinen 2014).
As a result, there is no direct connection between the stores and hence, calculation of overall
business data is extremely hard. In order to address this issue, the company is willing to
implement a new centralized and common database server to which, the databases of the five
branches will be connected. This will help the company to maintain an operational continuity in
their business in all the branches as well as create opportunities for further expansion.
The purpose of this project is to develop a new information system for Lilydale Movies
for creating a centralized data server to which all the stores will be connected. This report is a
documentation of the project plan and in order to prepare this document, data will be collected
from the company operations, existing technical setups, requirements and other data sources that
contain significant information regarding implementation of information systems.
Task Part A
1.0 Introduction
This case is about the Lilydale Movies, a Melbourne-based company that deals with the
rent and sale of movies to the customers. The owners of the company first founded it for
addressing the gaps that were existing in the contemporary movie businesses where the stores
only sold latest and updated popular movies for instant revenue and profit (Laudon & Laudon
2016). However, the owners emphasized the need for a company that will sell all types of movies
(not only popular latest movies) including past popular movies, international movies of various
languages and others. The company is now operating with five separate branches in Melbourne.
However, the main problem that has arisen is that although each of the branches has its own
database server, none of them are connected together (Arvidsson, Holmström & Lyytinen 2014).
As a result, there is no direct connection between the stores and hence, calculation of overall
business data is extremely hard. In order to address this issue, the company is willing to
implement a new centralized and common database server to which, the databases of the five
branches will be connected. This will help the company to maintain an operational continuity in
their business in all the branches as well as create opportunities for further expansion.
The purpose of this project is to develop a new information system for Lilydale Movies
for creating a centralized data server to which all the stores will be connected. This report is a
documentation of the project plan and in order to prepare this document, data will be collected
from the company operations, existing technical setups, requirements and other data sources that
contain significant information regarding implementation of information systems.
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
4REQUIREMENTS ANALYSIS AND MODELLING
2.0 Problems to Solve
There are several problems that need to be solved through the course of this project.
These problems are explained as follows.
Lack of Centralized Server – Every successful large scale business organization has a
centralized database server to which, all other systems (including the ones from different
branches) are connected together (Ahmadi et al. 2014). This central server is used to store all the
business related data from the different operational branches including international branches if
any. The use of central server will allow the management team to have more control over the
business organizations in all the branches of the company.
Classification and Categorization – Another existing problem to be addressed is the lack
of any classification system that can automatically analyze the movies and categorize them
according to genres and release dates. In the current system, there is no search option and the
sellers at the branches need to manually search the database to find the movie wanted by the
customer (Xu et al. 2014). The new automated information system will be able to solve this
problem as its internal algorithm will allow the user to search for the movie by using
genre/release date filter without having to search the entire database for one movie.
Movie of Demand – The third problem to be addressed through this problem is the lack
of sufficient inventory space in each of the stores of the company. Due to this, the inventory
cannot be filled by all listed movies at a time and as a result, some customers are not able to find
their movies of choice (Ismail et al. 2013). In order to address this, the company has proposed to
update the inventories with only the movies that are popular in that particular area. However, for
achieving this target, usage figures will be required and that can be done by implementing the
2.0 Problems to Solve
There are several problems that need to be solved through the course of this project.
These problems are explained as follows.
Lack of Centralized Server – Every successful large scale business organization has a
centralized database server to which, all other systems (including the ones from different
branches) are connected together (Ahmadi et al. 2014). This central server is used to store all the
business related data from the different operational branches including international branches if
any. The use of central server will allow the management team to have more control over the
business organizations in all the branches of the company.
Classification and Categorization – Another existing problem to be addressed is the lack
of any classification system that can automatically analyze the movies and categorize them
according to genres and release dates. In the current system, there is no search option and the
sellers at the branches need to manually search the database to find the movie wanted by the
customer (Xu et al. 2014). The new automated information system will be able to solve this
problem as its internal algorithm will allow the user to search for the movie by using
genre/release date filter without having to search the entire database for one movie.
Movie of Demand – The third problem to be addressed through this problem is the lack
of sufficient inventory space in each of the stores of the company. Due to this, the inventory
cannot be filled by all listed movies at a time and as a result, some customers are not able to find
their movies of choice (Ismail et al. 2013). In order to address this, the company has proposed to
update the inventories with only the movies that are popular in that particular area. However, for
achieving this target, usage figures will be required and that can be done by implementing the
5REQUIREMENTS ANALYSIS AND MODELLING
information system. This information system will analyze the sales data and prepare the usage
figures based on which, the inventories of the stores can be updated.
Member Registration – In the current setup, the company offers memberships to the
customers with some additional benefits than the regular customers. However, since none of the
stores are connected to each other, the membership of a customer in one store cannot be
recognized by another one. As a result, the customer is not able to gain membership benefits
from other stores although he is eligible for offers from the company itself. The new connected
server will allow each store to share information with others including approved membership
requests so that the customers are able to get premium benefits from all the stores.
However, the two main problems that have been selected to be addressed through the
proposed system in this particular project are developments of centralized server and the
common membership portal that will be accessed by all the branch stores of the company. This is
mainly because creation of the central database should be the top priority of the company to
maintain business continuity and the common membership portal will help the customers to
apply membership benefits in all the stores of the company. Furthermore, these two problems
can be addressed easily by one particular system and hence, they have been chosen for this
project.
3.0 Scope and System Requirements
The overall scope of the project involves development of information system that will be
able to address all the above mentioned problems. The scope statement includes the following:
Development of centralized server is within the scope of the project.
Development of the auto-classification system is within the scope of the project.
information system. This information system will analyze the sales data and prepare the usage
figures based on which, the inventories of the stores can be updated.
Member Registration – In the current setup, the company offers memberships to the
customers with some additional benefits than the regular customers. However, since none of the
stores are connected to each other, the membership of a customer in one store cannot be
recognized by another one. As a result, the customer is not able to gain membership benefits
from other stores although he is eligible for offers from the company itself. The new connected
server will allow each store to share information with others including approved membership
requests so that the customers are able to get premium benefits from all the stores.
However, the two main problems that have been selected to be addressed through the
proposed system in this particular project are developments of centralized server and the
common membership portal that will be accessed by all the branch stores of the company. This is
mainly because creation of the central database should be the top priority of the company to
maintain business continuity and the common membership portal will help the customers to
apply membership benefits in all the stores of the company. Furthermore, these two problems
can be addressed easily by one particular system and hence, they have been chosen for this
project.
3.0 Scope and System Requirements
The overall scope of the project involves development of information system that will be
able to address all the above mentioned problems. The scope statement includes the following:
Development of centralized server is within the scope of the project.
Development of the auto-classification system is within the scope of the project.
6REQUIREMENTS ANALYSIS AND MODELLING
Development of one common membership portal is within the scope of the
project.
Development of automated statistical data analysis system is within the scope of
the project.
For this particular project, only the development of centralized server and the
membership portal will be developed.
The system requirements for the central database system are as follows.
High end processor (at least Intel i3) for supporting the database operations
At least 2 GB RAM
A specific database system (preferably MySQL or others)
Database management tools for handling the data inside the database
Power back to prevent database crash during power cut
Software support for the member subscription portal
Anti-virus and firewalls for protecting the database from external attacks
4.0 User Stories and Acceptance Criteria
The interests of the stakeholders in the new system are shown in the following table.
Stakeholder Potential Interest
Company Owners Centralized Control of Business Operations
Financial Manager Payment Security and Assurance
Store Managers Inventory Search Made Easy
Customers Easy Shopping and Home Delivery in Online
Development of one common membership portal is within the scope of the
project.
Development of automated statistical data analysis system is within the scope of
the project.
For this particular project, only the development of centralized server and the
membership portal will be developed.
The system requirements for the central database system are as follows.
High end processor (at least Intel i3) for supporting the database operations
At least 2 GB RAM
A specific database system (preferably MySQL or others)
Database management tools for handling the data inside the database
Power back to prevent database crash during power cut
Software support for the member subscription portal
Anti-virus and firewalls for protecting the database from external attacks
4.0 User Stories and Acceptance Criteria
The interests of the stakeholders in the new system are shown in the following table.
Stakeholder Potential Interest
Company Owners Centralized Control of Business Operations
Financial Manager Payment Security and Assurance
Store Managers Inventory Search Made Easy
Customers Easy Shopping and Home Delivery in Online
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
7REQUIREMENTS ANALYSIS AND MODELLING
Shopping
Some identified users and their user stories are as follows.
Customers – The customers are the main users of the proposed system and with the
centralized server, they will be able to create their own profiles in the customer portal where they
can further get the option to shop online. Premium customers will also receive premium benefits
and offers.
Central Admin – The central admin will have more control over the business operations
in the five branches and will be able to monitor business operations as well.
The basic assumptions made during the preparation of the project plan are as follows.
It has been assumed that the centralized database will provide the administrators
to have more control over the business.
It has been assumed that business continuity will be maintained due to the
centralization of the server.
5.0 Recommendations
Based on the prepared project plan, the following recommendations can be suggested.
During centralization of the server, suitable security system should be applied in
order to protect the server data from external attacks.
Proper data encryption techniques should be used for transmission of business
data from the branch servers to the central server.
Shopping
Some identified users and their user stories are as follows.
Customers – The customers are the main users of the proposed system and with the
centralized server, they will be able to create their own profiles in the customer portal where they
can further get the option to shop online. Premium customers will also receive premium benefits
and offers.
Central Admin – The central admin will have more control over the business operations
in the five branches and will be able to monitor business operations as well.
The basic assumptions made during the preparation of the project plan are as follows.
It has been assumed that the centralized database will provide the administrators
to have more control over the business.
It has been assumed that business continuity will be maintained due to the
centralization of the server.
5.0 Recommendations
Based on the prepared project plan, the following recommendations can be suggested.
During centralization of the server, suitable security system should be applied in
order to protect the server data from external attacks.
Proper data encryption techniques should be used for transmission of business
data from the branch servers to the central server.
8REQUIREMENTS ANALYSIS AND MODELLING
6.0 Conclusion
In this report, a project plan has been forwarded for the development of information
system for Lilydale Movies. The two main issues that have been proposed to address in this
project include the development of common centralized server for the organization as well as the
common membership portal through which, the premium members will be able to gain premium
benefits in all the stores of the company. Based on the requirements and the scope of this project,
the overall project plan has been chalked and designed including technical specifications and
deliverables that need to be achieved in course of the project. In addition, a use case diagram has
been developed that has been used show the overall system layout that should be developed that
will help to solve the current identified problems at Lilydale Movies. For explaining the working
of the use case diagram, each of the systems has been further elaborated using intermediate use
case diagrams. In the overall system, these use cases will be used as the system blueprint and the
developments will be done accordingly. It has accordingly been assumed that the proposed
system will solve the problems that have been highlighted in the current system in Lilydale
Movies.
6.0 Conclusion
In this report, a project plan has been forwarded for the development of information
system for Lilydale Movies. The two main issues that have been proposed to address in this
project include the development of common centralized server for the organization as well as the
common membership portal through which, the premium members will be able to gain premium
benefits in all the stores of the company. Based on the requirements and the scope of this project,
the overall project plan has been chalked and designed including technical specifications and
deliverables that need to be achieved in course of the project. In addition, a use case diagram has
been developed that has been used show the overall system layout that should be developed that
will help to solve the current identified problems at Lilydale Movies. For explaining the working
of the use case diagram, each of the systems has been further elaborated using intermediate use
case diagrams. In the overall system, these use cases will be used as the system blueprint and the
developments will be done accordingly. It has accordingly been assumed that the proposed
system will solve the problems that have been highlighted in the current system in Lilydale
Movies.
9REQUIREMENTS ANALYSIS AND MODELLING
Task Part B
7.0 Use Case Diagram
The use case diagram for the overall system is as follows.
Figure 1: Use Case Diagram for the Proposed System
(Source: Created by Author)
Task Part B
7.0 Use Case Diagram
The use case diagram for the overall system is as follows.
Figure 1: Use Case Diagram for the Proposed System
(Source: Created by Author)
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
10REQUIREMENTS ANALYSIS AND MODELLING
8.0 Use Case Descriptions
The key functions are described as follows.
Name Customer Login
Description In order to do shopping from the company’s
website, the customer will need to enter the online
shopping portal
Actors Customers (Regular and Premium)
Organizational Benefits Secure E-Commerce
Assumptions The customers will be able to understand the use of
online portal without any difficulty
Triggers Login ID and Password
Pre-Conditions The customer has to enter the right login ID and
password
Post-Conditions When the correct id and password are entered, the
customer is redirected into the shopping portal
Name Central Database
Description The central database will be created to which all
the branches will be connected
Actors Central System Administrator
Organizational Benefits Business Continuity
Assumptions It has been assumed that the central database server
will enable the company to centralize all the
business operations and maintain business
8.0 Use Case Descriptions
The key functions are described as follows.
Name Customer Login
Description In order to do shopping from the company’s
website, the customer will need to enter the online
shopping portal
Actors Customers (Regular and Premium)
Organizational Benefits Secure E-Commerce
Assumptions The customers will be able to understand the use of
online portal without any difficulty
Triggers Login ID and Password
Pre-Conditions The customer has to enter the right login ID and
password
Post-Conditions When the correct id and password are entered, the
customer is redirected into the shopping portal
Name Central Database
Description The central database will be created to which all
the branches will be connected
Actors Central System Administrator
Organizational Benefits Business Continuity
Assumptions It has been assumed that the central database server
will enable the company to centralize all the
business operations and maintain business
11REQUIREMENTS ANALYSIS AND MODELLING
continuity for all the five branches
Triggers Business data entry
Pre-Conditions All relevant business data should be sent to the
central server
Post-Conditions The central server will store and manage all types
of business data
From the analysis of the key functions in the overall use case, three important
intermediate use cases are described as followed.
Customer Access to Online Portal – This use case is mainly centred around one actor i.e.
the customer. The premium customers who accept membership of the company will be allowed
to create own online portal in the company’s site with suitable username and password (Hammar
et al. 2015). Using these resources, the customers will be able to enter the online portal and view
premium products and offers provided by the company.
Admin Access to Online Portal – This is to enable the system admin of the company to
have access and control of the online portal. Furthermore, this access will allow them to maintain
the functions of the server and solve any customer queries, glitches and others accordingly.
Payment Gateway – This is another intermediate use case to which both the customer and
the system admin are connected. After completion of the sale request, an online receipt is
produced and sent to the customer (Enck et al. 2014). He will be able to use payment cards to
pay the sum mentioned in the receipt and then, the company will go ahead with the delivery of
the order.
continuity for all the five branches
Triggers Business data entry
Pre-Conditions All relevant business data should be sent to the
central server
Post-Conditions The central server will store and manage all types
of business data
From the analysis of the key functions in the overall use case, three important
intermediate use cases are described as followed.
Customer Access to Online Portal – This use case is mainly centred around one actor i.e.
the customer. The premium customers who accept membership of the company will be allowed
to create own online portal in the company’s site with suitable username and password (Hammar
et al. 2015). Using these resources, the customers will be able to enter the online portal and view
premium products and offers provided by the company.
Admin Access to Online Portal – This is to enable the system admin of the company to
have access and control of the online portal. Furthermore, this access will allow them to maintain
the functions of the server and solve any customer queries, glitches and others accordingly.
Payment Gateway – This is another intermediate use case to which both the customer and
the system admin are connected. After completion of the sale request, an online receipt is
produced and sent to the customer (Enck et al. 2014). He will be able to use payment cards to
pay the sum mentioned in the receipt and then, the company will go ahead with the delivery of
the order.
12REQUIREMENTS ANALYSIS AND MODELLING
The full use case description for one of the intermediate level use cases is as follows.
Name Payment Gateway
Description The payment gateway system will be created so
that the customer is able to pay for their purchased
movies online
Actors Customers, System Admin
Organizational Benefits Cashless Payments
Assumptions The gateway will be secure and easy to use
Triggers Online Receipt
Pre-Conditions The customer has to enter his payment card
information and verify the same using OTP
Post-Conditions The amount mentioned in the receipt will be
automatically deducted from the customer’s bank
account
9.0 Activity and Sequence Diagrams
For the activity and sequence diagrams, the use case chosen is the payment gateway. The
activity diagram for the proposed payment gateway system is as follows.
The full use case description for one of the intermediate level use cases is as follows.
Name Payment Gateway
Description The payment gateway system will be created so
that the customer is able to pay for their purchased
movies online
Actors Customers, System Admin
Organizational Benefits Cashless Payments
Assumptions The gateway will be secure and easy to use
Triggers Online Receipt
Pre-Conditions The customer has to enter his payment card
information and verify the same using OTP
Post-Conditions The amount mentioned in the receipt will be
automatically deducted from the customer’s bank
account
9.0 Activity and Sequence Diagrams
For the activity and sequence diagrams, the use case chosen is the payment gateway. The
activity diagram for the proposed payment gateway system is as follows.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
13REQUIREMENTS ANALYSIS AND MODELLING
Figure 2: Activity Diagram of the Payment Gateway
(Source: Created by Author)
Figure 2: Activity Diagram of the Payment Gateway
(Source: Created by Author)
14REQUIREMENTS ANALYSIS AND MODELLING
Figure 3: Sequence Diagram of the Payment Gateway
(Source: Created by Author)
Figure 3: Sequence Diagram of the Payment Gateway
(Source: Created by Author)
15REQUIREMENTS ANALYSIS AND MODELLING
References
Ahmadi, H., Rad, M.S., Nazari, M., Nilashi, M. & Ibrahim, O., 2014. Evaluating the factors
affecting the implementation of hospital information system (HIS) using AHP method. Life
Science Journal, 11(3), pp.202-207.
Arvidsson, V., Holmström, J. & Lyytinen, K., 2014. Information systems use as strategy
practice: A multi-dimensional view of strategic information system implementation and use. The
Journal of Strategic Information Systems, 23(1), pp.45-61.
Boud, D., Cohen, R. & Sampson, J. eds., 2014. Peer learning in higher education: Learning
from and with each other. Routledge.
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Coeurderoy, R., Guilmot, N. & Vas, A., 2014. Explaining factors affecting technological change
adoption: A survival analysis of an information system implementation. Management
Decision, 52(6), pp.1082-1100.
Dumais, S., Cutrell, E., Cadiz, J.J., Jancke, G., Sarin, R. & Robbins, D.C., 2016, January. Stuff
I've seen: a system for personal information retrieval and re-use. In ACM SIGIR Forum (Vol. 49,
No. 2, pp. 28-35). ACM.
Enck, W., Gilbert, P., Han, S., Tendulkar, V., Chun, B.G., Cox, L.P., Jung, J., McDaniel, P. &
Sheth, A.N., 2014. TaintDroid: an information-flow tracking system for realtime privacy
monitoring on smartphones. ACM Transactions on Computer Systems (TOCS), 32(2), p.5.
References
Ahmadi, H., Rad, M.S., Nazari, M., Nilashi, M. & Ibrahim, O., 2014. Evaluating the factors
affecting the implementation of hospital information system (HIS) using AHP method. Life
Science Journal, 11(3), pp.202-207.
Arvidsson, V., Holmström, J. & Lyytinen, K., 2014. Information systems use as strategy
practice: A multi-dimensional view of strategic information system implementation and use. The
Journal of Strategic Information Systems, 23(1), pp.45-61.
Boud, D., Cohen, R. & Sampson, J. eds., 2014. Peer learning in higher education: Learning
from and with each other. Routledge.
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Coeurderoy, R., Guilmot, N. & Vas, A., 2014. Explaining factors affecting technological change
adoption: A survival analysis of an information system implementation. Management
Decision, 52(6), pp.1082-1100.
Dumais, S., Cutrell, E., Cadiz, J.J., Jancke, G., Sarin, R. & Robbins, D.C., 2016, January. Stuff
I've seen: a system for personal information retrieval and re-use. In ACM SIGIR Forum (Vol. 49,
No. 2, pp. 28-35). ACM.
Enck, W., Gilbert, P., Han, S., Tendulkar, V., Chun, B.G., Cox, L.P., Jung, J., McDaniel, P. &
Sheth, A.N., 2014. TaintDroid: an information-flow tracking system for realtime privacy
monitoring on smartphones. ACM Transactions on Computer Systems (TOCS), 32(2), p.5.
1 out of 16
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.