MAJOR PROJECT

KENO LEESTUDENT ID: 11071018BSC BUSINESS COMPUTING 2012MAJOR PROJECTSales Database Management System for High Definition DVD Club

Table of ContentsCHAPTER 1 - INTRODUCTION81.1 Background of Organization under consideration81.2 Current Situation Overview 91.3 Problem Definition91.4 Aims/Objectives111.5 Objectives of Project111.6 Milestones131.7 Work Breakdown Structure Table131.8 Work Breakdown Structure 141.9 Dependency Table131.10 Activity Network Diagram 141.11 Gantt Chart131.12 Project Management Aspects 14 1.12.1 Progress Monitoring13 1.12.2 Risk Management (Risk Estimation Matrix)13 1.12.3 (A) Risk Plan13 1.12.3 (B) Risk Estimation Key13 1.12.3 (C) Risk Ratings131.13 Quality Management 14 1.13.1 Product Attributes13 1.13.2 Method For Quality Control13 1.13.3 Tools For Assurance131.14 Implementation Plan13 1.14.1 Deployment Strategies13 1.14.2 Justification of Deployment Strategy chosen13 1.14.3 Data Migration13 1.14.4 Training13

CHAPTER 2 LITERATURE REVIEW82.1 Theoretical Study 14 2.1.1 Web Hosting13 2.1.2 Web Hosting Companies in Trinidad132.2 Case Study13 2.2.1 Amazon.com13 2.2.2 Ebay.com13 2.2.3 Stubhub.com13 CHAPTER 3 - RESEARCH OR INVESTIGATIVE METHODS143.1 Deductive/Inductive13 3.1.1 Deductive Research Approach13 3.1.2 Inductive Research Approach13 3.1.3 Stubhub.com133.2 Survey/Case Study/Action Research 14 3.2.1 Survey Research13 3.2.2 Case Study13 3.2.3 Action Research133.3 One/Mixed/Multi13 3.3.1 One Method Research13 3.3.2 Mixed Method Research13 3.3.3 Multi Method Research133.4 Data Collection Methods and Analysis13 3.4.1 Interviews13 3.4.2 Questionaires13 3.4.3 Observations133.5 Methodology 14 3.5.1 Methodology13 3.5.2 Object Oriented Methodology133.6 Justification of choice13

CHAPTER 4 FEASIBILITY STUDY144.1 Business Case 14 4.1.1 Economic Analysis13 4.1.2 Social Analysis13 4.1.3 Technical Analysis13 4.1.4 Go/No Go Decision13

CHAPTER 5 SYSTEM ANALYSIS145.1 Problem Specification of current system 145.2 Fact Finding 145.3 Analysis of data collected14 5.3.1 Questionaire Analysis13 5.3.2 Interview Analysis13 5.3.3 Observation Analysis135.4 Object Oriented Analysis and Design Diagrams (Current System)14 5.4.1 Use Case Diagram (Current System)13 5.4.2 Class Diagram (Current System)13 5.4.3 Sequence Diagram for Sales Process (Current System)13 5.4.4 Sequence Diagram for Purchase Process (Current System)13 5.4.5 Sequence Diagram for Customer Membership Process (Current System)135.5 Object Oriented Analysis and Design Diagrams (Proposed System)14 5.5.1 Use Case Diagram (Proposed System)13 5.5.2 Class Diagram (Proposed System)13 5.5.3 Sequence Diagram for Sales Process (Proposed System)13 5.5.4 Sequence Diagram for Purchase Process (Proposed System)13 5.5.5 Sequence Diagram for Customer Membership Process (Proposed System)13 5.5.6 State Transition Diagram for Conducting a Sales (Proposed System)13 5.5.7 State Transition Diagram for Purchasing Stock (Proposed System)13 5.5.8 Sequence Diagram for Customer Purchase (Proposed System)13

CHAPTER 6 REQUIREMENT SPECIFICATION146.1 Summary of proposed system 146.2 Functional Requirements 14 6.2.1 Sales Modules13 6.2.2 Stock Module13 6.2.3 Supply Module13 6.2.4 Customer Membership Module136.3 Non-Functional Requirements 14 6.3.1 Security13 6.3.2 Usability13 6.3.3 Reliability13 6.3.4 Maintainability136.4 Business Requirements 14

CHAPTER 7 SYSTEM DESIGN147.1 Logical System Specification147.2 Data Design 147.2.1 Normalization13 7.2.2 ERD of proposed system137.3 Architectural Design 147.3.1 Program Structure Chart137.3.2 Pseudocode137.4 Procedural Design 147.4.1 Pseudocode137.4.2 Flowchart (Sales Module)137.5 Interface Design 147.5.1 Table showing Visio Design View/When saved as JPEG137.6 Test Plan 147.6.1 Blackbox Testing137.6.2 Whitebox Testing13

CHAPTER 8 DEVELOPMENT148.1 Screenshot of Developed System148.2 SQLPlus Coding 148.3 Oracle PL/SQL Coding148.4 Justification of development using Oracle (PL/SQL) 14

CHAPTER 9 TESTING149.1 Unit Test149.2 Module Test 149.3 Integration Test149.4 System Test 149.5 Acceptance Test 14

CHAPTER 10 IMPLEMENTATION1410.1 Implementation Plan1410.1.1 Deployment1310.1.2 Data Migration1310.2 Training Plan1410.3 User Guide1410.4 Backup Plan14

CHAPTER 11 INTERPRETATION OF RESULTS1411.1 Checklist of Requirements1411.2 Comparison of Results to Cases in Literature Review 1411.3 Summary of Client Appraisal/Acceptance/Feedback1411.4 Evaluation of CASE Tools used14

CHAPTER 12 EVALUATION1412.1 Critical Appraisal of all project stages1412.2 Conclusion 1412.3 Actual Gantt Chart vs Original Plan14

APPENDICES14Appendix A 14Appendix B14Appendix C 14Appendix D 14Appendix E 14Appendix F 14Appendix G 14Appendix H 14Appendix I 14Appendix J 14

MAJOR PROJECTBSC BUSINESS COMPUTING

1. INTRODUCTION

1.1 Background of organization under consideration

High Definition DVD Club is a well established and recognised DVD club in the Valencia community. It was formerly a DVD stall that operated on the road side. This DVD clubs initial road side vending venture was established in the year 2008 and transitioned into High Definition DVD Video Club in November of 2009. A growing population lead to increased qualitative and quantitative demands for the businesss products and services. This emphasized the need for an improved quality service and a greater range of the business products. High Definition DVD Club achieved financial stability during their road side venture. Today the business gives back to the community by sponsoring community type activities and events.

High Definition DVD Club provides a wide range of DVD movies. The owner is a very customer oriented individual who seeks to accommodate the entire community needs, by keeping records of customers buying trends. The owner at High Definition DVD Club has clearly stated her intention to consistently and continuously meet the growth in demand and services at her business place. She boasts that her prices are the best and that her product range and service quality can only improve. The business future goal is to improve the customers experience at the DVD club, by obtaining their input in the way forward. The owner also intends to open branches at other locations within the next five years to gain a customer base not only in Valencia, but in other parts of the country.

1.2 Current Situation OverviewHigh Definition DVD Club runs a self-serve sales system, whereby customers have the leisure of browsing displays for desired movies. Movies are strategically and conveniently displayed on the walls within the establishment, with six televisions each connected to a DVD player placed at different points of the business for sample viewing. Price posters and specials on DVDs are placed both on the establishments interior and exterior walls for advertisement as well as for convenient customer viewing.

The DVD club does not have a computer based system in which to keep records of DVD sales and stock, hence DVD sales conducted are recorded in a notebook. A notebook is also used to keep records of DVD in stock as well as information on membership of customers. Information on the DVD sold, its price and genre are kept in the DVD sales book. Currently there is also a dedicated notebook for the keeping of records as it pertains to DVDs in stock. Information recorded and stored in this book includes the DVD name, genre, quantity in stock and its price. Information recorded on a daily basis is meaningfully categorized then sales are calculated at the end of each day. This is to provide an idea of the days sales and profits or losses. These record books as well as other pertinent information are stored in a draw at the establishment.

The owner of High Definition DVD club currently conducts day to day sales at her business place with the aid of a customer service representative who provides assistance to customers who may need advice on DVD movies or technical assistance when viewing DVDs. She however is responsible for facilitating the DVD sales and the recording and storing of the necessary sale information.

1.3 Problem Definition High Definition Video Club is in high demand within the community, however it faced several challenges. Some of the problems faced by the business are as follows:

Keeping meaningful and concise data as it relates to DVD sales transactions. Data being recorded is often abbreviated and contains errors.

Inefficient documenting of customer membership information as well as the un-customer friendly process by which information is gathered.

Tedious and time consuming method of recording sales transactions when multiple customers are purchasing several movies.

Unavailability of readily available records of sales transactions as well as customer information.

Updating DVD movies in stock relevant to its quantity when there is a sale or purchase. Records kept of DVDs in stock tend to be inconsistent and incorrect.

1.4 Aims/ObjectivesIt is important that the Sales Database Management System to be implemented at High Definition DVD Club provide users with the following top-level functions:

To create, read, update and delete records as associated with the acronym CRUD.

To store records of DVD Sales Transactions, DVD In Stock, Supplies Purchased and Customer Membership Information.

To produce reports on DVD Sales, DVDs In stock, Supplies Purchased and Customer Membership Information.

To trigger an alert when the stock reaches a predefined minimum level.

1.5 Objectives of the project

Having carried out the necessary investigative work on High Definition DVD Club, the Waterfall Lifecycle Model alongside the Object Oriented Methodology will be used throughout the development of the project. The Waterfall Model will provide the initial framework from which object oriented designs can be drawn. This will ensure a simple, well-structured flow of events, continuous documentation as well as the drawing of design diagrams. The overall aim of this project is to produce a Sales Database Management System that would alleviate the problems faced by the DVD club thereby providing an easier, more efficient process of recording DVD sales, DVD in stock and customer membership information. The following are the objectives of this project. They are:

To develop a Sales Database Management System that would allow for the creation, reading, updating and deleting of records.

To produce the feasibility of developing a Sales Database Management System for the DVD club.

To conduct analysis relevant to the requirements of the project, from which a requirements analysis report will be produced. This analysis report would include fact finding and UML diagrams describing both the operations of the current and proposed system.

To design and code the Sales Database Management System for High Definition DVD Club.

To test and document the testing stage of the Sales Database Management System. Testing would include, white box, black box and regression.

To implement and evaluate the database management system. Implementation would include a conversion strategy, data migration, training, user manuals and a backup and recovery plan. The evaluation done should also include an evaluation of the entire project.

1.6 Milestones

STAGEDELIVERABLESESTIMATED DELIVERY DATE

INTRODUCTION

Background To The Project , Problem Definition, Top-Level Functional Requirements, Objectives To The Project, Milestone Plan, Work Breakdown Structure, Activity Network Diagram, Gantt Chart, Project Management Aspects25th March, 2012

LITERATURE REVIEWTheoretical Study, Hardware and Software Technology, Case Studies 3rd April, 2012

RESEARCH METHODResearch or Investigative Method, Justification of Choice, Methodology11th April, 2012

FEASIBILITY STUDY

Cost Benefits Analysis, Business and Technical System Options, User Requirements, Go or No Go Decision28th April, 2012

SYSTEMS ANALYSISFacts Finding, Current System Description , Proposed System Description22nd May, 2012

REQUIREMNT SPECIFICATION

Functional and Non-Functional Requirements, Business Requirements7th June, 2012

DESIGNLogical Design, Physical Design, Technical System Options, Business System Options3rd July, 2012

INTERIM REPORTAims and Objectives of the Project, Key Issues and Research Undertaken, Current Status of the Project7th July, 2012

DEVELOPMENT

System Coding8th August, 2012

TESTINGWhite Box Testing, Black Box Testing, Regression Testing, Test Report23rd August, 2012

IMPLEMENTATIONConversion Strategy, Data Migration Plan, User Manual, Training, Back and Recovery Plan26th September, 2012

INTERPRETATION OF RESULTSRequirements Checklist, Comparison of Results to Case Study, Client Appraisal Summary, Evaluation of CASE Tools3rd October, 2012

EVALUATIONProduct Evaluation , Project Evaluation

11th October, 2012

Table 1.6

1.7 Work Breakdown Structure Table

Activities

Number of DaysPercentage

Introduction

12 Days/171 Days7.0%

Literature Review

8 Days/171 Days4.7%

Research or Investigative Method

7 Days/171 Days4.1%

Feasibility Study

18 Days/171 Days10.5%

Requirements Analysis

22 Days/171 Days12.9%

Requirements Specification

8 Days/171 Days4.7%

Design

21 Days/171 Days12.3%

Interim Report

3 Days/171 Days1.8%

Coding

25 Days/171 Days14.6%

Testing

12 Days/171 Days7%

Implementation

21 Days/171 Days12.3%

Interpretation of Results

7 Days/171 Days4.1%

Evaluation

7 Days/171 Days4.1%

Total

171 Days/171 Days100%

Table 1.7

KENO LEEPage 1

KENO LEEPage 2

1.8 Work Breakdown Structure

Figure 1.8

MAJOR PROJECTBSC BUSINESS COMPUTING

KENO LEE Page 7

1.9 Dependency Table

IDTASK NAMEDURATIONPREDECESSOR

1Introduction12 Days----------

2Literature Review 8 Days1

3Research or Investigative Method 7 Days1,2

4Feasibility Study18 Days1

5Requirements Analysis22 Days4

6Requirements Specification8 Days5

7Design21 Days4,5

8Interim Report 3 Days1,2,3,4,5,5,7

9Coding25 Days7

10Testing12 Days6,7,9

11Implementation21 Days10

12Interpretation of Results 7 Days11

13Evaluation 7 Days12

MAJOR PROJECTBSC BUSINESS COMPUTINGTable 1.9KENO LEEPage 8

1.10 Activity Network Diagram

Diagram Key:

MAJOR PROJECTBSC BUSINESS COMPUTINGFigure 1.10KENO LEE Page 9

1.11 Gantt Chart

Figure 1.111.12 Project Management Aspects

Project management is a methodical approach to planning and guiding project processes from start to finish. Project management is relevant to most types of projects and is very useful to ensuring the control of complex processes that software development projects entails. The systems development lifecycle is one such methodology utilized for guiding a projects management process from the initiating feasibility study straight through to maintenance of the developed system (TechTarget, 2008). In this project three project management aspects are looked at, they are:

1.12.1 Progress Monitoring This can be described as the regular observation and recording of activities relevant to the progress of a project. Progress monitoring involves the routine gathering of information on different aspects of the project. Observation is done in a systematic and purposeful way and may involve giving feedback on the projects progress. Feedback reported is often utilized for making decisions relative to the improvement of a projects performance. Progress monitoring provides information that is useful for, analysing the business situation and its project, determining whether inputs in the project are well utilized, identifying problems the project faces and providing solutions, ensuring that activities are performed by the right persons and on time, using the lessons from one project experience on another and determining whether project planning was done in the most appropriate way to solve the problem at hand (Phil Bartle, 2011).

1.12.2 Risk Management This is the process of identifying, assessing, prioritorizing and controlling risks as a project unfolds. Once risks have been identified, the project manager should create a plan to minimize or eliminate the negative impact of those risks. Strategies for dealing with risks will vary according to the type of risk and project. The goal of risk management is to protect the project from vulnerabilities. A variety of strategies can be utilized to minimize or eliminate risks, however the process for identifying and managing risks, consists of four main stages, namely, identifying the risks, assessing the impact of the risks, alleviating critical risks and controlling risks (Whatisriskmanagement.net n.d.).

Risk Identification This is the first stage of risk management and is concerned with outlining possible risks to the project. Possible risks are identified relevant to the project, product and business. Table 1.4 provided below outlines possible risks that may affect this project by an ID, description and type.

Risk IDRisk DescriptionRisk Type

R1Underestimation of software development time. Product and Project

R2Underestimation of size software. Product and Project

R3Financial problems encountered by the business forces reduction in project budget.Project and Product

R4Requirement changes are more than expected and require significant rework of design.Project and Product

R5Illness at a critical period of project.Project

R6Reusable software components are defective.Product

R7Unanticipated oracle errors where resolution is time consuming.Product and Project

R8Essential hardware, necessary for project not obtained on schedule.Project

R9CASE tools integration issues. Product

R10Employee resistance to change.Business and Staff

Table 1.12.2

Risk Estimation Matrix

PROBABILITYIMPACT

InsignificantTolerableSeriousCatastrophic

Very High80 - 100

High65 - 79

R9R1, R2

Moderate41 - 64

R10R4, R5, R6, R7,R8

Low1 - 40

R3

Figure 1.12.2

MAJOR PROJECTBSC BUSINESS COMPUTING

KENO LEE Page 194

1.12. 3 (A) Risk PlanRisk IDDescriptionRisk TypeRisk Probability (p)Risk Impact (i)Risk Exposure p*iRisk StrategiesRisk Potential Indicator

R1Underestimation of software development time. Product and ProjectHighSeriousCatastrophicConduct historic research on time taken to develop similar products.If early stages result in time overrun.

R2Underestimation of size software. Product and ProjectHighSeriousCatastrophicHave supplementary unit on standby that can be added to the project at short notice (2 weeks).Estimated delivery date consistently not being met.

R3Financial problems encountered by the business forces reduction in project budget.Project and ProductLowCatastrophicSeriousSource all finances for capital expenditure prior to project commencement.Inability to meet weekly financial commitment.

R4Requirement changes are more than expected and require significant rework of design.Project and ProductModerateSeriousSeriousIdentify trace information that can be utilized to assess the impact of changes to requirements.Regular request to add features to system.

R5Illness at a critical period of project.ProjectModerateSeriousSeriousStay ahead of each stage delivery date by at-least a week to cater for downtime.Drop in bodys resistance.

R6Reusable software components are defective.ProductModerateSeriousSeriousCater for replacing defective components with reliable components.Software component are over five years old.

R7Unanticipated oracle errors where resolution is time consuming.Product and ProjectModerateSeriousSeriousAnticipate the unanticipated in development relevant to time.High severity virus found in oracle installation folder.

R8Essential hardware, necessary for project not obtained on schedule.ProjectModerateSeriousSeriousOrganise for hardware to be delivered at-least five days before it is actually needed.Necessary hardware was not in stock and supplier awaiting shipment.

R9CASE tools integration issues.

ProductHighTolerableSeriousResearch CASE tool relevant to its integration prior to obtaining and using. Utilize integration software.

R10Employee resistance to change.

Business and StaffModerateTolerableModerateEducate and communicate to employee the importance and benefits of change. Involve them in the change process and let them know that their input is important.Employee displaying low morale and sudden unwillingness to work overtime.

Table 1.12.3(A)

1.12.3 (B) Risk Estimation KeyCategoriesRisk ProbabilityRisk Impact

Very High80 - 1009 - 10

High65 - 797 - 8

Moderate41 - 644 - 5

Insignificant1 - 401 - 3

Table 1.12.3 (B)

1.12.3 (C) Risk RatingsRisk IdRiskRisk ProbabilityRisk Impact

R1Underestimation of software development time. HighSerious

R2Underestimation of size software. HighSerious

R3Financial problems encountered by the business forces reduction in project budget.LowCatastrophic

R4Requirement changes are more than expected and require significant rework of design.ModerateSerious

R5Illness at a critical period of project.ModerateSerious

R6Reusable software components are defective.ModerateSerious

R7Unanticipated oracle errors where resolution is time consuming.ModerateSerious

R8Essential hardware, necessary for project not obtained on schedule.ModerateSerious

R9CASE tools integration issues.

HighTolerable

R10Employee resistance to change.

ModerateTolerable

Table 1.12.3 (C)

1.13 Quality Management

Quality Management can be defined as an organizational wide approach taken to develop a precise understanding of what customers need and consistently deliver accurate solutions to meet these needs within budget, on time and with minimum loss to society. The process of quality management will ensure an effective design of processes that verify customer needs, plan product lifecycle and design as well as deliver the product or service. Quality management incorporates the measurement of all process elements, the analysis of performance and the continual improvement of products, services and the process of delivering them to customers (Chartered Quality Institute, n.d.). This form of management will effectively lead to improved business performance and should consider factors such as what improvements the organization needs, what quality management system is applicable and which areas or processes should the quality management system address. The bullet points that follow represent the quality management activities covered in this project.

1.13.1 Product Attributes The quality of a developed product is influenced by the quality of the production process. This is an important aspect of software development, since some product quality attributes are hard to assess. There however exists a very complex and poorly understood relationship between software processes and product quality (Ian Summerville, 2011). The following factors can be used to measure quality relevant to product attributes (Software Testing Help, 2007):

Reliability This measures if the product is reliable enough to sustain in any condition. Consistently correct results should be a product of this product reliability should be measured in different working environments and under different conditions.

Maintainability Different versions of the product should be easy to maintain. The adding of code to the existing system should be possible and simple to do. The system should be easy to upgrade to incorporate new features and techniques. Maintaining the system should also be cost effective.

Usability This will be measured in terms of ease of use. Applications should be user friendly, easy to learn and easy to navigate. The system should facilitate the easy inputting of data, operations and interpretation of output. It should also provide consistent user interface standards or conventions with other systems. New or infrequent users should find the system easy to use. Correctness The application should be correct in terms of its functionality, internal calculations and navigation. Effectively the application should adhere to defined functional requirements.

Efficiency This is measured in terms of the time required to complete any task given to the system. Ideally the system should utilize processor capacity, disk space and memory efficiently. A system that uses all the available resources degrades the performance afforded to the user. A system that is not efficient cannot be used for real-time applications.

Integrity or Security Integrity is a by-product of security. The systems integrity or security should be sufficient to prevent unauthorized access to systems functions, prevent information loss, ensure that the software is protected from viruses and protecting the privacy of data entered into the system.

Testability The system should be easy to test and find defects. Individual module testing should be possible if required.

Flexibility The system should be flexible enough to modify. The system should easily adapt when interacting with other products.

Reusability Software re-use is a good cost effective and time saving development technique. Code libraries should be generic enough to be easily used in different application modules. Re-use of divided applications in different modules of an application should be possible.

Interoperability The exchange of product data or devices with other systems should be easy to do. System modules should be able to work on different operating systems, different databases and protocol conditions.

1.13.2 Method for Quality Control Quality control involves checking the software development process to ensure that quality assurance procedures and standards are being followed. The deliverables from the software process are checked against the defined project standards in the quality control process. There are two complementary methods that maybe used to check the quality of project deliverables, namely (Ian Summerville, 2011):1. Quality reviews - This is the principle method that can be used to validate the quality of a process or product. In this method examination or done to part or all of a process or system and its documentation to find potential problems. Quality reviews are responsible for checking that product standards have been followed and for conformation with these standards relevant to software and documents. Deviations from these standards are communicated to the project manager. There exist different types of reviews with different objectives, they are (Ian Summerville, 2011) : Inspections for defect removal (product) Reviews for progress assessment (product and process) Quality reviews (product and standards)

Table 1.7 outlines different review types and their principle purpose.

Review TypePrinciple Purpose

Design or progress inspectionsTo detect detailed errors in the requirements, design or code.

Progress reviewsTo provide information for management about the overall progress of the project. This is both a process and a product review and is concerned with costs, plans and schedules.

Quality reviewsTo carry out a technical analysis of product components or documentation to find mismatches between the specification and the component design, code or documentation and to ensure that defined quality standards have been followed.

Table 1.13.2There exist three review functions relevant to quality control. These review functions include (Ian Summerville, 20011):

Quality function This function form part of the general quality management process.

Project management function This function is useful for providing information to project managers.

Training and communication This function supports the sharing of product knowledge between development team members.

2. Software measurement and metrics This approach involves deriving a numeric value for some attribute of a software product or its process. Derived values can be compared to each other and to established standards across an organization. This comparison will allow for the drawing of conclusions relevant to the quality of software or software processes (Ian Summerville, 2011). Two ways in which this approach may be useful to quality control are: It allows for making general predictions about a system. Characteristics of a systems components can be measured and aggregated, allowing for a general estimate of some system attributes to be calculated. An example of such an attribute is the number of faults in the system. It allows for the identifying of anomalous components. Individual system components characteristics that deviate from the norm can be identified through measurements. Measurements of system components are done to ascertain those components that are likely to contain the most errors, allowing for concentration to be place on those components during the review process.

Software metrics can be described as any type of measurement that relates to a software system, its process or documentation. This type of metric may be either control or predictor metrics, both of which has an influential impact on management decision making. Figure 1.5 below provides and illustration of this as well as outlines the association of control metrics with software processes and predictor metrics with software products. The average effort and time necessary to resolve reported defects is a suitable example of control metrics. The complexity of a module, the average length of identifiers in a program and the number of attributes and operations associated with objects in design are all examples of predictor metrics (Ian Summerville, 2011).

Software product

Software process

Control measurementsPredictor measurements

Management decisions

Figure 1.13.2 (A) (Ian Summerville, 2011)The direct measuring of software quality attributes is often impossible since quality attributes such as maintainability, understandability and usability are external attributes that are relevant to how developers and users see the software. It is ideal that a clear and validated relationship between the internal and external software attributes be established. There exist three conditions that must hold if the measurement of internal attributes is to be useful to predicting external software characteristics (Kitchenham, 1990): Internal attributes must be measured accurately.

A relationship must exist between what we can measure and the external behavioural attribute in which we are interested.

This relationship is understood, has been validated and can be expressed in terms of a formula or model.

Figure 1.6 provides an illustration of the relationships between internal and external software attributes.

Number of procedure parameters

Maintainability

Cyclomatic complexity

Reliability

Program size in lines of code

Portability

Number of error messages

Usability

Length of user manual

Figure 1.13.2 (B) (Ian Summerville, 2011)

1.13.3 Tools for Assurance This involves the process of quality assurance. Quality assurance is any systematic process of checking to see whether a product or service being developed is meeting specified requirements (TechTarget, 2007). The process defines how software quality can be achieved and how the development organization determines that the software has the required level of quality. The quality assurance process is primarily concerned with defining or selecting standards that should be applied to the software being developed (Ian Summerville, 2011).

Two types of standards that maybe established parts of the quality assurance process are (Ian Summerville, 2011):

Product standards This applies to the software being developed and includes document standards. Examples of these standards may include structure of requirements documents, standard comment header for an object class definition and coding standards for defining the use of a programming language.

Process Standards This defines the processes that should be followed during software development. It may include definitions of specifications, design and validation processes and a description of the documents that should be written in the course of these processes.

To avoid quality assurance problems, quality managers should take the following steps:

Involve software engineers in the selection of product standards. Review and modify standards regularly to reflect changing technologies. Provide software tools for assurance and consider the ISO 9000 standard and documentation standards.

When considering tools for assurance the ISO 9000 standard and documentation standards should be considered (Ian Summerville, 2011).

ISO 9000 Is an international standard that can be used in the development of a quality management system. The standard can be applied to a range of organisations and industries. ISO 9000 is the most general and applies to organisations concerned with the quality process.

Documentation standards This is important to a software project because documents are the only tangible way of representing the software and the software process. Standardized documents have a consistent appearance, structure and quality and should therefore be easier to read and understand. Three types of document standards that exist are:

Documentation process standards. These standards define the process that should be followed when producing documentation.

Document standards. The structure and presentation of documents are governed by this standard.

Documents interchange standards. This standard ensures compatibility between all electronic copies of documents.

1.14 Implementation PlanThis plan will provide details of the various activities and strategies that maybe utilized when implementing the completed system at the business (BusinessDictionary.com, n.d.). The implementation plan will provide an overview of different deployment strategies, data migration, training and documentation. The following deployment strategies would be considered (Wordpress.com, 2008):

1.14.1 Deployment Strategies

Direct Cutover This approach involves immediate changeover from the old system to the new. This deployment method is usually the least expensive since only one system is operated at a time. Direct Cutover however involves the most risks when compared to the other methods.

Parallel Operation This approach requires that both the old and new system operate fully for a specified period of time. Only when the users and developers are satisfied will the old system be terminated. This method involves the least risks since if the new system does not work, the old system can be reverted to. Parallel operation is however the most costly method.

Pilot Operation This method will involve implementing the complete new system at a selected location of the business. A user group will test the systems functionality at the pilot location. The old system will continue to operate for the entire organization including the pilot site. Once the system is successful at the pilot site it is implemented throughout the rest of the organization, usually using direct cutover. Pilot Operation assures that the new system is working, reduces the risk of system failure and is also less expensive when compared to parallel operation.

Phased Operation This method implements the new system in modules or stages. This is also a combination of direct cutover and parallel operation and is similar to pilot operation. The phased operation approach involves providing part of the system to all users. The risk of failure is limited to the implemented module only and is less expensive than the full parallel operation. This method can however be more expensive than a pilot approach if the system to be implemented has a number of separate phases.

1.14.2 Justification of Deployment Strategy chosenHaving assessed the four deployment strategies it has been decided that the pilot operation approach will be most appropriate. The pilot approach is a combination of both direct cutover and parallel operation that will allow for restricting implementation to a pilot location. This reduces the risk of system failure when compared to the direct cutover method. Operating the system at the pilot is also less expensive than the parallel approach. This approach will allow for direct cutover to be used once the new system has been successfully piloted. This reduces the changeover time and the direct cutover method will be generally risk free at this point.

1.14.3 Data MigrationThe process of data migration generally refers to the transfer of data between formats, types of storage and computer systems. Data migration is usually done when a new system is being adopted and data in both systems need to be mapped to each other without difficulties. The process of data migration generally requires considerable amounts of time and labour, hence the reason why it is done automatically in most cases. Manual methods are however also frequently used. The method chosen for a given system is totally dependent on both the system involved and the state of the data to be migrated.Data cleansing is a common procedure that is performed during data migration. This procedure is aimed at improving quality and requirements matching. When deciding on a method of data migration the variables data volume and data value should be considered. The following analytical steps should be performed before data migration begins (ETL Tools, n.d.):

Analyse and define the source structure Analyse and define the target structure Map between the source and target structure Define the data migration method

The process of data migration for this project will be carried out manually since High Definition Video Club currently operates a manual, paper based system of recording information.

1.14.4 TrainingThere exist various methods of training, which can be divided into cognitive and behavioural methods. It is important that trainers understand the pros and cons of each method as well as its impact on trainees while keeping their background and skills in mind before giving training. (Training and Development.Naukrihub.com, n.d.).

Cognitive methods This involves giving theoretical training to the trainees. The different methods that fall under the cognitive approach provide the rules describing how to do something, written or verbal information and demonstrate relationships among concepts. These methods are associated with changes in knowledge and attitude by stimulating learning. The various methods that fall under the cognitive approach are: (Training and Development.Naukrihub.com, n.d.): Lectures Demonstrations Discussions Computer based training Intelligent tutorial systems Programmed instructions Virtual reality

Behavioural methods This involves giving more of practical type training to trainees. The various methods under the behavioural approach allow the trainee to behave as if in a real life situation. These methods are useful for skill development. The various methods that fall under the behavioural approach are (Training and Development.Naukrihub.com, n.d.): Games and simulations Behaviour modelling Business games Case studies Role plays

Documentation - This will refer to a documented user manual produced for end users. The user manual will provide users with instructions and guidelines relevant to the use of the new system. This documentation will be made available both in hard and soft copy.

2. LITERATURE REVIEW

2.1 Theoretical Study

2.1.1 Web Hosting This refers to the business of providing the storage, connectivity and service necessary to serve files for a website (Marketing Terms, n.d.). This generally involves putting your websites content on a web server. This server space can be bought or rented from an Internet Service Provider (ISP). Web hosting services are commonly served from one of the following two hosting platform (tutorialpoint, n.d.):

1. Web Hosting Servers These provides hosting servers running different flavours of Windows and are usually more expansive because of software incensing costs.

2. Linux Hosting Servers These provides hosting servers running different flavours of UNIX and are cheaper that the Windows Hosting Servers.

There exists a range of hosting types available for selection based on requirement and budget, which includes free hosting, shared hosting, virtual dedicated hosting, dedicated hosting and co-located hosting (tutorialpoint, n.d.).

2.1.2 Web Hosting Companies in Trinidad Research of three web hosting companies in Trinidad and Tobago was done relevant to the type of services they provide, the server language they use and database type. The following information was gathered during this research:

1. Trinidad Web Host This Company provide web hosting services for individuals, hobbyist, entrepreneurs and companies. These services include web hosting, VPS hosting, domain name registration and professional email plans. The web hosting service provided by this company offers features such as CPanel Control Panel, LiteSpeed Enterprise WEbserver and CloudLinux Commercial OS. Trinidad Web Host supports a variety of Linux compatible web languages such as php, html and perl. They support mysql and mysqli with prepared statements databases (Trinidadwebhost.com, n.d.).

2. Ecaribay This web hosting company provides products and services such as domain registration, domain transfers, shared hosting, email hosting and SSL certificates. This company provides Unix Hosting Plans which are available in personal, business or advanced. Ecaribay uses the Parallels Plesk Panel to support its clients. This panel is user-friendly and full of features aimed at ensuring an enjoyable web hosting experience. Its features includes sitebuilder with over 70 design templates, over 100 open source software and website staging. Ecaribay uses the server-side scripting language PHP5, a MySQL database and programming languages such as Python, Ruby on Rails and CGI/Perl (Ecaribay.com, n.d.).

3. Maximus Design Studios Ltd. This Company provides web hosting solutions with a range of useful features. Their influence span across Trinidad and Tobago and four countries including the USA, UK, Bahamas and Cayman Islands. Maximus Design Studios limited serves as a one stop shop for their clients design, web, marketing, print and internet needs. The web hosting solutions provided by this company affords its users with Fantastico One Click Installs, free site builder, easy to use control panel, web based email access and 99.9% uptime (Maximus DesignStudio LTD, n.d.).

2.2 Case Studies In this study research was done on three organisations running similar systems to that of the proposed Sales Database Management System. These organizations included Amazon.com, Ebay.com and Stubhub.com. The details of the study will provide a brief history of the organization, any problems faced and most importantly look on their technology in terms of hardware, software and website to database integration.

2.2.1 Amazon.comAmzon.com is a Fortune 500 e-commerce company based in Seattle, Washington. This organization is multi-national and was one of the first to sell goods over the Internet. Amazon.com was founded in 1994, but launched in 1995 and now sells a wide range of products including books, CDs and DVDs and clothing. In Amazons early years of existence, they experienced scaling issues which led Amazon to make a big architectural change from a two-tier monolith to a fully distributed, decentralized services platform serving many different applications.Today Amazon.com boast three of the worlds largest Linux Databases and a Central Data Warehouse comprising of 28 HP Servers/4 CPU nodes running on Oracle 9i software. Security was a major concern of Amazon.com since thousands of people send their personal and credit card information to their servers every day. To optimize their websites security Amazon.com employed the Netscape Secure Commerce Server using SSL protocol. Amazon.coms website application code is written in Perl/Mason with the latter allowing for the interpolating of Perl and HTML as is possible with PHP. The organizations architecture however includes other platforms and programming languages such as C++, Java, Jboss and Servelets (howstuffworks, n.d.).

2.2.2 Ebay.comFounded in 1995 Ebay.com is a multi-national online auction and shopping website that allows for buying and selling a wide range of goods and services world-wide. This organisations product and service range are categorized as Books, Clothing, Shoes and Accessories, DVDs and Movies, Electronics and Baby to name a few. In 1995 Ebay.com was built on FreeBSD, Apache, Perl and GDBM. In 1997 Ebays website migrated to NT, ISS and C++ with Oracle DB on Solaris. In 1999 Ebay suffered from a series of service disruptions and made a complete restructure of their architecture. Ebays entire system was re-written in J2EE in 2002 and by 2005 Ebay.com boasted 200 database servers housed in sets of fifty (50) at four (4) different locations and twenty (20) search servers. This companys technological architecture also includes fifty (50) web-servers, application servers and data storage systems that talk to each other with each server having between six (6) and twelve (12) micro-processors. It must be noted that although these servers communicate with each other they run separately, which makes the adding of additional servers easy should problems arise. The architecture is a type of grid computing that allows for collecting errors as well as growth. Ebays database runs on Oracle software and the overall architecture operating on a mix of UNIX and Windows Operating System. Ebay.coms infrastructure allows millions of people to search, buy and sell items simultaneously. On the user end the system is a seamless one (High Scalability, 2008).

2.2.3 Stubhub.comStubhub.com is an online ticket marketplace and E-Bay subsidiary that facilitates the buying and selling of tickets to live entertainment and sporting events. Founded in 2000 this organization grew fast and by 2006 the companys limited technological infrastructure threatened their long term survival. Stubhubs access to data, customers and business drivers were inefficient and outdated. A combination of open source technology with the best of breed software tools were looked on as a possible solution that would provide a scalable warehouse infrastructure.Today Stubhub.coms technological infrastructure includes a mix of open source technology and best of breed software tools from Business Objects, Oracle, Omniture and SAS. A phased approach was used to deploy the extendible business intelligence (BI)/ data warehouse (DW) infrastructure. Stubhub.com moved from Access and Excel to Oracle and Business Objects which they still use today. Currently the company utilizes the software program Omniture to monitor its websites activity and to produce real-time reporting. Stubhubs architecture also includes three sources of ticket purchases namely Web, Point of Sale Systems and Bulk upload. A Manager layer provides object abstraction above the Ticket database as well as mediates all conversations with the ticket table. Two data pump feeds data from the ticket database to internal and external systems. This architecture is supported by a platform that includes Java, Cold Fusion (Legacy), ActiveMQ, SEDA, Jboss, XSL, Advanced Queuing from Oracle, Apache HttpClient and Log4j using the messaging format (High Scalability, 2012).

3. RESEARCH OR INVESTIGATIVE METHOD

Details of the research or investigative method selected:

Research Types

Inductive ApproachDeductive Approach

3.1 Deductive/Inductive

3.1.1 Deductive Research Approach The deductive research approach works from a more general to the more specific. This is often informally called a top-down approach. This approach generally begins with a theoretical thought related to a topic of interest. This is then narrowed down into more specific hypotheses that are testable. This approach narrows specifics even further when observations to address the hypotheses are made. Ultimately it allows for the testing of the hypotheses with specific data, which generally is a confirmation of original theories. Conclusions follow logically from available facts (Research Methods Knowledge Base, 2006).

3.1.2 Inductive Research Approach The inductive research approach moves from specific observations to broader generalizations and theories. This approach is sometimes informally called a bottom up approach. Inductive research begins with specific observations and measures. Patterns and regularities are detected and some tentative hypotheses that can be explored are formulated. The final output of this research is the development of general conclusions and theories. This approach involves some degree of uncertainty (Research Methods Knowledge Base, 2006).

3.2 Survey/Case Study/Action Research

3.2.1 Survey Research This is one of the more frequently used quantitative social science research. The survey approach involves the researcher selecting and administering a standardized questionnaire to a sample of respondents. A survey can be a written document that is completed by the person being surveyed, an online questionnaire, a face to face interview or a telephone interview. Surveys allows for the collecting of data from large or small populations which is sometimes referred to as the universe of a study. There exist several types of surveys which can be distributed using a variety of media. These include written surveys, oral surveys, electronic surveys and example surveys. The methods utilized when designing, conducting, analyzing and reporting the results of surveys differs according to the goals of research. The surveyed population and the survey type used (Writing@CSU, n.d.).

3.2.2 Case Study A case study from a research perspective is a holistic inquiry that investigates a contemporary phenomenon within its natural settings. This generally involves collecting and presenting detailed information about a particular participant or small group, frequently including the accounts of subjects themselves. This type of research is a form of qualitative descriptive research which looks intensely at an individual or small participant pool and drawing conclusions only about that individual or participant group and only in that specific context. This research method emphasizes on exploration and description and not the general truth (Writing@CSU, n.d.). Case Studies may deal with either single or multiple cases, with single case studies having two types, namely intrinsic and instrumental. An intrinsic case study is aimed at learning about a unique phenomenon which the study is focused on. An instrumental case study is aim at providing a general understanding of a phenomenon using a particular case. The collective case study deals with multiple cases and is aimed at providing a general understanding using a number of instrumental case studies (Yin, 1999). The type of study performed is dependent on the type of case that is most useful for the purpose of the research.

3.2.3 Action Research The action research method is a type of research where researchers reflect systematically on their practice, implementing informed actions to bring about improvement in practice. It is also widely described as a form of self-reflective enquiry undertaken by participants in social situations in order to improve the rationality and justice of their own social or educational practices, their understanding of these practices and the situation in which these practices are carried out. This research method defines areas for improving learning, developing action plans, acting on plans, gathering data, assessing their learning and redefining areas of further improvement. The main characteristics of action research are, it follows a cycle, it requires separate but mutually dependent steps, it is participative and allows for both the researcher and the subject to be active participants in the research process, it generates qualitative data and the process is reflective. Action research processes vary, however there is common emphasis on critical and democratic social theory and a departure from unengaged research as the appropriate enquiry path for practitioners in practical solutions (Carr and Kemmis, 1986).

3.3 One/Mixed/Multi

An appropriate method of research must be selected once your idea has been turned into a research question and a review of any necessary literature done. The methodology selected should be the one considered to be most effective for collecting the data needed to test the hypothesis. A research method can either be qualitative or quantitative. It however must be noted that it is possible to use mixed or multiple approaches. When considering the one approach, any of the following two methods can be used:

3.3.1 One Method Research Quantitative Methods Using this type of research, the data collected takes the form of measurements or counts which can be statistically analyzed. Quantitative research follows standard procedures, methods, forms of analysis and reporting the results of the research undertaken. This standardisation maximises objectivity and the method is based on meanings derived from numbers and results are numerical and standardised data (rdinfo.org.uk, n.d.).

Qualitative Methods This approach offers insights and understanding of participants, which is not obtainable from quantitative research. Qualitative research aims to study the subject in their natural surroundings and to collect naturally occurring non-biased data. Descriptions are given in words rather than numbers of the qualities of the subject through observation. Methods of qualitative research include structured and unstructured interviews, group interviews and focus groups. Using qualitative research methods allows for highlighting key themes or patterns emerging in the project and using them to comprehend and manage data when developing and testing the hypothesis (rdinfo.org.uk, n.d.).

3.3.2 Mixed Method ResearchMixed method research is a combination of both qualitative and quantitative research methods. This approach can be used in various ways, whereby each approach contributes to the description of a phenomenon. This approach allows for a better understanding of research. Mixed methods are research strategies that cross the boundaries of conventional paradigms of research by deliberately combining methods drawn from different underlying assumptions. There exist four mixed design approaches that may be used in mixed method research, namely concurrent design, concurrent triangulation, parallel design and sequential designs (Diversified Topics, 2011).

3.3.3 Multi Method ResearchMulti method research uses different methods of data collection and analysis with a single paradigm. In this approach, reference can be made to quantitative or qualitative approaches. There exist two types under this approach, namely multi method quantitative studies and multi method qualitative studies. The multi method quantitative studies stay within the paradigm but use more than one method of data collection. The multi method qualitative studies on the other hand may combine interviews and observations made of email discussions. The idea is to cross check between sources and to supplement one kind of data with another (Commonwealth of learning, n.d.).

3.4 Data Collection Methods and AnalysisThe most important rule concerning data collection and analysis is not to collect or analyse all possible kinds of data. Relevant to this project the following methods will be explored:

3.4.1 Interviews This is one of the most common methods for collecting data in qualitative research. Interviews allow participants to provide rich, contextual descriptions of events. The process can be somewhat time consuming and the quality of data is often dependent on the aptitude of the interviewer (Michelle Bryne, 2001). There exist three approaches to qualitative interviews namely, informal conversational, semi-structured and standardized open-ended. Interviews are useful for getting more in-depth information about perceptions, insights, attitudes, experiences or beliefs. It also allows for evaluating individual differences between respondents experiences and outcomes and serves as a follow up to other methods (Data Collection Methods for Evaluation, 2009).

3.4.2 Questionnaires These are a set of carefully designed questions given in exactly the same form to a group of people for the purpose of collecting data about some research topic (SAGE researchmethods, 2006). Questionnaires can be administered by mail, telephone, using face to face interviews, as handouts or electronically. The use of questionnaires are appropriate when resources are limited and you need data from many people, to gather data about knowledge, beliefs, attitudes and behaviours and when it is important to protect the privacy of participants (Evaluation Briefs, 2008).

3.4.3 Observations This is a method by which an individual or individuals gather first hand data on systems, processed or behaviours. It allows for collecting data on a wide range of behaviours, to identify a variety of interactions and to openly explore the evaluation topic. Direct observation of operations and activities allows the evaluator to develop a holistic perspective relative to the context within which the project operates. This method also allows the evaluator to learn about things the participants or staff maybe unaware of or unwilling to discuss in an interview. Observations may be are useful during both formative and summative phases of evaluation (nfs.gov, n.d).

3.5 MethodologyThis refers to the proper documentation of stages in the system development lifecycle. A methodology clearly states well defined objectives and outputs that each phase must produce. The defined output must be achieved at the end of each stage for the other to initiate. This term also outlines the framework for documentation as well as procedures and coding standards (kuhnllc.com, n.d.). This project will feature one of the following two methodologies, namely the Structured System Analysis and Design Methodology (SSADM) and the Object Oriented Methodology.

3.5.1 SSADM This is a systems development methodology that can be applied to the analysis and design stages of system development. This methodology involves a systematic approach to the analysis and design stages however strategic informational planning issues as well as the physical building, software testing and implementation are excluded. The two stages are broken down, defined and illustrated using text as well as diagrams. SSADM involves three main techniques in its development process, namely:

Logical Data Modelling This involves modelling the data requirements of the system. These requirements are indentified, modelled and properly documented.

Data Flow Modelling This is the process of modelling and identifying how data circulates within a system. Details identified and modelled must be well documented.

Entity Behaviour Modelling This is the process of identifying and modelling the events that directly impacts each entity. In this process sequential events are identified, modelled and documented in the sequence that they occur.

3.5.2 Object Oriented Methodology This is a programming methodology that is based on objects instead of just functions and procedures. These objects are organised into classes which allows for grouping individual objects together. The techniques this methodology affords can be used by analyst to identify objects of the system and their behaviour as time goes by and changes that occurs as a result of the happening of events. An object in this methodology refers to a specific type of instance or a class (Techterms, n.d.). Relationships that exist between objects of the system are defined and their attributes, differences and system manipulation needs identified and explored. Object Oriented Methodology utilizes Unified Modelling Language (UML) when designing and this allows for specifying, visualizing, constructing and documenting the systems artefacts. UML allows for the graphical display of analysis and design (Sanskrut, 2007). In object oriented design there exist three main mechanisms that form the foundation for the systems development. These mechanisms are (James, M. and James, O., 1998):

Encapsulation This refers to the process whereby objects compile data and their access methods. When this occurs, data within objects are only accessible via the use of these methods and data cannot be seen by the outside world when an object is encapsulated.

Inheritance This refers to when an object that belongs to an overall class of objects has the same access methods and characteristics. Objects may inherit characteristics from their parent class.

Polymorphism This refers to instances where different classes can implement the same message.

The object oriented process involves identifying system objects and relationships that exist among them. Once these relationships are identified, then coding can begin. System analysis, system design, object design and implementation are all foundation stages of this process.

3.6 Justification of choiceIt has been decided that the object oriented methodology will be used in the development of the system. This methodology was considered to be the most appropriate having chosen the Waterfall Lifecycle Model as the development specification on which the system will be developed. The Waterfall Lifecycle Model allows for research to be done at each of its stages, which provides a solid grounds for the initial object oriented designs to be drawn. This combination will allow for a combination of proper textual documentation as well as diagrams for illustrating design. It will also provide a wider scope for users to understand the proposed system as well as the promise of reduced maintenance, code reusability, real world modelling and improved reliability and flexibility. The Object Oriented Methodology is an approach to system design which can be implemented without any changes to existing software technology.

4. FEASIBILITY STUDYThe conducting of a feasibility study in the early stages of a project is crucial, since the study serves as a vital component in the business development process and enables organizations to assess the viability and cost benefits of the project before allocating financial resources. It also provides an independent assessment of the project and an overall enhancement of a projects credibility. A feasibility study serves as a useful logical tool that aids the economic decision making process, ensuring that viable decisions are made before resources are invested (existbi, n.d.).

4.1 Business Case This is part of a projects mandate and is produced before the project initiates. A business case seeks to address at a high level, the business needs that the project should meet. It usually includes the reasons for the project, expected business benefits, different options considered with the relevant justification where selections are made and the expected cost of the project. The business case is usually reviewed at the initiation of the project before a Go or No Go decision is made and should ideally be periodically reviewed during the project. Periodical review ensures that the business case is still valid and that the project is still on track to deliver the solution to the business need (infolific, n.d.). Relevant to this project, the following points will are discussed:

4.1.1 Economic Analysis This is the most widely used method when evaluating the effectiveness of developing a new system. This term is commonly referred to as a cost/benefit analysis and the procedure is aimed at determining the benefits and savings that are expected from the proposed system and comparing them with costs. When benefits outweigh costs then the decision to go ahead with the project can be made. Cost and benefit factors are identified in this analysis and can be categorised as development cost, operation cost and benefits (Matson, J., 2000). Specific for this project, the following points will be discussed under economic analysis:

Cost Benefit Analysis This is a technique that should be utilized to help in deciding the feasibility of the proposed system. This analysis will quantify the Database Management Systems costs and benefits and provide realistic statistics to aid the decision making process. Relative to this project the cost benefit analysis will consider all development costs, cost pertaining to building the system as well as implementation costs. The analysis that follows will consider hardware, software, labour, training and installation costs. This analysis will determine from a financial perspective whether it is feasible to go ahead with the project (cs.uwaterloo.ca, n.d.).CostsEstimated CostsTotal

Year 0Year 1Year 2Year 3Year 4Year 5

DEVELOPMENT COST1 Dell Desktop Computer$4000.00______________________________$4000.00

1 HP LaserJet Pro$1200.00______________________________$1200.00

1 Modem (Provided with Internet Service)

$250.00______________________________

$250.00

Norton Antivirus (1 Year)$220.00______________________________$220.00

Microsoft Office Professional$1280.00______________________________$1280.00

Total Development Cost$6950.00______________________________$6950.00

OPERATIONAL COSTComputer Service________________________$500.00$750.00$1250.00

Printer Ink and Paper$850.00$850.00$850.00$850.00$850.00$850.00$5100.00

Norton Re-Activation$220.00$220.00$220.00$220.00$220.00$1100.00

Electricity______$4000.00$4000.00$4000.00$4000.00$4000.00$20000.00

Internet______$2500.00$2500.00$2500.00$2500.00$2500.00$12500.00

Total Operational Cost$850.00$7570.00$7570.00$7570.00$8070.00$8320.00$39950.00

Accumulative Cost$7800.00$15370.00$22940.00$30510.00$38580.00$46900.00$46900.00

BENEFITSComputerized records of sales and stock.______

$3200.00

$3300.00

$3400.00

$3500.00

$3500.00

$20900.00

Computerized records of balances owed.______

$2500.00

$2600.00

$2600.00

$2800.00

$3000.00

$16500.00

Reliable computerized storage.______

$2350.00

$2400.00

$2400.00

$2500.00

$2600.00

$14250.00

Efficient and customer friendly information gathering.

______

$1900.00

$2200.00

$2250.00

$2300.00

$2500.00

$12650.00

Reduced data management time.______

$1520.00

$1800.00

$1800.00

$1900.00

$2000.00

$10270.00

Easier data analysis capabilities.______

$2100.00

$2250.00

$2300.00

$2300.00

$2500.00

$12700.00

Total Benefits______$13570.00$14550.00$14750.00$15300.00$16100.00$74270.00

Accumulative Benefits______$13570.00$28120.00$42870.00$58170.00$74270.00______

Table 4.1.1 (A) Net Benefit Total BenefitsMinusTotal CostsEqualsNet Benefit

Year 1$13570.00-$7570.00=$6000.00

Year 2$14550.00-$7570.00=$6980.00

Year 3$14750.00-$7570.00=$7180.00

Year 4$15300.00-$8070.00=$7230.00

Year 5$16100.00-$8320.00=$7780.00

Total$87270.00-$39100.00=$35170.00

Table 4.1.1 (B)

Break Even Analysis

Figure 4.1.1 (A)

Return on Investment (ROI) Over 5 YearsCalculationROI

$35170.00100 $46900.0074.9 %

4.1.2 Social Analysis A social analysis is a very important aspect of a feasibility study. This analysis will outline the users of the system and identify the different ways in which the implementation of the new system may impact them from social perspective. Relative to the staff at High Definition DVD Club the following social impacts have been identified:

Employee Satisfaction All employees have expressed their satisfaction towards the implementation of the new system. The manager has assured her support staff that his job is not at risk and as such he now sees the new system as tool through which his job will be made easier, efficient and more effective.

Increased Morale The manager as well as her support staff has both indicated that the implementation of the new system will be a huge morale booster. They have both portrait high levels of confidence and enthusiasm towards the proposed system and are looking forward to using the new system to carry out their duties.

Resistance to Change No employee of High Definition DVD Club has resisted to the implementation of the new system. The manager ensured that her support staff was involved from the projects initiation, keeping him well informed and educated as to what the project involves and the benefits that the new system will bring. The manger has made it clear to her support staff that his input is important to the projects success and that his job is in no way under threat.

4.1.3 Technical Analysis This analysis will involve the analysis of the businesss environment specific to its physical structure and business operations relative to its current technological infrastructure and the suggested technological infrastructure. This analysis will specifically look on hardware, software, benefits and cost as it relates to the current and suggested technological infrastructure.

Current Technological InfrastructureThere currently exists one desktop computer valued at three thousand five hundred dollars at High Definition DVD Club. This computer however has never been used for the recording of sales, stock or customer membership and has primarily been used for troubleshooting DVD errors and non-functionality. Apart from this computer, there exists no other hardware or software relative to the business technological infrastructure. The business has operated a strictly manual system of recording transactions since its inception. Infrastructure to support the use of technology is however present and includes a proper electrical supply and existing wiring to support an Internet service since the business currently has Flow Cable TV installed.

Suggested Technological Infrastructure

ComponentCost Benefits

HARDWARE1 Dell Desktop Computer (Intel Core i3 processor @ 2.60 GHz, 4 GB DDR3 SDRAM, 500 GB Hard Drive, Intel HD Graphics 2000, 20 Monitor and 18X DVD Burner)

$4000.00 Provides the hardware on which the Database Management System will be installed. Provides the hardware on which a host of other programmes can be used preparing and analyzing reports.

1 HP LaserJet Pro P1606dn$1200.00 Will allow for the printing of reports.

1 Modem (To be provided with Flow Internet Service)$250.00 Will allow for Internet accessibility.

SOFTWARENorton Antivirus Software (1 Year)$220.00 Provides security against malicious threats that may harm the computer.

Microsoft Office Professional (Full)$1280.00 Provides a range of programmes that will be useful when preparing reports and conducting analysis.

Adobe Reader (Free with Desktop)_____ Will allow for the opening and viewing of PDF files. This will beneficial since archive records will be maintained as PDF for security reasons.

4.1.4 Go or No Go DecisionThe investigative and analysis work done in the feasibility study painted a clearer picture of what the business will be required to inject into the project over a five year period relative to the development of the Sales Database Management System as well as the benefits that the business will enjoy over a five year period. Analysis work done in the different area of the study provided factual evidence of the projects feasibility. This study was utilized during the decision making process with management and they were impressed with the proposed benefits and most of all the 74.9% return on investment over a five year period. The manager has given the go ahead to move forward with the development of the Sales Database Management System.

5. SYSTEM ANALYSISThis analysis will involve a systematic approach that is aimed at helping the decision making process relevant to choosing a course of action by investigating the full problem and defining objectives and alternatives for a problem solving comparison.

5.1 Problem Specification of current system The current system of operation at High Definition DVD Club is strictly manual. The operation of such a system have been and been extremely tedious over the years and have drastically impacted the quality of data recorded. The current system does not afford its users efficiency, consistency and conciseness when recording business transactions. Data recorded is often incomplete and contain errors. The business has been losing income as a result of the manager having to concede in business transactions due to the lack of sufficient documentation to back any inconsistencies. These problems associated with the current system are stifling the businesss progress and as such the manager is now certain that change is the answer to her problem.

5.2 Fact Finding This is an investigative process that was carried out with the aim of gathering facts on the business for analysis purposes. A series of techniques including questionnaires, interviews, observations and documentation was utilized in this process.

Questionnaires These were prepared and handed out to customers at High Definition DVD Club and residence of the area. The questionnaire consisted of strictly close ended questions and had three main sections namely, demographics, problems encountered and recommended solutions. The graphs and pie charts that follow are statistical representations of analysis done with the facts found. Interviews An interview with the manager of High Definition DVD Club was arranged as another technique that can be used to gather facts. A compliment of seven questions was prepared and served as the tool through which the managers view on the current system as well as the proposed Sales Database Management System. It must be noted that any information considered to be relevant outside of what is gathered from the interview questions will also be recorded.

Observations This form of fact finding was conducted as a subset of the interview process. This technique was used to get a first hand view and better understanding of the businesss day to day activities, events and processes. This will be conducted over a two day period.

Documentation This form of fact finding is essential to analysis and involves defining the content and types of document stored. High Definition DVD Club currently do all their documentation in note books.

5.3 Analysis of data collected This will involve the assessment and analysis of the facts found having handed out questionnaires to customers of High Definition DVD Club. The graphs and pie charts that follow seek to meaningfully display statistical data gathered so as to allow for analysis.

5.3.1 Questionnaire Analysis

Figure 5.3.1 - relative to customer age group

Figure 5.3.1 represents statistics of the data gathered relative to Question 1. This question sought to determine the age group of customers that frequents the business. The findings show that 45% of the businesss customer population falls within the 18-24 age group, 40% between 25-31, 10% between 32- 40 and 5% over the age of 40. It is evident that the vast majority of the DVD Clubs population falls between the ages of 18-31. 85% of the population falls within this age group.

Figure 5.3.2 - relative to keeping paper based records using manual system

Figure 5.3.2 represents statistics of the data gathered relative to Question 5. This question sought customers view on the manual and paper-based methods of recording business transactions at the DVD Club. It is quite clear from the graph, customers opinion of such as system. 93% an overwhelming majority of customers find it unacceptable. This strengthens the case for the proposed Sales Database Management System.

Figure 5.3.3 - relative to financial differences with the manager

Figure 5.3.3 represents statistics of the data gathered relative to Question 7. This question sought to determine whether customers had any financial fall outs with the manager due to the improper keeping of records. The graph shows that 50% of customer never had such. This is good, however of the other 50% some more than others experienced such. While 35% of this 50% only experienced this once or twice, steps must be taken to ensure that such differences are not as a result of improper record keeping.

Figure 5.3.4 relative to the areas that negatively affect customers the most

Figure 5.3.4 represents statistics of the data gathered relative to Question 8. This question sought customers view on the business area that affects them most at the DVD Club. The pie chart shows that a vast majority of 65% of the customer population are affected by improper record keeping. A noticeable 25% indicated that service affects them the most and the remaining 10% of the population event split between the business layout and product availability. It is quite evident from these findings that current system is hurting not only the business but its customers.

Figure 5.3.5 relative to whether the manual paper based system is the cause of the problems

Figure 5.3.5 represents statistics of the data gathered relative to Question 9. This question sought customer opinion on whether the manual paper based system of operation is the cause of the problems faced at the DVD Club. It is clear from the doughnut chart that the current system is the cause of the problem in the customers opinion. A clear majority of majority of 90% of customers response was Yes and a mere 10% of them thought otherwise.

Figure 5.3.6 relative to a resolution for the problem

Figure 5.3.6 represents statistics of the data gathered relative to Question 10. This question sought customers suggestions as to a resolution to the problems being faced. The graph shows that a clear majority of 93% of customers believe that a computerized system will solve the problems currently faced. Of the remaining 7%, 5% sees proper management as the resolution and 2% indicating that filing cabinets will do the job.

5.3.2 Interview AnalysisThis interview and analysis was done with the aim of gathering firsthand data from the manager relative to the businesss current system of operation, the problematic junctions in the current system, her views on the proposed Sales Database Management System as a possible solution, her functional expectations of the proposed system and how she plans to finance the proposed business plan. The report that follows provides an analysis of the facts found in the interview.

The manager has indicated that she currently runs a manual paper-based system of recording her business transactions. She described the current system of manually entering details of Sales, Stock and Customer Membership in notebooks as tedious and inefficient. She has also indicated that her current method of generating reports from data recorded in the notebooks is inconsistent and sometimes incorrect.

The manager outlined the process of recording business information as the junction at which problems plague the current system. Problems associated with consistency, correctness, efficiency and tediousness of data collection, drastically affects her ability to liaise with her customers on the business floor. The manager in her feedback expressed great concern about discrepancies that are difficult to trace and correct in her profit calculations. She believes this is due to the inconsistency and incorrectness of the data recorded. When asked about the proposed Sales Database System as a possible solution, she responded with a confident Yes. She indicated that the system will improve the operation efficiency and effectiveness of the business. She expressed confidence that her record keeping problems will be a thing of the past with the implementation of such a system. She is very enthusiastic about working with a system from which she can easily create, read, update and delete details of Sales, Stock and Customer Membership. She also expects that the generating of reports will become easy.

Relative to financing the business plan, the manger indicated that while she does not have all the funds in savings, she will be looking to her bank for the funding required to finance the proposed business plan. She believes that she has a sound understanding of the proposed Sales Database Management System and the benefits it will bring her business and has dedicated her full support.

5.3.3 Observation AnalysisObservation of High Definition DVD Club was conducted over a two day period with the aim of ascertaining and understanding the businesss activities, events and processes using a birds eye view approach. This observation looked on processes, events and activities, data storage and people.

Process, Events and Activities Sales It was observed that the DVD Club consistently enjoys high customer traffic, with the majority of customers making a purchase. The process of Sales included customers browsing DVD displays and selecting DVDs they are interested in purchasing. Customers would then approach the sales counter at which point a payment is made. Details of the sale are then recorded in a notebook label Sales by the manager. It must be noted that non-membership customers are offered membership to the DVD Club in this process. Customers who accepted were required to provide some personal identification information to the manager who in turn recorded the information in a notebook labelled Membership Customers.

Stock Purchasing The purchasing of stock whether new or the replenishing of stock when the re-order level is met was done on Mondays and Thursdays. The manager would inform her supplier of the stock needed prior to the days mentioned and the supplier in-turn will prepare and deliver stock on the identified days. It was observed that on delivery, the supplier would pack out stock on the display walls under the supervision of the support staff. On completing this, the supplier provided invoicing for the order which the manager double checked before making a payment.

Calculation of daily sales This is done each night on the businesss closure by the manager. This generally involved the addition of all sales recorded on the day. It was observed that when stock is taken and payments are made to the supplier from the days sales, this cost incurred is subtracted from the days sales.

Data StorageData of sales, stock and customer membership was recorded in three separate notebooks that were labelled relative to what was being recorded in it. It was observed that lines were drawn in each to provide some separation of data inputted. These record books were stored in a filing draw used to house other important documents, namely receipts and utility bills. The filing draw is located behind the sales counter and is kept locked after business hours. Only the manager has the key for accessing the draw.

People Manager It was observed that the manager oversees all operations of the business, ensuring a smooth flow on a daily basis. She facilitates customers purchase after they have browsed and selected their DVD. When stock reaches its re-order level, the manager is responsible for purchasing stock. The payment of the businesss utility bills is also done by the manager and it must be noted that the manger performs in the capacity of a records keeper since she is also responsible for recording and storing all business information.

Support Staff It was observed that the support staff provides any technical or general support to customers with regards to previewing DVDs using the televisions and DVD players within the business. He is also responsible for ensuring the neatness and attractiveness of wall displays and the overall tidiness of the business interior and exterior. His physical presence is important to a smooth flow of events at the business.

5.4 Object Oriented Analysis and Design Diagrams Current System

5.4.1 Use Case Diagram (Current System)

Figure 5.4.1Figure 5.4.1 provides a visual description of the current system operated by High Definition DVD Club from a Use Case perspective. The diagram outlines the user of the current system and the tasks she manually performs.

5.4.2 Class Diagram (Current System)

Figure 5.4.2

Figure 5.4.2 provides a visual illustration of the current system operated by High Definition DVD Club from a Class: perspective. The diagram describes the object and information structures used by the manual paper based system operated at the business. This is done internally and via communication with its users. Classes and relationships that exist between classes are outlined in the diagram above. 5.4.3 Sequence Diagram for Sales Process (Current System)

Figure 5.4.3

Figure 5.4.3 provides a visual description of the interactions that existed between the customer, manager and objects in the current manual paper-based system and the messages that are passed between them during the Sales process.

5.4.4 Sequence Diagram for Purchase Process (Current System)

Figure 5.4.4Figure 5.4.4 provides a visual description of the interactions that existed between the supplier, manager and objects in the current manual paper-based system and the messages that are passed between them during the Purchase process. 5.4.5 Sequence Diagram for Customer Membership Process (Current System)

Figure 5.4.5Figure 5.4.5 provides a visual description of the interactions that existed between the customer, manager and objects in the current manual paper-based system and the messages that are passed between them during the Purchase process.

5.5 Object Oriented Analysis and Design Diagrams Proposed System

5.5.1 Use Case Diagram (Proposed System)

Figure 5.5.1Figure 5.5.1 provides a visual description of the proposed system operated by High Definition DVD Club from a Use Case perspective. The diagram outlines the user of the proposed system and the tasks she will perform using new system.

5.5.2 Class Diagram (Proposed System)

Figure 5.5.2

Figure 5.5.2 provides a visual illustration of the proposed system operated by High Definition DVD Club using a Class Diagram. The diagram describes the object and information structures used by the manual paper based system operated at the business. This is done internally and via communication with its users. Classes and relationships that exist between classes are outlined in the diagram above.

5.5.3 Sequence Diagram for Sales Process (Proposed System)

Figure 5.5.3

Figure 5.5.3 provides a visual description of the interactions that existed between the customer, manager and objects in the proposed system and the messages that are passed between them during the Sales Process.

5.5.4 Sequence Diagram for Purchase Process (Proposed System)

Figure 5.5.4

Figure 5.5.4 provides a visual description of the interactions that would exist between the manager, supplier and objects in the proposed system along with the messages that are passed between them during the Purchase Process. 5.5.5 Sequence Diagram for Add Customer Membership Process (Propose