Build a Website

Web page software development HTML5 Use Cases Original An individual customer wishes to keep financial and legal information in a place known to their next of kin, legal executors, other relevant persons, so that it is readily available after death. Including (for example) banking details, wills, insurance, etc. Such an individual purchases a LifeBank, enters important information e.g. by scanning documents and informs next of kin, solicitors and executors where the LifeBank is kept and relevant access passwords. On death the relevant persons recover the LifeBank and access the necessary information for probate, tax and other necessary steps to be completed with as little delay and expense as possible. MOD An employee of the MOD deployed on a ship (beyond convenient communication) is injured. His health information is contained on a LifeBank. The medic obtains his LifeBank and accesses the data with a tablet computer. Having checked the employee is not allergic to a certain medication the medic administers the medication and updates the notes on the LifeBank to include the latest treatment. The LifeBank is then returned to the employee and goes with him on evacuation making the new data available to the next carer if necessary. Development Phases Development will start with a two phase plan, further enhancement and an organised development cycle are beyond the scope of this document. The first phase will be a simple transfer of the existing functionality of LifeBank to a new platform this can then be followed by a second phase introducing the new functionality requested. By starting with the simpler task of merely transferring to a new platform, the risks of unexpected difficulties can be minimised since the structure is already well understood and known to work. If done carefully and keeping in mind the future development required, all (or nearly all) the code should be re-useable in Phase 2. The two phase approach will produce a quick win – with the phase one version available and working on Windows 10 before the harder task of introducing new functionality is started. Phase 1 A new development environment will be chosen in consultation with the developer. Req No Requirement Priority 1.1 The new environment will use HTML5 for web pages. Must have 1.2 The new environment will not use a proprietary language, extensions or modules. Should have 1.3 The new environment (if proprietary) will be from a well established supplier. Should have 1.4 The new environment should be replaceable by a competing environment with minimum rewriting of code. Should have 1.5 The new environment will be capable of producing code compatible with Windows 10, iOS 9.2 and Android 6.0. Must have 1.6 No new functionality will be introduced in Phase 1, but the transfer will be made in such a way as to simplify Phase 2 as much as possible. Must have 1.7 To the maximum extent possible the structure of data will not be hard coded into the application, instead field names and data definitions will be read from the database. Should have 1.8 Layout of fields, labels, etc will be automated as much as possible using CSS. Could have Phase 1 System Diagram Phase 2 Phase 2 will introduce new functionality and remote accessibility via the internet. Req No Requirement Priority 2.1 The LifeBank USB memory stick will have an encrypted partition on which the database and documents will be stored. Should have 2.2 The encrypted partition will use an established standard ( such as the American, Advanced Encryption Standard). Should have 2.3 The LifeBank USB memory stick will have an un-encrypted partition containing only the Application Installers for supported operating systems. Could have 2.4 The Application will offer as a data source, a choice of the databases currently connected with the LifeBank server. Must have 2.5 On opening, the Application the user will be asked for access credentials. Must have 2.6 Any instance of the Application will only allow access when correct access credentials are supplied Must have 2.7 Added documents and images will be stored in a dedicated directory on the encrypted partition with a record in the database including a link field to that document. Must have 2.8 The LifeBank server will be able to pass basic penetration testing Must have 2.9 The Application will allow the user to add fields to the database tables Should have 2.10 The Application will allow an administrator to delete fields from non-administrative database tables Should have Phase 2 System Diagram