Download System Design Specification - Project Management

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Database wikipedia , lookup

Relational model wikipedia , lookup

SQL wikipedia , lookup

Team Foundation Server wikipedia , lookup

Database model wikipedia , lookup

Microsoft Access wikipedia , lookup

Clusterpoint wikipedia , lookup

PL/SQL wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Transcript
University of Edinburgh
_______________________________________________________________________________________________________
Stage: Systems Analysis and Design
System Design Specification
Election Count System Upgrade
Communication, Media and Web (CMW)
CMW012
[ANNUAL PLAN NUMBER]
Document Version: 0.2
Date: 17/07/14
___________________________________________________________________________________
Information Services - Template Revised March 2011
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
Contents
1
1.1
1.2
2
DOCUMENT MANAGEMENT .................................................................. 4
Contributors ..................................................................................................... 4
Version Control ................................................................................................ 4
OVERVIEW .............................................................................................. 5
2.1
2.2
Scope.................................................................................................................. 5
Objectives.......................................................................................................... 5
2.3
2.4
Deliverables ...................................................................................................... 5
Current system ................................................................................................. 5
3
3.1
3.2
4
DEVELOPMENT TOOLS AND STANDARDS ......................................... 6
Development Tools ........................................................................................... 6
Development Standards................................................................................... 6
SYSTEM PROCESSES ............................................................................ 7
4.1
Objectives.......................................................................................................... 7
4.1.1 Objective 1 ..................................................................................................... 7
4.1.2 Objective 2 ..................................................................................................... 7
4.1.3 Objective 3 ..................................................................................................... 7
4.2
Deliverables ...................................................................................................... 8
4.2.1 Convert the applications to a newer supported MS environment .................. 8
5
USER INTERFACE ................................................................................ 10
5.1
Transactional Interface ................................................................................. 10
5.1.1 MyEd Interface ............................................................................................ 10
5.2
6
Reporting Interface ........................................................................................ 10
APPLICATION SECURITY .................................................................... 10
6.1
Authentication ................................................................................................ 10
6.2
6.3
Authorisation .................................................................................................. 10
Business Objects ............................................................................................. 10
7
DATABASE DESIGN ............................................................................. 10
8
APPLICATION INTERFACES................................................................ 10
9
DATA ...................................................................................................... 10
___________________________________________________________________________________
Page 2 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
9.1
Data Migration ............................................................................................... 10
9.2
Archiving Policy ............................................................................................. 10
10
IMPLEMENTATION ............................................................................ 10
___________________________________________________________________________________
Page 3 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
1 Document Management
1.1 Contributors
Please provide details of all contributors to this document.
Role
Systems Analyst
Designer
(Owner)
Business
Analyst
Project Manager
Project Sponsor
Business Area
Manager
Other document
contributors
Unit
ISG
Name
Geir Granum
Sue Woodger
Stuart McFarlane
1.2 Version Control
Please document all changes made to this document since initial distribution.
Date
08/07/14
17/07/14
Version
0.1
0.2
Author
GG
GG
Section
All
2,4
Amendment
Initial version
Document ODBC Direct replacement
___________________________________________________________________________________
Page 4 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
2 OVERVIEW
Please provide a general overview of the system design so that anyone reading this
section is able to gain an understanding of what functionality is provided and how
this functionality will be technically implemented.
2.1 Scope

To convert the applications to a newer supported MS environment (MS
Access, VB, SQL Database)
2.2 Objectives


Make the current count system compliant and supported i.e. convert the
current version to a newer, supported Microsoft platform
Add the system to a location which can be accessed by managed desktops on
the University network, ensuring remote access to the application.
2.3 Deliverables


Update the count system to a newer, supported Microsoft platform (Windows,
Access, VB and SQL database).
Move the count application to a location on the network so that it can be
accessed remotely from a University managed desktop
2.4 Current system
The current system is referencing 2 external libraries not available in current
Microsoft products:
1. Microsoft DTSPackage Object Library (dtspkg.dll) (part of SQL server pre
2008) Used by ATV count and STV count). This appears to be used for
reading text-files from disk into SQL server tables.
The replacement for this functionality in current versions of SQL server
appears to be ‘Microsoft.SqlServer.ManagedDTS.DLL’ part of the SQL server
Integration Services SDK
2. Microsoft Office Frontpage design-time controls (fpdtc.dll) which in
Frontpage is used to add ActiveX or Java applets to a web page. Possibly used
for ListView and other objects in Access forms.
The current system is using ODBC Direct (DAO)
http://en.wikipedia.org/wiki/Jet_Data_Access_Objects objects to programmatically
query the SQL server database from VBA. This is deprecated functionality in current
versions of Access. The recommendation is to use ADO objects
http://en.wikipedia.org/wiki/ActiveX_Data_Objects instead.
___________________________________________________________________________________
Page 5 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
3
DEVELOPMENT TOOLS AND STANDARDS
3.1 Development Tools


MS Access
VBA.
3.2 Development Standards
Tick the appropriate box to indicate the standards being followed for this application:
√ indicates compliance
Standard
Database Design
Cold Fusion
Java
Uportal Development
Accessibility
Web Style Standards
Supported Web Browsers
___________________________________________________________________________________
Page 6 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
4 SYSTEM PROCESSES
Take each process specified in the Business Requirements Document (BRD) and state how it will be
implemented technically (please make reference to the corresponding paragraph number in the BRD).
Where applicable, a specification of each screen which makes up a process should be provided (ie a
screenshot and descriptions of every data item displayed).
A resource estimate should be provided for each process.
All paragraphs should be numbered to assist cross referencing in testing stages.
4.1 Objectives
4.1.1 Objective 1
Make the current count system compliant and supported i.e. convert the current
version to a newer, supported Microsoft platform
The current system is dependent on 2 external libraries that are part of deprecated
Microsoft applications and are not part of a standard desktop install.
‘Microsoft DTSPackage Object Library’. This library was part of the SDK for earlier
versions of SQL server. In newer versions of SQL server this functionality appears the
have been included in SQL Server Integration Services (SSIS). Access to this
functionality requires that the necessary libraries are installed on the computer that
Access is running on. It is possible that this is not a ‘drop-in’ replacement and that VB
code in Access will have to be changed.
‘Microsoft Office Frontpage design-time controls’. This library was part of Microsoft
Office Frontpage, a discontinued HTML editor from Microsoft. It is unclear what
functionality from this library is used by the voting system. Typically the library
provides controls such as scrollable lists and tick boxes via ActiveX. HTML editing is
now part of the Visual Studio suite from Microsoft. However I have been unable to
find any documentation of a library that provides ‘design-time controls’. The
currently used DLL file (fpdtc.dll) appears to be stand-alone and if it is can be
continued to be used to provide this functionality.
ODBCdirect DAO code in VBA ClsSequel class modules will have to be replaced
with equivalent ADO code
4.1.2 Objective 2
Add the system to a location which can be accessed by managed desktops on the
University network, ensuring remote access to the application
Considering that the system is dependent on functionality in libraries that are not part
of managed desktop, this objective will be difficult to achieve.
4.1.3 Objective 3
Deliver the same functionality as the current Election Count system in a more
compliant form and simplify the code into a single code base
This may be difficult within the time frame.
___________________________________________________________________________________
Page 7 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
4.2 Deliverables
Project
Brief
section
4.1
To convert the applications to a newer
supported MS environment (MS Access, VB,
SQL Database)
4.2
Move the count application to a location on
the network so that it can be accessed
remotely from a University managed desktop
4.3
Deliver the count system functionality in a
single code base
4.4
4.5
4.6
Retain separation of the count system from
the EVES voting application
Can run system of multiple machines
Web front end
Category
M
M(may not be possible due
to dependencies)
M(may not be possible
within the time frame for
this project)
D
HD
D
4.2.1 Convert the applications to a newer supported MS
environment



HIGHLY RECOMMENDED: Move the SQL server databases: RECE and
STVCount from kennedy.mis.ed.ac.uk to supported infrastructure such as UCSSEQUEL (This may need Dev. Tech. resource. Full DEV/TEST/LIVE
environments may not be needed)
Change the ‘STV-count’ and ‘ATV-count’ Access databases to use the SSIS
package provided in current versions of SQL server instead of the DTS package it
is currently using. Configure it to use the SQL server database set up in the first
step.
Rewrite the ClsSequel class modules in both ‘STV-count’ and ‘ATV-count’ so
that they use DAO syntax instead of the currently used ODBCDirect, which is
deprecated. Changes may also have to be done in other modules using the
functionality of ClSequel to run SQL queries on the database.
4.2.1.1 STV count
The DTS package is used in the modules: dtsAuditUpload and dtsRankUpload. If the
SSIS package cannot be used as a replacement then the functionality in these modules
will have to be re-implemented using other technology using the following process
flows.
Process flow of dtsAuditUpload:
1: Connect to the catalog ‘STV count’ as the user ‘stvcnt’ to the database server
2: Clear the table: [ElectionCount].[dbo].[Download_audit]
3: Load the contents of the local file audit.txt into the table:
[ElectionCount].[dbo].[Download_audit]
Process flow of dtsRankUpload :
___________________________________________________________________________________
Page 8 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
1: Connect to the catalog ‘STV count’ as the user ‘stvcnt’ to the database server
2: Clear the table: [ElectionCount].[dbo]. [Download_rank]
3: Load the contents of the local file ranks.txt into the table: [ElectionCount].[dbo].[
Download_rank]
4.2.1.2 ATV count
The DTS package is used in the modules: dtsAuditUpload and dtsRankUpload. If the
SSIS package cannot be used as a replacement then the functionality in these modules
will have to be re-implemented using other technology using the following process
flows.
Process flow of dtsAuditUpload:
1: Connect to the catalog ‘rece’ as the user ‘recelect’ to the database server
2: Clear the table: [ElectionCount].[dbo].[Download_audit]
3: Load the contents of the local file audit.txt into the table:
[ElectionCount].[dbo].[Download_audit]
Process flow of dtsRankUpload :
1: Connect to the catalog ‘rece’ as the user ‘recelect’ to the database server
2: Clear the table: [ElectionCount].[dbo]. [Download_rank]
3: Load the contents of the local file ranks.txt into the table: [ElectionCount].[dbo].[
Download_rank]
___________________________________________________________________________________
Page 9 of 10
Systems Analysis & Design: System Design Specification
Version: 0.2
Election Count System Upgrade
_______________________________________________________________________________________________________
5
USER INTERFACE
5.1 Transactional Interface
N/A no new user interfaces part of the design
5.1.1 MyEd Interface
N/A
5.2 Reporting Interface
N/A
6
APPLICATION SECURITY
This section relates to application rather than physical security which is covered in the Technical
Architecture Document (TAD).
6.1 Authentication
6.2 Authorisation
Include application, menu and page authorisation and any application roles.
6.3 Business Objects
Include any specific object/row authorisation.
7 DATABASE DESIGN
N/A
No new database design
8 APPLICATION INTERFACES
N/A unchanged
9 DATA
9.1 Data Migration
Include any mappings between existing systems and the new system
9.2 Archiving Policy
10 IMPLEMENTATION
Specify any implementation issues that should be considered when creating an implementation plan at
the Build stage.
___________________________________________________________________________________
Page 10 of 10