DOC

Technology Feasibility Report

By Floyd Ortiz,2014-05-17 10:56
8 views 0
Section 1 ? Technology Feasibility Report. Diagram. Three Tier Model. Technology. MySQL. ODBC native DB Interfaces. HTTP. Response/Request. Technology

    BSc in Commercial Software Development

    Report 3

    Date: 5 December 2003

    41CSD2003-331.000

    Jennifer Merrigan

    Janette Murphy

    Damien Power

Table of Contents

Section 1 Technology Feasibility Report .................................................. 3

    Diagram ........................................................................................................... 3

1. Discussion of Each Component ................................................................. 3

     MySQL .................................................................................................. 3

     PHP ...................................................................................................... 3

     Apache ................................................................................................. 4

2. Justification of Technologies ................................................................... 4

3. Problems Encountered ............................................................................ 4

     SNET .................................................................................................... 4

     Oracle ................................................................................................... 5

     MySQL .................................................................................................. 5

     Lunar Pages ......................................................................................... 5

Section 2 Risk Management ......................................................................... 6

    Risk management ........................................................................................... 6

    Introduction .................................................................................................. 6

Risk Identification ............................................................................................ 7

Risk Analysis ................................................................................................... 8

Risk Planning ................................................................................................ 10

Risk Monitoring.............................................................................................. 11

     2

    Section 1 Technology Feasibility Report

Diagram

    Three Tier Model

     HTTP ODBC Technologies Technology Technology Response/native DB RequestInterfaces HTML Apache MySQL PHP Server VB

     Client Middle Server

     Tier Tier Tier

1. Discussion of Each Component

    ? MySQL

    The MySQL database server is the world's most popular open

    source database. Its architecture makes it extremely fast and

    easy to customize. Extensive reuse of code within the software

    and a minimalist approach to producing functionally rich features

    has resulted in a database management system unmatched in

    speed, compactness, stability and ease of deployment. The

    unique separation of the core server from the table handler

    makes it possible to run with strict transaction control or with

    ultra-fast transaction less disk access, whichever is most

    appropriate for the situation. MySQL to us stood out. MySQL is

    our database (provider). It supports multi-users much better than

    its rivals.

    ? PHP

    PHP is a widely-used general-purpose scripting language that is

    especially suited for Web development and can be embedded

    into HTML. PHP is the programming language that will allow us

    to query and input information into our MySQL database.

     3

    ? Apache

    Apache is our virtual server technology. Apache is a virtual

    HTTP web server. It can be downloaded as a binary or for

    windows. It is free to download and it works with the majority of

    operating systems that are available. It is reliable and secure

    and it supports SSL (Secure Sockets layer) security.

    Since April 1996, Apache has been the most popular web server

    with up to 60% of websites using it thus making it the more

    widely than all the other web servers combined. One of the main

    reasons that Apache has been so successful is that, because it

    is virtual you don’t have to be online to use it.

    2. Justification of Technologies

Our first decision was to use SNET, a WIT server provider. This

    hosted a number of problems for us (discussed below). When this

    didn’t work out for us it was back to the drawing board. We thought

    about going down the path of the IIS server in the college but as it

    we used this last year and that you cannot connect to the IIS server

    from home we decided to look elsewhere. Reluctant at first we

    decided to set up MySQL, PHP and an Apache server on Jennifer’s

    laptop, the problem with this is that for the moment all three team

    members have to work from this one device, but as the weeks go

    on we intend to have the three technologies set up on all team

    members computers.

    3. Problems Encountered

? SNET

    The process with SNET is to register with them by paying 3 euro

    to join their society. Then they give you a username and

    password to access your domain. We then proceeded to up

    load our pages, SNET showed our PHP pages no problem, but

    it was only when we tried to link our database technology

    MySQL came the problems. The college does not support

    MySQL so you have to create it at home, when it came to

    creating a connection, an error came up saying no connection

    available to the server SNET, We then proceeded to email

    SNET and asked them why, they came back saying that the

    college has a firewall in place that stops people accessing the

    server from outside the college but gave us a WINSCP2.exe file

    that allows you to upload files but not create a connection to the

    database.

     4

? Oracle

    When we thought about using the IIS server in the college, we would have had to use Oracle with it, the problem here again is that it is not accessible from home so the only time you can use Oracle is when you are in the college, it is also only available in a small number of labs that we are not scheduled for.

? MySQL

    From the start we knew using this technology would be a challenge. In the initial weeks of college we found out that the college was not prepared, as in previous years to allow us to use MySQL. They said that there are other technologies that have been purchased and as MySQL is free, we should use what the college is providing.

? Lunar Pages

    We didn’t come up against any problems with this technology, but we have reasons for not choosing this path. For the use of Lunar it costs $7.95 a month, it hosts your MySQL database on their server, it also gives you help creating your database through wizards (no real coding yourself!). The thing is with this it would be quite risky in the fact that you only have your pages hosted online, what if the server goes down? And how reliable is it? Will the college turn around at the end of the year and ask who connect up the database? Answer: Lunar pages! It just seems to good to be true.

     5

    Section 2 Risk Management

Risk management

Introduction

    A risk is a probability that some adverse circumstance will actually occur.

    Risks may threaten the project, the software that is being developed or the

    organisation. (Sommerville, 2001)

    There are 3 main categories of risks that can occur. They are as follows:

    1. Project- This type of risk affects the project schedule or resources.

    2. Product- This type of risk will affect the quality or performance of the

    software that is being developed.

    3. Business- This type of risk will affect the organisation developing or

    procuring the software.

Risks usually stem from loosely defined requirements, difficulties in estimating

    the time and resources required for software development, dependence on

    individual skills and requirements changes due to changes in customers

    needs. These risks that can occur depend on the project and the

    organisational environment where the project is being developed.

    (Sommerville, 2001)

In the area of risk management there is a process that each project manager

    should follow. It is as follows:

    1. Risk Identification- Here all the possible project, product and business

    risks are identified.

    2. Risk Analysis- Within this section of risk management, the likelihood

    and consequences of these risks are assessed.

    3. Risk Planning- Here the plans to address the risk either by avoiding it

    or minimising the effects on the project are drawn up.

    4. Risk Monitoring- The risks are constantly assessed and plans for risk

    mitigation revised as more information about the risks becomes

    available to the team.

     6

Risk Identification

    Within this section of risk management, all of the risks that may occur while

    the project is being implemented are identified. These range from the smallest

    risk that may only cause minor problems, to risks that can jeopardise the

    entire project.

Risk type Possible risks

    Technology The server could fail as a result of a

    hardware or software problem which

    could result in loss of time

     Defects during implementation could

    result in incompatibility between the

    various software components

     The many security restrictions in place in

    the college could result the inability to

    implement some required functionality.

     Human error or technical failure could

    result in loss of data and project work. People If team members become ill or

    unavailable for periods of time, it could

    slow progress down.

     If the team members do not possess the

    necessary skills and abilities,

    implementation could become very

    difficult.

     If the members cannot function efficiently

    as a team, development could be slowed

    down and quality could be compromised. Requirements Poor requirements gathering at the start

    could lead to the requirements changing

    midway through implementation resulting

    in wasted effort and time.

     The misinterpretation of requirements

    could result in the wrong or unsuitable

    application being developed Estimation Underestimation of the size of the project

    could result in schedule overrun

     Underestimation of the complexity of the

    project could result in schedule overrun

     Underestimation of the time required to

    develop the project would result in

    schedule overrun

     Overestimation of the free time available

    to team members and access to required

    hardware and software could result in

    schedule overrun

     7

Risk Analysis

    This section covers the likelihood of the risks that were identified in risk

    identification occurring. Each one of them are assessed and the

    consequences of their occurrence analysed.

    Risk Probability Effects If the team members do Moderate Catastrophic not possess the

    necessary skills and

    abilities, implementation

    could become very

    difficult.

    Defects during Low Catastrophic implementation could

    result in incompatibility

    between the various

    software components

    Human error or Low Catastrophic technical failure could

    result in loss of data and

    project work.

    The misinterpretation of Low Catastrophic requirements could

    result in the wrong or

    unsuitable application

    being developed

    Underestimation of the High Serious time required to develop

    the project would result

    in schedule overrun

    Overestimation of the High Serious free time available to

    team members and

    access to required

    hardware and software

    could result in schedule

    overrun

    The many security High Serious restrictions in place in

    the college could result

    the inability to

    implement some

    required functionality.

    The server could fail as Moderate Serious a result of a hardware or

    software problem which

    could result in loss of

    time

     8

    Underestimation of the Moderate Serious size of the project could

    result in schedule

    overrun

    Underestimation of the Moderate Serious complexity of the project

    could result in schedule

    overrun

    Poor requirements Low Serious gathering at the start

    could lead to the

    requirements changing

    midway through

    implementation resulting

    in wasted effort and

    time.

    If team members Low Tolerable become ill or

    unavailable for periods

    of time, it could slow

    progress down.

    If the members cannot Low Insignificant function efficiently as a

    team, development

    could be slowed down

    and quality could be

    compromised.

     9

Risk Planning

    Within this section of risk management there are 3 main types of planning that

    can be developed:

    A. Avoidance Strategies: Following these strategies means the probability

    that the risk will arise will be reduced.

    B. Minimisation Strategies: Following these strategies means that the

    impact of the risk will be reduces

    C. Contingency Plans: Following these strategies means, if the worst

    happens, you are prepared for it and have a strategy in place to deal

    with it.

    Risk Strategy Lack of skills Allow time to research any areas

    where the team member’s skills are

    not sufficient. And Consult other

    people who do possess the

    necessary expertise.

Incompatibility between components Research all the technologies

    extensively and make sure that

    implementation is being done

    correctly.

Loss of Data Develop standard procedure for

     making regular backups of all work

    done and store multiple copies of

    these backups in various locations

    such on server on compact disc on

    college account and on home PC.

Misinterpreting Requirements Spend sufficient time analysing

    requirements and refer back regularly

    to make sure they are being followed.

Underestimate available time Organise all the required work so that

    if necessary computer lab is

    unavailable work can be done on

    something else so as to maximise the

    time.

Security Restrictions in the College Find out exactly what security

     restrictions are in place in the college,

    and analyse how they will affect the

    project. Then decide on alternatives

    or compromises. Server Failure Ensure that the team has access to

    one or more backup servers so that

    development can continue in the

     10

Report this document

For any questions or suggestions please email
cust-service@docsford.com