|
|
| Line 1: |
Line 1: |
| | Zi5sGS <a href="http://hdhpmrnrkrqd.com/">hdhpmrnrkrqd</a>, [url=http://sklrqssdmote.com/]sklrqssdmote[/url], [link=http://fzwegricddwf.com/]fzwegricddwf[/link], http://uyedsqnmmwhl.com/ | | Zi5sGS <a href="http://hdhpmrnrkrqd.com/">hdhpmrnrkrqd</a>, [url=http://sklrqssdmote.com/]sklrqssdmote[/url], [link=http://fzwegricddwf.com/]fzwegricddwf[/link], http://uyedsqnmmwhl.com/ |
| | | | |
| − | ==Business Goals and Domain Assumptions==
| + | SZ8vEx <a href="http://idmoaseuwnnn.com/">idmoaseuwnnn</a>, [url=http://lesgjjimdhth.com/]lesgjjimdhth[/url], [link=http://iaunixbrmrwi.com/]iaunixbrmrwi[/link], http://wgxgrjappnwr.com/ |
| − | | |
| − | In the following sections will be reported the Business Goals and the Domain Assumptions for the current
| |
| − | case study.
| |
| − | | |
| − | === Business Goals ===
| |
| − | | |
| − | | |
| − | {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
| |
| − | |+ Table BG1. Business Goal TIS-BG-1
| |
| − | !Field !! Description
| |
| − | | |
| − | |- style="background:#f0f0f0; color:black"
| |
| − | ! UniqueID
| |
| − | ||TIS-BG-1
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Short Name
| |
| − | | Statewide provision of online services for citizens, companies, government agencies
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Type
| |
| − | | Business Goals.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Description
| |
| − | | The infrastructure must be able to make services of the public sector available to all the users, such as citizens, companies or government agencies. Each user can access, from somewhere, to the services providing login information; after the login the user can have the possibility to forward requests of some documents or require any service.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Rationale
| |
| − | | Essentially the rationale is the capability to make available the services offered by the public sector to citizens, companies and government agencies.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Involved Stakeholders
| |
| − | | Users and Public Body
| |
| − | | |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Priority of accomplishment
| |
| − | | Should have.
| |
| − | |}
| |
| − | | |
| − | | |
| − | {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
| |
| − | |+ Table BG2. Business Goal TIS-BG-2
| |
| − | !Field !! Description
| |
| − | | |
| − | |- style="background:#f0f0f0; color:black"
| |
| − | ! UniqueID
| |
| − | ||TIS-BG-2
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Short Name
| |
| − | | Improve speed and efficacy of processes
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Type
| |
| − | | Business Goals.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Description
| |
| − | | The infrastructure must be able to serve quickly the user requests. When a citizen requires a service, replies are received online. Moreover if a fee must be paid, user could access, easily, the e-payment service. At the end of the process, the requested item (authenticated if required) , is available. The online interactions make the process very fast, improving the perceived quality and user satisfaction.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Rationale
| |
| − | | The application of information technologies to the government process reduces the time to perform the task improving the efficiency.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Involved Stakeholders
| |
| − | | User, Public Boby, Certifier service, E-payment service
| |
| − | | |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Priority of accomplishment
| |
| − | | Should have.
| |
| − | |}
| |
| − | | |
| − | | |
| − | | |
| − | {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
| |
| − | |+ Table BG3. Business Goal TIS-BG-3
| |
| − | !Field !! Description
| |
| − | | |
| − | |- style="background:#f0f0f0; color:black"
| |
| − | ! UniqueID
| |
| − | ||TIS-BG-3
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Short Name
| |
| − | | Provide a 24h per day availability of the services
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Type
| |
| − | | Business Goals.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Description
| |
| − | | User may submit a request at any time and from anywhere, so service availability must be always guaranteed. User can access from anywhere in the world and can have a different time zone.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Rationale
| |
| − | | The infrastructure must guarantee a 24x7 availability of the services.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Involved Stakeholders
| |
| − | | User and Public Body
| |
| − | | |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Priority of accomplishment
| |
| − | | Should have.
| |
| − | |}
| |
| − | | |
| − | | |
| − | {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
| |
| − | |+ Table BG1. Business Goal TIS-BG-4
| |
| − | !Field !! Description
| |
| − | | |
| − | |- style="background:#f0f0f0; color:black"
| |
| − | ! UniqueID
| |
| − | ||TIS-BG-4
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Short Name
| |
| − | | Offer a good user experience and provide continuous feedbacks to users
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Type
| |
| − | | Business Goals.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Description
| |
| − | | The application must be easy to use, and of quick understanding guaranteeing usability and accessibility. The usability of an application is relatedto the interface, the navigability, the positioning of text and objects. The application should offer an interface highly intuitive; information should be displayed in a directly usable format. The users of the application can have different expertise: some user could be less able than others to interact with the application; moreover disabled users could access the application. Moreover the sequence of the task should be linear, the terminology understandable, time to load pages should not be long and users should be able to easily print their information. E-government application must provide continuous feedback to guide the user during the operations.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Rationale
| |
| − | | The e-government application must be easy to use and guide users during his operations.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Involved Stakeholders
| |
| − | | User, Public Body
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Priority of accomplishment
| |
| − | | Should have.
| |
| − | |}
| |
| − | | |
| − | {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
| |
| − | |+ Table BG1. Business Goal TIS-BG-5
| |
| − | !Field !! Description
| |
| − | | |
| − | |- style="background:#f0f0f0; color:black"
| |
| − | ! UniqueID
| |
| − | ||TIS-BG-5
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Short Name
| |
| − | | Guarantee confidentiality, integrity, authenticity, non-repudiation
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Type
| |
| − | | Business Goals.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Description
| |
| − | | E-government application must guarantee the confidentiality of the information the user provided when a service is requested. Such applications act as an interface for data that is kept in a distributed way. This can occur because of legal restrictions that aim to ensure data privacy. If data is changed, distributed transaction support is needed. Data encryption must be guaranteed for data transfers from the citizen to the public administration, among administrative offices and from a public administration to the citizen. The transfer of this data has to be encrypted to prevent the access of unauthorized persons. Messages can be signed to certify the sender of the message. A citizen can prove that he or she has sent a message through the digital signature. It is possible to prove that the recipient really received the message and that the sender really sent the message. The transmission of a document is logged in a way that it proves that the sender submitted the message and that the receiver received it. Both parties get a confirmation of this.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Rationale
| |
| − | | E-government applications frequently have to access, receive, or store data that contains personally identifiable information such as healthcare records, criminal justice investigations and proceedings, residence and geographic records, ethnicity, and so on. The originators of messages from citizens to public offices have to be guaranteed.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Involved Stakeholders
| |
| − | | User, Public Body, Certifier service
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Priority of accomplishment
| |
| − | | Should have.
| |
| − | |}
| |
| − | | |
| − | {| style="background:#cccc99;color:black;width:80%;" border="1" cellpadding="5" cellspacing="0" align="center"
| |
| − | |+ Table BG1. Business Goal TIS-BG-6
| |
| − | !Field !! Description
| |
| − | | |
| − | |- style="background:#f0f0f0; color:black"
| |
| − | ! UniqueID
| |
| − | ||TIS-BG-6
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Short Name
| |
| − | | Guarantee that provided information is not used for a scope different than the one required by the user
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Type
| |
| − | | Business Goals.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Description
| |
| − | | E-government application must guarantee the confidentiality of the information user provided when he requested a document. When a user requires a document, all his relevant personal information is needed, moreover if he have to pay a fee due to his request, he have to transmit information such as credit card number . It ’s important to guarantee that transmitted data are not used for different scope than the one required by the user.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Rationale
| |
| − | | When user perform a request of a document or a service, confidential data are transmitted; user must be guaranteed that data he communicated in the requests are not used for different scope.
| |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Involved Stakeholders
| |
| − | | User, Public Body and e-payment service
| |
| − | | |
| − | | |
| − | |- style="background:white; color:black"
| |
| − | ! Priority of accomplishment
| |
| − | | Should have.
| |
| − | |}
| |
| − | | |
| − | === Domain Assumptions ===
| |
| | | | |
| | == Domain Analysis == | | == Domain Analysis == |
In the following figure the strategic dependency diagram for the e-Government case study
is reported. The diagram reports the dependency between User (a Citizen, a Government Agency or a
Company) and Public Body to the satisfaction of the goal Require service; moreover User depends on
the Certifier service to gain trust on the obtained output, while the Certifier service is needed by the
Public Body to authenticate the service output. Moreover User needs the E-payment service to satisfy
the softgoal Charge Fee.
The following figure represent the context diagram of the e-government case study.
In the following figure the general use case diagram for the e-Government case study is reported.
